since Upgrade to karmic: mount problems, long boot time duration

Bug #466693 reported by Wind
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
mountall (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: mountall

Since the upgrade from jaunty to karmic i have problems on two computers when booting.

First computer:
Booting time before upgrade according to bootchart with jaunty: 0:30.
Booting time after upgrade to karmic: 1:35. (After approx. 15 system starts)

System boots - except for long boot time - after all korrect.
After system start the console with Ctrl-Alt-F1 shows:

..
fsck from util-linux-ng 2.16
One or more mounts listed in /etc/fstab cannot be mounted:
(ESC for recovery shell)
/: waiting for /dev/disk/by-uuid/........-....-....-....-............
/tmp: waiting for (null)
/data: waiting for /dev/disk/by-uuid/........-....-....-....-............
/home: waiting for /dev/disk/by-uuid/........-....-....-....-............
/dev/sda5: clean, .../... files, .../... blocks
..
fsck from util-linux-ng 2.16
One or more mounts listed in /etc/fstab cannot be mounted:
(ESC for recovery shell)
/data: waiting for /dev/disk/by-uuid/........-....-....-....-............
/home: waiting for /dev/disk/by-uuid/........-....-....-....-............
/dev/sda7: clean, .../... files, .../... blocks
..
fsck from util-linux-ng 2.16
..
/dev/sda8: clean, .../... files, .../... blocks
..

The device names and mount points are::
sda5 /
sda6 swap
sda7 /home
sda8 /data

At another computer the same problem follows after update to karmic.
Booting time before upgrade according to bootchart with jaunty: 0:34.
Booting time after upgrade to karmic: 3:08. (First start after upgrade)
Booting time after upgrade to karmic: 2:00. (five next starts)

Here i got analog messages as above:

One or more mounts listed in /etc/fstab cannot be mounted:
(ESC for recovery shell)
/: waiting for ...
...

I started the computer with a parallel installed debian and checked the two ubuntu partitions:
 UbuntuRoot sda5
 UbuntuHome sda6
with
 e2fsck -f -y -v /dev/sda5
 e2fsck -f -y -v /dev/sda6

Now boot time is 1:35 (for multiple system starts)

After the first system start after debians e2fsck the console with Ctrl-Alt-F1 shows:

fsck from util-linux-ng 2.16
UbuntuRoot: clean, .../... files, .../... blocks
fsck from util-linux-ng 2.16
UbuntuHome: clean, .../... files, .../... blocks

After the next further system start console with Ctrl-Alt-F1 shows:

fsck from util-linux-ng 2.16
UbuntuRoot: clean, .../... files, .../... blocks
fsck from util-linux-ng 2.16
One or more mounts listed in /etc/fstab cannot be mounted:
(ESC for recovery shell)
/home: waiting for /dev/disk/by-uuid/........-....-....-....-............
UbuntuHome: clean, .../... files, .../... blocks

There are always fsck calls at any system start.
The boot time takes one Minute longer than with jaunty.

What is the reason for this mount problems?

Versions of some installed packages:
mountall 1.0
grub 0.97-29ubuntu59
grub-common 1.97beta4-1ubuntu3

lsb_release -rd
Description: Ubuntu 9.10
Release: 9.10

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Nothing about the above is unusual, except the long boot time.

However you didn't attach any before or after bootcharts, so it's impossible to tell what causes that

Changed in mountall (Ubuntu):
status: New → Invalid
Revision history for this message
Caleb K (ckemere) wrote :

I have the same issue (though my startup warnings refer to blkid's). I'm attaching a bootchart that shows the effect. I found that if I disabled fsck in the /etc/fstab file, boot was much quicker. But that seems unsafe...

Revision history for this message
Johan Walles (walles) wrote :

A boot chart has been provided, please re-evaluate.

Changed in mountall (Ubuntu):
status: Invalid → New
Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

The bootchart was not provided by the original reporter, so it's impossible to tell whether this was their problem.

Caleb: it looks like you're just having a disk check in that chart.

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

Other bug subscribers

Remote bug watches

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