Posts by maciekelga

    I just wondering how to extend life of my disk. But I see is better to left them running all the time instead of spin down and than running again. This are disk recommend for NAS so theoreticly it should be not any problem for them.

    So APM off? No spin down?


    ---edit

    I set up APM to 254, AAM = disable. I see every hour parameter Start_Stop_Count and Load_Cycle_Count are increasing +1.

    Thank You.

    I don`t think my USB to sata controller have a functionality to spin down.

    Generally the NAS could be turned off overnight, let`s say between 1AM and 7AM. During the day, the disk could work, I don't mean saving energy, but saving disk usage. Maybe it would be better to turn off the spin down completely, leave the disks running?

    Hi,

    I'm using a OMV 5 on Raspberry Pi 4 with two WD Red 1T 2.5" disk connected to USB 3.0.


    I'm thinking how to set up correctly in OMV to keep disk in good condition for long time. Most of the time disk are not used. I am using a OMV in my private network to keep some files, as a mapped drives to my laptop, keep some movies or pictures.

    How to set up APM, Smart?

    I think would be good, if I need to use a drive it start up, than working for some time, 20-30 minutes and than again can be switch off. So some kind of wake up for request from any devices.


    Another question is if it is possibe to keep OMV disable in some hours range in auto kode? Let's say to keep OMV off between 00.00 and 6.00AM?


    Maciek

    Yes, I fixed it.



    My problem was low quality SD card, occasionally a crushing system. Finally I bought new SD card SanDisk Extreme Pro microSDHC 32GB 100/90 MB/s A1 V30 U3, install system from begining, since that time everything is fine.

    If you turn on Rock64 and the HDD spins up, but the filesystem is not mounted, can you try mount -a from CLI?


    And what is the output of blkid?

    To be honest I didn`t try mount -a from CLI, only from web interface in scheduled tasks I add a new task with mount -a command.


    Output of blkid


    Code
    /dev/mmcblk1p6: SEC_TYPE="msdos" LABEL="boot" UUID="9EDC-9F0B" TYPE="vfat" PARTLABEL="boot" PARTUUID="fa7b8eca-ad12-475c-8dcf-1c6a59d813fd"
    /dev/mmcblk1p7: LABEL="linux-root" UUID="b8c23142-1f40-4ed3-b46f-9b0c786e5583" TYPE="ext4" PARTLABEL="root" PARTUUID="35eb320a-8fd2-47c0-be33-c4ffe655f753"
    /dev/sda1: LABEL="NAS" UUID="37ed4398-0796-40a6-b01f-a6b35a6111a5" TYPE="ext4" PARTUUID="4c50a175-dc8d-40ef-9d97-64ac98aae56e"
    /dev/mmcblk1: PTUUID="b2dd447e-398e-4430-b563-56a38fa1ed42" PTTYPE="gpt"
    /dev/mmcblk1p1: PARTLABEL="loader1" PARTUUID="4247738d-4f5e-45be-96f6-472a2f59a804"
    /dev/mmcblk1p2: PARTLABEL="reserved1" PARTUUID="152441f4-fbde-4742-a0cd-39bb1b4e8a71"
    /dev/mmcblk1p3: PARTLABEL="reserved2" PARTUUID="9ad6fe91-3f12-4920-baa1-fe2158e7d972"
    /dev/mmcblk1p4: PARTLABEL="loader2" PARTUUID="12a38b07-2d50-4808-9ccc-d9b03eeafca4"
    /dev/mmcblk1p5: PARTLABEL="atf" PARTUUID="b53a4fe9-d373-41d3-a18e-a6dc958b5da1"

    -----edit-----
    Ok, I think I solved a problem modyfing a little bit a hardware site.
    I changed a SATA USB adapter. Previously HDD was powered up from USB 3.0, now adapter have additional USB cable to power up HDD. So one cable is connected to 3.0 as communication, second to 2.0 as power supply.
    I did few times reboot and since now is ok, I will observe it.

    If you turn on Rock64 and the HDD spins up, but the filesystem is not mounted, can you try mount -a from CLI?


    And what is the output of blkid?

    To be honest I didn`t try mount -a from CLI, only from web interface in scheduled tasks I add a new task with mount -a command.


    Output of blkid

    Code
    /dev/mmcblk1p6: SEC_TYPE="msdos" LABEL="boot" UUID="9EDC-9F0B" TYPE="vfat" PARTLABEL="boot" PARTUUID="fa7b8eca-ad12-475c-8dcf-1c6a59d813fd"
    /dev/mmcblk1p7: LABEL="linux-root" UUID="b8c23142-1f40-4ed3-b46f-9b0c786e5583" TYPE="ext4" PARTLABEL="root" PARTUUID="35eb320a-8fd2-47c0-be33-c4ffe655f753"
    /dev/sda1: LABEL="NAS" UUID="37ed4398-0796-40a6-b01f-a6b35a6111a5" TYPE="ext4" PARTUUID="4c50a175-dc8d-40ef-9d97-64ac98aae56e"
    /dev/mmcblk1: PTUUID="b2dd447e-398e-4430-b563-56a38fa1ed42" PTTYPE="gpt"
    /dev/mmcblk1p1: PARTLABEL="loader1" PARTUUID="4247738d-4f5e-45be-96f6-472a2f59a804"
    /dev/mmcblk1p2: PARTLABEL="reserved1" PARTUUID="152441f4-fbde-4742-a0cd-39bb1b4e8a71"
    /dev/mmcblk1p3: PARTLABEL="reserved2" PARTUUID="9ad6fe91-3f12-4920-baa1-fe2158e7d972"
    /dev/mmcblk1p4: PARTLABEL="loader2" PARTUUID="12a38b07-2d50-4808-9ccc-d9b03eeafca4"
    /dev/mmcblk1p5: PARTLABEL="atf" PARTUUID="b53a4fe9-d373-41d3-a18e-a6dc958b5da1"

    Files

    • openmedia.jpg

      (55.11 kB, downloaded 197 times, last: )

    Hi,
    I`m using Rock64 with OMV 4. I observe after reboot from time to time disk is not mounted, is not visible from GUI. I need to disconnect disk, make another reboot, after OMV is running connect disk again - than everything is fine until next reboot.
    Is it any solutions for this problem?
    I setup weekly automatic reboot.

    Hi,
    I have similar problem. I did a weekly reboot, after that disk connected to usb 3.0 is not mounted.
    How should looks instructions for reboot and mount a drive after that?


    Wysłane z mojego NEM-L21 przy użyciu Tapatalka