9.10 not recognizing 9.04 partitions [old superblocks?]

Bug #538597 reported by StargazerA5
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mdadm (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: mdadm

I created a RAID1 data(non-root, os is installed on a separate physical disk /dev/sdb) array in Jaunty 64 using all of sda1 and sdc1. Due to some unrelated problems, I had to do a fresh install and decided to use Karmic. I have not been able to get the array to be discovered in Karmic 64. In investigating, I noticed that Karmic had /dev/sda and /dev/sdc; while Jaunty had /dev/sda, /dev/sda1, /dev/sdc, and /dev/sdc1. Verified that discrepancy via a Jaunty 64 install disk.

Karmic:
---
root@Draco:~# ls/dev/sd*
/dev/sda /dev/sdb1 /dev/sdb3 /dev/sdb5
/dev/sdb /dev/sdb2 /dev/sdb4 /dev/sdc
root@Draco:~#
---
Jaunty:
---
root@ubuntu:~# ls/dev/sd*
/dev/sda /dev/sdb /dev/sdb2 /dev/sdb4 /dev/sdc
/dev/sda1 /dev/sdb1 /dev/sdb3 /dev/sdb5 /dev/sdc1
root@ubuntu:~#
---

Running fdisk in Karmic does reveal the partitions (note sdb6 and sdb7 deleted since running this output):

----
root@Draco:~# fdisk -l

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000e819b

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 121601 976760001 fd Linux raid autodetect

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00068bd7

   Device Boot Start End Blocks Id System
/dev/sdb1 * 1 15024 120680248+ 83 Linux
/dev/sdb2 15667 15810 1156680 82 Linux swap / Solaris
/dev/sdb3 15811 23821 64348357+ 83 Linux
/dev/sdb4 23822 121601 785417850 5 Extended
/dev/sdb5 43225 121601 629563221 83 Linux
/dev/sdb6 * 23822 42431 149484762 83 Linux
/dev/sdb7 42432 43224 6369741 82 Linux swap / Solaris

Partition table entries are not in disk order

Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00060ccb

   Device Boot Start End Blocks Id System
/dev/sdc1 1 121601 976760001 fd Linux raid autodetect

---

I suspect that the reason I can not detect the array is that Karmic can't see the partitions (though fdisk can???).

I further verified this behavior by checking /dev using a Karmic 64 disk

I also have a thread with more information about my attempts at using mdam failing at http://ubuntuforums.org/showthread.php?p=8962522

StargazerA5

Tags: dmraid mdadm
Revision history for this message
ceg (ceg) wrote :

Maybe https://wiki.ubuntu.com/ReliableRaid (Blocked hotplugging mechanisims)?

Revision history for this message
StargazerA5 (ubuntulaunchpad-beyondthishorizon) wrote :

Hi Ceg,

I think I partially understood that, but I don't think I understood well enough to check it out. Can you advise what I should do?

Thanks!

StargazerA5

Revision history for this message
ceg (ceg) wrote :

Bug #442735 dmraid eats mdadm-managed raid in upgrading from 9.04 to 9.10

If you don't use sata fakeraid, try uninstalling dmraid and "sudo update-initramfs -k all -u".

ceg (ceg)
summary: - RAID1 partitions created in Jaunty not recognised by Karmic
+ RAID1 partitions created in Jaunty not recognised by Karmic [old
+ superblocks?]
ceg (ceg)
summary: - RAID1 partitions created in Jaunty not recognised by Karmic [old
- superblocks?]
+ RAID1 partitions created in 9.04 not recognised 9.10 [old superblocks?]
ceg (ceg)
summary: - RAID1 partitions created in 9.04 not recognised 9.10 [old superblocks?]
+ 9.10 not recognizing 9.04 partitions [old superblocks?]
Revision history for this message
StargazerA5 (ubuntulaunchpad-beyondthishorizon) wrote :

That did it! Once dmraid was gone (and I reboot) Karmic started recognizing the missing partitions. Once that happened, I just had to get the array up and running.

tags: added: dmraid mdadm
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.