Re: mdadm -A erased the superblock ?

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

 



On Saturday March 22, pradeepjp@xxxxxxxxx wrote:
> 
> > Where there any kernel message (view with 'dmesg') at this time?
> 
> Mar 21 00:27:45 brahma kernel: md: invalid raid superblock magic on sdd
> Mar 21 00:27:45 brahma kernel: md: sdd does not have a valid v0.90 superblock, not
> importing!
> Mar 21 00:27:45 brahma kernel: md: md_import_device returned -22
> 

So mdadm did try to assemble the array out of /dev/sdd.  I wonder why.

When it did that, it would have told the kernel to forget about all
the partitions on /dev/sdd so they didn't confuse things.  This is why
/dev/sdd1 etc seem to disappear.

> 
> 
>     What is much more interesting, is that I rebooted the machine, and 'mdadm --examine'
> started working again (producing output).
> I then retried the 'mdadm -A' command and that went through as well.

What do you mean exactly.  Did it assemble the array correctly?


> I cannot recall if the raid set was originally created on a 32 or a 64 bit O.S.

It shouldn't make any difference.

> 
> Is there any other diagnostic I can try ?

Not sure... If the array is working now, I don't think there is a need
to explore further.
If it isn't, maybe
  strace -o /tmp/strace mdadm -v -A ......

immediately after a reboot might help (Attach "/tmp/strace").

NeilBrown
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux