From: Eric Sandeen <sandeen@redhat.com>
To: InvTraySts <invtrasys@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Fwd: Need help with Data Recovery on Ext4 partitions that became corrupted on running OS
Date: Wed, 25 Sep 2013 16:45:35 -0500 [thread overview]
Message-ID: <5243597F.1010108@redhat.com> (raw)
In-Reply-To: <CAOWv6b3_DbKjD5aGa1g-zEbVyJOar7NXLbaVA8ZKx+9s62bO2A@mail.gmail.com>
On 9/25/13 12:09 PM, InvTraySts wrote:
> 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.
that's userspace mount; look at dmesg to see what really went wrong.
> 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
ok, you did clone it wrong. Maybe you cloned sdc to sdf1? What do
# blkid /dev/sdf1
# blkid /dev/sdf
say?
> 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.
Should be. I think maybe you must "missed."
-Eric
next prev parent reply other threads:[~2013-09-25 21:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOWv6b1Jq0MAtELB_brhg_G3S2svEW8EaW9A8ciddTUdqDWFdQ@mail.gmail.com>
[not found] ` <CAOWv6b1m8A2S3sjDsJxOrRVztch6iq4zH9eFq5DKFMqtWWWpEw@mail.gmail.com>
2013-09-25 2:25 ` Fwd: Need help with Data Recovery on Ext4 partitions that became corrupted on running OS InvTraySts
2013-09-25 15:35 ` Eric Sandeen
2013-09-25 16:35 ` InvTraySts
2013-09-25 16:50 ` Eric Sandeen
2013-09-25 17:09 ` InvTraySts
2013-09-25 21:45 ` Eric Sandeen [this message]
2013-09-25 23:57 ` InvTraySts
2013-09-26 0:57 ` Eric Sandeen
2013-09-25 16:12 ` Jan Kara
2013-09-25 19:24 ` InvTraySts
2013-09-25 21:28 ` Jan Kara
2013-09-26 0:08 ` InvTraySts
2013-09-26 0:59 ` Eric Sandeen
2013-09-26 1:41 ` InvTraySts
2013-09-26 8:53 ` Jan Kara
2013-09-26 17:45 ` InvTraySts
2013-09-26 20:18 ` Jan Kara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5243597F.1010108@redhat.com \
--to=sandeen@redhat.com \
--cc=invtrasys@gmail.com \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.