From Bugzilla Helper: User-Agent: Mozilla/5.0 Galeon/1.2.0 (X11; Linux i686; U;) Gecko/20020314 Description of problem: I already added this as a comment to bug #55540 but there seems to have been no response, so I'll try and file as a bug in it's own right... It would seem that an initrd image generated with mkinitrd up to and including 3.3.6-1 doesn't work quite correctly if using a devfs enabled kernel. More specifically, the kernel boots OK but there is a non-fatal problem early on in the init sequence when trying to unmount the initrd filesystem. This is due to the filesystem being busy as a consequence of /dev being mounted underneath. The attached patch is something I plagiarised from Mandrake's additions to the original RH mkinitrd. Fundamentally, all it does is to close I/O on devfs to allow it to be remounted under real root instead of initrd root, and thus allow /initrd to be successfully unmounted. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Build devfs enabled kernel 2.Boot with mkinitrd generated initrd 3. Actual Results: System unable to unmount /initrd Additional info:
Created attachment 52264 [details] diffs against mkinitrd-3.3.6-1 to enable better handling of devfs enabled kernel
*** This bug has been marked as a duplicate of 51848 ***