Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,696

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Syslog is missing the last days, reboot and post new diags after array start.
  2. JorgeB
    Enable syslog server and post that log after a crash.
  3. JorgeB
    Sep 26 22:05:21 Tower kernel: mpt2sas_cm0: SAS host is non-operational !!!! Problem with the HBA, but before this there were already multiple disk issues, could be controller, cables, power issue, etc, start by checking the controller is well seated and sufficiently cooled, you can also try another PCIe slot if available.
  4. JorgeB
    You can easily recreate the docker image, then start the dockers one by one.
  5. JorgeB
    There are constant ATA errors on disks 1 and 3, check replace cables on both, there's also data corruption being detected on disk1, run memtest.
  6. JorgeB
    This can help sometimes: https://forums.unraid.net/topic/111161-pcie-errors/?do=findComment&comment=1013378
  7. JorgeB
    If you swapped cables with a working device and errors continue it suggests a disk problem, despite the healthy looking SMART.
  8. JorgeB
    You're using sas3flash that's for SAS3 models, you needed sas2flash.
  9. JorgeB
    Please post the diagnostics.
  10. JorgeB
    Please use the existing docker support thread:
  11. JorgeB
    Failing to copy the syslog possibly, make sure you're using a USB 2.0 port, server crashing appears more hardware related, I would always go with Intel for Unraid, though some are using Ryzen based servers reliably.
  12. JorgeB
    These are disks 5 and 10: Sep 25 14:45:03 Yggdrasil kernel: md: import disk5: (sdr) WDC_WD40EFRX-68WT0N0_WD-WCC4E1467225 size: 3907018532 Sep 25 14:45:03 Yggdrasil kernel: md: import disk10: (sdq) WDC_WD80EFZX-68UW8N0_R6GXW52Y size: 7814026532 What controller are the missing disks connected to? Also post a photo of them being detected in the BIOS.
  13. JorgeB
    Please don't crosspost, continue discussion in the other thread:
  14. JorgeB
    That suggests a xfs_repair issue, update to v6.10-rc1 and try again, it includes newer xfs-progs.
  15. JorgeB
    Please post the xfs_repair command you used and the complete output.
  16. JorgeB
    This means the devices have all the same ID, quite common with USB devices, in this case: Sep 23 22:18:59 Tower kernel: scsi 8:0:0:0: Direct-Access JMicron Generic 0209 PQ: 0 ANSI: 6 That won't work with Unraid, it requires each device to have a unique identification.
  17. JorgeB
    Don't have much experience with wifi 6, but with any wifi you'll never get close to the link speed, unlike cable, though I would expect wifi 6 could do better than that.
  18. JorgeB
    https://wiki.unraid.net/Un-Official_UnRAID_Manual#High_Water
  19. JorgeB
    Yes, with about 3GB/s usable, 2.2GB/s if connected to an expander with a single link.
  20. JorgeB
    See here first, if all is already correctly configured enable syslog server and post that log after a crash.
  21. JorgeB
    You can see which disk it is by looking at lsscsi on the diags: [11:0:3:0] disk SEAGATE ST6000NM0285 EF04 /dev/sdm /dev/sg12 state=running queue_depth=254 scsi_level=7 type=0 device_blocked=2 timeout=30 dir: /sys/bus/scsi/devices/11:0:3:0 [/sys/devices/pci0000:00/0000:00:03.2/0000:0c:00.0/host11/port-11:3/end_device-11:3/target11:0:3/11:0:3:0] sdm is currently Disk4
  22. JorgeB
    There's no SMART report for that disk in the diags, see if you can get one manually.
  23. JorgeB
    It's disk3.
  24. JorgeB
    It's fine to move them, devices are tracked by serial number.
  25. JorgeB
    At least get the syslog: cp /var/log/syslog /boot/syslog.txt
×
×
  • Create New...