On Mon, 10 Jul 2006 11:13:42 -0400 William L. Maltby BillsCentOS@triad.rr.com wrote:
I am quite sure that this is an 'sfdisk' issue unrelated to the problem I needed to solve. But I would like to be careful before I declare [RESOLVED].
My workstation, in use for over a year now, shows the same warning message (start=63...) as your transcript. Further, having used sfdisk for a *long* time for some fairly rigorous applications, I have complete confidence in it. Reread the man sections on the "+" and "-" suffix and you get your first clue. The run sfdisk again and add "-uS" and I think you will be OK with it.
[snip]
Perhaps I will try sfdisk with a different machine to see if there is a difference.
I don't think you'll see any difference if the config is similar. I've attached my transcript below.
Indeed your example (below) confirms that this is an sfdisk issue, unrelated to my LVM problem which I now consider resolved.
Well, this is what I call 2 (or 3) at the price of one. Thanks for the extra education!
Itay
============================================================= [root@wlmlfs08 ~]# sfdisk -l
Disk /dev/hda: 12161 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System /dev/hda1 * 0+ 12 13- 104391 83 Linux /dev/hda2 13 2445 2433 19543072+ 8e Linux LVM /dev/hda3 2446 4876 2431 19527007+ 8e Linux LVM /dev/hda4 0 - 0 0 0 Empty Warning: start=63 - this looks like a partition rather than the entire disk. Using fdisk on it is probably meaningless. [Use the --force option if you really want this]
[root@wlmlfs08 ~]# sfdisk -l -uS
Disk /dev/hda: 12161 cylinders, 255 heads, 63 sectors/track Units = sectors of 512 bytes, counting from 0
Device Boot Start End #sectors Id System /dev/hda1 * 63 208844 208782 83 Linux /dev/hda2 208845 39294989 39086145 8e Linux LVM /dev/hda3 39294990 78349004 39054015 8e Linux LVM /dev/hda4 0 - 0 0 Empty Warning: start=63 - this looks like a partition rather than the entire disk. Using fdisk on it is probably meaningless. [Use the --force option if you really want this] [root@wlmlfs08 ~]#
============================================================================