Comment 8 for bug 544548

Unfortunately, the workaround only works for a limit period of time. After some time, the problem reappears.

I attach an excerpt of my /var/log/messages. It starts with an unrecognized drive ("VFS" error messages). At 21:59:21, I do the workaround (sudo rmmod pata_via ; sudo modprobe pata_via) and the drive begins to work again... until 22:17:41, when I got an error message from udisk-daemon, following with a call trace, then a fault from hald-addon-st (with a call trace), then a fault from VirtualBox (and a call trace)... and finally the ata5 stops working around 22:20:55.

Then I do the workaround one more time (sudo rmmod pata_via ; sudo modprobe pata_via) and now I have again a functional drive... attached as ata7 instead of ata5, don't know why.