There needs to be a way to have unRAID ignore certain disks completely.  Until a more elegant solution is devised, perhaps just let us put an ignore= in disk.cfg, followed by the drive designation (or even the serial number, that'd be better).

 

I know something similar is in the laundry list, but the way it's described it could be talking about the same thing, or it could be talking about letting a drive be part of the array but not protected by parity (which seems just silly at first, but then you realize that if such a drive went down, it wouldn't count towards your failed disk count and losing parity).  I want an option where unRAID will completely ignore a drive so I can't accidentally select it to be part of the array.  Closest thing right now would be to assign a drive as the cache drive, but disable the mover script.  Would be pretty bad if the mover script came back to life though.

There is no problem having extra disks on your unRAID box.  I have one that operates like the "cache disk" in the latest beta that I have been using since 4.2.1.  From unRAID's perspective it looks like a disk available to join the array - but I just don't.

 

Is your request that unRAID protect you from yourself in not allowing you to accidently assign a certain disk to your array?  Since updating your devices is an infrequent event, it seems that maybe a little extra dilligence would take care of this.

Is your request that unRAID protect you from yourself in not allowing you to accidently assign a certain disk to your array?  Since updating your devices is an infrequent event, it seems that maybe a little extra dilligence would take care of this.

 

It's easy to say that.  It's also easy to do a rm -rf while accidentally in the wrong directory.  I'd rather not have to worry about accidentally assign the wrong drive, or having to remember which drive I'm not supposed to assign.  I plan on switching around a lot of drives especially in the next month or so, it'd be nice to pop in a new drive and only see one drive available to be assigned, instead of seeing two and hoping I pick the right one.  What if I mean to pick the right one, but my mouse jumped a bit and I clicked on the one just below it?  I don't "think" there'd be permanent damage, just change it right away to the other drive before starting the array, but bad things could still happen.

I plan on switching around a lot of drives especially in the next month or so, it'd be nice to pop in a new drive and only see one drive available to be assigned, instead of seeing two and hoping I pick the right one.

 

Then I would suggest to be very very careful.

Possibly write down somewhere the drive you do NOT want to put into the array.

 

The chances of having your feature installed in the next month need to be weighed against the currently releasing beta and the laundry list.

 

Granted, the feature request has merit. I think other things may be higher in the queue.

 

 

I plan on switching around a lot of drives especially in the next month or so, it'd be nice to pop in a new drive and only see one drive available to be assigned, instead of seeing two and hoping I pick the right one.

 

Then I would suggest to be very very careful.

Possibly write down somewhere the drive you do NOT want to put into the array.

 

The chances of having your feature installed in the next month need to be weighed against the currently releasing beta and the laundry list.

 

Granted, the feature request has merit. I think other things may be higher in the queue.

 

 

 

Of course I will be very, very careful.  I think it wouldn't be too hard to configure.  We already have a disk.cfg file, while you're looking at it to see what's been assigned, go ahead and look at what has to be ignored.  I'm sure other things are higher on the list, but this should be a pretty simple thing to add in.

 

I don't expect this to be added just for me or even any time soon.  I just like reporting things that I think would be beneficial.  I'm sure it'd help someone out there.

I think if you are careful you'll find that you won't make the mistake of assigning a drive that you don't want to assign to the array.  Setting up the array is pretty rare.  unRAID would make you press the "Restore" button if you added a new drive to the array by accident.