Re: hard drive crash

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



I attempted the floppy and said not large enough disc, As far as boot
sequence I did esc on startup and chose my boot option from there. It listed
all drives and particular cd drives.



"Paul" wrote:

Phil wrote:
HP a324x winxp I have a WD400EB hard drive that crashed. The recovery discs
do not work. I downloaded data lifeguard diagnostic from WD site. I tried
both the windows 1 and the cd 1. I set the booot to cd drive. I'm getting a
long pause then a message saying file missing or corrupt hal.dll I also
tried putting the win xp disc in to see if i could reformat. same error.

downloaded the wd data tools to the desktop then burnt to cd on another
computer.

Does anyone have any thoughts?

Thank you.

Have you tried the floppy version ? On my Seagate drive, they offered
a floppy version, and it runs something like FreeDOS to bootstrap the
diagnostic. Maybe that would work, if your BIOS will stop looking
at the other storage devices long enough to obey the boot order in
the BIOS.

http://support.wdc.com/product/download.asp?modelno=wd400eb&x=0&y=0

Have you double checked that you did a "Save and Exit" when in the
BIOS, and that the boot order really does have floppy and CD ahead
of the hard drive ? If you did a "Discard and Exit", maybe the changes
were lost. Also, some computers have a temporary boot menu ("popup")
at BIOS time - sometimes you get to that by pressing F8. On my
particular motherboard, it is bound to the F11 key. If you can get
in there, you should be able to see the CD drive, and select it.

Other options include

1) Disconnect hard drive data cable, to verify the drive isn't holding
up a shared IDE cable data channel. You must be aware of the rules
for master/slace/cable select and filling the connector at the end
of the data cable first, when changing the configuration. Depending on
data cable length and position, this might not be as easy as it
sounds. You can leave power connected on the drive, with no data
cable connected.

2) You could try slaving the drive to a working computer, again,
following the rules for cabling IDE devices (jumpers etc). If
the other machine had a fully working Windows on it, you could
run your diagnostic from there.

At this point, I won't make the post longer, with a data recovery
procedure, as there is no point unless the diagnostic can give you
some results. If the disk really is "dead", then software won't fix
it. If this is just a partition table or file system problem, there
may be some options to get the data back or to fix it.

Paul

.



Relevant Pages

  • Re: installation problems
    ... RH 9 had trashed my Linux partition and rendered my PC unbootable. ... >you can create the floppy from and can be created on a differnet ... >on the CD as the floppy boot image. ... and since flash drives seem to be listed in /proc as scsi devices, ...
    (comp.os.linux.misc)
  • Re: in lieu of swapping out hard drives
    ... I am skeptical that usb and eSATA are handled the same way in the BIOS. ... boot, I am given the option to boot from the external drive." ... I plugged and unplugged, boooted from local drives, etc. about a dozen ...
    (microsoft.public.windowsxp.general)
  • Re: [SLE] Problems with initrd after mkinitrd
    ... Not a problem, Patrick... ... "4MB Flash ROM with AMI* BIOS, Multiboot BBS ... - it brings the possibility back to life that these drives (or the entire IDE ...
    (SuSE)
  • Re: RedHat Linux 7.2 needed.
    ... drives replaced with current stuff, ... Unfortunately, it has a few problems, including a fan ... If you mean floppy only, I don't remember the last distribution that was ... Red Hat Linux 9 uses a different boot diskette layout than ...
    (comp.os.linux.misc)
  • Re: Grub hangs - two hard drives and a CD
    ... > What you wrote is all based on a wrong assumption that grub numbers drives ... > that the BIOS will call to boot an OS. ... The Bios calls to read disk require the register DL to ...
    (comp.os.linux.setup)