[Bug 234920] Re: Mismatching UUIDs after Hardy server install

[Alexander Dietrich]

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.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debian-installer in Ubuntu.
https://bugs.launchpad.net/bugs/234920

Title:
  Mismatching UUIDs after Hardy server install

Status in “debian-installer” package in Ubuntu:
  Incomplete

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
  succeeded.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/234920/+subscriptions