mdadm: metadata format 00.90 unknown, ignored.

[fjgaude]

Strange... using 9.10 desktop and letting the OS auto config the mdadm.conf file, there is no metadata=0.090 in the ARRAY line.

[Joshua]

I've just upgraded my RAID box to 9.10 and I'm seeing that problem as well. My version:

$ mdadm --version
mdadm - v2.6.7.1 - 15th October 2008

(Just to be clear, I'm running Karmic, 9.10 and not 8.10 as that date might indicate.)

I think fjgaude is correct that for simple setups, the auto configuration of the mdadm.conf file seems to work fine and I don't think it included any "metadata=X" parameter. When I set mine up, I had to manipulate the assignment of drives to new arrays and my setup involves arrays of arrays. I couldn't get the mdadm.conf file to be automatically generated correctly. So after I got the array working correctly, I ran:

$ sudo -i
# mdadm --detail --scan >> /etc/mdadm/mdadm.conf

That added new "ARRAY..." lines to the end of the mdadm.conf file. Then, I went into the file and manually deleted the old "ARRAY..." lines.

I noticed at the time that one major difference in those lines was the presence of the "metadata=X" parameter in the new lines. So far I haven't seen any problems with running the array with or without that parameter, though.

[runesvend]

I'm running Lucid and it's still present here, because the version of mdadm is the same:

mdadm - v2.6.7.1 - 15th October 2008

I've requested that mdadm be updated in the bug report linked to below. Please mark this as "affects me too" if you're interested in getting mdadm updated.

Bug 603118: Please update mdadm to version 3.1.2

[JohnnyC35]

I know this is an old thread but I just thought I would say that this bug is still around. I have (er had it) with the 00.90 format number, removing the 0 fixed it. I have the same error with "mdadm: metadata format 01.02 unknown, ignored." I tried removing the 0,that didn't seem to fix it. Just throwing that out there. Oh. and my mdadm version is v2.6.7.1 - 15th October 2008, on Ubuntu 10.04

[rubylaser]

Have you tried changing the metadata line in your /etc/mdadm/mdadm.conf to look like this?

ARRAY /dev/md0 metadata=1.2 UUID=d4e58776:640274d8:e368bf24:bd0fce41

[JohnnyC35]

Have you tried changing the metadata line in your /etc/mdadm/mdadm.conf to look like this?

ARRAY /dev/md0 metadata=1.2 UUID=d4e58776:640274d8:e368bf24:bd0fce41

it is coming up
mdadm: metadata format 1.02 unknown, ignored.

but I tried it as you quoted and the it came up as
mdadm: metadata format 1.2* unknown, ignored.

it's very odd

[rubylaser]

This works fine for me with mdadm 3.1.4

ARRAY /dev/md/0 metadata=1.2 spares=2 name=mdadm-test:0 UUID=3b5636d7:ba53bd11:9d6dbfd7:9b8a351f

root@mdadm-test:~# mdadm --detail /dev/md0
/dev/md0:
        Version : 1.2
  Creation Time : Tue Feb  8 19:09:35 2011
     Raid Level : raid10
     Array Size : 2087936 (2039.34 MiB 2138.05 MB)
  Used Dev Size : 1043968 (1019.67 MiB 1069.02 MB)
   Raid Devices : 4
  Total Devices : 6
    Persistence : Superblock is persistent

  Intent Bitmap : Internal

    Update Time : Tue Feb  8 19:12:41 2011
          State : active
 Active Devices : 4
Working Devices : 6
 Failed Devices : 0
  Spare Devices : 2

         Layout : near=2
     Chunk Size : 512K

           Name : mdadm-test:0
           UUID : 3b5636d7:ba53bd11:9d6dbfd7:9b8a351f
         Events : 20

    Number   Major   Minor   RaidDevice State
       0       8       17        0      active sync   /dev/sdb1
       1       8       33        1      active sync   /dev/sdc1
       2       8       49        2      active sync   /dev/sdd1
       3       8       65        3      active sync   /dev/sde1

       4       8       81        -      spare   /dev/sdf1
       5       8       97        -      spare   /dev/sdg1

This is just a Virtualbox instance, but it works fine for me with a newer version of mdadm.

[JohnnyC35]

hmm...

here's my details

sudo mdadm --detail /dev/md0
mdadm: metadata format 1.02 unknown, ignored.
/dev/md0:
Version : 01.02
Creation Time : Mon Jan 24 08:35:59 2011
Raid Level : raid1
Array Size : 971755649 (926.74 GiB 995.08 GB)
Used Dev Size : 1943511298 (1853.48 GiB 1990.16 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent

Update Time : Wed Feb 9 19:21:43 2011
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

Name : Downloads
UUID : f17ac96a:2a8ffc04:f19011d2:7689175f
Events : 16628

Number Major Minor RaidDevice State
0 8 18 0 active sync /dev/sdb2
2 8 114 1 active sync /dev/sdh2

[rubylaser]

Did you create this with the metadata=1.2 or -e 1.2 options? I assume so. If so, it could just be the older version of mdadm causing the problem.

[JohnnyC35]

my one raid, raid5 I created via cli. my raid1, the one I am having that error, I created it with the Ubuntu disk utility, so maybe that's how it got that funky metadata number. if it won't cause any issues I'll just ignore it