Jump to content

JeffDwork

Members
  • Posts

    11
  • Joined

  • Last visited

Posts posted by JeffDwork

  1. Helios64, power supply, case, pink plastic drive hardware.

     

    Limitations: Must run with min CPU speed = max CPU speed = 1200000, CPU governor = performance

    Has been tested with one disk running bonnie++ to a second Helios64 for many days with no errors.

    $200 USD + shipping.

    I will use escrow.com (I pay fees) to ensure that you get the equipment and I get the money :-)

  2. Anyone know a solution for this?

    Linux vlib2 5.9.14-rockchip64 #20.11.4 SMP PREEMPT Tue Dec 15 08:52:20 CET 2020 aarch64 aarch64 aarch64 GNU/Linux

     

    Jan 08 14:27:05 vlib2 systemd[2481]: Starting Timed resync...
    Jan 08 14:27:05 vlib2 profile-sync-daemon[11324]:  WARNING: Do not call /usr/bin/profile-sync-daemon as root.
    Jan 08 14:27:05 vlib2 systemd[2481]: psd-resync.service: Main process exited, code=exited, status=1/FAILURE
    Jan 08 14:27:05 vlib2 systemd[2481]: psd-resync.service: Failed with result 'exit-code'.
    Jan 08 14:27:05 vlib2 systemd[2481]: Failed to start Timed resync.
     

  3. I am truly sorry to have implied that I was asking for my trivial bug to be fixed. I know that your time is precious and that this project is vast. 

    The goals of my post:

    * Inform other users of a problem. I have edited my original post to include a work-around.

    * Determine where to post bug reports - I now understand why that's not possible for trivial issues.

    * Perhaps another user might know offhand where these counters are incremented and would reply with "look in file xyz". This would give me a start on fixing the problem myself. I had, and have, no expectation that the core team would fix this unless it happens to be related to a high-priority problem.

    * I only posted here because the bug appears to be in armbian kernel code as I do not observe it x86 ubuntu.

     

    Thank you for all that you do.

    Sincerely,

    Jeff

  4. In both Buster and Focal 20.11.1 on helios64 commands directed to a disk increment fields in /proc/diskstats

    This is incorrect and does not occur in the x86 version of xubuntu Focal 20.04.1.

     

    Specifically (see https://www.kernel.org/doc/Documentation/iostats.txt for field descriptions.):

      Check Power Mode increments "number of reads completed"

      Smart Return Status, Smart Read Data, and Smart Read Log increment "number of reads completed" and "number of sectors read"

    The smartd disk monitor uses these commands which makes the disk appear to be active to programs like hd-idle.

     

    The work-around is to set the inactive interval in hd-idle to something shorter (20 min, for example) than the polling interval of smartd (30 min default).

     

    I would like to track this down but I need some help finding where these counters are incremented.

     

    Is there a better place to report bugs like this than in this forum?

     

    Thanks,

    Jeff

  5. In both Buster and Focal 20.11.1 on helios64 commands directed to a disk increment fields in /proc/diskstats

    This is incorrect and does not occur in the x86 version of xubuntu Focal.

     

    Specifically (see https://www.kernel.org/doc/Documentation/iostats.txt for field descriptions.):

      Check Power Mode increments "number of reads completed"

      Smart Return Status, Smart Read Data, and Smart Read Log increment "number of reads completed" and "number of sectors read"

    The smartd disk monitor uses these commands which makes the disk appear to be active to programs like hd-idle.

     

    I hope this is the correct place to report this bug. 

     

    Thanks,

    Jeff

     

  6. 12 hours ago, GaryC said:

    Loading Environment from MMC... *** Warning - bad CRC, using default environment

    I also got this warning. After a few seconds of panic I realized it was because the environment section of the MMC was empty. It would be nice to add a note about this to the installation section of the wiki.

  7. What are you all using for stress testing? Is there something better than iozone ? I don't have an array - just 5 individual disks - to be accessed by NFS and samba. I'm running plain armbian ubuntu. I really want to run this thing before I trust it with my data.

     

    Thanks,

    Jeff

  8. Assembled my first (of two) helios64s. I needed to insulate the chassis around the leds, but the USB-C connector fit perfectly into the back panel opening. I noticed a problem with the sata cable for slot 1 where it passes under the chassis to reach the board socket. The chassis has a sharp edge that presses onto the cable, so I padded it with some electrical tape.

     

    cable-chassis.jpg

     

    In the box containing the system board there was a plastic bag with two jumper plugs and two screws and a threaded spacer. What is the purpose of the spacer and screws?

    spacer-and-screws.jpg

     

    I had stability problems using Windows to install OS to eMMC. Windows recognized the eMMC as a storage device for a few seconds after helios64 started but then it disappeared. It finally worked after about 10 tries. I was using a USB3 extension cable to reach my pc - perhaps that was the cause.

     

    Thanks,

    Jeff

  9. 12 hours ago, TDCroPower said:

    After several weeks of testing and trying I finally put my Helios64 into production.
    With the 20.08.10 and the possibility to run the firmware over the eMMC I can finally sleep more calmly again.

     

    And to prevent my wife from killing me because there is a lighting party going on in the hallway I taped the front LEDs with insulating tape...

     

     

    Search on Amazon for LightDims. Stick-on, peel-off semi-transparent plastic film in several different transparency levels - 50%, 15%, 0% (perhaps more levels).

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines