From the many many things I have read this should be very easy and straight foreword. Unfortunately for me there must be something wrong.

 

All I would like to do is move my disk assigned to "disk19" to "disk3" on the devices page. No physical moving of the drive at all.

 

Basically the same as what wanted to be done here : http://lime-technology.com/forum/index.php?topic=1812.0

 

Tom tells what to do here: http://lime-technology.com/forum/index.php?topic=364.msg2539#msg2539

 

So I should be able to start the array with this message being displayed: "Start will just record the new disk positions and bring the array on-line."

 

But all I get is: "Stopped. Invalid expansion."  " You may not add new disks when there exists missing, wrong, or disabled disk(s)"

 

It shows my disk19 as missing and disk3 as new (blue ball).

 

Tried everything I can think of, unplugged my cache drive, there is no other new or unassigned drives.

 

This is really bugging me as it looks like all I should have to do is unassign then reassign and that should be all but it just doesn't work.

 

 

 

Attach a system log to your next post.  Only way to analyze the situation.

 

 

This is one case where you need to log onto a console (the monitor and keyboard connected) or telnet to the machine and type "initconfig".

 

If you want, you can use the trust my array command next so that the parity is not rebuilt, but rather just checked. This would allow you to recover from a failed disk if something went bad rigth after you start. The short version is to type "mdcmd set invalidslot 99" next. You will get

 

cmdOper=set

cmdResult=ok

 

as the output.

 

http://www.lime-technology.com/wiki/index.php?title=Make_unRAID_Trust_the_Parity_Drive,_Avoid_Rebuilding_Parity_Unnecessarily

 

Peter

Forgot about the log, its attached now.

 

Well I did also recently remove a drive and did the "initconfig" without a hitch. It just worries me when it is telling the drive is missing and it is new in a different slot. Unless this is the expected behavior. So when I reassign the drive to a different disk I will not get the message "Start will just record the new disk positions and bring the array on-line" ever? It was a message I was expecting as that is exactly what has happened.

syslog-2010-09-16.txt

No, there is no such thing. The disk has to stay where it was assigned.

 

The physical port can change and it'll work through that but not the disk to slot assignments.

 

Peter

 

Thanks for the info Peter.

 

But I did just manage to move the drive to a different slot. Not exactly sure how I did it but I think this is how I went about it.

 

1 - "Removed the drive" http://www.lime-technology.com/wiki/index.php?title=FAQ#On_version_4.5.4_of_unRAID_onward

2 - Start array and stop Parity-Sync

3 - Stop array

4 - Added the drive to the slot I wanted it on. Found it as a valid drive. Not a new drive.

5 - Started the array and all my files are still all there.

6 - Parity-Sync

 

I didn't know that if you add a disk that was previously removed from unraid it will just pick it up as valid and will not add it as a new drive.