Jump to content

Reboot not working properly with OMV

mortomanos

By mortomanos
in Rockchip

 Share

Recommended Posts

mortomanos

mortomanos

Posted
Posted

During installing Helios64 with the latest image I experienced several times that the system did not come up. Now that it is fully installed with OMV enabled, I sometimes do a reboot, and the system does not come up. Unfortunately I cannot see anything on the console level (on MacOS). After pressing the reboot button (around one or two times) the system comes up as nothing happened ever. What can I do to have the system reboot in a stable manner? Since it will sit in the basement soon, I don't want to run down every time I see that it does not reboot properly.

0
  • gprovost changed the title to Reboot not working properly with OMV
mortomanos

mortomanos

Posted
  • Author
Posted

One success discovered today: Using a windows machine with FTDI drivers and Putty brings console output, I can now explore further when there are reboots that do not bring the system up.

1
mortomanos

mortomanos

Posted
  • Author
Posted (edited)
  On 12/8/2020 at 3:31 AM, aprayoga said:

@mortomanos Did you manage to see the problem in serial console?

Expand  

 

Today is public holiday so I had a little bit of time to check some things. I today needed to reboot several times with the reboot button, before the system came up. The serial console stopped always at "Starting kernel ..."

 

The system LED stays blue, the hard disks spin up and each LED flashes a few times, then all attached disks flash together 5-6 times. Then all HDD LEDs stay blue. The LAN LED does not show up.

When pressing the reboot button the console instantly outputs some messages, and the new boot sequence starts. Then again all LEDs stay blue and nothing happens (at "Starting kernel ...").

 

In the log itself there are a few messages that I think are not relevant, but I'll attach them here:

  Reveal hidden contents

 

Edited by aprayoga
Add spoiler
0
mortomanos

mortomanos

Posted
  • Author
Posted (edited)
  On 12/8/2020 at 11:58 PM, aprayoga said:

@mortomanos do you have other Linux system ? edit the boot/armbianEnv.txt and add 

extraargs=ignore_loglevel

 

Expand  

 

That did the trick getting kernel messages.

 

The boot hangs somewhere after md0 is found:

 

  Reveal hidden contents

After that - nothing is happening.

Edited by Werner
Add spoiler
0
mortomanos

mortomanos

Posted
  • Author
Posted (edited)

And a proper boot shows the following:

 

  Reveal hidden contents

 

Edited by Werner
Add spoiler
0
hartraft

hartraft

Posted
Posted

I'm getting the same problems as OP. When I do a sudo reboot, it's the same issue. The helios64 doesn't come up but you can still ping it on the network (LAN LED not on) 

0
aprayoga

aprayoga

Posted
Posted

@mortomanos looks like something wrong with the eMMC. It works intermittently.

on your first log, there are several error like this 

[    3.351947] mmc1: mmc_select_hs200 failed, error -110
[    3.352420] mmc1: error -110 whilst initialising MMC card

 

On your second log, it failed for several times but finally it initialized 

[    3.577160] mmc1: mmc_select_hs200 failed, error -110
[    3.577624] mmc1: error -110 whilst initialising MMC card
[    3.577761] of_cfs_init
[    3.578449] of_cfs_init: OK
[    3.631765] usb 3-1: New USB device found, idVendor=2109, idProduct=2815, bcdDevice= 7.04
[    3.632503] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    3.633140] usb 3-1: Product: USB2.0 Hub
[    3.633594] usb 3-1: Manufacturer: VIA Labs, Inc.
[    3.685522] hub 3-1:1.0: USB hub found
[    3.686115] hub 3-1:1.0: 4 ports detected
[    3.739853] mmc1: Command Queue Engine enabled
[    3.740269] mmc1: new HS200 MMC card at address 0001
[    3.741441] mmcblk1: mmc1:0001 AJTD4R 14.6 GiB
[    3.742111] mmcblk1boot0: mmc1:0001 AJTD4R partition 1 4.00 MiB
[    3.742891] mmcblk1boot1: mmc1:0001 AJTD4R partition 2 4.00 MiB
[    3.743579] mmcblk1rpmb: mmc1:0001 AJTD4R partition 3 4.00 MiB, chardev (243:0)
[    3.745394]  mmcblk1: p1

 

Could you check whether you have P10 jumper enabled?

0
mortomanos

mortomanos

Posted
  • Author
Posted
  On 12/21/2020 at 7:39 AM, aprayoga said:

Could you check whether you have P10 jumper enabled?

Expand  

 

No, both P10 and P11 are not shortened.

 

After upgrade to kernel 5.9.14 I haven't experienced the same problem so far, but this were only a handful of reboots. Also the initialization errors were not in the kernel logs so far. I will post an update if it happens again.

0
mortomanos

mortomanos

Posted
  • Author
Posted
  On 12/22/2020 at 12:42 PM, mortomanos said:

After upgrade to kernel 5.9.14 I haven't experienced the same problem so far, but this were only a handful of reboots. Also the initialization errors were not in the kernel logs so far. I will post an update if it happens again.

Expand  

 

Unfortunately today I had several reboots with the same problem again. MMC did not initialize, always with the same error -110. What can be the problem then?

0
crosser

crosser

Posted
Posted

I have armbian focal installed in mmc, kernel 5.10.16-rockchip64.

After `reboot` command, boot never completes (no heatbeat LED, no network access), though boot process seem to go quite far: 

[   10.832087] rk_gmac-dwmac fe300000.ethernet: TX Checksum insertion supported
[   10.832732] rk_gmac-dwmac fe300000.ethernet: Wake-Up On Lan supported
[   10.833507] rk_gmac-dwmac fe300000.ethernet: Normal descriptors
[   10.834059] rk_gmac-dwmac fe300000.ethernet: Ring mode enabled
[   10.834594] rk_gmac-dwmac fe300000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[   10.843920] rockchip-vop ff8f0000.vop: Adding to iommu group 2
[   10.847541] rockchip-vop ff900000.vop: Adding to iommu group 3
[   10.973820] libphy: stmmac: probed
[   10.974169] RTL8211F Gigabit Ethernet stmmac-0:00: attached PHY driver [RTL8211F Gigabit Ethernet] (mii_bus:phy_addr=stmmac-0:00, irq=POLL)
[   10.975287] RTL8211F Gigabit Ethernet stmmac-0:01: attached PHY driver [RTL8211F Gigabit Ethernet] (mii_bus:phy_addr=stmmac-0:01, irq=POLL)
[   11.294450] async_tx: api initialized (async)
[   11.450714] BTRFS: device label export devid 3 transid 224560 /dev/sdb1 scanned by btrfs (353)
[   11.452467] BTRFS: device label export devid 2 transid 224560 /dev/sda1 scanned by btrfs (353)
[   33.760041] vcc3v0_sd: disabling
[   33.760359] vcc5v0_typec: disabling
[   42.900266] random: crng init done

After reset button, boot sometimes completes, sometimes not. After power cycle, boot always completes.

Should I, too, contact support?

And what is "armbian overlay"?

 

0
mortomanos

mortomanos

Posted
  • Author
Posted

To give some feedback after more than one month of operation: The reboot problem did not happen again after using the overlay. For me, the problem is solved as for now.

I recommend every user with similar problems, just post your serial output in new threads in the forum, and contact support if the board admins advise it. Great support from Kobol, thank you.

1
Vin

Vin

Posted
Posted

seeing a similar issue

 

Helios was already working for some time, aside from regular crashes, but doesnt boot up anymore.

 

It does boot but crashes within a few seconds.

 

Any idea?

 

to rule out unrelated software issues, i flashed the current Armbian_21.02.3_Helios64_buster_current_5.10.21 image on a sd card.

 

Helios doesnt boot form the existing OS on the nand, nor from the fresh one on the sd.

 

 

 

  Reveal hidden contents

 

0
gprovost

gprovost

Posted
Posted

@Vin Based on the log you provided, the system is not crashing but powering off on its own ?! Something is triggering a poweroff 10sec after you finished to start. That's strange.

You sure it's not you who triggered the poweroff ? Or maybe the poweroff button on the front panel is being press by the sticker a bit ?

0
Vin

Vin

Posted
Posted

As i said, by software it shouldnt be possible since its fresh installs, i even used older images.

 

The sticker can also be ruled out, since its on for months and before it was running, also i wasnt pushing anything.

 

I really dont understand what or why, but yesterday i let it run on the battery until it was drained, reapplied the cable and restarted some more, and at some point it was even starting from my old nand image again

 

didnt do a restart so far since im worried it wont come up anymore.

0
gprovost

gprovost

Posted
Posted

Hmm that strange because as said on the log provided it look like a graceful shutdown so something must have triggered it.

 

Maybe try to dig in log in /var/log.hdd/ see if you can find something

0
crosser

crosser

Posted
Posted
  On 3/2/2021 at 5:12 AM, aprayoga said:

@crosser please modify /boot/armbianEnv.txt and add/modify following lines:

  

verbosity=7
console=serial
extraargs=earlyprintk ignore_loglevel

 

It should make the serial console more verbose.

mortomanos is referring to Armbian Device Tree Overlays

 

Expand  

Whether it is a coincidence, newer kernel after one of recent updates, or changed timing due to increased verbosity, but the system comes up all right after `reboot` command last few times. Knocking on wood. And thank you in any case!

0
prahal

prahal

Posted
Posted
  On 1/31/2021 at 7:43 AM, mortomanos said:

Support contacted me and gave me an armbian overlay, the first reboot did work without problems. I will observe further, but for now it looks good.

Expand  

@mortomanos

 

Could you post the dt overlay support gave you for the helios64 back in 2021?

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