Public bug reported:

Binary package hint: mdadm

Ubuntu server 6.06.1 i386

# mdadm --version; uname -a
mdadm - v1.12.0 - 14 June 2005
Linux server 2.6.15-27-server #1 SMP Fri Dec 8 18:43:54 UTC 2006 i686 GNU/Linux

# mdadm --query  /dev/md0
/dev/md0: 7.45GiB raid1 2 devices, 0 spares. Use mdadm --detail for more detail.
/dev/md0: No md super block found, not an md component.

Please, notice message "/dev/md0: No md super block found, not an md
component." in mdadm command answer. I think it is a bug as when I add "
--detail" switch, mdadm reports that "Superblock is persistent".
Somethingh has to be wrong here.

More details:

# cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 hdc6[2] hda6[0]
      283161536 blocks [2/1] [U_]
      [===>.................]  recovery = 15.1% (42771328/283161536) 
finish=116.6min speed=34330K/sec

md0 : active raid1 hdc5[1] hda5[0]
      7815488 blocks [2/2] [UU]

unused devices: <none>

# mdadm --query  /dev/md0
/dev/md0: 7.45GiB raid1 2 devices, 0 spares. Use mdadm --detail for more detail.
/dev/md0: No md super block found, not an md component.

# mdadm --query --detail /dev/md0
/dev/md0:
        Version : 00.90.03
  Creation Time : Sun Dec 31 14:14:38 2006
     Raid Level : raid1
     Array Size : 7815488 (7.45 GiB 8.00 GB)
    Device Size : 7815488 (7.45 GiB 8.00 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Mon Jan  1 16:03:34 2007
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           UUID : 1db5229c:5ef0b957:3f02ce46:bbdbd39c
         Events : 0.52971

    Number   Major   Minor   RaidDevice State
       0       3        5        0      active sync   /dev/hda5
       1      22        5        1      active sync   /dev/hdc5

# mount | grep md0
/dev/md0 on / type ext3 (rw,errors=remount-ro)

I see the same behavior on /dev/md1.

I build this md array with Ubuntu server 6.06.1 i386 install CD, I used
only one disk during installation, so RAID1 was configured as "degraded
(1 disk of 2)". I copied data from original disk to the new  RAID aray
and I am now updating RAID array to use 2 disks. I think this
information is not not interested for this bug report...

** Affects: mdadm (Ubuntu)
     Importance: Undecided
         Status: Unconfirmed

** Description changed:

  Binary package hint: mdadm
  
  Ubuntu server 6.06.1 i386
  
  # mdadm --version; uname -a
  mdadm - v1.12.0 - 14 June 2005
  Linux server 2.6.15-27-server #1 SMP Fri Dec 8 18:43:54 UTC 2006 i686 
GNU/Linux
  
  # mdadm --query  /dev/md0
  /dev/md0: 7.45GiB raid1 2 devices, 0 spares. Use mdadm --detail for more 
detail.
  /dev/md0: No md super block found, not an md component.
  
  Please, notice message "/dev/md0: No md super block found, not an md
  component." in mdadm command answer. I think it is a bug as when I add "
  --detail" switch, mdadm reports that "Superblock is persistent".
  Somethingh has to be wrong here.
  
  More details:
  
  # cat /proc/mdstat
  Personalities : [raid1]
  md1 : active raid1 hdc6[2] hda6[0]
        283161536 blocks [2/1] [U_]
        [===>.................]  recovery = 15.1% (42771328/283161536) 
finish=116.6min speed=34330K/sec
  
  md0 : active raid1 hdc5[1] hda5[0]
        7815488 blocks [2/2] [UU]
  
  unused devices: <none>
  
  # mdadm --query  /dev/md0
  /dev/md0: 7.45GiB raid1 2 devices, 0 spares. Use mdadm --detail for more 
detail.
  /dev/md0: No md super block found, not an md component.
  
  # mdadm --query --detail /dev/md0
  /dev/md0:
          Version : 00.90.03
    Creation Time : Sun Dec 31 14:14:38 2006
       Raid Level : raid1
       Array Size : 7815488 (7.45 GiB 8.00 GB)
      Device Size : 7815488 (7.45 GiB 8.00 GB)
     Raid Devices : 2
    Total Devices : 2
  Preferred Minor : 0
      Persistence : Superblock is persistent
  
      Update Time : Mon Jan  1 16:03:34 2007
            State : clean
   Active Devices : 2
  Working Devices : 2
   Failed Devices : 0
    Spare Devices : 0
  
             UUID : 1db5229c:5ef0b957:3f02ce46:bbdbd39c
           Events : 0.52971
  
      Number   Major   Minor   RaidDevice State
         0       3        5        0      active sync   /dev/hda5
         1      22        5        1      active sync   /dev/hdc5
  
+ # mount | grep md0
+ /dev/md0 on / type ext3 (rw,errors=remount-ro)
+ 
+ I see the same behavior on /dev/md1.
+ 
  I build this md array with Ubuntu server 6.06.1 i386 install CD, I used
  only one disk during installation, so RAID1 was configured as "degraded
  (1 disk of 2)". I copied data from original disk to the new  RAID aray
  and I am now updating RAID array to use 2 disks. I think this
  information is not not interested for this bug report...

-- 
mdadm reports "/dev/md0: No md super block found, not an md component."
https://launchpad.net/bugs/77609

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to