Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

264 profile views
  1. Thank you for your generosity! The Armbian community is doing a really great job. I am still grateful for all the help I found here when I had a problem with my Helios64. (Remember that? https://forum.armbian.com/topic/18855-upgrading-to-bullseye-troubleshooting-armbian-21081/?do=findComment&comment=129711 ) Today I'm not coming to ask for help (since my NAS is working perfectly fine!) but to say hi to everyone. And reading your positive message, Amix73, you even made me want to make a small donation. Thanks again, everyone!
  2. [RESOLVED] I have found a solution to this problem ! The solution is HERE. All my data are back. So happy ! Thank you again, guys !
  3. Hello everyone, Since the last time, I have good news and bad news. I'll start with the good news : My NAS boots by itself, without the MicroSD card. (The problem was indeed on the side of the armbianEnv.txt file. The good one, I mean...) Without your help ( @prahal , @ebin-dev , @Werner , @IcerJo), I would never have managed to get out of it. Thank you so much, all of you! (I have made a small donation to the Armbian forum as a material thank you to the community.) Now, for the bad news (sorry guys... ) : My device is still not working properly. When I do " apt upgrade ", I get the following error message : On OpenMediaVault, when I make a change in the settings and go for the validation (" The configuration has been changed. You must apply the changes in order for them to take effect. "), the procedure fails and I get this error message : Does anyone have any idea what is going on this time?
  4. 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 ?
  5. 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 !
  6. I have tried this. But it’s empty... (watch the video attached to this message) Strange, no ? armbianEnv Empty.mp4
  7. 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 (...) :
  8. 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)...
  9. 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 »)
  10. 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....) )
  11. Hello everyone, I am currently trying to repair my Helios64. I exposed my problem in this topic : A member ( @IcerJo ) said that this problem could be related to this topic. So I read the posts of this topic looking for a solution. I removed the hard drives from my NAS (to avoid a false manipulation) and I opened it (to be able to force the boot from the microSD with the jumper cab P10). Then I followed the instructions of the @TDCroPower message (here : Unfortunately, it didn't work. My NAS refuses to boot from the eMMC (fail at step 10 of the @TDCroPower message). Note that I tried 2 times these instructions: first with the Armbian_21.08.2_Helios64_buster_current_5.10.63 image. Then with the Armbian_21.05.1_Helios64_buster_current_5.10.35 image. My current version is: Armbian 21.08.3 Buster with Linux 5.10.63-rockchip64 and my NAS can only boot from the MicroSD card. Moreover, I can only communicate with it through the usb−usb-c cable, via picocom. SSH doesn’t work (I have an error message " WARNING: remote host identification has changed! "...). Concerning the boot from the eMMC, I understood that it was maybe necessary to refresh the bootloader on eMMC. I didn’t understand very well the procedure to follow to make such thing. I went to armbian-config > System > Install > 5 - Install/Update the bootloader on SD/eMMC, then I rebooted... but nothing. Here is what picocom returns when I try to boot from the eMMC: I'm a little bit lost. I don't understand much about it. Does anyone have a clue for me? Whether the NAS runs on eMMC or MicroSD doesn't really matter to me. I just want to be able to get a working NAS and recover the data from my hard drives (previously configured with OpenMediaVault). Thank you very much, everyone.
  12. Thank you, @IcerJo. I will try this today or tomorrow ! Two questions, please : 1/ Can I do this without fear for my data (I have 2 RAID1 encrypted with LUKS encryption plugin from OpenMediaVault) ; 2) Can I do this not with a previous Helios64 image (like the Linux 5.10.43-rockchip64) but with a more recent (like the 5.10.63 or the 5.10.64) ? I’m not sure but it’s seem that @alchemist have do this here :
  13. Something like that ? --> https://www.amazon.fr/AZDelivery-Adaptateur-UART-TTL-conversion-dinterface/dp/B08T24NML9/ref=sr_1_5?__mk_fr_FR=ÅMÅŽÕÑ&dchild=1&keywords=USB+UART+adapter&qid=1631903713&qsid=262-4238766-5218215&sr=8-5&sres=B08T24NML9%2CB07TFSZ3ZP%2CB07BBPX8B8%2CB01CYBHM26%2CB07N2YLH26%2CB07LH6NJSZ%2CB08VRQFNSN%2CB075XK737D%2CB07TXVRQ7V%2CB07WF7BJJH%2CB0773G2K92%2CB01LY97ZM5%2CB08Y8CJRZT%2CB082R9MYV9%2CB07VDSJPKX%2CB01N9RZK6I%2CB00VBOCUIO%2CB07LH54QHM%2CB072K3Z3TL%2CB004ZMYTYC&srpt=ELECTRONIC_ADAPTER OK, thank you, Werner, I will do that !
  14. Hello everyone, I’m starting this message by apologizing for my poor English (I am French) and also by informing you that I am a newbie with Linux. I have a big problem with my NAS Helios64. At first, I thought this problem was caused by OMV. So I went to the OMV forum to explain my situation. I created the following topic: https://forum.openmediavault.org/index.php?thread/40252-many-problems-after-an-update/&pageNo=1 . There, a kind moderator (macom) asked me to enter some instructions to try to pinpoint the root of the problem. After giving him some outputs, he told me: "For me it looks like your SD card is dead." My installation is not on an SD card but on the eMMC chip of the Helios64. (I followed the Kobol wiki instructions exactly from here : https://wiki.kobol.io/helios64/install/emmc/ ) After that, my NAS has become unreachable. I can no longer log into the OMV Dashboard. I cannot reach the NAS by SSH either. I can just tell you that all the LED lights on the NAS are solid blue. No red diode on. Is the eMMC chip of my NAS dead? Is there a solution that would prevent me from losing all the data stored on the hard drives? (They are in RAID1 and they are encrypted with the OMV LUKS encryption plugin) (I have not made a data backup elsewhere ... I know, big mistake!) I thank in advance all those who will take the time to help me.
  • Create New...