>>> 1. The problem was fixed when I went through the 3mb/second channel.
That's probably because it was a different controller or the hardware at least differed sufficiently enought so as to not exhibit the problem.
>>> 2. I had to re-install the OS completely due to data corruption caused by the READ FDMA QUEUED errors. Don't expect your system to work properly until you've re-installed.
I've had no problem getting 'fsck.ext4' to repair the minimal amount of problems that were caused so far. My system remounts the filesystem read-only immediately upon detection of errors so nothing else can be written and maybe that helped reduce any corruption.
Nevertheless, this is certainly a very serious problem and this bug warrants a high priority.
>>> 1. The problem was fixed when I went through the 3mb/second channel.
That's probably because it was a different controller or the hardware at least differed sufficiently enought so as to not exhibit the problem.
>>> 2. I had to re-install the OS completely due to data corruption caused by the READ FDMA QUEUED errors. Don't expect your system to work properly until you've re-installed.
I've had no problem getting 'fsck.ext4' to repair the minimal amount of problems that were caused so far. My system remounts the filesystem read-only immediately upon detection of errors so nothing else can be written and maybe that helped reduce any corruption.
Nevertheless, this is certainly a very serious problem and this bug warrants a high priority.