Jump to content

JorgeB

Moderators
  • Posts

    67,826
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Yes, but I wanted to see ones showing the parity sync, which is going at 185MB/s, quite normal, also note that most of your disks are SMR, including parity, so some write performance degradation is expected.
  2. Correct, and the main Unraid NIC must be set to eth0.
  3. Go to Settings -> Network Settings -> Interface rules and make the Gbit NIC eth0, then reboot, it will have the same settings as the older eth0. eth1 should then use a different subnet for the direct PC connection.
  4. Parity sync errors were immediately after the disk read errors, so yes, replacing it should fix that, assuming parity was 100% in sync.
  5. Please try rebooting in safe mode to rule out any plugin and post new diags if you see the same.
  6. Aug 1 14:00:07 Tower kernel: nvme nvme1: Device not ready; aborting initialisation, CSTS=0x0 Aug 1 14:00:07 Tower kernel: nvme nvme1: Removing after probe failure status: -19 Device is failing to initialize, if you can test with a different OS to confirm if the device is working or not.
  7. Disk is OK for now, but like mentioned it doesn't look very good, it will likely fail again in the near future, up to you if you want to give it another shot or replace now.
  8. libvirt.img should be excluded, it's a file that can change.
  9. Use the recover password procedure: https://wiki.unraid.net/Manual/Troubleshooting#Lost_root_Password
  10. Either one works, use the most convenient for you.
  11. If you don't have parity you can just add them back to the array.
  12. Please use the existing plugin support thread:
  13. Make sure disk shares are enabled, then click on cache and "compute" to see what exactly is using the space.
  14. Diags are incomplete, shares are missing, I wanted to see if there was something else on cache.
  15. I would run memtest for a couple of hours at least.
  16. Rebooting should fix that, then grab diags after array start.
  17. That looks more like a power connection/problem, and the disk looks healthy, but if the cables were replace/swapped and the problem persists it might be a disk problem, like mentioned above you should run an extended SMART test since the ones started never finished, likely due to spin down.
  18. Looks like a power/connection problem with the parity disk, check/replace cables and try again, look at the syslog to confirm the ATA errors are gone, or post new diags.
  19. It's logged as a disk problem, run an extended SMART test on disk3.
×
×
  • Create New...