Arch Linux
linux package

  1. Bug #379831
  2. Comment #2

Comment 2 for bug 379831

Revision history for this message
red-naxela (red-naxela) wrote :

I found out that it is also possible to use the libata option "force=noncq". It may be implemented under Debian (and Ubuntu perhaps too, I don't have it so please verify) by adding the line

libata force=noncq

to the file "/etc/initramfs-tools/modules" and then doing a "update-initramfs -u".
Further more I created a new file "options.conf" in the directory "/etc/modprobe.d" with the line

options libata force=noncq

in it and then rebooted. My linux then booted without the mysterious SATA errors in AHCI mode. I have a Hitachi Disk HTS545032B9A300 in my 3810T.

I don't know which option is better "libata noacpi=1" or "libata force=noncq". Found the clue for disabling NCQ on a website: http://lkml.indiana.edu/hypermail/linux/kernel/0706.1/0237.html .Probably not all hard disk drives support the NCQ (Native command queuing, see Wikipedia http://en.wikipedia.org/wiki/Native_command_queuing). If someone knows more, thanks for telling me.

Remark: For adding the kernel boot parameters it did not work for me to just add "libata.force=noncq" or "libata.noacpi=1" to the grub parameters. It did not recognize the option and ignored it. This is why I did the "more complicated" way described above, works also if you prefer using the noacpi=1 variant.