Jump to content

JorgeB

Moderators
  • Posts

    67,686
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. You should only do that if the missing disks are detected and can be mounted correctly.
  2. Similar to these: You can, changing cables won't change anything like that, disks are assigned using their serial numbers.
  3. If the disks are still missing try a new PSU, and check that any power/reset errors are gone before attempting rebuilds.
  4. Since the SMART test was successful disk should be OK, replace/swap cables to see if there's any difference.
  5. Most of that used space will be filesystem overhead, did you format the disk before or after rebuilding?
  6. If you didn't start the array after unassign it you just need to assign it back, if you did please post the diagnostics: Tools -> Diagnostics
  7. This usually happens if the drive dropped and reconnected with a different letter.
  8. If Docker/VM services are using the cache/pool disable them, unassign all cache devices, start array to make Unraid "forget" current cache config, stop array, reassign all cache device(s) (there can't be an "All existing data on this device will be OVERWRITTEN when array is Started" warning for any cache device), re-enable Docker/VMs if needed, start array.
  9. Yes, because parity need to be updated simultaneously, if you need to do this for a large amount of data best to temporarily disable parity, of course array will be unprotected.
  10. Not without the persistent syslog, set it to mirror to the flash drive then post that after a crash.
  11. RAID mode is fine with Intel fakeRAID, it still uses the AHCI driver. I would run memtest, multiple filesystem corruption without an apparent reason could be the result of bad RAM.
  12. Because you're using a NetApp enclosure SMART report is pretty much useless, I believe there's a way of getting a correct report manually, but you'll need to search the forum since I never used one of those enclosures.
  13. Disk17 dropped offline so there's no SMART, check connection and post new diags after that but most likely disk is fine, disk15 on the other hand appears to be failing, and that could be a problem since you don't have dual parity.
  14. Unfortunately there's nothing relevant logged before the crash, this usually indicates a hardware problem, there are some unrelated ATA errors you should also check, likely a power/connection issue.
  15. Why not? You should be able to back up to the array, or for example to an unassigned device mounted with UD plugin.
  16. No, multpitath is for redundancy, not extra bandwaith, usually you connect two HBAs to the same expander for that.
  17. Like mentioned in the link above they are under "legacy products"
  18. It's not always easy to find errors with memtest when getting so few errors, since you have 4 DIMMs I would suggest removing a couple and run two correcting parity checks, if issue persists with both sets then it's likely not a RAM problem, note that the first check after the problem is fixed might still find errors, but next ones should always find 0.
×
×
  • Create New...