Jump to content

JorgeB

Moderators
  • Posts

    67,812
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Click on cache and there will be a scrub option, need to scroll down. Should be safe before, but I would recommend after just in case there are some unexpected issues.
  2. Some controllers don't support spin down, mostly RAID controllers, that one should if flashed to LSI IT mode.
  3. Run a scrub on the pool to see if it can sync both devices, check output in end, check all errors were corrected, possibly some device issues with sdi, pool is also very full, should avoid that, try keeping it under 80% used, 90% tops.
  4. Controller is using or connected to a SATA port multiplier, don't use those, use one of the recommended controllers.
  5. OK, logs is clean now, first lets cancel the btrfs balance, to do that: mkdir /temp mount -o skip_balance /dev/sdj1 /temp If mount is successful type: btrfs balance cancel /temp then umount /temp Now unassign cache1, start array, stop array, re-assign both cache devices, start array and post new diags.
  6. Please post the diagnostics after a format attempt.
  7. Unassign all cache devices, start array, stop array, re-assign all cache devices, start array, that should do it.
  8. EL1 is a single expander backplane, took another look and you have two HBAs, so looks like you have both connected to the same expander, use just one, you can connect both cables form one HBA to the expander for increased bandwidth, but don't connect two HBAs to the same expander, that can be done for redundancy when supported by the OS, Unraid doesn't not support that.
  9. Try adding 30 secs or so to the shutdown timeout.
  10. Use the recover password procedure, it will work the same.
  11. Don't need a license for the trail key, hence trial, it's just to test if it boots correctly and the server is accessible.
  12. Try booting with a trial key, just to check if it's flash/config related.
  13. Docker image is corrupt, delete and recreate.
  14. I wouldn't, there could be small bottleneck when using the outer sectors with 24 drives, but nothing major.
  15. They are likely JMB585 based, and if yes they are in the recommended list:
  16. There appear to be two cables connected form the same HBA to two different expanders, Unraid doesn't support SAS multipath, connect just one cable, or both to the same expander if dual link is supported, then post new diags and the output of btrfs fi show
  17. Constant errors with this SSD: Model Family: Crucial/Micron Client SSDs Device Model: CT250MX500SSD1 Serial Number: 2011E2946AD2 Check/replace/swap cables, but there's no valid SMART report, could be a device problem..
  18. Unclear if the problem is the disk/connection or controller since the driver for that controller crashes when there's a problem, I would suggest swapping cables with a disk connected to the onboard ports and trying again, but that controller should be replaced when possible anyway, with one of the recommended models.
  19. Not surprised, since I suspected that NIC was not supported by v6.10.x, and the NIC was being detected, but since it's USB it doesn't show up on lspci, me being a dum dum. Soon there should be an easy way to install out of tree drivers, then you should be able to make that NIC work with a newer release.
  20. There could be some compatibility issue with the HBA, try it in a different PCI slot if available.
  21. No NIC is being detected other than the Wi-Fi, make sure that USB dongle is working and connected, though not sure it will be supported by Unraid.
×
×
  • Create New...