Here is mine in RHEL4, should be the same in RHEL3: <--- START /etc/mdadm.conf---> # mdadm.conf written out by anaconda DEVICE partitions MAILADDR root ARRAY /dev/md1 level=raid1 num-devices=2 UUID=f0d98b9d:bd8357f5:9445467d:b9e05289 ARRAY /dev/md2 level=raid1 num-devices=2 UUID=66965e3b:98502fa2:0a8ede82:85ff1c4b ARRAY /dev/md7 level=raid1 num-devices=2 UUID=38fe99db:0add2b8c:d4df2965:0faa4dea ARRAY /dev/md6 level=raid1 num-devices=2 UUID=d4702493:236a896b:e68c4704:5fe82579 ARRAY /dev/md5 level=raid1 num-devices=2 UUID=bd7ca83f:6c500445:85c0e1e1:a9555bc6 ARRAY /dev/md3 level=raid1 num-devices=2 UUID=a68d6d7f:87b269c7:705482c8:4b2528ed ARRAY /dev/md4 level=raid1 num-devices=2 UUID=7248edca:4129448b:fd4f1db3:26f83913 ARRAY /dev/md0 level=raid1 num-devices=2 UUID=8cbcc547:33864bb1:f6889cf7:5effd24e <--- END /etc/mdadm.conf---> 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: >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