Rock64 bricked after upgrade

[jean_bruder]

Dear all,

First of all, a big thank to the PINE64 Team for that really good board. I have 2 at home and I am very happy to use them !

Some days ago, I did the standard update I do all the weeks, and noticed new kernel release. I did my upgrade as usual using the "apt update", "apt upgrade" and finally "apt-dist-upgrade" command. But, the board did not boot ... Please find below the boot log of the latest kernel installed on the board :

Code:

DDR version 1.13 20180428 ID:0x805 N In LPDDR3 786MHz Bus Width=32 Col=11 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=4096MB ddrconfig:7 OUT Boot1 Release Time: Feb  2 2018 15:41:39, version: 2.46 ChipType = 0x11, 144 SdmmcInit=2 0 BootCapSize=0 UserCapSize=0MB FwPartOffset=2000 , 0 SdmmcInit=0 0 BootCapSize=0 UserCapSize=30528MB FwPartOffset=2000 , 0 StorageInit ok = 22736 Raw SecureMode = 0 SecureInit read PBA: 0x4 SecureInit read PBA: 0x404 SecureInit read PBA: 0x804 SecureInit read PBA: 0xc04 SecureInit read PBA: 0x1004 SecureInit ret = 0, SecureMode = 0 LoadTrustBL No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x200000, size=0xa445c RunBL31 0x10000
NOTICE:  BL31: v1.3(debug):f947c7e NOTICE:  BL31: Built : 21:14:39, Oct 31 2019 NOTICE:  BL31:Rockchip release version: v1.3 INFO:    ARM GICv2 driver initialized INFO:    Using rkfiq sec cpu_context! INFO:    boot cpu mask: 1 INFO:    plat_rockchip_pmu_init: pd status 0xe INFO:    BL31: Initializing runtime services INFO:    BL31: Preparing for EL3 exit to normal world INFO:    Entry point address = 0x200000 INFO:    SPSR = 0x3c9 U-Boot 2017.09-armbian (Nov 19 2019 - 00:12:37 +0100) Model: Pine64 Rock64 DRAM:  4 GiB MMC:   rksdmmc@ff520000: 0, rksdmmc@ff500000: 1 SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB *** Warning - bad CRC, using default environment In:    serial@ff130000 Out:   serial@ff130000 Err:   serial@ff130000 Model: Pine64 Rock64 misc_init_r cpuid=55524b503039303237000000000e1604 serial=87599d5955ac491 boot mode 0. Net:   eth0: ethernet@ff540000 Hit any key to stop autoboot:  0 Card did not respond to voltage select! mmc_init: -95, time 10 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 2940 bytes read in 43 ms (66.4 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 102 bytes read in 38 ms (2 KiB/s) 7134106 bytes read in 388 ms (17.5 MiB/s) 20722176 bytes read in 996 ms (19.8 MiB/s) 51040 bytes read in 67 ms (743.2 KiB/s) 2698 bytes read in 101 ms (25.4 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 39000000 ## Loading init Ramdisk from Legacy Image at 04000000 ...   Image Name:   uInitrd   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)   Data Size:    7134042 Bytes = 6.8 MiB   Load Address: 00000000   Entry Point:  00000000   Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000   Booting using the fdt blob at 0x1f00000   Loading Ramdisk to fc834000, end fcf01b5a ... OK   reserving fdt memory region: addr=1f00000 size=72000   Loading Device Tree to 00000000fc7bf000, end 00000000fc833fff ... OK Starting kernel ...

And nothing more ...

Can someone please help me to solve this issue without having to reinstall the system, as it hosts my NextCloud home server ?

Many thanks in advance,
Best regards,
Jean

[tophneal]

Obviously it's Debian-based, but it'll be helpful to tell us what OS you're using. There's several options for the Rock64.

[jean_bruder]

Obviously it's Debian-based, but it'll be helpful to tell us what OS you're using. There's several options for the Rock64.

Dear @tophneal,

Here's the content of the "/etc/arbian-image-release" :

Code:

  # PLEASE DO NOT EDIT THIS FILE BOARD=rock64 BOARD_NAME="ROCK64" BOARDFAMILY=rockchip64 BUILD_REPOSITORY_URL=https://github.com/armbian/build BUILD_REPOSITORY_COMMIT=64f00e82-dirty VERSION=5.91 LINUXFAMILY=rockchip64 BRANCH=default ARCH=arm64 IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image IMAGE_UUID=9c0c1b69-3833-446b-8b2c-fae7a1ceef1c

Content of the "/etc/debian_version" file :

Code:

10.3

I hope this will help 


I tryied to chroot to the SD Card in order to install a debian kernel package I downloaded from the apt.raspbian.com repository, but from my Linux Mint laptop, this seems to be not working because of the different architecture ?

Regards,
Jean

[tophneal]

Looking through a few similar issues on the Armbian forums, a good first step might be to run fsck on the SD. You might also try using armbian-config in chroot to downgrade your kernel.

[jean_bruder]

Looking through a few similar issues on the Armbian forums, a good first step might be to run fsck on the SD. You might also try using armbian-config in chroot to downgrade your kernel.

Dear @tophneal,

Checking the SD Card show no error on the card   

I followed the link https://askubuntu.com/questions/28099/ho...ll-kernels in order to downgrade the kernel, but got the following error while chrooting :

Code:

jean@Astux:~$ sudo chroot /mnt/SDCard/ chroot: impossible d'exécuter la commande « /bin/bash »: Erreur de format pour exec()

 
This seems to be induced by different binary formats :

Code:

jean@Astux:~$ file /mnt/SDCard/bin/bash /mnt/SDCard/bin/bash: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-, for GNU/Linux 3.7.0, BuildID[sha1]=b11533bde88bb45ef2891fbf3ad86c1869ed3a41, stripped jean@Astux:~$ file /bin/bash /bin/bash: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/l, for GNU/Linux 3.2.0, BuildID[sha1]=12f73d7a8e226c663034529c8dd20efec22dde54, stripped

Is there something I can do so far ? 

Regards,
Jean

[tophneal]

Try pointing to where /bin/bash is on your SD, for example chroot /mnt/SDCard /usr/bin/bash

[jean_bruder]

Try pointing to where /bin/bash is on your SD, for example chroot /mnt/SDCard /usr/bin/bash

Dear @tophneal,

The binary format is not the same on my laptop and the SD Card, so bash cannot start (see my above comment) 

Code:

jean@Astux:~$ sudo chroot /mnt/SDCard /bin/bash chroot: impossible d'exécuter la commande « /bin/bash »: Erreur de format pour exec()

Does that mean I have to find another board running the same kind of CPU in order to do the chroot properly ?

Regards,
Jean

[tophneal]

No, it means it can't find bash. Is /bin/bash the path to your Armbian bash?

Sorry. I'm wrong, yes. You'll need another device of the same architecture to properly chroot into it. Or you can use qemu-arm:

Code:

# This provides the qemu-arm-static binary apt-get install qemu-user-static # Mount my target filesystem on /mnt mount -o loop fs.img /mnt # Copy the static ARM binary that provides emulation cp $(which qemu-arm-static) /mnt/usr/bin # Or, more simply: cp /usr/bin/qemu-arm-static /mnt/usr/bin # Finally chroot into /mnt, then run 'qemu-arm-static bash' # This chroots; runs the emulator; and the emulator runs bash chroot /mnt qemu-arm-static /bin/bash

per https://unix.stackexchange.com/a/222981

You might also try copying any configuration changes you've made to you x86 install, make a fresh SD, and then copy over your configuration changes.