Nothing is connected to eSATA. I don't even have any eSATA device to check what happens when I connect it.

I don't think this is normal situation having a massive error message flooding to the log files.It stopes when I ordinary remove the sda devce with 'rm /dev/sda'.I don't think this is a solution. BTW I put this command into the /etc/rc.local.

Nothing is connected to eSATA. I don't even have any eSATA device to check what happens when I connect it.

I don't think this is normal situation having a massive error message flooding to the log files.It stopes when I ordinary remove the sda devce with 'rm /dev/sda'.I don't think this is a solution. BTW I put this command into the /etc/rc.local.

It seems to be a bug in kernel.

Is anyone else facing the same issue?

Install smartmontools if you don't have it already and run a "long" test. That should tell you if you have a drive problem.

Yeah, your right. I didn't read your post carefully enough to see you don't have anything connected to /dev/sda.

I'd say you probably have some software that's checking for available devices periodically and causing the kernel to spit out the errors when it detects no device attached at sda. If it really is the driver software polling the device by itself (without a software request), someone should probably fix that.

You could compile a custom kernel without the sata drivers included, that would eliminate it.

I've found that udisks-daemon was polling all the devs: /dev/sda /dev/sdb and /dev/sdc probably for automounting.

I just eliminated it by adding the following line:

Code:

KERNEL=="sda*", ENV{UDISKS_DISABLE_POLLING}="1"

to /lib/udev/rules.d/80-udisks.rules

however there's still open question remaining. Is it a bug in kernel sata module or udisks itself causing error message when accessing not connected disk or just my controller port is broken.Unfortunately I can't check it out because I haven't got the eSATA device.

I have the same issue with log flooding. I noticed it at the very beginning, when I got the D2plug. So I guess it is already present in the original configuration.

I now plugged in my eSATA drive. It shows up in /var/log/messages but you have to look for it, as dmesg will be flooded again instantly. According to

Code:

fdisk -l

the eSATA drive is on /dev/sdc and not sda which is mentioned in dmesg.

I then plugged in another external drive on the USB port: it appears as /dev/sdd and again it is instantly hidden in dmesg. When I remove the eSATA drive and plug in the USB hard disk on the combined eSATA/USB port, it is recognised as /dev/sdc. Same thing happens when the drive is plugged in at boot.