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 /?