We are on the same thing. Just had a look at /etc/mdadm.conf and I have no entries. Do I have to enter anything in this manually? Marc On Fri, 2006-01-27 at 16:01 -0500, Tom Callahan wrote: > try this: > > run "mdadm --detail --scan" > and paste the output into /etc/mdadm.conf, after removing all lines that > say "PARTITION" or "ARRAY" > > Then try rebooting and see what happens. I fear your array is not being > restarted upon boot. > > Thanks, > > Tom Callahan > TESSCO Technologies > Desk: (410)-229-1361 > Cell: (443)-506-6216 > Email: callahant@xxxxxxxxxx > > A real engineer only resorts to documentation when the keyboard dents on the forehead get too noticeable. > > > > Marc Leveille wrote: > > >I followed your advice and was able to make a file system on /dev/mdo. I > >enter this entry in fstab > >/dev/md0 /home/apps ext3 defaults 1 2 > > > >I tried ext2 and ext3 and got the same error after re-booting.this > >happens when Checking file system runs > >" The superblock could not be read or does not describe a valid ext2 > >file system/. > > > >the odd thing is that as soon as I create the file system on /dev/md0, I > >can mount it using mount -t ext3 /dev/md0 /home/apps. I can go in and > >see the lost and found folder. it only fails after a re-boot. Also if I > >remove the mdo entry in fstab, reboot and try mounting it manually, it > >now fails (invalid file system) > > > >thanks > > > >Marc > > > >On Fri, 2006-01-27 at 13:30 -0500, Frank DiPrete wrote: > > > > > >>Check the order here: > >> > >>1) create physical partitions on sdb and sdc of type linux raid > >>2) create the (soft) raid array > >>3) mkfs on the raid device created in step 2 > >>4) mount the file system created in step 3 > >> > >> > >> > >> > > > > > > > -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
