Skip to contentSkip to conversation

Kernel says there is not a valid superblock, but there is

DISCUSSION Phillip Susi 2 participants 3 messages Oct 20, 2014 – Oct 21, 2014 MD RAID

lore
Share & tools
lore

Phillip Susi

author
#0 lore raw

When trying to assemble, the kernel complains:

md: md1 stopped.
md: sda2 does not have a valid v1.2 superblock, not importing!
md: md_import_device returned -22
md: sdb2 does not have a valid v1.2 superblock, not importing!
md: md_import_device returned -22

Yet the superblock looks perfectly fine according to mdadm -E:

/dev/sda2:

          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 34e89993:37821273:5498dc63:07233b2c
           Name : devserv2:1

Creation Time : Mon Jun 16 11:24:00 2014
Raid Level : raid1
Raid Devices : 2

Avail Dev Size : 3900907520 (1860.10 GiB 1997.26 GB)

     Array Size : 158334976 (151.00 GiB 162.14 GB)
  Used Dev Size : 316669952 (151.00 GiB 162.14 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 40c38a87:88807f78:5bf71f34:4c9b2215

    Update Time : Mon Oct 20 09:56:25 2014
       Checksum : d2369656 - correct
         Events : 303

Device Role : Active device 0
Array State : AA ('A' == active, '.' == missing)

/dev/sdb2:

          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 34e89993:37821273:5498dc63:07233b2c
           Name : devserv2:1

Creation Time : Mon Jun 16 11:24:00 2014
Raid Level : raid1
Raid Devices : 2

Avail Dev Size : 3900907520 (1860.10 GiB 1997.26 GB)

     Array Size : 158334976 (151.00 GiB 162.14 GB)
  Used Dev Size : 316669952 (151.00 GiB 162.14 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 0fb85e8f:e697a9a0:7bd6eac4:03b8851d

    Update Time : Mon Oct 20 10:08:35 2014
       Checksum : 9b63a13c - correct
         Events : 311

Device Role : Active device 1
Array State : .A ('A' == active, '.' == missing)

#1 lore raw
Quoted 1 line · On Mon, 20 Oct 2014 11:09:59 -0400 Phillip Susi <[email protected]> wrote:

When trying to assemble, the kernel complains:

Which kernel?
uname -a
and may as well add
mdadm -V

as well.

NeilBrown

Quoted 64 lines

md: md1 stopped.
md: sda2 does not have a valid v1.2 superblock, not importing!
md: md_import_device returned -22
md: sdb2 does not have a valid v1.2 superblock, not importing!
md: md_import_device returned -22

Yet the superblock looks perfectly fine according to mdadm -E:

/dev/sda2:

          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 34e89993:37821273:5498dc63:07233b2c
           Name : devserv2:1

Creation Time : Mon Jun 16 11:24:00 2014
Raid Level : raid1
Raid Devices : 2

Avail Dev Size : 3900907520 (1860.10 GiB 1997.26 GB)

     Array Size : 158334976 (151.00 GiB 162.14 GB)
  Used Dev Size : 316669952 (151.00 GiB 162.14 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 40c38a87:88807f78:5bf71f34:4c9b2215

    Update Time : Mon Oct 20 09:56:25 2014
       Checksum : d2369656 - correct
         Events : 303

Device Role : Active device 0
Array State : AA ('A' == active, '.' == missing)

/dev/sdb2:

          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 34e89993:37821273:5498dc63:07233b2c
           Name : devserv2:1

Creation Time : Mon Jun 16 11:24:00 2014
Raid Level : raid1
Raid Devices : 2

Avail Dev Size : 3900907520 (1860.10 GiB 1997.26 GB)

     Array Size : 158334976 (151.00 GiB 162.14 GB)
  Used Dev Size : 316669952 (151.00 GiB 162.14 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 0fb85e8f:e697a9a0:7bd6eac4:03b8851d

    Update Time : Mon Oct 20 10:08:35 2014
       Checksum : 9b63a13c - correct
         Events : 311

Device Role : Active device 1
Array State : .A ('A' == active, '.' == missing)
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

author
#2 lore raw
Quoted 10 lines · NeilBrown
Quoted 1 line · On Mon, 20 Oct 2014 11:09:59 -0400 Phillip Susi <[email protected]> wrote:

When trying to assemble, the kernel complains:

Which kernel?
uname -a
and may as well add
mdadm -V

as well.

uname -a
Linux hyper1 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

mdadm -V
mdadm - v3.2.5 - 18th May 2012

I managed to hack around with dmsetup to create a linear mapping to the correct data offset that mdadm -E listed and recover my data and blow away and recreate the array. I saved a dump of the superblock if you want them for debugging.