Jump to content

Does anyone actually have a stable system?

tommitytom

By tommitytom
in Rockchip

 Share

Recommended Posts

tommitytom

tommitytom

Posted
Posted

Like many others, I get constant reboots with my Helios.  I'm not sure it's worth me posting logs as a number of people already seem to be doing that.  My question is, does anyone have a stable system?  If so what OS and kernel are you using?  I don't care about latest and greatest features, I just want it to stop hard rebooting.

1
wurmfood

wurmfood

Posted
Posted

I do. My system has been rock solid and is acting as a media storage device, NFS, and backup server.

 

wurmfood@helios64:~$ uname -a
Linux helios64 5.10.21-rockchip64 #21.02.3 SMP PREEMPT Mon Mar 8 01:05:08 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
 

ZFS on 4 Seagate 6 Tb disks plus a 250 Gb M.2 SSD. I haven't had to do any of the governor stuff other people have. The only problems I've run into have to do with remembering to rebuild the ZFS module when I update the kernel.

 

One thing I've noticed is that a number of people having problem seem to be using OMV and I'm not.

0
tommitytom

tommitytom

Posted
  • Author
Posted
  On 3/24/2021 at 2:47 AM, wurmfood said:

One thing I've noticed is that a number of people having problem seem to be using OMV and I'm not.

Expand  

 

Oh that's an interesting observation!  I'm using OMV too.  Maybe I should try going without it.  Thanks!

0
gprovost

gprovost

Posted
Posted

@tommitytom Can you show us the early stage boot log (you will need to capture serial console output). Just want to check if you are using rockchip blob or u-boot TPL/SPL, since the latest one has still some instability.

0
NickS

NickS

Posted
Posted

Stable System: Absolutely

I'm running with all latest maintenance & OMV5.

Linux 5.10.21-rockchip64, OMV 5.6.2-1(Usul)

 

---- but I'm keeping things very simple...

NO RAID

4 x HDD ALL THE SAME

NO ZFS

BOOT FROM SD 

AUTO SHUTDOWN & RESTART EACH 24 hours 

 

-- until I get to the apps

21 Docker containers running various apps & services.

 

I've had one docker image fail to come up on a couple of occasions.

 

So ... I'm a very happy customer.

My Data resilience doesn't come from RAID (which I really don't like 'cos 8TB disks take forever to rebuild).

I just backup critical data to my old trusty Helios4! 

 

2
gprovost

gprovost

Posted
Posted

@SIGSEGV During boot up, the first messages output on the serial will show if it's U-boot TPL/SPL our Rockchip blob.

 

This is the output with U-boot TPL/SPL

  

U-Boot TPL 2020.10-armbian (Mar 14 2021 - 07:07:37)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=16/15 CS=1 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=16/15 CS=1 Die BW=16 Size=2048MB
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...

U-Boot SPL 2020.10-armbian (Mar 14 2021 - 07:07:37 +0700)
Trying to boot from MMC2
NOTICE:  BL31: v2.2(release):a04808c-dirty
NOTICE:  BL31: Built : 07:07:20, Mar 14 2021

 

 

This is the output with Rockchip blob

 

  Quote

DDR Version 1.24 20191016
In
soft reset
SRX
channel 0
CS = 0
MR0=0x18
MR4=0x1
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=0x1
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, 322
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 = 68844
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

Expand  

 

0
Vin

Vin

Posted
Posted

Im also still having constant crashes.

 

But recently it already happened 3 times where it crashed for no obvious reason (was running for 1-2 days, nothing has been changed) but then doesnt boot up anymore.

 

So i already reinstalled it 3 times, before it happened again right now.

 

Running latest armbian, with OMV, LUKS, Docker

 

  Reveal hidden contents

 

0
wurmfood

wurmfood

Posted
Posted
  On 3/25/2021 at 6:18 AM, Vin said:

WD120EFAX-68UNTN0

Expand  

One note: It looks like you have CMR drives from WD in there. Those are known to have a variety of problems and may be contributing to the issues you're seeing.

0
ShadowDance

ShadowDance

Posted
Posted
  On 3/25/2021 at 11:51 PM, wurmfood said:

One note: It looks like you have CMR drives from WD in there. Those are known to have a variety of problems and may be contributing to the issues you're seeing.

Expand  

 

Are you sure about that? Generally CMR is considered good, SMR is what you'd want to stay away from. Is it something related to these specific drives?

0
wurmfood

wurmfood

Posted
Posted
  On 3/25/2021 at 11:58 PM, ShadowDance said:

 

Are you sure about that? Generally CMR is considered good, SMR is what you'd want to stay away from. Is it something related to these specific drives?

Expand  

Ah! Sorry, yes, you're right. I've been looking at these back and forth for the last few days. A lot of people here have been having trouble with WD drives and at least some of that seems to come down to the difference between the two types of drives.

1
gprovost

gprovost

Posted
Posted
  On 3/26/2021 at 1:40 AM, SIGSEGV said:

From the looks of it - Armbian 21.02.03 seems to install the Rockchip Blob.

Expand  

Yes it install the package but doesn't automatically update the bootloader on the target (sdcard or eMMC)

 

For this you will need nand-sata-install -> option 5

 

image.png.96ade7c7792179dfaaa9a0c278108d1d.png

 

0
bunducafe

bunducafe

Posted
Posted

After fiddeling aroud I finally have the helios64 also running solid. I never had any freezes before just some problems with getting the system to boot from the emmc device and, see other thread, with setting up OMV - LUKS - Snapraid - UnionFS

 

I am currently under: Linux helios64 5.10.21-rockchip64 #21.02.3 SMP PREEMPT Mon Mar 8 01:05:08 UTC 2021 aarch64 GNU/Linux

OMV Version 5.6.2-1 (Usul)

 

So I would say that OMV is not the culprit out of the box. The system works fine but it always depends on what kind of plugins you are using etc. So far I have no docker installed here but I certainly will do that again. I do recommend the OMV Backup Plugin so I can boot from the latest stable release via SDcard if I mess up with something. That's also nice.

1
hartraft

hartraft

Posted
Posted

My system has been "stable" running the LK 5.9. I updated to 5.10 in the past but had issues with stability under small load, not rebooting through omv etc. so I went back to the previous version. 

Running MergerFS / SnapRAID / LUKS on Seagate Ironwolves with the 1.2ghz frequency 

 

$ uname - a

Linux helios64 5.9.14-rockchip64 #20.11.3 SMP PREEMPT Fri Dec 11 20:50:18 CET 2020 aarch64 GNU/Linux

 

$ uptime

 20:25:53 up 67 days, 19:23, 2 users, load average: 0.08, 0.12, 0.12

 

I'm sticking with this until things get clearer but would like to get full use of my NAS hardware... 

1
axeleroy

axeleroy

Posted
Posted

My Helios is stable, running LUKS, MergerFS, SnapRAID, OMV and 9 Docker containers from SD Card and with 3 HDDs.

 

Although in order to get a stable system I had to lock CPU frequency at 1.2GHz, otherwise CPU intensive tasks (like SnapRAID's scrub) would cause my Helios to reboot.

  

================================================================================
= System information
================================================================================
Linux helios64 5.10.21-rockchip64 #21.02.3 SMP PREEMPT Mon Mar 8 01:05:08 UTC 2021 aarch64 GNU/Linux

================================================================================
= Uptime
================================================================================
12:25:17 up 8 days, 1:18, 0 users, load average: 0.01, 0.10, 0.15

================================================================================
= openmediavault information
================================================================================
Release: 5.6.2-1
Codename: Usul

================================================================================
= openmediavault plugins
================================================================================
ii openmediavault-backup 5.2.4 all backup plugin for OpenMediaVault.
ii openmediavault-flashmemory 5.0.8 all folder2ram plugin for OpenMediaVault
ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive
ii openmediavault-luksencryption 5.0.2 all OpenMediaVault LUKS encryption plugin
ii openmediavault-minidlna 5.0.5 all OpenMediaVault miniDLNA (DLNA server) plugin
ii openmediavault-omvextrasorg 5.6 all OMV-Extras.org Package Repositories for OpenMediaVault
ii openmediavault-snapraid 5.0.7 all snapraid plugin for OpenMediaVault.
ii openmediavault-unionfilesystems 5.1.2 all Union filesystems plugin for OpenMediaVault.
ii openmediavault-wol 3.4.2 all OpenMediaVault WOL plugin

 

PS: don't mind the uptime, I had to reboot to apply an update. Otherwise no problem since mid-February.

1
rupert

rupert

Posted
Posted

HI,

 

My poor little Kobol has to work very hard for a living:

 

Plex

NTP (GPSD) server

SMB share

Webmin

Zabbix agent

Zerotier client/bridge

Docker

Storj node

Raid 5 across 5 disks

 

And is as good as gold!

 

Had a few niggles to start with ie first week, since then its only rebooted as the OS requests otherwise excellent!

 

Running on a 64Gb SD Card

 

CPU full speed

 

Very pleased!

 

Rup

 

1
Polarisgeek

Polarisgeek

Posted
Posted

Just wanted to add my experience as maybe someone can get something semi-useful out of it. 

 

I started out with 3 - 4TB drives with 2 of them in Raid 1 and the 3rd on it's own.  I installed OMV and CUPS on a Micro SD card.  Even from the very beginning, I always had trouble restarting the system.  Sometimes it would boot after 3 tries, sometimes it would take 20 tries.  I watched and it was never the same issue twice that caused the boot failure.  I removed drives, plugged in different combo's, several fixes on the forums, anything I could think of and nothing really seemed to make a difference.  The good news was that once it was up and running, it ran great.  I had 2 months of uptime with no issues.  Then i'd run an update and have a heck of a time getting it restarted.  Just figured that's the way it was and hoped things would get better as the software matured.  

 

I'm now on my second iteration with 5 - 14TB (Thanks Uncle Joe) drives in Raid 6.  After 2 months, i've had 2 random crashes for unknown reasons, one at 3 days and the other after 7 days.  Aside from running updates and rebooting, it's been running solid for me.  I'm only running OMV and a CUPS server.    Getting to this point was a huge PITA.  I spent nearly 8 hours trying to get it up and running over the course of a Sunday.  It seemed like no matter what I did, i'd have a Kernel Panic during the setup process, and then the system wouldn't boot at all giving different errors every time.  So i'd re-download the image, and attempt to install from scratch again.  I played with installing different options, in different sequences (as much as possible), without much luck.  I verified the download every time.  I finally tried using USBImager, as an alternative to BalenaEtcher, and found that wring to the sdcard seemed better and the installation seemed better, although it did panic a couple times.  Once I finally got it running, I gave it some time, installed all the updates, reboot several times in between setting up OMV for testing and have been happy with it since.  The biggest difference now is that I don't worry about rebooting as it comes right up the first time instead of several tries like the first iteration.  

 

Overall, i've been happy with mine.  I'm very new to the Linux environment so it's been fun learning a new thing.  Keep up the great work!

2
CharlesGillanders

CharlesGillanders

Posted
Posted (edited)

Mine is running absolutely stable.  Only ever have to reboot due to updates.

 

I am running OMV - I have 5 x WDC WD40EFRX-68WT0N0 drives with Raid-6 and then LVM via the OMV LVM plugin - I'm running NFS, Samba, cloudflare tunnel daemon, and Docker (in docker there's portainer, duplicacy, traefik and authelia)

 

If it helps I'm only using the 1GB NIC and I do have the battery for power supply stability.  Oh and I'm on  5.10.21-rockchip64 #21.02.3 SMP PREEMPT 

Edited by CharlesGillanders
added more information
0
IcerJo

IcerJo

Posted
Posted

I set my Helios64 up last week, and placed it at it's final home/location. My unit had been running perfectly fine for 2 days then sometime this morning before I woke up it crashed and auto rebooted. System has been up for 2 hours now. Following the guide above, I have changed my cpufreq to 400mhz-1.4Ghz and I set the governor to OnDemand and will see if stability will last beyond two days :). Hopefully whatever the culprit is, will be fully ironed out by or before the Armbian becomes fully supported I was just on the site and it now says supported lol.

 

Thanks again to all!

0
rupert

rupert

Posted
Posted

HI,

 

My poor little Kobol has to work very hard for a living:

 

Plex

NTP (GPSD) server

SMB share

Webmin

Zabbix agent

Zerotier client/bridge

Docker

Storj node

Raid 5 across 5 disks

 

And is as good as gold!

 

Had a few niggles to start with ie first week, since then its only rebooted as the OS requests otherwise excellent!

 

Running on a 64Gb SD Card

 

CPU full speed

 

Very pleased!

 

I have to say the common factor in a LOT of those with issues is OMV as far as I can see, maybe there is an inherent issue there??

 

Rup

 

1
buster

buster

Posted
Posted

Mine is running just fine for months now. Just upgraded it (kernel 5.9... to 5.10..) and it's still running fine.

 

openmediavault 5.6.5-1

Mirror Raid with XFS and 2 disks

NFS, SMB Shares

Welcome to Armbian 21.02.3 Buster with Linux 5.10.21-rockchip64

0
hartraft

hartraft

Posted
Posted (edited)
  On 3/29/2021 at 6:30 PM, hartraft said:

 

$ uptime

 20:25:53 up 67 days, 19:23, 2 users, load average: 0.08, 0.12, 0.12

Expand  

Okay... So I had to jinx it... After 100 days of uptime, I had to do some electricity work in the house. Either the Helios64 shut-down after the UPS was spent or it rebooted / shut-down. Now I can't boot the thing back up anymore. 

Connected through picocom and it doesn't get past "Starting kernel". Tried without any disks attached, same thing. Similar to another thread, the LAN LEDs don't light up (obviously). Any ideas? 

Screenshot_20210501-125713217_1.jpg

 

  Reveal hidden contents

 

Edited by hartraft
Added logs
0
gprovost

gprovost

Posted
Posted

@hartraft Could you modify /boot/armbianEnv.txt and add/modify following lines:

  

verbosity=7
console=serial
extraargs=earlyprintk ignore_loglevel

 

If you are booting from eMMC, you will need to first boot from a fresh image on microSD, then mount the eMMC to modify /boot/armbianEnv.txt

0

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept