[Bug 1848856] Re: zfs on root fails with grub syntax error with multidisk pools

Jean-Baptiste Lallement jean-baptiste.lallement at ubuntu.com
Mon Nov 18 08:10:15 UTC 2019

** Summary changed:

- Upgrade from 19.04 to 19.10 with zfs on root fails with grub syntax error
+ zfs on root fails with grub syntax error with multidisk pools

You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.

  zfs on root fails with grub syntax error with multidisk pools

Status in grub2 package in Ubuntu:
  In Progress
Status in grub2 source package in Focal:
  In Progress

Bug description:
  At the end of the upgrade from 19.04 to 19.10, the post process of the
  update-grub reports:

  Syntax error at line 185
  Syntax errors are detected in generated GRUB config file.
  Ensure that there are no errors in /etc/default/grub
  and /etc/grub.d/* files or please file a bug report with
  /boot/grub/grub.cfg.new file attached.
  run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1
  dpkg: error processing package linux-image-5.3.0-18-generic (--configure):
   installed linux-image-5.3.0-18-generic package post-installation script subprocess returned error exit status 1
  Errors were encountered while processing:

  The system used https://github.com/zfsonlinux/zfs/wiki/Ubuntu-18.04
  -Root-on-ZFS to add zfs on root to a 19.04 system.

  The syntax error in grub.cfg.new is an extra } on line 185.  However,
  comparing the grub.cfg.new to the previously generated grub.cfg under
  19.04, there is a significant quantity of configuration missing.

  Manually running update-grub generates the same error.
  /etc/default/grub is the only file changed from default installation
  to include zswap.  This file was not changed prior to upgrade.

  The error is reported during the processing of
  /etc/grub.d/10_linux_zfs which is dated October 11.  I attempted the
  upgrade on 10/18 and have done multiple updates to get the latest
  kernel and remove old kernels prior to the upgrade.  So, I believe the
  problem is with one of the upgrade modules.

To manage notifications about this bug go to:

More information about the Ubuntu-sponsors mailing list