Re: Re Help with ES v3 Raid

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

Relevant Pages

  • Re: insufficient space in super block for rotational layout
    ... Occurs typically on very high density disks. ... the file system structure cannot ... Is this really an issue with a RAID 5 storage ... It doesn't sound like a problem with the array, but the size of the array. ...
    (comp.unix.solaris)
  • Problems creating RAID 5 using mdadm
    ... I have a fresh debian sarge installation on a RAID 1 array. ... # /etc/fstab: static file system information. ... The superblock could not be read or does not describe a correct ext2 filesystem. ...
    (Debian-User)
  • Re: Need help with corrupted RAID array
    ... How do you know it is the file system that is damaged and not the raid ... Have you run a chkdsk yet from the Recovery Console? ... One of the biggest dangers with a raid 0 array is that if something goes ...
    (microsoft.public.windowsxp.general)
  • Re: Need help with corrupted RAID array
    ... So what happens when you try to load Windows? ... I have no experience troublshooting a RAID setup, ... >> array? ... Is there any way to repair the file system? ...
    (microsoft.public.windowsxp.general)
  • RE: SUSPECT: Re: Directory Size problem
    ... running on muptiple computers and do not keep its queues in one ... the reason for the problem with the space not freeing ... The problem may be identified by rebooting the computer. ... Every file has two counters on it in the file system. ...
    (Fedora)