Found a work around or "fix". The Long Story: Apparently dmraid took my two partitions. Not exactly sure what it does with them, but it does prevent them from showing up within the /dev directory.
I read a lot of forums and found a simple way to have the partition show up as /dev/sdb1. You open the disk with fdisk using: fdisk /dev/sdb and then use the 'w' command to write the same partition table back to the disk. (Please be careful to make sure when you use 'p' command that the partitions are indeed what you expect.) So I did this for /dev/sdb and /dev/sdc, partitions for both of the disks now appeared in /dev. Now I tried to reassemble the mdadm raid and found that it was running in degraded mode. I saw that the partition it was using was "dm-0". (Something like that cannot remember exactly). I was confused for a little bit and a bit worried about my data. So a quick google showed that it was dmraid which had taken over. Doing: dmraid -b (command to list the partitions. this is from memory please read the man page to be sure) I got a list of the partitions it was managing. So it appeared that it was working "correctly" mdadm was just picking up the partitions created by dm-raid as a single disk and saying that it was a degraded array. The fix: I fixed this problem by removing the package dmraid and libdmraid. I also did fdisk /dev/sdb and then rewrote the same partition table (using 'w' command). This would cause the partition /dev/sdb1 to show up! I am not sure if fdisk is really necessary. -- 9.10 - Ubuntu cannot find partitions on my disk + network will not work https://bugs.launchpad.net/bugs/460790 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
