Ubuntu
e2fsprogs package

  1. Bug #110138
  2. Comment #0

Comment 0 for bug 110138

Revision history for this message
Daniel Hahler (blueyed) wrote : blkid reports incorrect info / update-grub fails to resolve UUID

I have a boot partition /dev/sda1:
# fdisk -l /dev/sda | grep sda1
/dev/sda1 * 1 7 56196 83 Linux

This is displayed in fstab as:
# /dev/hda1 -- converted during upgrade to edgy
UUID=70b7d252-5a65-45cd-a949-30569a2cce39 /boot ext3 defaults 0 2

# blkid /dev/sda1
/dev/sda1: TYPE="ntfs"

# vol_id /dev/sda1
ID_FS_USAGE=filesystem
ID_FS_TYPE=ext3
ID_FS_VERSION=1.0
ID_FS_UUID=70b7d252-5a65-45cd-a949-30569a2cce39
ID_FS_LABEL=
ID_FS_LABEL_SAFE=

The problem I have with this, is that update-grub fails somehow:
# LANG=C update-grub
Searching for GRUB installation directory ... found: /boot/grub
findfs: Unable to resolve 'UUID=70b7d252-5a65-45cd-a949-30569a2cce39'
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-2.6.20-15-server
Updating /boot/grub/menu.lst ... done

Because update-grub fails to resolve the UUID, it puts "/boot/..." into the menu.lst and then grub itself fails with "File not found" (because it should be rather /... than /boot/...).

I'm not sure where the bug here really is.. maybe there's some confusion about "hda1" and "sda1"?!