johmei

Yeah I'd rather wait to make sure. I have a good 18-20 hours or so or more before these drives are done pre-clearing anyway. In the meantime, the Array is offline. And actually on that note, I just had a question pop in my head; when you "spin down" the array, is that supposed to be literal? Are the drives actually supposed to stop spinning? Or does it just park the heads or something? Because the entire array is offline but the drivers still be vibratin' from what I can only imagine are the platters spinning. Just curious about that.

I have some questions specific to a simultaneous parity swap procedure. The manual only outlines how to do this with a single parity drive and a single data drive but can I assume the procedure is the same except literally doing it twice at the same time? To be more specific, would the procedure be as follows: Stop the array Unassign both disk 1 and disk 2 (the failed data drives) Start the array and choose "Yes I want to do this" checkbox. Stop the array again (I currently have both 12 TB drives connected to the Z97 Sata controller doing a pre-clear so I don't believe I need to mess with actually disconnecting any drives) Unassign BOTH Parity and Parity 2 Assign the new 12 TB drives (after preclear finishes) to Parity and Parity 2 Assign the old Parity and Parity 2 drives in the slots of disk 1 and disk 2 (I assume doesn't matter which) Go to the Main > Array Operation section and there should be a Copy button Put a check in the "Yes I want to do this" checkbox and click the "Copy" button and wait for a long long time until the copy completes. The start button will now be present with a description indicating that it is ready to start a Data-Rebuild...I should put a check in the "Yes I want to do this" checkbox and click "start" And then I just wait and minimize use of the array so it'll finish faster/less complications. Is that about right more or less? I quoted JorgeB as per their suggestion and trurl's vote of confidence in what they say, but really if anybody can answer and reassure me that I have the correct procedure then feel free to let me know Thanks so much everybody!

Ahh, I actually saw somebody mention that about USB drives in a post somewhere. That makes sense. The LSI SAS2008 controller has been the only one I've used so far, and the Z97 SATA controller is in AHCI mode so I'm assuming everything should be fine As soon as these pre-clears finish, I'll reboot and make absolute sure the Intel SATA controller doesn't have any funky settings though just to be safe. I'll need it properly configured anyway because my LSI controller only has 8 drive support and I want to add at least 1 more drive.

I haven't finished reading through the manual yet (going through it right now), but I've a quick question; does unraid identify disks and what disk they are in the array based off of the S/N or something unique in the drive? Or does it ID them another way? I'm basically wondering if it matters what controller or what port any given drive is plugged into or not. I'm assuming it doesn't matter and I can do the Parity swap with the 12 TB drives via the onboard SATA controller and then move them to my LSI controller when all the smoke clears and my data is safe. But I want to make sure.

awesome, thank you so much for the suggestion! I'll get that installed for definite. Something else I wanted to ask; would it be safest if I went out and got 2 x 4 TB drives to rebuild the bad drives before messing with the parity drives? Or is the risk the same doing a parity swap? And the risk, as I understand it, is being that another drive will die while one drive is being rebuilt....not sure if there are other risks as well?\ Thanks!

Do the manuals cover a simultaneous Parity Swap? Is there anything specific about that procedure that I should know? I assume at the very least, it would mean putting both 12 TB drives in at the same time and as such...I should do a preclear on both 12 TB drives first right? Anything else I should know, or any other tips/suggestions that might help? Thanks!

Something that I should of realized (when building a NAS of any kind) is that a drive failing will not necessarily be catastrophic and it will not necessarily be all red lights flashing in your face. Because everything SEEMED to be working fine, I didn't know why the errors kept popping up. After getting them for a bit I realized that I should really look into them. Honestly, I don't know how much later I would have waited if I hadn't decided to buy two new parity drives when I did. Now I know, and the mistake won't happen again (but it's also why I have a full online backup) but I must say, I do wish those notifications had been more "in your face" A message stating, "This could be potentially very serious and may cause data loss if no action is taken" would be nice and would catch my eye a lot more than just random warnings and the occasional error. Still, lesson learned, I'll be setting up email alerts or something after this is taken care of for sure.

Phew....okay. I decided to make sure all my drives were good before I proceeded with the parity swap so I did an extended Smart test on all of them and It looks like disk 1 and disk 2 are bad (attached extended smart log below). I'm already preclearing one of my 12 TB drives to do a parity swap but this is scary territory right now. Suggestions to proceed? Should I switch out both parity drives one at a time and then rebuild the bad drives with the old parity drives? Switch one parity drive out, then rebuild one of the drives, switch the other one out and then rebuild the other? Thanks, johnsnas-smart-20211013-19502.zip

Roger that, thanks. If anybody has anything else to add or anything else that might be important to note, please let me know! Otherwise, I'll check back if I run into any further issues. Thanks!

10% test remaining....does that mean it could not complete the final 10% of the test for whatever reason? using one of the parity disks to replace disk 1 would be ideal, but how would I do this and would there be any risk? Are you suggesting replace one of the parity drives with the 12 TB (so I'd have 1 x 4TB parity and 1 x 12 TB parity) and then take the previous parity drive to swap out the bad disk1? I assume both doing a parity swap and replacing a bad drive would be simple enough to find procedures for in the unraid wiki/forums/reddit, but is there anything else I should know? Thanks again!

what's the significance of the 10%? And....what would be the best approach to replacing this drive? I was planning to replace both my 4 TB Parity drives with 12 TB Parity drives but I wanted to make sure everything was healthy before I did. I want to be careful because even with my offsite backup, and even with 2 parity drives, I just don't want to risk anything going wrong. Having said that, would it be safe to replace my parity drives first? Or is there something else I need to do because of this disk failure before I consider that? Thanks!

Started that last night luckily for both the Parity and Disk1. Parity says all is good, completed without error. But Disk1 says Errors aoccured and to check SMART report, which I've included in this post. I'm gonna read over it to see if I can make sense of it but I know you'll likely recognize issues immediately. Thanks for the help in all this again btw. johnsnas-smart-20211011-0357.zip

Oh yeah lol. Well let's see. I'm in the log right now and it looks like there are quite a few read errors on disk1 from yesterday (10/10/2021) and...I don't see anything else but I swear there were other warnings for other disks (I just don't remember which ones and I cleared the notifications)...and actually I thought they were mostly warnings but all I see is several errors for Disk 1. But under the dashboard it says there is also a SMART error on my first parity drive. So I guess Disk 1 and Parity.

I had been randomly getting errors/warnings for a bit now and everything seemed to work fine, and most of the stuff that popped up in my notification box were actually just warnings (that I can't recall what those warnings were since I'm stupid and cleared the notifications) and I never really thought about it until now but...I don't really know how to recognize if a disk is bad and needs to be replaced or not. I came across a post here that looked similar to my situation and after they shared their diagnostics it was confirmed that one of their disks were toast. I have 2 4 TB parity drives and just actually bought 2 new 12 TB parity drives but I want to make sure everything is healthy before I replace those two because I'll ideally want to use the previous parity drives as extra storage for now. Anyway, as per the post that I found, I'm going to attach my diagnostics file since I'm now worried and need to make sure my data is safe. I do also upload all my data to Crashplan so I'm hoping that no matter what, I should be fine here. A short and sweet generalization of things to look out for for future reference would be good too. If there's a section in the wiki all about disk health (I imagine there must be), that would probably be best for me to check out too. Thanks very much for the assistance! johnsnas-diagnostics-20211010-2004.zip

I read somewhere in this thread that once a user migrates to crashplan pro that gfjardim's crashplan docker thing will update to the pro automatically? But it didn't say exactly HOW this happens. Or rather, it didn't say what I should expect. So when I opened up the Crashplan docker and saw the same crashplan home interface, and the same status, followed by "checking files" and all that jazz, i stopped it immediately because I have no idea what it's doing or if it's expected behavior. Can someone please clearly outline what kind of behavior is expected after the migration process? Exactly how and when does the docker container update automatically? Do I have to open it? Log out of it? Is there anything I need to do to trigger it? EDIT: I've been reading some of the threads here and someone mentioned entering their account license key in the app and that kick started the update? Where can I even find that? I'm looking around for it anywhere that I can think to look :\ EDIT02: I also noted somebody mentioning checking the History so I did. It said that it was downloading an update. TO BE CLEAR TO THOSE LOOKING FOR THE SAME ANSWER: Expected behavior will be nothing...until you check History. There is no other indication (or I did not see any) that it was updating the app. But the only thing I did was start the docker and opened the webview, then looked at history and at the very bottom (latest log entry), it stated that it was downloading an update. Thanks!

No worries at all. Thank you for getting back to me with a response. I'm probably going to play it safe and just trim it down by deleting the least important stuff and upload it again. It's better than having to re-upload everything and you and the other guy are the only two people I could find that said it didn't delete your stuff (although I didn't find anybody that explicitly said that it DID delete their stuff), so it's possible it was just a hiccup or something. Thanks again though for sharing your experience with that!

Can anyone else please confirm that it did not delete their archived over 5TB?? Because I'm getting some pretty solid, very clear, "Your data WILL be deleted" messages and warnings. It's not saying it might, it's saying it WILL. Did you get these warnings when you migrated, Shadowrunner? I'm trying to decide if I should delete enough data to bring it below 5TB or risk having to reupload it all. Granted, it's not near the size of yours, but I would still rather not have to upload over 2 TBs of data if possible. Also, something to add that's confusing me; it's reporting my backup as 5.8TBs on the migration page, however, the CrashPlan app (I'm using gfjardim's) says completed 7.3TB of 7.7TB. Anyone have any ideas about that? (Just checked my last backup report email and it says 7.6TB...so confused)