Whoops!... Just shutdown and impossible to start again...!?

[pierre]

Hello,

 

so we use Kobol 64 with OMV since 4 months, and no problem at all.

Just yesterday, want to change Ethernet cable, correctly shutdown the Helios64 NAS, and impossible to start it again.

 

Just have the right system light, but left LED no blinking, no information in the USBC terminal.

 

For the "recovery", press the recovery button, and then press the power button, and the LED System don't light up.

 

What can we do, format the system, and reinstall OMV with all parameters... Not really serious, ins't it ?

 

Thank you for any help.

 

Regard.

 

[barnumbirr]

Try and restart your Helios64 while connected to it via serial, you should then see the boot logs.

If you need to increase verbosity of said logs, edit your armbianEnv.txt to contain the following:

 

armbianEnv.txt

Report back with the logs.

Hope this helps.

[pierre]

Hello, here is the logs when I just boot.

 

U-Boot 2020.07-armbian (Dec 15 2020 - 08:45:45 +0100)

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...
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
3185 bytes read in 8 ms (388.7 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1
166 bytes read in 6 ms (26.4 KiB/s)
15755753 bytes read in 673 ms (22.3 MiB/s)
28582400 bytes read in 1213 ms (22.5 MiB/s)
81913 bytes read in 19 ms (4.1 MiB/s)
## Loading init Ramdisk from Legacy Image at 06000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    15755689 Bytes = 15 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 f4fe0000, end f5ee69a9 ... OK
   Loading Device Tree to 00000000f4f63000, end 00000000f4fdffff ... OK

Starting kernel ...

 

And with the "recover" tool

 

U-Boot 2020.07-armbian (Dec 15 2020 - 08:45:45 +0100)

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
using mmc0 device for download mode
rockchip_dnl_mode = ums mode
rockchip_dnl_mode = maskrom mode

FATAL: read zero bytes from port
term_exitfunc: reset failed for dev UNKNOWN: Input/output error

 

So, nothing really working...

 

Thank you.

 

Regard.

[pierre]

So I tried to reinstall with the eMMC method and with the classic SDcard method.

Still the same, no reaction.

 

Oh yes, when I tried to reset (with the SDcard method), here is the logs: see the screenshot

[pierre]

Ok, so I reinstalled on the eMMC card.

Apparently it is ok, but impossible to made something with the terminal.

When rebooting still same problem with characters... Maybe a language, local problem ?

See screenshot (with CRTL-C in the middle)

 

 

[pierre]

Hi, nobody have these characters problem...?

 

And it isn't ok that after a shutdown the system won't boot up. I imagine I'm not the only one...

 

Regard.

[wurmfood]

It's showing it boot completely. There's a login prompt there on the console. Why it's showing the extra characters, I'm not sure. My picocom configuration matches yours and I don't see that.

What's interesting is you've got the SysRq coming up when, I believe, that's normally only triggered by a key combination. I wonder if something is causing extra characters to be sent over the serial console that's causing the problem.

[pierre]

So strange, but after these specials characters, I have access to root login. So it is ok for now...

[Sander Steffann]

Since today I have exactly the same problems. The console doesn't work properly, sometimes shows garbage, and when it works it does have massive packet (well, character) loss. I tried several things, but I haven't been able to use the console properly. I created a new SD card and booted that, and barely managed to set the root password. After that I could log in over SSH, which works fine. But I have the feeling the console hardware is somehow broken

[allen--smithee]

Hi@Sander Steffann,

could you make a photo novel to better explain your problem step by step.

 

the only time I got an offensive message in the serial console was due to cleaning a little too wet.

liquid had flowed into the FCBGA 828.

I remember that the leds on the motherboard were on error.

I used an air gun on it to get rid of the water and put the card in the sun for 1 hour.

I was very lucky not to burn anything