[opensuse] Partition 1 does not end on cylinder boundary
I just upgraded my 160GB hdd to 500GB on my ThinkPad T60 and everything was fine with my original 2 distros. fdisk -l listed with no errors. I installed 5 new distros including OpenSuse 11.3 Suse works fine but now: # fdisk -l now reads: Disk /dev/sda: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 6374 51196288+ 7 HPFS/NTFS Partition 1 does not end on cylinder boundary. /dev/sda2 6374 7167 6365520 c W95 FAT32 (LBA) Partition 2 does not end on cylinder boundary. /dev/sda3 7167 8670 12073320 c W95 FAT32 (LBA) Partition 3 does not end on cylinder boundary. /dev/sda4 8670 60802 418751369+ f W95 Ext'd (LBA) /dev/sda5 8670 8798 1028128+ 82 Linux swap / Solaris /dev/sda6 8798 13897 40960048+ 83 Linux /dev/sda7 13897 18996 40960048+ 83 Linux /dev/sda8 18996 19379 3076888+ 83 Linux /dev/sda9 19379 23204 30723808+ 83 Linux /dev/sda10 23204 27029 30723808+ 83 Linux /dev/sda11 27030 27794 6144831 83 Linux /dev/sda12 27795 28559 6144831 83 Linux /dev/sda13 28560 29324 6144831 83 Linux sda6, sda7, sda8, and sda9 end at cylinder and the next partition starts at same cylinder as the previous cylinder. The next partition should start at the next cylinder as sda10,sda11,sda12 and sda13. How can I correct this? Does testdisk correct this, is it safe to use? jozien -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I just upgraded my 160GB hdd to 500GB on my ThinkPad T60 and everything was fine with my original 2 distros. fdisk -l listed with no errors. I installed 5 new distros including OpenSuse 11.3 Suse works fine but now: # fdisk -l now reads:
Disk /dev/sda: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System /dev/sda1 * 1 6374 51196288+ 7 HPFS/NTFS Partition 1 does not end on cylinder boundary. /dev/sda2 6374 7167 6365520 c W95 FAT32 (LBA) Partition 2 does not end on cylinder boundary. /dev/sda3 7167 8670 12073320 c W95 FAT32 (LBA) Partition 3 does not end on cylinder boundary. /dev/sda4 8670 60802 418751369+ f W95 Ext'd (LBA) /dev/sda5 8670 8798 1028128+ 82 Linux swap / Solaris /dev/sda6 8798 13897 40960048+ 83 Linux /dev/sda7 13897 18996 40960048+ 83 Linux /dev/sda8 18996 19379 3076888+ 83 Linux /dev/sda9 19379 23204 30723808+ 83 Linux /dev/sda10 23204 27029 30723808+ 83 Linux /dev/sda11 27030 27794 6144831 83 Linux /dev/sda12 27795 28559 6144831 83 Linux /dev/sda13 28560 29324 6144831 83 Linux
sda6, sda7, sda8, and sda9 end at cylinder and the next partition starts at same cylinder as the previous cylinder. The next partition should start at the next cylinder as sda10,sda11,sda12 and sda13.
How can I correct this? Does testdisk correct this, is it safe to use?
jozien
I doubt that you have a problem. Those are all calculated values; Linux does not use CHS. Partition boundaries are logical, not physical. I have a disk like yours, where the primaries were created with Windows and the logicals all with Linux. SuSE's Partitioner sees all the partitions with a 1 cylinder ending/starting offset. By contrast, fdisk sees the Windows created partitions with the first two ending/starting on +1 cylinder while it sees the second/third as ending/starting on the same cylinder. Windows, depending on the version, will write to the table using DOS CHS values or it will use LBA calculated values ignoring CHS (as Linux does). I suggest reading the fdisk man page as it discusses this in a bit more detail, and the cfdisk (which is more reliable than fdisk) man page as well. The short of it is that it is possible for there to be minor variations in how the table is reported, depending not only on OS but even which tool is being used; this does not necessarily indicate a problem (although that can arise when manipulating a partition table entry with a different OS than what was used to initially create that entry). Manipulating these table values manually is extremely high risk. If Linux and Windows are all able to read the partition table and write to their partitions, you are probably fine. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Aug 26, 2010 at 5:10 PM, dwgallien
I just upgraded my 160GB hdd to 500GB on my ThinkPad T60 and everything was fine with my original 2 distros. fdisk -l listed with no errors. I installed 5 new distros including OpenSuse 11.3 Suse works fine but now: # fdisk -l now reads:
Disk /dev/sda: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System /dev/sda1 * 1 6374 51196288+ 7 HPFS/NTFS Partition 1 does not end on cylinder boundary. /dev/sda2 6374 7167 6365520 c W95 FAT32 (LBA) Partition 2 does not end on cylinder boundary. /dev/sda3 7167 8670 12073320 c W95 FAT32 (LBA) Partition 3 does not end on cylinder boundary. /dev/sda4 8670 60802 418751369+ f W95 Ext'd (LBA) /dev/sda5 8670 8798 1028128+ 82 Linux swap / Solaris /dev/sda6 8798 13897 40960048+ 83 Linux /dev/sda7 13897 18996 40960048+ 83 Linux /dev/sda8 18996 19379 3076888+ 83 Linux /dev/sda9 19379 23204 30723808+ 83 Linux /dev/sda10 23204 27029 30723808+ 83 Linux /dev/sda11 27030 27794 6144831 83 Linux /dev/sda12 27795 28559 6144831 83 Linux /dev/sda13 28560 29324 6144831 83 Linux
sda6, sda7, sda8, and sda9 end at cylinder and the next partition starts at same cylinder as the previous cylinder. The next partition should start at the next cylinder as sda10,sda11,sda12 and sda13.
How can I correct this? Does testdisk correct this, is it safe to use?
jozien
I doubt that you have a problem. Those are all calculated values; Linux does not use CHS. Partition boundaries are logical, not physical. I have a disk like yours, where the primaries were created with Windows and the logicals all with Linux. SuSE's Partitioner sees all the partitions with a 1 cylinder ending/starting offset. By contrast, fdisk sees the Windows created partitions with the first two ending/starting on +1 cylinder while it sees the second/third as ending/starting on the same cylinder. Windows, depending on the version, will write to the table using DOS CHS values or it will use LBA calculated values ignoring CHS (as Linux does). I suggest reading the fdisk man page as it discusses this in a bit more detail, and the cfdisk (which is more reliable than fdisk) man page as well. The short of it is that it is possible for there to be minor variations in how the table is reported, depending not only on OS but even which tool is being used; this does not necessarily indicate a problem (although that can arise when manipulating a partition table entry with a different OS than what was used to initially create that entry). Manipulating these table values manually is extremely high risk. If Linux and Windows are all able to read the partition table and write to their partitions, you are probably fine. --
I agree. I'm certain Linux and Windows Vista and newer could totally care less about cylinder boundaries. I'm fairly confident XP did not care either. OTOH, if you are trying to run Win95 or some such, it may break the way it is. Greg -- Greg Freemyer Head of EDD Tape Extraction and Processing team Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer CNN/TruTV Aired Forensic Imaging Demo - http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retriev... The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Greg Freemyer wrote:
I agree. I'm certain Linux and Windows Vista and newer could totally care less about cylinder boundaries.
There is an issue with newer drives that use 4 KB sectors. With these, the sectors get mapped into a series of eight 512 B sectors, which the operating system sees. You'll want the partitions to start on the 4K sector boundaries, for performance reasons. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* dwgallien (dwgallien@gmail.com) [20100826 23:10]:
Windows, depending on the version, will write to the table using DOS CHS values or it will use LBA calculated values ignoring CHS (as Linux does).
It's simpler than that. All DOS based Windows versions, i.e. up to Win ME will boot DOS first so they will use CHS based addressing and thus need those synthetic values to be correct. Anything later uses LBA and will ignore CHS values. Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* dwgallien (dwgallien@gmail.com) [20100826 23:10]:
Windows, depending on the version, will write to the table using DOS CHS values or it will use LBA calculated values ignoring CHS (as Linux does).
It's simpler than that. All DOS based Windows versions, i.e. up to Win ME will boot DOS first so they will use CHS based addressing and thus need those synthetic values to be correct. Anything later uses LBA and will ignore CHS values.
Philipp
That is what I was referring to. My memory is sketchy on this, but IIRC XP at release still used CHS and it was SP1 that switched to LBA (therefore requiring XP to support both methods with LBA the default). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* dwgallien (dwgallien@gmail.com) [20100827 16:14]:
My memory is sketchy on this, but IIRC XP at release still used CHS and it was SP1 that switched to LBA (therefore requiring XP to support both methods with LBA the default).
My knowledge there is zero, so I can't comment on it. Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
dwgallien -
Greg Freemyer -
James Knott -
Joe Zien -
Philipp Thomas