N
Ninjix
Guest
Here's a quick tip in case anyone else encounters an ata COMRESET failed error.
Last night I added 1TB disk to our dev team's Proxmox server running on a PowerEdge
T105. Starting the systems up again, the proxmox-ve-2.6.24 kernel was slow to respond and reported ata4: COMRESET failed (errno=-16) errors. The problem was resolved by enabling the fourth SATA port in the BIOS. I'm guessing the the kernel could "sort of see" the disk but the chipset blocked the bus resets.
Hope this helps.
Last night I added 1TB disk to our dev team's Proxmox server running on a PowerEdge
T105. Starting the systems up again, the proxmox-ve-2.6.24 kernel was slow to respond and reported ata4: COMRESET failed (errno=-16) errors. The problem was resolved by enabling the fourth SATA port in the BIOS. I'm guessing the the kernel could "sort of see" the disk but the chipset blocked the bus resets.
Hope this helps.
