Discussion:
[gentoo-user] Disk /dev/dm-0 doesn't contain a valid partition table
(too old to reply)
Valmor de Almeida
2010-08-03 16:10:03 UTC
Permalink
Hello,

After a recent sync and new kernel built, I get these messages from
fdisk -l that did not use to get before. Searching the web, it appears
that fdisk is listing my LVM partitions. Why is it doing now? It has
never done it before.

Thanks,

--
Valmor


fdisk -l

Disk /dev/dm-0: 26.8 GB, 26843545600 bytes
255 heads, 63 sectors/track, 3263 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/dm-0 doesn't contain a valid partition table

Disk /dev/dm-1: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/dm-1 doesn't contain a valid partition table

Disk /dev/dm-2: 5368 MB, 5368709120 bytes
255 heads, 63 sectors/track, 652 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/dm-2 doesn't contain a valid partition table

Disk /dev/dm-3: 2147 MB, 2147483648 bytes
255 heads, 63 sectors/track, 261 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/dm-3 doesn't contain a valid partition table

Disk /dev/dm-4: 53.7 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/dm-4 doesn't contain a valid partition table


df

/dev/mapper/vfda-usr 26213596 11144004 15069592 43% /usr
/dev/mapper/vfda-var 10485436 232620 10252816 3% /var
/dev/mapper/vfda-opt 5242716 311388 4931328 6% /opt
/dev/mapper/vfda-tmp 2097084 32852 2064232 2% /tmp
/dev/mapper/vfda-home
Bill Longman
2010-08-03 17:10:01 UTC
Permalink
Post by Valmor de Almeida
Hello,
After a recent sync and new kernel built, I get these messages from
fdisk -l that did not use to get before. Searching the web, it appears
that fdisk is listing my LVM partitions. Why is it doing now? It has
never done it before.
Thanks,
--
Valmor
fdisk -l
Disk /dev/dm-0: 26.8 GB, 26843545600 bytes
255 heads, 63 sectors/track, 3263 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/dm-0 doesn't contain a valid partition table
Disk /dev/dm-1: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/dm-1 doesn't contain a valid partition table
Disk /dev/dm-2: 5368 MB, 5368709120 bytes
255 heads, 63 sectors/track, 652 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/dm-2 doesn't contain a valid partition table
Disk /dev/dm-3: 2147 MB, 2147483648 bytes
255 heads, 63 sectors/track, 261 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/dm-3 doesn't contain a valid partition table
Disk /dev/dm-4: 53.7 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/dm-4 doesn't contain a valid partition table
df
/dev/mapper/vfda-usr 26213596 11144004 15069592 43% /usr
/dev/mapper/vfda-var 10485436 232620 10252816 3% /var
/dev/mapper/vfda-opt 5242716 311388 4931328 6% /opt
/dev/mapper/vfda-tmp 2097084 32852 2064232 2% /tmp
/dev/mapper/vfda-home
It seems to me you now have BLK_DEV_DM in your kernel.

I've seen this on many systems with lvm. I always thought it was normal
and I just ignored them. But I do have some systems that have lvm that
don't show those errors. What partition support do you have in your new
kernel?
Mark Knecht
2010-08-03 18:10:02 UTC
Permalink
Post by Valmor de Almeida
Hello,
After a recent sync and new kernel built, I get these messages from
fdisk -l that did not use to get before. Searching the web, it appears
that fdisk is listing my LVM partitions. Why is it doing now? It has
never done it before.
Thanks,
--
Valmor
Don't know if it's involved but the recent updates warned about
changes in how /dev is handled. I'd suggest going back to those
messages and making sure the warnings were comprehended.

Hope this helps,
Mark
Bill Longman
2010-08-03 22:10:02 UTC
Permalink
Post by Valmor de Almeida
fdisk -l
Disk /dev/dm-0 doesn't contain a valid partition table
Why are you using fdisk on a logical volume? To my knowledge (which of
course may be outdated/wrong) an LV doesn't contain a partition table so
looking for it with fdisk -l shouldn't give you any valid data. Use lvs
or lvdisplay instead. If you wish to manipulate the underlying partition
table (the "physical volumes") then you can use fdisk...
He's not doing on a physical volume, they just happen to show up. He's
just using "fdisk -l" to generally see what volumes are out there.
pk
2010-08-03 23:10:01 UTC
Permalink
Post by Bill Longman
He's not doing on a physical volume, they just happen to show up. He's
just using "fdisk -l" to generally see what volumes are out there.
Ah, ok. Misunderstanding from my side...

Best regards

Peter K

pk
2010-08-03 22:10:02 UTC
Permalink
Post by Valmor de Almeida
fdisk -l
Disk /dev/dm-0 doesn't contain a valid partition table
Why are you using fdisk on a logical volume? To my knowledge (which of
course may be outdated/wrong) an LV doesn't contain a partition table so
looking for it with fdisk -l shouldn't give you any valid data. Use lvs
or lvdisplay instead. If you wish to manipulate the underlying partition
table (the "physical volumes") then you can use fdisk...

Best regards

Peter K
Loading...