fdisk gives unable to read /dev/hda... mbr is gone... what can it be?
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
fdisk gives unable to read /dev/hda... mbr is gone... what can it be?
hi guys,
i have a bad situation with a new hd : 3 months old Western Digital 80 GB ...
rebooting ....
i got the detection process of the drives and everything was ok . . All my masters and slaves were detected..
after that, i got that classic screen looking for boot record ...
during this process, in my boot HD, i got a short loop of CPU beep .... : - (
after that i cannot reach my system anymore...
informations ..
1. i have backup of everything in the disk ... no problem to loose data..
2. "fdisk /dev/hda" gvives me "Unable to read /dev/hda"
3. i ran "fdisk /mbr" - with a MSDOS boot disk ... I hear that this would erase the MBR ...
After information "3",
i got no beep anymore during reboot . now there is a message..
"Missing operating system..."
but i still can't run "fdisk /dev/hda" ... I receive the same message again ..
"unable to read /dev/hda"....
I'm wondering if the drive itself is OK. Also make sure the cables are seated snuggly. If you don't mind loosing your data, you could run the Western Digital setup for new disks, might need to download this. If may contain a diagnostics program. Don't know if this would be destructive or not.
I've heard that some HDD require that you have special
drivers for them.
How about with a Windows CD? Can you use recovery console,
and fixbmr? Can you install NT?
Do you have a spare drive around? If that works, then, it
sounds like your new drive is the problem, and you can
return it on warranty.
My friend spent many hours over a few months trying to
coax his computer to boot. He did all kinds of things with the
hard drive. But, it turned out to be something on the motherboard.
He is now going to buy a new machine.
Delete ALL the partitions on the hard drive and start over. Sometimes,
the old file systems don't get wiped out and it causes lots of grief.
I speak from experience on this one. See my other post about grub.
now i am back with a new HD ...
the old one is history..
after trying the new world, at least for me, of e2fsck, dd, ...
nothing worked...
i still have the old hd ... it was in the garantie so i got a new one...
i never saw something like that...
WD really new and then gone..
dos-fdisk didn't see the drive also..
linux fdisk no chance..
anyway i still have it and i will try to figure out what happened..
thanks again for the feedback..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.