------- Comment From [email protected] 2015-02-26 16:51 EDT------- Hi Brian,
As you observed, grub.cfg has "root=UUID=e3142d5d-f8f1-4278-a08a- 6bda31d2dc79" as it's default entry, and has alternate entries for /dev/sda, sde, sdq and sdu also. None of these drives is in a multipath group. Is the expectation here that these should belong to a multipath group, and the system should be booted from the multipath device? Should this UUID be pointing to a multipath device instead of a single path? Could this have been an install problem? Given that the UUID points to a single path device, it does look correct as it's booted currently: root@zop01:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-3.18.0-13-generic root=UUID=e3142d5d-f8f1-4278-a08a-6bda31d2dc79 ro splash quiet root@zop01:~# ll /dev/disk/by-uuid/*c79 lrwxrwxrwx 1 root root 10 Feb 18 07:11 /dev/disk/by-uuid/e3142d5d-f8f1-4278-a08a-6bda31d2dc79 -> ../../sdu2 root@zop01:~# mount /dev/sdq2 on / type ext4 (rw,errors=remount-ro) Second, on the /etc/fstab: root@zop01:~# cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> /dev/mapper/mpath0p2 / ext4 errors=remount-ro 0 1 /dev/mapper/mpath0p3 none swap sw 0 0 ... Again we see this naming inconsistency, Currently, this system has only the /dev/mapper/mpathX-partX names, none of the /dev/mapper/mpathXpX names. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1425773 Title: multipath command not showing boot disk information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1425773/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
