Re: Re Help with ES v3 Raid
- From: Marc Leveille <marc.leveille@xxxxxxxxxxxxxx>
- Date: Fri, 27 Jan 2006 15:47:40 -0500
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
- Follow-Ups:
- Re: Re Help with ES v3 Raid
- From: Eric Sisler
- Re: Re Help with ES v3 Raid
- From: Tom Callahan
- Re: Re Help with ES v3 Raid
- References:
- Re Help with ES v3 Raid
- From: Frank DiPrete
- Re Help with ES v3 Raid
- Prev by Date: Re Help with ES v3 Raid
- Next by Date: Re: Help with ES v3 Raid1 (Mirror)
- Previous by thread: Re Help with ES v3 Raid
- Next by thread: Re: Re Help with ES v3 Raid
- Index(es):
Relevant Pages
|