Ubuntu
usplash package

Fails to mount /home on sd-card during boot

Bug #481836 reported by Bart de Koning
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
usplash (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: usplash

After updating to karmic each time I boot my Acer Aspire One cannot mount /home during boot (with Jaunty I did not have this problem).
/home is located on a SD-card:

in fstab:
#UUID=9648ab61-a70a-4dc1-9a50-851404098820
/dev/mmcblk0p1 /home ext4 relatime 0 2

(it does not matter whether I use /dev or the UUID)

It gives a warning instead that it is unable to find the device and asks to press esc to drop to a shell.
mount -a in that shell gives a similar warning that it cannot find the device pressing ctrl-D after issuing this command, resumes boot process and ... magically it also mounts the SD-card without a problem.

It looks like that in the new boot procedure the call to mount all devices is given before SD-cards are initialized, or it could also be that the call is too early with respect to the time a SD-card needs to be able to respond after booting. It looks also a bit like bug 290153.

Hope this can be fixed soon, or that someone knows a workaround!

ProblemType: Bug
Architecture: i386
Date: Fri Nov 13 11:02:03 2009
DistroRelease: Ubuntu 9.10
MachineType: Acer AOA110
Package: usplash 0.5.49
ProcCmdLine: root=UUID=e043ebce-824a-446e-b1ad-dc19af0b92e4 ro quiet splash
ProcEnviron:
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: usplash
Tags: ubuntu-unr
Uname: Linux 2.6.31-14-generic i686
UsplashConf:
 # Usplash configuration file
 # These parameters will only apply after running update-initramfs.

 xres=1024
 yres=600
dmi.bios.date: 05/09/2008
dmi.bios.vendor: INSYDE
dmi.bios.version: v0.3109
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: Intel Corp.
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvrv0.3109:bd05/09/2008:svnAcer:pnAOA110:pvr1:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: AOA110
dmi.product.version: 1
dmi.sys.vendor: Acer

Revision history for this message
Bart de Koning (bratdaking) wrote :
Revision history for this message
WeatherGod (ben-v-root) wrote :

Bart, thank you for taking the time to help make Ubuntu better. I am marking this bug as a duplicate of another because this is a known issue. Please see the following link for more info.

http://www.ubuntu.com/getubuntu/releasenotes/910#Login%20screen%20presented%20before%20optional%20filesystems%20are%20mounted

To get rid of the error message, add the "bootwait" option to your /home entry in your fstab file.

Revision history for this message
Steve Langasek (vorlon) wrote :

"/home" is not considered an optional filesystem. You should not mark this filesystem as "bootwait" in /etc/fstab, and doing so is reported to cause other problems. I don't think this bug is related to bug #439604.

Revision history for this message
Bart de Koning (bratdaking) wrote :

Thanks for reading and responding on this bug-report so fast.
It looks quite similar, but it is not. This is not happening when it runs a fsck or something, it always happens. The problem is also not that it boots too quick, it just does not boot at all, but has to enter a root shell, needs manually issuing 'mount -a' (I tried a few other things but that did not work at all, it needs to be a mount command), and push ctrl-D to resume. I guess it issues the mountall command too quick, before the SD-card is yet initialized...
I will try to see if I can find some more related error messages...

Revision history for this message
Bart de Koning (bratdaking) wrote :

To be complete: adding bootwait to the mount options in /etc/fstab does not fix it

(btw. if you add bootwait issuing mount -a in a terminal when it is not mounted yet results in an error!)

Revision history for this message
WeatherGod (ben-v-root) wrote :

Bart, I am looking over your dmesg file, and I see that after 10 seconds, there is about a 30-second gap where I presume you are issuing your mount -a command? After that, it looks like the boot process finishes fairly quickly.

If that is the case, then what is interesting is the udev does not start until after you issue your mount -a command. I don't know if that is significant, but I am putting it out there.

Revision history for this message
Bart de Koning (bratdaking) wrote : Re: [Bug 481836] Re: Fails to mount /home on sd-card during boot

Could that mean that I need additional time during my boot process. Is there
a way I can test that?

2009/11/16 WeatherGod <email address hidden>

> Bart, I am looking over your dmesg file, and I see that after 10
> seconds, there is about a 30-second gap where I presume you are issuing
> your mount -a command? After that, it looks like the boot process
> finishes fairly quickly.
>
> If that is the case, then what is interesting is the udev does not start
> until after you issue your mount -a command. I don't know if that is
> significant, but I am putting it out there.
>
> --
> Fails to mount /home on sd-card during boot
> https://bugs.launchpad.net/bugs/481836
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Phillip Susi (psusi) wrote :

The usplash package has been superseded by plymouth and has been removed from the Ubuntu archive. Closing all related bugs.

Changed in usplash (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.