Jump to content

JorgeB

Moderators
  • Posts

    67,594
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. One thing that causes that is having multi-path enable, Unraid doesn't support that, make sure there's only one cable going to each enclosure.
  2. Older 8TB drives were helium filled, newer ones are air file an run considerably hotter.
  3. It should be the same as before, what happens if you start the array?
  4. Looks like a connection/power problem, disk dropped offline, replace cables to rule them out and if the emulated disk is mounting and contents look OK you can rebuild on top.
  5. Not using the md device means parity is no longer valid, you should run a correcting parity check.
  6. Unraid doesn't stripe data in the array, so read speed can never be faster than a single disk, pools can be faster.
  7. 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.
  8. After formatting the cache pool did you re-create the docker image or copied the old one?
  9. Uninstall the Sleep plugin.
  10. Only model affected appears to be the ST8000VN004.
  11. 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.
  12. CRC errors don't reset but it they keep increasing there's still a problem.
  13. 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.
  14. Delete that file, it's not a valid Unraid key.
  15. Libvirt.img is where the XMLs for the VMs are stored.
  16. 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.
  17. 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.
  18. 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.
×
×
  • Create New...