http://bugzilla.novell.com/show_bug.cgi?id=483136
http://bugzilla.novell.com/show_bug.cgi?id=483136#c31
Felix Miata changed:
What |Removed |Added
----------------------------------------------------------------------------
Info Provider|mrmazda@earthlink.net |mmarek@novell.com
--- Comment #31 from Felix Miata 2010-02-22 12:14:15 UTC ---
"It fails" means the same thing here as I wrote in comment 0. Quoting comment
0: "Waiting for device /dev/root to appear ... could not find /dev/root ...
want to fall back to /dev/....". With root=LABEL=10suse113 on cmdline, it's
/dev/md3 that it asks to fall back to, then after answering y, it's "Waiting
for
device /dev/md3 to appear ... not found -- exiting to /bin/sh; sh: cannot set
terminal process group (-1): Inappropriate ioctl for device; sh: no job control
in this shell; $"
'$ mdadm --assemle /dev/md3 /dev/sda10 /dev/sdb10' appears to work, with 'mount
-t ext3 /dev/md3 /' also working, but I don't know what to try next, as 'init
1' next fails.
If I boot with root=/dev/sda10 on cmdline I get what appears to be a normal
boot result, with /dev/md10 on /. Should I add linuxrc=debug to that and then
run mkinitrd? I don't know capture via serial console process. Will
/boot/log/YaST2/mkinitrd.log provide the output you want instead?
I must have typed something wrong when I tried to boot by changing from
root=LABEL=10suse113 to root=/dev/md10 in the gfx Grub edit box before writing
comment 29. Now when I try root=/dev/md10 I get what seems to be a normal boot
with no apparent waiting for /dev/root to appear. /dev/md[0-6] are all mounted
where they belong according to mount output.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.