Lassley7

Members
  • Posts

    84
  • Joined

  • Last visited

Everything posted by Lassley7

  1. Then what was throwing the errors to begin with? It had to be bad disk/data…
  2. The disk wasn’t good, that’s why I got into this mess to begin with. That’s why I’m confused as to why it’s now showing good, when nothing has changed other then the data is on a new disk in the array and this one is now empty.
  3. From the beginning we narrowed this issue down to a bad connection/drive. After doing all the steps to recover my data off that drive, I then ran 2 extended smart tests. And they both passed without error. Does this mean the drive was good? And the data that I copied back over to the array was not? I’m confused on how it was a bad drive and now it’s showing good. Should I put this drive back in the array? I posted the smart test above
  4. But IF it’s not, will that corrupt parity again? Folks on discord said unraid doesn’t care about the data only the sectors? Also would you trust putting this drive that was throwing errors back in? Now it reads as a good drive so that doesn’t make sense to me. That tells me the data that was bad on that drive is now back in the array..
  5. So I got everything back up and running. I’m going to assume that corrupted data can throw errors again? I moved all the data without issues too a new drive, once the “bad” drive was empty I ran 2 extended smart test and both said passed 0 errors.. doesn’t this likely mean I likely moved bad data back too my array? And the drive was actually never bad… should I run a new parity sync? poseidon-smart-20230905-0505.zip
  6. Will krusader do this? Do you have a recommended tutorial for rsync for my situation? Thanks for all the help recently
  7. What app would you recommend? I’ve never had too copy over “bad” data before anytime I’ve had a drive fail I’ve been able too use the proper way of emulating and rebuilding its all replaceable data on that drive so I’d rather skip ANY that could be bad and not risk it “trying multiple times first”
  8. Will it skip them or will I have to tell it to skip them using UD? So a bulk copy should be fine? Also is a party sync after copying with UD needed right away
  9. How would you handle this once the sync is done? Could the errors be from empty bits? “Bit rot” or likely in the files? Would u copy a little at a time and test? I don’t want too corrupt my array again
  10. I followed The "Remove Drives Then Rebuild Parity" Method as a bunch suggested on discord… they said to then mount the disk with issues using UD and copy it over… I hope this wasn’t a mistake
  11. what if one already decided too remove the config for the new drive and now its showing as a "new device" and start is saying `Start will start Parity-Sync and/or Data-Rebuild.`
  12. the drive has sadly been formatted.. what i mean by empty is theres no important data on it as of now so how can one replace the failed one with one that is already added to the array... the failed drive did populate as emulated and from what i could tell all data was there.. the problem is i dont have the funds for another disk atm i just added this new one im reffering too, can a new config accomplish this?
  13. How can I replace that failed disk with an empty one that’s already part of the array. I just added it there’s no data on it but it is in fact part of the array now assuming I have to do a new config at this point? Since I stupidly added my only new drive already
  14. Well when running a non correcting sync is when the errors happen so how does one assume it’s good?
  15. Well I swapped it with a different tray location and started sync again just woke up to that same disk showing errors. Sounds to me like it’s time too replace that disk all 5 syncs I’ve tried have all been errors on that single disk.. am I safe too go ahead and take that drive out and assign a new blank one in it’s place and rebuild? Do I do a non correction sync?
  16. well we came back with errors again.. same disk.. going too try swapping too a different tray if that doesn't do it im assuming bad drive? heres diag just incase but appears too be the same errors poseidon-diagnostics-20230831-2034.zip
  17. Correct so if the non correcting check has 0 errors I then need to run a correcting check? Or am I good with just the non correcting check with 0 errors
  18. If the next parity sync is fine, would u then run a parity correction pass? Or would you run more than one non correction sync?
  19. So adding new disk won’t add to the party problem. That’s good to know yeah I’m not a fan of sas backplanes too breakout cables.. unfortunately that’s all I had to work with and up until now I’ve seen no issues. Are u suggesting this is NOT a bad drive and more 99% a bad connection? If party has errors again would you try a new slot or a new breakout cable
  20. Reseated my breakout cables. Also cleaned some dust out of the machine. I don’t see anything obvious on the cables. Time too try a new non correction parity? Should I cancel the zeroing pass on the new drive I’m adding and prioritize parity?
  21. i decided too upgrade my parity disk too a larger one so i can have larger disks in the array, i ran a non correcting check and im getting read errors on disk 5. can someone look into the diag and tell me if they think a correcting pass should be done, or what i should do next? poseidon-diagnostics-20230830-1754.zip
  22. it keeps changing to "update" or is not up to date also showing this on the my server dashboard
  23. ended up being a port forward issue or a dns resolver issue fixes: remove all port forwards turn off docker/vm set http:80 https:443 added myunraid.net to dns resolver in pfsense not completely sure witch one did the trick or if all did
  24. I’m having the same issue. Did you ever get yours going??