MarianKoniuszko Posted November 11, 2023 Share Posted November 11, 2023 Hello, Yesterday I upgrade some docker apps (Homeassistant, Unassigned Devices) and don't click DONE. I shutdown laptop. Then there was some errors when Appdata Backup plugin works. I reboot becuse today morning I noticed that dockers don't show at all. I reboot and see one of my drives don't monut: `Unmountable: Unsupported or no filesystem`. I check drive in maintance mode and get some alerts: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... block (0,141243410-141243425) multiply claimed by bno space tree, state - 1 block (0,141243442-141243469) multiply claimed by bno space tree, state - 1 block (0,141243474-141243477) multiply claimed by bno space tree, state - 1 block (0,141243482-141243485) multiply claimed by bno space tree, state - 1 block (0,141243490-141243497) multiply claimed by bno space tree, state - 1 block (0,141243502-141243517) multiply claimed by bno space tree, state - 1 block (0,141243522-141243533) multiply claimed by bno space tree, state - 1 block (0,141243554-141243561) multiply claimed by bno space tree, state - 1 block (0,141243570-141243573) multiply claimed by bno space tree, state - 1 block (0,141243586-141243589) multiply claimed by bno space tree, state - 1 block (0,141243598-141243601) multiply claimed by bno space tree, state - 1 block (0,141243618-141243621) multiply claimed by bno space tree, state - 1 block (0,141243646-141243649) multiply claimed by bno space tree, state - 1 block (0,141243654-141243669) multiply claimed by bno space tree, state - 1 block (0,141243814-141243821) multiply claimed by bno space tree, state - 1 block (0,141243838-141243841) multiply claimed by bno space tree, state - 1 block (0,141243850-141243857) multiply claimed by bno space tree, state - 1 block (0,141243954-141243957) multiply claimed by bno space tree, state - 1 block (0,141243978-141244009) multiply claimed by bno space tree, state - 1 block (0,141244022-141244025) multiply claimed by bno space tree, state - 1 block (0,141244058-141244109) multiply claimed by bno space tree, state - 1 block (0,141244146-141244149) multiply claimed by bno space tree, state - 1 block (0,141244182-141244201) multiply claimed by bno space tree, state - 1 block (0,141244398-141244401) multiply claimed by bno space tree, state - 1 block (0,141244406-141244417) multiply claimed by bno space tree, state - 1 block (0,141244630-141244661) multiply claimed by bno space tree, state - 1 block (0,141244666-141244669) multiply claimed by bno space tree, state - 1 block (0,141244674-141244709) multiply claimed by bno space tree, state - 1 block (0,141244714-141244733) multiply claimed by bno space tree, state - 1 block (0,141244754-141244757) multiply claimed by bno space tree, state - 1 block (0,141244766-141244769) multiply claimed by bno space tree, state - 1 block (0,141244790-141244797) multiply claimed by bno space tree, state - 1 block (0,141244834-141244841) multiply claimed by bno space tree, state - 1 block (0,141244858-141244861) multiply claimed by bno space tree, state - 1 block (0,141244874-141244877) multiply claimed by bno space tree, state - 1 block (0,141244926-141244929) multiply claimed by bno space tree, state - 1 block (0,141244934-141244965) multiply claimed by bno space tree, state - 1 block (0,141244970-141244981) multiply claimed by bno space tree, state - 1 block (0,141244986-141244997) multiply claimed by bno space tree, state - 1 block (0,141245018-141245029) multiply claimed by bno space tree, state - 1 block (0,141245126-141245141) multiply claimed by bno space tree, state - 1 block (0,141245146-141245153) multiply claimed by bno space tree, state - 1 block (0,141245174-141245189) multiply claimed by bno space tree, state - 1 block (0,141245194-141245209) multiply claimed by bno space tree, state - 1 block (0,141245234-141245253) multiply claimed by bno space tree, state - 1 block (0,141245442-141245457) multiply claimed by bno space tree, state - 1 block (0,148650552-148655054) multiply claimed by bno space tree, state - 1 block (0,149724468-149724515) multiply claimed by cnt space tree, state - 2 block (0,157330949-157333507) multiply claimed by cnt space tree, state - 2 block (0,151505166-151507489) multiply claimed by cnt space tree, state - 2 block (0,156512789-156515215) multiply claimed by cnt space tree, state - 2 block (0,156478020-156481222) multiply claimed by cnt space tree, state - 2 agf_freeblks 30860681, counted 30883623 in ag 0 sb_ifree 122873, counted 122867 sb_fdblocks 576021232, counted 538688917 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 bad btree key (is 669151, should be 669054) in inode 436364925 data fork, btree block 54549144 bad btree key (is 683621, should be 675713) in inode 436364925 data fork, btree block 54549144 bad fwd (right) sibling pointer (saw 54549151 parent block says 141988604) in inode 436364925 (data fork) bmap btree block 54549150 bad data fork in inode 436364925 would have cleared inode 436364925 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... free space (0,53072796-53072796) only seen by one free space btree free space (0,149724316-149724467) only seen by one free space btree free space (0,151502028-151505165) only seen by one free space btree free space (0,156474988-156478019) only seen by one free space btree free space (0,156509401-156512788) only seen by one free space btree free space (0,157328278-157330948) only seen by one free space btree - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 6 - agno = 2 - agno = 4 - agno = 5 - agno = 7 - agno = 1 entry "docker.img" in shortform directory 436364923 references free inode 436364925 would have junked entry "docker.img" in directory inode 436364923 bad btree key (is 669151, should be 669054) in inode 436364925 data fork, btree block 54549144 bad btree key (is 683621, should be 675713) in inode 436364925 data fork, btree block 54549144 bad fwd (right) sibling pointer (saw 54549151 parent block says 141988604) in inode 436364925 (data fork) bmap btree block 54549150 would have cleared inode 436364925 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... entry "docker.img" in shortform directory inode 436364923 points to free inode 436364925 would junk entry - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... Maximum metadata LSN (9:2584326) is ahead of log (9:2575678). Would format log to cycle 12. No modify flag set, skipping filesystem flush and exiting. In check filesystem status I see: xfs_repair status: Not available. text error warn system array login Nov 11 10:08:47 unRAID kernel: ata5: SATA max UDMA/133 abar m2048@0x85302000 port 0x85302300 irq 146 Nov 11 10:08:47 unRAID kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 11 10:08:47 unRAID kernel: ata5.00: ATA-11: ST8000VX004-2M1101, AV01, max UDMA/133 Nov 11 10:08:47 unRAID kernel: ata5.00: 15628053168 sectors, multi 16: LBA48 NCQ (depth 32), AA Nov 11 10:08:47 unRAID kernel: ata5.00: Features: NCQ-sndrcv Nov 11 10:08:47 unRAID kernel: ata5.00: configured for UDMA/133 Nov 11 10:08:47 unRAID kernel: sd 6:0:0:0: [sdc] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB) Nov 11 10:08:47 unRAID kernel: sd 6:0:0:0: [sdc] 4096-byte physical blocks Nov 11 10:08:47 unRAID kernel: sd 6:0:0:0: [sdc] Write Protect is off Nov 11 10:08:47 unRAID kernel: sd 6:0:0:0: [sdc] Mode Sense: 00 3a 00 00 Nov 11 10:08:47 unRAID kernel: sd 6:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Nov 11 10:08:47 unRAID kernel: sd 6:0:0:0: [sdc] Preferred minimum I/O size 4096 bytes Nov 11 10:08:47 unRAID kernel: sdc: sdc1 Nov 11 10:08:47 unRAID kernel: sd 6:0:0:0: [sdc] Attached SCSI disk Nov 11 10:09:17 unRAID emhttpd: ST8000VX004-2M1101_WSD7QSSD (sdc) 512 15628053168 Nov 11 10:09:17 unRAID kernel: mdcmd (4): import 3 sdc 64 7814026532 0 ST8000VX004-2M1101_WSD7QSSD Nov 11 10:09:17 unRAID kernel: md: import disk3: (sdc) ST8000VX004-2M1101_WSD7QSSD size: 7814026532 Nov 11 10:09:17 unRAID emhttpd: read SMART /dev/sdc Nov 11 10:40:38 unRAID kernel: ata5.00: exception Emask 0x10 SAct 0x7f000 SErr 0x4890000 action 0xe frozen Nov 11 10:40:38 unRAID kernel: ata5.00: irq_stat 0x04400040, connection status changed Nov 11 10:40:38 unRAID kernel: ata5: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Nov 11 10:40:38 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:40:38 unRAID kernel: ata5.00: cmd 60/80:60:c0:07:bd/00:00:01:00:00/40 tag 12 ncq dma 65536 in Nov 11 10:40:38 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:40:38 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:40:38 unRAID kernel: ata5.00: cmd 60/40:68:40:08:bd/05:00:01:00:00/40 tag 13 ncq dma 688128 in Nov 11 10:40:38 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:40:38 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:40:38 unRAID kernel: ata5.00: cmd 60/40:70:80:0d:bd/05:00:01:00:00/40 tag 14 ncq dma 688128 in Nov 11 10:40:38 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:40:38 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:40:38 unRAID kernel: ata5.00: cmd 60/40:78:c0:12:bd/05:00:01:00:00/40 tag 15 ncq dma 688128 in Nov 11 10:40:38 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:40:38 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:40:38 unRAID kernel: ata5.00: cmd 60/40:80:00:18:bd/05:00:01:00:00/40 tag 16 ncq dma 688128 in Nov 11 10:40:38 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:40:38 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:40:38 unRAID kernel: ata5.00: cmd 60/40:88:40:1d:bd/05:00:01:00:00/40 tag 17 ncq dma 688128 in Nov 11 10:40:38 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:40:38 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:40:38 unRAID kernel: ata5.00: cmd 60/40:90:80:22:bd/05:00:01:00:00/40 tag 18 ncq dma 688128 in Nov 11 10:40:38 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:40:38 unRAID kernel: ata5: hard resetting link Nov 11 10:40:44 unRAID kernel: ata5: link is slow to respond, please be patient (ready=0) Nov 11 10:40:48 unRAID kernel: ata5: COMRESET failed (errno=-16) Nov 11 10:40:48 unRAID kernel: ata5: hard resetting link Nov 11 10:40:50 unRAID kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 11 10:40:50 unRAID kernel: ata5.00: configured for UDMA/133 Nov 11 10:40:50 unRAID kernel: ata5: EH complete Nov 11 10:41:12 unRAID kernel: ata5.00: exception Emask 0x10 SAct 0x1fc0 SErr 0x4890000 action 0xe frozen Nov 11 10:41:12 unRAID kernel: ata5.00: irq_stat 0x04400040, connection status changed Nov 11 10:41:12 unRAID kernel: ata5: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Nov 11 10:41:12 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:41:12 unRAID kernel: ata5.00: cmd 60/40:30:80:4d:3f/05:00:02:00:00/40 tag 6 ncq dma 688128 in Nov 11 10:41:12 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:41:12 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:41:12 unRAID kernel: ata5.00: cmd 60/40:38:c0:52:3f/05:00:02:00:00/40 tag 7 ncq dma 688128 in Nov 11 10:41:12 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:41:12 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:41:12 unRAID kernel: ata5.00: cmd 60/40:40:00:58:3f/05:00:02:00:00/40 tag 8 ncq dma 688128 in Nov 11 10:41:12 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:41:12 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:41:12 unRAID kernel: ata5.00: cmd 60/40:48:40:5d:3f/05:00:02:00:00/40 tag 9 ncq dma 688128 in Nov 11 10:41:12 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:41:12 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:41:12 unRAID kernel: ata5.00: cmd 60/40:50:80:62:3f/05:00:02:00:00/40 tag 10 ncq dma 688128 in Nov 11 10:41:12 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:41:12 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:41:12 unRAID kernel: ata5.00: cmd 60/40:58:c0:67:3f/05:00:02:00:00/40 tag 11 ncq dma 688128 in Nov 11 10:41:12 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:41:12 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:41:12 unRAID kernel: ata5.00: cmd 60/80:60:00:6d:3f/00:00:02:00:00/40 tag 12 ncq dma 65536 in Nov 11 10:41:12 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:41:12 unRAID kernel: ata5: hard resetting link Nov 11 10:41:17 unRAID kernel: ata5: link is slow to respond, please be patient (ready=0) Nov 11 10:41:22 unRAID kernel: ata5: COMRESET failed (errno=-16) Nov 11 10:41:22 unRAID kernel: ata5: hard resetting link Nov 11 10:41:24 unRAID kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 11 10:41:24 unRAID kernel: ata5.00: configured for UDMA/133 Nov 11 10:41:24 unRAID kernel: ata5: EH complete Nov 11 10:41:24 unRAID kernel: ata5.00: exception Emask 0x10 SAct 0x1e0e0 SErr 0x4090000 action 0xe frozen Nov 11 10:41:24 unRAID kernel: ata5.00: irq_stat 0x00400040, connection status changed Nov 11 10:41:24 unRAID kernel: ata5: SError: { PHYRdyChg 10B8B DevExch } Nov 11 10:41:24 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:41:24 unRAID kernel: ata5.00: cmd 60/80:28:00:6d:3f/00:00:02:00:00/40 tag 5 ncq dma 65536 in Nov 11 10:41:24 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:41:24 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:41:24 unRAID kernel: ata5.00: cmd 60/40:30:c0:67:3f/05:00:02:00:00/40 tag 6 ncq dma 688128 in Nov 11 10:41:24 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:41:24 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:41:24 unRAID kernel: ata5.00: cmd 60/40:38:80:62:3f/05:00:02:00:00/40 tag 7 ncq dma 688128 in Nov 11 10:41:24 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:41:24 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:41:24 unRAID kernel: ata5.00: cmd 60/40:68:40:5d:3f/05:00:02:00:00/40 tag 13 ncq dma 688128 in Nov 11 10:41:24 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:41:24 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:41:24 unRAID kernel: ata5.00: cmd 60/40:70:00:58:3f/05:00:02:00:00/40 tag 14 ncq dma 688128 in Nov 11 10:41:24 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:41:24 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:41:24 unRAID kernel: ata5.00: cmd 60/40:78:c0:52:3f/05:00:02:00:00/40 tag 15 ncq dma 688128 in Nov 11 10:41:24 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:41:24 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:41:24 unRAID kernel: ata5.00: cmd 60/40:80:80:4d:3f/05:00:02:00:00/40 tag 16 ncq dma 688128 in Nov 11 10:41:24 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:41:24 unRAID kernel: ata5: hard resetting link Nov 11 10:41:30 unRAID kernel: ata5: link is slow to respond, please be patient (ready=0) Nov 11 10:41:34 unRAID kernel: ata5: COMRESET failed (errno=-16) Nov 11 10:41:34 unRAID kernel: ata5: hard resetting link Nov 11 10:41:36 unRAID kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 11 10:41:36 unRAID kernel: ata5.00: configured for UDMA/133 Nov 11 10:41:36 unRAID kernel: ata5: EH complete Nov 11 10:44:37 unRAID kernel: ata5: limiting SATA link speed to 3.0 Gbps Nov 11 10:44:37 unRAID kernel: ata5.00: exception Emask 0x10 SAct 0x4000003f SErr 0x4090000 action 0xe frozen Nov 11 10:44:37 unRAID kernel: ata5.00: irq_stat 0x00400040, connection status changed Nov 11 10:44:37 unRAID kernel: ata5: SError: { PHYRdyChg 10B8B DevExch } Nov 11 10:44:37 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:44:37 unRAID kernel: ata5.00: cmd 60/40:00:c0:11:6c/05:00:06:00:00/40 tag 0 ncq dma 688128 in Nov 11 10:44:37 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:44:37 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:44:37 unRAID kernel: ata5.00: cmd 60/40:08:00:17:6c/05:00:06:00:00/40 tag 1 ncq dma 688128 in Nov 11 10:44:37 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:44:37 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:44:37 unRAID kernel: ata5.00: cmd 60/40:10:40:1c:6c/05:00:06:00:00/40 tag 2 ncq dma 688128 in Nov 11 10:44:37 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:44:37 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:44:37 unRAID kernel: ata5.00: cmd 60/80:18:80:21:6c/00:00:06:00:00/40 tag 3 ncq dma 65536 in Nov 11 10:44:37 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:44:37 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:44:37 unRAID kernel: ata5.00: cmd 60/40:20:00:22:6c/05:00:06:00:00/40 tag 4 ncq dma 688128 in Nov 11 10:44:37 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:44:37 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:44:37 unRAID kernel: ata5.00: cmd 60/40:28:40:27:6c/05:00:06:00:00/40 tag 5 ncq dma 688128 in Nov 11 10:44:37 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:44:37 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:44:37 unRAID kernel: ata5.00: cmd 60/40:f0:80:0c:6c/05:00:06:00:00/40 tag 30 ncq dma 688128 in Nov 11 10:44:37 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:44:37 unRAID kernel: ata5: hard resetting link Nov 11 10:44:43 unRAID kernel: ata5: link is slow to respond, please be patient (ready=0) Nov 11 10:44:47 unRAID kernel: ata5: COMRESET failed (errno=-16) Nov 11 10:44:47 unRAID kernel: ata5: hard resetting link Nov 11 10:44:49 unRAID kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Nov 11 10:44:49 unRAID kernel: ata5.00: configured for UDMA/133 Nov 11 10:44:49 unRAID kernel: ata5: EH complete Nov 11 10:47:45 unRAID kernel: ata5.00: exception Emask 0x10 SAct 0x3f8000 SErr 0x4890000 action 0xe frozen Nov 11 10:47:45 unRAID kernel: ata5.00: irq_stat 0x04400040, connection status changed Nov 11 10:47:45 unRAID kernel: ata5: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Nov 11 10:47:45 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:47:45 unRAID kernel: ata5.00: cmd 60/40:78:80:0b:7f/05:00:0a:00:00/40 tag 15 ncq dma 688128 in Nov 11 10:47:45 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:47:45 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:47:45 unRAID kernel: ata5.00: cmd 60/40:80:c0:10:7f/05:00:0a:00:00/40 tag 16 ncq dma 688128 in Nov 11 10:47:45 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:47:45 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:47:45 unRAID kernel: ata5.00: cmd 60/40:88:00:16:7f/05:00:0a:00:00/40 tag 17 ncq dma 688128 in Nov 11 10:47:45 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:47:45 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:47:45 unRAID kernel: ata5.00: cmd 60/40:90:40:1b:7f/05:00:0a:00:00/40 tag 18 ncq dma 688128 in Nov 11 10:47:45 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:47:45 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:47:45 unRAID kernel: ata5.00: cmd 60/80:98:80:20:7f/00:00:0a:00:00/40 tag 19 ncq dma 65536 in Nov 11 10:47:45 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:47:45 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:47:45 unRAID kernel: ata5.00: cmd 60/40:a0:00:21:7f/05:00:0a:00:00/40 tag 20 ncq dma 688128 in Nov 11 10:47:45 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:47:45 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:47:45 unRAID kernel: ata5.00: cmd 60/40:a8:40:26:7f/05:00:0a:00:00/40 tag 21 ncq dma 688128 in Nov 11 10:47:45 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:47:45 unRAID kernel: ata5: hard resetting link Nov 11 10:47:51 unRAID kernel: ata5: link is slow to respond, please be patient (ready=0) Nov 11 10:47:55 unRAID kernel: ata5: COMRESET failed (errno=-16) Nov 11 10:47:55 unRAID kernel: ata5: hard resetting link Nov 11 10:47:57 unRAID kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Nov 11 10:47:57 unRAID kernel: ata5.00: configured for UDMA/133 Nov 11 10:47:57 unRAID kernel: ata5: EH complete Nov 11 10:51:12 unRAID kernel: ata5.00: exception Emask 0x10 SAct 0xfe0 SErr 0x4890000 action 0xe frozen Nov 11 10:51:12 unRAID kernel: ata5.00: irq_stat 0x0d400040, interface fatal error, connection status changed Nov 11 10:51:12 unRAID kernel: ata5: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Nov 11 10:51:12 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:51:12 unRAID kernel: ata5.00: cmd 60/40:28:40:7c:f4/05:00:0e:00:00/40 tag 5 ncq dma 688128 in Nov 11 10:51:12 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:51:12 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:51:12 unRAID kernel: ata5.00: cmd 60/40:30:80:81:f4/05:00:0e:00:00/40 tag 6 ncq dma 688128 in Nov 11 10:51:12 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:51:12 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:51:12 unRAID kernel: ata5.00: cmd 60/40:38:c0:86:f4/05:00:0e:00:00/40 tag 7 ncq dma 688128 in Nov 11 10:51:12 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:51:12 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:51:12 unRAID kernel: ata5.00: cmd 60/40:40:00:8c:f4/05:00:0e:00:00/40 tag 8 ncq dma 688128 in Nov 11 10:51:12 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:51:12 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:51:12 unRAID kernel: ata5.00: cmd 60/40:48:40:91:f4/05:00:0e:00:00/40 tag 9 ncq dma 688128 in Nov 11 10:51:12 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:51:12 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:51:12 unRAID kernel: ata5.00: cmd 60/40:50:80:96:f4/05:00:0e:00:00/40 tag 10 ncq dma 688128 in Nov 11 10:51:12 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:51:12 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:51:12 unRAID kernel: ata5.00: cmd 60/80:58:c0:9b:f4/00:00:0e:00:00/40 tag 11 ncq dma 65536 in Nov 11 10:51:12 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:51:12 unRAID kernel: ata5: hard resetting link Nov 11 10:51:18 unRAID kernel: ata5: link is slow to respond, please be patient (ready=0) Nov 11 10:51:22 unRAID kernel: ata5: COMRESET failed (errno=-16) Nov 11 10:51:22 unRAID kernel: ata5: hard resetting link Nov 11 10:51:24 unRAID kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Nov 11 10:51:24 unRAID kernel: ata5.00: configured for UDMA/133 Nov 11 10:51:24 unRAID kernel: ata5: EH complete Nov 11 10:51:48 unRAID kernel: ata5.00: exception Emask 0x10 SAct 0xfe SErr 0x4890000 action 0xe frozen Nov 11 10:51:48 unRAID kernel: ata5.00: irq_stat 0x04400040, connection status changed Nov 11 10:51:48 unRAID kernel: ata5: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Nov 11 10:51:48 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:51:48 unRAID kernel: ata5.00: cmd 60/40:08:c0:7c:7b/05:00:0f:00:00/40 tag 1 ncq dma 688128 in Nov 11 10:51:48 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:51:48 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:51:48 unRAID kernel: ata5.00: cmd 60/40:10:00:82:7b/05:00:0f:00:00/40 tag 2 ncq dma 688128 in Nov 11 10:51:48 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:51:48 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:51:48 unRAID kernel: ata5.00: cmd 60/40:18:40:87:7b/05:00:0f:00:00/40 tag 3 ncq dma 688128 in Nov 11 10:51:48 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:51:48 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:51:48 unRAID kernel: ata5.00: cmd 60/40:20:80:8c:7b/05:00:0f:00:00/40 tag 4 ncq dma 688128 in Nov 11 10:51:48 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:51:48 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:51:48 unRAID kernel: ata5.00: cmd 60/40:28:c0:91:7b/05:00:0f:00:00/40 tag 5 ncq dma 688128 in Nov 11 10:51:48 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:51:48 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:51:48 unRAID kernel: ata5.00: cmd 60/40:30:00:97:7b/05:00:0f:00:00/40 tag 6 ncq dma 688128 in Nov 11 10:51:48 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:51:48 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:51:48 unRAID kernel: ata5.00: cmd 60/80:38:40:9c:7b/00:00:0f:00:00/40 tag 7 ncq dma 65536 in Nov 11 10:51:48 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:51:48 unRAID kernel: ata5: hard resetting link Nov 11 10:51:54 unRAID kernel: ata5: link is slow to respond, please be patient (ready=0) Nov 11 10:51:58 unRAID kernel: ata5: COMRESET failed (errno=-16) Nov 11 10:51:58 unRAID kernel: ata5: hard resetting link Nov 11 10:52:00 unRAID kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Nov 11 10:52:00 unRAID kernel: ata5.00: configured for UDMA/133 Nov 11 10:52:00 unRAID kernel: ata5: EH complete Nov 11 10:52:27 unRAID kernel: ata5: limiting SATA link speed to 1.5 Gbps Nov 11 10:52:27 unRAID kernel: ata5.00: exception Emask 0x10 SAct 0x1ee00000 SErr 0x4890000 action 0xe frozen Nov 11 10:52:27 unRAID kernel: ata5.00: irq_stat 0x04400040, connection status changed Nov 11 10:52:27 unRAID kernel: ata5: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Nov 11 10:52:27 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:52:27 unRAID kernel: ata5.00: cmd 60/40:a8:80:57:13/05:00:10:00:00/40 tag 21 ncq dma 688128 in Nov 11 10:52:27 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:52:27 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:52:27 unRAID kernel: ata5.00: cmd 60/40:b0:c0:5c:13/05:00:10:00:00/40 tag 22 ncq dma 688128 in Nov 11 10:52:27 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:52:27 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:52:27 unRAID kernel: ata5.00: cmd 60/40:b8:00:62:13/05:00:10:00:00/40 tag 23 ncq dma 688128 in Nov 11 10:52:27 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:52:27 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:52:27 unRAID kernel: ata5.00: cmd 60/40:c8:40:67:13/05:00:10:00:00/40 tag 25 ncq dma 688128 in Nov 11 10:52:27 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:52:27 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:52:27 unRAID kernel: ata5.00: cmd 60/80:d0:80:6c:13/00:00:10:00:00/40 tag 26 ncq dma 65536 in Nov 11 10:52:27 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:52:27 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:52:27 unRAID kernel: ata5.00: cmd 60/40:d8:00:6d:13/05:00:10:00:00/40 tag 27 ncq dma 688128 in Nov 11 10:52:27 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:52:27 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:52:27 unRAID kernel: ata5.00: cmd 60/40:e0:40:72:13/05:00:10:00:00/40 tag 28 ncq dma 688128 in Nov 11 10:52:27 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:52:27 unRAID kernel: ata5: hard resetting link Nov 11 10:52:33 unRAID kernel: ata5: link is slow to respond, please be patient (ready=0) Nov 11 10:52:38 unRAID kernel: ata5: COMRESET failed (errno=-16) Nov 11 10:52:38 unRAID kernel: ata5: hard resetting link Nov 11 10:52:40 unRAID kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Nov 11 10:52:40 unRAID kernel: ata5.00: configured for UDMA/133 Nov 11 10:52:40 unRAID kernel: ata5: EH complete Nov 11 10:54:56 unRAID kernel: ata5.00: exception Emask 0x10 SAct 0xfe0000 SErr 0x4890000 action 0xe frozen Nov 11 10:54:56 unRAID kernel: ata5.00: irq_stat 0x0d400040, interface fatal error, connection status changed Nov 11 10:54:56 unRAID kernel: ata5: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Nov 11 10:54:56 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:54:56 unRAID kernel: ata5.00: cmd 60/40:88:c0:9c:4d/05:00:12:00:00/40 tag 17 ncq dma 688128 in Nov 11 10:54:56 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:54:56 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:54:56 unRAID kernel: ata5.00: cmd 60/40:90:00:a2:4d/05:00:12:00:00/40 tag 18 ncq dma 688128 in Nov 11 10:54:56 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:54:56 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:54:56 unRAID kernel: ata5.00: cmd 60/40:98:40:a7:4d/05:00:12:00:00/40 tag 19 ncq dma 688128 in Nov 11 10:54:56 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:54:56 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:54:56 unRAID kernel: ata5.00: cmd 60/40:a0:80:ac:4d/05:00:12:00:00/40 tag 20 ncq dma 688128 in Nov 11 10:54:56 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:54:56 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:54:56 unRAID kernel: ata5.00: cmd 60/40:a8:c0:b1:4d/05:00:12:00:00/40 tag 21 ncq dma 688128 in Nov 11 10:54:56 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:54:56 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:54:56 unRAID kernel: ata5.00: cmd 60/80:b0:00:b7:4d/00:00:12:00:00/40 tag 22 ncq dma 65536 in Nov 11 10:54:56 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:54:56 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 10:54:56 unRAID kernel: ata5.00: cmd 60/40:b8:80:b7:4d/05:00:12:00:00/40 tag 23 ncq dma 688128 in Nov 11 10:54:56 unRAID kernel: ata5.00: status: { DRDY } Nov 11 10:54:56 unRAID kernel: ata5: hard resetting link Nov 11 10:55:02 unRAID kernel: ata5: link is slow to respond, please be patient (ready=0) Nov 11 10:55:06 unRAID kernel: ata5: COMRESET failed (errno=-16) Nov 11 10:55:06 unRAID kernel: ata5: hard resetting link Nov 11 10:55:08 unRAID kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Nov 11 10:55:08 unRAID kernel: ata5.00: configured for UDMA/133 Nov 11 10:55:08 unRAID kernel: ata5: EH complete Nov 11 11:01:59 unRAID kernel: ata5.00: exception Emask 0x10 SAct 0x7f0000 SErr 0x4890000 action 0xe frozen Nov 11 11:01:59 unRAID kernel: ata5.00: irq_stat 0x0d400040, interface fatal error, connection status changed Nov 11 11:01:59 unRAID kernel: ata5: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Nov 11 11:01:59 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:01:59 unRAID kernel: ata5.00: cmd 60/40:80:40:5b:02/05:00:19:00:00/40 tag 16 ncq dma 688128 in Nov 11 11:01:59 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:01:59 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:01:59 unRAID kernel: ata5.00: cmd 60/40:88:80:60:02/05:00:19:00:00/40 tag 17 ncq dma 688128 in Nov 11 11:01:59 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:01:59 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:01:59 unRAID kernel: ata5.00: cmd 60/40:90:c0:65:02/05:00:19:00:00/40 tag 18 ncq dma 688128 in Nov 11 11:01:59 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:01:59 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:01:59 unRAID kernel: ata5.00: cmd 60/40:98:00:6b:02/05:00:19:00:00/40 tag 19 ncq dma 688128 in Nov 11 11:01:59 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:01:59 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:01:59 unRAID kernel: ata5.00: cmd 60/40:a0:40:70:02/05:00:19:00:00/40 tag 20 ncq dma 688128 in Nov 11 11:01:59 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:01:59 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:01:59 unRAID kernel: ata5.00: cmd 60/80:a8:80:75:02/00:00:19:00:00/40 tag 21 ncq dma 65536 in Nov 11 11:01:59 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:01:59 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:01:59 unRAID kernel: ata5.00: cmd 60/40:b0:00:76:02/05:00:19:00:00/40 tag 22 ncq dma 688128 in Nov 11 11:01:59 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:01:59 unRAID kernel: ata5: hard resetting link Nov 11 11:02:04 unRAID kernel: ata5: link is slow to respond, please be patient (ready=0) Nov 11 11:02:09 unRAID kernel: ata5: COMRESET failed (errno=-16) Nov 11 11:02:09 unRAID kernel: ata5: hard resetting link Nov 11 11:02:11 unRAID kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Nov 11 11:02:11 unRAID kernel: ata5.00: configured for UDMA/133 Nov 11 11:02:11 unRAID kernel: ata5: EH complete Nov 11 11:06:08 unRAID kernel: ata5.00: exception Emask 0x10 SAct 0x3f80 SErr 0x4890000 action 0xe frozen Nov 11 11:06:08 unRAID kernel: ata5.00: irq_stat 0x0d400040, interface fatal error, connection status changed Nov 11 11:06:08 unRAID kernel: ata5: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Nov 11 11:06:08 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:06:08 unRAID kernel: ata5.00: cmd 60/40:38:80:df:e1/05:00:1c:00:00/40 tag 7 ncq dma 688128 in Nov 11 11:06:08 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:06:08 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:06:08 unRAID kernel: ata5.00: cmd 60/40:40:c0:e4:e1/05:00:1c:00:00/40 tag 8 ncq dma 688128 in Nov 11 11:06:08 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:06:08 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:06:08 unRAID kernel: ata5.00: cmd 60/80:48:00:ea:e1/00:00:1c:00:00/40 tag 9 ncq dma 65536 in Nov 11 11:06:08 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:06:08 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:06:08 unRAID kernel: ata5.00: cmd 60/40:50:80:ea:e1/05:00:1c:00:00/40 tag 10 ncq dma 688128 in Nov 11 11:06:08 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:06:08 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:06:08 unRAID kernel: ata5.00: cmd 60/40:58:c0:ef:e1/05:00:1c:00:00/40 tag 11 ncq dma 688128 in Nov 11 11:06:08 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:06:08 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:06:08 unRAID kernel: ata5.00: cmd 60/40:60:00:f5:e1/05:00:1c:00:00/40 tag 12 ncq dma 688128 in Nov 11 11:06:08 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:06:08 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:06:08 unRAID kernel: ata5.00: cmd 60/40:68:40:fa:e1/05:00:1c:00:00/40 tag 13 ncq dma 688128 in Nov 11 11:06:08 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:06:08 unRAID kernel: ata5: hard resetting link Nov 11 11:06:14 unRAID kernel: ata5: link is slow to respond, please be patient (ready=0) Nov 11 11:06:18 unRAID kernel: ata5: COMRESET failed (errno=-16) Nov 11 11:06:18 unRAID kernel: ata5: hard resetting link Nov 11 11:06:20 unRAID kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Nov 11 11:06:20 unRAID kernel: ata5.00: configured for UDMA/133 Nov 11 11:06:20 unRAID kernel: ata5: EH complete Nov 11 11:13:31 unRAID kernel: ata5.00: exception Emask 0x10 SAct 0xfe0000 SErr 0x4890000 action 0xe frozen Nov 11 11:13:31 unRAID kernel: ata5.00: irq_stat 0x0d400040, interface fatal error, connection status changed Nov 11 11:13:31 unRAID kernel: ata5: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Nov 11 11:13:31 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:13:31 unRAID kernel: ata5.00: cmd 60/40:88:c0:6d:eb/05:00:23:00:00/40 tag 17 ncq dma 688128 in Nov 11 11:13:31 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:13:31 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:13:31 unRAID kernel: ata5.00: cmd 60/80:90:00:73:eb/00:00:23:00:00/40 tag 18 ncq dma 65536 in Nov 11 11:13:31 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:13:31 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:13:31 unRAID kernel: ata5.00: cmd 60/40:98:80:73:eb/05:00:23:00:00/40 tag 19 ncq dma 688128 in Nov 11 11:13:31 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:13:31 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:13:31 unRAID kernel: ata5.00: cmd 60/40:a0:c0:78:eb/05:00:23:00:00/40 tag 20 ncq dma 688128 in Nov 11 11:13:31 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:13:31 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:13:31 unRAID kernel: ata5.00: cmd 60/40:a8:00:7e:eb/05:00:23:00:00/40 tag 21 ncq dma 688128 in Nov 11 11:13:31 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:13:31 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:13:31 unRAID kernel: ata5.00: cmd 60/40:b0:40:83:eb/05:00:23:00:00/40 tag 22 ncq dma 688128 in Nov 11 11:13:31 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:13:31 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:13:31 unRAID kernel: ata5.00: cmd 60/40:b8:80:88:eb/05:00:23:00:00/40 tag 23 ncq dma 688128 in Nov 11 11:13:31 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:13:31 unRAID kernel: ata5: hard resetting link Nov 11 11:13:37 unRAID kernel: ata5: link is slow to respond, please be patient (ready=0) Nov 11 11:13:41 unRAID kernel: ata5: COMRESET failed (errno=-16) Nov 11 11:13:41 unRAID kernel: ata5: hard resetting link Nov 11 11:13:43 unRAID kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Nov 11 11:13:43 unRAID kernel: ata5.00: configured for UDMA/133 Nov 11 11:13:43 unRAID kernel: ata5: EH complete Nov 11 11:37:22 unRAID kernel: ata5.00: exception Emask 0x10 SAct 0x1fc00 SErr 0x4890000 action 0xe frozen Nov 11 11:37:22 unRAID kernel: ata5.00: irq_stat 0x04400040, connection status changed Nov 11 11:37:22 unRAID kernel: ata5: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Nov 11 11:37:22 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:37:22 unRAID kernel: ata5.00: cmd 60/80:50:c0:47:1b/00:00:3b:00:00/40 tag 10 ncq dma 65536 in Nov 11 11:37:22 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:37:22 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:37:22 unRAID kernel: ata5.00: cmd 60/40:58:40:48:1b/05:00:3b:00:00/40 tag 11 ncq dma 688128 in Nov 11 11:37:22 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:37:22 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:37:22 unRAID kernel: ata5.00: cmd 60/40:60:80:4d:1b/05:00:3b:00:00/40 tag 12 ncq dma 688128 in Nov 11 11:37:22 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:37:22 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:37:22 unRAID kernel: ata5.00: cmd 60/40:68:c0:52:1b/05:00:3b:00:00/40 tag 13 ncq dma 688128 in Nov 11 11:37:22 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:37:22 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:37:22 unRAID kernel: ata5.00: cmd 60/40:70:00:58:1b/05:00:3b:00:00/40 tag 14 ncq dma 688128 in Nov 11 11:37:22 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:37:22 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:37:22 unRAID kernel: ata5.00: cmd 60/40:78:40:5d:1b/05:00:3b:00:00/40 tag 15 ncq dma 688128 in Nov 11 11:37:22 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:37:22 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:37:22 unRAID kernel: ata5.00: cmd 60/40:80:80:62:1b/05:00:3b:00:00/40 tag 16 ncq dma 688128 in Nov 11 11:37:22 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:37:22 unRAID kernel: ata5: hard resetting link Nov 11 11:37:28 unRAID kernel: ata5: link is slow to respond, please be patient (ready=0) Nov 11 11:37:32 unRAID kernel: ata5: COMRESET failed (errno=-16) Nov 11 11:37:32 unRAID kernel: ata5: hard resetting link Nov 11 11:37:34 unRAID kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Nov 11 11:37:34 unRAID kernel: ata5.00: configured for UDMA/133 Nov 11 11:37:34 unRAID kernel: ata5: EH complete Nov 11 11:37:46 unRAID kernel: ata5.00: exception Emask 0x10 SAct 0xfe0000 SErr 0x4890000 action 0xe frozen Nov 11 11:37:46 unRAID kernel: ata5.00: irq_stat 0x0d400040, interface fatal error, connection status changed Nov 11 11:37:46 unRAID kernel: ata5: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Nov 11 11:37:46 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:37:46 unRAID kernel: ata5.00: cmd 60/40:88:c0:52:49/05:00:3b:00:00/40 tag 17 ncq dma 688128 in Nov 11 11:37:46 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:37:46 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:37:46 unRAID kernel: ata5.00: cmd 60/40:90:00:58:49/05:00:3b:00:00/40 tag 18 ncq dma 688128 in Nov 11 11:37:46 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:37:46 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:37:46 unRAID kernel: ata5.00: cmd 60/40:98:40:5d:49/05:00:3b:00:00/40 tag 19 ncq dma 688128 in Nov 11 11:37:46 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:37:46 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:37:46 unRAID kernel: ata5.00: cmd 60/40:a0:80:62:49/05:00:3b:00:00/40 tag 20 ncq dma 688128 in Nov 11 11:37:46 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:37:46 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:37:46 unRAID kernel: ata5.00: cmd 60/40:a8:c0:67:49/05:00:3b:00:00/40 tag 21 ncq dma 688128 in Nov 11 11:37:46 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:37:46 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:37:46 unRAID kernel: ata5.00: cmd 60/80:b0:00:6d:49/00:00:3b:00:00/40 tag 22 ncq dma 65536 in Nov 11 11:37:46 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:37:46 unRAID kernel: ata5.00: failed command: READ FPDMA QUEUED Nov 11 11:37:46 unRAID kernel: ata5.00: cmd 60/40:b8:80:6d:49/05:00:3b:00:00/40 tag 23 ncq dma 688128 in Nov 11 11:37:46 unRAID kernel: ata5.00: status: { DRDY } Nov 11 11:37:46 unRAID kernel: ata5: hard resetting link Nov 11 11:37:52 unRAID kernel: ata5: link is slow to respond, please be patient (ready=0) Nov 11 11:37:56 unRAID kernel: ata5: COMRESET failed (errno=-16) Nov 11 11:37:56 unRAID kernel: ata5: hard resetting link Nov 11 11:37:58 unRAID kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Nov 11 11:37:58 unRAID kernel: ata5.00: configured for UDMA/133 Nov 11 11:37:58 unRAID kernel: ata5: EH complete Nov 11 11:42:12 unRAID emhttpd: read SMART /dev/sdc Nov 11 11:43:23 unRAID emhttpd: ST8000VX004-2M1101_WSD7QSSD (sdc) 512 15628053168 Nov 11 11:43:23 unRAID kernel: mdcmd (4): import 3 sdc 64 7814026532 0 ST8000VX004-2M1101_WSD7QSSD Nov 11 11:43:23 unRAID kernel: md: import disk3: (sdc) ST8000VX004-2M1101_WSD7QSSD size: 7814026532 Nov 11 11:43:23 unRAID emhttpd: read SMART /dev/sdc unraid-diagnostics-20231111-1153.zip Quote Link to comment
JorgeB Posted November 11, 2023 Share Posted November 11, 2023 Replace cables for disk3 and post new diags after array start. Quote Link to comment
MarianKoniuszko Posted November 11, 2023 Author Share Posted November 11, 2023 15 minutes ago, JorgeB said: Replace cables for disk3 and post new diags after array start. Hi, I will try but now I find command on other thread: `xfs_repair -v /dev/sdc` ``` xfs_repair -v /dev/sdc Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .................................................................................................................................................................................................................. ``` Regards Quote Link to comment
itimpi Posted November 11, 2023 Share Posted November 11, 2023 That is the wrong device name. Is there any reason you are not doing it via the GUI by clicking on the drive and then using the check/repair from there? That way you automatically get the correct device name. Quote Link to comment
MarianKoniuszko Posted November 11, 2023 Author Share Posted November 11, 2023 3 minutes ago, itimpi said: That is the wrong device name. Is there any reason you are not doing it via the GUI by clicking on the drive and then using the check/repair from there? That way you automatically get the correct device name. Hi, I check that Disk3 log and that was /dev/sdc. When I check that drive in maintaince mode I have xfs repair status not available. Quote Link to comment
itimpi Posted November 11, 2023 Share Posted November 11, 2023 6 minutes ago, MarianKoniuszko said: Hi, I check that Disk3 log and that was /dev/sdc. When I check that drive in maintaince mode I have xfs repair status not available. The device name always includes the partition number, and the exact name can vary according to the Unraid release and whether you are using encryption or not. I suspect that the format is set to 'auto' which is why no option is offered via the GUI. Explicitly setting the format to be XFS would give you the option. If you want to to do it via the CLI then the correct device name would be /dev/md3p1 which maintains parity since you appear to be using Unraid 6.12.4 without encryption. Going via /dev/sdc1 would invalidate parity. Quote Link to comment
MarianKoniuszko Posted November 11, 2023 Author Share Posted November 11, 2023 I format that drive to xfs at start. Quote Link to comment
MarianKoniuszko Posted November 11, 2023 Author Share Posted November 11, 2023 12 minutes ago, itimpi said: The device name always includes the partition number, and the exact name can vary according to the Unraid release and whether you are using encryption or not. I suspect that the format is set to 'auto' which is why no option is offered via the GUI. Explicitly setting the format to be XFS would give you the option. If you want to to do it via the CLI then the correct device name would be /dev/md3p1 which maintains parity since you appear to be using Unraid 6.12.4 without encryption. Going via /dev/sdc1 would invalidate parity. So what should I do now? Abort that repair command? Quote Link to comment
Solution JorgeB Posted November 11, 2023 Solution Share Posted November 11, 2023 You should fix the ATA errors first, they are most likely a power/connection problem, then check filesystem from the GUI, without -n. Quote Link to comment
MarianKoniuszko Posted November 11, 2023 Author Share Posted November 11, 2023 3 minutes ago, JorgeB said: You should fix the ATA errors first, they are most likely a power/connection problem, then check filesystem from the GUI, without -n. OK, I will do that but repairing still on. Should I abort it or wait till end? Quote Link to comment
itimpi Posted November 11, 2023 Share Posted November 11, 2023 2 hours ago, MarianKoniuszko said: OK, I will do that but repairing still on. Should I abort it or wait till end? The repair is looking for a superblock which it will never find since you used the wrong device name so you should abandon it. Quote Link to comment
MarianKoniuszko Posted November 11, 2023 Author Share Posted November 11, 2023 20 minutes ago, itimpi said: The repair is looking for a superblock which it will never find since you used the wrong device name so you should abandon it. How to do that? Ctrl+C in terminal window or Stop Array? Quote Link to comment
MarianKoniuszko Posted November 11, 2023 Author Share Posted November 11, 2023 @JorgeB do You think it's because that adapter? Quote Link to comment
MarianKoniuszko Posted November 11, 2023 Author Share Posted November 11, 2023 Hello @itimpi and @JorgeB I change SATA cable for brand new and that power adapter to new one. Still have the same error. When I check without -n Disk in Maintance mode I get ERROR to use -L option. Now it check: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata block (0,141243410-141243425) multiply claimed by bno space tree, state - 1 block (0,141243442-141243469) multiply claimed by bno space tree, state - 1 block (0,141243474-141243477) multiply claimed by bno space tree, state - 1 block (0,141243482-141243485) multiply claimed by bno space tree, state - 1 block (0,141243490-141243497) multiply claimed by bno space tree, state - 1 block (0,141243502-141243517) multiply claimed by bno space tree, state - 1 block (0,141243522-141243533) multiply claimed by bno space tree, state - 1 block (0,141243554-141243561) multiply claimed by bno space tree, state - 1 block (0,141243570-141243573) multiply claimed by bno space tree, state - 1 block (0,141243586-141243589) multiply claimed by bno space tree, state - 1 block (0,141243598-141243601) multiply claimed by bno space tree, state - 1 block (0,141243618-141243621) multiply claimed by bno space tree, state - 1 block (0,141243646-141243649) multiply claimed by bno space tree, state - 1 block (0,141243654-141243669) multiply claimed by bno space tree, state - 1 block (0,141243814-141243821) multiply claimed by bno space tree, state - 1 block (0,141243838-141243841) multiply claimed by bno space tree, state - 1 block (0,141243850-141243857) multiply claimed by bno space tree, state - 1 block (0,141243954-141243957) multiply claimed by bno space tree, state - 1 block (0,141243978-141244009) multiply claimed by bno space tree, state - 1 block (0,141244022-141244025) multiply claimed by bno space tree, state - 1 block (0,141244058-141244109) multiply claimed by bno space tree, state - 1 block (0,141244146-141244149) multiply claimed by bno space tree, state - 1 block (0,141244182-141244201) multiply claimed by bno space tree, state - 1 block (0,141244398-141244401) multiply claimed by bno space tree, state - 1 block (0,141244406-141244417) multiply claimed by bno space tree, state - 1 block (0,141244630-141244661) multiply claimed by bno space tree, state - 1 block (0,141244666-141244669) multiply claimed by bno space tree, state - 1 block (0,141244674-141244709) multiply claimed by bno space tree, state - 1 block (0,141244714-141244733) multiply claimed by bno space tree, state - 1 block (0,141244754-141244757) multiply claimed by bno space tree, state - 1 block (0,141244766-141244769) multiply claimed by bno space tree, state - 1 block (0,141244790-141244797) multiply claimed by bno space tree, state - 1 block (0,141244834-141244841) multiply claimed by bno space tree, state - 1 block (0,141244858-141244861) multiply claimed by bno space tree, state - 1 block (0,141244874-141244877) multiply claimed by bno space tree, state - 1 block (0,141244926-141244929) multiply claimed by bno space tree, state - 1 block (0,141244934-141244965) multiply claimed by bno space tree, state - 1 block (0,141244970-141244981) multiply claimed by bno space tree, state - 1 block (0,141244986-141244997) multiply claimed by bno space tree, state - 1 block (0,141245018-141245029) multiply claimed by bno space tree, state - 1 block (0,141245126-141245141) multiply claimed by bno space tree, state - 1 block (0,141245146-141245153) multiply claimed by bno space tree, state - 1 block (0,141245174-141245189) multiply claimed by bno space tree, state - 1 block (0,141245194-141245209) multiply claimed by bno space tree, state - 1 block (0,141245234-141245253) multiply claimed by bno space tree, state - 1 block (0,141245442-141245457) multiply claimed by bno space tree, state - 1 block (0,148650552-148655054) multiply claimed by bno space tree, state - 1 block (0,149724468-149724515) multiply claimed by cnt space tree, state - 2 block (0,157330949-157333507) multiply claimed by cnt space tree, state - 2 block (0,151505166-151507489) multiply claimed by cnt space tree, state - 2 block (0,156512789-156515215) multiply claimed by cnt space tree, state - 2 block (0,156478020-156481222) multiply claimed by cnt space tree, state - 2 agf_freeblks 30860681, counted 30883623 in ag 0 sb_ifree 122873, counted 122867 sb_fdblocks 576021232, counted 538688917 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 correcting bt key (was 669151, now 669054) in inode 436364925 data fork, btree block 54549144 correcting bt key (was 683621, now 675713) in inode 436364925 data fork, btree block 54549144 bad fwd (right) sibling pointer (saw 54549151 parent block says 141988604) in inode 436364925 (data fork) bmap btree block 54549150 bad data fork in inode 436364925 cleared inode 436364925 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 2 - agno = 4 - agno = 5 - agno = 1 - agno = 6 - agno = 7 entry "docker.img" in shortform directory 436364923 references free inode 436364925 junking entry "docker.img" in directory inode 436364923 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (9:2584326) is ahead of log (1:2). Format log to cycle 12. done What should I do now? Regards. Quote Link to comment
MarianKoniuszko Posted November 11, 2023 Author Share Posted November 11, 2023 After I make Clean Reboot all Drives are mounnted. Do I have to try repair that drive or start to install my containers again because they are gone? Quote Link to comment
MarianKoniuszko Posted November 11, 2023 Author Share Posted November 11, 2023 Also every plugin is uninstalled? What to do now? Quote Link to comment
itimpi Posted November 11, 2023 Share Posted November 11, 2023 You now need to check if you have a lost+found folder as that is where the repair process puts any files of folders for which it could not find the directory entry to give them the correct name and gives them cryptic names. Unfortunately if you do have lost+found then sorting it out is a manual process although the Linux file command can at least give you the content type for any file. In practice if you have reasonable backups it is easier to restore from them. Quote Link to comment
MarianKoniuszko Posted November 11, 2023 Author Share Posted November 11, 2023 11 minutes ago, itimpi said: You now need to check if you have a lost+found folder as that is where the repair process puts any files of folders for which it could not find the directory entry to give them the correct name and gives them cryptic names. Unfortunately if you do have lost+found then sorting it out is a manual process although the Linux file command can at least give you the content type for any file. In practice if you have reasonable backups it is easier to restore from them. I reinstall all apps and plugins from Previous Apps tab and everything works OK. Can You tell me where I have to look that lost+found? I cannot find it anywhere. Regards. Quote Link to comment
itimpi Posted November 11, 2023 Share Posted November 11, 2023 1 minute ago, MarianKoniuszko said: Can You tell me where I have to look that lost+found? I cannot find it anywhere. You do not always have one if the repair process has had no issues. If you have one it will be on the drive that you repaired. It also then normally shows up as a User Share as well because it is a top level folder. Quote Link to comment
MarianKoniuszko Posted November 11, 2023 Author Share Posted November 11, 2023 Just now, itimpi said: You do not always have one if the repair process has had no issues. If you have one it will be on the drive that you repaired. It also then normally shows up as a User Share as well because it is a top level folder. OK, so I don't have one and everything looks fine now. Thank You very much for help. Quote Link to comment
MarianKoniuszko Posted November 11, 2023 Author Share Posted November 11, 2023 Hello @JorgeB and @itimpi. One more thing. I see now I run array in Safe Mode. Everything works fine. I install all apps and plugins and I'm afraid something will broke if I reboot? Quote Link to comment
JorgeB Posted November 12, 2023 Share Posted November 12, 2023 You need to try, if it doesn't work correctly in normal mode it's likely a plugin issue. Quote Link to comment
MarianKoniuszko Posted November 12, 2023 Author Share Posted November 12, 2023 Thank You. Everything works fine. Regards. 1 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.