Raid1 mdadm: RAID1 error: mdadm: No super block found on ...

From: Reinhard Sy (reinhard_at_meinberlikomm.de)
Date: 05/04/04

  • Next message: jludwig: "Re: HD corruption" 
    To: fedora-list@redhat.com
Date: Tue, 04 May 2004 21:18:36 +0200

    Hi

    I have now set my RAID1 but if I use :

    [root@muckla root]# mdadm -E /dev/md0
    mdadm: No super block found on /dev/md0 (Expected magic a92b4efc, got
    00000000)
    [root@muckla root]# mdadm -E /dev/md1
    mdadm: No super block found on /dev/md1 (Expected magic a92b4efc, got
    00000000)
    [root@muckla root]# mdadm -E /dev/md2
    mdadm: No super block found on /dev/md2 (Expected magic a92b4efc, got
    139d47d7)
    [root@muckla root]#

    What does it mean ?. I think my raid running well.

    Here the output of lsraid for md0:

    [root@muckla root]# lsraid -a /dev/md0
    [dev 9, 0] /dev/md0 1628B05F.8E582771.6BC25A99.B080AB1F
    online
    [dev 3, 1] /dev/hda1 1628B05F.8E582771.6BC25A99.B080AB1F good
    [dev 22, 1] /dev/hdc1 1628B05F.8E582771.6BC25A99.B080AB1F good

    If I do an query with mdadm I get :

    [root@muckla root]# mdadm -Q --detail /dev/md0
    /dev/md0:
            Version : 00.90.00
      Creation Time : Sun May 2 21:53:46 2004
         Raid Level : raid1
         Array Size : 4882624 (4.66 GiB 4.100 GB)
        Device Size : 4882624 (4.66 GiB 4.100 GB)
       Raid Devices : 2
      Total Devices : 2
    Preferred Minor : 0
        Persistence : Superblock is persistent

        Update Time : Mon May 3 05:49:54 2004
              State : dirty, no-errors
     Active Devices : 2
    Working Devices : 2
     Failed Devices : 0
      Spare Devices : 0

        Number Major Minor RaidDevice State
           0 3 1 0 active sync /dev/hda1
           1 22 1 1 active sync /dev/hdc1
               UUID : 1628b05f:8e582771:6bc25a99:b080ab1f
             Events : 0.13
    [root@muckla root]#

    Is the state dirty a problem ? I have nothing found in the man page of
    mdadm.

    Here some additional information about the disks.....

    fdisk looks good I set the type to fd
    [root@muckla root]# fdisk -l /dev/hda

    Disk /dev/hda: 80.0 GB, 80026361856 bytes
    255 heads, 63 sectors/track, 9729 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes

       Device Boot Start End Blocks Id System
    /dev/hda1 1 608 4883728+ fd Linux raid autodetect
    /dev/hda2 609 1094 3903795 fd Linux raid autodetect
    /dev/hda3 1095 9729 69360637+ fd Linux raid autodetect
    [root@muckla root]# fdisk -l /dev/hdc

    Disk /dev/hdc: 80.0 GB, 80026361856 bytes
    16 heads, 63 sectors/track, 155061 cylinders
    Units = cylinders of 1008 * 512 = 516096 bytes

       Device Boot Start End Blocks Id System
    /dev/hdc1 1 9688 4882720+ fd Linux raid autodetect
    /dev/hdc2 9689 17438 3906000 fd Linux raid autodetect
    /dev/hdc3 17439 155061 69361992 fd Linux raid autodetect

    Here my /etc/raidtab:

    [root@muckla root]# cat /etc/raidtab
    raiddev /dev/md0
            raid-level 1
            nr-raid-disks 2
            nr-spare-disks 0
            chunk-size 4
            persistent-superblock 1
            device /dev/hda1
            raid-disk 0
            device /dev/hdc1
            raid-disk 1
    raiddev /dev/md1
            raid-level 1
            nr-raid-disks 2
            nr-spare-disks 0
            chunk-size 4
            persistent-superblock 1
            device /dev/hda2
            raid-disk 0
            device /dev/hdc2
            raid-disk 1
    raiddev /dev/md2
            raid-level 1
            nr-raid-disks 2
            nr-spare-disks 0
            chunk-size 4
            persistent-superblock 1
            device /dev/hda3
            raid-disk 0
            device /dev/hdc3
            raid-disk 1

    Sorry a lot of questions.

    Has anybody got the same problems or is it not a problem ?

    BTW: I am running a smp kernel: Linux muckla 2.4.21-9.0.1.EL.um.3smp #1
    SMP Thu Apr 22 12:46:27 JST 2004 i686 i686 i386 GNU/Linux

    Is this the problem.

    Thanks for any hint
    Reinhard 

    -- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
  • Next message: jludwig: "Re: HD corruption"

    Relevant Pages

    • Re: MD device not found on boot
      ... Gave up waiting for root device. ... mdadm: metadata format 00.90 unknown ignored. ... metada format 00.90 unknown, ...
      (Debian-User)
    • Re: Raid1 mdadm: RAID1 error: mdadm: No super block found on ...
      ... State: dirty, no erros ... [root@muckla root]# mdadm -E /dev/hda1 ... Raid Devices: 2 ... > From man mdadm ...
      (Fedora)
    • [opensuse] Having mdadm to email
      ... With 10.2 having activitieson any drive was emailing ... to root. ... There is any setup ... somewhere to have mdadm send an email in case of problem. ...
      (SuSE)
    • labelling root file system (RELENG_8)
      ... installation's root partition. ... This failed, tunefs reports it cannot ... Still no joy => tunefs cannot update the super block. ... The root fs uses softupdates but no journalling -- what other hoops do I ...
      (freebsd-stable)