The hard drive in an external case I used for system backups appeared to fail with I/O errors. I replaced it with a new WD hard drive (sent as a warranty replacement months ago), and WD replaced the failed drive.
Only a few weeks later, I'm seeing the same errors on the new drive. One day last week the console was filled with journal recovery errors. The next few days everything worked just fine. This morning's report of the dirvish backup cron job showed that 3 of the 6 partitions were backed up, then the process failed: >From [email protected] Mon Sep 10 00:37:34 2012 Date: Mon, 10 Sep 2012 00:37:34 -0700 (PDT) From: [email protected] To: [email protected] Subject: cron for user root /root/dirvish-backup.sh salmo-usr:default:20120909-2200: cannot open log file /media/hd0/salmo-usr/20120909-2200/log cannot open config file: default.conf cannot open config file: default.conf Just now I tried mounting the drive to see if I could figure out what's going on. Could not mount it: [root@salmo ~]# mount /media/hd0 mount: wrong fs type, bad option, bad superblock on /dev/sdb, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so Taking the advice: [root@salmo ~]# dmesg | tail EXT3-fs (sdb): error loading journal sd 318:0:0:0: [sdb] Unhandled sense code sd 318:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08 sd 318:0:0:0: [sdb] Sense Key : 0x3 [current] sd 318:0:0:0: [sdb] ASC=0x11 ASCQ=0x0 sd 318:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 1d 1b 72 b8 00 00 f0 00 end_request: I/O error, dev sdb, sector 488338104 JBD: Failed to read block at offset 27704 JBD: recovery failed EXT3-fs (sdb): error loading journal I've had very good experiences with WD drives over the years. To have issues with two of them in the same role after a couple of years of flawless operation is highly unusual. Your advice, suggestions, and recommendations are needed. I want to get my nighly backups running reliably again. If it's the iMicro enclosure (with a USB2 connection and separate power supply), suggest an alternative. If it's a software issue, advise me on how to resolve it or further diagnose what's going on. TIA, Rich _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
