Jump to content

JorgeB

Moderators
  • Posts

    67,589
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Not using the md device means parity is no longer valid, you should run a correcting parity check.
  2. Unraid doesn't stripe data in the array, so read speed can never be faster than a single disk, pools can be faster.
  3. Try in a different slot if available, until it's detected in the devices it will never work, you can also try it in a different PC just to make sure it's working.
  4. After formatting the cache pool did you re-create the docker image or copied the old one?
  5. Uninstall the Sleep plugin.
  6. Only model affected appears to be the ST8000VN004.
  7. There have been a couple of reports where it looks like the shutdown time-out is not being honored, i.e., Unraid considers an unclean shutdown after a couple of seconds even if the set time is much longer, changing the setting (Settings -> Disk Settings) to re-apply it fixed it.
  8. CRC errors don't reset but it they keep increasing there's still a problem.
  9. Disk looks fine, but since both parity drives are invalid it can't be emulated, if you already replaced cables do another new config to enable all the disks and start a new parity sync.
  10. Delete that file, it's not a valid Unraid key.
  11. Libvirt.img is where the XMLs for the VMs are stored.
  12. It's a known issue with that PMC controller, if it's an option I would recommend replacing it with an LSI HBA, you'll need a new cable though.
  13. If it's an option I would recommend replacing it with a recommended controller, if not and it was working best to stick with v6.8.
  14. Filesystem check is done with the disks assigned, if there's no option in the GUI you need to first set the correct filesystem by clicking on that disk, or run it in the console.
  15. Disk looks fine, replace the cables and try again, you should also update the LSI firmware since it's quite old.
  16. Timeout appears to be kicking sooner than it should, go to Settings - Disk Settings and change the shutdown timeout to a different value just to re-apply, set it to like 60 secs.
  17. Normal when bridging is enable. Nope sorry, but it happens to other users, possibly hardware related.
×
×
  • Create New...