trurl Posted August 6, 2022 Share Posted August 6, 2022 Aug 6 15:36:17 Tower kernel: XFS (md1): Mounting V5 Filesystem Aug 6 15:36:17 Tower kernel: XFS (md1): Starting recovery (logdev: internal) Aug 6 15:36:17 Tower kernel: XFS (md1): Ending recovery (logdev: internal) Aug 6 15:36:17 Tower kernel: ata9.00: exception Emask 0x10 SAct 0x400000 SErr 0x190002 action 0xe frozen Aug 6 15:36:17 Tower kernel: ata9.00: irq_stat 0x80400000, PHY RDY changed Aug 6 15:36:17 Tower kernel: ata9: SError: { RecovComm PHYRdyChg 10B8B Dispar } Aug 6 15:36:17 Tower kernel: ata9.00: failed command: READ FPDMA QUEUED Aug 6 15:36:17 Tower kernel: ata9.00: cmd 60/08:b0:b8:47:5c/00:00:07:00:00/40 tag 22 ncq dma 4096 in Aug 6 15:36:17 Tower kernel: res 40/00:b0:b8:47:5c/00:00:07:00:00/40 Emask 0x10 (ATA bus error) Aug 6 15:36:17 Tower kernel: ata9.00: status: { DRDY } Aug 6 15:36:17 Tower kernel: ata9: hard resetting link Aug 6 15:36:24 Tower kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Aug 6 15:36:24 Tower kernel: ata6.00: configured for UDMA/133 Aug 6 15:36:27 Tower kernel: ata9: softreset failed (1st FIS failed) Aug 6 15:36:27 Tower kernel: ata9: hard resetting link Aug 6 15:36:33 Tower kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Aug 6 15:36:33 Tower kernel: ata9.00: configured for UDMA/133 Aug 6 15:36:33 Tower kernel: ata9: EH complete Quote Link to comment
trurl Posted August 6, 2022 Share Posted August 6, 2022 [6:0:0:0] disk ATA WDC WD40EFAX-68J 0A83 /dev/sdg /dev/sg6 state=running queue_depth=32 scsi_level=6 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/6:0:0:0 [/sys/devices/pci0000:00/0000:00:17.0/ata6/host6/target6:0:0/6:0:0:0] [9:0:0:0] disk ATA OOS12000G OOS1 /dev/sdj /dev/sg9 state=running queue_depth=32 scsi_level=6 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/9:0:0:0 [/sys/devices/pci0000:00/0000:00:1b.0/0000:01:00.0/ata9/host9/target9:0:0/9:0:0:0] [10:0:0:0] disk ATA WDC WD40EFAX-68J 0A83 /dev/sdk /dev/sg10 state=running queue_depth=32 scsi_level=6 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/10:0:0:0 [/sys/devices/pci0000:00/0000:00:1b.0/0000:01:00.0/ata10/host10/target10:0:0/10:0:0:0] Quote Link to comment
trurl Posted August 6, 2022 Share Posted August 6, 2022 00:17.0 SATA controller [0106]: Intel Corporation 400 Series Chipset Family SATA AHCI Controller [8086:a382] DeviceName: Onboard - SATA Subsystem: ASUSTeK Computer Inc. Device [1043:8694] 01:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9215 PCIe 2.0 x1 4-port SATA 6 Gb/s Controller [1b4b:9215] (rev 11) Subsystem: Marvell Technology Group Ltd. 88SE9215 PCIe 2.0 x1 4-port SATA 6 Gb/s Controller [1b4b:9215] 02:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9215 PCIe 2.0 x1 4-port SATA 6 Gb/s Controller [1b4b:9215] (rev 11) Subsystem: Marvell Technology Group Ltd. 88SE9215 PCIe 2.0 x1 4-port SATA 6 Gb/s Controller [1b4b:9215] Quote Link to comment
StewLoft Posted August 6, 2022 Author Share Posted August 6, 2022 Is it showing anything concerning? Quote Link to comment
trurl Posted August 6, 2022 Share Posted August 6, 2022 I think this all means disk1 is on the Intel controller, and disks 5 and 9 are on the 1st Marvell controller. So maybe their problems are unrelated. And you are still having connection problems on disk9 Quote Link to comment
StewLoft Posted August 6, 2022 Author Share Posted August 6, 2022 Looks ok for now Quote Link to comment
trurl Posted August 6, 2022 Share Posted August 6, 2022 Since all disks are read to emulate disk1, lets leave that one for later. Check filesystem on disk9. Be sure to capture the output so you can post it. Quote Link to comment
StewLoft Posted August 6, 2022 Author Share Posted August 6, 2022 How do I capture the output? Just screen capture? Quote Link to comment
trurl Posted August 6, 2022 Share Posted August 6, 2022 Might not fit in one screenshot. Try copy/paste Quote Link to comment
trurl Posted August 6, 2022 Share Posted August 6, 2022 Are you running this from webUI with -n? Quote Link to comment
trurl Posted August 6, 2022 Share Posted August 6, 2022 I'm surprised there was that much from a mountable disk. Start array in Normal mode (no rebooting) and post new diagnostics. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.