Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,554

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Disk14 needs to be replaced, if there were errors on that disk only and you have dual parity the other rebuilt disk should be OK, but would need the diags to confirm.
  2. JorgeB
    This is not a stock Unraid feature, you should post in the support thread for the plugin you're using for that.
  3. JorgeB
    Memtest only works if you boot in legacy mode, it won't in UEFI mode, nothing on the syslog that I can see, one thing you can try it to boot the server in safe mode with all docker/VMs disable, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
  4. JorgeB
    It won't hurt to post that, since the diags after rebooting aren't much help, but if there's nothing in that log most likely it's a hardware issue.
  5. JorgeB
    SMART is failing and the disk should be replaced.
  6. JorgeB
    You can run a balance but don't see how there could be duplicate files, pools config looks correct, note that due to a btrfs bug free space reported when using a raid1 pool with an odd number of devices will almost always be incorrect.
  7. JorgeB
    If you need to move data you need to do it manually, other option is to use different split level settings.
  8. JorgeB
    8GB (or 16GB for the future) should be enough.
  9. JorgeB
    I missed that part, but it would be really bad luck that any out sync sectors caused by the unclean shutdown (usually mostly in the beginning of the disk) coincided with the read errors, and if that was the case I would expect they would be detected by parity2.
  10. JorgeB
    It can happen with for example an unclean shutdown, or some hardware issue like bad RAM, and at most could be a btrfs issue, not Unraid.
  11. JorgeB
    Then you should reboot and post new diags after that's fixed, difficult to look for issues in a syslog filled with other errors, related or not.
  12. JorgeB
    One final data point, SMR (disk3) vs CMR (disk4), similar amount of data transferred, note the time and average speed differences:
  13. JorgeB
    Disk is OK for now, since it passed the SMART test, but the previous errors were almost certainly a disk problem, and you should keep an eye on these attributes: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 792 200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 60 If they continue to increase it will likely fail again soon.
  14. JorgeB
    The errors were from SATA array devices, e.g. disk1 and disk2 for a long periods of time (1 hour), also don't forget to update the LSI firmware.
  15. JorgeB
    Changed Status to Closed Changed Priority to Other
  16. JorgeB
    This was a filesystem problem: Nov 28 15:16:22 nicknas2 kernel: BTRFS: error (device nvme0n1p1) in __btrfs_free_extent:3066: errno=-2 No such entry Nov 28 15:16:22 nicknas2 kernel: BTRFS info (device nvme0n1p1): forced readonly If you reformatted cache you already did what needed to be done, closing this since it's a general support issue.
  17. JorgeB
    Not necessarily related but you're getting a lot of Power-on or device reset occurred on multiple disks, this is usually a power/connection problem, also a good idea to update the LSI firmware since it's very old.
  18. JorgeB
    28/11/2020 14:04,Alert,192.168.1.6,XFS (dm-0): Corruption detected. Unmount and run xfs_repair Check filesystem on disk1.
  19. JorgeB
    Surprised it ever worked, you need to use the latest beta for that NIC to be correctly supported, you can download it from here: https://s3.amazonaws.com/dnld.lime-technology.com/next/unRAIDServer-6.9.0-beta35-x86_64.zip
  20. JorgeB
    Try this and post that log after a crash, if you haven't yet also a good idea to run memtest.
  21. JorgeB
    Please post the diagnostics: Tools -> Diagnostics
  22. JorgeB
    Iperf is showing low performance, but yes should be getting more than 30MB/s, though a first you mentioned 10MB/s? Try with another client if possible, like a WIndows PC.
  23. JorgeB
    If a read error occurs during a parity check that(those) block(s) will be recalculated from the other disks plus parity and written back to the offending disk, if there's a write error the disk will be disable, if there isn't data can be considered OK (assuming of course that parity was 100% valid before).
  24. JorgeB
    That's a known issue, fixed for next beta.
  25. JorgeB
    That's what you asked for. Yes, the replacement is done online, i..e, you can still use dockers/VMs during it, that's the main advantage.
×
×
  • Create New...