[ILUG] New drives getting recognized as device mapper devices
Walter Faleiro
curtorkar at gmail.com
Mon Oct 20 05:04:51 IST 2008
Hi,
I had two sas disk drives connected to a sunfire X4100 and used half of each
as /tmp and swap.
now when I removed them from the original system and connected it to an
alternate sunfire X4100 they get recognized as below
fdisk -l
Disk /dev/sda: 73.4 GB, 73407865856 bytes
255 heads, 63 sectors/track, 8924 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 4128 33053737+ 82 Linux swap
/dev/sda3 4129 5433 10482412+ 83 Linux
Disk /dev/sdb: 146.8 GB, 146810536448 bytes
255 heads, 63 sectors/track, 17848 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 1 17834 143251573+ 83 Linux
Disk /dev/sdc: 146.8 GB, 146810536448 bytes
255 heads, 63 sectors/track, 17848 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 1 17848 143364028+ 82 Linux swap
Disk /dev/dm-0: 146.6 GB, 146695782400 bytes
255 heads, 63 sectors/track, 17834 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/dm-0p1 1 17834 143251573+ 83 Linux
Disk /dev/dm-1: 146.6 GB, 146695782400 bytes
255 heads, 63 sectors/track, 17834 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/dm-1p1 1 17848 143364028+ 82 Linux swap
Disk /dev/dm-2: 146.6 GB, 146689611264 bytes
255 heads, 63 sectors/track, 17833 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/dm-2 doesn't contain a valid partition table
I cannot use /dev/sdbx and /dev/sdcx.
However I can use the drives when I do the following
dmsetup remove_all
mount -a
swapon /dev/sdc1
mount /dev/sdb1 /mnt/location
On subsequent reboot thought, the dm-0 and dm-1 is back in action and I have
to run dmsetup remove_all again.
The sunfire X4100 has its raid controller, but I am not sure if its the
system issue or the issue with the way the OS looks at the drives.
Has anyone encountered this before?
--Walter
More information about the ILUG
mailing list