ceri Posted April 1 Posted April 1 When the ODROID-M1 is setup to boot from SPI with the system installed on a M2 ssd, power loss seems to lead to an unbootable system. Once an SD card with armbian is inserted and the system is booted through the recovery button once, logged in* and then shutdown normally, the system boots again from SPI. * Without login and regular shutdown of the system booted from sd card, the issue remains I have observed and reproduced this issue several times in the last year. In my case the M1 is connected to a power strip that turns on and off the multiple devices. When I forget to unplug the M1 and it gets turned on and off several times over a day or more, the issue appears. When I turn it of manually I could not yet observe the issue, so it may be related to being booted and turned off multiple times in short order. When I investigate the journal of the last boot circles, there is nothing there, as if the boot process never started, leaving me to suspect an issue with the bootloader in combination with SPI and power loss. 0 Quote
Werner Posted April 2 Posted April 2 8 hours ago, ceri said: unbootable This error description leads nowhere. Hook up a debug serial console to get an idea what happens inside while the system does not boot. Share the logs here. Also verify powering and wiring. https://debug.armbian.de 0 Quote
ceri Posted April 2 Author Posted April 2 (edited) I was hoping that the description would make it easy to reproduce to find the issue. If that's not the case I can try to find the required cable somewhere nearby to give it a try myself. Update: Any recommendations where to get a UART adapter in germany when amazon is to be avoided? Even conrad does not have any listed that I can find Edited April 2 by ceri 0 Quote
ceri Posted 2 hours ago Author Posted 2 hours ago (edited) Finally got around to debug this: Previously I had the system on an nvme drive and the bootloader on spi After reinstalling the system and bootloader both on mmc flash, I eventually ran into the very same issue. According to the logs, the boot bails with the following error: Log1: Quote Scanning for bootflows in all bootdevs Seq Method State Uclass Part Name Filename --- ----------- ------ -------- ---- ------------------------ ---------------- Scanning global bootmeth 'efi_mgr': 7[r[999;999H[6n8Card did not respond to voltage select! : -110 Cannot persist EFI variables without system partition 0 efi_mgr ready (none) 0 <NULL> ** Booting bootflow '<NULL>' with efi_mgr Loading Boot0000 'mmc 0' failed EFI boot manager: Cannot load any image Boot failed (err=-14) Scanning bootdev 'mmc@fe2b0000.bootdev': Card did not respond to voltage select! : -110 ** fs_devread read error - block Scanning bootdev 'nvme#0.blk#1.bootdev': \00\00 When I remove the nvme drive, the boot process works just fine for some reason: (boot log after nvme removal) Log2: Quote Scanning for bootflows in all bootdevs Seq Method State Uclass Part Name Filename ---- ------ -------- ---- ------------------------ ---------------- Scanning global bootmeth 'efi_mgr': 7[r[999;999H[6n8Card did not respond to voltage select! : -110 Cannot persist EFI variables without system partition 0 efi_mgr ready (none) 0 <NULL> ** Booting bootflow '<NULL>' with efi_mgr Loading Boot0000 'mmc 0' failed EFI boot manager: Cannot load any image Boot failed (err=-14) Scanning bootdev 'mmc@fe2b0000.bootdev': Card did not respond to voltage select! : -110 pcie_dw_rockchip pcie@fe280000: PCIe-0 Link Fail pcie_dw_rockchip pcie@fe280000: PCIe-0 Link Fail scanning bus for devices... SATA link 0 timeout. AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode flags: ncq stag pm led clo only pmp fbss pio slum part ccc apst Bus usb@fd000000: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 Bus usb@fd800000: USB EHCI 1.00 Bus usb@fd840000: USB OHCI 1.0 Bus usb@fd880000: USB EHCI 1.00 Bus usb@fd8c0000: USB OHCI 1.0 scanning bus usb@fd000000 for devices... 1 USB Device(s) found scanning bus usb@fd800000 for devices... 1 USB Device(s) found scanning bus usb@fd840000 for devices... 2 USB Device(s) found scanning bus usb@fd880000 for devices... 1 USB Device(s) found scanning bus usb@fd8c0000 for devices... 2 USB Device(s) found Scanning bootdev 'mmc@fe310000.bootdev': 1 script ready mmc 1 mmc@fe310000.bootdev.part /boot/boot.scr ** Booting bootflow 'mmc@fe310000.bootdev.part_1' with script Boot script loaded from mmc 0:1 246 bytes read in 11 ms (21.5 KiB/s) 16644645 bytes read in 110 ms (144.3 MiB/s) 37874176 bytes read in 230 ms (157 MiB/s) 121646 bytes read in 35 ms (3.3 MiB/s) Working FDT set to 12000000 Trying kaslrseed command... Info: Unknown command can be safely ignored since kaslrseed does not apply to all boards. Unknown command 'kaslrseed' - try 'help' ## Loading init Ramdisk from Legacy Image at 12180000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 16644581 Bytes = 15.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 12000000 Booting using the fdt blob at 0x12000000 Working FDT set to 12000000 Loading Ramdisk to ebe9a000, end ece799e5 ... OK Loading Device Tree to 00000000ebe13000, end 00000000ebe99fff ... OK Working FDT set to ebe13000 Starting kernel ... When I reinstall the nvme, the boot fails again. However, booting from sd-card (using recovery button) and reflashing the bootloader to the mmc fixes the issue as well with the same result as removing the nvme drive had, resulting in the same log2 as above. I had fixed the issue before by reflashing the bootloader to spi but just like yesterday, it eventually stopped booting again until I reflashed the boot loader. There isn't anything particular happening before this occurs, though the last few times it was always after the system had run for some time. After cutting power (without shutdown) and booting it again after a few minutes, the issue would appear. (The device is always cut from power instead of shutting it down, but there was never an error on any drive due to that). The issue also did not show when the device was just turned of (without power) for a day or two. It seems to trigger quite randomly. I already tried to erase the spi flash to avoid any old entries messing up the boot order but without effect. Any clue what I could try next? Edited 2 hours ago by ceri 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.