Helios4 Armbian doesnt start

[Fefo]

Armbianmonitor:

http://ix.io/1Ukq

Hi,

I'm new proud user of Helios4 Batch3.  I started to "play" with different options on this board - and after a 24 hours of use - board doesnt start anymore.

Status led blinks but and disk leds blink for short time.

It is not possible to connect via terminal console or network.

 

I'think that problem (at least logs point that way) with missing or unavail mount point or (one) disk problem.

But nevertheless I think that system itself should still be accessible. Am I wrong? Some disks can fail but not all mount points reside on them.

 

If I disconnect all disks (physically) then connection(s) is/are possible again.

 

I'm still completely new to this board and system.

 

Please advise.

Regards.

Edited September 5, 2019 by Fefo

[gprovost]

19 hours ago, Fefo said:

Status led blinks but and disk leds blink for short time.

Can you clarify ? Do you mean System Activity / Heatbeat LED (LED1) is still blinking but system is not reachable ?

If LED1 blinks means the system is alive, if it stops blinking it means either System Hang or Halted.

 

 

 

I see you have a mix of HDD, all of them desktop type of hard drive. Are they new or old ?

 

Based on your log file, there an issue with the HDD connected to SATA port 4 (Western Digital Green 1TB) which is part of the RAID5 array you created.

The HDD might be faulty, or could be a faulty cable or bad connection.

 

So I would try first to run the system without this disk or checking/changing the SATA cable.

 

For now with those logs it's not clear what would make the system not accessible on console or network. So please first clarify the questions above.

 

[Fefo]

Hi,

 

Yes - System activity led is blinking

Yes - power indicator led is also on

System is not possible to reach either by console or network

 

STEP-1

I have tried starting system without mentioned disk on SATA port 4 and then is OK (access possible). 

STEP-2

I changed SATA cable for port4 and reconnecting disk - system becomes unnaccessible again.

STEP-3

I have tried starting system without disk on SATA port 3 and then is OK (access possible). 

STEP-4

I tried and changed SATA cable for port 3 and reconnecting disk - system becomes unnaccessible again.

 

My result:

If Disks on SATA3 and SATA4 are both connected - system doesnt start. 

Last operation (before malfunction) was creating mirror (inside OpenMediaVault) between this two disks (both 1TB - on SATA 3 and SATA4 ports )

 

 

Is it a SW bug of some sort?

 

Info:  At this point data loss is not a problem - I have this for testing purposes for now.

Regards

 

 

[Fefo]

I have now made following:

removed array md0 from fstab

umount -l /dev/md0

mdadm --stop /dev/md0

mdadm --zero-superblock /dev/sdb

mdadm --zero-superblock /dev/sdc

reboot ...

 

This was clearly Software issue - now it works with all disks connected.

Perhaps anyone else with similar problem?

 

[aprayoga]

On 9/6/2019 at 5:55 PM, Fefo said:

Hi,

 

Yes - System activity led is blinking

Yes - power indicator led is also on

System is not possible to reach either by console or network

 

STEP-1

I have tried starting system without mentioned disk on SATA port 4 and then is OK (access possible). 

STEP-2

I changed SATA cable for port4 and reconnecting disk - system becomes unnaccessible again.

STEP-3

I have tried starting system without disk on SATA port 3 and then is OK (access possible). 

STEP-4

I tried and changed SATA cable for port 3 and reconnecting disk - system becomes unnaccessible again.

 

My result:

If Disks on SATA3 and SATA4 are both connected - system doesnt start. 

Last operation (before malfunction) was creating mirror (inside OpenMediaVault) between this two disks (both 1TB - on SATA 3 and SATA4 ports )

 

 

Is it a SW bug of some sort?

 

Info:  At this point data loss is not a problem - I have this for testing purposes for now.

Regards

 

 

I still confused with your configuration, you said you setup sdb & sdc as mirror but from the armbian log on first post, it's RAID level 5 with member sdb, sdc, &sdd

 

Quote

[ 2.858020] async_tx: api initialized (async)

[ 2.864901] md/raid:md0: not clean -- starting background reconstruction

[ 2.864938] md/raid:md0: device sdb operational as raid disk 0

[ 2.864941] md/raid:md0: device sdc operational as raid disk 1

[ 2.864943] md/raid:md0: device sdd operational as raid disk 2

[ 2.866085] md/raid:md0: raid level 5 active with 3 out of 3 devices, algorithm 2

[ 2.916888] md0: detected capacity change from 0 to 2000140894208

[ 3.685359] random: crng init done

 

Please run the following commands to make boot process more verbose

sudo sed -i 's/verbosity=1/verbosity=7/g' /boot/armbianEnv.txt
echo "extraargs=no_console_suspend ignore_loglevel" | sudo tee -a /boot/armbianEnv.txt
sudo sed -i 's/exit 0/dmesg -n 8\nexit 0/g' /etc/rc.local
sudo reboot

and please capture serial console from very beginning of u-boot.

Oh, with the configuration that has problem.