Jump to content

JorgeB

Moderators
  • Posts

    67,432
  • Joined

  • Last visited

  • Days Won

    706

Everything posted by JorgeB

  1. Like mentioned I've seen errors logged before, but never disks getting disabled because of that, still worth trying.
  2. It is, but it uses the same driver as the SASLP/SAS2LP, and those have several issues with latest Unraid releases, and it's usually similar, they were working great before until they don't anymore.
  3. That's expected, it will need to be rebuilt. There's should be a check mark to allow the array to start with a missing disk.
  4. That's mostly worthless as a way to access a disk health, it only changes if there's a FAILING NOW SMART attribute.
  5. Then you can ignore that, there's also fs corruption on disk4 that I missed when I first looked since log is heavily spammed with the oom errors. Mar 17 12:18:05 unRAID kernel: XFS (md4): Metadata corruption detected at xfs_dinode_verify+0xa5/0x52e [xfs], inode 0x90d66a8e dinode Mar 17 12:18:05 unRAID kernel: XFS (md4): Unmount and run xfs_repair
  6. Many using that including myself, post a screenshot of the network settings for both servers, also you'll need to use the 10GbE IP address from all transfers you want using it.
  7. The LSI spin up/spin down errors started only on the latest Unraid releases.
  8. I've seen some logged errors recently with LSI and spin downs/spin ups, but they appear harmless, not actual errors, and never disable a disk, but you could try disabling spin down for a couple of days and see it it makes any difference.
  9. There's not one answer, it just depends on what's best for you.
  10. That question is answered in the link above, if you just take the time to read and understand it.
  11. https://wiki.unraid.net/Un-Official_UnRAID_Manual#High_Water
  12. Not because of that but it should still be replaced because it failed the extended SMART test.
  13. Logs are lost after a reboot, so no way to see what might have caused that, you can try this to see if it catches something in case it happens again, but it might not if it's a hardware problem.
  14. Yes If you transfer to a user share, no if you transfer to a disk share.
  15. https://lime-technology.com/forums/topic/72837-error-log-filled-to-100-in-1day-47min-with-this/?do=findComment&comment=669775
  16. Rebuilding won't help, a deleted file recovery util like UFS explorer might.
  17. I suspect the problem is controller related, and I would recommend replacing that rockeraid with a recommended controller. If you unassing disk3 and start the array the emulated disk should mount correctly, then you'll need to rebuild, ideally on a new controller.
  18. If you are sure the assignments are correct just enter the old passphrase twice, then check "parity is already valid" before starting the array.
  19. Yes, re-formatting is usually the best course of action for that, also you can see here for how to better monitor a cache pool for connection issues.
  20. No, just replace it, Unraid won't notice any difference.
  21. Server is constantly running out of memory, you should try and fix that first.
  22. I very much doubt there's any data to recover, but please try to follow the instructions:
  23. Extended SMART test failed = failed disk SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 10% 28170 5845199728
×
×
  • Create New...