I have a pool (not party of the array) with a device/drive that is said to be "wrong":

 

This is because I took out the previous drive, and replaced it with a larger drive.

I transferred all the data from the old drive to the new drive.

 

How do I tell Unraid to forget about the old drive, use the new drive, and not affect any other part of the configuration (other pools, array, shares)?  I also don't want to erase the contents on the new drive.

 

 

 

attach diagnostics to your NEXT post in this thread

I finally got it to work.  I had to scroll down to the bottom of the page (which is far off my screen), and click to start the array...even though the pool isn't in the array.  I might have had to put a check mark in a box, but can't remember 100%...but look in "Array Operation" for clues (even though it's not part of the array).

 

The hokey organization part is the pool devices are not part of the array, yet there's tasks that appear under "Array Operations".  So you can't manage the pools at the pool.  You can't manage the devices at the device.

 

Another hokey issue was my other pool didn't have the right partition.  When you click on the drive/device/pool, you can't erase or format.  Again you have to scroll to the bottom of the page under "Array Operations", and put a check mark in a box to format the "unmountable" drives, and manually verify you are formatting the correct drive.

 

I wish I can manage the device/pool in one place, and the same place where the error/info messages are located.  Like clicking the pool name, or clicking the device name.

 

It's also confusing using the word "cache".  Cache seems to have dual meanings.  There's the pool named "cache" and there's the cache functionality.  This gets more confusing when dealing with shares+cache+pool+disks.

 

I'm not sure if I'm doing something completely wrong, or if this should be constructive feedback.

 

I have my main protected array (parity + data (which Unraid confusingly calls disks, because I have disks outside of the array)).

 

I have a cache pool.  This is used for cache, but also docker and VM and Unraid files, so it's not really 100% "cache" pool, at least not by my definition.  I'd like to see this organized better to separate cache, VM, Unraid, docker.

 

I have a pool (JBOD eventually) for backups.

 

I have a pool  (JBOD eventually) for temporary/junk/scratch/partial downloads.

 

 

 

 

 

 

 

 

tower-diagnostics-20220910-1137.zip

14 minutes ago, Jaybau said:

scroll down to the bottom of the page

Settings - Display Settings - Page view: Tabbed

Thank you for the "tabbed view".

 

Though I would like to know if it makes logical/intuitive sense to have pool and device specific actions in the "Array Operations" tab?  Orw ould it not be more intuitive to at least have the messages/errors on the same tab?  And actionable within the same tab, or clicking down into the pool and/or device?  That's where I would expect to manage the pool and/or device.

No changes are committed until the array is started

And changes can't be made unless the array is stopped.

Several things happening at array start/stop that aren't only about the array. All array and pools are mounted, user shares are mounted, docker/libvirt vdisks mounted if Docker / VM Manager are enabled.

2 minutes ago, trurl said:

No changes are committed until the array is started

 

Thanks, I'll need to remember that.  I was trying to fix the "errors" before starting/committing they array.

And Docker / VM Manager started, autostart containers and VMs, I think Script plugin also can run scripts on array start, maybe some other things I don't use or remember.

 

And all that is reversed when array is stopped. Until all that is done array isn't stopped.

 

Shutdown and reboot also try to stop the array first but can timeout if array can't be stopped for some reason. Here is a thread about that: