Jump to content

JorgeB

Moderators
  • Posts

    67,737
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Jan 6 19:28:20 Pensieve kernel: ahci 0000:02:00.1: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000f address=0x800006801000000 flags=0x0010] Problem with the onboard SATA controller, quite common with some Ryzen boards, look for a BIOS update or use an add-on controller.
  2. Read SMART Data failed: scsi error badly formed scsi parameters Disk isn't giving a full SMART report, this is usually a disk problem, you can try swapping cables just to confirm.
  3. Correct SFF-8088 to 4x SATA will work, obviously cables need to be rerouted inside de case.
  4. They only change color/status if a write fails, and it didn't yet, it also passed a recent extended SMART test, which also supports that it's OK for now, but the failing now SMART attribute might indicate it will fail sooner or later.
  5. That look like a bug, since you're not using encryption set default filesystem to xfs (Settings -> Disk Settings)
  6. You can stop the array, and if/when all pool devices are back online and appear on the main page and are already assigned, after a page refresh if needed (you can't just re-assigned them manually), you can just re-start it.
  7. It could, but more likely it would cause problems directly on the disks, independent of the controller they are connected to.
  8. I didn't say you should replace the disk, but the controller. Yes, possibly the controller, probably the controller f the issues have been happening on disks connect there.
  9. This is the Unraid default for disks, parity partition starts on sector 2048, it means it was partitioned outside Unraid, recently Unraid started supporting that starting sector for SSDs so it doesn't complain, but because of that there are a few less sectors available, to resolve this you'd need to wipe that partition then let Unraid repartition it and re-sync parity.
  10. You should monitor the attributes, but if the extended test passes disk is OK.
  11. Disks have the same exact size, possibly the partition isn't starting on the default sector, post output of: fdisk -l /dev/sdb
  12. https://forums.unraid.net/topic/117581-cache-ssd-broken-how-to-replace/?do=findComment&comment=1076957
  13. It's the same, just replace that parity disk and start the array to re-sync parity.
  14. SASLP is not recommended for a long time, good idea to replace it, especially if the disks giving you issues are connected there.
  15. Those are slim optical drive power cables, you need SAS to SATA forward breakout cables to use an LSI HBA.
  16. In the syslog. Not necessarily, like mentioned it's usually a power or connection problem, it's like the device disconnected and connected, could be power, could be SATA. To the device, in this case disk4
  17. Run an extended SMART test to confirm if it's a disk problem or not, could also be some compatibility issue if it only happens with that model.
  18. Extended SMART test passed so disk is OK for now.
  19. Cache is reporting media errors, xfs_repair won't work on a failing device, best bet is to clone the device to a new one with ddrescue then use xfs_repair on it.
  20. Jan 4 17:59:48 15620-BEAST kernel: sd 1:0:6:0: Power-on or device reset occurred These repeating errors suggest a power/connection problem, could be the backplane, or backplane slot, or even the HBA, though less likely, start by using a different slot if available, or swap lots and see if the issue stays with the slot.
  21. Not that uncommon with filesystem corruption, take a look to see if there's anything important/salvageable there.
×
×
  • Create New...