• Content Count

  • Joined

  • Last visited

 Content Type 


Member Map






Everything posted by jshc1

  1. If I find time after Sunday, I will check my Hc1.
  2. More or less. The blue LED can say a lot, especially if the person cannot connect the console. This was useful not so long ago in the 5.x kernel where after upgrading from 4.14 simply Odroid HC does not boot and the diode just lights up all the time indicating that the sbc is hanging. For example, if the sd card were damaged and the boot partition is missing, the LED would not light up at all, the same effect as without an sd card. For novice users it is always best to stick to the standards because later unnecessary problems are created especially with headless sbc and no uart.
  3. I would recommend changes to settings only for advanced users. Changes for fun can only make future diagnostics more difficult when someone changes the heartbeat and then it can only result in unnecessary confusion.
  4. I'm not sure. It is possible that somewhere on the odroid forum / wiki something is about it. I wrote it from my own observations based on Odroid HC1, which I had for two years.
  5. ssh -v may tell you something more. (ssh -v root@IP) I have never had a problem with armbian and ssh on the first login. Try again from the beginning ...
  6. Odroid does not behave like PI. Odroid has one blue diode which signals heartbeat signal. After connecting the power it will light up. If it finds a boot and starts booting, it will start flashing. The blinking speed depends on the load. The red LED is on all the time when the current reaches the sbc. The green LED lights up when HDD is connected, blinks when HDD has activity. The first start of Armbian needs about 30 seconds before it is ready for the first login.
  7. Maybe not use dd .... 1. Install the latest version of balenaEtcher. 2. Make sure your sd card is ok and the system is able to save files / create partitions on it. 3. Download the correct Armbian file, maybe https://dl.armbian.com/odroidxu4/Buster_legacy 4. Extract Armbian from 7z. 5. Run balenaEtcher (as root) select the Armbian_20.02.0-rc1_Odroidxu4_buster_legacy_4.14.165.img and write to the card. 6. Must work. If nothing is dumped on the sd card then try on a different system / sd card. If that's such a problem then I can make a clean copy of the system with the help of acronis true image and you will use it ... But I don't see such a need.
  8. Are you sure you're doing everything right? Not long ago I tested buster and 4.14 on HC1 and it was ok. Until recently there was a problem with 5.y on HC. And as @Igor said, wait or make yourself. Or just start with buster and 4.14 and for some time when 5.x will be stable for HC then you will change. As for OMV and clouds, I don't know what exactly doesn't work for you. For omv use armbian-config. But remember that omv 5.x is still beta. I still use 4.x because of 5.x there are a lot of problems all the time so I prefer to wait until the end of the year. You can run the clouds in the docker ... If you prefer video help, watch "Techno Dad Life" has a lot of material about OMV and docker but on x86 basis so you will have to show some independence in adoption. As for HC1, try this one https://dl.armbian.com/odroidxu4/Buster_legacy don't worry, let etcher take care of the partitions. It should work ... If it still doesn't work and somehow this is a problem with 20.y then maybe https://dl.armbian.com/odroidxu4/archive/Armbian_19.11.6_Odroidxu4_buster_legacy_4.14.161.7z Or go into old age and just install stretch 19.x / 4.14.x for me on HC1 works 100%. If that doesn't work, then you either do something wrong or you have hardware problems. https://dl.armbian.com/odroidxu4/archive/Armbian_19.11.6_Odroidxu4_stretch_legacy_4.14.161.7z
  9. Do not use the 5.x kernel with Odroid HC1 / HC2 / XU4 / MC for now, stay on 4.14.
  10. Relax ladies and gentlemen! Odroid HC1 and HC2 when it comes to NAS is one of the better options available on the market when it comes to one hdd and for this price. I have already written about it above. Sometimes some have a poor quality physical USB2.0 port which causes pin contact problems. It was enough for me to press the metal latches. And frequent symptoms of loose pins are problems with disappearing hardware or lack of maximum power supply at the port. But OP apparently doesn't use HDD on usb2.0 so that shouldn't worry him! The HDD is connected not via USB in itself. This is a SATA-USB3.0 bridge that has nothing to do with the physical USB2.0 port. However, not many problems on the JMicron SATA-USB3.0 bridge. JMS578 is quite a good construction, there will certainly be some problems but nothing that would make HC1 suddenly go to the trash. Personally, I had no problem for two years. And you, too, will not have problems. Do not panic! Odroid HC1 / HC2 is still a very good SBC as a NAS. The problems you have are not problems with HC1, but problems in the software layer, not hardware. If this is to be a NAS, I recommend trying to install OpenMediaVault via armbian-config, it will simplify samba / nfs configuration ...
  11. Here you have Buster (server) and 4.14.161 after installation you will up to 4.14.165 https://dl.armbian.com/odroidxu4/Buster_legacy And the desktop buster version and 4.14.161 https://dl.armbian.com/odroidxu4/Buster_legacy_desktop https://dl.armbian.com/odroidxu4/
  12. Buy! I personally have HC1 for almost two years and no problems. Alternatively, you might think about HC2 if 3.5 inches will interest you in the future, especially if you need something above 5TB at normal prices it will be a better solution than 2.5. As for OS, install Armbian based on buster but with 4.14.y kernel because currently 5.x has big problems with HC, it doesn't boot at all. But 4.14 is not a problem because some time will be supported. As for samba, stretch has 4.5.16, buster has 4.9.5 If you need 4.11.3, you will need to install samba from bullseye / sid sources. Buy a decent PSU, don't save !!! I also recommend buying a branded A1 / A2 SD card. If you are thinking about using a USB port, it would be good to have a HUB with power. In general, imho Odroid has something of poor quality USB ports, quite loose and likes to have problems with pin contact, sometimes you need to bend the metal plates for better contact but these are random cases. My HC1 works well with the rf receiver and the USB sound card. After buying it is worth checking if the Firmware is new, if not update ... https://wiki.odroid.com/odroid-xu4/software/jms578_fw_update My armbian HC1 handles omv, pihole, kodi, xrdp and chromium. If you have fast hdd / ssd then getting 80-100MB/s should not be such a problem with SMB. You can also think of a uart-usb cable especially dedicated to odroid just in case. Generally it's ok and stable, I do uptime 20/30/50 days.
  13. In theory, yes, in practice there may be little power. Although I've heard that some use, the same gutters as XU4, HC1, HC2 so look for information about XU4/HC and plex. First you would have to take care of hardware support ...
  14. Can you tell me such a thing ... where is 162 you wrote about, because arm-conf only gives me a maximum of 161. I'm probably blind. It would also be good to delete 5.4 for now, so that no one accidentally gets into a problem and complains about it as with TK recently
  15. The truth is quite brutal ... In fact, after Thomas leaves almost no one deals with OMV in the context of ARM. Volker Theile has never been interested in ARM, his focus is only on x86. There is Aaron Murray but he is not officially a dev. He deals with omv extras and generally helps but ... When Thomas left Aron promised that images for all ARM sbc would be built and it ended with just that.... "The pre-install images have been deprecated in favor of using this guide -" https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/install And as for Thomas Kaiser, he left omv on Jul 26th 2019, like many other places...
  16. Good luck with 5.4 My HC1 absolutely does not want to boot with 5.4
  17. So... .161 works ok. I checked again 5.4 and still no boot. I checked the clean Buster 5.4 installation and the same, 30 seconds heartbeat, and darkness. There is no ssh, hc dead ... I checked clean 4.14 stretch installations and change to 5.4 again darkness. My HC1 just has 5.x allergies I don't know how your HC1 works with 5.x
  18. I saw this behavior on one of 5.4.x I changed to nightly and I probably used current and I had the same symptom as TK, the blue diode is lit all the time and no boot, on DEV, however, as I wrote above, the diode stops lighting and there is no boot. Of course, I'm talking about an update, maybe with a clean installation something is better and works just like yours
  19. Strange, since your hc is booting hmmm ... If I find the time, I'll try a clean installation. Whether it's warm or cold I can't see the difference. I have a maximum clock frequency of 2Ghz and 1.5Ghz, boot problems or stability I didn't have until 5.x The same thing happened at 5.0 but then I thought it was the initial problem of underdevelopment and I hoped that it would be solved over time but remained with me to this day. But if you say that there are problems with stability, then probably I will stay for now at 4.14. Any plans for 4.14.161 in the near future? Because .157 is a bit old ... Currently, arm-conf only shows me DEV when it comes to 5.x PS in the attachment both boot partitions ... Working correctly 4.14.157 and problematic with 5.4.6 Kernels.4_14.157-5.4.6.tar
  20. I can send you the whole boot partition if it helps...
  21. Everything looks similar between 5.4 and 4.14 ... Everything is on SD. Nothing modified. 4.14 works normally without problems I do uptime 20-30 days. Only there is always this problem with boot at 5.x As if something was wrong with armbian-config and the installation procedure or with the 5.x kernel for HC1. I log in. I run armbian-config and System / Other / I change the kernel ... the typical 5.4 installation procedure begins and the old kernel is removed, after which the ssh connection is broken and after a while it gets reboot and HC1 does not get up anymore. Only the blue LED is lit for a while as if it was looking for a boot and goes off, nothing happens. Red and green behave normally. dtb exists and points to the right place. I did the test, restored working 4.14.157 boot partition from backup and manually copied 5.4.6 and changed the links ... the effect is the same no boot and just change the links back to 4.14.157 and it is boot. It seems that specifically with 5.x for hc there is something wrong ... UUID is also ok. Unfortunately, I do not have a cable that would fit the odroid, I only have a regular uart.
  22. This situation has been around for quite a long time with 5.x and HC1. Using armbian-config theoretically the installation is the same as in the case of 4.14.x At the end of the installation, automatic reboot is made and the HC1 does not get up again. Hard power on / off also does nothing. The blue idode will light up for a moment and afterwards go off and nothing happens as if something was wrong with the boot. I have performed the installation 5.x a dozen times always the same so a random error during installation I rather rule out. What's worse, this behavior has always been with 5.x, earlier I just treated it as an error with the early version 5.x but now with 5.4.6 it's a bit too far to ignore it. Any ideas?
  23. My HC1 after changing from 4.14.157 to 5.4.6 using armbian-config is not able to get up ... zero response, no boot Does HC1 work with kernel 5 and boot, can anyone confirm?