rootisgod

If anyone still needs help on this, I made a blog post on setting up ESXi 7.0 U1 on latest version of Unraid (6.9.0 RC1). Network and SATA disks work out the box. Thanks for the post originally though, it helped me a lot. http://www.rootisgod.com/2020/ESXi-On-Unraid/

Yup, I meant a 'safe' rip out! I'm not that crazy.... Great, that's very helpful. I also forgot that the original disk still has the data so I really can't lose. Thanks very much! Though you may have just cost me hundreds in new hard disks EDIT: I checked the new config tool just to be sure what it did, and it does seem to have a preserve option so you dont have to be super paranoid about putting things back as they were after removing some disks. So i take back my original suggestion somewhat, it seems to do the job nicely. Relevant part highlighted in green.

I didn't look at it that way before actually, replacing when I actually have a new disk is better. Plus it makes it one step, thanks! So, could I in theory just rip out disk x, insert a blank new one of higher capacity, tell it to use that as the new disk x, then parity recovers all the data for me to the new disk? Or would that be a bit daft to rely on and it would be better to migrate data off to an existing disk first (using unbalance say) assuming I had existing space elsewhere on the array to do that?

I was just about to migrate data from 2 x 2TB disk to a single 8TB disk and then remove the 2 x 2TB drives to get back some disk bays. I didnt realise the removal process was so painful. I just added a 14TB parity disk yesterday (future proof!) and really dont want another parity check so soon (though understandable if unavoidable). But, a simple 'remove disk' option which says to poweroff, remove disk and then poweron again would be very welcome to ease my worries. Creating a new config seems a bit scary, though i'm sure I would be fine, it seems a bit against the grain to do something so drastic for a procedure most people will do at some point.