Try an `lvscan` to see if your logical volume is detected. Then mount the appropriate /dev/mapper/... device instead of the bare /dev/md0.
On Fri, Jan 29, 2010 at 12:17 PM, Mike A. <[email protected]> wrote: > I believed it's in LVM > > > On Fri, Jan 29, 2010 at 12:15 PM, Mark David Dumlao <[email protected]> > wrote: >> You moved it from an old server to a new one. By any chance, did you >> use xfs, jfs, or some nonstandard filesystem on your old server? >> Perhaps you don't have the appropriate xfs/jfs tools installed on your >> new one just yet. Or perhaps you used LVM before? >> >> On Fri, Jan 29, 2010 at 11:59 AM, Mike A. <[email protected]> wrote: >>> Hi, >>> >>> I installed a new CentOS server and added 4 hard disk which is >>> configured as RAID0. These hard disk came from an old server and just >>> wanted to restore the data that's store in it. >>> >>> In DMESG, it says that the RAID was detected and it was configured. (see >>> below) >>> >>> md: Autodetecting RAID arrays. >>> md: autorun ... >>> md: considering sdd1 ... >>> md: adding sdd1 ... >>> md: adding sdc1 ... >>> md: adding sdb1 ... >>> md: adding sda1 ... >>> md: created md0 >>> md: bind<sda1> >>> md: bind<sdb1> >>> md: bind<sdc1> >>> md: bind<sdd1> >>> md: running: <sdd1><sdc1><sdb1><sda1> >>> md: raid0 personality registered for level 0 >>> md0: setting max_sectors to 512, segment boundary to 131071 >>> raid0: looking at sdd1 >>> raid0: comparing sdd1(976759808) with sdd1(976759808) >>> raid0: END >>> raid0: ==> UNIQUE >>> raid0: 1 zones >>> raid0: looking at sdc1 >>> raid0: comparing sdc1(976759808) with sdd1(976759808) >>> raid0: EQUAL >>> raid0: looking at sdb1 >>> raid0: comparing sdb1(976759808) with sdd1(976759808) >>> raid0: EQUAL >>> raid0: looking at sda1 >>> raid0: comparing sda1(976759808) with sdd1(976759808) >>> raid0: EQUAL >>> raid0: FINAL 1 zones >>> raid0: done. >>> raid0 : md_size is 3907039232 blocks. >>> raid0 : conf->hash_spacing is 3907039232 blocks. >>> raid0 : nb_zone is 1. >>> raid0 : Allocating 4 bytes for hash. >>> md: ... autorun DONE. >>> >>> However, whenever I mount /dev/md0 to a folder, it gives me this error: >>> >>> mount: wrong fs type, bad option, bad superblock on /dev/md0, >>> missing codepage or other error >>> In some cases useful info is found in syslog - try >>> dmesg | tail or so >>> >>> What do you think is the problem? How can I mount /dev/md0 so I can >>> restore it's data? >>> >>> Please help. >>> >>> Thanks! >>> _________________________________________________ >>> Philippine Linux Users' Group (PLUG) Mailing List >>> http://lists.linux.org.ph/mailman/listinfo/plug >>> Searchable Archives: http://archives.free.net.ph >>> >> >> >> >> -- >> This email is: [ ] actionable [ ] fyi [ ] social >> Response needed: [ ] yes [ ] up to you [ ] no >> Time-sensitive: [ ] immediate [ ] soon [ ] none >> _________________________________________________ >> Philippine Linux Users' Group (PLUG) Mailing List >> http://lists.linux.org.ph/mailman/listinfo/plug >> Searchable Archives: http://archives.free.net.ph >> > _________________________________________________ > Philippine Linux Users' Group (PLUG) Mailing List > http://lists.linux.org.ph/mailman/listinfo/plug > Searchable Archives: http://archives.free.net.ph > -- This email is: [ ] actionable [ ] fyi [ ] social Response needed: [ ] yes [ ] up to you [ ] no Time-sensitive: [ ] immediate [ ] soon [ ] none _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List http://lists.linux.org.ph/mailman/listinfo/plug Searchable Archives: http://archives.free.net.ph
