Mismatching UUIDs after Hardy server install

Bug #234920 reported by Alexander Dietrich on 2008-05-26
Affects Status Importance Assigned to Milestone
debian-installer (Ubuntu)

Bug Description

When booting a fresh Hardy server install, the filesystem checking step failed
with an error message like "device with UUID xyz could not be found".

This is my setup:
/dev/md0 = /dev/sda1 + /dev/sdb1, ext2 at "/boot"
/dev/md1 = /dev/sda2 + /dev/sdb2, xfs at "/"
/dev/md2 = /dev/sda3 + /dev/sdb3, xfs at "/srv"
/dev/md3 = /dev/sda4 + /dev/sdb4, swap

When I investigated, I found that /etc/fstab and /dev/disk/by-uuid specified one
UUID for /dev/md0, but blkid reported a completely different one! If this had been
/dev/md1, the system would probably have failed to boot.
I used tune2fs to set the UUID on /dev/md0, and the filesystem check at boot

Unfortunately I have no idea how this happened, but maybe the installer should
run a UUID check before rebooting the system.

tricky1 (tricky1) wrote :

All distros of Hardy (including server) have ugly bugs preventing use of raid 1 mirroring. The whole concept needs thorough rework. See Bug 252485 and others.

tricky1 (tricky1) wrote :

it is well known for 2 years :-(

Changed in debian-installer:
status: New → Confirmed
Gregg (gclaeys) wrote :

I have the same issue on ubuntu 9.04.

uname :
2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux

I recently changed my swap partition to make it bigger, using gparted.
This operation changed the UUID, but gparted still to indicate me the old UUID for the partition.

The UUDI gaven to me by *blkin* and *gparted* where the same and that is was not present in /dev/disk/by-uuid.

So I have found *vol_id -u /dev/sdaX*, wich gave me the right UUID.

I modify the *fstab* and now my swap partition is automatically used (at least gparted tell me it is).

This would be perfect I could use the hibernate function that was working fine before.

Now, when I hibernate it gave me no error, but when I start my computer it gave me some filesystem error and do not load the boot image of the hibernation.
I do not know if this is because it is still looking for the old swap partition at startup or something else.

I hope this help, if u need more information email me.

Kiri (kiri) wrote :

When installing with root partition on /dev/sda1 and another partition on an LVM storage device I get the messages
GRUB loading.
error: no such device: <UUID>
before the boot menu. Booting then proceeds normally. Is this the same bug?

Phillip Susi (psusi) wrote :

Work can not be done on this without being able to reproduce it. Are you able to reproduce it?

Changed in debian-installer (Ubuntu):
status: Confirmed → Incomplete
Alexander Dietrich (adietrich) wrote :

Sorry, I'm not planning to re-install my server (or something comparable) in the near future. Hopefully some of the other commenters can contribute information.

I have since moved to a non-mirrored config for /boot.

Launchpad Janitor (janitor) wrote :

[Expired for debian-installer (Ubuntu) because there has been no activity for 60 days.]

Changed in debian-installer (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers