Jump to content

Kosmatik

Members
  • Posts

    6
  • Joined

  • Last visited

Posts posted by Kosmatik

  1. 18 hours ago, Igor said:


    You need to update boot loader in any case. Recent eMMC cards have updated bootloader and it works out of the box ... we will provide updating eMMC from armbian-config, but it's not implemented yet. You will need to boot once from SD card with attached eMMC and update boot loader on eMMC from menu (or manually). Than you are done and you can either write IMG to eMMC or install via our nand-sata-install utility.

     

    BTW. We solved only low level problem and boot loader, once you have the system running on eMMC is being updated.

     

     

    EDIT: Just compiled 4.9.46 and it worked.

     

    Sorry I should've said this. I had 4.9.37 running fine from emmc, updating it to 4.9.44 caused it to not boot.

     

    I've tried uncommenting boot.ini setting to update emmc again, but that did not help.

  2. @tkaiser I did actually read your response. I think if the JMS561 things get sorted out, then it'll be plenty enough for what I use it for. It's used as a media storage and streamer, my important data is backed up in multiple places.

     

    What attracted me to the Cloudshell2 was that it's a complete package. I was looking at the ClearFog Pro/Base but ended up not getting it due to not wanting to design and 3d print an enclosure that holds it and the HDDs.

     

    However, this all might be moot if Helios4 gets funded.

  3. Ok, I figured out what's causing it.

     

    The bridge is JMS561.

    OMV pulls this for all drives when the Devices tab is clicked.

    smartctl -x /dev/sda -d sat

     

    Running this manually I can also crash it.

     

    Specifically this:

     

    smartctl -l devstat /dev/sda

    crashes here:

    root@openmediavault:~# smartctl -l devstat /dev/sda -d sat,12
    smartctl 6.4 2014-10-07 r4002 [armv7l-linux-4.9.30-odroidxu4] (local build)
    Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
    
    ATA_READ_LOG_EXT (addr=0x00:0x00, page=0, n=1) failed: 48-bit ATA commands require SAT ATA PASS-THROUGH (16)
    Read GP Log Directory failed
    
    Device Statistics (SMART Log 0x04)
    Page Offset Size         Value  Description
    ATA_SMART_READ_LOG failed: Connection timed out
    Read Device Statistics pages 0-7 failed

    It still appends -d sat even if the bridge is defined in the .h file.

     

    What would be the (potential) fix? Update of smartmontools?

     

    EDIT: Hard drive issues probably.

     

    Running the same command on /dev/sdb does not cause the crash.

  4. Hello Everyone,

     

    As @tkaiser is probably aware from the hardkernel forum, I'm having issues with USB/SMART and OMV.

     

    Basically, USB resets whenever SMART data is pulled from OMV's web interface, it works fine if I manually do it in shell.

     

    Here is some info.

     

    http://sprunge.us/HdbK

     

    I was proposed to update smartmontools to 6.5, but there are library dependencies that are missing. 

     

    If any of you fine folks have any ideas as to what could be causing it, I would be grateful.

     

    Thank you

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines