Actions
Bug #5674
open
bootadm update-menu doesn't work with EFI-labeled disks
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Start date:
2015-03-01
Due date:
% Done:
0%
Estimated time:
Difficulty:
Medium
Tags:
needs-triage
Gerrit CR:
External Bug:
Description
If you create root pool on EFI-labeled disk, bootadm update-menu can't handle this:
# bootadm update-menu -R /a -o /dev/rdsk/c2t0d0 bootadm: fstyp -a on device /dev/rdsk/c2t0d0 failed bootadm: failed to get pool for device: /dev/rdsk/c2t0d0 bootadm: fstyp -a on device /dev/rdsk/c2t0d0 failed bootadm: failed to get pool name from /dev/rdsk/c2t0d0 bootadm: failed to create GRUB boot signature for device: /dev/rdsk/c2t0d0 bootadm: failed to get grubsign for root: /a, device /dev/rdsk/c2t0d0 # bootadm update-menu -R /a -o /dev/rdsk/c2t0d0s0 bootadm: failed to determine fdisk partition: /dev/rdsk/c2t0d0 bootadm: cannot get (hd?,?,?) for menu. menu not on bootdisk: /dev/rdsk/c2t0d0s0 bootadm: duplicate command default at line 9 of /aboot/grub/menu.lst
Updated by Hans Rosenfeld over 8 years ago
The first invocation of bootadm looks wrong, but the 2nd one should work. I wonder why there is -z to indicate ZFS, it thought that was mandatory.
I do remember seeing some warnings from bootadm, but the menu was updated correctly. Is that the case here? Could it be that bootadm works despite spewing out warnings?
Updated by Alexander Pyhalov over 8 years ago
Yes, it's the case. Bootadm works despite printing some warnings.
Actions