ureadhead prevent the system from booting after fsck during 180 seconds

Bug #572938 reported by Id2ndR
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ureadahead (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: ureadahead

Steps to reproduce :
- Send sys keys : ALT+SYS+B during a boot
- fsck will be perfom during the reboot during few seconds
=> show that the percent change very slowly and there is no disk activity. In my case, it go from 0% to 70% normaly, and then from 70 to 90-91% very very slowly with no disk activity. Then it changed the number of drive to scan from 1 to 3. And finally the boot process resume.

Look at attached bootchart.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: ureadahead 0.100.0-4.1
ProcVersionSignature: Ubuntu 2.6.34-1.4~oga1-generic 2.6.34-rc5
Uname: Linux 2.6.34-1-generic x86_64
Architecture: amd64
Date: Sat May 1 12:34:43 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100224.1)
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.utf8
 SHELL=/bin/bash
SourcePackage: ureadahead

Revision history for this message
Id2ndR (id2ndr) wrote :
Revision history for this message
Id2ndR (id2ndr) wrote :
Revision history for this message
Id2ndR (id2ndr) wrote :

In fact this is not 180 seconds but 225 seconds (timout of 180 added to the sleep of 45 seconds). You can show it in the bootchart by this operation : 252 (begining of ureadhead) = 27 (end of fsck) + 180 + 45.

Revision history for this message
Jan Nemecek (mcgiany) wrote :

Hi, same problem here. There is also problem with canceling the check disk. When i press the "C" key, checking doesn't stop and still continue.

Revision history for this message
Id2ndR (id2ndr) wrote :

I get the trouble again on an other computer. This time it wasn't 180+45 seconds but more, so I check in logs files why.
In fact there was a trouble on checking two partitions so I think I can explain the delay with combination of sums of 180 and 45.

I also found (in this computer), that the trouble itself is not due to ureadead directly but a missing command (fsck.ntfs) on my system and ureadhead doesn't manage that.

See attached /var/log/boot.log and corresponding bootchart.

Revision history for this message
Id2ndR (id2ndr) wrote :
Revision history for this message
Id2ndR (id2ndr) wrote :

In my previous case, the bug with fsck.ntfs is https://bugs.launchpad.net/bugs/441242 and I fix the trouble by disabling the check as explain in https://bugs.launchpad.net/ubuntu/+source/partman-basicfilesystems/+bug/441242/comments/6

I'll report again when I'll get the trouble on the computer from which I create the bug report.

@all:
Please attach your /var/log/boot.log when the trouble occurs.

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

This massive delay actually sounds more like Bug 571707 ...

Revision history for this message
Id2ndR (id2ndr) wrote :

I'm marking this as a duplicate of bug 571707 that seems to be the same one. If it's not, I am unmarking it later.

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.