July 24, 201213 yr The story I did a John M atlas build (my first unraid build), but decided esxi wasn't for me. I ditched the esxi thumb drive and reset the boot order in bios. Unraid booted fine, but I was unable to access it via the web gui. I figured it was because of a plugin I had installed and decided to try a fres install. I took this opportunity to upgrade to rc5 by downloading the new package and deleting my current unraid and copying the new one over. I booted the unraid server, but I still couldn't access the web gui. Went through the forums looking for advice, and it ended up being a silly bit about putting http if front of the server name. The stupidity Put my discs in (what I thought) was the correct order and started it up. Noticed it didn't go valid right away and was checking/writing parity. I hit the stop button and double checked everything. Turns out I had put my cache drive as disc 6 because my real disc 6 hadn't been recognized by unraid yet. This is a problem that I am aware of, but havent had the resources to fix yet. I typically just have to pull it out and slide it back in for unraid to see it. Disc 6 doesn't contain any data. I am just using it as a place holder until I can purchase a solid drive. The parity did write, but none of the other discs showed any writes by the time I stopped it (about 20 seconds). The million dollar question(s) What did I do? Have I lost my data, or does the parity drive just need to rebuild? The attached photo shows what my configuration should be. I would appreciate any advice this wonderful community has to offer. I only have about 5tb of data spread across the first five drives. I could try some kung-fu/google-fu for data recovery, but I have a feeling I'm not the only idiot to do this.
July 24, 201213 yr If you didn't try to start the array with the wrong drive in the parity slot, you should be ok. The worst that I can see would be that your parity will need to be rebuilt.
July 24, 201213 yr Author That would be a wonderful conclusion to a horrible day. I've had my fingers crossed hoping that would be the general consensus from everyone. Thank you for your quick reply. It will make it a lot easier to sleep tonight! Is there anyway to make sure of the data will still be good before I restart the array?
July 24, 201213 yr Unassign the parity drive and start the array unprotected. You should be able to see all your data. The parity slot is the only "dangerous" slot, any other drive slot should just attempt to mount and read the drive assigned to it. As soon as you assign a parity disk, the array will want to rebuild parity by overwriting that disk, unless it thinks parity is already valid.
Archived
This topic is now archived and is closed to further replies.