https://bugzilla.novell.com/show_bug.cgi?id=340971#c1 --- Comment #1 from Pieter Hollants 2007-11-12 04:32:34 MST --- Argh. Wrong UUID. So, strictly speaking, INVALID. However, could it be possible to add a more verbose error message to mkinitrd, causing it to abort what it can't stat()? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=340971 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm@novell.com AssignedTo|kernel-maintainers@forge.provo.novell.com |hare@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=340971#c4 Hannes Reinecke changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #4 from Hannes Reinecke 2007-11-16 03:13:08 MST --- And I must say the error indicates it quite clearly. It tries to mount a device / file which isn't there. _Why_ it isn't there is exactly the task of the admin to find out. mkinitrd cannot really know that you did a spelling error :-) And for the RAID device: The mkinitrd should be created with RAID support, otherwise it won't be able to start the RAID and hence it'll try to access the underlying devices. Doesn't do much harm in your case (as you're most likely running a mirrored RAID), but in general it won't work. If we were misdetecting the RAID then this would be a bug; but a different one, please. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=340971#c6 --- Comment #6 from Pieter Hollants 2007-11-16 03:25:17 MST --- Also, with regard to Lars' comment, it's not about RAID support in the created initrd, but the output of the mkinitrd run itself: Root device: UUID=cb9e1c18-d895-4be2-8303-c4d1fe6e85f1 (/dev/sdb1) (mounted on / as ext3) Apparantly mkinitrd tries to find the device belonging to the UUID and ends up using one of the two disks of the RAID, instead of the RAID device itself. My question - resulting from the question what the stat() in mkinitrd does - was whether this could do any harm, Lars suggested it does. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=340971 Hannes Reinecke changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |pieter.hollants@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=340971#c9 Pieter Hollants changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED Info Provider|pieter.hollants@novell.com | --- Comment #9 from Pieter Hollants 2007-11-17 04:34:31 MST --- Created an attachment (id=183785) --> (https://bugzilla.novell.com/attachment.cgi?id=183785) Output of bash -x /sbin/mkinitrd -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=340971#c11 Hannes Reinecke changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hare@novell.com AssignedTo|hare@novell.com |kasievers@novell.com Status|REOPENED |NEW --- Comment #11 from Hannes Reinecke 2007-11-21 04:33:21 MST --- No, this is actually udev doing things wrong. By rights the symlink should be pointing to /dev/md0, not sdb1. Kay, I think we need to do the overwrite magic here, too. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=340971#c13 Pieter Hollants changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|pieter.hollants@novell.com | --- Comment #13 from Pieter Hollants 2007-11-21 12:00:02 MST --- pief@hermes:~> rpm -q udev udev-103-12 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=340971#c15 --- Comment #15 from Pieter Hollants 2007-11-22 11:13:13 MST --- Not really. I can try to reproduce within VMware with 10.3, but only if this could trigger a udev update for 10.2, otherwise I'm stuck anyway ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.