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.

Disks don't spin down

Featured Replies

Hi together

I'm not able to let all my sata-hdds spin down and need your help.

what i've done so far:

  • checked the forum
  • Checked file activies with different plug-ins
  • optimizied plex
  • moved docker to cache only
  • Rest of the shares is 1st cache then array
  • mover goes every 4h
  • spin down delay is 15min

 

diagnostics are attached.

 

thanks a lot 

 

onkel

tower-diagnostics-20240320-0834.zip

Solved by onkelnatas

  • Author

+ stopped all dockers, manually spin down the disks --> not even 30s until the spin up again.

  • Community Expert

Your 'system' share has files on disk1.    This will keep disk1 and the parity drive spun up as disk1 is where the docker.img file is currently located.  To get best performance you want this to be on the 'cache' pool.  

 

To get move to move these files to the 'cache' pool you need to follow the procedure documented here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI.  In addition every forum page has a DOCS link at the top and a Documentation link at the bottom.   The Unraid OS->Manual section covers most aspects of the current Unraid release.

 

Once you have all of the 'system' share on the 'cache' pool you can then set the Secondary storage for that share to 'None' and enable Exclusive Shares under Settings->Global Share settings to get best performance.

  • Author

moved nearly all shares to cache, without the multimedia (7TB). shutdown all dockers/VMs and manually spin down the disk:

10s and the are up again. HEEEEEEELP

 

tower-diagnostics-20240320-2129.zip

  • Community Expert
46 minutes ago, onkelnatas said:

moved nearly all shares to cache

According to these latest diagnostics:

b-----s                           shareUseCache="no"      # Share exists on disk1
b--------n                        shareUseCache="only"    # Share exists on disk1
isos                              shareUseCache="only"    # Share exists on disk1
M--------a                        shareUseCache="yes"     # Share exists on cache, disk1
system                            shareUseCache="only"    # Share exists on cache, disk1
T---------e                       shareUseCache="only"    # Share exists on disk1
u------p                          shareUseCache="only"    # Share exists on cache, disk1

So, you have several shares set to only use the cache drive, but they have files on disk1, including the earlier mentioned "system" share.

 

Merely changing the settings will not move anything. In fact, changing a share to only use cache will guarantee that mover will ignore it, since it is not possible to set a Mover action for shares without Secondary storage.

 

Also, syslog has several entries where mover says the file already exists. Mover won't replace files.

 

And nothing can move or delete open files, so you have to disable Docker and VM Manager in Settings to work with some of these.

 

Might be simpler to clean this up yourself using Dynamix File Manager.

 

 

 

 

  • Community Expert
M--------a                        shareUseCache="yes"     # Share exists on cache, disk1

What is the purpose of this share? Does it have seeding torrents?

  • Author
1 hour ago, trurl said:
M--------a                        shareUseCache="yes"     # Share exists on cache, disk1

What is the purpose of this share? Does it have seeding torrents?

 

Multimedia (TV shows and movies)
2 Docker are having access to this share:
- Jdownloader (no active downloads)
- and Plex (no automatic folder scanning)

I just tested:
1.) shutdown all dockers/VMs

2.) spindown the array

3.) wait 2min (no spin up)
4.) start any docker (even pi-hole with no mounts to Multimedia): disks spinned up

 

I'm getting sick of it...

 

  • Community Expert

Do you have any client computer with a mapped drive to that share?

  • Community Expert

Have you managed to get all of the ‘system’ share onto the cache pool?   Have you corrected any of the other wrong share settings?   Do you have Turbo Write mode enabled?

 

I would suggest posting new diagnostics taken with the array started in Normal mode so we can see current settings.

 

 

  • Community Expert
2 hours ago, itimpi said:

Have you managed to get all of the ‘system’ share onto the cache pool?   Have you corrected any of the other wrong share settings?

Most recent diagnostics shows those OK.

  • Author
  • Solution
18 hours ago, itimpi said:

Have you managed to get all of the ‘system’ share onto the cache pool? yes
  Have you corrected any of the other wrong share settings?  yes

Do you have Turbo Write mode enabled?  I switched from auto to "read,..." just now. Tests are positiv, seems to work!
 

 

 

 


Let me give u a feedback after the weekend.
Thank you all so much for your help!

  • 2 weeks later...
  • Author

All good.

thank you!

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...

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.