Prev: S.M.A.R.T. reallocated sector count failure
Next: Jbod NAS
From: ndy on 25 Feb 2006 02:08
lately I have been getting this message on a DOS screen upon startup,
first from hibernation, and now from a shutdown restart. does this mean
my HD is failing, or can it be file corruption?

over the last 3-4 weeks I have been occasionally getting this error
message after starting from hibernation mode. it just sits there, push
any key and it makes no difference, can't use F8, anything.
I'll turn it off and then it would proceed to starting the hibernation
startup. as of late it has taken more than 1 reboot, and then it got to
like 4 or so so I figured I better stop with that for a while and just
shutdown regular, but it is also doing this from a shutdown as well.
both, after the machine has been off for some time or usually, overnight.

at first I thought it might have something to do with my DSL modem as I
have a recent habit of turning it off some time while the computer is
down or in hibernation when I figure I won't be needing it for a day or
so and thought maybe this was changing the configuration, different from
when it shut off and upsetting the apple cart. but I think this turning
it on, off, before shutdown, after, whatever, which seemed to make some
difference, now was only anecdotal as some initial investigation seem to
be something to do with the HD itself, rather than any program as I
haven't really done much change to the machine except for the usual MS
updates over the last month or any change to a bios.

this last time I started my computer from a overnight shutdown it took 6
reboots to get it to go past the screen and it is getting a little scary.

a Google search suggest this is nothing new and some suggest its a HD
failure. but the drive is only a few months old with a clean XP Pro
install and worked for a month without any problems then this started
intermittently, and now slowly getting worse, to now pretty much every
time. I dare not turn my machine off right now and figure I guess a call
to Maxtor in in order, but it is the weekend. some suggest corrupted
files such as the boot sector and/or the ntdetect, ntldr files.

any ideas to do help narrow the causes, or can it be such a myriad of
things, I'm screwed???

thanks ..........
 | 
Pages: 1
Prev: S.M.A.R.T. reallocated sector count failure
Next: Jbod NAS