Jump to content

SIGSEGV

Members
  • Posts

    73
  • Joined

  • Last visited

Everything posted by SIGSEGV

  1. @allen--smithee Nice - having the temperature ramp up slowly is sign that the new thermal pad + heat sink + fans are working better. So from factory only the CPU has a thermal pad? or is there more than one contact point with the heatsink from the factory? I'm much inclined to try this solution on my system - just to get the slow & gentle temperature curve (plus I have a few ARM based handhelds that might need a bit of heatsink modding).
  2. I'm interested on your results @allen--smithee
  3. I'm having the same issue once Armbian gets installed to eMMC using the armbian-config tool [Armbian 21.02.1 Focal] Boots fine with the image on the microSD card, but it won't finish booting when on the eMMC (all lights solid blue and no heart beat).
  4. Yes, either a smaller SSDs focused version - or a solution to fit more SSD or 2.5 drives with a SATA port multiplier on the same space as the 5 drives, to increase storage density. If later revisions of the main CPU board or newer boards can be retro fit into these cases, it would make for a smooth and straight upgrade path.
  5. @roswitina Support for OpenZFS is coming, probably v0.8.5 or v0.8.6 will arrive before v2.0.0 In the mean time, if you want to give OpenZFS v2.0.0 a try on the current kernel you can try these scripts to build the debs needed. Keep in mind that you would need to compile your files every time you want to upgrade your Armbian installation to match the kernel. Building can take around 15-30 minutes - the process will use the RAM based tmpfs so your storage is untouched. Credits goes to @wurmfood and @grek for putting together the original versions. Type exit after compilation finishes to go back to default environment Install all 'deb' files under /tmp/chroot-zfs/zfs. with 'dpkg -i' add_chroot.sh - run manually as root or sudo user if you like: build_zfs.sh - place under /build directory of chroot environment.
  6. @slymanjojo If you don't need the transcoding - the minidlna package could be a good alternative, low resource usage and the performance mostly will depend on your network and the reproduction device. Once HW transcoding makes it to the latest kernels, the other packages should behave much better - you're not the only one waiting for it.
  7. Did you create a bootable microSD card? The U-Boot image is not on SPI yet - so it needs it will look for it on the SD and eMMC - if you haven't written the image on either of these you won't get any output on the console.
  8. Can you write the image of the latest release to a microSD card and try to boot off of that? You might need to update the boot loader on your eMMC, but you'll need to be able to boot from a release on an microSD card to be able to boot your system first.
  9. @Ammonia Do you have some pictures of the board with the bypass and link to the replacement MOSFET with better power ratings?
  10. Yes, I saw NicoD's review - very interesting. Really cool presentation by Igor. @Igor @NicoD do you guys know what make and model the donated ARMs server is? I'm really interested on these type pf boards because of my line of work. Squeezing efficiency (instructions/watt) is turning into a big deal. Data centers are trying to reduce costs and energy efficient servers are becoming a big part of it. Designing and building scalable and highly available systems for telecommunications, makes up a good part of the projects I'm constantly involved in and most of the work loads can be architecture agnostic so ARM server are good candidates (this is why I mentioned the PANDA B1000N) MIPS will eventually catch-up and hopefully become a bit more mainstream and give people more choices.
  11. Good day everyone. I'm looking for your recommendations on a not too expensive ARMs powered board. - Preferably 16 or more cores (big.LITTLE mix is fine) - Cortex-A53/A55 or better. - 16GB of RAM or higher - NMVe support - Support for mounting several boards on U1 shallow spaces (depth of 25cm [10 inches] or less) - Support for booting Armbian and CentOS/Fedora Main purpose - system development (Linux, Java, Scala, Go, RUST), Kubernetes, database and overall platform tinkering. The Bamboo Systems - PANDA B1000N looks really nice, but I'm not sure it is in the modestly priced range - unless thinking that paying upfront for the board will save me $$$ on the electricity bill. Any comments and suggestions are welcomed.
  12. What problems did you get? I found a post from 3 year ago - thou it was made for CentOS it contains a basic setup for ZFS and iSCSI, these steps work on Armbian as well. zfs create -o volblocksize=32k -V 10G tslpool/iscsi1 zfs set sync=disabled tslpool/iscsi1 targetcli block/ create name=block_backend dev=/dev/zvol/tslpool/iscsi1 cd /iscsi create iqn.2017-11.com.mydomain.ad.zfstest:iscsidisk1 cd /iscsi/iqn.2017-11.com.mydomain.ad.zfstest:iscsidisk1/tpg1/acls # create acl with the initiator (client) name here, not the one you just created create iqn.1991-05.com.microsoft:dc1.ad.mydomain.com cd iqn.1991-05.com.microsoft:dc1.ad.mydomain.com set auth userid=user set auth password=12to16characters cd /iscsi/iqn.2017-11.com.mydomain.ad.zfstest:iscsidisk1/tpg1/luns create /backstores/block/block_backend cd / ls saveconfig exit systemctl enable target.service systemctl restart target.service firewall-cmd --permanent --add-port=3260/tcp firewall-cmd --reload
  13. @wurmfood You should be able to use a ZVOL or create a file on the dataset that represent the target (blockio and fileio) respectively.
  14. This discussion is interesting because I can relate to both sides. As an end user - having multiple filesystems to choose from is great, choosing the right one is where I need to spend my time choosing the right tool for the task. Having a ZFS DKMS is great, but if after an update my compiler is missing a kernel header, I won't be able to reach my data. Shipping a KMOD (with the OS release) might give me access to my data after each reboot/upgrade. The ECC/8GB RAM myth is getting old but it has garnered enough attention that most newbies won't read or search beyond the posts with most views. Armbian as a whole is always improving - a few weeks ago iSCSI was introduced for most boards (and helped me replace two x86_64 servers with one Helios64) - and an implementation of ZFS that works out of the box will be added soon enough. That being said, this is a community project - if a user wants 24x7 incident support, then maybe the ARM based SBCs + Armbian are not the right choice for them. Having a polite discussion with good arguments (like this thread) is what gets things moving forward - We don't have to agree with all the points, but we all want to have stable and reliable systems as our end goal.
  15. If you have a second microSD, you can flash the new OS there and keep your old microSD as backup - taking an image of the microSD is possible too. Use the dd command. If our information is already on the software raid - you should be able to back up and remount the drives without issues. I don't use OMV, but you should be able set it up again with out issue.
  16. @snakekick, having the kernel swappiness set to 100 on systems where the swap is implemented as compresses RAM is normal. You want the pages that have been swapped out to be compressed and stored in RAM to make the swap-in operation as fast as possible (decompressing the page is faster than reading it first from disk). Since the storage for some of these devices is on the slow side (microSD, eMMC) - having the swap on RAM tends to speed up the memory operations (swap-in & swap-out), while at the same time helping to avoid unnecessary wear on your flash storage.
  17. Angel, Most SATA drives should work out of the box - it's possible that at the time when the specs were written the Kobol team only had access to drives up to 16TB in size. 18TB drives should be no problem for modern filesystems (EXT4,XFS, ZFS, etc.) - The only real issue you might have would be the power drawn from the power supply at startup. Give it a try - connect the drive into the NAS and it should be listed as a device with the command 'lsblk'.
  18. SIGSEGV

    ZFS on Helios64

    @Demodude123 It might be worth a try this approach to load the module on boot sudo sh -c "echo zfs >/etc/modules-load.d/zfs.conf" @deucalion @Demodude123 Were you able to make a deb package with the kmod?? The dmks is nice, but a kernel module to match the Armbian release would probably be better for end users. @Igor what would your thoughts be on this matter? I'm aware that not all armbian supported hardware might benefit from it since not all are used for storage purposes, but those that are could have a new option for the filesystem.
  19. SIGSEGV

    ZFS on Helios64

    @0utc45t thanks for the update - those are great news.
  20. SIGSEGV

    ZFS on Helios64

    @0utc45t, Looking forward to your results.
  21. SIGSEGV

    ZFS on Helios64

    I agree with @TRS-80. Some topics are better documented with a small How To post or even within the Wiki pages of the Kobol/Helios64 projects. That being said - I will post how to get iSCSI targets published on Armbian - now that the new kernels has been released, hopefully it will be made sticky for others wanting to do the same. Regarding the recent release of ZFSon Linux - let's try out and document our findings. I will for sure test it out and come back here to document how it went.
  22. SIGSEGV

    ZFS on Helios64

    With yesterday's release of ZFSon Linux 2.0, shouldn't all of this be easier? I'm looking forward to seeing performance and stability improvements with the new version - as well as ease of deployment.
  23. I upgraded and it's working fine for me. I have configures iSCSI and replaced about 6 virtual machines by moving their services into the Helios64. I have to say that PostgreSQL 13 runs very well with the loads being spread across all cores on the system. Now I just have figure out how to reconfigure the UniFi controller to run either as a docker image or as another service (leaning towards a container at this point).
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines