allen--smithee

  • Posts

    24
  • Joined

  • Last visited

Reputation Activity

  1. Like
    allen--smithee got a reaction from iav in Very noisy fans   
    @gprovost
    Is it possible to know the characteristics of the thermal bridge?
    (W.mK et thickness)
     
    @bunducafe
    You can use your helios64 without fan with a CPU limitation following :
    # 816Mhz and 1Ghz (eco)
    # 1.2Ghz CPU 100% Temp <82 ° (safe)
    # 1.41Ghz CPU 100% Temp <90 ° (Limit)
     
    not viable :
    # 1.6Ghz CPU100% Temp > 95 ° reboot and reset fancontrol config /etc and there I regret that it is not a K.
    Nevertheless, it is reassuring to see that the protection method works.
     
    From my own personal experience, it is not necessary to change the fans immediately
    and you will quickly agree thereafter that the noise of the fans is erased by the noise of a single rotating hard disk.
    But if you use it also as a desk with SSD like me, you would definitely want to use it without limitation.
    In that event you must familiarize yourself with Fancontrol otherwise you will also be disappointed with your Noctua or any fan.
  2. Like
    allen--smithee reacted to gprovost in Kobol Team is taking a short Break !   
    It’s been 3 months since we posted on our blog. While we have been pretty active on Armbian/Kobol forum for support and still working at improving the software support and stability, we have been developing in parallel the new iteration of Helios64 around the latest Rockchip SoC RK3568.
     
    However things haven’t been progressing as fast as we would have wished. Looking back, 2020 has been a very challenging year to deliver a new product and it took quite a toll on the small team we are. Our energy level is a bit low and we still haven’t really recovered. Now with electronic part prices surge and crazy lead time, it’s even harder to have business visibility in an already challenging market.
     
    In light of the above, we decided to go on a full break for the next 2 months, to recharge our battery away from Kobol and come back with a refocused strategy and pumped up energy.
     
    Until we are back, we hope you will understand that communication on the different channels (blog, wiki, forum, support email) will be kept to a minimum for the next 2 months.
     
    Thanks again all for your support.
  3. Like
    allen--smithee reacted to SIGSEGV in Feature / Changes requests for future Helios64 board or enclosure revisions   
    My comment might be late to the party - if there was a possibility to add an optional display and a few user-configurable buttons to the Front Panel, that would be great.
    I know it would mess a bit with the airflow, but it could be used for system monitoring and few other specific use cases.
  4. Like
    allen--smithee reacted to Polarisgeek in Does anyone actually have a stable system?   
    Just wanted to add my experience as maybe someone can get something semi-useful out of it. 
     
    I started out with 3 - 4TB drives with 2 of them in Raid 1 and the 3rd on it's own.  I installed OMV and CUPS on a Micro SD card.  Even from the very beginning, I always had trouble restarting the system.  Sometimes it would boot after 3 tries, sometimes it would take 20 tries.  I watched and it was never the same issue twice that caused the boot failure.  I removed drives, plugged in different combo's, several fixes on the forums, anything I could think of and nothing really seemed to make a difference.  The good news was that once it was up and running, it ran great.  I had 2 months of uptime with no issues.  Then i'd run an update and have a heck of a time getting it restarted.  Just figured that's the way it was and hoped things would get better as the software matured.  
     
    I'm now on my second iteration with 5 - 14TB (Thanks Uncle Joe) drives in Raid 6.  After 2 months, i've had 2 random crashes for unknown reasons, one at 3 days and the other after 7 days.  Aside from running updates and rebooting, it's been running solid for me.  I'm only running OMV and a CUPS server.    Getting to this point was a huge PITA.  I spent nearly 8 hours trying to get it up and running over the course of a Sunday.  It seemed like no matter what I did, i'd have a Kernel Panic during the setup process, and then the system wouldn't boot at all giving different errors every time.  So i'd re-download the image, and attempt to install from scratch again.  I played with installing different options, in different sequences (as much as possible), without much luck.  I verified the download every time.  I finally tried using USBImager, as an alternative to BalenaEtcher, and found that wring to the sdcard seemed better and the installation seemed better, although it did panic a couple times.  Once I finally got it running, I gave it some time, installed all the updates, reboot several times in between setting up OMV for testing and have been happy with it since.  The biggest difference now is that I don't worry about rebooting as it comes right up the first time instead of several tries like the first iteration.  
     
    Overall, i've been happy with mine.  I'm very new to the Linux environment so it's been fun learning a new thing.  Keep up the great work!
  5. Like
    allen--smithee got a reaction from hartraft in Helios64 - freeze whatever the kernel is.   
    @tionebrr
    Source : https://www.rockchip.fr/RK3399 datasheet V1.8.pdf
     
    1.2.1 Microprocessor
     Dual-core ARM Cortex-A72 MPCore processor and Quad-core ARM Cortex-A53MPCore processor, both are high-performance, low-power and cached application processor
     Two CPU clusters.Big cluster with dual-coreCortex-A72 is optimized for high-performance and little cluster with quad-core Cortex-A53 is optimized for low power.
    <... >
     PD_A72_B0: 1st Cortex-A72 + Neon + FPU + L1 I/D cache of big cluster
     PD_A72_B1: 2nd Cortex-A72+ Neon + FPU + L1 I/D cache of big cluster
    <... >
     PD_A53_L0: 1st Cortex-A53 + Neon + FPU + L1 I/D Cache of little cluster
     PD_A53_L1: 2nd Cortex-A53 + Neon + FPU + L1 I/D Cache of little cluster
     PD_A53_L2: 3rd Cortex-A53 + Neon + FPU + L1 I/D Cache of little cluster
     PD_A53_L3: 4th Cortex-A53 + Neon + FPU + L1 I/D Cache of little cluster
    <...>
     
    3.2 Recommended Operating Conditions
    The below table describes the recommended operating condition for every clock domain.
    Table 3-2 Recommended operating conditions
    Parameters Symbol Min Typ Max Units
    Supply voltage for Cortex A72 CPU BIGCPU_VDD 0.80 0.90 1.25 V
    Supply voltage for Cortex A53 CPU LITCPU_VDD 0.80 0.90 1.20 V
    Max frequency of Cortex A72 CPU 1.8 GHz
    Max frequency of Cortex A53 CPU 1.4 GHz
     
  6. Like
    allen--smithee got a reaction from tionebrr in Helios64 - freeze whatever the kernel is.   
    @tionebrr
    Source : https://www.rockchip.fr/RK3399 datasheet V1.8.pdf
     
    1.2.1 Microprocessor
     Dual-core ARM Cortex-A72 MPCore processor and Quad-core ARM Cortex-A53MPCore processor, both are high-performance, low-power and cached application processor
     Two CPU clusters.Big cluster with dual-coreCortex-A72 is optimized for high-performance and little cluster with quad-core Cortex-A53 is optimized for low power.
    <... >
     PD_A72_B0: 1st Cortex-A72 + Neon + FPU + L1 I/D cache of big cluster
     PD_A72_B1: 2nd Cortex-A72+ Neon + FPU + L1 I/D cache of big cluster
    <... >
     PD_A53_L0: 1st Cortex-A53 + Neon + FPU + L1 I/D Cache of little cluster
     PD_A53_L1: 2nd Cortex-A53 + Neon + FPU + L1 I/D Cache of little cluster
     PD_A53_L2: 3rd Cortex-A53 + Neon + FPU + L1 I/D Cache of little cluster
     PD_A53_L3: 4th Cortex-A53 + Neon + FPU + L1 I/D Cache of little cluster
    <...>
     
    3.2 Recommended Operating Conditions
    The below table describes the recommended operating condition for every clock domain.
    Table 3-2 Recommended operating conditions
    Parameters Symbol Min Typ Max Units
    Supply voltage for Cortex A72 CPU BIGCPU_VDD 0.80 0.90 1.25 V
    Supply voltage for Cortex A53 CPU LITCPU_VDD 0.80 0.90 1.20 V
    Max frequency of Cortex A72 CPU 1.8 GHz
    Max frequency of Cortex A53 CPU 1.4 GHz
     
  7. Like
    allen--smithee reacted to gprovost in SATA issue, drive resets: ataX.00: failed command: READ FPDMA QUEUED   
    @Fred Fettinger Your errors are most likely due too a not stable HDD harness. You can contact us to support@kobol.io to see if replacement of the HDD wire harness is needed.
     
    @ShadowDance Thanks for the feedback and at least we can remove grounding issue from the list of possible root causes.
    Looks like that in the use case of very heavy HDD I/O load arising mainly during scrubbing operation too much noise is generated resulting in those HSM violation.
    Thanks to all your tests, the issue seem unfortunately to point to noise filtering issue. As previously mentioned, we will fix that in next revision.
    We will see if the new SATA controller firmware has any impact but we doubt that. I think the only solution for current revision is to limit ATA speed to 3Gbps when using btrfs or zfs.
  8. Like
    allen--smithee reacted to deanl3 in nand-sata-install to eMMC, won't start kernel   
    @gprovost Fantastic, that did the trick, thank you!
    Not sure how that got in there either. Strangely, those lines are present on the armbianEnv on my SD card and were not causing an issue.
     
    Thanks!
  9. Like
    allen--smithee reacted to NickS in Does anyone actually have a stable system?   
    Stable System: Absolutely
    I'm running with all latest maintenance & OMV5.
    Linux 5.10.21-rockchip64, OMV 5.6.2-1(Usul)
     
    ---- but I'm keeping things very simple...
    NO RAID
    4 x HDD ALL THE SAME
    NO ZFS
    BOOT FROM SD 
    AUTO SHUTDOWN & RESTART EACH 24 hours 
     
    -- until I get to the apps
    21 Docker containers running various apps & services.
     
    I've had one docker image fail to come up on a couple of occasions.
     
    So ... I'm a very happy customer.
    My Data resilience doesn't come from RAID (which I really don't like 'cos 8TB disks take forever to rebuild).
    I just backup critical data to my old trusty Helios4! 
     
  10. Like
    allen--smithee reacted to scottf007 in ZFS or normal Raid   
    Hi All, 

    I am on my Helios64 (already have a Helios4). 

    I am running 2 x 8TB, 1x 256 M2, OMV5 debian etc.
     
    I have ZFS running (from the wiki instructions) in a basic mirror format, and if I add a few drives I think it would still be a mirror, however I have the following question. It seems far more complicated than MDADM, and potentially more unstable (not in terms of the underlying technology, but in terms of changing these kernals etc every week). 

    Do you think for an average home user that this is really worth it or will constantly need work? To change it would mean starting again, but I do not want to change the setup every month and would intend to keep it stable for media, and backing up some stuff for the next few years. Or if it is working it should be fine for the long term?
     
    Cheers
    Scott
  11. Like
    allen--smithee reacted to Werner in Unable to boot   
    If you refuse to provide further information for debugging as mentioned above it is quite hard to help you. Noone here is a clairvoyant
     
  12. Like
    allen--smithee got a reaction from gprovost in Very noisy fans   
    The probleme of this post is resolved !!
    Your Fans with an efficient thermal pad and ssd disks is 22w and 10db peak.
    I very rarely exceed 12w over a Day and the unit is completely inaudible.
    Except for doing these tests which does not at all reflect the reality of normal use. 
    Please Kobol make a 2.5 inch version case for Helios. I think will be perfect for as a solution for my home family. (I think of my children in particular and their father .) 
     
    My ssd and HDDs disks all stay below 40 ° during writing.
  13. Like
    allen--smithee reacted to Gareth Halfacree in Encrypted OpenZFS performance   
    Your MicroServer has either an Opteron or Ryzen processor in it, either one of which is considerably more powerful than the Arm-based RK3399.
     
    As a quick test, I ran OpenSSL benchmarks for AES-256-CBC on my Ryzen 2700X desktop, an older N54L MicroServer, and the Helios64, block size 8129 bytes.
     
    Helios64: 68411.39kB/s.
    N54L: 127620.44kB/s.
    Desktop: 211711.31kB/s.
     
    From that, you can see the Helios64 CPU is your bottleneck: 68,411.39kB/s is about 67MB/s, or within shouting distance of your 62MB/s real-world throughput - and that's just encryption, without the LZ4 compression overhead.
     
  14. Like
    allen--smithee reacted to SIGSEGV in Very noisy fans   
    @allen--smithee Thanks for the feedback.
  15. Like
    allen--smithee got a reaction from SIGSEGV in Very noisy fans   
    The probleme of this post is resolved !!
    Your Fans with an efficient thermal pad and ssd disks is 22w and 10db peak.
    I very rarely exceed 12w over a Day and the unit is completely inaudible.
    Except for doing these tests which does not at all reflect the reality of normal use. 
    Please Kobol make a 2.5 inch version case for Helios. I think will be perfect for as a solution for my home family. (I think of my children in particular and their father .) 
     
    My ssd and HDDs disks all stay below 40 ° during writing.
  16. Like
    allen--smithee got a reaction from SIGSEGV in Very noisy fans   
    @ gprovost
    As we might expect, there is a little spread of the pads on the outer edges of the processor, but also on the edge of the radiator
    and so you were right, there is no need to leave the inductors bareheaded.
    Now I think 19x19 is enough for the dimensions of the cpu thermical pad with a 1.5mm. 
    I redid the separation between the CPU Pad and the rest of the board and put pieces of pad in the slots of the inductors. 
    You don't know if it will be possible so, nevertheless now we know what we need for our next blends at home ;).
     
    P6 and P7> PWM = 35
    P6 & P7> PWM = 50 is my new PWMMAX on Fancontrol
    P6 et P7> PWM = 255
     
     
    @SIGSEGV
    If you are interested in this solution.
    I recommend TP-VP04-C 1.5mm for your helios64 (2 plates of 90x50x1.5mm)
     
     
  17. Like
    allen--smithee got a reaction from clostro in Very noisy fans   
    @ gprovost
    As we might expect, there is a little spread of the pads on the outer edges of the processor, but also on the edge of the radiator
    and so you were right, there is no need to leave the inductors bareheaded.
    Now I think 19x19 is enough for the dimensions of the cpu thermical pad with a 1.5mm. 
    I redid the separation between the CPU Pad and the rest of the board and put pieces of pad in the slots of the inductors. 
    You don't know if it will be possible so, nevertheless now we know what we need for our next blends at home ;).
     
    P6 and P7> PWM = 35
    P6 & P7> PWM = 50 is my new PWMMAX on Fancontrol
    P6 et P7> PWM = 255
     
     
    @SIGSEGV
    If you are interested in this solution.
    I recommend TP-VP04-C 1.5mm for your helios64 (2 plates of 90x50x1.5mm)
     
     
  18. Like
    allen--smithee got a reaction from gprovost in Very noisy fans   
    @gprovost
    my Cpu + 2disks fan will always have a PWMMIN=35
    my intention is to decrease PWMMAX and to delay the intervention of active ventilation.
     
    Before, solicited the cpu made the fans roar, this is no longer the case today.
    I can perform tasks with the first 5 minutes of a 100% CPU and the unit remains silent and afterwards I don't need a big air flow to stay cold.
     
    cat / dev / thermal-board / temp1_input indicates:
     10 ° less than the CPU during stress.
     1 ° less than the CPU at rest.
    I have to perform a long test to confirm but I think I can maintain Tcpu100% < 70° (Tboard < 60°) with only PWMMAX = 50 on fan-p6. 
     
    There are certainly some points to improve concerning the thickness, in my unit, I used a thickness of 1.5 mm for the whole surface.
    I realized that the inductors were high points on the PCB.
    My intention was to remove the thermal pad on top so that it would be in direct contact with the radiator.
    It would be relevant to try with 2mm in order to also cover the inductors from the top. 
     
    It is planned to dismantle it in a week to see the contact points and check the height in the gel.
    unfortunately the gel has already sagged, I can't modify the height of the radiator with the elements unless I do a modeling pad workshop,
    but I can crush a very thin layer of pad at the top of inductor to avoid an air cushion. 
    If necessary I have a second Gelid Pad 90x50x1.5 but I would like to keep it for the next one 
     
    the 3W solution does the job, it's not the most efficient (not to say an insulator) but it's an economical solution,
    and intended for most people who use traditional Hard Disk Drives that require active ventilation to improve the life span.
    My use is particular, after all my unit screws into a living room and uses SDD that heats up little.
    But it's a point to be improved indeed and if you charge an extra 10$ for a 6W pad you can be sure that I'll take it off to put a better and I'll tell you that your solution was crap.
  19. Like
    allen--smithee reacted to gprovost in Very noisy fans   
    @allen--smithee Actually what you are doing is not ideal since now the inductors (little squary components that appears through your thermal pad) are not able anymore to dissipate heat via the heatsink. These inductors generate quite a lot of heat and it will spread to LPDDR4 and PMIC trough PCB. The purpose of the Helios64 heatsink is obviously not to just dissipate heat for the SoC but for all other key components (LPDDR4, SATA controller, USB-to-LAN, etc...).
     
    Here your measurement is only from the SoC point of view, which is not necessary the best way at looking at overall thermal management. Could you add back some thermal pad on the inductors and re-run your thermal measurement. It would be interesting to see if you see the same thing afterwards.
     
    In any case we will change thermal pad supplier, we are not really happy by the current one.
     
  20. Like
    allen--smithee got a reaction from SIGSEGV in Very noisy fans   
    After one hour of disassembly, cleaning, cutting, installation and reassembly.
    My helios64 has gelid thermal pad GP-Ultimate solutions whose manufacturer boasts a small 15W.mK.
     
    I think I just solved my ventilation problem for this generation and the following ones.
    I will do the tests within a week but for the moment Helios64 remains very cold even under full load.
  21. Like
    allen--smithee reacted to gprovost in Very noisy fans   
    Around 3W/m-K. Dimension and thickness below , the small 21x21x1mm square is the one above the RK3399 SoC :
     

     
     
    Let's clarify, you can use Helios64 board in passive cooling mode on its own, but if the board is installed in the provided enclosure along HDDs device then you definitely need active cooling.
  22. Like
    allen--smithee got a reaction from gprovost in Very noisy fans   
    hi @bunducafe
    in order of price, time and efficiency. 
    a) you can play with the parameters of fancontrol to find a passive / active fan compromise, and limit the rotational speed and therefore the noise of the fans. (/etc/fancontrol). 
    b) you can also lower the frequency of the processor to reduce its TDP, (armbian-config)
    c) i do not know the specifications of the thermal bridge (W.mK and thickness) between the CPU and the radiator, maybe this can be replaced to improve thermal conductivity between them. (<10euro)
    d) New Fans (>30euros)
     
     
  23. Like
    allen--smithee reacted to bunducafe in Very noisy fans   
    Hi folks,
     
    I am fairly new here, reading, trying to understand but do have some knowledge with Unix and some SBC. Now the Helios64 is on arrival and I would like to know if I should change the fans immediately in order to get a quieter case. 
     
    Is the NF-A8-PWM significantly less noisy than the stock ones? Or is there maybe a different route to go?! 
  24. Like
    allen--smithee reacted to SIGSEGV in Feature / Changes requests for future Helios64 board or enclosure revisions   
    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.
  25. Like
    allen--smithee reacted to RlndVt in Feature / Changes requests for future Helios64 board or enclosure revisions   
    A 2.5" variation for either a SSD based NAS; or a low power NAS with 2.5" HDD's. Of course the current design could be used for 2.5" drives, but a more compact design would be nice.