Communication failure when accessing disks on Proxmox node

lgjunior

New Member
May 23, 2024
1
0
1
Good afternoon, when attempting to access the disks on my Proxmox node, an error message appears stating "communication failure (0) or Connection timed out (596)". The goal was to view all the disks of the server in order to link them to the server itself. Despite encountering this error when trying to access the disks through the Proxmox interface, running the "lsblk" command from the shell successfully lists the available disks.

Upon checking the system logs, a potentially related error message is found:

Jun 03 15:41:02 proxmox-nas kernel: sd 8:0:0:0: [sdf] tag#6 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=2s
Jun 03 15:41:02 proxmox-nas kernel: sd 8:0:0:0: [sdf] tag#6 Sense Key: Medium Error [current]
Jun 03 15:41:02 proxmox-nas kernel: sd 8:0:0:0: [sdf] tag#6 Add. Sense: Unrecovered read error - auto reallocate failed
Jun 03 15:41:02 proxmox-nas kernel: sd 8:0:0:0: [sdf] tag#6 CDB: Read(16) 88 00 00 00 00 00 00 00 08 00 00 00 01 00 00 00
Jun 03 15:41:02 proxmox-nas kernel: I/O error, dev sdf, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
Jun 03 15:41:02 proxmox-nas kernel: ata9: EH complete

Is the issue with the sdf device causing the timeout error?
 
Possibly? Run a SMART long test to start with, and I would run fsck on any filesystems hosted on sdf.

Make sure you have backups, and be ready to replace the disk.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!