Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

Staggered Spinup if Parity-Check starts or Spin Up Buttons are used

mgutt
in Feature Requests

Featured Replies

To avoid most of the extreme power peaks I like to see a new Disk Setting, which does the following:

 

1.) If a Parity-Check is started (manually or by schedule), it should access some data of each Disk with a delay of 5 seconds before really starting the Check itself.

 

2.) If someone clicks on the Spin Up Button in the dashboard, it should access some data of each Disk with a delay of 5 seconds

 

 

This could be done by a loop and for example "dd if=/mnt/disk$disk_id of=/dev/null bs=512 count=1".

 

  • Quote
    • Thanks 1
    25 minutes ago, mgutt said:

    If someone clicks on the Spin Up Button in the dashboard

    Just tested on my system using grey arrows under the array its spins drives up sequentially see log below.

     

    image.png.d794f810eb3f97dd74e1c249c88439e6.png

      

    Jul 29 20:26:35 Tower emhttpd: spinning down /dev/sdg
Jul 29 20:26:35 Tower SAS Assist v2022.05.25: Spinning down device /dev/sdg
Jul 29 20:26:36 Tower emhttpd: spinning down /dev/sdf
Jul 29 20:26:36 Tower SAS Assist v2022.05.25: Spinning down device /dev/sdf
Jul 29 20:26:37 Tower emhttpd: spinning down /dev/sdi
Jul 29 20:26:37 Tower SAS Assist v2022.05.25: Spinning down device /dev/sdi
Jul 29 20:26:37 Tower emhttpd: spinning down /dev/sdh
Jul 29 20:26:37 Tower SAS Assist v2022.05.25: Spinning down device /dev/sdh
Jul 29 20:26:37 Tower emhttpd: spinning down /dev/sdk
Jul 29 20:26:37 Tower SAS Assist v2022.05.25: Spinning down device /dev/sdk
Jul 29 20:26:37 Tower emhttpd: spinning down /dev/sdl
Jul 29 20:26:37 Tower SAS Assist v2022.05.25: Spinning down device /dev/sdl
Jul 29 20:26:45 Tower emhttpd: spinning up /dev/sdg
Jul 29 20:26:56 Tower emhttpd: read SMART /dev/sdg
Jul 29 20:26:57 Tower emhttpd: spinning up /dev/sdf
Jul 29 20:27:12 Tower emhttpd: read SMART /dev/sdf
Jul 29 20:27:12 Tower emhttpd: spinning up /dev/sdi
Jul 29 20:27:26 Tower emhttpd: read SMART /dev/sdi
Jul 29 20:27:27 Tower emhttpd: spinning up /dev/sdh
Jul 29 20:27:40 Tower emhttpd: read SMART /dev/sdh
Jul 29 20:27:41 Tower emhttpd: spinning up /dev/sdk
Jul 29 20:27:54 Tower emhttpd: read SMART /dev/sdk
Jul 29 20:27:55 Tower emhttpd: spinning up /dev/sdl
Jul 29 20:28:06 Tower emhttpd: read SMART /dev/sdl

     

  • Quote
    • Author

    @SimonF

    Is this a new feature of Unraid 6.9?

     

    My productive server is still on 6.8: 

    Jul 29 21:44:30 thoth emhttpd: Spinning up all drives...
Jul 29 21:44:30 thoth emhttpd: spinning up /dev/sdh
Jul 29 21:44:30 thoth emhttpd: spinning up /dev/sdg
Jul 29 21:44:30 thoth emhttpd: spinning up /dev/sdd
Jul 29 21:44:30 thoth emhttpd: spinning up /dev/sde
Jul 29 21:44:30 thoth emhttpd: spinning up /dev/sdb
Jul 29 21:44:30 thoth emhttpd: spinning up /dev/sdf
Jul 29 21:44:30 thoth emhttpd: spinning up /dev/sdi

     

  • Quote
    Just now, mgutt said:

    @SimonF

    Is this a new feature of Unraid 6.9?

     

    My productive server is still on 6.8: 

    Jul 29 21:44:30 thoth emhttpd: Spinning up all drives...
Jul 29 21:44:30 thoth emhttpd: spinning up /dev/sdh
Jul 29 21:44:30 thoth emhttpd: spinning up /dev/sdg
Jul 29 21:44:30 thoth emhttpd: spinning up /dev/sdd
Jul 29 21:44:30 thoth emhttpd: spinning up /dev/sde
Jul 29 21:44:30 thoth emhttpd: spinning up /dev/sdb
Jul 29 21:44:30 thoth emhttpd: spinning up /dev/sdf
Jul 29 21:44:30 thoth emhttpd: spinning up /dev/sdi

     

    Let me test on my 6.9.2 this test was on 6.11rc

  • Quote

    I'm not sure what are the conditions, I think there are several possibilities (at least in 6.10.3)

     

    I thought it was doing it, but I just hit the spin up button and got an instant spin up of all drives :

    image.png.8c0cdc50193ad667ab69b56619d47c51.png

    Spoiler

    Jul 29 21:45:18 mediahub emhttpd: Spinning up all drives...
    Jul 29 21:45:18 mediahub emhttpd: spinning up /dev/sdm
    Jul 29 21:45:18 mediahub emhttpd: spinning up /dev/sdk
    Jul 29 21:45:18 mediahub emhttpd: spinning up /dev/sdd
    Jul 29 21:45:18 mediahub emhttpd: spinning up /dev/sde
    Jul 29 21:45:18 mediahub emhttpd: spinning up /dev/sdb
    Jul 29 21:45:18 mediahub emhttpd: spinning up /dev/sdf
    Jul 29 21:45:18 mediahub emhttpd: spinning up /dev/sdc
    Jul 29 21:45:18 mediahub emhttpd: spinning up /dev/sdn
    Jul 29 21:45:18 mediahub emhttpd: spinning up /dev/sdo
    Jul 29 21:45:18 mediahub emhttpd: spinning up /dev/sdl
    Jul 29 21:45:35 mediahub kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    Jul 29 21:45:35 mediahub kernel: ata3.00: configured for UDMA/133
    Jul 29 21:45:35 mediahub kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    Jul 29 21:45:35 mediahub kernel: ata9.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
    Jul 29 21:45:35 mediahub kernel: ata9.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
    Jul 29 21:45:35 mediahub kernel: ata9.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
    Jul 29 21:45:35 mediahub kernel: ata9.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
    Jul 29 21:45:35 mediahub kernel: ata9.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
    Jul 29 21:45:35 mediahub kernel: ata9.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
    Jul 29 21:45:35 mediahub kernel: ata9.00: configured for UDMA/133
    Jul 29 21:45:35 mediahub emhttpd: read SMART /dev/sdm
    Jul 29 21:45:35 mediahub emhttpd: read SMART /dev/sdj
    Jul 29 21:45:35 mediahub emhttpd: read SMART /dev/sdh
    Jul 29 21:45:35 mediahub emhttpd: read SMART /dev/sdg
    Jul 29 21:45:35 mediahub emhttpd: read SMART /dev/sdd
    Jul 29 21:45:35 mediahub emhttpd: read SMART /dev/sde
    Jul 29 21:45:35 mediahub emhttpd: read SMART /dev/sdb
    Jul 29 21:45:35 mediahub emhttpd: read SMART /dev/sdf
    Jul 29 21:45:35 mediahub emhttpd: read SMART /dev/sdn
    Jul 29 21:45:35 mediahub emhttpd: read SMART /dev/sdo
    Jul 29 21:45:35 mediahub emhttpd: read SMART /dev/sdl
    Jul 29 21:45:35 mediahub emhttpd: read SMART /dev/sdi
    Jul 29 21:45:35 mediahub emhttpd: read SMART /dev/sda
    Jul 29 21:45:36 mediahub emhttpd: read SMART /dev/sdk
    Jul 29 21:45:36 mediahub emhttpd: read SMART /dev/sdc

     

    However, if I hit the Array spin up arrow only, then it seems that it is done in steps :

    image.png.0a331766cd5c316aeb272c2573859af5.png

    Spoiler

    Jul 29 21:48:41 mediahub emhttpd: spinning up /dev/sdo
    Jul 29 21:48:49 mediahub emhttpd: read SMART /dev/sdo
    Jul 29 21:48:50 mediahub emhttpd: spinning up /dev/sde
    Jul 29 21:48:58 mediahub emhttpd: read SMART /dev/sde
    Jul 29 21:48:58 mediahub emhttpd: spinning up /dev/sdl
    Jul 29 21:49:07 mediahub emhttpd: read SMART /dev/sdl
    Jul 29 21:49:07 mediahub emhttpd: spinning up /dev/sdm
    Jul 29 21:49:16 mediahub emhttpd: read SMART /dev/sdm
    Jul 29 21:49:16 mediahub emhttpd: spinning up /dev/sdf
    Jul 29 21:49:25 mediahub emhttpd: read SMART /dev/sdf
    Jul 29 21:49:25 mediahub emhttpd: spinning up /dev/sdn
    Jul 29 21:49:34 mediahub emhttpd: read SMART /dev/sdn
    Jul 29 21:49:35 mediahub emhttpd: spinning up /dev/sdb
    Jul 29 21:49:44 mediahub emhttpd: read SMART /dev/sdb
    Jul 29 21:49:44 mediahub emhttpd: spinning up /dev/sdc
    Jul 29 21:50:00 mediahub kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    Jul 29 21:50:00 mediahub kernel: ata3.00: configured for UDMA/133
    Jul 29 21:50:00 mediahub emhttpd: read SMART /dev/sdc
    Jul 29 21:50:00 mediahub emhttpd: spinning up /dev/sdk
    Jul 29 21:50:17 mediahub kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    Jul 29 21:50:17 mediahub kernel: ata9.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
    Jul 29 21:50:17 mediahub kernel: ata9.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
    Jul 29 21:50:17 mediahub kernel: ata9.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
    Jul 29 21:50:17 mediahub kernel: ata9.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
    Jul 29 21:50:17 mediahub kernel: ata9.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
    Jul 29 21:50:17 mediahub kernel: ata9.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
    Jul 29 21:50:17 mediahub kernel: ata9.00: configured for UDMA/133
    Jul 29 21:50:17 mediahub emhttpd: read SMART /dev/sdk
    Jul 29 21:50:17 mediahub emhttpd: spinning up /dev/sdd
    Jul 29 21:50:26 mediahub emhttpd: read SMART /dev/sdd

     

  • Quote
    • Thanks 1
    6 minutes ago, mgutt said:

    @SimonF

    Is this a new feature of Unraid 6.9?

     

    My productive server is still on 6.8: 

    Jul 29 21:44:30 thoth emhttpd: Spinning up all drives...
Jul 29 21:44:30 thoth emhttpd: spinning up /dev/sdh
Jul 29 21:44:30 thoth emhttpd: spinning up /dev/sdg
Jul 29 21:44:30 thoth emhttpd: spinning up /dev/sdd
Jul 29 21:44:30 thoth emhttpd: spinning up /dev/sde
Jul 29 21:44:30 thoth emhttpd: spinning up /dev/sdb
Jul 29 21:44:30 thoth emhttpd: spinning up /dev/sdf
Jul 29 21:44:30 thoth emhttpd: spinning up /dev/sdi

     

    For 6.9.2 some where already in use hence only read smart.

      

    Jul 29 20:49:35 unraid emhttpd: read SMART /dev/sdp
Jul 29 20:49:35 unraid emhttpd: spinning up /dev/sdr
Jul 29 20:49:44 unraid emhttpd: read SMART /dev/sdr
Jul 29 20:49:45 unraid emhttpd: spinning up /dev/sds
Jul 29 20:49:54 unraid emhttpd: read SMART /dev/sds
Jul 29 20:49:54 unraid emhttpd: spinning up /dev/sdm
Jul 29 20:50:04 unraid emhttpd: read SMART /dev/sdm
Jul 29 20:50:04 unraid emhttpd: spinning up /dev/sde
Jul 29 20:50:13 unraid emhttpd: read SMART /dev/sde
Jul 29 20:50:14 unraid emhttpd: read SMART /dev/sdf
Jul 29 20:50:14 unraid emhttpd: spinning up /dev/sdg
Jul 29 20:50:19 unraid emhttpd: read SMART /dev/sdg
Jul 29 20:50:19 unraid emhttpd: spinning up /dev/sdl
Jul 29 20:50:19 unraid emhttpd: read SMART /dev/sdl
Jul 29 20:50:28 unraid emhttpd: spinning up /dev/sdk
Jul 29 20:50:37 unraid emhttpd: read SMART /dev/sdk
Jul 29 20:50:37 unraid emhttpd: spinning up /dev/sdq
Jul 29 20:50:46 unraid emhttpd: read SMART /dev/sdq
Jul 29 20:50:46 unraid emhttpd: spinning up /dev/sdn
Jul 29 20:50:56 unraid emhttpd: read SMART /dev/sdn
Jul 29 20:50:56 unraid emhttpd: read SMART /dev/sdo
Jul 29 20:50:56 unraid emhttpd: read SMART /dev/sdt

     

  • Quote

    Mine pretty much always start staggered on 6.10.3, and I'd like an option to tell it not to :) Only have 3 drives to start most of the time, but they take 10 seconds each to spin up...

    Edited by Kilrah

  • Quote

    • Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Reply to this topic...
    Go to topic listing

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.