[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Mdadm raid1 "broken" after kernel upgrade.



Hi All,

Can someone please point me in the right direction with this? I've looked on google etc but can not find a solution to it, I will really appreciate it if I can get
this working as before I did a kernel upgrade...

Before kernel:

Partitioning scheme: RAID1
mdadm -Q /dev/md0
/dev/md0: 125.38MiB raid1 2 devices, 0 spares.
active sync /dev/.static/dev/sda1
active sync /dev/.static/dev/sdb1

mdadm -Q /dev/md1
/dev/md1: 1.91GiB raid1 2 devices, 0 spares.
active sync /dev/.static/dev/sda2
active sync /dev/.static/dev/sdb2

mdadm -Q /dev/md2
/dev/md2: 184.28GiB raid1 2 devices, 0 spares.
active sync /dev/.static/dev/sda3
active sync /dev/.static/dev/sdb3

/boot ext2 /dev/md0
Swap /dev/md1
/ ext3 /dev/md2

After:

mdadm -E /dev/md0
mdadm: No super block found on /dev/md0 (Expected magic a92b4efc, got 00000000)

mdadm -E /dev/md1
mdadm: No super block found on /dev/md1 (Expected magic a92b4efc, got 00000000)

mdadm -E /dev/md2
mdadm: No super block found on /dev/md2 (Expected magic a92b4efc, got d3fdfe1d)

mdadm -Q /dev/md0
/dev/md0: 125.38MiB raid1 2 devices, 0 spares. Use mdadm --detail for more detail.
/dev/md0: No md super block found, not an md component.

mdadm -Q /dev/md1
/dev/md1: 1.91GiB raid1 2 devices, 0 spares. Use mdadm --detail for more detail.
/dev/md1: No md super block found, not an md component.

mdadm -Q /dev/md2
/dev/md2: 184.28GiB raid1 2 devices, 0 spares. Use mdadm --detail for more detail.
/dev/md2: No md super block found, not an md component.

It looks like the RAID is still working? but why does mdadm -Q report "No md super block found, not an md component"? At boot time I get a message saying that it is not a valid

mdadm --detail /dev/md0
/dev/md0:
        Version : 00.90.01
  Creation Time : Tue Jul 12 18:08:31 2005
     Raid Level : raid1
     Array Size : 128384 (125.38 MiB 131.47 MB)
    Device Size : 128384 (125.38 MiB 131.47 MB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Wed Dec 21 14:46:09 2005
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           UUID : 6c66612d:5dc6ac9a:f8397b8f:353faf1d
         Events : 0.2159

    Number   Major   Minor   RaidDevice State
0 8 1 0 active sync /dev/.static/dev/sda1 1 8 17 1 active sync /dev/.static/dev/sdb1

mdadm --detail /dev/md1
/dev/md1:
        Version : 00.90.01
  Creation Time : Tue Jul 12 18:08:43 2005
     Raid Level : raid1
     Array Size : 2000000 (1.91 GiB 2.05 GB)
    Device Size : 2000000 (1.91 GiB 2.05 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 1
    Persistence : Superblock is persistent

    Update Time : Tue Jul 12 18:32:41 2005
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           UUID : c3ad6470:16562435:0bbfb7a0:78b7e039
         Events : 0.3

    Number   Major   Minor   RaidDevice State
0 8 2 0 active sync /dev/.static/dev/sda2 1 8 18 1 active sync /dev/.static/dev/sdb2

mdadm --detail /dev/md2
/dev/md2:
        Version : 00.90.01
  Creation Time : Tue Jul 12 18:08:51 2005
     Raid Level : raid1
     Array Size : 193229696 (184.28 GiB 197.87 GB)
    Device Size : 193229696 (184.28 GiB 197.87 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 2
    Persistence : Superblock is persistent

    Update Time : Wed Dec 21 15:34:44 2005
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           UUID : ed65af19:ff18db27:b4070dfc:d4db19a0
         Events : 0.7791265

    Number   Major   Minor   RaidDevice State
0 8 3 0 active sync /dev/.static/dev/sda3 1 8 19 1 active sync /dev/.static/dev/sdb3

Thank you

Jonathan



Reply to: