Concluded the second test, BAD BLOCK confirmed, at the same spot. Looks to me this is the trouble maker, and this made me look ridiculous... I was believing that fsck would "grasp" any inconsistencies or bad blocks upon boot up, silly me, it just does partial check-ups. The Samsung's ESTOOL utility ended up my rage quest against AMD SB700 and Samsung themselves.
Guess it's time for a backup and a badblocks -svw /dev/sda3 -- ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen https://bugs.launchpad.net/bugs/285892 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
