On Fri, 2006-01-27 at 13:47, 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) Others have suggested the /etc/mdmadm.conf file, which may help. However, if you are running a 2.4.x kernel you may have better luck with and /etc/raidtab config file. Recent experiences here show that the 2.4.x kernel series has a startup script for /etc/raidtab but not /etc/mdmadm.conf. The 2.4.x kernels use older commands that are part of the raidtools package. Newer 2.6.x kernels use newer commands like mdadm. Both can be used the manipulate software RAID arrays, but again I don't think 2.4.x kernels include a startup scripts for mdmadm and the associated configuration file. -Eric -- Eric Sisler <esisler@xxxxxxxxxxxxxxxxxxxxx> Library Applications Specialist Westminster Public Library Westminster, CO USA Linux - Don't fear the Penguin. Want to know what we use Linux for? Visit http://wallace.westminster.lib.co.us/linux -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
