someoneotherthanyou

Members
  • Posts

    16
  • Joined

  • Last visited

someoneotherthanyou's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Closing the loop here and final update. Parity has been completely rebuilt, array is happy, and I owe you all a beer!!! Thank you again and Happy Holidays to all!
  2. Yup, exactly Absolutely I do....My inbox was going crazy! Repeat after me...RAID is NOT a backup...RAID is DEFINITELY not a backup. I had just setup a docker for my CrashPlan Pro account prior to this. That was the first task I started once the array came back up.
  3. After an hour of slight dismay and mildly freaking out I actually applied a bit of logic and reassigned the parity disk to the old disk7 (8TB) as well as properly reassigning the remaining disks to their proper slots and fired up the array. I sighed a huge sigh of relief when presented with this on the server And this on my Windows 10 system This has been quite an adventure for sure. I've taken the original 8TB parity drive and put it into my external USB 3.0 SATA dock to run diags on it. Crystal Disk failed it as did WD Data Lifeguard. Very disappointing as the drive only had 2255 hours on it. It began it's life as an EasyShare external drive with 3 of it's brethren for the beginning of my Unraid journey. Fortunately the drive is covered under warranty until 8/2020 so it will get sent back. As to the mysterious disk6? It is a wicked ancient 4TB drive I had laying around but at some point I will pull it from the server case and test it. For now it just sits unassigned. It's a pretty safe assumption it is a lost cause. No data on it though so I'm not overly concerned. All drives will fail eventually and it's time had come. Thanks again for all the help in getting me through this debacle. It is very much appreciated. Best
  4. I elected to remove the drive PRIOR So I decided to shut down the server and remove the suspect 8TB (parity) drive. Did not touch the 4TB (failed) drive. Really, really wish I would have done that as I am now faced with this upon restarting it. How freaking FUBARD am I now? I had to unplug a total of 5 drives in order to ascertain which drive was the parity drive. It occurs to me now that which SATA/SAS port the drives are connected to might be somewhat important (ya think?). Is that my issue here?
  5. Roger that. I’ll check back in after the parity rebuild and let you guys know the results. Maybe a dumb question, but should I refrain from using the array before parity rebuild?
  6. When should I pull the bad 8TB and 4TB drives out of the case so that I can RMA them? The 8TB is less than 90 days old SMH
  7. I was able to stop the array, and did as instructed. Here is screenshot from new config... and screenshot prior to starting array I'll wait for further instructions prior to firing the array back up. Or should I power down to pull the drives from the array?
  8. Addendum to above: I mistakenly thought that the array had stopped. It has been attempting to stop the array unsuccessfully for over 45 minutes now but keeps having issues unmounting disk shares.
  9. Sorry it has taken me through today to address this. I have the array stopped and am in the new config menu with the retain all setting checked. I am presented with this rather ominous warning however. I'm a little hesitant to move forward. However, in the interim the amount of errors on the parity drive has exploded to this I guess my ultimate question is how much danger am I in of losing everything on this array?
  10. I cannot figure out how to actually access it via the GUI as shown here. That is extremely likely TBH. But from what I am understanding now, is since disk6 is emulated that when I click on folder contents it is an actual representation of that drive. Is that correct? And that by doing the same for disk7 that it is also void of any files? Hopefully I am making enough sense to help you help me. I very much appreciate all the questions everyone is asking to clarify the situation. Thank you for not getting frustrated by my lack of understanding.
  11. Is there anyway to rebuild disk6 within Unraid if I cannot mount it? I'm thinking about rebooting the box as it hasn't been powercycled in 43 days. Would that maybe encourage disk6 to mount again
  12. As requested zip file is attached. Thank you nasnashurray-diagnostics-20181209-1218.zip
  13. Thanks for your reply OK...Makes sense. 2 thoughts come to mind though. a) I don't know how to mount it and the GUI will not let me and b) to the best of my knowledge no data has been written to it as of yet. Doesn't my config write up to 50% of each drive sequentially through to the end of the array? For instance disk4, 5 & 7 have no data written to them yet since disk3 has not reached 50% full yet. Picture below to illustrate.