digrouz's questions

Today I did update my system which was originally installed following Ubuntu 20.04 Root on ZFS. While updating, I see that there is an update for grub, which failed to run the included grub-install.

So I decided to replay the grub installation from the guide:

grub-install --target=x86_64-efi --efi-directory=/boot/efi \
    --bootloader-id=ubuntu --recheck --no-floppy

cp -a /boot/efi/EFI /boot/efi2
grub-install --target=x86_64-efi --efi-directory=/boot/efi2 \
    --bootloader-id=ubuntu-2 --recheck --no-floppy

(i'm on a mirror)

which failed too. I can still reboot my system with success but I guess it still run the old grub binaries.

Am I the only one facing this issue? What's the incidence of it ?

Here is some more infos:

 dpkg -l | grep grub
ii  grub-common                          2.04-1ubuntu26.7                      amd64        GRand Unified Bootloader (common files)
ii  grub-efi-amd64                       2.04-1ubuntu26.7                      amd64        GRand Unified Bootloader, version 2 (EFI-AMD64 version)
ii  grub-efi-amd64-bin                   2.04-1ubuntu26.7                      amd64        GRand Unified Bootloader, version 2 (EFI-AMD64 modules)
ii  grub-efi-amd64-signed                1.142.9+2.04-1ubuntu26.7              amd64        GRand Unified Bootloader, version 2 (EFI-AMD64 version, signed)
ii  grub2-common                         2.04-1ubuntu26.7                      amd64        GRand Unified Bootloader (common files for version 2)

running :

grub-install --target=x86_64-efi --efi-directory=/boot/efi \ --bootloader-id=ubuntu --recheck --no-floppy -vv
...
grub-install: info: writing 656 bytes of a fixup block starting at 0xe000.
grub-install: info: adding a relocation entry for 0xf010.
grub-install: info: adding a relocation entry for 0xf018.
grub-install: info: adding a relocation entry for 0xf028.
grub-install: info: adding a relocation entry for 0xf030.
grub-install: info: adding a relocation entry for 0xf040.
grub-install: info: adding a relocation entry for 0xf048.
grub-install: info: adding 393 padding fixup entries.
grub-install: info: writing 808 bytes of a fixup block starting at 0xf000.
grub-install: info: reading /usr/lib/grub/x86_64-efi/crypto.mod.
grub-install: info: reading /usr/lib/grub/x86_64-efi/gcry_crc.mod.
grub-install: info: reading /usr/lib/grub/x86_64-efi/gzio.mod.
grub-install: info: reading /usr/lib/grub/x86_64-efi/zfs.mod.
grub-install: info: reading /usr/lib/grub/x86_64-efi/part_gpt.mod.
grub-install: info: reading /usr/lib/grub/x86_64-efi/search_fs_uuid.mod.
grub-install: info: reading /boot/grub/x86_64-efi/load.cfg.
grub-install: info: kernel_img=0x556fae524f00, kernel_size=0x1a000.
grub-install: info: the core size is 0x31b40.
grub-install: info: writing 0x34000 bytes.
grub-install: info: copying `/usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed' -> `/boot/efi2/EFI/ubuntu-2/grubx64.efi'.
grub-install: info: copying `/usr/lib/shim/shimx64.efi.signed' -> `/boot/efi2/EFI/ubuntu-2/shimx64.efi'.
grub-install: info: copying `/usr/lib/shim/mmx64.efi' -> `/boot/efi2/EFI/ubuntu-2/mmx64.efi'.
grub-install: info: copying `/usr/lib/shim/BOOTX64.CSV' -> `/boot/efi2/EFI/ubuntu-2/BOOTX64.CSV'.
grub-install: info: copying `/boot/grub/x86_64-efi/load.cfg' -> `/boot/efi2/EFI/ubuntu-2/grub.cfg'.
grub-install: info: copying `/usr/lib/shim/shimx64.efi.signed' -> `/boot/efi2/EFI/BOOT/BOOTX64.EFI'.
grub-install: info: copying `/usr/lib/shim/fbx64.efi' -> `/boot/efi2/EFI/BOOT/fbx64.efi'.
grub-install: info: copying `/usr/lib/shim/mmx64.efi' -> `/boot/efi2/EFI/BOOT/mmx64.efi'.
grub-install: info: Registering with EFI: distributor = `ubuntu-2', path = `\EFI\ubuntu-2\shimx64.efi', ESP at hostdisk//dev/sdl,gpt1.
grub-install: warning: Internal error.
grub-install: error: failed to register the EFI boot entry: Operation not permitted.

How do I fix this ?

I've 2 MP600 on my system which are un-usable by Ubuntu 20.04.1 with HWE kernel: 5.8.0-25-generic

root@ubuntu:/dev/disk/by-id# mkfs.ext4 /dev/nvme1n1p1
mke2fs 1.45.5 (07-Jan-2020)
/dev/nvme1n1p1 is apparently in use by the system; will not make a filesystem here! 

My motherboard is Asrock x570m pro4 with a Ryzen 9 3950x cpu. Both nvme shows properly in bios and are on compatibility list at vendor website : Asrock website

I tried to contact Corsair which sounded not helpfull at all, stating to format them under windows. Which I tried with an external adapter on a windows laptop. That went successfull, but after repluging them into the ubuntu host, they still unusable, no mkfs, no mount, always stating device or ressource busy.

How can make them usable ? What Am I missing ?

I'm on ubuntu 18.04 which is part of an active directory domain using sssd.

How can get my ubuntu to register its hostnmae to the dns server.

I saw How to get Ubuntu Host to Register Hostname With DNS Server which seems to not apply to 18.04 has it's not using dhclient ?

I did not find anything in netplan to do this.

I found a way to do it with systemd-networkd: https://unix.stackexchange.com/questions/450032/systemd-networkd-dhcp-hostname-option but it's not doing it and I don't any error message anywhere regarding the fact that networkd is trying and failing.

Any idea ?

I'm running 17.04 on a zfs root. While running update-initramfs I receive a warning that may have no impact but I would look to be sure, and report upstream if the issue is not on my side. Is anyone having the same behavior ?

$ sudo update-initramfs -c -k all 
update-initramfs: Generating /boot/initrd.img-4.10.0-15-generic
Warning: /sbin/fsck.zfs_member doesn't exist, can't install to initramfs, ignoring.

I was wondering if it was possible to install the pantheon desktop from elementary-os on a ubuntu 16.10 ?

thx