Flolm Posted September 14, 2021 Posted September 14, 2021 (edited) Hello, I have tried the procedure described on this topic (https://forum.armbian.com/topic/15431-helios64-support/page/9/) but it doesn't work for me. armbian is installed on an SSD, I have no micro SD card in my Helios64. Today, i can no longer start armbian :/ This is what the serial console shows me: Reveal hidden contents DDR Version 1.24 20191016 In channel 0 CS = 0 MR0=0x18 MR4=0x2 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x18 MR4=0x2 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! change freq to 416MHz 0,1 Channel 0: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB Channel 1: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB 256B stride channel 0 CS = 0 MR0=0x18 MR4=0x2 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x18 MR4=0x2 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! channel 0, cs 0, advanced training done channel 1, cs 0, advanced training done change freq to 856MHz 1,0 ch 0 ddrconfig = 0x101, ddrsize = 0x40 ch 1 ddrconfig = 0x101, ddrsize = 0x40 pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD ddr_set_rate to 328MHZ ddr_set_rate to 666MHZ ddr_set_rate to 928MHZ channel 0, cs 0, advanced training done channel 1, cs 0, advanced training done ddr_set_rate to 416MHZ, ctl_index 0 ddr_set_rate to 856MHZ, ctl_index 1 support 416 856 328 666 928 MHz, current 856MHz OUT Boot1: 2019-03-14, version: 1.19 CPUId = 0x0 ChipType = 0x10, 253 SdmmcInit=2 0 BootCapSize=100000 UserCapSize=14910MB FwPartOffset=2000 , 100000 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 SdmmcInit=0 1 StorageInit ok = 67875 SecureMode = 0 SecureInit read PBA: 0x4 SecureInit read PBA: 0x404 SecureInit read PBA: 0x804 SecureInit read PBA: 0xc04 SecureInit read PBA: 0x1004 SecureInit read PBA: 0x1404 SecureInit read PBA: 0x1804 SecureInit read PBA: 0x1c04 SecureInit ret = 0, SecureMode = 0 atags_set_bootdev: ret:(0) GPT 0x3380ec0 signature is wrong recovery gpt... GPT 0x3380ec0 signature is wrong recovery gpt fail! LoadTrust Addr:0x4000 No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x200000, size=0xe5b60 RunBL31 0x40000 NOTICE: BL31: v1.3(debug):42583b6 NOTICE: BL31: Built : 07:55:13, Oct 15 2019 NOTICE: BL31: Rockchip release version: v1.1 INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3 INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: plat_rockchip_pmu_init(1190): pd status 3e INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2020.10-armbian (Mar 08 2021 - 14:54:58 +0000) SoC: Rockchip rk3399 Reset cause: POR DRAM: 3.9 GiB PMIC: RK808 SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB MMC: mmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from MMC... *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Model: Helios64 Revision: 1.2 - 4GB non ECC Net: eth0: ethernet@fe300000 scanning bus for devices... starting USB... Bus usb@fe380000: USB EHCI 1.00 Bus dwc3: usb maximum-speed not found Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus usb@fe380000 for devices... 1 USB Device(s) found scanning bus dwc3 for devices... cannot reset port 4!? 4 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 Card did not respond to voltage select! switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3185 bytes read in 17 ms (182.6 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 0 166 bytes read in 13 ms (11.7 KiB/s) Failed to load '/boot/uInitrd' Failed to load '/boot/Image' 81924 bytes read in 42 ms (1.9 MiB/s) 2698 bytes read in 32 ms (82 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 09000000 Bad Linux ARM64 Image magic! SCRIPT FAILED: continuing... Device 0: unknown device scanning bus for devices... Device 0: unknown device ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@fe300000 missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/01-64-62-66-d0-08-ea ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@fe300000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000000 ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@fe300000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000000 ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@fe300000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/000000 ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@fe300000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000 ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@fe300000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000 ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@fe300000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/000 ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@fe300000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/00 ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@fe300000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/0 ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@fe300000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-rk3399-helios64 ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@fe300000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-rk3399 ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@fe300000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@fe300000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/default ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@fe300000 Config file not found ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@fe300000 ethernet@fe300000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@fe300000 => Can you help me please ? i have a pretty complex setup and i wouldn't want to reinstall everything. Thank you, Flolm Edited September 14, 2021 by Flolm 0 Quote
ebin-dev Posted September 15, 2021 Posted September 15, 2021 Hi @Flolm, what you could do to rescue your system on emmc is to boot from sd (i.e. using a fresh Armbian Buster) and reinstall linux on emmc from there (using chroot as described here). You also need to check whether the UUIDs are set correctly in /mnt/system/etc/fstab and /mnt/system/boot/armbianEnv.txt (assuming that your emmc is mounted to /mnt/system). Good luck! P.S.: in any case you should maintain a backup of your emmc (on sd). 0 Quote
Flolm Posted September 16, 2021 Author Posted September 16, 2021 Hi @ebin-dev, Thank you for your quick reply. Unfortunately, my system is not installed on emmc storage but on an SSD drive (slot 1). Is the procedure much the same? Which armbian Buster version should I boot from the SD card? If I understood correctly: boot on the sd card (with Jumper 10?) / Reinstall the system on emmc storage. Then how can I get my SSD to be the system again? I wouldn't want to break everything ... Thank you so much Flolm 0 Quote
ebin-dev Posted September 16, 2021 Posted September 16, 2021 On 9/16/2021 at 7:29 AM, Flolm said: Then how can I get my SSD to be the system again? Expand If you could boot from SD - the current Buster image should be fine - mount your ssd, replace linux on ssd (same procedure), and check the UUIDs at the two locations hopwfully solves the problem. 0 Quote
Flolm Posted September 16, 2021 Author Posted September 16, 2021 Hello, I started on a clean armbian buster image but the problem is that I can not already see my SSD drive where the broken system is located... My ssd has ~120 Gb of storage normally but I can't see it. I only see my 4 hard drives mounted in RAID10 and the SD Card ~30 Gb fdisk -l : 0 Quote
Werner Posted September 16, 2021 Posted September 16, 2021 Did you check wiring of the SSD? Did you test the SSD on a different system for functionality? 0 Quote
Flolm Posted September 16, 2021 Author Posted September 16, 2021 Yes my SSD is working fine until armbian update. He has not moved from his slot in helios64. So I don't understand why I can't see it ... 0 Quote
Flolm Posted September 17, 2021 Author Posted September 17, 2021 I think I will have to completely rebuild my server :/ All because of a simple update via armbian-config ... First of all, I must be able to recover all my data from my RAID10, I hope to be able to succeed ... Then, if I start from scratch, can I take the last armbian image for Helios64? (i.e) Armbian_21.05.9_Helios64_bullseye_current_5.10.63.img.xz or is it recommended to stay on the image: Armbian_21.05.9_Helios64_buster_current_5.10.63.img.xz sources: https://mirrors.netix.net/armbian/dl/helios64/archive/ Thank you 0 Quote
Werner Posted September 17, 2021 Posted September 17, 2021 Both sharing the same very same kernel package so firmware is identical. I would go for bullseye since this is the most recent stable Debian release. 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.