RE: Raid 5 Issue, cannot recognize EXT3 File system.

["Guy Watkins" <linux-raid@watkins-home.com>]

I have not paid attention to this thread.  So, might be asking a stupid
question...

Are the disks from a system of the same platform?  If not, maybe the byte
ordering is different?  I think I recall this as an issue with the 0.9
superblock, but I think it was not an issue with a newer superblock.  Maybe
it was just a feature request.  Not sure.

Anyway, mdadm supports "byteorder".  man mdadm for more info.  I have never
used it.

} -----Original Message-----
} From: linux-raid-owner@vger.kernel.org [mailto:linux-raid-
} owner@vger.kernel.org] On Behalf Of Majed B.
} Sent: Tuesday, September 22, 2009 8:14 PM
} To: Sunpyo Hong
} Cc: Robin Hill; linux-raid@vger.kernel.org
} Subject: Re: Raid 5 Issue, cannot recognize EXT3 File system.
} 
} If you are sure that you have created the array with the proper order
} of disks (They MUST be in the correct order! Your disks may have
} changed their names for some reason -- verify that they are in
} order!!) and that you have assembled them properly, I would suggest
} you run a tool called "testdisk"
} 
} You may have a corrupt filesystem, and testdisk would try to fix it.
} Also, to make sure that you have assembled the array in the correct
} order, and if the filesystem can't be fixed if it's corrupt, use a
} file-recovery tool like foremost or magicrescue and see if they
} recover your data.
} 
} On Tue, Sep 22, 2009 at 9:42 PM, Sunpyo Hong <sunpyo.hong@amac.com> wrote:
} > Nothing showed up when I did  "sudo lvscan". I'm pretty much stumped.
} >
} > -----Original Message-----
} > From: Majed B. [mailto:majedb@gmail.com]
} > Sent: Tuesday, September 22, 2009 11:24 AM
} > To: Sunpyo Hong
} > Cc: Robin Hill; linux-raid@vger.kernel.org
} > Subject: Re: Raid 5 Issue, cannot recognize EXT3 File system.
} >
} > When the array is properly assembled, "sudo lvscan" should show any
} > logical volumes. Maybe even without the array assembled.
} >
} > If nothing shows up, then you don't have an LV configured.
} >
} > On Tue, Sep 22, 2009 at 6:15 PM, Sunpyo Hong <sunpyo.hong@amac.com>
} wrote:
} >>> I am stopping and starting the array. I couldn't mount in both
} instances.
} >>> The before is the initial assembly array that I force assembled
} through
} >>> mdadm -Af. This assembled the raid, but couldn't see an ext3 file
} system.
} >>
} >>>I haven't followed all of this thread, so maybe I missed something,
} >>>but have you considered the possibility that there is an LVM config
} >>>on the md array, and that the ext3 filesystem is inside a logical
} >>>volume?
} >>
} >>>NeilBrown
} >>
} >> Hi Neil, I already checked with western digital and its support team.
} What
} >> they've told me is that the Raid is an EXT3 and is not LVM config on
} the
} > HD,
} >> however knowing WD they might just say that so I'd fork over the cash
} to
} > get
} >> my HD recovered for thousands of dollars from them. Is there a way I
} can
} >> check if it's LVM config-ed? Thanks!
} >>
} >>
} >> --
} >> To unsubscribe from this list: send the line "unsubscribe linux-raid"
} in
} >> the body of a message to majordomo@vger.kernel.org
} >> More majordomo info at  http://vger.kernel.org/majordomo-info.html
} >>
} >
} >
} >
} > --
} >       Majed B.
} >
} >
} 
} 
} 
} --
}        Majed B.
} --
} To unsubscribe from this list: send the line "unsubscribe linux-raid" in
} the body of a message to majordomo@vger.kernel.org
} More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html