Created attachment 944349 [details]
generated grub.cfg

Description of problem:
I have Fedora 21 which worked quite well for couple of days including couple of reboots. This morning I have got in gnome-shell a notification that Updates are available and I should [Restart & Update]. So, I did (ignoring my numerous terrible experience with PackageKit update) and the result was that I was greeted on reboot by grub prompt.

Apparently there was something way more fundamentally broken, because plain grub2-install /dev/sda && grub2-mkconfig didn't help.

The problems I have managed to identify so far (by the way, I still don't have working grub2 configuration, so I have to boot manually from grub prompt):

1) grub2-mkconfig doesn't follow -o option:

wycliff:~# rm -f /tmp/grub.cfg*
wycliff:~# grub2-mkconfig -o /tmp/grub.cfg
Generating grub configuration file ...
wycliff:~# ls /tmp/grub.cfg
ls: cannot access /tmp/grub.cfg: No such file or directory
wycliff:~# ls /tmp/grub.cfg.new
/tmp/grub.cfg.new
wycliff:~#

2) And even that /tmp/grub.cfg.new is weird (see attached), it doesn't have one menu item for my kernel, and points to nonsensical LVM volumes. I have this LVM

wycliff:~# lvs
  LV           VG         Attr       LSize
  lv_fedora    vg_wycliff -wi-a-----   9.00g
  lv_home      vg_wycliff -wi-ao---- 246.50g
  lv_root      vg_wycliff -wi-ao----  39.53g
  lv_store01   vg_wycliff -wi-a-----   7.00g
  lv_swap      vg_wycliff -wi-ao----   5.88g
  lv_virtOther vg_wycliff -wi-a-----   9.88g
wycliff:~#

and this partitions:

wycliff:~# fdisk -l /dev/sda

Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000dc905

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1  *         2048   1026047   1024000   500M 83 Linux
/dev/sda2         1026048 410626047 409600000 195.3G 8e Linux LVM
/dev/sda3       410626048 822741492 412115445 196.5G 83 Linux
/dev/sda4       822741493 976773167 154031675  73.5G 83 Linux

wycliff:~#

And this is the output of blkid:

wycliff:~# blkid
/dev/sda1: LABEL="BOOT" UUID="abdc285d-a329-4804-bb51-b6b88084d9b3" TYPE="ext4" PARTUUID="000dc905-01"
/dev/sda2: UUID="SzzvWh-x332-5kUh-BkfF-2J18-H57I-Y6Bflc" TYPE="LVM2_member" PARTUUID="000dc905-02"
/dev/sda3: UUID="dWCO6M-RFJq-QvV5-l7Uz-4sWY-m5OP-jQVFbj" TYPE="LVM2_member" PARTUUID="000dc905-03"
/dev/sda4: LABEL="BACIK" UUID="6a79ea59-8501-493a-a383-eb5033bedd60" UUID_SUB="3dc081da-0289-48b3-ba4c-a968ec273577" TYPE="btrfs" PARTUUID="000dc905-04"
/dev/mapper/vg_wycliff-lv_root: LABEL="KOREN" UUID="4b54050d-bd6c-4f62-b289-5f5199b3d3f2" TYPE="ext4"
/dev/mapper/vg_wycliff-lv_swap: UUID="3096a1fd-faf1-4e15-b8f4-05fdb54997a7" TYPE="crypto_LUKS"
/dev/mapper/swap: UUID="0ddff937-06c2-478b-bd9e-5e2cd5a77612" TYPE="swap"
/dev/mapper/vg_wycliff-lv_home: UUID="b3f0d4df-e5ba-470f-ae81-60c001d117cf" TYPE="crypto_LUKS"
/dev/mapper/vg_wycliff-lv_virtOther: PTUUID="000e428b" PTTYPE="dos"
/dev/mapper/vg_wycliff-lv_fedora: PTUUID="dfd3a9a4" PTTYPE="dos"
/dev/mapper/vg_wycliff-lv_store01: PTUUID="37e8822d-b1cf-4a83-bff7-31f9ca1d1ef7" PTTYPE="gpt"
/dev/mapper/home: UUID="a4160d88-e54e-47c2-8659-cb756ee87051" TYPE="ext4"
/dev/sdc: LABEL="Internal SD" UUID="DB8C-563E" TYPE="vfat"
wycliff:~#

I am not completely sure what should I thus think about this line in the generated grub2.cfg:

set root='lvmid/VdXBCR-fOqO-CL2A-jL7C-c56z-IRyG-41y4ry/yIjEzX-XlJb-9nam-TJEn-gnNe-JdzM-WQ5ADW'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint='lvmid/VdXBCR-fOqO-CL2A-jL7C-c56z-IRyG-41y4ry/yIjEzX-XlJb-9nam-TJEn-gnNe-JdzM-WQ5ADW'  4b54050d-bd6c-4f62-b289-5f5199b3d3f2
else
  search --no-floppy --fs-uuid --set=root 4b54050d-bd6c-4f62-b289-5f5199b3d3f2
fi

Couldn’t grub2-mkconfig just prefer labels when they are there? root=LABEL=KOREN seems to me like the best option in my case.


Version-Release number of selected component (if applicable):
grubby-8.35-4.fc21.x86_64
kernel-3.16.3-302.fc21.x86_64
grub2-tools-2.02-0.8.fc21.x86_64
grub2-2.02-0.8.fc21.x86_64

How reproducible:
Happened once, but it was more than enough.

Steps to Reproduce:
1. not sure, I think I just tried to Upgrade
2.
3.

Actual results:
pure disaster ... system doesn't boot and /boot configuiration seems to be all wrong without much clear path to the recovery.

Expected results:
system working with non-broken configuration.