Perusal, Synthesis, Bliss

November 18, 2012: again a problem with external hard drive

As one year ago (November 1, 2011), I have a problem with an external hard drive: a Seagate Momentus 5400.6 (500 GB) hard drive shipped with my MSI computer (which mother card has rapidly burnt). I have put it in an external hard drive box (brand: Auchan). rdiff-backup gives I/O errors at some time in the backup process. So, first I use:
$ sudo fsck.ext3 -y /dev/dm-6
e2fsck 1.42.5 (29-Jul-2012)
/dev/dm-6 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Error reading block 45613398 (Attempt to read block from filesystem resulted in short read) while getting next inode from scan.  Ignore error? yes
Force rewrite? yes
But after some time, strange lines appear:
Directory inode 17433576, block #0, offset 0: directory corrupted
Salvage? yes
Missing ’.’ in directory inode 17433576.
Fix? yes
Setting filetype for entry ’.’ in ??? (17433576) to 2.
Missing ’..’ in directory inode 17433576.
Fix? yes
Setting filetype for entry ’..’ in ??? (17433576) to 2.
It is finished after few hours, and the disk seems to be clean:
$ fsck.ext3 -y /dev/dm-6
e2fsck 1.42.5 (29-Jul-2012)
/dev/dm-6: clean, 546078/19537920 files, 30142314/78141952 blocks
But a new try of rdiff-backup yields an error almost immediately:
OSError: [Errno 5] Input/output error: ’/media/c3c3a9ac-e40d-48c8-9a33-fbdb3cef04e5/home/rdiff-backup-data/increments/local/jscordia/src/external_projects/0_OLD_EXTERNAL_PROJECTS/libgda-4.1.11/libgda/thread-wrapper/.deps’
So I use badblocks, as one year ago:
$ badblocks /dev/dm-6

I stop it after after one night, and as one year ago, I try:
$ mke2fs -cc -t ext4 /dev/dm-6
But it is very, very long. I decide to stop it, before the end. After that, impossible to mount it. Then I used the OpenSuse partitioner to format it with encryption. I do it without problem, and reboot: it is recognized correctly on Kubuntu. It remains to see if it will accept several backups without I/O error.
Several weeks later, about five backups after, no problem, and no nasty sound.
April 20, 2013: still no problem has appeared.