James_Darkness
-
Posts
86 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by James_Darkness
-
-
On 6/15/2022 at 10:31 PM, trurl said:
What do you mean? What exactly is gray? Screenshot? Your earlier screenshots had all drives green.
None of my screens shots show green? To be more precise and exact I'm talking about how much storage is being used or free is colored gray instead of green
-
On 6/14/2022 at 9:11 AM, trurl said:
Not entirely clear about your response, but if you run a non-correcting parity check and it finds no parity errors then everything should be OK now.
But why is everything gray then?
-
4 hours ago, trurl said:
So you reset your configuration to what it was on that backup then Unraid doesn't remember anything that happened after that backup was taken.
In the parity history screenshot in the first post, when did this flash drive reset occur?
This is the 3rd USB actrul but the time line is. on my second USB I run it with one parity drive instead of two. 3 days later when that flash drive also brakes I run it with the same old backup of the flash drive that I used to make the second flash drive 3 days ago. to make my new 3rd USB that I'm using now. I also plug in the second parity Drive in
-
5 hours ago, trurl said:
Your description of what you did with parity2 is lacking enough details to know what happened.
If you ran without parity2 and without doing New Config to remove parity2 from the array, then parity2 would have become disabled when it couldn't be written. If you did remove parity2 with New Config, then it wouldn't have become disabled since nothing was assigned as parity2. Either way, if you reassigned parity2, it would have been rebuilt when you started the array.
If you aren't still getting sync errors then parity2 must have been rebuilt when you reassigned it, or corrected when you did a correcting parity check.
at the same time my flash drive broke so when i got a new sata cable i also restored my unraid with the backup that had both parity drives
-
3 hours ago, trurl said:
I think the most likely explanation is you had parity errors for some reason, you corrected those, and now parity is correct.
One thing that can cause inconsistent parity checks is bad RAM, but it looks like your parity checks are consistent now.
Have you been following the discussions on the 6.10 release threads as it relates to Dell and NICs? Your syslog seems to have a lot of dumps related to that on startup, don't know if it is relevant or not. Did you upgrade Unraid during the parity checks in question?
I know why I had parity errors I was using only one of my two parity drives. my parity drive two sata cable broke so for a few days i ran it with only one drive and put in the new cable a few days later. but all my drives are gray instead of green right after that. should I or can I force a rebuild of my second parity drive to fix this issue
-
On 6/11/2022 at 6:25 AM, trurl said:
The reason I asked about rebooting is because I was hoping you had not. Syslog resets on reboot so we have lost all syslog information about those previous parity checks.
Don't reboot. Do another non-correcting parity check without rebooting and then post diagnostics so we can compare them.
ok and it didn't find any errors again if its not parity could it be something else
-
On 6/9/2022 at 8:01 AM, trurl said:
Have you rebooted since that first parity check?
Yes multiple times. I even now did a 3rd parity check
-
1 hour ago, trurl said:
So you had it correct parity errors?
Then there were no parity errors because they had already been corrected on that previous check?
sorry I just edited it I meant to say "Write corrections to parity" off
-
so after i moved my server my usb flash drive failed on me along with a sata cable for my
Parity drive two. after getting another flash drive i booted the server up with only one
Parity drive. after that flash drive failed shortly after I'm on my 3rd usb flash drive and i also got a new sata cable. but my drives are gray instead of green so i did a Parity Check with the "Write corrections to parity" check box off it found errors so i ran it again with Write corrections to parity on but it found no errors.
-
Just now, itimpi said:
Did you actually got through the automated licence transfer process with the second USB? If not then there is chance that you have not yet used up your allowed annual automatic transfer so that you can proceed ahead of feedback from Limetech (although they do tend to be quite quick).
Unfortunately I did it just took awhile for it to take affect/didn't know what i was doing. But I had that unraid API error as shown above
-
14 minutes ago, itimpi said:
Are you using the USB Creator tool to create the drive or using the manual method. If using the Creator tool then it could be worth trying again using the Manual method - in my experience it can be more reliable for some reason,
It could also be worth trying a different USB port on the server in case the one you have been using is becoming faulty.
OK it's booted again but because it's my 3rd USB I guess I have to wait for unraid to contact me me back about getting a license for this usb
-
4 minutes ago, itimpi said:
Are you using the USB Creator tool to create the drive or using the manual method. If using the Creator tool then it could be worth trying again using the Manual method - in my experience it can be more reliable for some reason,
It could also be worth trying a different USB port on the server in case the one you have been using is becoming faulty.
I'm doing it manualy I did try the creation tool on my old USB drive but because I'm having problems I've just been copying it over. I'm on my 3rd USB now and copied over all the data
-
39 minutes ago, itimpi said:
The errors on sda are read failures on the flash drive. Is this a new drive or did you try rewriting the original one?
It's the new drive that I've used for other things but erased everything on it to make it my new unraid boot Drive. I'm currently trying a third Drive that I didn't want to get rid of.
-
On 6/5/2022 at 2:37 AM, itimpi said:
There is something wrong then if the original key is in the config folder (which it should be if you copied the config folder over). The system should recognise the key does not match the new flash drive and initiate the transfer process.
if that is not happening to you I can only suggest your email Limetech (contact details at bottom of every forum page) giving details.
I'm still waiting to hear back from unraid support but I again rebooted my system and now I'm getting this error any ideas what it is
-
OK it no longer says beta? I'm very confused. But I have this error now
4 minutes ago, itimpi said:There is something wrong then if the original key is in the config folder (which it should be if you copied the config folder over). The system should recognise the key does not match the new flash drive and initiate the transfer process.
if that is not happening to you I can only suggest your email Limetech (contact details at bottom of every forum page) giving details.
-
Well I booted my unraid and it has all my files and vms / dockers but it says beta and that I can make a new key next year. I contacted support to see what they can do.
-
I copied everything and it told me to buy a new key
-
ok i got a new usb and i got it to boot bye copying over all the files from the old usb. but I how to active it or move my key that I purchased for unraid
-
I just [put the usb into my pc and it found errors says it fixed them but if i scan again the errors are still there there so i tried booting from it no luck an make a copy of the the files but I assume because of the license it wont let it boot what do i need to do?
-
I also tried booting into safe mode. but I get the same error message
-
Is my USB dying? I thought a reboot would automatically fix it but it didn't. All I did was turn it off for an update turned on fine and logged in. Turned off again to put in a 10gb nic and this happen. I've used this exact Nic in this system before
-
On 4/7/2022 at 1:24 AM, itimpi said:
I also note that that the docker.img file is explicitly set to be on disk1. Normally you want it to be on the cache to get better performance from your docker containers.
It is also set to be 100GB which seems excessive. The default of 20GB is enough for most people unless you have a lot of docker containers. Is there a reason you have such a large size? If you find you are filling that up when docker containers are running you may have a docker container mis-configured to write into the docker.img file when it should be mapped to use Unraid storage external to the containers.
thank you after deleting the img file from inside the docker setting docker is working and I'm redownloading everything now. i also changed the size to 20gb
one more thing my server is running very slow and buggy so i looked at my logs and its filled with this
-
56 minutes ago, itimpi said:
You are likely to get better informed feedback if you post your system’s diagnostics zip file.
thank you, after a reboot i got my shares back but my docker wont start. i did edit the docker.img settings and nothing
-
my dockers don't work and my shares are gone all i did was add a cache drive
Parity error (I think)
in General Support
Posted
o, I'm sorry. I thought I meant something went wrong. id didn't change that setting. must be a new default