2017-11-20 23:34 CET

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0001852openmediavaultBugpublic2017-11-14 07:05
ReportergodFuture 
Assigned Tovotdev 
PriorityhighSeveritymajorReproducibilitysometimes
StatusclosedResolutionno change required 
Product VersionArrakis (4.x) 
Target VersionFixed in Version 
Summary0001852: System freezes frequently on sata error
DescriptionThe system boots fine. From time to time the system freezes. I notice that because the omv webview does not respond and an error dialog appears saying "communication problem". Or my nextcloud client system tray icon shows me that the nextcloud server hosted on omv just got offline. A few moments later everything is fine again. When I check the kernel log, I find this:

Nov 14 00:35:39 media-server kernel: [ 3353.635649] ata11.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Nov 14 00:35:39 media-server kernel: [ 3353.635700] ata11.00: failed command: FLUSH CACHE
Nov 14 00:35:39 media-server kernel: [ 3353.635724] ata11.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 7
Nov 14 00:35:39 media-server kernel: [ 3353.635775] ata11.00: status: { DRDY }
Nov 14 00:35:39 media-server kernel: [ 3353.635795] ata11: hard resetting link
Nov 14 00:35:39 media-server kernel: [ 3353.950012] ata11: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Nov 14 00:35:39 media-server kernel: [ 3353.976249] ata11.00: configured for UDMA/133
Nov 14 00:35:39 media-server kernel: [ 3353.976253] ata11.00: retrying FLUSH 0xe7 Emask 0x4
Nov 14 00:35:39 media-server kernel: [ 3353.976311] ata11: EH complete
(END)

Identifying the devices by their port on ata, I could see that these errors occur for the system drives which are two SSDs on lvm on mdadm. The two SSDs are the only ones that run on 6G link speed. Forcing libata to 3G helps to reduce the frequency of the freezes, but it does not prevent them completely, because there are still entries in the kernel log popping up.
Steps To ReproduceI have installed omv on minimal debian 9.2 and loaded kernel version 4.13. Normally the errors happen when the system is on writing to the disks.
Additional InformationOn Ubuntu 16.04, my previous os, these error did also exist. Changing sata cables, motherboard or even buying an as media 10x sata controller did not change that.
Tagsdebian, disk, kernel, lvm, raid, WebGUI
Product build4.0.9.1
Attached Files

-Relationships
+Relationships

-Notes

~0005031

ryecoaaron27 (reporter)

This is not an OMV issue or even a kernel issue. Your drives are having problems.

~0005032

godFuture (reporter)

@ryecoaaron27
As they work fine under windows 10 x64 pro and smart is fine...do you have more concrete ideas what is wrong with the drives? What could I test to proof your thesis?

~0005033

ryecoaaron27 (reporter)

It isn't a thesis. Look up the DRDY status on the web. Plenty of things could cause it - smart isn't perfect, it could be a bad cable, it could be bad implementation of the bios on your motherboard, a bad bios setting, etc. Either way, it isn't an OMV bug and doesn't belong on bugtracker.

~0005034

votdev (administrator)

This bug is not related to OMV.
+Notes

-Issue History
Date Modified Username Field Change
2017-11-14 01:30 godFuture New Issue
2017-11-14 01:30 godFuture Status new => assigned
2017-11-14 01:30 godFuture Assigned To => votdev
2017-11-14 01:30 godFuture Tag Attached: debian
2017-11-14 01:30 godFuture Tag Attached: disk
2017-11-14 01:30 godFuture Tag Attached: kernel
2017-11-14 01:30 godFuture Tag Attached: lvm
2017-11-14 01:30 godFuture Tag Attached: raid
2017-11-14 01:30 godFuture Tag Attached: WebGUI
2017-11-14 01:39 ryecoaaron27 Note Added: 0005031
2017-11-14 01:47 godFuture Note Added: 0005032
2017-11-14 02:03 ryecoaaron27 Note Added: 0005033
2017-11-14 07:05 votdev Status assigned => closed
2017-11-14 07:05 votdev Resolution open => no change required
2017-11-14 07:05 votdev Note Added: 0005034
+Issue History