August 1, 20232 yr attached the diagnostic file As soon as the monthly parity check started I get errors like these (until I stop the parity check) I have a hard time figuring out which disk is attached to ata2 (i see ata3 sometime as well), may be a bad cable (first to swap) or maybe the disk. Checked SMART self tests (short) and no worries there. help is much appreciated! thanks ps. it may be the SCSI number as shown in the screenshot? not sure Quote 2023-07-31 00:00:38.010 Jul 31 00:00:38 Tower kernel: res 40/00:00:78:d4:08/00:00:00:00:00/40 Emask 0x50 (ATA bus error) 2023-07-31 00:00:38.010 Jul 31 00:00:38 Tower kernel: ata2.00: cmd 60/40:08:78:d4:08/05:00:00:00:00/40 tag 1 ncq dma 688128 in 2023-07-31 00:00:38.010 Jul 31 00:00:38 Tower kernel: ata2.00: failed command: READ FPDMA QUEUED 2023-07-31 00:00:38.010 Jul 31 00:00:38 Tower kernel: ata2: SError: { HostInt PHYRdyChg 10B8B DevExch } 2023-07-31 00:00:38.010 Jul 31 00:00:38 Tower kernel: ata2.00: irq_stat 0x00400040, connection status changed 2023-07-31 00:00:38.010 Jul 31 00:00:38 Tower kernel: ata2.00: exception Emask 0x50 SAct 0x6 SErr 0x4090800 action 0xe frozen 2023-07-31 00:00:36.256 Jul 31 00:00:36 Tower kernel: ata3.00: configured for UDMA/133 2023-07-31 00:00:36.256 Jul 31 00:00:36 Tower kernel: ata2: EH complete 2023-07-31 00:00:36.256 Jul 31 00:00:36 Tower kernel: ata2.00: configured for UDMA/133 2023-07-31 00:00:36.256 Jul 31 00:00:36 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) 2023-07-31 00:00:36.006 Jul 31 00:00:35 Tower kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) 2023-07-31 00:00:35.254 Jul 31 00:00:35 Tower kernel: ata3: COMRESET failed (errno=-16) 2023-07-31 00:00:35.254 Jul 31 00:00:35 Tower kernel: ata2: hard resetting link 2023-07-31 00:00:35.254 Jul 31 00:00:35 Tower kernel: ata2: COMRESET failed (errno=-16) 2023-07-31 00:00:30.982 Jul 31 00:00:30 Tower kernel: ata3: link is slow to respond, please be patient (ready=0) 2023-07-31 00:00:30.982 Jul 31 00:00:30 Tower kernel: ata2: link is slow to respond, please be patient (ready=0) 2023-07-31 00:00:25.219 Jul 31 00:00:25 Tower kernel: ata2: hard resetting link 2023-07-31 00:00:25.219 Jul 31 00:00:25 Tower kernel: ata2.00: status: { DRDY } 2023-07-31 00:00:25.219 Jul 31 00:00:25 Tower kernel: res 40/00:00:40:e0:02/00:00:00:00:00/40 Emask 0x50 (ATA bus error) 2023-07-31 00:00:25.219 Jul 31 00:00:25 Tower kernel: ata2.00: cmd 60/78:88:40:e0:02/04:00:00:00:00/40 tag 17 ncq dma 585728 in 2023-07-31 00:00:25.219 Jul 31 00:00:25 Tower kernel: ata2.00: failed command: READ FPDMA QUEUED 2023-07-31 00:00:25.219 Jul 31 00:00:25 Tower kernel: ata2: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch } 2023-07-31 00:00:25.219 Jul 31 00:00:25 Tower kernel: ata2.00: irq_stat 0x0c400040, interface fatal error, connection status changed 2023-07-31 00:00:25.219 Jul 31 00:00:25 Tower kernel: ata2.00: exception Emask 0x50 SAct 0x20000 SErr 0x4890800 action 0xe frozen 2023-07-31 00:00:02.420 Jul 31 00:00:02 Tower emhttpd: read SMART /dev/sdc 2023-07-31 00:00:02.420 Jul 31 00:00:02 Tower emhttpd: read SMART /dev/sdf 2023-07-31 00:00:02.420 Jul 31 00:00:02 Tower emhttpd: read SMART /dev/sde 2023-07-31 00:00:02.420 Jul 31 00:00:02 Tower emhttpd: read SMART /dev/sdd 2023-07-31 00:00:02.420 Jul 31 00:00:02 Tower emhttpd: read SMART /dev/sdg 2023-07-31 00:00:01.927 Jul 31 00:00:01 Tower kernel: md: recovery thread: check P ... 2023-07-31 00:00:01.919 Jul 31 00:00:01 Tower kernel: mdcmd (36): check 2023-07-30 22:22:54.610 Jul 30 22:22:54 Tower emhttpd: spinning down /dev/sdd 2023-07-30 21:02:46.896 Jul 30 21:02:46 Tower emhttpd: spinning down /dev/sdg 2023-07-30 20:52:30.876 Jul 30 20:52:30 Tower emhttpd: spinning down /dev/sde 2023-07-30 20:47:45.894 Jul 30 20:47:45 Tower emhttpd: read SMART /dev/sdg 2023-07-30 20:27:02.163 Jul 30 20:27:02 Tower emhttpd: read SMART /dev/sde tower-diagnostics-20230801-1936.zip
August 1, 20232 yr Community Expert Jul 28 02:09:52 Tower kernel: ata3: link is slow to respond, please be patient (ready=0) Jul 28 02:09:52 Tower kernel: ata2: link is slow to respond, please be patient (ready=0) Jul 28 02:09:56 Tower kernel: ata2: COMRESET failed (errno=-16) Jul 28 02:09:56 Tower kernel: ata3: COMRESET failed (errno=-16) Jul 28 02:09:57 Tower kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 28 02:09:57 Tower kernel: ata2.00: configured for UDMA/133 Jul 28 02:09:57 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 28 02:09:58 Tower kernel: ata3.00: configured for UDMA/133 It's not just during a parity check, this is usually a power/connection problem, check/replace cables, ATA2 and ATA3 are parity and disk3
August 1, 20232 yr Author Thanks really appreciated! How did you know thats parity and disk3? I will replace those cables and run the parity check again, if it fails I may need to check the power supply as suggested in other topics, would you agree?
August 2, 20232 yr Community Expert You can check lsscsi.txt in the diags: [2:0:0:0] disk ATA WDC WD80EFZX-68U 0A83 /dev/sdc /dev/sg2 state=running queue_depth=32 scsi_level=6 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/2:0:0:0 [/sys/devices/pci0000:00/0000:00:1f.2/ata2/host2/target2:0:0/2:0:0:0] [3:0:0:0] disk ATA WDC WD80EFAX-68K 0A81 /dev/sdd /dev/sg3 state=running queue_depth=32 scsi_level=6 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/3:0:0:0 [/sys/devices/pci0000:00/0000:00:1f.2/ata3/host3/target3:0:0/3:0:0:0] 13 hours ago, RBB87 said: would you agree? Worth a try.
August 7, 20232 yr Author thanks for sticking with me. i can consider the tower being lost from a hardware perspective. I took the disks out to check the data in another unraid system (nuc), Unassigned Devices says it can only format the disk instead of mounting. xfs_repair does not work as there are no partitions found (at least on 2 disks, havent checked the others yet), I do see /dev/sdb, biut no way to mount it? Any tips?
August 7, 20232 yr Community Expert Assuming you used USB to connect them it may not mount because of that.
August 7, 20232 yr Author Yes USB indeed, so what do i need to do to read the data from outside of the unraid env where the system crashed? I thought USB was they way to go
August 7, 20232 yr Community Expert Some USB bridges are not transparent, try using a SATA port in another PC if available, if not try a different USB bridge.
August 7, 20232 yr Author e.g. https://www.megekko.nl/product/6202/1031641/USB-SATA-HDD-SSD-docking-station/ACT-AC1500-2-5-3-5-SATA-harde-schijf-docking-station-USB-3-2-Gen1 or similar? I now have a usb Samsung g3 chip i pulled out of an old usb enclosure.. that may be the issue?
August 7, 20232 yr Author SATA bay worked fine at a friend's house, tomorrow getting a new one myself. So should be good! Keep you posted
August 17, 20232 yr Author @JorgeBI'm now trying to get data from the disk mounted via usb to a unraid nuc. some dirs list as follows /bin/ls: reading directory '/mnt/disks/WDC_WD40_EFRX-68WT0N0/media/movies-hd': Input/output error i tried xfs_repair. but no luck afterwards. Now what? any help is really appreciated! Edited August 17, 20232 yr by RBB87
August 17, 20232 yr Author I will check another usb Sata reader, can that cause the issues? Another 8TB disk copied everything open just fine..
August 17, 20232 yr Community Expert Aug 17 16:32:32 Nuc kernel: XFS (sdb1): metadata I/O error in "xfs_da_read_buf+0x9a/0xff [xfs]" at daddr 0x7a604038 len 8 error 5 Possibly a filesystem problem, try checking filesystem with UD, it would also be good to see a SMART report, but there are no disk errors logged.
August 17, 20232 yr Author ow wait i see it now, i can not do that for a usb disk? Edited August 17, 20232 yr by RBB87
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.