So for instance, where I can run: mount /dev/sda1 /media/tmp It will attempt to mount but complain about either a bad filesystem, superblock, etc. If I try to mount the cloned drive: mount: you must specify the filesystem type Looking back at dmesg the results are different: [767942.335569] JBD2: Invalid start block of journal: 0 [767942.335572] EXT4-fs (sda1): error loading journal [767947.740996] EXT3-fs (sdf1): error: can't find ext3 filesystem on dev sdf1. [767947.741123] EXT4-fs (sdf1): VFS: Can't find ext4 filesystem [767947.741253] FAT-fs (sdf1): invalid media value (0xad) [767947.741255] FAT-fs (sdf1): Can't find a valid FAT filesystem [767947.741403] EXT2-fs (sdf1): error: can't find an ext2 filesystem on dev sdf1. [767957.299593] EXT4-fs (sdf1): VFS: Can't find ext4 filesystem Looking at dumpe2fs for the filesystem on /dev/sdf1 (sdf is the cloned drive, the actual drive, sda, is in the original e-mail) root@server:~# dumpe2fs /dev/sdf1 dumpe2fs 1.42.5 (29-Jul-2012) dumpe2fs: Bad magic number in super-block while trying to open /dev/sdf1 Couldn't find valid filesystem superblock. dd didn't say it had any errors, and the log file for ddrescue doesn't appear to give any errors either. I can run it again though. Should there be any difference in the command that I run this time? I was under the impression that notrunc,noerror,sync would have been suitable to clone the drive over. On Wed, Sep 25, 2013 at 12:50 PM, Eric Sandeen <sandeen@xxxxxxxxxx> wrote: > On 9/25/13 11:35 AM, InvTraySts wrote: >> Not used to mailing list courtesy so forgive how gmail responds to these... >> >> I didn't have any kind of error on the RAID controller itself. When I >> went back for one of the weekends, I went into the RAID controller >> BIOS and everything was reported as normal. Of the four logical drives >> experiencing problems, only two of them were on the controller, one >> was plugged into the motherboard, the last one was plugged into an >> add-on SATA card. >> >> I don't know what happened on the 24th of August, all I know is that >> it was working fine the previous night, tried to get on the network, >> and everything had stopped working (web server, DHCP, bind, samba, >> etc). Went down to inspect the machine and noticed that it was running >> but there was nothing showing up the monitor when plugging it in. So I >> am not sure of the exact events of how it failed, I just know that >> after hardware testing, the processor was dead. > > Ok, so pretty extreme hardware failure. > >> I have tried using dd and ddrescue using the following commands: >> dd if=/dev/sdc of=/dev/sdf bs=4096 conv=notrunc,noerror,sync >> ddrescue -vf /dev/sdh /dev/sdf /home/andrew/logfile.txt > > (you said the copy was worse; what was wrong with it?) > (did the dd or ddrescue encounter any errors while doing the copy?) > > dd should have worked fine, and you should be able to play with that > image. First thing I'd try, if it still throws the bad journal > error first, is to tune2fs -O ^has_journal /dev/sdf > > Then try to mount and /or run e2fsck on it, see how it fares. > The journal is just the first thing mount's going to look at; > if the corruption is widespread you may just have a cascade of other > errors behind it, but worth a shot. > > -Eric > -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
