Comment 88 for bug 285892

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