Posts by vishnumrao


    As the name "hd_idle" says, I assume that a spindown command is only issued when the disk is idle. Anything else doesn´t make any sense. In the readme of hd_idle one can read "hd-idle is a utility program for spinning-down external disks after a period of idle time". hd-idle utility, modified to use hdparm tool to spin down disks

    I just went with the brief description on the github page that said "hd-idle utility, modified to use hdparm tool to spin down disks" I guess I should RTFM. :-). Thanks for the clarifications.

    @cabrio_leo thanks for the tip on hd_idle. I finally got around to trying your tip on the RPI NAS. Installed hd_idle and the disks now spind down completely. This is good.

    One question: does hd_idle only spindown the disks when they are idle or does it just count down a time set in the config file and periodically issues a spindown command? I am a bit concerned that a spindown maybe issued in the middle of an io transfer operation.

    Thank you for the info.

    I am planning to set up a RAID5. I am planning to start with 3 drives and then add a 4th drive. Yeah as you said, I will have a full backup on a separate location before attempting a grow operation.

    GUIInstall drive -> Storage Disks -> Wipe (Short)
    Raid Management -> Select Raid -> Recover -> Add new drive
    When sync has finished Raid Management -> Select the raid -> Grow
    Then, File Systems -> Select the raid -> Resize

    Does this instruction delete the data ? I mean the "Wipe (Short)" is whats driving my question.

    This is down by the USB to SATA bridge controller in the external USB case and independently to your spindown settings in OMV. This is a very common behavior of many USB cases as I have written above.


    Wow, I did not know USB to SATA enclosures altered the drive behavior. Weird. I wonder why they would do it, rather than leave it to the OS or drive to behave in their default states.

    Sorry my explanation was a bit unclear I guess. The heads first unload/park with a click about a minute or two after IO stops. Then about 9-10 minutes later the disk spins down. I can hear the spindown. But if I listen closely I can still hear the disk spinning. I think its going to a low RPM speed. It stays there infinitely.

    Now if I issue a hdparm -Y command the disk fully spinsdown. This is corroborated by the power as well.

    IO in progress on both hdd - 19-20W
    Heads parked - 15W
    Low speed spin - 12W
    Full spindown after hdparm -y command - 8W.

    Hope this clarifies.

    I looked into the SMART polling time. My smart poll time is set to 3600 i.e. once every 60 minutes, if the drive is not in standby. So that is certainly not the issue. My HDDs are set to spindown after 10 minutes.

    To better observe the behavior of the disks I moved the Pi and the disks to my desk. I can listen to the drives better this way. I have also connected a killawatt to monitor power changes.

    After making these changes, I notice that after a few minutes, there is a click and the heads are likely parked at this time. I don't know why it does this, since its much less than the 10 minutes I set. Then after about 10 minutes the disks spindown. But its not spinning down completely.
    I can also see the power coming down in steps. From about 19-20 when both HDD are in use to about 15W after heads are parked, and then finally to about 12W.

    I wonder if its something set as a default in the HDD firmware? the default value for APM on this HDD is 0x01

    I recently set up OMV 5 on an AMD system (A75m-itx motherboard). it has 4x SATA ports. OMV 5.x is installed on USB connected SSD. After playing a bit with this system, I am now ready to add HDDs to it.

    I have 3x HGST 2TB (HDS5C3020ALA632) hard drives. I believe these are 5940 RPM.
    I also have 1x 2TB HGST drive (HDS722020ALA330). This is a 7200 RPM drive.

    My intention is to create a RAID5. So 4x TB drives resulting in a 6TB data volume. All my data will be backed up to a 6 TB USB connected external hard drive.

    Question: Is it OK to create a RAID with drives that have different RPM speeds?

    Thanks for the response. I did a manual "hdparm -Y /dev/sda" and "hdparm -Y /dev/sdb". I could hear the click and the drive spin down. No issues.

    Also as I had reported in my original post, if I reboot and do no SMB/CIFS access, the drives would go into a spindown after about 10 minutes.

    So it definitely is something on the pi thats keeping the disks from spinning down.

    I am trying to setup a RPI3 based OMV NAS for a friend. His needs are very basic. He wants to backup pic from his phone whenever his phone runs out of space. The RPI is connected wire connected to the router. Speeds hit 11.5 MB/s and its sufficient to meet my friends need.

    Two 320 GB Hitachi (HDT725032VLA380)hard disks are connected. They are inside a 2 bay USB case (a dual bay USB 3.0 case Ultra U12-43846).

    I have one user on the NAS and on 320 GB HDD is exposed as a SMB/CIFS share.

    Problem statement: The primary hard disk won't spind down after an access by SMB/CIFS user. But other hdd seems to be going into spindown.

    If I reboot and have no activity then both HDDs will spindown. But SMB/CIFS access will wake up drive and then after that that HDD will never spindown.

    Anyidea why the spindown is prevented?

    Note: SMART monitoring is enabled. But disabling it makes no difference.

    Yeah. I might have to live with some extra steps to go save some power. Though energy is not super expensive where I live, my conscience pricks me when I waste power!

    WOL can be triggered in different ways.
    Some advanced routers have it integrated in their WebUI, or you could use an app from your smartphone.

    You could also schedule a wake up, there's a plugin for that.

    Thanks for the response.

    I can trigger through router, or desktop application etc. But those are some extra steps to be accessing a shared network drive. I guess thats the price to pay to be putting the system on suspend.

    Scheduling a wake up is a good idea. But my use case is mostly random. Need to access on demand.

    I recently set up OMV 5 on an AMD system (A75m-itx motherboard). It connects through the onboard Gbit capable NIC. Its an RTL8111E. I have the autoshutdown plugin installed and suspend after set time works.

    However I don't know how to wake up the system once it goes into suspend. Since the machine has suspended, I don't see it having an IP address (from my routers list of connected clients). Also it does not advertise any network drives on the routers network.

    At first I thought I was doing something wrong in my BIOS setting or my motherboard did not support or some error on my end. But after endlessly looking on the web, I came across this wiki article, which pointed me to a wol application. This application wakes up my OMV system from suspend. So clearly this application sends some "magic packet" which wakes up the system.

    Question to the community: How do you wake up your NAS systems once the machine is suspended?

    My use case is that I have 5 clients connecting to the SMB share on the network. One is a Ubuntu desktop, W10 laptop, Kodi running on a RPI, one android phone, one iphone.

    The phones connect to the SMB share primarily to dump pics on to the SMB share. While I certainly want to suspend the system when not in use, I don't want to always use a command line application to wake up my system and then access the shared drive. Any insights on how to best to wol the system?

    The problem was that I did not check the BIOS right. It had a second entry that was necessary to enable, it was for PCI power on, although the Realtek Ethernet is no PCI card. I found a hint on some blog. WOL now works fine together with autoshutdown!

    Hello, I have an ASrock motherboard and can't get WOL working. Would you please explain the BIOS settings that helped you? Maybe with screenshot? And maybe link the hint you found on the web that lead to the resolution of your issue?

    It did not work.

    Just out of curiosity I did a clean install. Ran all the updates and tried the rsync. It works now. Triggers as expected.

    I have created a backup image via dd. Just in case it stops working again.

    I set up the following:
    N trigger
    minutes to 5
    trial run only (my target directory has a years worth of pics, also backed up on a separate hdd).

    I am able to get it to trigger. I am seeing entries in the rsync jobs log 5 minutes apart.

    So somethings wrong when only time is set without the N trigger.

    Edit: I removed the N trigger and rsync does not trigger.

    @macom Yes, its enabled. I had tried a trial run by manual execution. It ran fine. I will double check today.

    @Adoby Sorry I haven't responded to your comment. Thanks for the input. But the use case here is very simple. Keep content on main NAS drive mirrored everyday. Also I am setting this up for a friend. So I plan to stick to using the GUI. In case he needs to fiddle around with it.