Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,416

  • Joined

  • Last visited

  • Days Won

    705

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Yes, by the type of check logged, also by the way it reports the errors found (incorrect vs corrected). Non correct: Apr 3 00:03:50 Poseidon kernel: mdcmd (42): check nocorrect .... Apr 3 01:27:24 Poseidon kernel: md: recovery thread: P incorrect, sector=923136256 Correct: Apr 3 13:16:02 Poseidon kernel: mdcmd (43): check correct .... Apr 3 14:12:54 Poseidon kernel: md: recovery thread: P corrected, sector=923136400
  2. JorgeB
    Correct : Apr 4 10:49:49 Tower kernel: sd 2:0:1:0: [sdc] Unsupported sector size 528. Unraid only supports 512B or 4KB sectors, there's a FAQ entry on how to reformat those drives.
  3. JorgeB
    No because it's letting you know that it found those errors, I guess there could be an extra field to say correct or non correct, or for example: 1st one would say 2011 errors found 2nd one could say 2011 errors corrected You can ask for that as a feature request, though maybe there is already a similar one.
  4. JorgeB
    First check detected 2011 sync errors. Second check fixed those 2011 sync errors.
  5. JorgeB
    1st check was the auto check, that one is non correct. 2nd check, done by you was correct, all errors were corrected. Clear now?
  6. JorgeB
    The most likely culprit would be the Win desktop, try to get a different computer to test with, but it can also be a NIC, switch, cable, etc.
  7. JorgeB
    Yes, that what I said above:
  8. JorgeB
    No, you can do one if you want to confirm all is good, but it would be fine to wait for the next scheduled check. Next time, if an unclean shutdown happens and sync errors are detected, and there are usually a few errors right in the beginning, you can cancel the auto check and start a correcting one.
  9. JorgeB
    Auto parity check after an unclean shutdown is non correct, the one you did after that was correct, so next one should be error free.
  10. JorgeB
    Changed Status to Closed Changed Priority to Other
  11. JorgeB
    Sleep is not officially supported by Unraid, but you can ask for help on the general support forum or the sleep plugin support thread.
  12. JorgeB
    There are various possibilities, for a recent user it was the AV software, basically you need to try various different things until you find the culprit.
  13. JorgeB
    Macvlan call traces are usually related to having dockers with custom IP addresses, more info here, in the end there was a general protection fault, possibly unrelated and might be a hardware issue, but see if getting rid of the call traces helps.
  14. JorgeB
    No, only the trial license requires internet connection, and only at array start.
  15. JorgeB
    With Unraid there's no real need to schedule extended SMART tests (at least for array devices), since a parity check works the same, i.e., it reads all sectors of all disks, usually once a month is the recommended frequency for that.
  16. JorgeB
    Not sure, quick google search suggests a Megaraid controller, no IT mode: https://forums.servethehome.com/index.php?threads/ibm-serveraid-m5110-cross-flashing.657/
  17. JorgeB
    Tell me about it, very strange times, just what the world needed, an f*ing pandemic. Hopefully the data is mostly all there.
  18. JorgeB
    OK, but that's why I mentioned to only rebuild on top if the data on the emulated disk looked correct.
  19. JorgeB
    https://wiki.unraid.net/Un-Official_UnRAID_Manual#Split_level
  20. JorgeB
    If the emulated disk is not showing all the data you can mount the actual disk with UD and see if mounts and looks OK (note that array must be stopped and the disk unassigned), and if it does you could do a new config instead of rebuilding.
  21. JorgeB
    That's good and it will confirm if the disk is really failing, and it does appear to be, in any case parity isn't 100% valid because of the read errors on that disk.
  22. JorgeB
    Yep, everything looking fine at the moment, you might hold on on the replacement for now, just keep an eye on it, but it it happens again I would replace it.
  23. JorgeB
    First run with just -v, if it asks for -L, and it likely will, use it.
  24. JorgeB
    You need to update Unraid, some older releases have a bug on xfs-progs.
  25. JorgeB
    Likely that SMART attribute is no longer failing now, please post new diags
×
×
  • Create New...