belegdol

I will try downgrading u-boot next once I find the older package somewhere. Kernel does not seem to be the cause given that it has been working fine with both my own build 6.6.122 and 6.6.128 before and rolling back not helping. New device is something I had on my mind for a while. But given the RAM and SSD prices these days, I do not really want to overspend. Not to mention that the SBC landscape has not been that great lately when it comes to compact NAS offerings. HC4 is five years old at this point. Many even recommend N100 but this is a whole different size category.

This could be, but something has changed and is now triggering this behaviour. Warm reboots have been working fine for years.

Other packages upgraded by unattended-upgrades: Start-Date: 2026-03-15 10:51:39 Commandline: apt upgrade Requested-By: julas (1000) Upgrade: linux-base:armhf (4.12~bpo12+1, 4.12.1~bpo12+1) End-Date: 2026-03-15 10:51:51 Start-Date: 2026-03-16 06:20:00 Commandline: /usr/bin/unattended-upgrade Upgrade: linux-image-current-odroidxu4:armhf (25.11.2.3, 26.2.1) End-Date: 2026-03-16 06:21:56 Start-Date: 2026-03-16 06:22:47 Commandline: /usr/bin/unattended-upgrade Upgrade: base-files:armhf (25.11.2-12.4+deb12u12-bookworm, 26.2.1-12.4+deb12u13-bookworm), armbian-bsp-cli-odroidxu4-current:armhf (25.11.2, 26.2.1) End-Date: 2026-03-16 06:23:48 Start-Date: 2026-03-16 06:24:54 Commandline: /usr/bin/unattended-upgrade Upgrade: armbian-firmware:armhf (25.11.2, 26.2.1) End-Date: 2026-03-16 06:26:03 Start-Date: 2026-03-16 06:26:48 Commandline: /usr/bin/unattended-upgrade Upgrade: linux-dtb-current-odroidxu4:armhf (25.11.2.3, 26.2.1) End-Date: 2026-03-16 06:26:52 Start-Date: 2026-03-16 06:27:35 Commandline: /usr/bin/unattended-upgrade Upgrade: linux-u-boot-odroidxu4-current:armhf (25.11.2, 26.2.1) End-Date: 2026-03-16 06:27:37 Unfortunately, the previous versions seem to be gone from the repos. Is there any way of getting these back?

Rolling "back" linux-{dtb,image}-current to my self-built 6.6.128 did not help.

I was able to see the data on the drive just fine when connected to another machine via eSATA cable. Oddly enough, the partition showed back up again after reattaching it to the odroid and starting it again. I have then rebooted the odroid again, and the partition went away once again. So it appears to be some sort of cold vs warm boot difference.

Hello, I have updated my Odroid HC1 to 26.2.1 - just the kernel, u-boot and such. I have been running a self-built 6.6.128 prior so kernel version itself is unlikely the issue. After rebooting, my SATA drive seems dead - no partitions are detected, only the main sda device. This is what the journal said before: Mar 05 15:51:31 kernel: usb 4-1: new SuperSpeed USB device number 2 using xhci-hcd Mar 05 15:51:31 kernel: usb 4-1: New USB device found, idVendor=152d, idProduct=0578, bcdDevice=31.02 Mar 05 15:51:31 kernel: usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 05 15:51:31 kernel: usb 4-1: Product: USB to ATA/ATAPI Bridge Mar 05 15:51:31 kernel: usb 4-1: Manufacturer: JMicron Mar 05 15:51:31 kernel: usb 4-1: SerialNumber: 0123456789ABCDEF Mar 05 15:51:31 kernel: SCSI subsystem initialized Mar 05 15:51:31 kernel: usbcore: registered new interface driver usb-storage Mar 05 15:51:31 kernel: scsi host0: uas Mar 05 15:51:31 kernel: usbcore: registered new interface driver uas Mar 05 15:51:31 kernel: scsi 0:0:0:0: Direct-Access JMicron Generic 3102 PQ: 0 ANSI: 6 Mar 05 15:51:31 kernel: sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB) Mar 05 15:51:31 kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks Mar 05 15:51:31 kernel: sd 0:0:0:0: [sda] Write Protect is off Mar 05 15:51:31 kernel: sd 0:0:0:0: [sda] Mode Sense: 53 00 00 08 Mar 05 15:51:31 kernel: sd 0:0:0:0: [sda] Disabling FUA Mar 05 15:51:31 kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 05 15:51:31 kernel: sd 0:0:0:0: [sda] Preferred minimum I/O size 4096 bytes Mar 05 15:51:31 kernel: sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes) Mar 05 15:51:31 kernel: sda: sda1 Mar 05 15:51:31 kernel: sd 0:0:0:0: [sda] Attached SCSI disk This is what it says now: Mar 19 09:36:34 kernel: usb 4-1: New USB device found, idVendor=152d, idProduct=0578, bcdDevice=31.02 Mar 19 09:36:34 kernel: usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 19 09:36:34 kernel: usb 4-1: Product: USB to ATA/ATAPI Bridge Mar 19 09:36:34 kernel: usb 4-1: Manufacturer: JMicron Mar 19 09:36:34 kernel: usb 4-1: SerialNumber: 0123456789ABCDEF Mar 19 09:36:34 kernel: SCSI subsystem initialized Mar 19 09:36:34 kernel: usbcore: registered new interface driver usb-storage Mar 19 09:36:34 kernel: scsi host0: uas Mar 19 09:36:34 kernel: usbcore: registered new interface driver uas Mar 19 09:36:34 kernel: scsi 0:0:0:0: Direct-Access JMicron Generic 3102 PQ: 0 ANSI: 6 Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] Unit Not Ready Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] Sense Key : 0x4 [current] Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81 Mar 19 09:36:34 kernel: r8152-cfgselector 6-1: reset SuperSpeed USB device number 2 using xhci-hcd Mar 19 09:36:34 kernel: r8152 6-1:1.0: load rtl8153a-3 v2 02/07/20 successfully Mar 19 09:36:34 kernel: r8152 6-1:1.0 eth0: v1.12.13 Mar 19 09:36:34 kernel: r8152-cfgselector 6-1: reset SuperSpeed USB device number 2 using xhci-hcd Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=0x07 driverbyte=DRIVER_OK Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] Sense Key : 0x4 [current] Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81 Mar 19 09:36:34 kernel: r8152 6-1:1.0: load rtl8153a-3 v2 02/07/20 successfully Mar 19 09:36:34 kernel: r8152 6-1:1.0 eth0: v1.12.13 Mar 19 09:36:34 kernel: r8152 6-1:1.0 enx001e06326076: renamed from eth0 Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=0x07 driverbyte=DRIVER_OK Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] Sense Key : 0x4 [current] Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81 Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 B) Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] 0-byte physical blocks Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] Test WP failed, assume Write Enabled Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] Asking for cache data failed Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] Preferred minimum I/O size 4096 bytes not a multiple of physical block size (0 bytes) Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of physical block size (0 bytes) Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] Attached SCSI disk I will try attaching the drive to another PC to exclude a poorly timed hardware failure.

Nicely done 👍 I remember dealing with similar problems when I upgraded my desktop to an nvme drive. I transferred the partition to the new drive but the OS would not boot from it due to nvme modules being missing.

What does lsinitramfs say? Is the usb_storage in? This is how it looks here: $ lsinitramfs /boot/initrd.img-6.6.108-current-odroidxu4 | grep usb usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/hid/usbhid usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/hid/usbhid/usbhid.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/i2c/busses/i2c-tiny-usb.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/aqc111.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/asix.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/ax88179_178a.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/catc.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/cdc_eem.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/cdc_ncm.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/ch9200.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/dm9601.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/int51x1.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/kaweth.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/lan78xx.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/mcs7830.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/pegasus.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/rndis_host.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/rtl8150.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/smsc75xx.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/smsc95xx.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/sr9700.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/sr9800.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/host usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/host/ehci-fsl.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/host/fsl-mph-dr-of.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/uas.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/ums-alauda.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/ums-cypress.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/ums-datafab.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/ums-eneub6250.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/ums-freecom.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/ums-isd200.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/ums-jumpshot.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/ums-karma.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/ums-onetouch.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/ums-realtek.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/ums-sddr09.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/ums-sddr55.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/ums-usbat.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/usb-storage.ko usr/lib/systemd/network/73-usb-net-by-mac.link usr/lib/udev/rules.d/50-usb-realtek-net.rules

Please forgive me if it is a stupid question, but what is preventing us from keeping n previous kernels installed in case an update is broken and does not boot? Fedora does it, Ubuntu does too. In general it should be simpler to boot a previous kernel than to try to pull the SD card and fix it in a second machine.

If you are able to read the panicking SD card in another PC, how does the folder structure look like? This is mine: $ sudo ls -Rlh /boot [sudo] password for julas: /boot: total 36M -rw-r--r-- 1 root root 78 Feb 6 13:26 armbianEnv.txt -rw-r--r-- 1 root root 0 Sep 6 2019 armbianEnv.txt.out -rw-r--r-- 1 root root 1.5K May 29 2018 armbian_first_run.txt.template -rw-r--r-- 1 root root 38K May 29 2018 boot.bmp -rw-r--r-- 1 root root 4.8K May 29 2018 boot-desktop.png -rw-r--r-- 1 root root 13K Sep 15 2022 boot.ini -rw-r--r-- 1 root root 0 Jun 25 2019 boot.ini.out -rw-r--r-- 1 root root 200K Feb 6 13:11 config-6.6.75-current-odroidxu4 lrwxrwxrwx 1 root root 28 Feb 6 13:24 dtb -> dtb-6.6.75-current-odroidxu4 drwxr-xr-x 2 root root 4.0K Feb 6 13:23 dtb-6.6.75-current-odroidxu4 -rw-r--r-- 1 root root 13M Feb 6 13:24 initrd.img-6.6.75-current-odroidxu4 drwx------ 2 root root 12K May 29 2018 lost+found -rw-r--r-- 1 root root 3.2M Feb 6 13:11 System.map-6.6.75-current-odroidxu4 lrwxrwxrwx 1 root root 32 Feb 6 13:24 uInitrd -> uInitrd-6.6.75-current-odroidxu4 -rw-r--r-- 1 root root 13M Feb 6 13:24 uInitrd-6.6.75-current-odroidxu4 -rw-r--r-- 1 root root 8.4M Feb 6 13:11 vmlinuz-6.6.75-current-odroidxu4 lrwxrwxrwx 1 root root 32 Feb 6 13:24 zImage -> vmlinuz-6.6.75-current-odroidxu4 /boot/dtb-6.6.75-current-odroidxu4: total 3.1M -rw-r--r-- 1 root root 1.7K Feb 6 13:11 ads7846.dtbo -rw-r--r-- 1 root root 42K Feb 6 13:11 exynos3250-artik5-eval.dtb -rw-r--r-- 1 root root 52K Feb 6 13:11 exynos3250-monk.dtb -rw-r--r-- 1 root root 59K Feb 6 13:11 exynos3250-rinato.dtb -rw-r--r-- 1 root root 69K Feb 6 13:11 exynos4210-i9100.dtb -rw-r--r-- 1 root root 60K Feb 6 13:11 exynos4210-origen.dtb -rw-r--r-- 1 root root 57K Feb 6 13:11 exynos4210-smdkv310.dtb -rw-r--r-- 1 root root 64K Feb 6 13:11 exynos4210-trats.dtb -rw-r--r-- 1 root root 65K Feb 6 13:11 exynos4210-universal_c210.dtb -rw-r--r-- 1 root root 98K Feb 6 13:11 exynos4212-tab3-3g8.dtb -rw-r--r-- 1 root root 98K Feb 6 13:11 exynos4212-tab3-lte8.dtb -rw-r--r-- 1 root root 99K Feb 6 13:11 exynos4212-tab3-wifi8.dtb -rw-r--r-- 1 root root 106K Feb 6 13:11 exynos4412-i9300.dtb -rw-r--r-- 1 root root 106K Feb 6 13:11 exynos4412-i9305.dtb -rw-r--r-- 1 root root 75K Feb 6 13:11 exynos4412-itop-elite.dtb -rw-r--r-- 1 root root 103K Feb 6 13:11 exynos4412-n710x.dtb -rw-r--r-- 1 root root 74K Feb 6 13:11 exynos4412-odroidu3.dtb -rw-r--r-- 1 root root 74K Feb 6 13:11 exynos4412-odroidx2.dtb -rw-r--r-- 1 root root 74K Feb 6 13:11 exynos4412-odroidx.dtb -rw-r--r-- 1 root root 73K Feb 6 13:11 exynos4412-origen.dtb -rw-r--r-- 1 root root 98K Feb 6 13:11 exynos4412-p4note-n8010.dtb -rw-r--r-- 1 root root 65K Feb 6 13:11 exynos4412-smdk4412.dtb -rw-r--r-- 1 root root 64K Feb 6 13:11 exynos4412-tiny4412.dtb -rw-r--r-- 1 root root 106K Feb 6 13:11 exynos4412-trats2.dtb -rw-r--r-- 1 root root 63K Feb 6 13:11 exynos5250-arndale.dtb -rw-r--r-- 1 root root 59K Feb 6 13:11 exynos5250-smdk5250.dtb -rw-r--r-- 1 root root 65K Feb 6 13:11 exynos5250-snow.dtb -rw-r--r-- 1 root root 65K Feb 6 13:11 exynos5250-snow-rev5.dtb -rw-r--r-- 1 root root 61K Feb 6 13:11 exynos5250-spring.dtb -rw-r--r-- 1 root root 27K Feb 6 13:11 exynos5260-xyref5260.dtb -rw-r--r-- 1 root root 45K Feb 6 13:11 exynos5410-odroidxu.dtb -rw-r--r-- 1 root root 35K Feb 6 13:11 exynos5410-smdk5410.dtb -rw-r--r-- 1 root root 74K Feb 6 13:11 exynos5420-arndale-octa.dtb -rw-r--r-- 1 root root 73K Feb 6 13:11 exynos5420-chagall-wifi.dtb -rw-r--r-- 1 root root 73K Feb 6 13:11 exynos5420-klimt-wifi.dtb -rw-r--r-- 1 root root 83K Feb 6 13:11 exynos5420-peach-pit.dtb -rw-r--r-- 1 root root 69K Feb 6 13:11 exynos5420-smdk5420.dtb -rw-r--r-- 1 root root 82K Feb 6 13:11 exynos5422-odroidhc1.dtb -rw-r--r-- 1 root root 89K Feb 6 13:11 exynos5422-odroidxu3.dtb -rw-r--r-- 1 root root 88K Feb 6 13:11 exynos5422-odroidxu3-lite.dtb -rw-r--r-- 1 root root 88K Feb 6 13:11 exynos5422-odroidxu4.dtb -rw-r--r-- 1 root root 74K Feb 6 13:11 exynos5422-samsung-k3g.dtb -rw-r--r-- 1 root root 84K Feb 6 13:11 exynos5800-peach-pi.dtb -rw-r--r-- 1 root root 1.3K Feb 6 13:11 hktft32.dtbo -rw-r--r-- 1 root root 1.8K Feb 6 13:11 hktft35.dtbo -rw-r--r-- 1 root root 1.5K Feb 6 13:11 hktft-cs-ogst.dtbo -rw-r--r-- 1 root root 224 Feb 6 13:11 i2c0.dtbo -rw-r--r-- 1 root root 226 Feb 6 13:11 i2c1.dtbo -rw-r--r-- 1 root root 417 Feb 6 13:11 onewire.dtbo -rw-r--r-- 1 root root 691 Feb 6 13:11 spi0.dtbo -rw-r--r-- 1 root root 792 Feb 6 13:11 sx865x-i2c1.dtbo -rw-r--r-- 1 root root 227 Feb 6 13:11 uart0.dtbo /boot/lost+found: total 0

Comparing the two UART logs provided by @Davy, log containing ** File not found /boot/armbianEnv.txt ** ** Unrecognized filesystem type ** ** File not found armbianEnv.txt ** does boot, whereas log not containing these 3 lines ends with a kernel panic. Not sure whether this is relevant yet, but it is definitely interesting.

@Igor, is it possible to compare the kernel configurations used for the official build vs what I have running?

Are you guys able to check which of the packages is causing trouble specifically?

For comparison purposes, the hash values for my working build are: linux-image-current-odroidxu4_24.11.1.2_armhf__1-S1b53-D0531-P3da6-C3a73H5845-HK01ba-V014b-B59f0-R448a.deb. I could upload my builds somewhere for testing purposes, but I am not sure if it won't be setting a bad example wrt. not downloading builds from random strangers on the internet.

Apologies for the trouble. I will try to have a look over the next few days. In the meantime, @Davy, are you able to post UART logs for the working boot? I somehow recall the boot.ini message is always there. It is also possible to mount the SD card on a PC, this is how I recovered from a broken update once or twice. I am running a self-compiled 6.6.75 on my HC1 at this very moment so this issue is definitely curious.