Well, here's an update - and I'm not real happy about this but I'm
glad to share my pain. If you have root on a software RAID you can not
boot to an install CD and jump out at the first option to boot
installed system - you'll get the errors I saw. HOWEVER, if you stay
in the install (linuxrc?), you'll get a SECOND option to jump out and
boot the installed system and at that point the system CAN see the
software RAID devices!
All of this comes to late for me as I've already blown the thing a way
(I was able to break the mirror, mount the one partition and copy
everything off - so now we'll see how well I can just copy all of it
back into a new system, yuck!). BUT, it might save you all the
trouble.
AND, while I'm doing this (I guess I build lame linux boxes for fun
and work now) I'm writing down all of my steps in as much detail as
needed (which isn't much, really) and will share that with you as
well.
On 12/15/05, Olaf Hering
On Wed, Dec 14, Brian Loe wrote:
ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1 ReiserFS: md0: warning: vs-5150: search_by_key: invalid format found in block 4947981. Fsck? ReiserFS: md0: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occured trying to find stat data of [11 81164 0x0 SD] INIT: version 2.85 booting
and then the rest is a lof of the reiserfs run with --rebuild-tree errors... and loads a "maintenance mode" - which I guess I'm suppose to use to remount md0, run fsck with --rebuild-tree and reboot. Before I do that I want to make sure its not still some kind of bootloader issue.
I dont know how the reiserfs warnings can happen. The bootloader part is working ok.
-- short story of a lazy sysadmin: alias appserv=wotan