Article ID: 118998, created on Dec 3, 2013, last review on May 9, 2014

  • Applies to:
  • Virtuozzo 6.0
  • Virtuozzo hypervisor


Similar error messages can be seen in the virtual machine's kernel buffer, in the output of the command dmesg or in the file /var/log/messages:

[166606.708346] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[166606.708389] ata3.00: failed command: WRITE DMA EXT
[166606.708403] ata3.00: cmd 35/00:10:a0:37:54/00:00:19:00:00/e0 tag 0 dma 8192 out
[166606.708405]          res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[166606.708419] ata3.00: status: { DRDY }
[166606.708432] ata3: hard resetting link
[166626.225053] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[166626.230668] ata3.00: configured for UDMA/100
[166626.230674] ata3.00: device reported invalid CHS sector 0
[166626.230687] ata3: EH complete


This messages are the result of the following chain of events:

  • operation of deleting a snapshot started for the virtual machine,
  • before/during the operation some request was sent from SATA driver to the physical disk (from VM point of view),
  • during snapshot deletion there is a time when the FS/VM is frozen,
  • after the snapshot has been deleted, the request is aborted because it is considered to be processed for too long,
  • these aborts are logged as the error messages you mentioned in the initial correspondence.

(In case there was no snapshot-operated operation, the cause can be different).


At the moment there are no indications that this causes any real problems for the virtual machine (except for the logged messages).

The procedure have been changed in Parallels Cloud Server - there the time VM spends 'frozen' is deducted from the time, for which SATA controller considers the request to be processed, and this kind of aborts are avoided.

Upgrading the installation to Parallels Cloud Server 6.0 is recommended.

Search Words

failed command: WRITE DMA EXT

ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

hard resetting link

ata3: hard resetting link

a26b38f94253cdfbf1028d72cf3a498b 2897d76d56d2010f4e3a28f864d69223 c62e8726973f80975db0531f1ed5c6a2 0dd5b9380c7d4884d77587f3eb0fa8ef

Email subscription for changes to this article
Save as PDF