Aircan Posted May 14, 2021 Posted May 14, 2021 Hi, I am using Nextcloudpi Image (Armbian) on an HC1. This setup is obviously not booting anymore after system upgrade. Packages that have been upgraded: - armbian-config - armbian-firmware - linux-buster-root-legacy-odroidxu4 - linux-dtb-legacy-odroidxu4 - linux-image-legacy-odroidxu4 - linux-u-boot-odroidxu4-legacy Insterting the µSD into an Laptop running PureOS (Debian fork) I can access log files. I could investigate so far, that there was a system upgrade (armbian-firmware_21.05.1) on 2021-05-11 6:00 am. After that a message that system will be rebooted on 2021-05-12 4:00 am. That actually happened. I can see this in several log files. BUT after that system shutdown there are no further log entries, which indicates a failes boot (in my very unprofessional opinion). Since this system is not only running NC, but also AdGuard and other stuff, it is very important to me. There is a full NC backup I weekly run, BUT not for AdGuard and other stuff. That is why I am fighting not to reflash the SD card. I can post log files or other things, that may enable you helping and investigating the issue. Thank you very much in advance. 0 Quote
cw73 Posted May 15, 2021 Posted May 15, 2021 Just out of interest, do you have a USB keyboard connected? I have upgraded a Cubieboard2 recently and it only boots the new image, when I disconnect the USB keyboard. This happens with two different keyboards. Luckily this Cubieboard2 runs no important things right now. I grabbed the logs via the serial console and I can post them, if this would be helpful. 0 Quote
Aircan Posted May 15, 2021 Author Posted May 15, 2021 vor 31 Minuten schrieb cw73: do you have a USB keyboard connected? No. There is a SSD connected via SATA and a HDD via USB. But thanks for the hint. I will disconnect HDD connected via USB and re-test again. edit: Unplugged - tested - result: Still not booting. I really think it is due to armbian upgrade, now resulting in no boot. 0 Quote
Aircan Posted May 15, 2021 Author Posted May 15, 2021 After further investigating armbian repos and docs, it might be helpful to pull you in, @Igor. Your help is highly appreciated here. Thank you very much in advance. 0 Quote
Aircan Posted May 15, 2021 Author Posted May 15, 2021 Hi @gilarelli. I stumbled upon your thread here. I might have the same problem like you had. Except I am running on Odroid HC1. System does not boot (see above) and I only do have access to the SD card via another Linux device (mounted drive). So no terminal to edit system config anyhow. Can you elaborat a bit more on your solution how to downgrade system again? Thank you very much in advance. 0 Quote
gilarelli Posted June 1, 2021 Posted June 1, 2021 (edited) Hi and sorry for the late answer - I had troubles with faulty drives in my RAID setup and thought that I lost everything and only solved this 2 weeks ago. Your system is on a sdcard? Because mine is on an eMMC, so I could boot on a sdcard. Maybe you can boot on your system with an USB pen drive (with a base OS installed on it) and access your OS on the sdcard will pluged in your board? If you can boot with another device while your sdcard is plugged in, then you've got good chances to get it back IMHO. Edit: PM me if you wish, as I'm not always on this forum and will probably miss your reply Edited June 1, 2021 by gilarelli contact information 0 Quote
marsch Posted June 3, 2021 Posted June 3, 2021 (edited) I'm having the exact same issue, cannot boot my OrangePi PC+ if any USB device is connected =( Armbian 21.05.1 and Kernel 5.10.x It does boot fine without anything connected and I can use it fine by plugging the devices after the u-boot handles the boot process to the kernel, but meh, not the expected behavior. Just wanted to report in the issue for now, since I saw the topic with the kinda exact same issue, tho still investigating and looking what has changes on the latest commits that could affect it since builds from february still boot fine, maybe u-boot v2021.04 broke something.. my u-boot keeps boot looping with the following logs.. Spoiler U-Boot SPL 2021.04-armbian (Jun 02 2021 - 19:20:10 -0700) DRAM: 1024 MiB Trying to boot from MMC1 U-Boot 2021.04-armbian (Jun 02 2021 - 19:20:10 -0700) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: XunlMMC: mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1 LoUnable to use mmc 1:1... le Err: vidconsole phy interface0 230454 bytes read in 14 ms ( starting USB... USB EHCI 1.00 Bus usb@1c1a400: Bus usb@1c1b000: USB EHCI 1.00 Bus usb@1c1b400: USB OHCI 1.0 1.00 Bus usb@1c1c400: USB OHCI 1.0 Bus usb@1c1d000: USB EHCI 1.00 Bus usb@1c1d400: USB OHCI 1.0 scanning bus usb@1c1a000 for devices... 1 USB Device(s) found scanning bus usb@1c1a400 for devices... scanning bus usb@1c1b000 for devices... scanning bus usb@1c1b400 for devices... 1 USB Device(s) found scanning bus usb@1c1c000 for devices... B Device(s) found scanning bus usb@1c1c400 for devices... 1 US1 USB Device(s) found switch to partitions Scanning mmc 0:1... Found U-Boot script /boot/boot.scr (1.9 MiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc (98.6 KiB/s10527763 bytes read in 502 ms (20 MiB/s) 20 MiB/s) Found mainline kernel configuration 32732 bytes read in 7 ms (4.5 MiB/s) KiB/s) Applying kernel provided DT fixup script (sun8i-h3-fixup.scr) ## Executing script at 45000000 ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 data abort pc : [<7dfa7d58>] lr : [<00000011>] sp : 79f6ba18 ip : 000003d0 fp : 7dff15a8 r10: 00000020 r9 : 79f73ec0 r8 : 7dffb04c r7 : 6c616972 r6 : 00000010 r5 : e6f027 0501 441d (686d) U-Boot SPL 2021.04-armbian (Jun 02 2021 - 19:20:10 -0700) U-Boot 2021.04-armbian (Jun 02 2021 - 19:20:10 -0700) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: XunlC: mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1 Loading Environment from FAT... In: serial Out: vidconsole Err: vidconsole phy interface0 230454 bytes read in 13 ms (16.9 MiB/s) Bus usb@1c1a000: USB EHCI 1.00 Bus usb@1c1a400: USB OHCI 1.0 Bus usb@1c1b000: USB EHCI 1.00 Bus usb@1c1b400: USB OHCI 1.0 Bus usb@1c1c000: Bus usb@1c1c400: USB OHCI 1.0 Bus usb@1c1d000: USB EHCI 1.00 Bus usb@1c1d400: USB OHCI 1.0 scanning bus usb@1c1a000 for devices... 1 USB Device(s) found 1 USB Device(s) found scanning bus usb@1c1b000 for devices... 1 USB Device(s) found 1 USB Device(s1 USB Device(s) found 2 USB Device(s) found 1 USB Device(s) found scanning bus usb@1c1d400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device 0:1... Found U-Boot script /boot/boot.scr (1.9 MiB/s) ## Executing script at 43100000 U-boot loaded from SD 202 bytes read in 2 ms) 20 MiB/s) 20 MiB/s) Found mainline kernel configuration 32732 bytes read in 7 ms (4.5 MiB/s) 4185 bytes read in 9 ms (454.1 KiB/s) Applying kernel provided DT fixup script (sun8i-h3-fixup.scr) ## Executing script at 45000000 ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 EHCI failed to shut down host controller. data abort pc : [<7dfa7d58>] lr : [<00000011>] reloc pc : [<4a013d58>] lr : [<cc06c011>] off Mode SVC_32 (T) Code: d005 f027 0501 441d (686d) U-Boot SPL 2021.04-armbian (Jun 02 2021 - 19:20:10 -0700) DRAM: 1024 MiB Trying to boot from MMC1 Moading Environment from FAT... In: serial Out: vidconsole Err: vidconsole Net: phy interface0 eth0: ethernet@1c30000 230454 bytes read in 13 ms (16starting USB... Bus usb@1c1a000: USB EHCI 1.00 Bus usb@1c1a400: USB OHCI 1.0 Bus usb@1c1b000: USB EHCI 1.00 Bus usb@1c1b400: USB OHCI 1.0 Bus usb@1c1c000: USB EHCI 1.00 Bus usb@1c1c400: USB OHCI 1.0 USB EHCI 1.00 Bus usb@1c1d400: ing bus usb@1c1a000 for devices... 1 USB Device(s) found 1 USB Device(s) found scanning bus usb@1c1b000 for devices... 1 USB Device(s) found scanning bus usb@1c1b400 for devices... 1 USB Device(s) found scanning bus usb@1c1c000 for devices... scanning bus usb@1c1c400 for devices... scanning bus usb@1c1d000 for devices... 1 USB Device(s) found scanning bus usb@1c1d400 for devices... 1 USB Device(s) found switch to paScanning mmcFound U-Boot 3964 bytes read in 2 ms) ## Executing script at 43100000 Boot script loaded from mmc (98.6 KiB/s) 20 MiB/s) 20 MiB/s) Found mainline kernel configuration32732 bytes read in 7 ms (44185 bytes read in 8 ms (510.7Applying kernel provided DT fixup script (sun8i-h3-fixup.scr) ## Executing script at 45000000 Image Name: uInitrd Image Type: 10527699 Bytes = 10 MiB Verifying Checksum ... ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 data abort pc : [<7dfa7d58>] lr : [<00000011>] reloc pc : [<4a013d58>] lr : [<cc06c011>] ff Mode SVC_32 (T) Code: d005 f027 0501 441d (686d) DRAM: 1024 MiB Trying to boot from MMC1 U-Boot 2021.04-armbian (Jun 02 2021 - 19:20:10 -0700) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunl Loading Environment from FAT... In: serial Out: vidconsole Err: vidconsole phy interface0 .9 MiB/s) Bus usb@1c1a000: USB EHCI 1.00 Bus usb@1c1a400: USB EHCI 1.00 Bus usb@1c1b400: USB OHCI 1.0 Bus usb@1c1c000: USB EHCI 1.00 Bus usb@1c1c400: USB OHCI 1.0 Bus usb@1c1d000: USB OHCI 1.0 scanning bus usb@1c1a000 for devices... 1 USB Device(s) found scanning bus usb@1c1a400 for devices... Edited June 3, 2021 by marsch added u-boot log 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.