[Bug 1531474] [NEW] update-grub improperly inserting <cr> between devices on linux line of grub.cfg in multi-dev btrfs sys's

[DiagonalArg]

Public bug reported:

On a new install of wily.  update-grub is improperly inserting a
carriage return on the "linux" line of the grub.cfg menu items, between
the two devices of a btrfs raid1 system (which for my system is in a
luks container).  The menu entries all looks like this:

menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-/dev/mapper/luks.root1_/dev/mapper/luks.root2' {
        recordfail
        load_video
        gfxmode $linux_gfx_mode
        insmod gzio
        if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
        insmod part_msdos
        insmod btrfs
        set root='hd2,msdos1'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd2,msdos1 --hint-efi=hd2,msdos1 --hint-baremetal=ahci2,msdos1  fe74974e-3e23-43af-bfb1-7b520673c52b
        else
          search --no-floppy --fs-uuid --set=root <UUID>
        fi
        linux   /@s3970boot/vmlinuz-4.2.0-23-generic root=/dev/mapper/luks.root1
/dev/mapper/luks.root2 ro rootflags=subvol=@  quiet splash $vt_handoff
        initrd  /@s3970boot/initrd.img-4.2.0-23-generic
}


Removing that <cr> makes everything boot fine.

** Affects: grub2 (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: btrfs grub2 raid

-- 
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/1531474

Title:
  update-grub improperly inserting <cr> between devices on linux line of
  grub.cfg in multi-dev btrfs sys's

Status in grub2 package in Ubuntu:
  New

Bug description:
  On a new install of wily.  update-grub is improperly inserting a
  carriage return on the "linux" line of the grub.cfg menu items,
  between the two devices of a btrfs raid1 system (which for my system
  is in a luks container).  The menu entries all looks like this:

  menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-/dev/mapper/luks.root1_/dev/mapper/luks.root2' {
          recordfail
          load_video
          gfxmode $linux_gfx_mode
          insmod gzio
          if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
          insmod part_msdos
          insmod btrfs
          set root='hd2,msdos1'
          if [ x$feature_platform_search_hint = xy ]; then
            search --no-floppy --fs-uuid --set=root --hint-bios=hd2,msdos1 --hint-efi=hd2,msdos1 --hint-baremetal=ahci2,msdos1  fe74974e-3e23-43af-bfb1-7b520673c52b
          else
            search --no-floppy --fs-uuid --set=root <UUID>
          fi
          linux   /@s3970boot/vmlinuz-4.2.0-23-generic root=/dev/mapper/luks.root1
  /dev/mapper/luks.root2 ro rootflags=subvol=@  quiet splash $vt_handoff
          initrd  /@s3970boot/initrd.img-4.2.0-23-generic
  }

  
  Removing that <cr> makes everything boot fine.

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