If the raid1 is a disk, remove one of the disks from the raid and reboot, see
what happens. If problem persists swap the raid disks and try again. Check
the bootlog, see what the kernel has to say about the boot process, see of
there is any mention of raid in there... This could easily be a dead disk in
a raid.
Well I'm convinced it's not the disk. When I run fsck I can see the directories scrolling by. Not only that, I just unplugged the drive that does not have the OS on it, same error. Plus, when I boot with Knoppix 3.7 I can see/read all the partitions on both drives.
I cannot fully boot, I'm just left with a prompt asking for the root password, once authenticated, no network, no hostname (like runlevel 1 or something).
Just out of curiosity, is reiser for real or what? Three weeks, that's the worst filesystem crash I have ever seen. Or is it RAID that SuSE is incapable of? IIRC, I was only able to make a RAID volume with reiser.
The boot process isn't logged, my /var/log/boot.log file is empty.
cS
_______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
