tinyblob

Removed the drive and ported the system over to the new HP Microserver flawlessly. Thanks for the support. Quick run-down of the steps I took, incase anyone else ends up here looking for the same answer: * Cleared the data off the drive i was removing from the array. This was really just for my own sanity. * Did a full parity check. Again, this was just for my sanity. * Stopped my array. * Unassigned the drive i was removing (in my case this was the last drive in the array). * With the array stopped i connected via telnet and issued an "initconfig" command. * Answered "Yes" when prompted (apparently it can't be "yes"..). * Logged back into the webui. * Was prompted by the webui to entirely rebuild parity - said yes to that. * Above step was left to run overnight, since it was going to take 7 hours or something. After that was completed the array was in full working order without the drive i unassigned. I could then remove it comfortably. However, since i was moving to a new server i took the following steps: * Took screenshots of the current drive layout in it's working condition. * Removed drives and put them in the caddies for the new server. * Printed labels for each drive with serial numbers (for my own sanity, i like to be able to pull the right drive if necessary). * Booted unraid. * Logged into webui. * Array is stopped and unworking thanks to the rearrangement and/or different drive controller. * Assign drives to their correct position based on serial number and screenshots. * Start array. Woo! All done.

Perfect, that's a weight off my mind! The new system hasn't arrived yet, but i'll keep at it and add solved to the original post title if it all goes okay!

Ah, sorry, i forgot to mention that! I'm running 4.7 currently, and i'm on a Plus license. Well, initconfig and new config sound fairly serious. Which stage would I be doing that? Are they for setting up the array once I've moved it, or for removing the empty drive in the last slot? I assume they're entirely non-destructive? Sorry for all the questions, just want to make sure I understand everything before I make a big step! --EDIT-- Found an entry in the FAQ, here: http://lime-technology.com/wiki/index.php?title=FAQ#How_do_I_remove_a_hard_disk_that_I_do_not_plan_on_replacing.3F. This seems to outline what I need to do. I'd previously attempted the "Removing multiple drives" instructions, which were clearly for an older version. Can't believe I missed this other part! I'll have a go at that. I see there's also a FAQ entry about moving the array to a new machine, which goes most of the way towards solving my second issue. But just one clarification - when I power on the array in my new machine (with a different controller card and drive layout) will it boot with the array stopped so I can rearrange it?

Hi there, I've had an unRAID server since the beginning of 2008. My current setup is far too big and noisy so I've picked up one of the ubiquitous HP Proliant Microservers to transplant into. I've got a couple of issues I could use some help with. 1) I currently have 6 drives, but the Microserver can only take 5, so I've emptied one drive and intend to remove it from the array. I unassigned the drive but couldn't seem to make unRAID "forget" about it. The end result was having to reassign the drive and completely rebuild the "data" on it. Annoying. I'm thinking it was maybe a problem because the drive was in position 5, leaving a gap in the array. I'm moving all the data from drive 6 onto drive 5 today. How do I permanently remove a drive from the array? 2) I'm going to be moving the whole array over to brand new hardware. My intention was to note down the serial number and position of each drive so I could assign them correctly on the new machine. But my worry is that the drives will be hooked up in a different order on the new motherboard. Won't unRAID just try to power up the machine with the drives set up? How do I deal with this situation? Thanks for any advice you can give, I'm really looking forward to having my NAS back up and running!