marshy919 Posted August 25, 2017 Share Posted August 25, 2017 So this is surely my fault... A couple things happened. I had a new SSD to install, and I was going to do so as an unassigned device (for temp download location). While I was at it, I saw an error on drive 22. I've never used this slot, although I think I may have mounted my existing cache drive there once when first building the server. Anyway, the error was something like "disk missing, files are emulated" - along those lines. So I googled that error, and came across something showing that you can fix this by tools > new config. A quick read of that showed what to do (i think)... I selected to keep my cache and parity drives (cause they are correct with no errors atm). I then see that all my data drives are unassigned. I select all the data drives to be selected again. So currently the parity drive, cache and data drives are all selected. When I started the array, it done a parity check but showed all my data drives as unmountable (I'd need to format them again). I cancelled the parity check after about 30 seconds, checked my drives with Krusader and it was saying they are empty. I then stopped the array and started to panic. Clearly I've done something wrong, unsure what exactly... How do I go about getting this data back? Fortunately I had nothing super important, just media, but a fair bit of it... Thanks Quote Link to comment
marshy919 Posted August 25, 2017 Author Share Posted August 25, 2017 Feeeew, all the data is there still. I just needed to not mount the parity drive. Now I can see all the disk usage, etc etc. Can someone please explain what to do from here? I don't want to break anything! I just need to add back my parity drive and sync that. Add an unassigned device to an SSD. Quote Link to comment
JorgeB Posted August 25, 2017 Share Posted August 25, 2017 That's a bug on v6.4, first array start after a new config will result in all unmountable data disks, stopping and re--starting the array fixes it. Quote Link to comment
marshy919 Posted August 25, 2017 Author Share Posted August 25, 2017 16 minutes ago, johnnie.black said: That's a bug on v6.4, first array start after a new config will result in all unmountable data disks, stopping and re--starting the array fixes it. Oh thanks, I thought I did something wrong. So I can just re-add the parity drive? Quote Link to comment
JorgeB Posted August 25, 2017 Share Posted August 25, 2017 46 minutes ago, marshy919 said: So I can just re-add the parity drive? Yes Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.