19 19

About This Club

Dedicated section for talk & support for the Helios4 and Helios64 open source NAS. Lead and moderated by the Kobol Team.
  1. What's new in this club
  2. You should settle the dust down. First check where you mount /dev/mmcblk2p1. Do you: mount /dev/mmcblk2p1 /mnt or mount /dev/mmcblk2p1 /mount ? Because the content of the emmc will show up in the above command right directory. It will not be in /mount or /mnt if you did not made it so in the mount command. Second give use the emmc boot/armbianEnv.txt because it could be you set the sdcard armbianEnv.txt to boot with sdcard kernel and "rootdev" (ie boot partition) as emmc. Thus it works but you have to let the sdcard for the boot which is fragile. It ought ot contains: verbosity=1 bootlogo=false overlay_prefix=rockchip rootdev=UUID=e4e3bcd6-3f03-4362-bbe0-f1654138c5d8 rootfstype=ext4 overlays=dwc3-0-host usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u,0x0bc2:0x231a:u only. "echo" and "> /mount/boot/armbianEnv.txt" where only there so you could paste the full command and have it write the armbianEnv.txt in /mount/boot for you. If you write them down in armbianEnv.txt it kills boot. Then feel free to update. I currenty run OMV with buster and armbian up to date on my helios64.
  3. Confirmation : I’m able to connect to my OpenMediaVault with web browser. It’s here ! Thank god you, guys ! So, what do I do next ? Update OMV (and Armbian, via the Update Management of OMV) ? Or fix the eMMC boot problem ?
  4. I just tried it and it doesn't work (« "/mount/boot/armbianEnv.txt" E212: Can't open file for writing », with VIM). Then, I was struck by a doubt... So, I checked if armbianEnv.txt exists (in my eMMC). I have mount my eMMC as @Werner said (here). Then, I tried this : As you can see, it seems that there is nothing except « system » in /mnt. No armbianEnv.txt here. But I have find armbianEnv.txt in /boot. Look : So, I have edited this armbianEnv.txt here (with copy-paste of that ). I have checked the UUID in /etc/fstab (here). « root@helios64:/etc# sudo vim fstab » : Then... I turned off the NAS..... removed the MicroSD.... restart.... and..... ... It doesn't work !!! Same problem as usual : (kernel never start.) After that, I restarted with the MicroSD... as usual... and I see that (!) : What I put in purple color is new for the situation. I guess I found my OMV installation, more or less !
  5. If it is empty then you now know why u-boot fails to boot the kernl. Mine was filled with garbage due to the FS corruption (due to the emmc bug) Fill the emmc armbianEnv.txt with: echo 'verbosity=1 bootlogo=false overlay_prefix=rockchip rootdev=UUID=e4e3bcd6-3f03-4362-bbe0-f1654138c5d8 rootfstype=ext4 overlays=dwc3-0-host usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u,0x0bc2:0x231a:u' > /mount/boot/armbianEnv.txt and reboot. You are done !
  6. I have tried this. But it’s empty... (watch the video attached to this message) Strange, no ? armbianEnv Empty.mp4
  7. If you followed the example given by werner it should be mounted to /mount ... Try this: sudo vim /mount/boot/armbianEnv.txt
  8. You are right ! : I made the mistake of editing the /boot/armbianEnv.txt of the SDcard. (I didn’t touch the UUID but I added this line « overlays=dwc3-0-host ».) So, I followed what @Werner wrote (« mkdir ~/mount && mount /dev/mmcblk2p1 ~/mount && cd ~/mount ») and this is what I see with « root@helios64:~/mount# sudo vim /boot/armbianEnv.txt » : « root@helios64:~/mount# sudo vim /mnt/boot/armbianEnv.txt » gives this (!) : (Yes, it’s empty !) « root@helios64:~/mount# sudo vim /etc/fstab » gives this : And « root@helios64:~/mount# fsck /dev/mmcblk2p1 », that (...) :
  9. Beware ! Do not change your sdcard /boot/armbianEnv.txt. Only the one of the emmc ! thus /mnt/boot/armbianEnv.txt if you mount /dev/mmcblk2p1 to /mnt . As I understood you checked the /boot/armbianEnv.txt of the Sdcard which is not right. If you boot from the sdcard then this one is correct, do not change it. But check your emmc one is not corrupted. Thus /mnt/boot/armbianEnv.txt and compare with the one I gave. As fsck showed your emmc partition was corrupted and fixed by fsck. Try to run fsck /dev/mmcblk2p1 as second time and paste output just to be confident it is now ok. Then when yoiu boot without sdcard try to force u-boot to boot from emmc. run bootcmd_mmc0 from u-boot prompt. Cheers. There are not many option for a failed boot. But check emmc not sdcard files. From your lsblk output : rootdev=UUID=e4e3bcd6-3f03-4362-bbe0-f1654138c5d8
  10. mount your eMMC to some random folder. code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } mkdir ~/mount && mount /dev/mmcblk2p1 ~/mount && cd ~/mount
  11. I am deeply sorry to ask such a beginner's question, but : how can I do that ? I mean : I know how to edit (with « sudo vim ») /etc/fstab and /boot/armbianEnv.txt, but I don’t know how to « reach » theses files in the eMMC (/dev/mmcblk2p1)...
  12. On emmc (/dev/mmcblk2p1) you just need to replace the root UUID in /etc/fstab and in /boot/armbianEnv.txt to match the UUID of your emmc (e4e3bcd6-3f03-4362-bbe0-f1654138c5d8). Then reboot without microsd in the slot...
  13. I booted from the MicroSD (command « run bootcmd_mmc1 »). The command « sudo vim /boot/armbianEnv.txt » shows : So, I added (with vim) the line « overlays=dwc3-0-host ». When I enter « sudo blkid », I have this : I entered « fsck /dev/mmcblk2p1 » and it showed this : I turned off the NAS, removed the MicroSD, turned on.... and... it’s not working... What did I miss ? Do I have to change the « rootdev=UUID » in boot/armbianEnv.txt ? Remplacing the actual UUID of the MicroSD by the UUID of the eMMC ? (Note : now, if the MicroSD is in the NAS, this one boot automatically with no need of the command « run bootcmd_mmc1 »)
  14. Just FYI: https://www.ebay.de/itm/304188439104 (currently at 50€)
  15. They are the same as before as far as I know, "netdev" is selected: $ cat /sys/class/leds/helios64\:blue\:net/trigger none usb-gadget usb-host kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock usbport disk-activity disk-read disk-write ide-disk mtd nand-disk heartbeat cpu cpu0 cpu1 cpu2 cpu3 cpu4 cpu5 activity default-on panic mmc1 mmc2 rc-feedback [netdev] tcpm-source-psy-4-0022-online gpio-charger-online rfkill-any rfkill-none stmmac-0:00:link stmmac-0:00:1Gbps stmmac-0:00:100Mbps stmmac-0:00:10Mbps
  16. check that eMMC boot/armbianEnv.txt contains: verbosity=1 bootlogo=false overlay_prefix=rockchip rootdev=UUID=a79a14c0-3cf4-4fb9-a6c6-838571351371 rootfstype=ext4 overlays=dwc3-0-host usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u,0x0bc2:0x231a:u Note rootdev=UUID= will be different. You can check your by running sudo blkid from the sdcard os. I believe yours is fine so you could also: fsck /dev/mmcblk2p1 when booting from sdcard (booting kernel that has the emmc fix only ! your log shows 5.10.63 armbian 22.08.2 so your are fine. But double check before fscking). Fscking will tell you if the filesystem is fine (readable/mountable by for one u-boot itself to start the kernel). My mmcblk2p1 boot/armbianEnv.txt content was wrong as I ran fsck when my emmc was unstable (this was a bad idea). Thus u-boot was unable to start the system. Restoring armbianENv.txt fixed my boot. The red is fine it is color for deb file type. just a note. The steps were to download from : root@helios64:/mnt/system# wget http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.43-rockchip64/linux-dtb-current-rockchip64_21.05.4_arm64.deb root@helios64:/mnt/system# wget http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.43-rockchip64/linux-headers-current-rockchip64_21.05.4_arm64.deb root@helios64:/mnt/system# wget http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.43-rockchip64/linux-image-current-rockchip64_21.05.4_arm64.deb not 5.10.63 ... but 5.10.63 will be fine too per ie 21.08.2 has the emmc fix.
  17. Hi folks, I am wondering if somebody with a mac enviroment has a decent / performant samba connectivity? After I upgraded to Big Sur I have severe issues with the samba protocol when accessing my shares on the helios running openmediavault. I know that Apple had made some changes with samba but there might be some users that dug a little bit deeper and could give me a hint. I did try it with different settings in the extra options over the past weeks but with no luck so far. Sidenote: Also NFS is terribly slow and laggy. I am back with AFP connection now that does the job perfectly and fast.
  18. ended up re-installing and all good, but i'd like to know what caused it, looks to be GPT sig wrong
  19. You can check the trigger settings on the led. Something along 'cat /sys/class/leds/helios64:blue:net/trigger'
  20. Last night I shutdown my Helios 64 (sudo shutdown now) but when i went to boot it this morning, after startup it looks to be hung, all blue lights solidly on. It's set to run from the micro SD card, so wondering if i hit a R/W limit on that. Serial log below, it doesn't progress beyond "starting kernel" I can mount the MicroSD on my ubuntu box and read the file structure DDR Version 1.24 20191016 In channel 0 CS = 0 MR0=0x18 MR4=0x2 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x18 MR4=0x1 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=0x2 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x18 MR4=0x1 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, 254 SdmmcInit=2 0 BootCapSize=100000 UserCapSize=14910MB FwPartOffset=2000 , 100000 mmc0:cmd5,20 SdmmcInit=0 0 BootCapSize=0 UserCapSize=60906MB FwPartOffset=2000 , 0 StorageInit ok = 76288 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 U-Boot 2020.10-armbian (Mar 08 2021 - 14:54:58 +0000) 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... starting USB... Bus usb@fe380000: USB EHCI 1.00 Bus dwc3: usb maximum-speed not found Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus usb@fe380000 for devices... 1 USB Device(s) found scanning bus dwc3 for devices... cannot reset port 4!? 4 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found 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 5 ms (622.1 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 166 bytes read in 5 ms (32.2 KiB/s) 15755777 bytes read in 674 ms (22.3 MiB/s) 28582400 bytes read in 1212 ms (22.5 MiB/s) 81913 bytes read in 13 ms (6 MiB/s) Failed to load '/boot/dtb/rockchip/overlay/-fixup.scr' Moving Image from 0x2080000 to 0x2200000, end=3de0000 ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 15755713 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 f4fe9000, end f5eef9c1 ... OK Loading Device Tree to 00000000f4f6c000, end 00000000f4fe8fff ... OK Starting kernel ...
  21. Yes, you are right. Didn't notice that. I also see an odd flash here and there but doesn't seem to be related to the network activity at all.
  22. Hi @prahal, thank you for helping me ! So, I have remove the jumper cap and the MicroSD card, but the boot from eMMC doesn’t work. This is what I have when I try to start from eMMC : ... and the kernel never start. (The System activity LED of the Front Panel is blue still. It’s not blinking.) When I boot from the MicroSD card (with the command « run bootcmd_mmc1 »), it’s working. When I boot from the MicroSD card, at the step 5 of the @TDCroPower’s message (https://forum.armbian.com/topic/18855-upgrading-to-bullseye-troubleshooting-armbian-21081/?do=findComment&comment=128305 ), I see this (I don’t know if it’s normal, especialy what is in red) : ( Maybe I have made a mistake because when I have do the step 6 of @TDCroPower’s message, I only « wget » 3 packages of this link : http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.63-rockchip64/ : linux-dtb-current-rockchip64_21.08.2_arm64.deb , linux-headers-current-rockchip64_21.08.2_arm64.deb and linux-image-current-rockchip64_21.08.2_arm64.deb. I didn’t « wget » the 3 packages « 21.05.9 ». (But, when i have try the downgrading with the Armbian_21.05.1_Helios64_buster_current_5.10.35 image on my MicroSD, i have « wget » all the three packages of http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.35-rockchip64/ . But it was not working neither....) )
  23. Hi fri.K, it definitively looks like a driver issue (something goes wrong in rtl8152_post_reset)... I will try to debug further based on your information. I'm also wondering if there's an issue with power consumption when using both NIC (attached the image of my fix for 1Gbps)... cable size (AWG) and length could be an issue? Will try to test also an external USB-RTL8152 dongle to see if the same driver works.
  24. Hi jotapesse, yes same for me ... but on closer inspection ... the flashing of the LAN activity light no longer seems to be tied to real network activity! 1/ It flashes a lot less than it used to do. 2/ If I download a large movie file from the Helios64 to my PC I occasionally see a brief flash, but not the sustained activity that I'd expect from a download that takes several minutes. 3/ Inspecting my network router, I can see constant low level activity on the Helios64 ip address (I only have one ethernet cable attached to the Helios64) but don't see any flashing LED. So in conclusion ... its still not working properly!
  25. Nearly at 300€ already, getting too pricey for me, sorry guys :/
  26. If you boot from sdcard while your previous system was on eMMC the ssh identification is different. If you want to connect to the sd card rescue system: ssh -o "UserKnownHostsFile /dev/null" -o StrictHostKeyChecking=no -o "PasswordAuthentication yes" root@helios64 I mean if your system is on eMMC and you boot from a sd card rescue system you have to tell ssh to ignore the host (and force password auth because the sd card system will not have public kay auth set up). about the failure at step 10 ... you should remove the sd card before boot (and your jumper mod) to boot from eMMC and all should be fine. Mind the process you followed did not tell to set the jumper 10 because it tells to switch boot media via u-boot prompt a command "run bootcmd_mmc1" for sd and "run bootcmd_mmc0" for eMMC. Doing both jumper 10 and u-boot bootcmd_mmc1 is undefined. Simply do one or the other not both. Cheers