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.

Not Using New HD?

Featured Replies

I recently added a new hard drive to my array and for some reason unRaid is not using it.  Here are screenshots of my setup:

 

mSERAZK.png

 

gtJ7BjL.png

 

vGcqlcy.png

 

As you can see disk 3 is not being used, even when I add more files.  In my shares it's not showing the space as being there either.  As you can see in the third image I do have the disk included.  Any idea what is wrong?

Post a screen shot of this:

 

http://tower/boot/config/share.cfg

 

(change "tower" to whatever name or IP address you've assigned to your unraid install)

Your other two disks currently have 1.50TB used and 1.54TB used.

 

If this was the state when you added the new 3TB drive, I suspect the high-water allocation had recently "shifted" to Disk 1 (before you added Disk3).  If that's the case, it will continue to write to Disk1 until there is 250GB remaining ... and at that time will compute which drive is next.  At that point, Disk3 will be the "drive of choice" ... and will remain so until 1.5TB have been written to it.

 

  • Author

Post a screen shot of this:

 

http://tower/boot/config/share.cfg

 

(change "tower" to whatever name or IP address you've assigned to your unraid install)

 

# Generated settings:
shareUser="e"
shareUserInclude="disk1,disk2"
shareUserExclude=""
shareSMBEnabled="yes"
shareNFSEnabled="no"
shareNFSFsid="100"
shareAFPEnabled="no"
shareInitialOwner="Administrator"
shareInitialGroup="Domain Users"
shareCacheEnabled="yes"
shareCacheFloor="2000000"
shareMoverSchedule="40 3 * * *"
shareMoverLogging="yes"

 

It doesn't look like disk 3 is showing up in there.

 

Your other two disks currently have 1.50TB used and 1.54TB used.

 

If this was the state when you added the new 3TB drive, I suspect the high-water allocation had recently "shifted" to Disk 1 (before you added Disk3).  If that's the case, it will continue to write to Disk1 until there is 250GB remaining ... and at that time will compute which drive is next.  At that point, Disk3 will be the "drive of choice" ... and will remain so until 1.5TB have been written to it.

 

 

I've had the drive in there for a little bit (before one of the drives hit the 1.5TB used) so I think it should be using it now.

 

Check under Settings->Share Settings

 

I checked there and that looks like it was the problem!  Disk 3 wasn't added.  I thought I just had to add it under the individual shares and not there.  It's showing up with the right size now so I'm sure it will start putting files there now.  Thanks everyone!

Yes, if you added it before Disk 1 crossed the 1.5TB point, Disk 3 definitely should have bee selected at that point.

 

It seems you simply didn't have it actually added to the share.

 

Just noticed that your shares show "Disk 1", "Disk 2", and "Disk 3".    I think SimpleFeatures adds the space for display purposes;  but just in case you added these via UnRAID's Web GUI, you do NOT use spaces for them in the native interface => i.e. the includes should be disk1, disk2, and disk3 (no spaces).

 

Also ... if you want your shares to use all the disks, there's no reason to have ANY includes or excludes.

 

Archived

This topic is now archived and is closed to further replies.

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.