Jump to content

JorgeB

Moderators
  • Posts

    67,831
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Could be this issue: https://forums.unraid.net/bug-reports/prereleases/69x-610x-intel-i915-module-causing-system-hangs-with-no-report-in-syslog-not-alder-lake-r1674/ If you don't need the iGPU driver block it from loading, if it doesn't help enable the syslog server and post that after a crash.
  2. Disk is OK for now, but SMART is showing some issues, so keep and replace if there are more errors or replace now.
  3. If you zeroed out all drives before removing them parity should remain valid, do you by any chance still have diags showing the complete process? In any case, and as long as the next check doesn't find any errors, I wouldn't worry, most likely some step was missed or not completed correctly.
  4. Yes, but it's a 12TB drive, not so widely used as lower capacities, it's still my best guess.
  5. I believe this one was mentioned before, no personal experience: https://www.donordrives.com/
  6. 53:00.0 RAID bus controller [0104]: Broadcom / LSI MegaRAID SAS 2008 [Falcon] [1000:0073] (rev 03) Subsystem: Broadcom / LSI MegaRAID SAS 9240-8i [1000:9240] Kernel driver in use: megaraid_sas Kernel modules: megaraid_sas Controller is not flashet to IT mode, it will work like that if you create individual jbod/raid0 volumes for all disks, but it's not recommended, you should flash it to IT mode.
  7. Run fstrim -va and check the result, it will trim all supported filesystems and show it in the output.
  8. Where do you have libvirt.img stored?
  9. It's been like that for a while, at least from v6.9 onward IIRC, but I would also prefer those settings would remain untouched.
  10. You can download them on the console, see the link.
  11. Run an extended SMART test on disk4.
  12. Best bet would be to ask in the existing plugin support thread.
  13. If you removed array disks you need to do a parity sync, not parity check.
  14. If you have enough SATA ports you can add one or both 800GB devices and remove the other ones, one a time.
  15. If the drives are being detected by the LSI BIOS it's not the cables and they should also be detected by Unraid.
  16. That's how high water works, disk2 is past the 50% mark, all other disks are smaller, only once you get over 75% used on disk1 it will write to another disk.
  17. It's still dropping offline: Aug 16 10:56:06 BIGDADDY kernel: ata1: hard resetting link Aug 16 10:56:12 BIGDADDY kernel: ata1: COMRESET failed (errno=-16) Aug 16 10:56:12 BIGDADDY kernel: ata1: reset failed, giving up Aug 16 10:56:12 BIGDADDY kernel: ata1.00: disabled Aug 16 10:56:12 BIGDADDY kernel: ata1: EH complete If you already replaced both cables try a different SATA port.
  18. The flash drive is dropping offline, use a different USB controller, ideally USB 2.0, not 3.0
  19. Don't see how, looks like a board/BIOS issue, look for a "keep booting on errors/no keyboard" or similar setting in the BIOS.
  20. To see if it's FUSE related enable disk shares and transfer directly to the cache share, see if there's any difference.
×
×
  • Create New...