Anyone know what causes this failure? I had shut down my linux box properly (formatted with ReiserFS) and 8.0 pro, turned my computer on today to a kernel panic - couldn't mount FS. Doh. Apparently my drive is munged ... It had been working perfectly. I am unsure if it's a hardware failure or a software one (I eventually bailed on trying to salvage the drive, rebooted into XP Pro and formatted the drive). No errors found. I have a SuperMicro P4DC6+ with duel Prestonia Xeon 2.2ghz, 1 gig of RAM. The drive was just a little 20 gig EIDE I had used to test out Suse 8.0 pro. Any advice? Thanks, Sean
I have a SuperMicro P4DC6+ with duel Prestonia Xeon 2.2ghz, 1 gig of RAM. The drive was just a little 20 gig EIDE I had used to test out Suse 8.0 pro.
What drive is it? I would use the testing/fixing tools that the manufacturer may have available.
Any advice?
Thanks,
Sean
Matt
Try booting from the DVD/CD and see if you can mount the filesystem. Also, I've had my laptop do strange things. Depending on the phase of the moon, my CD/DVD comes up as some corruption of Toshiba most of the time, but occasionally it gets it right. On 3 Jun 2002 at 15:09, Sean McGrath wrote:
Anyone know what causes this failure? I had shut down my linux box properly (formatted with ReiserFS) and 8.0 pro, turned my computer on today to a kernel panic - couldn't mount FS.
Doh.
Apparently my drive is munged ... It had been working perfectly. I am unsure if it's a hardware failure or a software one (I eventually bailed on trying to salvage the drive, rebooted into XP Pro and formatted the drive). No errors found.
I have a SuperMicro P4DC6+ with duel Prestonia Xeon 2.2ghz, 1 gig of RAM. The drive was just a little 20 gig EIDE I had used to test out Suse 8.0 pro.
Any advice?
Thanks,
Sean
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
-- Jerry Feldman Enterprise Systems Group Hewlett-Packard Company 200 Forest Street MRO1-3/F1 Marlboro, Ma. 01752 508-467-4315 http://www.testdrive.compaq.com/linux/
On Monday 03 June 2002 8:09 pm, you wrote:
Anyone know what causes this failure? I had shut down my linux box properly (formatted with ReiserFS) and 8.0 pro, turned my computer on today to a kernel panic - couldn't mount FS.
Any advice?
"reiserfsck --rebuild-sb" might get you out of it. Doesn't look good though... :( -- 3:14pm up 23 days, 7:25, 1 user, load average: 0.23, 0.06, 0.02
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 05 June 2002 09:16, Derek Fountain wrote:
On Monday 03 June 2002 8:09 pm, you wrote:
Anyone know what causes this failure? I had shut down my linux box properly (formatted with ReiserFS) and 8.0 pro, turned my computer on today to a kernel panic - couldn't mount FS.
Any advice?
"reiserfsck --rebuild-sb"
might get you out of it. Doesn't look good though... :(
I've noticed that when the system hangs and I reboot, it always says "WARNING: Log replay on read-only filesystem." Thus the / filesystem is never repaired after a crash. This has been going on with Reiser since Suse7.1 . How does one check/repair /? - -- War is peace. Freedom is slavery. Ketchup is a vegetable. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjz+JAUACgkQnQ18+PFcZJsgZgCeMDkR2ud0rQXalYpIRyRnFZrE oaIAnjNIVbtPocdCBkeEjZ2+dMEck9+x =CXeF -----END PGP SIGNATURE-----
Not sure how to help you... for me it was simply a bad Maxtor drive. Doh. I should have noticed something funny... every time I reboot my BIOS had to update with new information from the drive. I reinstalled from scratch on a new drive, and other than Yast2 dying after upgrading to KDE 3.0.1, all is well... Sean -----Original Message----- From: Carl [mailto:quantum@ultra2k.com] Sent: Wednesday, June 05, 2002 10:45 AM To: suse-linux-e@suse.com Subject: Re: [SLE] Wahh -- bad superblock hard drive failure -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 05 June 2002 09:16, Derek Fountain wrote:
On Monday 03 June 2002 8:09 pm, you wrote:
Anyone know what causes this failure? I had shut down my linux box properly (formatted with ReiserFS) and 8.0 pro, turned my computer on today to a kernel panic - couldn't mount FS.
Any advice?
"reiserfsck --rebuild-sb"
might get you out of it. Doesn't look good though... :(
I've noticed that when the system hangs and I reboot, it always says "WARNING: Log replay on read-only filesystem." Thus the / filesystem is never repaired after a crash. This has been going on with Reiser since Suse7.1 . How does one check/repair /?
participants (5)
-
Carl -
Derek Fountain -
Jerry Feldman -
Matthew Johnson -
Sean McGrath