count-doku

Members
  • Content Count

    54
  • Joined

  • Last visited

About count-doku

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  • Location
    Germany

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Then the Helios or the Clearfog BASE would probably suit you best. They have the same processor (even SoM) but different carrier boards. Helios has the advantage of offering you 4x SATA directly but only one Gbit Interface (could be expanded via usb3 though). Clearfog BASE is similiar sized but offers 2x Gbit Ethernet (+1 if you use the sfp connector) and a mPCIe Port which can be used for SATA extender cards. (There is also the M.2 interface with only SATA populated. This might be used for a external ssd / hdd or even with multiple, there are some extender cards out there - all untested though.)
  2. May I ask what your goal is? Do want a NAS like device or more of a Router/Switch kind of thing? If it is NAS is your main aim, I would definitely think about the Helios. Power consumption is not really an issue here, because as long as you use hdd's they will most probably consume more than the board. Remember, even WD My Clouds consume up to 10W. If your more targeted towards Network/Router/Switch stuff, Clearfog is probably you're better option. With the two mpcie slots isn't a problem to drive up to 8 disks and it has 2 independet Gbit Ethernet ports (one switched to 6 slave ports).
  3. @deb2016 just to wind up on this issue. This is somehow fixed in the new Armbian 5.91 (default). See the download page or armbian docs for more info.
  4. @Igor This is not a problem on deb2016 side. This is a general problem. You posted some armbian-monitor link above, of your setup: Did you read the results? Because if you check your 'lspci' output, you would realise that your 4x marvell sata card is not detected in linux: ### lspci: 00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04) 00:03.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04) 02:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac Wireless Network Adapter So this is the same problem @deb2016 is facing. In my opinion this is a big problem (maybe even with the drivers for 88se9215 (which is probably your sata card)) and we should try to fix this together with current work on mvebu. See also github issue. https://github.com/armbian/build/issues/1426
  5. 'apt update' only updates the local package list (repository) and tells you, if there are updated packages. 'apt upgrade' then does actually upgrade the packages so apt update / apt upgrade will mostly be used together in this order. If the current bootloader is broken, use the old one. No need to update if it works. You can still update/upgrade everything else. Just don't do armbian-config -> update bootloader. Or if you want to test, at least backup your sdcard or whatever beforehand. As a general rule of thumb, if it updates automatically (via apt update/upgrade) it is safe to use in production. If you need to go via armbian-config (and do it manually) so for example switching kernels or updating the bootloader it might be unsafe, and you should probably backup your installation beforehand.
  6. count-doku

    count-doku

  7. Hi, single pcie card can give you 4 SATA already (there http://amzn.to/2fEd93N from the armbian download page) Depending where you live it might be worth to check the pcengines boards: https://pcengines.ch/apu2.htm They also have some nice boards, with lots of ethernet and mpcie slots. Don't know about the software support though.
  8. Hi, I would not recommend using the espressobin right now, because it seems to have some different hardware versions with more or less problems currently, just look into the bug report forum for espressobin and check the last few threads. I'd rather use the clearfog (pro) board from solidrun. It features a dedicated gbit wan port and a 6 port gbit switch. This will probably be good when used as router/firewall/switch. It also has some sfp cage which could be used for another gbit copper or even higher speeds fiber - but I am unsure about how good kernel support is for that atm. For you're storage needs it has 2 mPCIe Ports in which you can put some SATA controller - the one linked on the download page (with Marvell Controller 4 channel) is working. And there are also a few others (Delock) which should work. Maxing this out you could get up to 8 SATA drives running. Be sure to check out x86, there are some mini-itx mainboard/cpu combos with pretty decent stats and low consumption as well. In the end this mainly depends on where your priority lies: consumption, storage, network, processing power? And always remember that you'd need some external power supply giving you 12V and 5V for the hdd's. Or some extra buck converter. Greetings, count-doku
  9. Ok I suspected that, and I was not criticizing it. It is a good solution. Just wanted to explain why I even updated Will it help if I do some test (different versions) and post logs? Great. I assume if you remove latest version the old 5.75 will be available still?
  10. Good evening, as uboot doesn't get updated automatically since a few versions back, I ran the uboot install script manually today - so far everything worked, uboot got copied to the boot sector. After rebooting though it seems that uboot is not working / properly compiled. It runs normally until the point where it would boot linux, then stops saying it can't find the various commands (bootz, help, echo etc). It dropped me to the uboot shell. I tried a few commands (help, reset etc) and all just gave a "command not found" failure. After restoring the 5.75 uboot from some backup it works again. Is there some known problem in the current uboot? Otherwise we should probably tell users not to upgrade atm. I will provide uboot serial output tomorrow, no time today. Greetings, count-doku
  11. Not sure but isn't the camera cable on the pics you posted inserted in the wrong direction? I thought the blue thing needed to be facing up relative to the connector.
  12. Okay then I will make a backup of my clearfog setup, update kernel via armbian-config and test it. If nothing breaks it stays on, and I will report here in a week or so. For the Helios: Don't think it matters alot - maybe just re-add the -20°C tweak...
  13. Hello, today I tried upgrading my ClearfogPro Kernel from 4.14.106 (next) to 4.19.20(dev). So far everything seems to be working (samba, dnsmasq, minidlna, network etc.), see also attached armbianmonitor link. Great work @ armbian. I also noticed that the reported temperature by "cat /sys/devices/virtual/thermal/thermal_zone0/temp" seems to be about 20°C lower than with the old kernel. I appreciate this, because it seems to be closer to the real value (measured with thermal probe at heatsink). The old 4.14 kernel always reported some value around 65-70°C which seemed a bit high for idling (cpu running at 800Mhz like 80% of the time). The new value of 35°C is quite realistic I guess. Does anyone know / have information about a change in temperature reading on the clearfog in the last kernel upgrades? EDIT: Checked in the kernel diff between 4.14 and 4.19 and there are some changes to https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/thermal/armada_thermal.c?h=linux-4.19.y They definitely changed something regarding some trim values - though I don't understand enough to really say if that changes the temperature reading. But if it did it might also be interesting for the Helios4 guys, I remember seeing some questions about high temperatures in their thread. @gprovost could this be related? Can I somehow help getting the 4.19 Kernel to be next? Like specific things to test? Or is your plan to skip 4.19 completely and go directly to 5.x? Greetings, count-doku
  14. One other thing to check if the disks are faulty / just doing the clicking -> connect them to some computer. Listen there.
  15. just to answer your original question mdm63, as nobody else seems to be able to give some simple answer without talking about money. As Armbian is hosted on github you will probably always be able to build images for your board even if it is EOS/EOL. Worst case is that you will have to go back and pick some commit in which the board is still available in the build script ( if they at somepoint remove the configs for the board). I would suggest that you make some backup of the current (or last working) version of the buildscript (and maybe cache / kernel) so that even if the repositiory is gone, you can still generate images for your board. Greetings, count-doku