| View previous topic :: View next topic |
| Author |
Message |
mathfeel
l33t
Joined: 03 Aug 2004
Posts: 700
|
 Posted: Sat Feb 12, 2005 9:44 am Post subject: initrid fail to unmount after boot |
 |
|
I am using the initrid generated by genkernel
with :
genkernel initrd
it fails to unmount after boot because under its mounting point, two more mounting points exist and must be unmounted first...
Is this normal? |
|
| Back to top |
|
 |
xbmodder
Guru
Joined: 25 Feb 2004
Posts: 404
|
|
| Back to top |
|
|
mathfeel
l33t
Joined: 03 Aug 2004
Posts: 700
|
| Posted: Sat Feb 12, 2005 11:42 am Post subject: |
|
|
If there is a command that gives the information shown at the bootsreen, I can show you the exact error is:
Failed to unmount initrd
and, actually also something like
/linuxrc : [###] : Not Found
where ### is some #... |
|
| Back to top |
|
|
dfarr
n00b
Joined: 12 Feb 2005
Posts: 1
|
| Posted: Sat Feb 12, 2005 7:23 pm Post subject: |
|
|
| linuxrc fails at line 472 complaining that it cannot find [ and initrd (/tmp/.initrd) is not unmounted. I noticed this problem after upgrading to coreutils-5.2.1-r4 and my prism54 based wlan card stopped working because hotplug could not load its firmware. This problem is caused when linuxrc does a pivot_root and [ is no longer in the path. However, this happens only if you have a separate /usr partition which at this stage is not yet mounted. The quick fix is to copy /usr/bin/[ to /bin/[ and linuxrc should work again. |
|
| Back to top |
|
|
PipesDownUK
n00b
Joined: 22 Jun 2004
Posts: 37
|
| Posted: Sun Feb 13, 2005 11:02 am Post subject: Fix confirmed, fixed kicker crash too, whatabout long term f |
|
|
I'd like to confirm the fix posted above by dfarr  as I too had the same problem. After an emerge I began getting the following.
| Code: | Booting ./linuxrc: 441 [: not found
/linuxrc: 441: [: not found
umount: /tmp/.initrd device is busy
*: Failed to umount the initrd |
I too have /usr on it own partition. Doing the short term fix posted above by dfarr, prevented these messages appearing on the next reboot.  In my case I also found that kicker was crashing when starting KDE leaving me without menus. This fix also solved that problem.
 Having implemented a short term fix, will there be a long term fix? I'm not knowledgeable enough to understand the problem, what the short term fix does, or any long term effects of the short term fix, but I'm not comfortable with leaving a workaround in place long term.  |
|
| Back to top |
|
|
|
Kernel & Hardware
