Hi, I have two different linux systems and unfortunately both crashed very recently. One is a 3 (SCSI) disk machine
and apparently crashed after a power failure. When it tries to boot it recognizes all 3 disks, but is unable to read the third one(containing /home, unfortunately). This is a Seagate Barracuda disk from 1999, so maybe it is not unexpected to have a crash in 4 years.
The other one I am more concerned about is an IBM 38GB IDE
disk from 2001. This one is in a PC having two different
linux systems on it, one on /dev/hda is a 2.2.10 kernel
and is working fine. The second one(the one that crashed)
/dev/hdb had a 2.4.18 kernel. The crash occured fairly suddenly, I had an open shell from KDE doing a vi
of a file, had to go discuss somewhere for half an hour then when I got back the system was hung, I alt-ctrl-backspace and then rebooted and the difference is it will
not even see the second disk(which gives me some hope that
it is not some partition that has crashed, but maybe a bad connection?)
Does anyone understand why in one case BIOS sees the faulty
disk and in the other case it pretends it's not even there?
Any suggestions what to do next?
I am able to boot via floppy(since lilo was on /dev/hdb)
but cannot mount /dev/hdb2 /tmp/root or home
of course, it does not even admit there is a second HD
in there.
Thanks in advance for any help,
svar
and apparently crashed after a power failure. When it tries to boot it recognizes all 3 disks, but is unable to read the third one(containing /home, unfortunately). This is a Seagate Barracuda disk from 1999, so maybe it is not unexpected to have a crash in 4 years.
The other one I am more concerned about is an IBM 38GB IDE
disk from 2001. This one is in a PC having two different
linux systems on it, one on /dev/hda is a 2.2.10 kernel
and is working fine. The second one(the one that crashed)
/dev/hdb had a 2.4.18 kernel. The crash occured fairly suddenly, I had an open shell from KDE doing a vi
of a file, had to go discuss somewhere for half an hour then when I got back the system was hung, I alt-ctrl-backspace and then rebooted and the difference is it will
not even see the second disk(which gives me some hope that
it is not some partition that has crashed, but maybe a bad connection?)
Does anyone understand why in one case BIOS sees the faulty
disk and in the other case it pretends it's not even there?
Any suggestions what to do next?
I am able to boot via floppy(since lilo was on /dev/hdb)
but cannot mount /dev/hdb2 /tmp/root or home
of course, it does not even admit there is a second HD
in there.
Thanks in advance for any help,
svar