Debian/OMV/zfs HC4 boot stuck in "Import ZFS pools"

Post Reply
dqbydt
Posts: 69
Joined: Wed Mar 01, 2017 7:52 am
languages_spoken: English
ODROIDs: C1+ C2 C4 HC4 XU4 VU5 VU7+
Has thanked: 1 time
Been thanked: 3 times
Contact:

Debian/OMV/zfs HC4 boot stuck in "Import ZFS pools"

Post by dqbydt »

I have an HC4 with Debian buster/OMV/zfs, which has been working fine for ~1.5 years. I took a system update via OMV, and suddenly it does not boot anymore. Boot gets stuck in

Code: Select all

[***   ] A start job is running for Import ZFS pools by cache file (1min 17s no limit)
Internet search reveals that this can be caused if disks are identified by device name rather than disk-id. If you boot with a USB flash drive inserted, the device names can change resulting in named disks not being found. This is not the case for me.

I found some other suggestions (e.g. this) but petitboot seems to mount the SD card partitions as readonly; how can I make changes in the rootfs? (And is this even a reasonable thing to try?)

User avatar
tobetter
Posts: 10982
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 741 times
Been thanked: 1873 times
Contact:

Re: Debian/OMV/zfs HC4 boot stuck in "Import ZFS pools"

Post by tobetter »

No idea what happen to ZFS, but you can try this if you like to try some workaround found in the internet.

1. Instead of adding/changing /etc/modprobe.dzfs.conf[/b], add scsi_mod.scan=sync to the kernel command line in Petitboot. For this, in Petitboot, move the cursor to Debian boot entry and press 'e' in order to have boot config and add it to the end of the line of kernel command line.
2. If you like to change the root file system which is read only in Petitboot, you can mount it with the option mount -o remount,rw if you know the exact device node for the storage.
3. Alternatively, you can boot small Ubuntu through network. Run netboot_default in the Petitboot command line and select the boot entry with Live System so it will load and run small Linux system through network. You can get into it with the account odroid and odroid for its password.

igorpec
Posts: 1078
Joined: Sat Dec 12, 2015 4:34 pm
languages_spoken: bash,c++,python
Has thanked: 70 times
Been thanked: 164 times
Contact:

Re: Debian/OMV/zfs HC4 boot stuck in "Import ZFS pools"

Post by igorpec »

dqbydt wrote:
Fri Nov 18, 2022 9:44 am
I have an HC4 with Debian buster/OMV/zfs, which has been working fine for ~1.5 years.
Which kernel / ZFS version are you using?

dqbydt
Posts: 69
Joined: Wed Mar 01, 2017 7:52 am
languages_spoken: English
ODROIDs: C1+ C2 C4 HC4 XU4 VU5 VU7+
Has thanked: 1 time
Been thanked: 3 times
Contact:

Re: Debian/OMV/zfs HC4 boot stuck in "Import ZFS pools"

Post by dqbydt »

Thanks @tobetter, the Live System is useful. However it is not possible to install zfs tools in this image as the zfs-dkms package is too old for the 5.11 kernel in the image:

Code: Select all

Error! The /var/lib/dkms/zfs/0.8.3/5.11.0-odroid-arm64.aarch64/dkms.conf for module zfs includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch. This indicates that it should not be built.
And sure enough, /var/lib/dkms/zfs/0.8.3/source/dkms.conf has

Code: Select all

BUILD_EXCLUSIVE_KERNEL="^4\.[0-9]+..."
so it is for kernels up to 4.9. So it is not possible to use zfs commands within my rootfs chroot to administer the zfs pool. Would it be possible to upgrade the zfs packages in the live image to 2.0.3?

For now, I chrooted into my rootfs through the Live image and disabled all the zfs related services:

Code: Select all

# systemctl disable zfs-import-cache.service
# systemctl disable zfs-mount.service
# systemctl disable zfs.target
This has enabled the system to boot although of course the zfs mounts are not available. However, it doesn't even report that any pools are present:

Code: Select all

# zpool status
no pools available
So I will need to do some more research into that.
Which kernel / ZFS version are you using?

Code: Select all

# uname -r
5.10.0-odroid-arm64

# dpkg -l | g zfs
ii  libzfs4linux                       2.0.3-9~bpo10+1                      arm64        OpenZFS filesystem library for Linux
ii  openmediavault-zfs                 5.0.6                                arm64        OpenMediaVault plugin for ZFS
ii  zfs-dkms                           2.0.3-9~bpo10+1                      all          OpenZFS filesystem kernel modules for Linux
ii  zfs-zed                            2.0.3-9~bpo10+1                      arm64        OpenZFS Event Daemon
ii  zfsutils-linux                     2.0.3-9~bpo10+1                      arm64        command-line tools to manage OpenZFS filesystems

dqbydt
Posts: 69
Joined: Wed Mar 01, 2017 7:52 am
languages_spoken: English
ODROIDs: C1+ C2 C4 HC4 XU4 VU5 VU7+
Has thanked: 1 time
Been thanked: 3 times
Contact:

Re: Debian/OMV/zfs HC4 boot stuck in "Import ZFS pools"

Post by dqbydt »

It appears that doing a zpool import results in a kernel oops/mem abort (although it doesn't result in a total system crash). When I originally posted that boot appeared to be stuck in "import ZFS pools", there also was an oops dump in the output preceding, although there was no way to scroll up to see the source of the dump.

I just tried doing a zpool import manually, and that triggered an oops. I compared this output with the photo I had taken of the stuck boot, and the call trace matches exactly. So this must be what is happening during boot -- it tries to do an import and crashes; subsequent zpool commands hang indefinitely. That is why the boot gets stuck in the import stage. [Right now after having manually triggered the oops, any following zpool commands like zpool status, hang forever.]

What could cause this to happen though? I did nothing significant other than taking updates through OMV. Is there a way to find out the contents of the last system update? And how do I go about recovering this?

[Edit: adding oops log]

Code: Select all

[ 4025.750181] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000028
[ 4025.750184] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000028
[ 4025.750191] Mem abort info:
[ 4025.750288] Mem abort info:
[ 4025.752885]   ESR = 0x96000004
[ 4025.752890]   EC = 0x25: DABT (current EL), IL = 32 bits
[ 4025.752893]   SET = 0, FnV = 0
[ 4025.752895]   EA = 0, S1PTW = 0
[ 4025.752897] Data abort info:
[ 4025.752902]   ISV = 0, ISS = 0x00000004
[ 4025.755452]   ESR = 0x96000004
[ 4025.755457]   EC = 0x25: DABT (current EL), IL = 32 bits
[ 4025.757971]   CM = 0, WnR = 0
[ 4025.760426]   SET = 0, FnV = 0
[ 4025.760430]   EA = 0, S1PTW = 0
[ 4025.760435] Data abort info:
[ 4025.762894] user pgtable: 4k pages, 48-bit VAs, pgdp=000000003f641000
[ 4025.762896] [0000000000000028] pgd=0000000000000000, p4d=0000000000000000
[ 4025.765330]   ISV = 0, ISS = 0x00000004
[ 4025.765332]   CM = 0, WnR = 0
[ 4025.765338] user pgtable: 4k pages, 48-bit VAs, pgdp=000000003f641000

[ 4025.767767] Internal error: Oops: 96000004 [#1] PREEMPT SMP
[ 4025.767771] Modules linked in:
[ 4025.770201] [0000000000000028] pgd=0000000000000000
[ 4025.772602]  softdog xt_nat xt_tcpudp macvlan veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user nft_counter xt_addrtype
[ 4025.775037] , p4d=0000000000000000
[ 4025.777436]  nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink br_netfilter bridge cpufreq_powersave

[ 4025.782194]  cpufreq_conservative overlay zram snd_soc_hdmi_codec dw_hdmi_i2s_audio snd_soc_meson_axg_tdmout snd_soc_meson_g12a_tohdmitx snd_soc_meson_codec_glue meson_rng rng_core snd_soc_meson_axg_frddr snd_soc_meson_axg_fifo reset_meson_audio_arb meson_dw_hdmi sg dw_hdmi meson_vdec(C) v4l2_mem2mem videobuf2_dma_contig videobuf2_v4l2 videobuf2_memops panfrost videobuf2_common gpu_sched videodev ir_nec_decoder meson_ir mc snd_soc_meson_axg_sound_card snd_soc_meson_card_utils meson_drm snd_soc_meson_axg_tdm_interface snd_soc_meson_axg_tdm_formatter meson_canvas pwm_fan zfs(PO) zunicode(PO) zzstd(O) zlua(O) zcommon(PO) znvpair(PO) zavl(PO) icp(PO) spl(O) ip_tables x_tables raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx raid1 raid0 multipath linear md_mod spidev axg_audio sclk_div clk_phase ahci libahci spi_meson_spicc libata meson_gxl realtek
[ 4025.818666] CPU: 1 PID: 11578 Comm: vdev_open Tainted: P         C O      5.10.0-odroid-arm64 #1 Debian 5.10.105-202203131842~buster
[ 4025.818667] Hardware name: Hardkernel ODROID-HC4 (DT)
[ 4025.818670] pstate: 60c00009 (nZCv daif +PAN +UAO -TCO BTYPE=--)
[ 4025.818680] pc : blk_throtl_bio+0x48/0x720
[ 4025.818685] lr : submit_bio_checks+0x184/0x470
[ 4025.818686] sp : ffff8000139ab880
[ 4025.818688] x29: ffff8000139ab880 x28: 0000000000000000 
[ 4025.818691] x27: 0000000000044000 x26: ffff0000085796c0 
[ 4025.818695] x25: 0000000000000000 x24: ffff000002b88000 
[ 4025.818698] x23: ffff00000b038a80 x22: 0000000000000000 
[ 4025.818701] x21: ffff000009c10000 x20: ffff000009c10000 
[ 4025.818704] x19: ffff00003f661800 x18: 0000000000000000 
[ 4025.818707] x17: 0000000000000000 x16: 0000000000000000 
[ 4025.818710] x15: 0000000000000001 x14: 0000000000000002 
[ 4025.818713] x13: 00000000000943d1 x12: ffff0000b6fcb910 
[ 4025.818717] x11: ffff8000a5a01000 x10: 0000000000000000 
[ 4025.818720] x9 : ffff0000ed047100 x8 : ffff000001d65ec8 
[ 4025.818723] x7 : 0000000000000000 x6 : 000000004950b000 
[ 4025.818726] x5 : ffff000001d65e70 x4 : 0000000000000000 
[ 4025.818729] x3 : ffff000002b88750 x2 : 0000000000000001 
[ 4025.818732] x1 : ffff000002b88000 x0 : ffff000003437000 
[ 4025.818736] Call trace:
[ 4025.818740]  blk_throtl_bio+0x48/0x720
[ 4025.818743]  submit_bio_checks+0x184/0x470
[ 4025.818746]  submit_bio_noacct+0x30/0x438
[ 4025.818748]  submit_bio+0x48/0x1f0
[ 4025.818877]  vdev_disk_io_start+0x5ec/0x9b0 [zfs]
[ 4025.818996]  zio_vdev_io_start+0xdc/0x2b8 [zfs]
[ 4025.819106]  zio_nowait+0xd0/0x1a8 [zfs]
[ 4025.819217]  vdev_probe+0xfc/0x318 [zfs]
[ 4025.819327]  vdev_open+0x220/0x6c0 [zfs]
[ 4025.819436]  vdev_open_child+0x20/0x38 [zfs]
[ 4025.819453]  taskq_thread+0x294/0x430 [spl]
[ 4025.819459]  kthread+0x154/0x158
[ 4025.819464]  ret_from_fork+0x10/0x34
[ 4025.819471] Code: b9864800 8b000f83 f9405c7c b9401276 (f9401799) 
[ 4025.819475] ---[ end trace 06298c1d0fc11291 ]---
[ 4025.819486] Internal error: Oops: 96000004 [#2] PREEMPT SMP
[ 4025.819490] Modules linked in: softdog xt_nat xt_tcpudp macvlan veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user nft_counter xt_addrtype nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink br_netfilter bridge cpufreq_powersave cpufreq_conservative overlay zram snd_soc_hdmi_codec dw_hdmi_i2s_audio snd_soc_meson_axg_tdmout snd_soc_meson_g12a_tohdmitx snd_soc_meson_codec_glue meson_rng rng_core snd_soc_meson_axg_frddr snd_soc_meson_axg_fifo reset_meson_audio_arb meson_dw_hdmi sg dw_hdmi meson_vdec(C) v4l2_mem2mem videobuf2_dma_contig videobuf2_v4l2 videobuf2_memops panfrost videobuf2_common gpu_sched videodev ir_nec_decoder meson_ir mc snd_soc_meson_axg_sound_card snd_soc_meson_card_utils meson_drm snd_soc_meson_axg_tdm_interface snd_soc_meson_axg_tdm_formatter meson_canvas pwm_fan zfs(PO) zunicode(PO) zzstd(O) zlua(O) zcommon(PO) znvpair(PO) zavl(PO) icp(PO) spl(O) ip_tables x_tables raid10 raid456 async_raid6_recov async_memcpy
[ 4025.819625]  async_pq async_xor async_tx raid1 raid0 multipath linear md_mod spidev axg_audio sclk_div clk_phase ahci libahci spi_meson_spicc libata meson_gxl realtek
[ 4025.819653] CPU: 3 PID: 11577 Comm: vdev_open Tainted: P      D  C O      5.10.0-odroid-arm64 #1 Debian 5.10.105-202203131842~buster
[ 4025.819655] Hardware name: Hardkernel ODROID-HC4 (DT)
[ 4025.819658] pstate: 60c00009 (nZCv daif +PAN +UAO -TCO BTYPE=--)
[ 4025.819668] pc : blk_throtl_bio+0x48/0x720
[ 4025.819672] lr : submit_bio_checks+0x184/0x470
[ 4025.819674] sp : ffff8000139a3880
[ 4025.819675] x29: ffff8000139a3880 x28: 0000000000000000 
[ 4025.819679] x27: 0000000000044000 x26: ffff000008555d40 
[ 4025.819682] x25: 0000000000000000 x24: ffff0000033ee580 
[ 4025.819685] x23: ffff00000cac7e80 x22: 0000000000000000 
[ 4025.819688] x21: ffff000009ce8000 x20: ffff000009ce8000 
[ 4025.819691] x19: ffff000008d69e00 x18: 0000000000000000 
[ 4025.819694] x17: 0000000000000001 x16: 0000000000000019 
[ 4025.819697] x15: 0000000000000001 x14: 0000000000000002 
[ 4025.819700] x13: 00000000000943d1 x12: ffff0000b6ff9910 
[ 4025.819703] x11: ffff8000a5a2f000 x10: 0000000000000000 
[ 4025.819706] x9 : ffff0000ed047100 x8 : ffff0000546a97e8 
[ 4025.819709] x7 : 0000000000000000 x6 : 000000004952d000 
[ 4025.819712] x5 : ffff0000546a9790 x4 : 0000000000000000 
[ 4025.819715] x3 : ffff0000033eecd0 x2 : 0000000000000001 
[ 4025.819718] x1 : ffff0000033ee580 x0 : ffff000008e22000 
[ 4025.819721] Call trace:
[ 4025.819726]  blk_throtl_bio+0x48/0x720
[ 4025.819729]  submit_bio_checks+0x184/0x470
[ 4025.819733]  submit_bio_noacct+0x30/0x438
[ 4025.819735]  submit_bio+0x48/0x1f0
[ 4025.819862]  vdev_disk_io_start+0x5ec/0x9b0 [zfs]
[ 4025.819985]  zio_vdev_io_start+0xdc/0x2b8 [zfs]
[ 4025.820099]  zio_nowait+0xd0/0x1a8 [zfs]
[ 4025.820212]  vdev_probe+0xfc/0x318 [zfs]
[ 4025.820325]  vdev_open+0x220/0x6c0 [zfs]
[ 4025.820440]  vdev_open_child+0x20/0x38 [zfs]
[ 4025.820459]  taskq_thread+0x294/0x430 [spl]
[ 4025.820466]  kthread+0x154/0x158
[ 4025.820472]  ret_from_fork+0x10/0x34
[ 4025.820480] Code: b9864800 8b000f83 f9405c7c b9401276 (f9401799) 
[ 4025.820484] ---[ end trace 06298c1d0fc11292 ]---

igorpec
Posts: 1078
Joined: Sat Dec 12, 2015 4:34 pm
languages_spoken: bash,c++,python
Has thanked: 70 times
Been thanked: 164 times
Contact:

Re: Debian/OMV/zfs HC4 boot stuck in "Import ZFS pools"

Post by igorpec »

In case you want to skip debugging of old ZFS + old private kernel and start using it, perhaps rather follow this path:
https://www.armbian.com/odroid-hc4/ (remove petitiboot as you don't need it)
https://forum.armbian.com/topic/17337-z ... k-like-me/ (Ubuntu)
https://forum.armbian.com/topic/19336-a ... droid-hc4/ (Debian -> OMV)
We have several deployment running Armbian with no troubles at all. Some are x86, some HC4.

dqbydt
Posts: 69
Joined: Wed Mar 01, 2017 7:52 am
languages_spoken: English
ODROIDs: C1+ C2 C4 HC4 XU4 VU5 VU7+
Has thanked: 1 time
Been thanked: 3 times
Contact:

Re: Debian/OMV/zfs HC4 boot stuck in "Import ZFS pools"

Post by dqbydt »

igorpec wrote:
Sat Nov 19, 2022 3:59 pm
In case you want to skip debugging of old ZFS + old private kernel and start using it, perhaps rather follow this path:
We have several deployment running Armbian with no troubles at all. Some are x86, some HC4.
But will I be able to import my current zfs mirror seamlessly in the Armbian install? If there are any prerequisites (e.g. zpool export?) then I am forced to try and debug my current installation.

igorpec
Posts: 1078
Joined: Sat Dec 12, 2015 4:34 pm
languages_spoken: bash,c++,python
Has thanked: 70 times
Been thanked: 164 times
Contact:

Re: Debian/OMV/zfs HC4 boot stuck in "Import ZFS pools"

Post by igorpec »

dqbydt wrote:
Mon Nov 21, 2022 4:38 pm
But will I be able to import my current zfs mirror seamlessly in the Armbian install?
Import of older pools on newer versions usually works without a problem. Sometimes it tells you that once you upgrade, you can't use it on older version of ZFS. This is normal and expected. Anyway ZFS is not Armbian or Debian thing ... https://github.com/zfsonlinux

dqbydt
Posts: 69
Joined: Wed Mar 01, 2017 7:52 am
languages_spoken: English
ODROIDs: C1+ C2 C4 HC4 XU4 VU5 VU7+
Has thanked: 1 time
Been thanked: 3 times
Contact:

Re: Debian/OMV/zfs HC4 boot stuck in "Import ZFS pools"

Post by dqbydt »

I was able to revive my system. A summary in case it is helpful for anyone:
  • System was stuck in boot in zfs import. Booted into live image via petitboot by running netboot_default. chrooted into the rootfs and disabled zfs targets/services. This allowed the system to boot.
  • zpool status was showing “no pools available”. Tried zpool import and that resulted in a kernel oops. After that, all zpool commands would just hang. This is what was causing the boot hang.
  • `grep upgrade /var/log/dpkg.log` showed that kernel got upgraded from 5.10.23 to 5.10.105. (It was after this uprade that it had stopped booting.)
  • dkms reported "Module zfs/2.0.3 already built for kernel 5.10.0-odroid-arm64/4." This seems reasonable: only the patchlevel changed; this should not have necessitated rebuild of any modules.
  • Forced recompile of the zfs modules anyway, via dkms remove and dkms install.
  • Then did a zpool import. That worked! Then restored the zfs target/services and rebooted. Everything now works fine.
So somehow rebuild of the zfs modules worked, even though that shouldn't have been necessary. I would indeed be happier with a mainline kernel/latest ZFS, and will try installing Armbian. I have a couple of questions:
  1. If it is possible to run mainline kernel, why does HardKernel maintain a private kernel? I assume it is because not all parts of the SOC are supported in mainline? If so, what support is missing in mainline?
  2. Being able to boot into a live image was critical to rescuing my system. Is this possible via Uboot?
Thank you @tobetter and @igorpec for your suggestions so far.

User avatar
tobetter
Posts: 10982
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 741 times
Been thanked: 1873 times
Contact:

Re: Debian/OMV/zfs HC4 boot stuck in "Import ZFS pools"

Post by tobetter »

dqbydt wrote:
Thu Nov 24, 2022 7:41 am
I was able to revive my system. A summary in case it is helpful for anyone:
  • System was stuck in boot in zfs import. Booted into live image via petitboot by running netboot_default. chrooted into the rootfs and disabled zfs targets/services. This allowed the system to boot.
  • zpool status was showing “no pools available”. Tried zpool import and that resulted in a kernel oops. After that, all zpool commands would just hang. This is what was causing the boot hang.
  • `grep upgrade /var/log/dpkg.log` showed that kernel got upgraded from 5.10.23 to 5.10.105. (It was after this uprade that it had stopped booting.)
  • dkms reported "Module zfs/2.0.3 already built for kernel 5.10.0-odroid-arm64/4." This seems reasonable: only the patchlevel changed; this should not have necessitated rebuild of any modules.
  • Forced recompile of the zfs modules anyway, via dkms remove and dkms install.
  • Then did a zpool import. That worked! Then restored the zfs target/services and rebooted. Everything now works fine.
Glad to hear you can finally recover your storage and happy to know Live System helps. It sounds like the kernel with Live System would need an update.
So somehow rebuild of the zfs modules worked, even though that shouldn't have been necessary. I would indeed be happier with a mainline kernel/latest ZFS, and will try installing Armbian. I have a couple of questions:
  1. If it is possible to run mainline kernel, why does HardKernel maintain a private kernel? I assume it is because not all parts of the SOC are supported in mainline? If so, what support is missing in mainline?
Critical element with mainline kernel is multimedia. Other features become way better stable than years ago by the genius kernel maintainers & contributors, also Panfrost team amazing that offers better GPU features. IMO, no matter mainline kernel is supported or not, having private kernel and supporting with it is also important.

IMO many reasons:
1) It's true that new SBC support is always behind than current kernel version/release and specifically when its SOC is new. We have this issue with ODROID-M1, it works with the upstream kernel after applying patches which are not merged - fortunately many of them are already merged into the next version.
2) Many demand to use recent kernel with new features, current upstream kernel version is 6.x while official Ubuntu 22.04 kernel version is 15.x.
3) Vanilla upstream kernel has lack support for the peripherals for industry customers. It's not a device driver issue at all, just it's a bit hard to manage the kernel for their product. So private kernel for ODROID have changes to help using GPIO/SPI/I2C for their field application and adding more peripherals.
4) Some hardware features could be supported with a hack due to the lack of hardware capability or the fix is only for a specific board in certain case, this change won't be accepted by kernel maintainers.

Any of them convince me to maintain a private upstream kernel for ODROID, one could be supported by tested packages with a features/hack not in upstream kernel and one can save time to huddle the issue and maintain a kernel by oneself using tested upstream kernel. This is a service, I believe.
[*] Being able to boot into a live image was critical to rescuing my system. Is this possible via Uboot?
[/list]
If you mean to boot though the network, it's not possible with the stock U-Boot from Hardkernel since it does not support stable network access.
If you mean to boot from a SD on your HC4, I think this image could but not really since it's ISO format...not sure if U-Boot can recognize ISO image. Otherwise, the image must be converted into raw image format with regular file system types like FAT|EXT2/3/4.
http://ppa.linuxfactory.or.kr/installer ... 210331.iso

AFAIK, no SBC other than ODROID have such Live System image.

dqbydt
Posts: 69
Joined: Wed Mar 01, 2017 7:52 am
languages_spoken: English
ODROIDs: C1+ C2 C4 HC4 XU4 VU5 VU7+
Has thanked: 1 time
Been thanked: 3 times
Contact:

Re: Debian/OMV/zfs HC4 boot stuck in "Import ZFS pools"

Post by dqbydt »

Thank you for the detailed explanation. That does clarify things.
If you mean to boot though the network, it's not possible with the stock U-Boot from Hardkernel since it does not support stable network access.
No, I mean that I am considering switching to Armbian with latest mainline kernel support + latest zfs. Since this HC4 is strictly being used as a headless NAS, I can live with the mainline restrictions you mention (no multimedia/graphics/gpio/other hw support). However Armbian does not work with petitboot (I think). It needs U-boot. If I run into a similar problem in future, I would want to have the ability to boot into a live image to do system repair. Petitboot does support live image, but if U-boot does not, then I might have to hold off on switch to Armbian.
These users thanked the author dqbydt for the post:
tobetter (Thu Nov 24, 2022 3:19 pm)

igorpec
Posts: 1078
Joined: Sat Dec 12, 2015 4:34 pm
languages_spoken: bash,c++,python
Has thanked: 70 times
Been thanked: 164 times
Contact:

Re: Debian/OMV/zfs HC4 boot stuck in "Import ZFS pools"

Post by igorpec »

dqbydt wrote:
Thu Nov 24, 2022 3:10 pm
However Armbian does not work with petitboot (I think). It needs U-boot. If I run into a similar problem in future, I would want to have the ability to boot into a live image to do system repair. Petitboot does support live image, but if U-boot does not, then I might have to hold off on switch to Armbian.
If you want to rescue a system once installed to sata, you only need to download Armbian (all images are live, which you transfer to the destination or not) and boot it. To temporally boot into rescue image, you only need to press a button. If you didn't install to sata and you boot from SD card, then you only download Armbian and boot from new SD card / image. After your live system is up, install ZFS and mount the pool (and previous SD card attached to USB) and do whatever you need - rescue files, fix file system, ... And small hint - when you will go for Armbian, stick to Ubuntu variant, as it is in a bit better state then Debian based.

dqbydt
Posts: 69
Joined: Wed Mar 01, 2017 7:52 am
languages_spoken: English
ODROIDs: C1+ C2 C4 HC4 XU4 VU5 VU7+
Has thanked: 1 time
Been thanked: 3 times
Contact:

Re: Debian/OMV/zfs HC4 boot stuck in "Import ZFS pools"

Post by dqbydt »

@igorpec Thank you, that is all very clear.
And thanks for the Ubuntu hint, I would have picked Debian by default.

Post Reply

Return to “Other OS”

Who is online

Users browsing this forum: No registered users and 1 guest