none
ATA Errors on Debian 6 VM

    Question

  • I have a Microsoft Hyper-V Server 2012 that is running two guests. One VM is running Linux Debian 6 64 bit and the other is running Microsoft Windows 7 pro.  Recently I have been receiving the following errors on the Linux VM:

    ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    ata1.00: failed command: WRITE DMA
    ata1.00  cmd ca/00:08:80:fe:cd/00:00:00:00:00/e0 tag 0 dma 4096 out
                 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    ata1.00: status: {DRDY}

    I do not have LIS installed on this VM, but I did not have these errors before.  What do you recommend?

    Thanks.


    -JP

    Wednesday, April 29, 2015 10:01 PM

All replies

  • For Debian the LIS support comes built into the kernel. The LIS team submits LIS updates upstream and the Debian chooses whether to backport those changes to the kernels used in their distribution. There is no separately downloaded package for Debian to install LIS support.

    However, the kind of error you are seeing is more commonly related to a failed cable or controller, especially if you only recently started seeing the problem. Usually the first thing to try is to replace the ribbon cable connecting the drive to the controller.

    Thursday, April 30, 2015 12:15 AM
  • Thanks Josh for the response.  I do not believe the problem is hardware related.  I swapped out the SATA cable and I am receiving the same errors.  I wanted to know about the older versions of Debian and LIS support.  It looks like the LIS support being built into the kernel is for the latest version.  How can I verify that my VM has LIS installed?  Thanks.

    -JP

    Tuesday, May 19, 2015 1:30 AM
  • There is no easy way to verify the exact level of LIS, as kernel patches don't specifically tie to LIS versions, and querying LIS requires the KVP daemon which is not installed on Debian. As a result querying LIS from Hyper-V manager and Powershell produce blank results.

    From inside the VM you can use lsmod to see if the Hyper-V kernel modules are present. You should see hv_vmbus, hv_netvsc, hv_storvsc, and hv_utils at a minimum. hv_balloon, hid_hyperv, hyperv_keyboard, and hyperv_fb would indicate a pretty good set of base services.

    To have everything, a "ps aux" should indicate a running hv_fcopy_daemon, hv_vss_daemon, and hv_kvp_daemon. Unfortunately on Debian you won't be seeing those as they are not packaged and distributed via Debian's repositories.

    Access to your disks is conducted through emulated devices in Hyper-V, so it should appear as a normal ATA disk to the Linux VM. The drivers don't do very much, they just pass through requests from the VM to the underlying hardware with minimal translation. That's why my suggestion was to look for a hardware problem first.

    Was this working before and it suddenly changed? Diagnosis may require investigating other changes that may have happened before the problem started.


    Joshua R. Poulson, Program Manager, Microsoft Open Source Technology Center

    • Proposed as answer by SMARTech(CA) Wednesday, September 20, 2017 5:28 PM
    • Unproposed as answer by SMARTech(CA) Wednesday, January 31, 2018 9:10 PM
    Tuesday, May 19, 2015 5:06 PM
  • I have a Microsoft Hyper-V Server 2012 that is running two guests. One VM is running Linux Debian 6

    ~~

     Why not Debian 7 ? Or 8 ?

    (

     Using modern version , IMHO, can solve problems

    )




    ~~

    From inside the VM you can use lsmod to see if the Hyper-V kernel modules are present. You should see hv_vmbus, hv_netvsc, hv_storvsc, and hv_utils at a minimum.

    ~~

    Yes, and see some info on

    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661318

    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684283

     +

    http://vvm.blog.tut.by/2012/11/02/debian-on-hyper-v/

    Wednesday, May 20, 2015 2:14 PM
  • "Backtrace"

    Is that a tool to help in this case?

    Tuesday, September 19, 2017 8:26 PM
  • ~~

    "Backtrace"

    Is that a tool to help in this case?

    ~~

    Please, describe your case more detail. Are You really need Debian 6?

    Tuesday, October 10, 2017 1:16 PM
  • Hello All,

    I upgraded the hardware for my Hyper V server and also I performed a fresh install of Debian 8.  The problem no longer exists.


    -JP


    • Edited by SMARTech(CA) Wednesday, January 31, 2018 9:09 PM
    • Proposed as answer by SMARTech(CA) Wednesday, January 31, 2018 9:09 PM
    Wednesday, January 31, 2018 9:09 PM