- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi all,
I have a mSATA drive on which my virtual machines are running. When under load I regularly receive errors from the drive like the follows:
[Fr Apr 10 10:01:20 2015] ata6.00: exception Emask 0x50 SAct 0x20000 SErr 0x4890800 action 0xe frozen
[Fr Apr 10 10:01:20 2015] ata6.00: irq_stat 0x08400040, interface fatal error, connection status changed
[Fr Apr 10 10:01:20 2015] ata6: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch }
[Fr Apr 10 10:01:20 2015] ata6.00: failed command: WRITE FPDMA QUEUED
[Fr Apr 10 10:01:20 2015] ata6.00: cmd 61/40:88:90:29:e9/05:00:09:00:00/40 tag 17 ncq 688128 out
res 40/00:8c:90:29:e9/00:00:09:00:00/40 Emask 0x50 (ATA bus error)
[Fr Apr 10 10:01:20 2015] ata6.00: status: { DRDY }
[Fr Apr 10 10:01:20 2015] ata6: hard resetting link
[Fr Apr 10 10:01:21 2015] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[Fr Apr 10 10:01:21 2015] ata6.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[Fr Apr 10 10:01:21 2015] ata6.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[Fr Apr 10 10:01:21 2015] ata6.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[Fr Apr 10 10:01:21 2015] ata6.00: supports DRM functions and may not be fully accessible
[Fr Apr 10 10:01:21 2015] ata6.00: disabling queued TRIM support
[Fr Apr 10 10:01:21 2015] ata6.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[Fr Apr 10 10:01:21 2015] ata6.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[Fr Apr 10 10:01:21 2015] ata6.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[Fr Apr 10 10:01:21 2015] ata6.00: supports DRM functions and may not be fully accessible
[Fr Apr 10 10:01:21 2015] ata6.00: disabling queued TRIM support
[Fr Apr 10 10:01:21 2015] ata6.00: configured for UDMA/33
[Fr Apr 10 10:01:21 2015] ata6: EH complete
I found various threads but most of them indicated a bad SATA cable to be the issue. Since this is a mSATA drive which is directly attached to the mainboard there's no cable involved.
Then I found a thread on this forum indicating a voltage problem. Can anyone confirm compatibility issues with this mainboard+msata combination?
Is there a way to override and manually adjust the voltage in the BIOS to provide the msata drive with the appropriate voltage?
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hello Sneaker15,
Try updating the BIOS of the motherboard. Check for firmware updates for this mSATA.
What happens if you test this mSATA in a different motherboard?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi Kevin,
thanks for the quick response.
I had BIOS and MSATA Firmware already updated to latest version. Unfortunately that didn't help.
Also I don't have another motherboard to try but ordered an USB 3.0 to MSATA converter. Will try that as soon as the device arrives and let you know about the outcome.
Any advice in the meantime?
Thanks
Martin

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page