Click to See Complete Forum and Search --> : Did I just fry my TWO new Hard Drives?
I don't understand.
I installed RH 9 yesterday on my WD 80GB HDD. Then after some problems I decided to uninstall it, so I went into the linux rescue mode, used parted to delete partitions. Then MS-DOS to fdisk /mbr.
Now, trying to install Win and it gives me - couldn't load setupdd.sys file.
Trying to install RedHat 9 - right when it starts to "formatting" I get Kernel panics, some Stack errors etc.
I've tried to fdisk, tried to format using WD Utilities etc - same thing, Windows/Linux won't install.
What's the problem? Exactly the same thing happend on my other HDD. They're brand new. What's going on? It hangs when it tries to format.. what could be the problem?
sarah31
08-12-2003, 04:14 PM
try zeroing the mbr or if that fails zero the whole drive.
How.. :) Never done it before.
sarah31
08-12-2003, 04:21 PM
look at this thread (http://www.justlinux.com/forum/showthread.php?s=&threadid=108732)
I've tried:
dd if=/dev/zero of=/dev/hda
and it gives me same crap Kernel problems....
Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing
The Linux Kid
08-12-2003, 04:48 PM
If you can use a windoze box, go to google and search for Zapdisk. Copy this to a dos boot disk and put the disk in your computer that needs to be fixed. Boot off the disk and type zapdisk. Press yes and all that sort of thing and after a few seconds your mbr + some more will all be destroyed! It worked for me when I had a similar problem to the one that you are now facing.
Hope that helps,
The Linux Kid.
Same thing... didn't help :(
mrBen
08-12-2003, 06:09 PM
Grab the relevant testing tool from the WD website, and use it to test your drive and/or erase/zero the drive.
mdwatts
08-12-2003, 06:13 PM
Is this the 8mb cache WD 80gb HD?
I just replaced my 2mb cache 80gb Maxtor with the WD and find I have to boot twice to get the damn thing recognized by the bios or else the bootloader of course will not startup.
I've tried 'auto' and 'user defined' in the bios and I still have the same problem.
:mad: :mad: :mad:
Got it to work somehow -- here is the problem - when I list it as hda - doesn't work, when I change it to hdb (with the cable) it does work.
Why won't it work as hda?
Also, if I install a second HDD and it lists it as hda will it cause any problems?
mdwatts
08-12-2003, 06:23 PM
How are the jumpers set on both drives? Cableselect or as master and slave?
I never use cableselect myself... only jumper as either master or slave.
anmaxp
08-12-2003, 07:11 PM
I just replaced my 2mb cache 80gb Maxtor with the WD and find I have to boot twice to get the damn thing recognized by the bios or else the bootloader of course will not startup.
mdwatts, i had the same problem with my WD 40gb drive, turns out there's a feature on the 40 to 120gb drives that 'spins down' the drive to reduce noise or something like that, and somehow its not working properly. anyways i also had to reboot my pc several times to get the drive recognized (even tried playing with jumpers and cables)
anyways wd has an update for these drives to get them working fine again, check it out
http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_admin=1&p_faqid=913&p_created=1047068027
or go to http://support.wdc.com/download/ and download the IDE Upgrade Utility (Non-3Ware controller cards) , make a bootdisk and run the util...
that should get u guys up n running again!!
btw, i also had problems reading and writing to the drive before the update
Originally posted by mdwatts
I never use cableselect myself... only jumper as either master or slave. Yeah, cable select can be problematic sometimes- I always hard-set my Master/Slave jumpers instead.
mdwatts
08-13-2003, 05:25 AM
Originally posted by anmaxp
mdwatts, i had the same problem with my WD 40gb drive, turns out there's a feature on the 40 to 120gb drives that 'spins down' the drive to reduce noise or something like that, and somehow its not working properly. anyways i also had to reboot my pc several times to get the drive recognized (even tried playing with jumpers and cables)
anyways wd has an update for these drives to get them working fine again, check it out
http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_admin=1&p_faqid=913&p_created=1047068027
or go to http://support.wdc.com/download/ and download the IDE Upgrade Utility (Non-3Ware controller cards) , make a bootdisk and run the util...
that should get u guys up n running again!!
btw, i also had problems reading and writing to the drive before the update
Thanks anmaxp as you've saved me a bit of searching around WD's site. :)
mrBen
08-13-2003, 05:48 AM
Note for all:
You should _never_ use cable select unless you are absolutely positive that you have the correct type of cable, and that your motherboard supports it. Given that only a tiny proportion of older motherboard do (mostly in old Dell and Compaq machines) it's not usually worth the hassle.
Master and Slave rules (until we all switch to S-ATA)
hard candy
08-13-2003, 06:08 AM
But the newer 80 conductor ultra DMA ATA cables do support cable select and the newer mother boards with the new cables do support it. Here's a good article on it:
Cable select (http://www.pcguide.com/ref/hdd/if/ide/confCS-c.html)
AussieJohn
08-13-2003, 06:52 AM
Regardless of what HardCandy quotes, Mr Ben is correct.
I use 2 of WDs 80Gb (8mb) HDDs and use round cables but I do not use cable select (and never have done) and I HAVE NEVER HAD ANY SETUP OR RUNNING PROBLEMS EVER.
You must take time to read Western Digitals' instructions for install carefully and not just go using what you think are the okay install procedures.
Cheers.
phil_r
08-13-2003, 08:21 AM
On this topic, for a machine that has 2 hd's and 2 cdrom drives, would people advocate one hd and one CD per cable or 2 hd's on one cable and the two cdroms on the other?
Phil.
hard candy
08-13-2003, 09:11 AM
It really depends on which way most of the data will be going, HD --> CDRW should go a little faster if they are on separate channels.
IMHO, /dev/hda and cdrom on channel one (if hda is primary drive writing to cdrw) and hdb and cdrw on channel two.
And I have used cable select on my system with 2 Maxtor drives and a cdrom and cdrw all with cable select and 80 connector flat cables for 6 months with no problems other than bad blocks on a since replaced Maxtor drive. I believe most of the newer off- the- shelf systems use cable select. I know Dell uses it as their default.
mdwatts
08-14-2003, 03:27 PM
Originally posted by anmaxp
mdwatts, i had the same problem with my WD 40gb drive, turns out there's a feature on the 40 to 120gb drives that 'spins down' the drive to reduce noise or something like that, and somehow its not working properly. anyways i also had to reboot my pc several times to get the drive recognized (even tried playing with jumpers and cables)
anyways wd has an update for these drives to get them working fine again, check it out
http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_admin=1&p_faqid=913&p_created=1047068027
or go to http://support.wdc.com/download/ and download the IDE Upgrade Utility (Non-3Ware controller cards) , make a bootdisk and run the util...
that should get u guys up n running again!!
btw, i also had problems reading and writing to the drive before the update
I tried the wdnewcfg.exe utility, but it kept telling me it cannot find a 'WDC' device.
I had a look on the WD support site and one solution was to remove the jumper if you only have a single device (HD) on the channel of which I do.
Strange as I always jumper my HD's as master even though they sometimes are the only device on the channel and I've never had any problems before this happened.
Well it worked as the bios now detects the WD on first boot and Grub doesn't take 20 seconds to finally load.
anmaxp
08-14-2003, 07:20 PM
that's weird, i got it to run the first time i ran the app from a bootdisk, well anyways at least u have it working now!!!
glad if i could be of some help whatsoever :D
For those who are interested - turns out bad memory stick! :mad:
anmaxp
08-15-2003, 05:06 PM
For those who are interested - turns out bad memory stick!
mhh thats why whenever i see one of my pc's acting weird the first thing i do is to change the memory sticks... hey, its saved me from hours of bangin' my head against the keyboard :p
mdwatts
08-16-2003, 08:23 AM
Originally posted by anmaxp
that's weird, i got it to run the first time i ran the app from a bootdisk, well anyways at least u have it working now!!!
glad if i could be of some help whatsoever :D
Yes you were... Thanks again.
Originally posted by mdwatts
Thanks anmaxp as you've saved me a bit of searching around WD's site.