Upgraded edgy to feisty, device-mapper is dieing on raid0 arrays
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devmapper (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
On boot the kernels device mapper contiously floods output:
[35923.922369] device-mapper: table: 254:5: striped: Couldn't parse stripe destination
[35923.922420] device-mapper: ioctl: error adding target to table
[35924.034654] device-mapper: table: 254:5: striped: Couldn't parse stripe destination
[35924.034704] device-mapper: ioctl: error adding target to table
The root drive is correctly mapped:
/dev/mapper/hda3 30715280 7114904 23600376 24% /
but both of my raid 0 arrays (2 disks each) are not working anymore:
brw-rw---- 1 root disk 9, 0 2007-04-25 00:59 /dev/md0
brw-rw---- 1 root disk 9, 255 2007-04-25 00:59 /dev/md255
The mdstat shows one is online
chris@:~$ cat /proc/mdstat
Personalities : [raid0]
md0 : active raid0 hdc[0] sdc[1]
586114560 blocks 64k chunks
unused devices: <none>
but it wont mount with my original fstab entry of /dev/md0 and complains of wrong fs type
This output seems wrong as to state there are two arrays on the same device?
chris@:~$ sudo vim /etc/mdadm/
DEVICE partitions
ARRAY /dev/md0 level=raid0 num-devices=2 UUID=db874dd1:
ARRAY /dev/md0 level=raid0 num-devices=2 UUID=af45c1d8:
MAILADDR root
chris@:~$ ls -l /dev/disk/by-uuid
total 0
lrwxrwxrwx 1 root root 17 2007-04-25 01:00 352ecc55-
lrwxrwxrwx 1 root root 17 2007-04-25 01:00 5746f359-
lrwxrwxrwx 1 root root 9 2007-04-25 00:59 60b92513-
lrwxrwxrwx 1 root root 19 2007-04-25 00:59 60fcedab-
lrwxrwxrwx 1 root root 17 2007-04-25 01:00 9159561a-
lrwxrwxrwx 1 root root 17 2007-04-25 01:00 e831455b-
chris@:-$ sudo fdisk -l (snippet)
Disk /dev/md0: 600.1 GB, 600181309440 bytes
2 heads, 4 sectors/track, 146528640 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk /dev/md0 doesn't contain a valid partition table
This is a result of an upgrade from a working edgy installation, which was upgraded previously from an original dapper install. The previous kernel was 2.6.17-11, and now I'm using 2.6.20-15. I tried booting the 17 kernel and it soft panicked on the device mapper. There was a patch added to this code (I googled the above error message) that traps this error in the recent kernel so something happened to my arrays during the upgrade. Any ideas?
Do you still have this problem with gutsy?