Jump to content

integros

Members
  • Posts

    7
  • Joined

  • Last visited

  1. Finally found the time to set my Helios4 up (3 HDDs & 1 SSD) and I'm still a little bit underwhelmed. Mainly because I can't find reliable Information. Is a constant temperature of 65°C (all drives in standby and nothing besides a ssh-session running - cpu runs at 1.6GHz but the governor is "ondemand") acceptable or should I adjust fancontrol to start at 50°C (or even lower)? I don't care if the fans run (as long as the power consumption doesn't increase significantly) because the Helios4 is in our basement. How can I move the system to the SSD connected to the first SATA-port? Right now I'm running the latest Debian-Image from here (4.14.98-mvebu).
  2. 5.67 ist the official/latest release. How do I enter your commands? With bash (default shell here) I always get "setenv: command not found".
  3. Thank you very much. Problem fixed. Time to set my Helios4 up. Some Questions to all Helios4-Users: - I have 3 HDDs and 1 SSD. Is there a way to put the whole System to the SSD and boot from it? Couldn't find an instruction how to achieve that. - I am planning to make all drives accessible to different Users in our LAN (no RAID). What is the most energy efficcient solution? OMV or setting everything manually up? - Is there a way to use an UPS with the Helios4? Similar to the use with a Synology?
  4. Here is the serial console log:
  5. It's late here, but I'll try to provide the serial console logs tomorrow. What I did was quite straight forward. Downloaded the Image, flashed it to a SD card with etcher, booted, logged in as root via ssh, created new user, changed IP to a static IP, rebooted, logged in as new user, tried to update, reboot - no more lights, no longer able to connect. Tried this with armbian-config, with apt update and with the bionic Image. Always the same result.
  6. Finally found the time to assemble my Helios4, downloaded the Image (4.14.83 stretch), connected via ssh, created a new user and made some changes for my network. Rebooted and everything was working fine. Tried to update via armbian-config, but as soon as I rebooted the card/system was no longer recognised. Tried to update via apt upgrade/update and also tried the bionic image. Always the same result - the system doesn't boot after trying to update, no LED was blinking. Putting the original Image (4.14.83 stretch or bionic) back to the same SD-Card solved the boot problem.
  7. Hi, I'm running into a problem I can't solve. On my new Odroid HC1 I'm trying to set up a SFTP with chroot, but no matter what I'm trying it doesn't work on Armbian (or OMV). Tried it multiple times with a clean Armbian (Armbian_5.59_Odroidxu4_Debian_stretch_next_4.14.66 - also tried the Bionic image) install, simply added a user, added the required lines to sshd_config but each time I get a "Broken Pipe" error. On the other side when I use the minimal Ubuntu image from Hardkernel.com the chroot SFTP works without a problem. But I would like to run Armbian. Has anybody been able to create a chroot for SFTP on a Odroid HC1/2? Could it be that it is a problem with the how the partitions are mounted? The "df -h" results of a working ubuntu image root@odroid:~# df -h Filesystem Size Used Avail Use% Mounted on udev 929M 0 929M 0% /dev tmpfs 200M 5.8M 194M 3% /run /dev/mmcblk1p2 30G 1.4G 28G 5% / tmpfs 998M 0 998M 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 998M 0 998M 0% /sys/fs/cgroup /dev/mmcblk1p1 128M 15M 114M 12% /media/boot tmpfs 200M 0 200M 0% /run/user/0[/quote]
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines