• Posts

  • Joined

  • Last visited

Everything posted by johmei

  1. I found the something. Apparently Crashplan Pro decided to dump 400 plus GBs of files in the appdata/CrashPlanPRO/conf/tmp directory. 😕 took some digging to find it and that definitely explains things. I used MC to delete them and the space is back. I also did an extended smart test and it said everything checked out. So I'm guessing everything is good, I just need to figure out wth Crashplan did that and stop it from doing that again. Thanks a ton for the help and reassurance on this!! It's very much appreciated!
  2. That's the weird thing though....I have the mover scheduled for every week and I know I don't load up 500 GB or even close in a week. This has never happened before and I tried to manually invoke the mover and nothing. And when I try to view the pool....there's no data on there other than about 10-20 GB worth for my Docker Plugins and that includes a 10 GB for the docker image, at least not that I can see. I have no idea how it is saying there is no space on it. It makes no sense. It's never gotten even remotely close to filling up since I first fired this system up about 6 or 7 years ago. Any thoughts?
  3. When you set something up so long really forget so many things 😕 I'm not exactly sure what information is needed, but I'll start with the Diag File. In my Dashboard, one of my cache drives in the pool is stating it has an error. I guess that has something to do with the issue but I thought the point of having a mirrored cache drives was that when one breaks, the other continues to function but that doesn't seem to be the case. I need to take care of this and I'm worried about losing data that is still on the cache that hasn't been moved yet. The cache is just acting weird and I'm worried about losing data, otherwise, I'd just be reading the manual and messing with stuff myself. Please advise and/or ask follow up questions as I know I left important information out. Samsung_SSD_850_EVO_500GB_S21HNXAG941287N is the first cache drive and Samsung_SSD_850_EVO_500GB_S21HNXAG643841J is the second cache drive (the one with the errors) Thanks so much
  4. Thanks very much for confirming this! While I hope there won't be a next time any time soon, I won't do maintenance mode if I have to again just in case I need access to my files!
  5. I don't know what happened (I only know it was related to plugging in my old bad drives to try and pre-clear/test them again just out of curiosity) but unraid decided that my first parity disk was bad or something 🙄 (it's brand new and went through no less than 1 full preclear) so I learned a lesson there. But I started the array in maintenance mode and hit sync with the intention of it helping to shave some time off, without realizing I actually needed to access some data before the 17 hours that I'd have to wait without mounting the array. Is there a safe way to not have to start the parity sync over and still mount the array? Or will I have to start over? And if I do, how do I do that safely? I assume I would simply cancel the parity-sync, and then start the array only not in maintenance mode this time? Thanks so much!
  6. Thanks so much for the reassurance on that! And for everything! I couldn't have confidently done this without your guidance and feedback! And thanks to everybody else also that chipped in and helped me on this issue. I greatly appreciate it! You're all awesome!
  7. All the other drives did finish without errors luckily. It seems like this was a really close call. I'll be paying more attention to this stuff in the future and setup some alerts as trurl suggested. But I am concerned because the now failing disk was previously one of the two parity disks. Should I be concerned and if so, how can I verify the integrity of my data short of checking every single file in it's entirety?
  8. Well it finished re-building and seemed to be successful but well....My Previous Parity 1 drive (RXYD) is my new Disk 1 and before I did the parity swap (the copy) I did an extended smart test on every drive and every drive (except for the known bad drives, P23S and RYB9) passed. After everything re-built, I received a read warning again for Disk 1 so I did an extended smart test again on all the drives in the new array and RXYD failed with 30% left (see smart log below). I went ahead and included a full diagnostics in case you wanna take a look also. The other extended tests are still running but it looks like I'll have to replace another drive as well so soon 😕
  9. Okay it just did that because one disk was a bit behind. I'm now at the step where I have to start the Array but it's not exactly as described in the manual. The manual states, "The Start button will now be present, and the description will now indicate that it is ready to start a Data-Rebuild. Put a check in the Yes I want to do this checkbox (older versions: Yes, I'm sure), and click the Start button" But it doesn't say that it's ready to rebuild data. It's talking about expanding the file system of the data disks first and I don't see a check box. I'm assuming it's fine to just hit start and it will still do what it's supposed to, but just in case, I want to make sure so I've included a screenshot below. Both Parity drives have a green dot on them (the new 12 TB drives) just since that's cut out at the top. Thanks!! Well crap...things are not going as per the manual/instructions and I don't know what to do now (see attached image). I'm confused because it's still copying, but says it's not ready and that the content is being reconstructed? But that part isn't supposed to happen until after it's finished copying, right? So what is it doing? It shouldn't be reconstructing anything yet, right? Not sure what to do. MYR4 is one of my old parity drives also, I took a screenshot of everything before I started so that I would know which drives were where.
  10. Awesome, thanks so much for verifying that! And thanks for the heads up/tip on that. I definitely wasn't planning on rebooting or powering down, but it's good to know it would have to start over anyway! I'll get this entire thing started as soon as these drives finish pre-clearing!
  11. 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.
  12. 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!
  13. 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.
  14. 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.
  15. 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!
  16. 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!
  17. 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.
  18. 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,
  19. 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!
  20. 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!
  21. 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!
  22. 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.
  23. 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.
  24. 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!
  25. 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!