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.

Bug shrinking array by three small/empty drives and rebuilding

Featured Replies

Problems following https://wiki.unraid.net/Shrink_array

---------------------------------------

I have a dual parity array and have recently done a full parity check without error, running the latest unraid pro...

I have a full printout of all drive assignments

 

I rsynced (with remove) all data off of three old 1tb hard drives (to the array) and confirmed they are empty

I shut down the array,

I changed the included shares list to only include the drives I want to keep in the array (checked all but 3 drives)

Then tools, new config, retain all, yes, apply

On main, I unassigned the three drives to be removed

double checked all other drives are listed correctly

 

I cannot start the array due to "invalid configuration" to rebuild parity without the drives.

 

What am I missing? Is this a bug? Is there a work around?

Shouldn't I be able to remove as many drives as I want and just rebuild parity?

 

Invalid Configuration.png

Edited by bsim

  • Community Expert
6 minutes ago, bsim said:

What am I missing?

You didn't do a new config, or it didn't take, try again.

  • Author

It looks like the "shrink array" page is the problem...It has you unassigning the drives after the "new config". Using a bit of logic I was able to figure out that unassigning the drives then "new config" works beautifully.  The document needs to be fixed.

  • Community Expert
It looks like the "shrink array" page is the problem...It has you unassigning the drives after the "new config".

And that's correct, though it will also work if you unassign them before.

 

 

  • Author

I did attempt to unassign them twice after "new config", neither took (just invalid configuration both times)...could it be the removal of three drives at once that caused a glitch?

 

As soon as I did unassign before "new config" it worked flawlessly. Overall doing it before does seem to make much more logical sense for the process.

  • Community Expert
I did attempt to unassign them twice after "new config", neither took (just invalid configuration both times)...could it be the removal of three drives at once that caused a glitch?

No, it will work as long as you don't start the array, while the drive icons are blue, once it's started you can't remove devices any longer, or until you do another new config.

 

 

  • Author

Thats the point, new config then unassigning drives=the drive icons never went blue, and never gave me the option to start the array

until I unassigned before new config, then got the blueballs and the option to start rebuilding.

  • Community Expert
40 minutes ago, bsim said:

Thats the point, new config then unassigning drives=the drive icons never went blue

 

54 minutes ago, johnnie.black said:

You didn't do a new config, or it didn't take, try again.

 

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.