ata4.00 ERROR - How to find this disk?

proxmoxajin · May 5, 2023

Hi,
My PVE host with 10 disks starts , appear follow info:

"
May 05 14:30:46 p1 kernel: ata4.00: exception Emask 0x50 SAct 0x0 SErr 0x40d0802 action 0xe frozen
May 05 14:30:46 p1 kernel: ata4: SError: { RecovComm HostInt PHYRdyChg CommWake 10B8B DevExch }
May 05 14:30:46 p1 kernel: ata4.00: failed command: READ DMA
May 05 14:30:46 p1 kernel: ata4.00: cmd c8/00:08:22:7f:00/00:00:00:00:00/e0 tag 0 dma 4096 in
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x54 (ATA bus error)
May 05 14:30:46 p1 kernel: ata4.00: status: { DRDY }
May 05 14:30:46 p1 kernel: ata4: hard resetting link
May 05 14:30:47 p1 kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 05 14:30:47 p1 kernel: ata4.00: configured for UDMA/133
May 05 14:30:47 p1 kernel: ata4: EH complete
"

I use "lsblk -S" show disks list:
"
sda 0:0:0:0 disk ATA ST500DM002-1SB10 CC63 ZA48YTEG ata
sdb 0:0:1:0 disk ATA ST500DM002-1BD14 HP74 Z6EJ40XE ata
sdc 1:0:0:0 disk ATA ST500DM002-1BD14 KC48 W3THX3PL ata
sdd 1:0:1:0 disk ATA WDC_WD5000AAKX-0 1H15 WD-WMC2E0086167 ata
sde 2:0:0:0 disk ATA WDC_WD5000AAKX-0 1H19 WD-WCC2ECH68094 ata
sdf 3:0:0:0 disk ATA ST500DM002-1BD14 KC45 W2A9CKP7 ata
sdg 4:0:0:0 disk ATA WDC_WD5000AAKX-0 1H19 WD-WCC2ERU68797 sata
sdh 5:0:0:0 disk ATA WDC_WD5000AAKX-0 1H15 WD-WCAYUHX94107 sata
sdi 6:0:0:0 disk ATA WDC_WD5000AAKX-0 1H19 WD-WCC2EHX22047 sata
sdj 7:0:0:0 disk ATA WDC_WD5000AAKX-0 1H15 WD-WCC2E0AZJAAJ sata
sdk 36:0:0:0 disk USB SanDisk_3.2Gen1 1.00 0101b1988c8b1e9421
"

How to find 'ata4.00' corresponding disk in the list ' sda-sdj' ?

Thanks!

Chris · May 5, 2023

proxmoxajin said:
Hi,
My PVE host with 10 disks starts , appear follow info:

"
May 05 14:30:46 p1 kernel: ata4.00: exception Emask 0x50 SAct 0x0 SErr 0x40d0802 action 0xe frozen
May 05 14:30:46 p1 kernel: ata4: SError: { RecovComm HostInt PHYRdyChg CommWake 10B8B DevExch }
May 05 14:30:46 p1 kernel: ata4.00: failed command: READ DMA
May 05 14:30:46 p1 kernel: ata4.00: cmd c8/00:08:22:7f:00/00:00:00:00:00/e0 tag 0 dma 4096 in
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x54 (ATA bus error)
May 05 14:30:46 p1 kernel: ata4.00: status: { DRDY }
May 05 14:30:46 p1 kernel: ata4: hard resetting link
May 05 14:30:47 p1 kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 05 14:30:47 p1 kernel: ata4.00: configured for UDMA/133
May 05 14:30:47 p1 kernel: ata4: EH complete
"

I use "lsblk -S" show disks list:
"
sda 0:0:0:0 disk ATA ST500DM002-1SB10 CC63 ZA48YTEG ata
sdb 0:0:1:0 disk ATA ST500DM002-1BD14 HP74 Z6EJ40XE ata
sdc 1:0:0:0 disk ATA ST500DM002-1BD14 KC48 W3THX3PL ata
sdd 1:0:1:0 disk ATA WDC_WD5000AAKX-0 1H15 WD-WMC2E0086167 ata
sde 2:0:0:0 disk ATA WDC_WD5000AAKX-0 1H19 WD-WCC2ECH68094 ata
sdf 3:0:0:0 disk ATA ST500DM002-1BD14 KC45 W2A9CKP7 ata
sdg 4:0:0:0 disk ATA WDC_WD5000AAKX-0 1H19 WD-WCC2ERU68797 sata
sdh 5:0:0:0 disk ATA WDC_WD5000AAKX-0 1H15 WD-WCAYUHX94107 sata
sdi 6:0:0:0 disk ATA WDC_WD5000AAKX-0 1H19 WD-WCC2EHX22047 sata
sdj 7:0:0:0 disk ATA WDC_WD5000AAKX-0 1H15 WD-WCC2E0AZJAAJ sata
sdk 36:0:0:0 disk USB SanDisk_3.2Gen1 1.00 0101b1988c8b1e9421
"

How to find 'ata4.00' corresponding disk in the list ' sda-sdj' ?

Thanks!

Hi,
you can run ls -la /dev/disk/by-path to see which path symlinks to which device name

proxmoxajin · May 5, 2023

Chris said:
Hi,
you can run ls -la /dev/disk/by-path to see which path symlinks to which device name

Thanks a lot , I get the symlink to the disk.
Have a good day!

proxmoxajin · May 6, 2023

Hi,
After I disconnected the symlinked disk ,there are 9 disks in the host.
But warning message still appears:
The info on screen is below : " Attach file "
And the host syslog is below:


May 06 11:37:11 p1 kernel: ata1: lost interrupt (Status 0x50)
May 06 11:37:11 p1 kernel: ata4: lost interrupt (Status 0x50)
May 06 11:37:11 p1 kernel: ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x40d0002 action 0xe frozen
May 06 11:37:11 p1 kernel: ata4: SError: { RecovComm PHYRdyChg CommWake 10B8B DevExch }
May 06 11:37:11 p1 kernel: ata4.00: failed command: WRITE DMA EXT
May 06 11:37:11 p1 kernel: ata4.00: cmd 35/00:00:00:43:19/00:04:00:00:00/e0 tag 0 dma 524288 out
         res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x14 (ATA bus error)
May 06 11:37:11 p1 kernel: ata4.00: status: { DRDY }
May 06 11:37:11 p1 kernel: ata4: hard resetting link
May 06 11:37:12 p1 kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 06 11:37:12 p1 kernel: ata4.00: configured for UDMA/33
May 06 11:37:12 p1 kernel: ata4: EH complete
May 06 11:37:13 p1 kernel: ata1.00: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
May 06 11:37:13 p1 kernel: ata1.01: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 06 11:37:13 p1 kernel: ata1.00: configured for UDMA/100
May 06 11:37:13 p1 kernel: ata1.01: configured for UDMA/33
May 06 11:37:17 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - got timeout
May 06 11:37:17 p1 pvestatd[1490]: status update time (12.861 seconds)
May 06 11:37:20 p1 pvedaemon[15107]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - got timeout
May 06 11:37:25 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - unable to connect to VM 202 qmp socket - timeout after 51 retries
May 06 11:37:25 p1 pvestatd[1490]: status update time (8.057 seconds)
May 06 11:37:35 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - unable to connect to VM 202 qmp socket - timeout after 51 retries
May 06 11:37:35 p1 pvestatd[1490]: status update time (8.056 seconds)
May 06 11:37:44 p1 kernel: ata1: lost interrupt (Status 0x50)
May 06 11:37:45 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - unable to connect to VM 202 qmp socket - timeout after 51 retries
May 06 11:37:45 p1 pvestatd[1490]: status update time (8.056 seconds)
May 06 11:37:46 p1 kernel: ata1.00: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
May 06 11:37:46 p1 kernel: ata1.01: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 06 11:37:46 p1 kernel: ata1.00: configured for UDMA/100
May 06 11:37:46 p1 kernel: ata1.01: configured for UDMA/33
May 06 11:37:55 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - got timeout
May 06 11:37:56 p1 pvestatd[1490]: status update time (8.047 seconds)
May 06 11:38:03 p1 pvedaemon[15107]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - unable to connect to VM 202 qmp socket - timeout after 51 retries
May 06 11:38:05 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - unable to connect to VM 202 qmp socket - timeout after 51 retries
May 06 11:38:05 p1 pvestatd[1490]: status update time (8.059 seconds)
May 06 11:38:15 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - unable to connect to VM 202 qmp socket - timeout after 51 retries
May 06 11:38:15 p1 pvestatd[1490]: status update time (8.057 seconds)
May 06 11:38:17 p1 kernel: ata1: lost interrupt (Status 0x50)
May 06 11:38:18 p1 kernel: ata1.00: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
May 06 11:38:18 p1 kernel: ata1.01: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 06 11:38:18 p1 kernel: ata1.00: configured for UDMA/100
May 06 11:38:19 p1 kernel: ata1.01: configured for UDMA/33
May 06 11:38:27 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - got timeout
May 06 11:38:27 p1 pvestatd[1490]: status update time (9.952 seconds)
May 06 11:38:29 p1 pvedaemon[15107]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - unable to connect to VM 202 qmp socket - timeout after 51 retries
May 06 11:38:35 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - unable to connect to VM 202 qmp socket - timeout after 51 retries
May 06 11:38:35 p1 pvestatd[1490]: status update time (8.056 seconds)
May 06 11:38:45 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - unable to connect to VM 202 qmp socket - timeout after 51 retries
May 06 11:38:45 p1 pvestatd[1490]: status update time (8.058 seconds)
May 06 11:38:50 p1 kernel: ata1: lost interrupt (Status 0x50)
May 06 11:38:51 p1 kernel: ata1.00: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
May 06 11:38:51 p1 kernel: ata1.01: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 06 11:38:51 p1 kernel: ata1.00: configured for UDMA/100
May 06 11:38:51 p1 kernel: ata1.01: configured for UDMA/33
May 06 11:38:56 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - got timeout
May 06 11:38:56 p1 pvedaemon[15107]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - got timeout
May 06 11:38:56 p1 pvestatd[1490]: status update time (9.654 seconds)
May 06 11:39:05 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - unable to connect to VM 202 qmp socket - timeout after 51 retries
May 06 11:39:05 p1 pvestatd[1490]: status update time (8.060 seconds)
May 06 11:39:15 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - unable to connect to VM 202 qmp socket - timeout after 51 retries
May 06 11:39:15 p1 pvestatd[1490]: status update time (8.056 seconds)
May 06 11:39:22 p1 kernel: ata1: lost interrupt (Status 0x50)
May 06 11:39:22 p1 kernel: ata4: lost interrupt (Status 0x50)
May 06 11:39:22 p1 kernel: ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x40d0002 action 0xe frozen
May 06 11:39:22 p1 kernel: ata4: SError: { RecovComm PHYRdyChg CommWake 10B8B DevExch }
May 06 11:39:22 p1 kernel: ata4.00: failed command: WRITE DMA EXT
May 06 11:39:22 p1 kernel: ata4.00: cmd 35/00:00:00:79:19/00:08:00:00:00/e0 tag 0 dma 1048576 out
         res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x14 (ATA bus error)
May 06 11:39:22 p1 kernel: ata4.00: status: { DRDY }
May 06 11:39:22 p1 kernel: ata4: hard resetting link
May 06 11:39:23 p1 kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 06 11:39:23 p1 kernel: ata4.00: configured for UDMA/33
May 06 11:39:23 p1 kernel: ata4: EH complete
May 06 11:39:24 p1 kernel: ata1.00: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
May 06 11:39:24 p1 kernel: ata1.01: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 06 11:39:24 p1 kernel: ata1.00: configured for UDMA/100
May 06 11:39:24 p1 kernel: ata1.01: configured for UDMA/33
May 06 11:39:29 p1 pvedaemon[15107]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - got timeout
May 06 11:39:29 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - got timeout
May 06 11:39:29 p1 pvestatd[1490]: status update time (11.658 seconds)
May 06 11:39:37 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - unable to connect to VM 202 qmp socket - timeout after 51 retries
May 06 11:39:37 p1 pvestatd[1490]: status update time (8.056 seconds)
May 06 11:39:47 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - unable to connect to VM 202 qmp socket - timeout after 51 retries
May 06 11:39:47 p1 pvestatd[1490]: status update time (8.058 seconds)
May 06 11:39:55 p1 kernel: ata1: lost interrupt (Status 0x50)
May 06 11:39:57 p1 kernel: ata1.00: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
May 06 11:39:57 p1 kernel: ata1.01: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 06 11:39:57 p1 kernel: ata1.00: configured for UDMA/100
May 06 11:39:57 p1 kernel: ata1.01: configured for UDMA/33
May 06 11:40:02 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - got timeout
May 06 11:40:02 p1 pvestatd[1490]: status update time (12.660 seconds)
May 06 11:40:05 p1 pvedaemon[1519]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - unable to connect to VM 202 qmp socket - timeout after 51 retries
May 06 11:40:10 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - unable to connect to VM 202 qmp socket - timeout after 51 retries
May 06 11:40:10 p1 pvestatd[1490]: status update time (8.060 seconds)
May 06 11:40:20 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - unable to connect to VM 202 qmp socket - timeout after 51 retries
May 06 11:40:20 p1 pvestatd[1490]: status update time (8.059 seconds)
May 06 11:40:28 p1 kernel: ata4: lost interrupt (Status 0x50)
May 06 11:40:28 p1 kernel: ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x40d0002 action 0xe frozen
May 06 11:40:28 p1 kernel: ata4: SError: { RecovComm PHYRdyChg CommWake 10B8B DevExch }
May 06 11:40:28 p1 kernel: ata4.00: failed command: WRITE DMA EXT
May 06 11:40:28 p1 kernel: ata4.00: cmd 35/00:00:80:88:19/00:0a:00:00:00/e0 tag 0 dma 1310720 out
         res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x14 (ATA bus error)
May 06 11:40:28 p1 kernel: ata4.00: status: { DRDY }
May 06 11:40:28 p1 kernel: ata4: hard resetting link
May 06 11:40:29 p1 kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 06 11:40:29 p1 kernel: ata4.00: configured for UDMA/33
May 06 11:40:29 p1 kernel: ata4: EH complete
May 06 11:40:34 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - got timeout
May 06 11:40:34 p1 pvestatd[1490]: status update time (11.859 seconds)
May 06 11:40:37 p1 pvedaemon[15107]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - got timeout
May 06 11:40:42 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - unable to connect to VM 202 qmp socket - timeout after 51 retries
May 06 11:40:42 p1 pvestatd[1490]: status update time (8.056 seconds)
May 06 11:40:52 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - unable to connect to VM 202 qmp socket - timeout after 51 retries
May 06 11:40:52 p1 pvestatd[1490]: status update time (8.056 seconds)
May 06 11:41:01 p1 kernel: ata4: lost interrupt (Status 0x50)
May 06 11:41:01 p1 kernel: ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x48d0002 action 0xe frozen
May 06 11:41:01 p1 kernel: ata4: SError: { RecovComm PHYRdyChg CommWake 10B8B LinkSeq DevExch }
May 06 11:41:01 p1 kernel: ata4.00: failed command: WRITE DMA EXT
May 06 11:41:01 p1 kernel: ata4.00: cmd 35/00:00:80:a7:19/00:04:00:00:00/e0 tag 0 dma 524288 out
         res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x14 (ATA bus error)
May 06 11:41:01 p1 kernel: ata4.00: status: { DRDY }
May 06 11:41:01 p1 kernel: ata4: hard resetting link
May 06 11:41:02 p1 kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 06 11:41:02 p1 kernel: ata4.00: configured for UDMA/33
May 06 11:41:02 p1 kernel: ata4: EH complete
May 06 11:41:02 p1 pvestatd[1490]: status update time (7.664 seconds)
May 06 11:41:12 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - unable to connect to VM 202 qmp socket - timeout after 51 retries
May 06 11:41:12 p1 pvestatd[1490]: status update time (8.057 seconds)
May 06 11:41:14 p1 pvedaemon[1519]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - unable to connect to VM 202 qmp socket - timeout after 51 retries
May 06 11:41:22 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - unable to connect to VM 202 qmp socket - timeout after 51 retries
May 06 11:41:22 p1 pvestatd[1490]: status update time (8.057 seconds)
May 06 11:41:32 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - unable to connect to VM 202 qmp socket - timeout after 51 retries
May 06 11:41:32 p1 pvestatd[1490]: status update time (8.058 seconds)
May 06 11:41:33 p1 kernel: ata1: lost interrupt (Status 0x50)
May 06 11:41:35 p1 kernel: ata1.00: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
May 06 11:41:35 p1 kernel: ata1.01: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 06 11:41:35 p1 kernel: ata1.00: configured for UDMA/100
May 06 11:41:35 p1 kernel: ata1.01: configured for UDMA/33
May 06 11:41:35 p1 qm[24747]: <root@pam> starting task UPID:p1:000060AD:000DE9E8:6455CC6F:qmstop:202:root@pam:
May 06 11:41:35 p1 qm[24749]: stop VM 202: UPID:p1:000060AD:000DE9E8:6455CC6F:qmstop:202:root@pam:
May 06 11:41:40 p1 qm[24749]: VM 202 qmp command failed - VM 202 qmp command 'quit' failed - got timeout
May 06 11:41:40 p1 pvedaemon[1519]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - got timeout
May 06 11:41:43 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - unable to connect to VM 202 qmp socket - timeout after 51 retries
May 06 11:41:43 p1 pvestatd[1490]: status update time (9.358 seconds)
May 06 11:41:51 p1 qm[24747]: <root@pam> end task UPID:p1:000060AD:000DE9E8:6455CC6F:qmstop:202:root@pam: OK
May 06 11:41:51 p1 pvestatd[1490]: VM 202 qmp command failed - VM 202 qmp command 'query-proxmox-support' failed - unable to connect to VM 202 qmp socket - No such file or directory
May 06 11:41:51 p1 pvestatd[1490]: status update time (7.157 seconds)
May 06 11:42:06 p1 pvedaemon[1519]: <root@pam> end task UPID:p1:00003805:0007CFCA:6455BCD0:vncproxy:202:root@pam: OK
May 06 11:42:06 p1 kernel: ata4: lost interrupt (Status 0x50)
May 06 11:42:06 p1 kernel: ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x40d0002 action 0xe frozen
May 06 11:42:06 p1 kernel: ata4: SError: { RecovComm PHYRdyChg CommWake 10B8B DevExch }
May 06 11:42:06 p1 kernel: ata4.00: failed command: WRITE DMA EXT
May 06 11:42:06 p1 kernel: ata4.00: cmd 35/00:b0:80:c6:19/00:05:00:00:00/e0 tag 0 dma 745472 out
         res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x14 (ATA bus error)
May 06 11:42:06 p1 kernel: ata4.00: status: { DRDY }
May 06 11:42:06 p1 kernel: ata4: hard resetting link
May 06 11:42:06 p1 pveproxy[14748]: worker exit
May 06 11:42:07 p1 kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 06 11:42:07 p1 kernel: ata4.00: configured for UDMA/33
May 06 11:42:07 p1 kernel: ata4: EH complete
May 06 11:42:07 p1 kernel: fwbr202i0: port 2(tap202i0) entered disabled state
May 06 11:42:07 p1 kernel: fwbr202i0: port 2(tap202i0) entered disabled state
May 06 11:42:07 p1 kernel:  sda: sda1 sda2
May 06 11:42:07 p1 kernel: fwbr202i1: port 2(tap202i1) entered disabled state
May 06 11:42:07 p1 kernel: fwbr202i1: port 2(tap202i1) entered disabled state
May 06 11:42:07 p1 kernel:  sde: sde1 sde2
May 06 11:42:07 p1 systemd[1]: 202.scope: Succeeded.
May 06 11:42:07 p1 systemd[1]: 202.scope: Consumed 7min 42.655s CPU time.
May 06 11:42:07 p1 kernel:  sdd: sdd1 sdd2
May 06 11:42:07 p1 kernel:  sdb: sdb1 sdb2
May 06 11:42:08 p1 kernel:  sdf: sdf1 sdf2

Which one is problem?
Thanks for helping!

leesteken · May 6, 2023

What is the (new) output of ls -l /dev/disk/by-path? Maybe your drive(s) are bad, or the cables are bad or have a bad connection, or the SATA controller broke?

alexskysilk · May 6, 2023

you're drives are VERY old.

just sayin.

proxmoxajin · May 7, 2023

leesteken said:
What is the (new) output of ls -l /dev/disk/by-path? Maybe your drive(s) are bad, or the cables are bad or have a bad connection, or the SATA controller broke?

Hi,
Here it is below:


root@p1:~# ls -la /dev/disk/by-path
total 0
drwxr-xr-x 2 root root 1040 May  8 04:39 .
drwxr-xr-x 7 root root  140 May  8 04:38 ..
lrwxrwxrwx 1 root root    9 May  8 04:39 pci-0000:00:14.0-usb-0:3:1.0-scsi-0:0:0:0 -> ../../sdi
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:00:14.0-usb-0:3:1.0-scsi-0:0:0:0-part1 -> ../../sdi1
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:00:14.0-usb-0:3:1.0-scsi-0:0:0:0-part2 -> ../../sdi2
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:00:14.0-usb-0:3:1.0-scsi-0:0:0:0-part3 -> ../../sdi3
lrwxrwxrwx 1 root root    9 May  8 04:39 pci-0000:00:14.0-usb-0:4:1.0-scsi-0:0:0:0 -> ../../sdj
lrwxrwxrwx 1 root root    9 May  8 04:39 pci-0000:00:1f.2-ata-1 -> ../../sda
lrwxrwxrwx 1 root root    9 May  8 04:39 pci-0000:00:1f.2-ata-1.0 -> ../../sda
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:00:1f.2-ata-1.0-part1 -> ../../sda1
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:00:1f.2-ata-1.0-part2 -> ../../sda2
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:00:1f.2-ata-1-part1 -> ../../sda1
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:00:1f.2-ata-1-part2 -> ../../sda2
lrwxrwxrwx 1 root root    9 May  8 04:39 pci-0000:00:1f.2-ata-2 -> ../../sdb
lrwxrwxrwx 1 root root    9 May  8 04:39 pci-0000:00:1f.2-ata-2.0 -> ../../sdb
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:00:1f.2-ata-2.0-part1 -> ../../sdb1
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:00:1f.2-ata-2.0-part2 -> ../../sdb2
lrwxrwxrwx 1 root root    9 May  8 04:39 pci-0000:00:1f.2-ata-2.1 -> ../../sdc
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:00:1f.2-ata-2.1-part1 -> ../../sdc1
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:00:1f.2-ata-2.1-part2 -> ../../sdc2
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:00:1f.2-ata-2-part1 -> ../../sdc1
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:00:1f.2-ata-2-part2 -> ../../sdb2
lrwxrwxrwx 1 root root    9 May  8 04:39 pci-0000:00:1f.5-ata-1 -> ../../sdd
lrwxrwxrwx 1 root root    9 May  8 04:39 pci-0000:00:1f.5-ata-1.0 -> ../../sdd
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:00:1f.5-ata-1.0-part1 -> ../../sdd1
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:00:1f.5-ata-1.0-part2 -> ../../sdd2
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:00:1f.5-ata-1-part1 -> ../../sdd1
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:00:1f.5-ata-1-part2 -> ../../sdd2
lrwxrwxrwx 1 root root    9 May  8 04:39 pci-0000:00:1f.5-ata-2 -> ../../sde
lrwxrwxrwx 1 root root    9 May  8 04:39 pci-0000:00:1f.5-ata-2.0 -> ../../sde
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:00:1f.5-ata-2.0-part1 -> ../../sde1
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:00:1f.5-ata-2.0-part2 -> ../../sde2
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:00:1f.5-ata-2-part1 -> ../../sde1
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:00:1f.5-ata-2-part2 -> ../../sde2
lrwxrwxrwx 1 root root    9 May  8 04:39 pci-0000:05:00.0-ata-1 -> ../../sdf
lrwxrwxrwx 1 root root    9 May  8 04:39 pci-0000:05:00.0-ata-1.0 -> ../../sdf
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:05:00.0-ata-1.0-part1 -> ../../sdf1
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:05:00.0-ata-1.0-part2 -> ../../sdf2
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:05:00.0-ata-1-part1 -> ../../sdf1
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:05:00.0-ata-1-part2 -> ../../sdf2
lrwxrwxrwx 1 root root    9 May  8 04:39 pci-0000:05:00.0-ata-2 -> ../../sdg
lrwxrwxrwx 1 root root    9 May  8 04:39 pci-0000:05:00.0-ata-2.0 -> ../../sdg
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:05:00.0-ata-2.0-part1 -> ../../sdg1
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:05:00.0-ata-2.0-part2 -> ../../sdg2
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:05:00.0-ata-2-part1 -> ../../sdg1
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:05:00.0-ata-2-part2 -> ../../sdg2
lrwxrwxrwx 1 root root    9 May  8 04:39 pci-0000:05:00.0-ata-3 -> ../../sdh
lrwxrwxrwx 1 root root    9 May  8 04:39 pci-0000:05:00.0-ata-3.0 -> ../../sdh
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:05:00.0-ata-3.0-part1 -> ../../sdh1
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:05:00.0-ata-3.0-part2 -> ../../sdh2
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:05:00.0-ata-3-part1 -> ../../sdh1
lrwxrwxrwx 1 root root   10 May  8 04:39 pci-0000:05:00.0-ata-3-part2 -> ../../sdh2

proxmoxajin · May 7, 2023

proxmoxajin said:
Hi,
Here it is below:

root@p1:~# ls -la /dev/disk/by-path total 0 drwxr-xr-x 2 root root 1040 May 8 04:39 . drwxr-xr-x 7 root root 140 May 8 04:38 .. lrwxrwxrwx 1 root root 9 May 8 04:39 pci-0000:00:14.0-usb-0:3:1.0-scsi-0:0:0:0 -> ../../sdi lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:00:14.0-usb-0:3:1.0-scsi-0:0:0:0-part1 -> ../../sdi1 lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:00:14.0-usb-0:3:1.0-scsi-0:0:0:0-part2 -> ../../sdi2 lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:00:14.0-usb-0:3:1.0-scsi-0:0:0:0-part3 -> ../../sdi3 lrwxrwxrwx 1 root root 9 May 8 04:39 pci-0000:00:14.0-usb-0:4:1.0-scsi-0:0:0:0 -> ../../sdj lrwxrwxrwx 1 root root 9 May 8 04:39 pci-0000:00:1f.2-ata-1 -> ../../sda lrwxrwxrwx 1 root root 9 May 8 04:39 pci-0000:00:1f.2-ata-1.0 -> ../../sda lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:00:1f.2-ata-1.0-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:00:1f.2-ata-1.0-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:00:1f.2-ata-1-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:00:1f.2-ata-1-part2 -> ../../sda2 lrwxrwxrwx 1 root root 9 May 8 04:39 pci-0000:00:1f.2-ata-2 -> ../../sdb lrwxrwxrwx 1 root root 9 May 8 04:39 pci-0000:00:1f.2-ata-2.0 -> ../../sdb lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:00:1f.2-ata-2.0-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:00:1f.2-ata-2.0-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 9 May 8 04:39 pci-0000:00:1f.2-ata-2.1 -> ../../sdc lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:00:1f.2-ata-2.1-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:00:1f.2-ata-2.1-part2 -> ../../sdc2 lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:00:1f.2-ata-2-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:00:1f.2-ata-2-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 9 May 8 04:39 pci-0000:00:1f.5-ata-1 -> ../../sdd lrwxrwxrwx 1 root root 9 May 8 04:39 pci-0000:00:1f.5-ata-1.0 -> ../../sdd lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:00:1f.5-ata-1.0-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:00:1f.5-ata-1.0-part2 -> ../../sdd2 lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:00:1f.5-ata-1-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:00:1f.5-ata-1-part2 -> ../../sdd2 lrwxrwxrwx 1 root root 9 May 8 04:39 pci-0000:00:1f.5-ata-2 -> ../../sde lrwxrwxrwx 1 root root 9 May 8 04:39 pci-0000:00:1f.5-ata-2.0 -> ../../sde lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:00:1f.5-ata-2.0-part1 -> ../../sde1 lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:00:1f.5-ata-2.0-part2 -> ../../sde2 lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:00:1f.5-ata-2-part1 -> ../../sde1 lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:00:1f.5-ata-2-part2 -> ../../sde2 lrwxrwxrwx 1 root root 9 May 8 04:39 pci-0000:05:00.0-ata-1 -> ../../sdf lrwxrwxrwx 1 root root 9 May 8 04:39 pci-0000:05:00.0-ata-1.0 -> ../../sdf lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:05:00.0-ata-1.0-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:05:00.0-ata-1.0-part2 -> ../../sdf2 lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:05:00.0-ata-1-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:05:00.0-ata-1-part2 -> ../../sdf2 lrwxrwxrwx 1 root root 9 May 8 04:39 pci-0000:05:00.0-ata-2 -> ../../sdg lrwxrwxrwx 1 root root 9 May 8 04:39 pci-0000:05:00.0-ata-2.0 -> ../../sdg lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:05:00.0-ata-2.0-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:05:00.0-ata-2.0-part2 -> ../../sdg2 lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:05:00.0-ata-2-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:05:00.0-ata-2-part2 -> ../../sdg2 lrwxrwxrwx 1 root root 9 May 8 04:39 pci-0000:05:00.0-ata-3 -> ../../sdh lrwxrwxrwx 1 root root 9 May 8 04:39 pci-0000:05:00.0-ata-3.0 -> ../../sdh lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:05:00.0-ata-3.0-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:05:00.0-ata-3.0-part2 -> ../../sdh2 lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:05:00.0-ata-3-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 10 May 8 04:39 pci-0000:05:00.0-ata-3-part2 -> ../../sdh2

And this :


root@p1:~# lsblk -S
NAME HCTL       TYPE VENDOR   MODEL                   REV SERIAL                                                                                                                   TRAN
sda  0:0:0:0    disk ATA      ST500DM002-1SB10A      CC63 ZA48YTEG                                                                                                                 ata
sdb  1:0:0:0    disk ATA      ST500DM002-1BD142      KC48 W3THX3PL                                                                                                                 ata
sdc  1:0:1:0    disk ATA      WDC_WD5000AAKX-00ERMA0 1H15 WD-WMC2E0086167                                                                                                          ata
sdd  2:0:0:0    disk ATA      WDC_WD5000AAKX-08ERMA0 1H19 WD-WCC2ECH68094                                                                                                          ata
sde  3:0:0:0    disk ATA      ST500DM002-1BD142      KC45 W2A9CKP7                                                                                                                 ata
sdf  4:0:0:0    disk ATA      WDC_WD5000AAKX-08U6AA0 1H19 WD-WCC2ERU68797                                                                                                          sata
sdg  5:0:0:0    disk ATA      WDC_WD5000AAKX-003CA0  1H15 WD-WCAYUHX94107                                                                                                          sata
sdh  6:0:0:0    disk ATA      WDC_WD5000AAKX-08ERMA0 1H19 WD-WCC2EHX22047                                                                                                          sata
sdi  36:0:0:0   disk  USB     SanDisk_3.2Gen1        1.00 0101b1988c8b1e9421f99effb79e84c970d53733b4f9c1dadc284fd6705e64ef0f2700000000000000000000b83078c1ff0a730091558107cd2cf52a usb
sdj  37:0:0:0   disk  USB     SanDisk_3.2Gen1        1.00 0901459c519cebe2ee9ce798cea2d433c3b81f6c2abf6c73dca4bb09ee751def4f4c000000000000000000001ef7daceff033120675581075d2d3b09 usb

proxmoxajin · May 7, 2023

alexskysilk said:
you're drives are VERY old.

just sayin.

Hi，
This is my homelab. I just have a few 500G capacity disks in my hand, and I plan to do NAS or PVE hyper-converged testing and learning. If the disk can work normally, it will be more satisfactory.

proxmoxajin · May 7, 2023

leesteken said:
What is the (new) output of ls -l /dev/disk/by-path? Maybe your drive(s) are bad, or the cables are bad or have a bad connection, or the SATA controller broke?

Hi,
The new output on screen is below,
Would you please find the specific cause of the failure?
thanks！

Chris · May 8, 2023

As already stated by others, these errors indicate communication failure between your host and the drives. So this is most likely hardware related and you should check, powersupply, sata cables, check your disk using smartctl.

alexskysilk · May 8, 2023

proxmoxajin said:
If the disk can work normally, it will be more satisfactory.

I think you already have your answer

proxmoxajin · May 9, 2023

Chris said:
As already stated by others, these errors indicate communication failure between your host and the drives. So this is most likely hardware related and you should check, powersupply, sata cables, check your disk using smartctl.

Thanks, I'm dealing with a problem with a disk failure.

proxmoxajin · May 9, 2023

alexskysilk said:
I think you already have your answer

Thanks for your attention.

Search

Search

ata4.00 ERROR - How to find this disk?

proxmoxajin

Active Member

Chris

Proxmox Staff Member

proxmoxajin

Active Member

proxmoxajin

Active Member

Attachments

leesteken

Distinguished Member

alexskysilk

Distinguished Member

proxmoxajin

Active Member

proxmoxajin

Active Member

proxmoxajin

Active Member

proxmoxajin

Active Member

Chris

Proxmox Staff Member

alexskysilk

Distinguished Member

proxmoxajin

Active Member

proxmoxajin

Active Member