Frankthetank907
-
Posts
9 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Frankthetank907
-
-
50 minutes ago, JorgeB said:
By any chance did you do a parity swap recently?
I did do one back in October when I swapped an older 8TB parity drive out with another 18TB WD red pro, why?
-
1 hour ago, itimpi said:
It looks as if the system incorrectly started a correcting check:
Dec 4 03:00:01 Tower kernel: mdcmd (36): check Dec 4 03:00:01 Tower kernel: md: recovery thread: check P Q ...and then later found errors on parity1. I will try running a test to see if I can replicate the incorrect starting of a correcting check on my system in case it is a new bug in the 6.12.6 release. However why errors were found I have no idea. The fact that docker containers were running should be irrelevant.
BTW: With such large parity disks you may find it advantageous to install my Parity Check Tuning plugin? Even if you do not use all its features the fact that it adds to the Parity check history entries whether a check was correcting or not may be useful information.
Interesting, like I said in my original post this is the first time it has ever done something like this, and I did just update to the 6.12.6 release so maybe it is a new bug, or it could be a coincidence too but I am not going to pretend that I know what I am talking about when it comes to how the underlying system actually works lol. Will be interesting to see if you or anyone else is able to replicate this issue.
Also thanks for letting me know about your plugin, I will install it after this parity check finishes for sure. Looking forward to see if you are able to come up with anything on your system, and thanks for looking into the logs and helping out, I have no idea what I am looking at when I was sifting through them lol.
-
I forgot to mention, during the parity check (which is still running) I do have all of my docker containers running and doing their normal tasks, I am not sure if this could have somehow caused a sync error between the disks and parity, but I have never hand an issue with it in the past.
-
I have been running unraid for a few years now, never have I ever had any errors detected when doing a parity check until now. As you can see from the screen shots I have attached it appears as if the automatic parity check is also writing corrections to parity, which I am confused by because I have always had the option for it to automatically write corrections to parity during scheduled checks deselected. I am running Unraid version 6.12.6 as of 4 days ago, I have also attached the diagnostics file for troubleshooting, if anyone can help me understand what is going on it would be greatly appreciated. Thanks for any help in advance.
-
On 11/2/2021 at 3:18 AM, JorgeB said:
Because the other device is missing Unraid is not trying to mount the pool degraded (assuming it's raid1), you can do that manually, if successful backup pool contents and re-create the pool after replacing cables on the device that caused issues before.
This did the trick, thank you for the help!
-
1
-
-
4 minutes ago, JorgeB said:
Because the other device is missing Unraid is not trying to mount the pool degraded (assuming it's raid1), you can do that manually, if successful backup pool contents and re-create the pool after replacing cables on the device that caused issues before.
I will give this a shot!
-
Hi, I have been running my server for almost 2 years with no issues, tonight I was having an issue where my server log file was filling up
so I rebooted the server, when it came back up the second cache drive was missing completely from the system, like I never even had it in there.
I tried reseating the connectors and even tried other connectors from a different drive and it still wouldn't show up, so I tried reducing the cache pool back to 1 drive until I can order a replacement drive. When I tried bringing the array online the remaining cache drive would not mount, it was giving me the "unmountable : not mounted" error, so I went to the drive and checked the BTRFS file system check in read only mode
I also went to the drive and took a capture of the disk log itself 
I connected the "bad" drive to my computer and it shows up in disk management so I am unsure if it is actually bad or not. What can I do from here? I want to try to recover the file system if at all possible, any help is greatly appreciated.
-
On 12/27/2019 at 10:27 AM, SpencerJ said:
The Unraid forum is about to hit a major milestone: 100,000 members! As of Christmas time, 2019, we're sitting at approximately 99,000 forum members. To commemorate this awesome community achievement, let's do another giveaway!
What's at stake?
- 90 winners will receive limited-edition Unraid case badges! These 2x2 inch domed, polyurethane server badges will look great on your own home lab (badges not for sale, sorry)!
- 9 winners will receive an Unraid case badge AND a $25 gift card to the Unraid merch store.
- 1 Grand Prize Winner: receives a case badge, a $25 gift card AND an Unraid pro license! Pretty sweet huh!?
See the linked blog post for pics and additional info!
How to Enter:
Simply tell us:
- one thing you like most about Unraid
and
-
one thing you'd like to see added to the OS in 2020
That's it! Winners will be drawn at random from the forum entrants here.
At our current rate, we will likely hit 100,000 members late January or early February 2020. Follow the Unraid twitter account for periodic forum # updates!
Entries will close as soon as we hit 100,000 forum members so don't delay in entering! Good luck.
1. The one thing I like most about Unraid is the UI, as a beginner with Unraid it was extremely easy for me to get started and now that I have used it for a few months I really enjoy how simple it is to do most things such as build VM's and Docker containers. The most useful thing I have found so far is the community though, they help out a ton.
2. One thing I would like to see added to the OS in 2020 is the ability to set up Snapshots so if say a picture was accidentally deleted on a share It would be easily recoverable, also snapshots for VM's and Docker containers, but it would also be nice to have native ZFS
so I rebooted the server, when it came back up the second cache drive was missing completely from the system, like I never even had it in there.
I connected the "bad" drive to my computer and it shows up in disk management so I am unsure if it is actually bad or not. What can I do from here? I want to try to recover the file system if at all possible, any help is greatly appreciated.
millions of sync errors corrected during scheduled parity check
in General Support
Posted
interesting, that is good to know, that would explain all the errors it is picking up, thanks for that info! Still would like to figure out why it decided to automatically write corrections to parity even with that option not being selected in the settings though, that could potentially be very problematic if there was some sort of corruption on the array.