Superblock not read at boot

Bug #120285 reported by Bananabob on 2007-06-13
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Undecided
Unassigned

Bug Description

At boot I sometimes get the following message

Log of fsck -C -R -A -a
Thu Jun 14 10:17:08 2007

fsck 1.40-WIP (14-Nov-2006)
fsck.ext3: No such file or directory while trying to open /dev/Volume0/lvol0
/dev/Volume0/lvol0:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

fsck died with exit status 8

Thu Jun 14 10:17:08 2007

If I then type shutdown -r now the system gives me a logon screen. I then ask for a reboot and the system will boot perfectly normally.

uname -a
Linux thorium 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux

John - Richmond (moshuptrail) wrote :

I am getting the same behavior on an HP Pavillion Desktop except mine is consistent. It will not boot at all. I get this error EVERY time.
The only solution has been to revert to the 2.6.17 kernel. Obviously there is nothing wrong with the superblock if I can boot with an older kernel.

John - Richmond (moshuptrail) wrote :

I will be happy to provide any details possible.
This problem is reproducible. On my HP Pavilion 750c Desktop it happens on every boot with the 2.6.20-16-386 kernel.
Simply dropping back to the 2.6.17 kernel allows the system to boot.
John

John - Richmond (moshuptrail) wrote :

Here is fstab. Some explanation:
hda - old hd with possible bad blocks - not used except to recover data now and then
hdb - new Maxtor hd. has copy of Windows XP in hdb1 & hdb2. Ubuntu boots from hdb6.
hdb6,7,8 are logical partitions within a container partition

John - Richmond (moshuptrail) wrote :

output of dmesg (tar.gz format)

John - Richmond (moshuptrail) wrote :

contents /var/log/udev

John - Richmond (moshuptrail) wrote :

Okay, this is NOT exactly a bug.
It may be caused by the use of /dev/hdxx device identifiers in fstab.
Evidently this latest kernel no longer recognizes those and the partitions are now identified as /dev/sdxx.
The problem in this case is caused by a bug in the upgrade path from Dapper to Edgy.
Edgy is supposed to convert the fstab to UUID identifiers, but if there are duplicate UUID's it does not.
In fact, if you have duplicate UUIDs you cannot successfully mount all drives using UUID identifiers.
I have not yet tried using /dev/sdxx identifiers in the fstab, but if I convert the fstab to use UUID and do not mount any of the duplicate UUID drives it will work with the 2.6.20 kernel.

If there is a bug it is this: There is no way (that I am aware of) to change the UUID of an NTFS or FAT32. So if UUID identifiers are required in fstab, there is no way to mount NTFS or FAT32 drives that have been cloned, and thus have duplicate UUID's.

Bananabob (bananabob) wrote :

Here is my FSTAB. My question is what does it mean and how do I change it to get it work with the new kernel? It seems to me that I am using dev/sdxx ids!

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1
UUID=69eb4fab-f38b-43f7-8796-39734a877b89 / ext3 defaults,errors=remount-ro 0 1
# /dev/sda2
UUID=b800200b-197f-40e2-b27e-684b783e1bea none swap sw 0 0
# /dev/sdb2
UUID=101458e2-7316-4b2e-9550-f4354323c9d7 none swap sw 0 0
/dev/Volume0/lvol0 /home ext3 defaults 0 2
/dev/cdrom /media/cdrom0 udf,iso9660 user,noauto 0 0

John - Richmond (moshuptrail) wrote :

Banana -
post the output of these two commands:
blkid
sudo fdisk -lu

Also, explain your hd structure. You have sda, sdb, and volume? What are those devices and what's on them.

I'm no genius, but maybe I can help (whilst we wait for a techie to look at this)

Bananabob (bananabob) wrote :

Here is the commands outout as requested.

bananabob@thorium:~$ blkid
/dev/sda1: LABEL="System" UUID="69eb4fab-f38b-43f7-8796-39734a877b89" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda2: TYPE="swap" UUID="b800200b-197f-40e2-b27e-684b783e1bea"
/dev/sdb1: LABEL="Development" UUID="e4ee9322-cbbf-4252-ad3e-ba14032571a4" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb2: TYPE="swap" UUID="101458e2-7316-4b2e-9550-f4354323c9d7"

bananabob@thorium:~$ sudo fdisk -lu

Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes

   Device Boot Start End Blocks Id System
/dev/sda1 63 19535039 9767488+ 83 Linux
/dev/sda2 19535040 27342629 3903795 82 Linux swap / Solaris
/dev/sda3 27342630 625137344 298897357+ fd Linux raid autodetect

Disk /dev/sdb: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes

   Device Boot Start End Blocks Id System
/dev/sdb1 63 19535039 9767488+ 83 Linux
/dev/sdb2 19535040 27342629 3903795 82 Linux swap / Solaris
/dev/sdb3 27342630 625137344 298897357+ fd Linux raid autodetect

Disk /dev/md0: 306.0 GB, 306070814720 bytes
2 heads, 4 sectors/track, 74724320 cylinders, total 597794560 sectors
Units = sectors of 1 * 512 = 512 bytes

Disk /dev/md0 doesn't contain a valid partition table
bananabob@thorium:~$

My set up is supposed to be this. I have a RAID setup. One disk that is where all my data and system files are held. The second disk is the alternate in the RAID. The front of it contains Development partition this is empty. The rest is the mirror of my data.

I have no idea what the volume is for but I have been getting the following message
 dm_task_set_name: Device /dev/mapper/Volume0-lvol0 not found
So I assume that my fstab is incorrect in some way. Although it is exactly the same as my Edgy one apart from the CDROM mount line.

John - Richmond (moshuptrail) wrote :

I agree, there is something odd about your fstab. For starters, it lists two swap partitions. If there is some advantage to that I am not aware of it. It may even be bad. Second, couldn't your root partition (/dev/sda1) be paired with the unused partition (/dev/sdb1) in a Raid volume to get improved performance? Or is that not possible with Linux? Lastly, it would appear that /dev/Volume0/lvol0 in fstab is referring to the Raid volume at /dev/sda3 & /dev/sdb3. Exactly how does Raid do that? I would need to read up on Raid. There must be a Raid set-up file somewhere...

In short, while there are questions about the use & configuration of Raid, the only oddity in your fstab is the presence of two swap partitions. I would not fool with the entry for /home in fstab until you understand how Raid configures itself.

John - Richmond (moshuptrail) wrote :

Final suggestion: Start a thread in Installation & Upgrades and ask about proper RAID configuration for Feisty.
I assume you are using "software-only RAID 1 using mdadm", correct? I did a little poking around and it's not a simple thing, but you'll get more answers there.

Bananabob (bananabob) wrote :

Hello, I'm Bananabob's Son.

Here are a few more pieces of information.

The raid is set up using partions 3 of both drives.
Swap is on partions 2 of both drives to load balance.
Root is on partion 1 of the first drive. Partition 1 of the second drive is for a developmental root if the need arises.

On the raid (md0) there is a LVM Physical Volume (Volume0), in that is a logical volume (lvol0).

On the logical volume is the /home partition.

I have changed the fstab for the /home partition to use UUID and will get Dad to update you if the problem continues.

bananabob@thorium:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1
UUID=69eb4fab-f38b-43f7-8796-39734a877b89 / ext3 defaults,errors=remount-ro 0 1
# /dev/sda2
UUID=b800200b-197f-40e2-b27e-684b783e1bea none swap sw 0 0
# /dev/sdb2
UUID=101458e2-7316-4b2e-9550-f4354323c9d7 none swap sw 0 0
#/dev/Volume0/lvol0
UUID=e1298250-91d0-4524-8fea-abeffc04d4ec /home ext3 defaults 0 2
/dev/cdrom /media/cdrom0 udf,iso9660 user,noauto 0 0

bananabob@thorium:~$ blkid
/dev/sda1: LABEL="System" UUID="69eb4fab-f38b-43f7-8796-39734a877b89" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda2: UUID="b800200b-197f-40e2-b27e-684b783e1bea" TYPE="swap"
/dev/sdb1: LABEL="Development" UUID="e4ee9322-cbbf-4252-ad3e-ba14032571a4" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb2: UUID="101458e2-7316-4b2e-9550-f4354323c9d7" TYPE="swap"
/dev/mapper/Volume0-lvol0: LABEL="Home" UUID="e1298250-91d0-4524-8fea-abeffc04d4ec" SEC_TYPE="ext2" TYPE="ext3"

Bananabob (bananabob) wrote :

A new problem in this saga

Two days in a row I have had the following messages on bootup.

BusyBox V1.1.3 (Debian 1:1.1.3-3ubuntu3) Built-in Shell (ash)
Enter 'help' for a list of built-in commands.
/bin/sh: can't access tty; job control turned off
(initramfs)

Of course on reboot - I have to use the reset button on the box, everything works.

It would appear that the problem with booting is more to do with this kernel than anything else. (but what do I know about kernels?) :-)

Marco Rodrigues (gothicx) wrote :

Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

Changed in linux-source-2.6.20:
status: New → Incomplete
assignee: nobody → ubuntu-kernel-team
Bananabob (bananabob) wrote :

A few days ago my son ran the following command:

sudo update-initramfs -u

Since then I have had no boot-up problems. This does not mean that the problem is fixed, because I can go for days without having any problems, and then get several in a row. So I would like to wait a while before I claim the problem is fixed.

So in light of your request here is the information.
bananabob@thorium:~$ uname -a
Linux thorium 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux

Bananabob (bananabob) wrote :

And the next attachment here

Bananabob (bananabob) wrote :

Well the problem has not been fixed. Here is the current indication:
Log of fsck -C -R -A -a
Fri Jul 6 08:50:24 2007

fsck 1.40-WIP (14-Nov-2006)
fsck.ext3: Unable to resolve 'UUID=e1298250-91d0-4524-8fea-abeffc04d4ec'
fsck died with exit status 8

Fri Jul 6 08:50:24 2007
----------------

As you can see from below this is rubbish:

bananabob@thorium:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1
UUID=69eb4fab-f38b-43f7-8796-39734a877b89 / ext3 defaults,errors=remount-ro 0 1
# /dev/sda2
UUID=b800200b-197f-40e2-b27e-684b783e1bea none swap sw 0 0
# /dev/sdb2
UUID=101458e2-7316-4b2e-9550-f4354323c9d7 none swap sw 0 0
#/dev/Volume0/lvol0
UUID=e1298250-91d0-4524-8fea-abeffc04d4ec /home ext3 defaults 0 2
/dev/cdrom /media/cdrom0 udf,iso9660 user,noauto 0 0

Plus, of course I could reboot into the system perfectly after this "error"

Bananabob (bananabob) wrote :

Well here we go again! This morning when I powered up my PC i had the following problems
1 - USB (I-pod) device would not automount.
so I rebooted with a shutdown -r now
2. had 3 trys at this because of all the problems noted in previous entries
3. Then I had no menus from the gnome toolbar and the shutdown command was not found
So I hit the reset switch
4. Back to USB (I-pod) device would not automount.
So once again I issued a shutdown -r now

Ahhh. it works now.

Is anyone looking into this problem?

Bananabob (bananabob) wrote :

Today it was my USB (I-pod) device would not automount.

Here is information that has been provided before

uname -a
Linux thorium 2.6.20-16-generic #2 SMP Sun Sep 23 19:50:39 UTC 2007 i686 GNU/Linux

Bananabob (bananabob) wrote :

lspci -vvnn > lspci-vvnn.log

Bananabob (bananabob) wrote :

changed to new because new information added

Changed in linux-source-2.6.20:
status: Incomplete → New

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Bananabob (bananabob) wrote :

I am sorry but right now I am unable to help you debug this due to other commitments, and I am changing over to 64-Bit Hardy.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Andres Mujica (andres.mujica) wrote :

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04 - http://www.ubuntu.com/getubuntu/download. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers