Find the answer to your Linux question:
Results 1 to 2 of 2
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1

    RAID 0 Filesystem checking?

    os:Red Hat Enterpris Linux ES release 3

    i combined two harddisk to RAID 0 and format it to ext 3.
    Then add the line "/dev/md0 /new ext3 defaults 1 1" into fstab.
    No error occurred after run " mount -a". Everyting oK.

    reboot system

    When the filesystem check, error occur.

    checking filesystems
    fsck.ext3: /dev/md0:
    The superblock could not be read or does not describe a 
    correct ext2 filesystem.
    If the device is valid and it really contains an ext 2 filesystem 
    ( and not swap or ufs or something else),
    then the superblock is corrupt, and you might try running 
    e2fsck with an alternate superblock&#58; e2fsck -b 8193 <device>
    Invalid argument while trying to open /dev/md0
    How can i do to fix it?

    If set it to not be checked at startup
    -"/dev/md0 /new ext3 defaults 0 0" into fstab.

    mount&#58; wrong fs type, bad option, bad superblock on /dev/md0,
           or too many mounted file systems
           &#40;could this be the IDE device where you in fact use
           ide-scsi so that sr0 or sda or so is needed?&#41;

    Show about error but i can enter linux.
    it can't mount md0 (raid drive).

    On the other side,
    "raidstart /dev/md0"
    "mount -t ext3 /dev/md0 /new"
    md0 can be used!!


  2. #2

    Question /dev/md0 mount of external seemed to corrupt

    I made attempts to mount an external firewire drive to my system. I have hosed something up with the /dev/md0 raid volume. I get the superblock error described above and I am unable to mount.

    Has anyone learned any more about this problem. Any new insights in recent months?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts