Something seems to be wrong with my file systems, and I want to fsck everything. But I cannot. The setup consists of 2 hds, carrying 3 raid1 (ext3) file systems (boot, /, swap). OS is up-to-date CentOS 5. So I boot from CentOS 5.3 dvd in rescue mode, do not mount the file systems, and try to run fsck -y /dev/md0 fsck -y /dev/md1 fsck -y /dev/md2 For each try I get an error message: "Superblock could not be found..." "The device does not seem to contain a valid ext2 filesystem..." Well, of course not, the filesystem is ext3, not ext2. I also tried fsck.ext3, but the error messages stay the same. So, how could I fsck these arrays? - Jussi -- Jussi Hirvi * Green Spot Topeliuksenkatu 15 C * 00250 Helsinki * Finland Tel. +358 9 493 981 * Mobile +358 40 771 2098 (only sms) jussi.hirvi at greenspot.fi * http://www.greenspot.fi
On Wed, Jul 21, 2010 at 9:42 PM, Jussi Hirvi <listmember at greenspot.fi> wrote:> Something seems to be wrong with my file systems, and I want to fsck > everything. But I cannot. > > The setup consists of 2 hds, carrying 3 raid1 (ext3) file systems (boot, > /, swap). OS is up-to-date CentOS 5. > > So I boot from CentOS 5.3 dvd in rescue mode, do not mount the file > systems, and try to run > ? ? ? ?fsck -y /dev/md0 > ? ? ? ?fsck -y /dev/md1 > ? ? ? ?fsck -y /dev/md2 > > For each try I get an error message: "Superblock could not be found..." > "The device does not seem to contain a valid ext2 filesystem..."ext2 is the base of the journaling ext3 FS. I would suggest you use TestDisk <http://www.cgsecurity.org/wiki/TestDisk> and see if you can recover your filesystem. The tool is powerful. I have been able to recover disk partitions and the filesystems within when all other tools reported "no disk partition" on the HDD. Good luck. -- Arun Khan
On Jul 21, 2010, at 12:12 PM, Jussi Hirvi <listmember at greenspot.fi> wrote:> Something seems to be wrong with my file systems, and I want to fsck > everything. But I cannot. > > The setup consists of 2 hds, carrying 3 raid1 (ext3) file systems (boot, > /, swap). OS is up-to-date CentOS 5. > > So I boot from CentOS 5.3 dvd in rescue mode, do not mount the file > systems, and try to run > fsck -y /dev/md0 > fsck -y /dev/md1 > fsck -y /dev/md2 > > For each try I get an error message: "Superblock could not be found..." > "The device does not seem to contain a valid ext2 filesystem..." > > Well, of course not, the filesystem is ext3, not ext2. > > I also tried fsck.ext3, but the error messages stay the same. > > So, how could I fsck these arrays?Are you using lvm on top of the mdraid? If so you need to fsck the lvs not the mds. -Ross
On 07/21/2010 09:12 AM, Jussi Hirvi wrote:> > So I boot from CentOS 5.3 dvd in rescue mode, do not mount the file > systems, and try to run > fsck -y /dev/md0 > fsck -y /dev/md1 > fsck -y /dev/md2 > > For each try I get an error message: "Superblock could not be found..." > "The device does not seem to contain a valid ext2 filesystem..."Perhaps they weren't started automatically? Try running "mdadm -IRs" and then look at the contents of /proc/mdstat and the output of 'dmesg' for more information.
Jussi Hirvi schrieb:> Something seems to be wrong with my file systems, and I want to fsck > everything. But I cannot. > > The setup consists of 2 hds, carrying 3 raid1 (ext3) file systems (boot, > /, swap). OS is up-to-date CentOS 5. > > So I boot from CentOS 5.3 dvd in rescue mode, do not mount the file > systems, and try to run > fsck -y /dev/md0 > fsck -y /dev/md1 > fsck -y /dev/md2you should check, using "cat /proc/mdstat ", whether the raid devices were found and started. If not, you could do it manually, e.g. mdadm /dev/md0 --assemble /dev/sdaX /dev/sdbY where the disk (e.g. a and b) and partition (e.g. X and Y) names need to be filled in. There's also mdadm --examine /dev/sdaX , and of course fdisk -l /dev/sda Once the devices appear correctly in /proc/mdstat, you should be able to fsck them. HTH, Kay> > For each try I get an error message: "Superblock could not be found..." > "The device does not seem to contain a valid ext2 filesystem..." > > Well, of course not, the filesystem is ext3, not ext2. > > I also tried fsck.ext3, but the error messages stay the same. > > So, how could I fsck these arrays? > > - Jussi >