Ubuntu 20.04.1 lts driver & kernal has different version conflict

len@len-Z390-AORUS-ULTRA:~$ sudo inxi -Fxz
Kernel: 5.4.0-21-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
Desktop: Gnome 3.36.4 Distro: Ubuntu 20.04.1 LTS (Focal Fossa)
Type: Desktop System: Gigabyte product: Z390 AORUS ULTRA v: N/A
serial: N/A
Mobo: Gigabyte model: Z390 AORUS ULTRA-CF v: x.x serial: N/A
UEFI: American Megatrends v: F10b date: 12/18/2019
Topology: 8-Core model: Intel Core i9-9900KF bits: 64 type: MT MCP
arch: Kaby Lake rev: C L2 cache: 16.0 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 115200
Speed: 800 MHz min/max: 800/5000 MHz Core speeds (MHz): 1: 800 2: 800
3: 800 4: 800 5: 800 6: 801 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800
13: 800 14: 800 15: 800 16: 800
Device-1: NVIDIA TU106 [GeForce RTX 2070 Rev. A] vendor: ASUSTeK
driver: nvidia v: 435.21 bus ID: 01:00.0
Display: server: X.Org 1.20.8 driver: fbdev,nouveau FAILED: nvidia
unloaded: modesetting,vesa resolution: 1024x768~76Hz
OpenGL: renderer: llvmpipe (LLVM 10.0.0 256 bits) v: 3.3 Mesa 20.0.8
direct render: Yes
Device-1: Intel Cannon Lake PCH cAVS vendor: Gigabyte
driver: snd_hda_intel v: kernel bus ID: 00:1f.3
Device-2: NVIDIA TU106 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus ID: 01:00.1
Sound Server: ALSA v: k5.4.0-21-generic
Device-1: Intel Wireless-AC 9560 [Jefferson Peak] driver: iwlwifi
v: kernel bus ID: 00:14.3
IF: wlo1 state: up mac:
Device-2: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: 3.2.6-k
port: efa0 bus ID: 00:1f.6
IF: eno2 state: down mac:
Local Storage: total: 465.76 GiB used: 59.71 GiB (12.8%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 500GB
size: 465.76 GiB
ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 970 EVO Plus 500GB
size: 465.76 GiB
ID-3: /dev/nvme2n1 vendor: Samsung model: SSD 970 EVO Plus 500GB
size: 465.76 GiB
Device-1: dataocean type: zfs status: ONLINE size: 464.00 GiB
free: 464.00 GiB Components: online: N/A
Device-2: rpool type: zfs status: ONLINE raid: no-raid size: 460.00 GiB
free: 400.00 GiB Components: online: nvme1n1p5
ID-1: / size: 392.38 GiB used: 6.51 GiB (1.7%) fs: zfs
raid: rpool/ROOT/ubuntu_q6zf8y
ID-2: /var/log size: 387.05 GiB used: 1.19 GiB (0.3%) fs: zfs
raid: rpool/ROOT/ubuntu_q6zf8y/var/log
ID-3: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap
dev: /dev/nvme1n1p3
System Temperatures: cpu: 44.0 C mobo: N/A
Fan Speeds (RPM): N/A
Processes: 722 Uptime: 21h 08m Memory: 31.29 GiB used: 8.50 GiB (27.2%)
Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17
inxi: 3.0.38

My thoughts are I may have to do the above commands from an Ubuntu 20.04.1 live USB so the grub gets updated, note above the grub update did not work, (drive busy)

What do you think???

ah I think I have an idea.
I don’t have ubuntu 20 (with ZFS), but I did a search:

(solution #0)

If you have a bpool (as in boot pool), and I don’t see that in you inxi output, might that be the problem.
first run zpool status
look what pools you have.
then run:
zpool import -a -d /dev/disk/by-id
run zpool status again and see if you have the bpool.
then try update-grub and see if it does update your kernel list.


Thanks, I will read up on the the article you provided.

I will dig into this Monday, thank you again for your help.

The article does not say much more then I’ve told you.
Just run the few commands, nothing bad can happen.

len@len-Z390-AORUS-ULTRA:~$ zpool status
pool: dataocean
state: ONLINE
scan: scrub repaired 0B in 0 days 00:00:00 with 0 errors on Sun Nov 8 00:24:01 2020

NAME                                                     STATE     READ WRITE CKSUM
dataocean                                                ONLINE       0     0     0
  mirror-0                                               ONLINE       0     0     0
    nvme-Samsung_SSD_970_EVO_Plus_500GB_S4EVNF0MA60672T  ONLINE       0     0     0
    nvme-Samsung_SSD_970_EVO_Plus_500GB_S4EVNF0MA60669M  ONLINE       0     0     0

errors: No known data errors

pool: rpool
state: ONLINE
scan: scrub repaired 0B in 0 days 00:00:47 with 0 errors on Sun Nov 8 00:24:48 2020

rpool        ONLINE       0     0     0
  nvme1n1p5  ONLINE       0     0     0

errors: No known data errors
len@len-Z390-AORUS-ULTRA:~ zpool import -a -d /dev/disk/by-id cannot discover pools: permission denied len@len-Z390-AORUS-ULTRA:~ sudo zpool import -a -d /dev/disk/by-id
[sudo] password for len:
Sorry, try again.
[sudo] password for len:
cannot mount ‘/boot’: directory is not empty

len@len-Z390-AORUS-ULTRA:~ zfs list NAME USED AVAIL REFER MOUNTPOINT bpool 292M 1.46G 176K /boot bpool/BOOT 290M 1.46G 176K none bpool/BOOT/ubuntu_q6zf8y 290M 1.46G 290M /boot dataocean 8.56M 449G 7.63M /dataocean rpool 59.7G 386G 96K / rpool/ROOT 10.5G 386G 96K none rpool/ROOT/ubuntu_q6zf8y 10.5G 386G 6.52G / rpool/ROOT/ubuntu_q6zf8y/srv 96K 386G 96K /srv rpool/ROOT/ubuntu_q6zf8y/usr 407M 386G 96K /usr rpool/ROOT/ubuntu_q6zf8y/usr/local 407M 386G 407M /usr/local rpool/ROOT/ubuntu_q6zf8y/var 3.57G 386G 96K /var rpool/ROOT/ubuntu_q6zf8y/var/games 96K 386G 96K /var/games rpool/ROOT/ubuntu_q6zf8y/var/lib 2.38G 386G 2.25G /var/lib rpool/ROOT/ubuntu_q6zf8y/var/lib/AccountServices 96K 386G 96K /var/lib/AccountServices rpool/ROOT/ubuntu_q6zf8y/var/lib/NetworkManager 180K 386G 180K /var/lib/NetworkManager rpool/ROOT/ubuntu_q6zf8y/var/lib/apt 73.9M 386G 73.9M /var/lib/apt rpool/ROOT/ubuntu_q6zf8y/var/lib/dpkg 52.3M 386G 52.3M /var/lib/dpkg rpool/ROOT/ubuntu_q6zf8y/var/log 1.19G 386G 1.19G /var/log rpool/ROOT/ubuntu_q6zf8y/var/mail 96K 386G 96K /var/mail rpool/ROOT/ubuntu_q6zf8y/var/snap 160K 386G 160K /var/snap rpool/ROOT/ubuntu_q6zf8y/var/spool 120K 386G 120K /var/spool rpool/ROOT/ubuntu_q6zf8y/var/www 96K 386G 96K /var/www rpool/USERDATA 49.2G 386G 96K / rpool/USERDATA/len_3ii4c7 49.0G 386G 49.0G /home/len rpool/USERDATA/root_3ii4c7 228M 386G 228M /root rpool/var 376K 386G 96K /var rpool/var/lib 280K 386G 96K /var/lib rpool/var/lib/docker 184K 386G 184K /var/lib/docker len@len-Z390-AORUS-ULTRA:~

zfs set overlay=on bpool
to allow mounting in a busy directory. then:

zfs mount bpool

len@len-Z390-AORUS-ULTRA:~ sudo zfs set overlay=on bpool len@len-Z390-AORUS-ULTRA:~ zfs mount bpool
cannot mount ‘bpool’: ‘canmount’ property is set to ‘off’

zfs set canmount=on bpool

and then the previous commands again followed by update-grub

len@len-Z390-AORUS-ULTRA:~ zfs set canmount=on bpool cannot set property for 'bpool': permission denied len@len-Z390-AORUS-ULTRA:~ sudo zfs set canmount=on bpool
len@len-Z390-AORUS-ULTRA:~ zfs set overlay=on bpool cannot set property for 'bpool': permission denied len@len-Z390-AORUS-ULTRA:~ sudo zfs set overlay=on bpool
len@len-Z390-AORUS-ULTRA:~ sudo zfs mount bpool len@len-Z390-AORUS-ULTRA:~ sudo update-grub
Sourcing file /etc/default/grub' Sourcing file /etc/default/grub.d/init-select.cfg’
/usr/sbin/grub-mkconfig: 269: cannot create /boot/grub/grub.cfg.new: Directory nonexistent

what does ls -aR /boot show?

len@len-Z390-AORUS-ULTRA:~ sudo ls -aR /boot [sudo] password for len: /boot: . .. len@len-Z390-AORUS-ULTRA:~

Ok, I’m a bit lost here.
If you do zfs unmount bpool, does ls -aR boot show more?

len@len-Z390-AORUS-ULTRA:~ sudo zfs unmount bpool len@len-Z390-AORUS-ULTRA:~ sudo ls -aR /boot
. memtest86+.bin
… memtest86+.elf
config-5.4.0-54-generic memtest86+_multiboot.bin
grub System.map-5.4.0-54-generic
initrd.img vmlinuz
initrd.img-5.4.0-21-generic vmlinuz-5.4.0-54-generic
initrd.img-5.4.0-54-generic vmlinuz.old

. … grub.cfg grubenv unicode.pf2

Well I’m really lost on the zfs setup of ubuntu.
But you have the config-5.4.0-54-generic vmlinuz-5.4.0-54-generic
initrd.img-5.4.0-54-generic files there.
Can’t tell you why update-grub does not recognize them.
Revert the settings we made:
zfs set overlay=off canmount=off bpool

I’d ask in the ubuntu forums for help on this, sorry I can’t help you on that.

Thanks for your help, you went over and beyond on this, can see a new system install I think if Ubuntu forums areof no help, ZFS is great to use, so many features, but hard to set up and work with, thanks mate, talk next time

It looks to me there’s an ubuntu bug, re the link I posted.

The zfs on root is new, so easily possible there are still a few quirks.