From: Eric Sandeen <sandeen@redhat.com>
To: Drew Reusser <dreusser@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Issue with bad file system
Date: Mon, 19 Nov 2012 09:18:01 -0600 [thread overview]
Message-ID: <50AA4DA9.5090602@redhat.com> (raw)
In-Reply-To: <CAPAnFc9ziuDdFV=4u2jcaGFTBV4M6xnkqbatOB0azgSShDYxTQ@mail.gmail.com>
On 11/18/12 10:46 PM, Drew Reusser wrote:
> Hello all,
>
> I am having an issue with a ext4 file system which I cannot get to
> come back up. There were no changes that I know of, but I rebooted,
> and when the system came back up it was not able to read from the hard
> drives. I have it setup in a raid 10 configuration, and can mount the
> raid array with no issues. However when I mount the file system, I
> get the following error "EXT4-fs (md0): VFS: Can't find ext4
> filesystem" from the log files.
>
> Is there anyone that can help as I have to get this data back and I
> prefer not to have to go to a professional to get it back and spend
> the money.
>
> -Drew
>
> Basic Info: 4x1TB disks, raid 10 equaling 2TB total. All four disks
> are just one giant partition starting at the 2MB mark so I could boot
> and put mdadm in the boot sector and get into linux.
>
> Some basic commands below:
>
>
> mint mnt # mount -t ext4 /dev/md0 /mnt/raid
> mount: wrong fs type, bad option, bad superblock on /dev/md0,
> missing codepage or helper program, or other error
> In some cases useful info is found in syslog - try
> dmesg | tail or so
>
Ok, at this point you need to do what it says:
# dmesg | tail
so we can see for ourselves why the kernel rejected it (is there
anything other than "EXT4-fs (md0): VFS: Can't find ext4
filesystem" ?
does /proc/mdstat look right? This is more likely an md config
issue than an ext4 problem. What does file -s /dev/md0 or
blkid /dev/md0 say?
-Eric
>
>
> C is the pen-drive I am booting from currently and F is the 2TB disk I
> was using to backup to.
>
> mint dev # cat /proc/partitions
> major minor #blocks name
>
> 7 0 939820 loop0
> 8 0 976762584 sda
> 8 1 976760832 sda1
> 8 16 976762584 sdb
> 8 17 976237568 sdb1
> 8 32 1985024 sdc
> 8 33 1984960 sdc1
> 8 48 976762584 sdd
> 8 49 976760832 sdd1
> 8 64 976762584 sde
> 8 65 976237568 sde1
> 11 0 1048575 sr0
> 8 80 1953514584 sdf
> 8 81 1953512448 sdf1
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2012-11-19 15:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 4:46 Issue with bad file system Drew Reusser
2012-11-19 15:18 ` Eric Sandeen [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-19 6:30 George Spelvin
2012-11-19 7:23 ` Drew Reusser
2012-11-19 8:32 ` George Spelvin
2012-11-19 15:29 ` Eric Sandeen
2012-11-19 17:00 ` Drew Reusser
2012-11-19 16:57 ` Drew Reusser
2012-11-19 17:14 ` Eric Sandeen
2012-11-19 18:41 ` Theodore Ts'o
2012-11-19 19:15 ` George Spelvin
2012-11-19 19:36 ` Theodore Ts'o
2012-11-19 19:53 ` Drew Reusser
2012-11-19 20:24 ` Theodore Ts'o
2012-11-19 19:54 ` Drew Reusser
2012-11-19 21:15 ` George Spelvin
2012-11-19 21:30 ` Eric Sandeen
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=50AA4DA9.5090602@redhat.com \
--to=sandeen@redhat.com \
--cc=dreusser@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.