Problems with invalid superblock

Problems with invalid superblock

[William Marques]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I trying to setup a raid0 without success, using the mdadm 2.3.1
package, compiled from sources.
No matters if its linear or stripping raid0 mode, the errors are the same:

master# mdadm --create --verbose /dev/md0 --level=0 --raid-devices=2
/dev/sda2 /dev/sda3
master:~# mdadm -E /dev/md0
mdadm: No md superblock detected on /dev/md0.

I made  a lot's of tests with this, trying to recriate, but without sucess.

The strange thing is that the Raid is running:
master:~# mdadm -Q -D /dev/md0
/dev/md0:
        Version : 00.90.01
  Creation Time : Fri Feb 17 19:35:21 2006
     Raid Level : raid0
     Array Size : 1052096 (1027.61 MiB 1077.35 MB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Fri Feb 17 19:35:21 2006
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

     Chunk Size : 64K

           UUID : ad53c04e:73590c3f:8ea811aa:f81097e1
         Events : 0.1

    Number   Major   Minor   RaidDevice State
       0       8        2        0      active sync   /dev/sda2
       1       8        3        1      active sync   /dev/sda3
But I cant mount the device:
mount: wrong fs type, bad option, bad superblock on /dev/md0,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so


I'm using a Debian Sarge box, updated, but with mdadm compiled from
sources. With Debian binaries, the same error occours.
Kernel 2.6.8-2-686
Tested with ubuntu 5.10, kernel 2.6.12 compiled from source with the
same resoults.
Is it a problem if the devices are on the same HD? I'm trying this way
because it's a test. If, so thats ok, in real life we will be using 2
SATA 160GB discs.
Has anyone else that I can do?

If anyone has any clue about this, please, let me know, as it is part of
a important project I'm working on, and I gave this solution to "merge"
the hard discs in one bigger device.

Thanks in advance,

- --
William Marques
Consultor Linux - TI
LPIC-1: LPI000058633
Scinergy Consulting Ltda.
Fone: +55 21 2224-3224
http://www.scinergy.com.br
Rio de Janeiro - Brasil
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFD9kdZbwzoNUPCOg8RAtvDAJ9gLoNsEF47VjmkhDyIyXmXMpHaUwCfewFG
wyuUjlS4+QhM96XVoS7b8mE=
=hmqJ
-----END PGP SIGNATURE-----

Re: Problems with invalid superblock

[Patrik Jonsson]

[-- Attachment #1: Type: text/plain, Size: 666 bytes --]

William Marques wrote:
> Hi,
> 
> I trying to setup a raid0 without success, using the mdadm 2.3.1
> package, compiled from sources.
> No matters if its linear or stripping raid0 mode, the errors are the same:
> 
> master# mdadm --create --verbose /dev/md0 --level=0 --raid-devices=2
> /dev/sda2 /dev/sda3
> master:~# mdadm -E /dev/md0
> mdadm: No md superblock detected on /dev/md0.
...

> But I cant mount the device:
> mount: wrong fs type, bad option, bad superblock on /dev/md0,
>        missing codepage or other error
>        In some cases useful info is found in syslog - try
>        dmesg | tail  or so

You did make a file system on md0, right?

/Patrik

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]

Re: Problems with invalid superblock

[Gil]

William Marques wrote:
> Hi,
> 
> I trying to setup a raid0 without success, using the mdadm 2.3.1
> package, compiled from sources.
> No matters if its linear or stripping raid0 mode, the errors are the same:
> 
> master# mdadm --create --verbose /dev/md0 --level=0 --raid-devices=2
> /dev/sda2 /dev/sda3
> master:~# mdadm -E /dev/md0
> mdadm: No md superblock detected on /dev/md0.

Try mdadm -E /dev/sda2 or mdadm -E /dev/sda3.

--Gil

Re: Problems with invalid superblock

[William Marques]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gil escreveu:
> William Marques wrote:
>> Found something interesting in syslog:
>>
>> Feb 17 21:25:27 master kernel: md: bug in file drivers/md/md.c, line 1513
>> Feb 17 21:25:27 master kernel:
>> Feb 17 21:25:27 master kernel: md:^I**********************************
>> Feb 17 21:25:27 master kernel: md:^I* <COMPLETE RAID STATE PRINTOUT> *
>> Feb 17 21:25:27 master kernel: md:^I**********************************
>> Feb 17 21:25:27 master kernel: md0:
>> Feb 17 21:25:27 master kernel: md:^I**********************************
>> Feb 17 21:25:27 master kernel:
> 
> Not really.  This is the sort of thing I would post back to the
> list.  Earlier I was just pointing out that mdadm -E was for the
> components of a raid device, rather than the raid device itself.
> 
> --Gil
> 
ok, sorry abou that, I don realize tha I just not copy the list... done now.

- --
William Marques
Consultor Linux - TI
LPIC-1: LPI000058633
Scinergy Consulting Ltda.
Fone: +55 21 2224-3224
http://www.scinergy.com.br
Rio de Janeiro - Brasil
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFD9oefbwzoNUPCOg8RAntqAJwKVWzUmD/x3l6ZVujOjoHoPuULAgCfQaTS
ISGTnRcKnUUhsPy2iG7Q0EY=
=0VkN
-----END PGP SIGNATURE-----