[SSI-devel] Re: 2.6.8.1 on SuSE
Brought to you by:
brucewalker,
rogertsang
From: Bharata B R. <bha...@hp...> - 2004-12-17 06:13:42
|
On Fri, 2004-12-17 at 00:12, Brian J. Watson wrote: > Bharata B Rao wrote: > > Hello Brian, > > > > While trying 2.6.8.1 ssi kernel on SuSE, I encountered the following > > problem. > > > > 1. The root device failed to mount. The following line in linuxrc gave > > an error: > > > > echo mkrootdev /dev/root | nash --quiet --force > > mount -o chard,defaults --ro -t ext3 /dev/root /sysroot > > > > Error was: /dev/root is not a valid block device. > > > > It appeared that nash failed to create a proper /dev/root (it refers to > > root= from kernel command line or /proc/sys/kernel/real-root-dev if > > former isn't available. So just to bypass this problem I added the > > following line to my linuxrc > > > > --> echo 0x6802 > /proc/sys/kernel/real-root-dev > > > > before calling nash, which temporarily bypassed this problem. > > I don't see this problem on FC2, which shouldn't be any different at > this stage, except maybe some minor differences in the way grub passes > command line arguments to the kernel. > > Do you have root= defined in your grub.conf? My grub.conf stanza is: Yes I have root=6802 defined in my menu.lst. Infact the stanza looks like this here: title Linux-ssi kernel (hd0,0)/vmlinuz-2.6.8.1-new root=6802 vga=0x31a splash=silent desktop resume=/dev/cciss/c0d0p3 showopts console=tty1 console=ttyS0,38400 initrd (hd0,0)/initrd-2.6.8.1-new.img > > > title Fedora Core (2.6.8.1_ssi_1) > > root (hd0,0) > > kernel /vmlinuz-2.6.8.1_ssi_1 ro root=LABEL=/ console=ttyS00,115200 > > initrd /initrd-2.6.8.1_ssi_1.img > > The console= argument is for serial console. > > > > 2. With that workaround, /sbin/init got started by the machine hung > > pretty early thereafter. The log follows: > > > > Starting init > > INIT: version 2.85 booting > > System Boot Control: Running /etc/init.d/boot > > Mounting /proc filesystem > > done > > Mounting sysfs on /sys > > done > > Mounting /dev/pts > > done > > tty_open:init_dev 0 failed) > > > > Entering kdb (current=0xddc060b0, pid 65904) on processor 0 due to > > Keyboard Entry > > [0]kdb> bt > > I came across this yesterday. It happens when you try to ssh into the > node. John can look at this when he's less busy. For now, use the > console instead. For convenience purposes, do you have a serial console > configured? Yes I am using a serial console, but the problem is not happening when I try ssh, but it happens very early in the boot. Regards, Bharata. |