Okay, here's where I got. I followed your instructions strictly and
the boot would hang waiting for device md - so I changed the lilo.conf
file to read append="root=/dev/md0" and ran through the rest of the
instructions again.
Upon reboot it did all of the same things (recreating the raid drives,
etc.) and then found /dev/md0, but the next lines read:
no record for 'md0' in database
rootfs: major=9 minor=0 devn=2304
Mounting root /dev/md0
ReiserFS: md0: found reiserfs format "3.6" with standard journal
ReiserFS: md0: using ordered data mode
ReiserFS: md0: journal params: device md0, size 8192, journal first
block 18, max trans len 1024, max batch 900, max commit age 30, max
trans age 30
ReiserFS: md0: checking transaction log (md0)
ReiserFS: md0: Using r5 hash to sort names
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.
Oh, and THANK YOU OLAF!!!!!!! I can feel that I'm getting very close
now - so long as I don't lose everything trying to fix this drive
problem!
On 12/14/05, Olaf Hering
On Wed, Dec 14, Brian Loe wrote:
Do I do this from the rescue prompt or do I boot to the installed system and mount / and /var rw manually?
You can do this from the installed system. Make sure that sda2 is not mounted and part of /etc/fstab. parted (unlike fdisk) can edit partitions which are not used by the system.
-- short story of a lazy sysadmin: alias appserv=wotan