What is the nitty gritty on the steps that defrag uses?

Specifically, can a crash of the computer during defrag lose or corrupt the
file that was in process at the time of the crash?

I had XP SP3 crash hard during a defrag with Auslogics defragger. I don't
know why. I rebooted afterwards, and all seemed well. There was a 2.048 GB
dump file on my C drive (the same size as my RAM), which I deleted. XP
appears to be running normally. But since I have several hundred programs
and utilities installed, it's hard to know if something may be corrupted
somewhere.

I ran the full 6 step disk check in XP prior to the next bootup, and all
tested out perfectly - no disk problems. But I continue to wonder if the
file that was being processed at the time of the crash was damaged.

I'd like to know the sequence of steps in the defrag process. Can a crash
compromise the file being defragged at the instant of the crash?

Ron Hirsch

NTFS is a "Journaling" file system. A further extension of those
capabilities
is found in Vista's Transactional NTFS format. Both provide protections
against data loss.

"Ron Hirsch" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> What is the nitty gritty on the steps that defrag uses?
>
> Specifically, can a crash of the computer during defrag lose or corrupt
> the
> file that was in process at the time of the crash?
>
> I had XP SP3 crash hard during a defrag with Auslogics defragger. I don't
> know why. I rebooted afterwards, and all seemed well. There was a 2.048 GB
> dump file on my C drive (the same size as my RAM), which I deleted. XP
> appears to be running normally. But since I have several hundred programs
> and utilities installed, it's hard to know if something may be corrupted
> somewhere.
>
> I ran the full 6 step disk check in XP prior to the next bootup, and all
> tested out perfectly - no disk problems. But I continue to wonder if the
> file that was being processed at the time of the crash was damaged.
>
> I'd like to know the sequence of steps in the defrag process. Can a crash
> compromise the file being defragged at the instant of the crash?
>
> Ron Hirsch
>

On Sat, 22 Nov 2008 18:52:44 -0500, "Ron Hirsch"
<(E-Mail Removed)> wrote:

>I had XP SP3 crash hard during a defrag with Auslogics defragger. I don't
>know why. I rebooted afterwards, and all seemed well. There was a 2.048 GB
>dump file on my C drive (the same size as my RAM), which I deleted. XP
>appears to be running normally. But since I have several hundred programs
>and utilities installed, it's hard to know if something may be corrupted
>somewhere.

It is extremely unlikely that you'll ever find out. Rest assured that
interrupting a defrag session normally doesn't result in any harm.

You say your system is running fine. Relax. Move on.

Unless you can't because you're one of those who believes "Just
because you're paranoid doesn't mean they aren't following you".

Hi Charlie and McCarty,

Thanks to you both for your replies.

I Googled "journaling file system", and this link has some good data on what
that is.

http://en.wikipedia.org/wiki/Journaling_file_system

My problem is that I'm always a very curious person. :-)

When the crash occurred, I should have taken out a digital camera, and shot
the blue screen, for my info. But I did not not. The Event Viewer in XP did
list the crash, but there was really no info on the cause, that I could see.

I am now a little nervous about doing my next weekly defrag. But, since I
also create weekly images of my C drive via True Image, if it should occur
again, I'll just restore an image from before the crash. The complete 6 step
chkdsk showed zero problems on the drive, so it should be fine. Actually, it
is a relatively new drive. The prior drive had a serious problem, and I had
to replace it last summer. It apparently had some problems that were
difficult to diagnose, with a sector(s) in the free space, and was causing
problems when the system tried to write to that area.

Thanks again

Ron

Ron

My concern would be what caused the crash and do I need to fix something
so that it doesn't happen again. What was the complete Stop Error
report?

Have you installed any other Auslogic software like Boost Speed?


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

Ron Hirsch wrote:
> What is the nitty gritty on the steps that defrag uses?
>
> Specifically, can a crash of the computer during defrag lose or
> corrupt the file that was in process at the time of the crash?
>
> I had XP SP3 crash hard during a defrag with Auslogics defragger. I
> don't know why. I rebooted afterwards, and all seemed well. There was
> a 2.048 GB dump file on my C drive (the same size as my RAM), which I
> deleted. XP appears to be running normally. But since I have several
> hundred programs and utilities installed, it's hard to know if
> something may be corrupted somewhere.
>
> I ran the full 6 step disk check in XP prior to the next bootup, and
> all tested out perfectly - no disk problems. But I continue to wonder
> if the file that was being processed at the time of the crash was
> damaged.
>
> I'd like to know the sequence of steps in the defrag process. Can a
> crash compromise the file being defragged at the instant of the crash?
>
> Ron Hirsch

"Ron Hirsch" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Hi Charlie and McCarty,
>
> Thanks to you both for your replies.
>
> I Googled "journaling file system", and this link has some good data on
> what
> that is.
>
> http://en.wikipedia.org/wiki/Journaling_file_system
>
> My problem is that I'm always a very curious person. :-)
>
> When the crash occurred, I should have taken out a digital camera, and
> shot
> the blue screen, for my info. But I did not not. The Event Viewer in XP
> did
> list the crash, but there was really no info on the cause, that I could
> see.
>
> I am now a little nervous about doing my next weekly defrag. But, since I
> also create weekly images of my C drive via True Image, if it should occur
> again, I'll just restore an image from before the crash. The complete 6
> step
> chkdsk showed zero problems on the drive, so it should be fine. Actually,
> it
> is a relatively new drive. The prior drive had a serious problem, and I
> had
> to replace it last summer. It apparently had some problems that were
> difficult to diagnose, with a sector(s) in the free space, and was causing
> problems when the system tried to write to that area.
>
> Thanks again
>
> Ron
>
A "weekly defrag"!!! You really believe in overkill.
Jim

Gerry,

That is my real concern - waht did cause th crash. That is why I've trying
to understand what happened.

I have no other Auslogic software installed. The defrag software has been
used for about 6 months, with no problem. As I noted, the 6 step XP chkdsk
showed the C drive as 100% OK in all areas.

There is always the possibility that the bit error rate for hard drives
finally slipped a bit somewhere, but that's being too optimistic.

After I create my weekly image of the C drive, I plan on running Auslogic
defrag again.

The only info in the event viewer is

Category 102
Event ID 1003

Error code 000000d1, parameter1 00000060, parameter2 00000002, parameter3
00000000, parameter4 ba7074c6.


Ron

++++++++++++++++++++++++++

"Gerry" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
Ron

My concern would be what caused the crash and do I need to fix something
so that it doesn't happen again. What was the complete Stop Error
report?

Have you installed any other Auslogic software like Boost Speed?

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

Ron Hirsch wrote:
> What is the nitty gritty on the steps that defrag uses?
>
> Specifically, can a crash of the computer during defrag lose or
> corrupt the file that was in process at the time of the crash?
>
> I had XP SP3 crash hard during a defrag with Auslogics defragger. I
> don't know why. I rebooted afterwards, and all seemed well. There was
> a 2.048 GB dump file on my C drive (the same size as my RAM), which I
> deleted. XP appears to be running normally. But since I have several
> hundred programs and utilities installed, it's hard to know if
> something may be corrupted somewhere.
>
> I ran the full 6 step disk check in XP prior to the next bootup, and
> all tested out perfectly - no disk problems. But I continue to wonder
> if the file that was being processed at the time of the crash was
> damaged.
>
> I'd like to know the sequence of steps in the defrag process. Can a
> crash compromise the file being defragged at the instant of the crash?
>
> Ron Hirsch

Hi Jim,

Yes, you could say that. But a weekly defrag takes only a couple of minutes,
as there's not much to defrag. We all have our "thing". I'm a very neat and
organized person, and I practise overkill in many areas.

I also create an image of my C drive weekly, and I back up all my data et al
after every session. I have a good program (Folder Sync) where I write
scripts to do that - so it's a piece of cake. I store images and backups on
a variety of drives - E: and F:, which are internal, and a number of USB
external drives.

True Image has saved me many times when I had hardware failures of drives,
and occasonal weird corruptions which were difficult to analyze, and fix.
Hard drives are guaranteed fo fail someday. I've had about 7 such failures
in my 22 years of using computers. In the beginning, using floppies, then
tapes, was a tough way to go. True Image is something that every computer
user should consider using. If I have my C drive crash and burn, I can
change the drive to a new already formatted one (which I always have on
hand), run TI from the recovery CD, and restore things to normal, all in
about 20 minutes.

I built the system - so I know my around it very well. All my activities are
for personal use - I retired many years ago.

That's a lot quicker than starting from scratch. Revo uninstaller lists over
200 programs et al that are installed. Plus I have about 15-20 external USB
devices. And I have much of my software highly customized. Starting from
scratch would probably take me at least 100 hours to get things back in
order.

So yes, I believe on overkill on everything. :-)

Ron

+++++++++++++++++++++
>
A "weekly defrag"!!! You really believe in overkill.
Jim

Ron

Disable automatic restart on system failure. This should help by
allowing time to write down the STOP code properly should they occur
again. Right click on the My Computer icon on the Desktop and select
Properties, Advanced, Start-Up and Recovery, System Failure and uncheck
box before Automatically Restart.

It is best to leave it as disabled even after you resolve the problem.

Background information on Stop Error message
http://msdn2.microsoft.com/en-us/library/ms795930.aspx

0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
The system attempted to access pageable memory using a kernel process
IRQL that was too high. The most typical cause is a bad device driver
(one that uses improper addresses). It can also be caused by caused by
faulty or mismatched RAM, or a damaged pagefile.
Source: http://aumha.org/a/stop.htm

http://www.microsoft.com/whdc/devtoo...nstallx86.mspx

Are there any yellow question marks in Device Manager? Right click on
the My Computer icon on your Desktop and select Properties,
Hardware,Device Manager. If yes what is the Device Error code?

Try Start, Run, type "sigverif.exe" without quotes and hit OK. What
drivers are listed as unsigned? Disregard those which are not checked.

Which version of Windows XP? Home Edition, Professional or?

What hardware changes have you made recently?

Have chaned any IRQ settings?

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Ron Hirsch wrote:
> Gerry,
>
> That is my real concern - waht did cause th crash. That is why I've
> trying to understand what happened.
>
> I have no other Auslogic software installed. The defrag software has
> been used for about 6 months, with no problem. As I noted, the 6 step
> XP chkdsk showed the C drive as 100% OK in all areas.
>
> There is always the possibility that the bit error rate for hard
> drives finally slipped a bit somewhere, but that's being too
> optimistic.
>
> After I create my weekly image of the C drive, I plan on running
> Auslogic defrag again.
>
> The only info in the event viewer is
>
> Category 102
> Event ID 1003
>
> Error code 000000d1, parameter1 00000060, parameter2 00000002,
> parameter3 00000000, parameter4 ba7074c6.
>
>
> Ron
>
> ++++++++++++++++++++++++++
>
> "Gerry" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> Ron
>
> My concern would be what caused the crash and do I need to fix
> something so that it doesn't happen again. What was the complete Stop
> Error
> report?
>
> Have you installed any other Auslogic software like Boost Speed?
>
> Hope this helps.
>
> Gerry
> ~~~~
> FCA
> Stourport, England
> Enquire, plan and execute
> ~~~~~~~~~~~~~~~~~~~
>
> Ron Hirsch wrote:
>> What is the nitty gritty on the steps that defrag uses?
>>
>> Specifically, can a crash of the computer during defrag lose or
>> corrupt the file that was in process at the time of the crash?
>>
>> I had XP SP3 crash hard during a defrag with Auslogics defragger. I
>> don't know why. I rebooted afterwards, and all seemed well. There was
>> a 2.048 GB dump file on my C drive (the same size as my RAM), which I
>> deleted. XP appears to be running normally. But since I have several
>> hundred programs and utilities installed, it's hard to know if
>> something may be corrupted somewhere.
>>
>> I ran the full 6 step disk check in XP prior to the next bootup, and
>> all tested out perfectly - no disk problems. But I continue to wonder
>> if the file that was being processed at the time of the crash was
>> damaged.
>>
>> I'd like to know the sequence of steps in the defrag process. Can a
>> crash compromise the file being defragged at the instant of the
>> crash?
>>
>> Ron Hirsch

Ron Hirsch wrote:
> Hi Jim,
>
> Yes, you could say that. But a weekly defrag takes only a couple of minutes,
> as there's not much to defrag. We all have our "thing". I'm a very neat and
> organized person, and I practise overkill in many areas.
>
> I also create an image of my C drive weekly, and I back up all my data et al
> after every session. I have a good program (Folder Sync) where I write
> scripts to do that - so it's a piece of cake. I store images and backups on
> a variety of drives - E: and F:, which are internal, and a number of USB
> external drives.
>
> True Image has saved me many times when I had hardware failures of drives,
> and occasonal weird corruptions which were difficult to analyze, and fix.
> Hard drives are guaranteed fo fail someday. I've had about 7 such failures
> in my 22 years of using computers. In the beginning, using floppies, then
> tapes, was a tough way to go. True Image is something that every computer
> user should consider using. If I have my C drive crash and burn, I can
> change the drive to a new already formatted one (which I always have on
> hand), run TI from the recovery CD, and restore things to normal, all in
> about 20 minutes.
>
> I built the system - so I know my around it very well. All my activities are
> for personal use - I retired many years ago.
>
> That's a lot quicker than starting from scratch. Revo uninstaller lists over
> 200 programs et al that are installed. Plus I have about 15-20 external USB
> devices. And I have much of my software highly customized. Starting from
> scratch would probably take me at least 100 hours to get things back in
> order.
>
> So yes, I believe on overkill on everything. :-)
>
> Ron
>
> +++++++++++++++++++++
> A "weekly defrag"!!! You really believe in overkill.
> Jim
>
>
I would say you are so well protected that you need not worry about any
crashes that occur during defrag. You might consider changing weekly
defrags to monthly, though.

I've had a few crashes but only lost a hard disk once in 25 years of
computer ownership. The first few years don't count, as there were only
floppy disks then. <G> And, yes, I use Acronis True Image to back up.

Bill