I have this same issue -- minor differences in error text -- running Hardy (v8.04.3 LTS). My message text says "ata1.00 ..." or "ata3.00 ..." instead of the ata2.00 reported here.
Trouble started after install of update that added a new kernel as [code] vmlinuz-2.6.24-26-386 vmlinuz-2.6.24-26-generic [/code] along with [code] initrd.img-2.6.24-26-386 initrd.img-2.6.24-26-generic [/code] When all of this happened, my running initrd.img file ended up in the bit bucket (I think). The corresponding vmlinuz file was not affected. Now when I boot, there is not a match between vmlinuz and initrd.img. Sadly, I'm having a whale of the time recovering the lost initrd.img from what I learn now are flawed save sets. -- ata2.00: exception emask 0x0 sact ... https://bugs.launchpad.net/bugs/223014 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
