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.

Drop dependency of drive/slot location

Featured Replies

I am surprised this has not been requested before which makes me think there is some technical gotcha I am missing.

 

Currently unRAID has a bit of a fit if the drives move about. i.e. if you move drives to a different slot/port.

 

Unfortunately for many reasons this can happen even if you don't actually move a drive i.e. kernel changes or adding a new drive

 

Since the parity XOR does not care about order why does order matter?

There are times I wished unRAID used the dev/disk/by-id method also.

Older versions of unRAID used the disk controller port to tie a given "slot" in the array to a drive.  As long as you used the same set of ports, it usually figured things out.  It did not use the actual /dev/sd? or /dev/hd? device names.

 

Newer versions of unRAID, (since 5.0-beta8 I think) use the disk model/serial number to tie a given disk to a 'slot' in the array.

 

As long as the model number/serial number of the disk does not change, it is able to figure things out. 

 

Are you looking for something in addition?  I'm thinking the feature you are requesting is already there.

Currently unRAID has a bit of a fit if the drives move about. i.e. if you move drives to a different slot/port.

 

No it doesn't ... unless I'm misunderstanding what you are asking for.  I have stopped the array, hot-swapped drives to different slots in my 5in3 cages (even on to different controllers) and restarted the array.  The array comes up and runs as though nothing has changed.  This works with any of the more recent 5.00 betas/RCs.

Older versions of unRAID used the disk controller port to tie a given "slot" in the array to a drive.  As long as you used the same set of ports, it usually figured things out.  It did not use the actual /dev/sd? or /dev/hd? device names.

 

Newer versions of unRAID, (since 5.0-beta8 I think) use the disk model/serial number to tie a given disk to a 'slot' in the array.

 

As long as the model number/serial number of the disk does not change, it is able to figure things out. 

 

Are you looking for something in addition?  I'm thinking the feature you are requesting is already there.

 

Yup, I've rebuilt 2 unRAID servers this month and all my drives were still green after booting to unRAID. It definitely does not care about order anymore.

  • Author

Are you looking for something in addition?  I'm thinking the feature you are requesting is already there.

 

Nope it sounds like its already implemented and I am quoting experience from 4.X issues I have seen.

 

Dont you just love things being fixed before you ask for them lol

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.