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.
I was having some trouble using my system (nothing happened - no logins, running programs stopped, etc. Ping from remote machines still worked; filesystems exported from this system and mounted on remote systems were still accessible from the remote machines) so I rebooted. The local filesystems were checked; one of them (200GB Seagate with a single ext3 fs on it) came up "/dev/hdg1: Recovering journal" and everything stopped. This was about two hours ago. The HDD access light is on full (unblinking).
Previously, I've found that if there's a power failure during a fsck, the disk becomes unusable - I've got two HDDs that I can't get any system to recognise (as *anything*).
If I reboot, am I likely to do any damage to my HDD (which has a lot of irreplacable data on it, and is not backed up...)
I'm running kernel version 2.4.20 with xfs patches; it was originally a redhat 7.2 system, but I've changed almost everything. It's on a dual-processor 500MHz celeron box.
"I've got two HDDs that I can't get any system to recognise (as *anything*)."
Do you mean from a BIOS point of view or the operating system?
The BIOS doesn't find them; fdisk says the device is invalid. As far as I can tell the firmware has been damaged, though how fsck could have done this is uncertain (to me, anyway.)
As for the current problem, I rebooted, and recovered the disk. I'm now in the process of backing the data up.
... am I likely to do any damage to my HDD (which has a lot of irreplacable data on it, and is not backed up...)
You are joking I hope.
Last time I lost a couple of drives like that was a power surge during a storm - it blew straight past my crappy UPS.
Tried all the "off the wall" remedies like sticking them in a freezer for the night. Nothing worked. They joined the pile of dead-uns' in the corner - a couple of S-ATA disks that seemed to have over-heated (before I upped the fans in the box).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.