[Bug 1613008] Re: Ub 16.10 - grub writes invalid search entry in grub.cfg

[Mate Kukri]

We still use search lines like this and they work just fine.

** Changed in: grub2 (Ubuntu)
       Status: New => Invalid

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

Title:
  Ub 16.10 - grub writes invalid search entry in grub.cfg

Status in grub2 package in Ubuntu:
  Invalid

Bug description:
  Description:	Ubuntu Yakkety Yak (development branch)
  Release:	16.10
  grub-efi_2.02~beta2-36ubuntu10_amd64.deb
  grub-efi-amd64-signed_1.73+2.02~beta2-36ubuntu10_amd64.deb
  grub-efi-amd64-bin_2.02~beta2-36ubuntu10_amd64.deb
  grub-efi-amd64_2.02~beta2-36ubuntu10_amd64.deb

  I had InsydeH20 setup "load file", grubx64.efi.signed, and at the grub
  prompt I tested search, search.fs_uuid, search.fs_file, and
  search.label. The old search line in grub.cfg is a bug!

  You will not notice anything wrong in the result, if at grub prompt
  you search with the expectation of seeing (hd0,msdos1) because search
  will always echo that default back to you as if it did a search, when
  it did nothing. Try looking for uuid/file/label for (hd0,msdos2) or
  another partition number higher than the first partition. Broken!

  All of these "search --nofloppy" grub.cfg lines are broken in several
  different ways including the "=" not working anymore:

  search --nofloppy --fs-uuid [uuid] --set=root

  the new, working syntax goes like this:

  search -n -u [uuid] -s root

  That's the bug. 16.10 64-bit just installed grub and Ubuntu nicely in
  efi mode, then reboot bsod due to the bad search line in grub.cfg.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1613008/+subscriptions