Dapper: persistent boot failure - ext3 filesystem not detected

Bug #37528 reported by Ulf Karlsson
10
Affects Status Importance Assigned to Milestone
klibc (Ubuntu)
Fix Released
Medium
Unassigned
Dapper
Invalid
Medium
Unassigned

Bug Description

In the fstype tool there is a problem if the lower 16 bit of number of free inodes in a ext3 filesystem happens to match minix filesystem magic.

This will cause the system not to boot since ubuntu will attempt to mount the filesystem as a minix filesystem.

This problem has been discussed before, but the cause was never investigated, e.g.:

http://www.ubuntuforums.org/archive/index.php/t-95729.html

Stupid workaround:

mount /dev/sda1 /root
touch /root/newfile
sync

Revision history for this message
Riku Voipio (riku-voipio) wrote :

Apparently is fixed by:

http://www.kernel.org/git/gitweb.cgi?p=libs/klibc/klibc.git;a=commit;h=2f7cdff4361e65c6405a0a0e17363e9684567fa0

Which through some unfortunate circumstance does not appear to be in dapper version of klibc..

Revision history for this message
dovik (dovik-martin) wrote : no "ext3" or "minix" message related but ...

i'm using Dapper LTS.

yesterday my girlfriend (with "Desktop" right only) have shutdown our computer and relaunch it later in the afternoon and ... the problem began :

ubuntu start to initialize, then prompt/BusyBox :

Mounting /dev/sda1 on /root failed: No such device
Mounting /root/dev on /dev/.static/dev failed: No such file or directory
Mounting /sys on /root/sys failed : No such file or directory
Mounting /proc on /root/proc failed : No such file or directory
Target filesystem does not have /sbin/init

BusyBox (...) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty: job control turned off

after one hour of reading forum using Dapper LiveCD, i found this :
http://forum.ubuntu-fr.org/viewtopic.php?pid=303897#p303897
and this :
http://ubuntuforums.org/archive/index.php/t-95729.html

and try similar solution :
sudo mkdir /mnt/ubuntu
sudo mount /dev/sda1 /mnt/ubuntu
sudo vim /mnt/ubuntu/bug_minix
type some word (the adresse of the post where i found the solution ^^)
<escap>:wq!

and reboot ... et voilà. the problem was resolve.

how can i give you more details to investigate and really resolve this bug ?

(sorry for my poor english)

Revision history for this message
Ulf Karlsson (ohmega) wrote : Re: [Bug 37528] no "ext3" or "minix" message related but ...

Has the fix for this still not been integrated into Dapper? Incredible.

This bug is rather critical IMHO.

/Ulf

2007/4/14, dovik <email address hidden>:
> i'm using Dapper LTS.
>
> yesterday my girlfriend (with "Desktop" right only) have shutdown our
> computer and relaunch it later in the afternoon and ... the problem
> began :
>
> ubuntu start to initialize, then prompt/BusyBox :
>
> Mounting /dev/sda1 on /root failed: No such device
> Mounting /root/dev on /dev/.static/dev failed: No such file or directory
> Mounting /sys on /root/sys failed : No such file or directory
> Mounting /proc on /root/proc failed : No such file or directory
> Target filesystem does not have /sbin/init
>
> BusyBox (...) Built-in shell (ash)
> Enter 'help' for a list of built-in commands.
>
> /bin/sh: can't access tty: job control turned off
>
> after one hour of reading forum using Dapper LiveCD, i found this :
> http://forum.ubuntu-fr.org/viewtopic.php?pid=303897#p303897
> and this :
> http://ubuntuforums.org/archive/index.php/t-95729.html
>
> and try similar solution :
> sudo mkdir /mnt/ubuntu
> sudo mount /dev/sda1 /mnt/ubuntu
> sudo vim /mnt/ubuntu/bug_minix
> type some word (the adresse of the post where i found the solution ^^)
> <escap>:wq!
>
> and reboot ... et voilà. the problem was resolve.
>
> how can i give you more details to investigate and really resolve this
> bug ?
>
> (sorry for my poor english)
>
> --
> ext3 reported as minix
> https://bugs.launchpad.net/bugs/37528
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Ulf Karlsson (ohmega)
Changed in klibc:
status: Unconfirmed → Confirmed
Revision history for this message
Colin Watson (cjwatson) wrote :

This was fixed in klibc 1.3.1 (i.e. Edgy and onward). Opening a new Dapper task for this, in the event that anyone wants to backport it.

Changed in klibc (Ubuntu Dapper):
status: New → Confirmed
importance: Undecided → Medium
Changed in klibc (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
JC Hulce (soaringsky) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The version of Ubuntu you're reporting this issue on is in End of Life status, and newer versions have fixed this issue. You can learn more about this at https://wiki.ubuntu.com/Releases

Changed in klibc (Ubuntu Dapper):
status: Confirmed → 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.