Partition does not start on physical sector boundary?
I've one HD on my laptop, with two partitions (one ext3 with Ubuntu 12.04 installed and one swap).
fdisk is giving me a Partition 1 does not start on physical sector boundary warning. What is the cause and do I need to fix it? If so, how?
This is sudo fdisk -l:
Disk /dev/sda: 750.2 GB, 750156374016 bytes
255 testine, 63 settori/tracce, 91201 cilindri, totale 1465149168 settori
Unità = settori di 1 * 512 = 512 byte
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Identificativo disco: 0x5a25087f
Dispositivo Boot Start End Blocks Id System
/dev/sda1 * 63 1448577023 724288480+ 83 Linux
Partition 1 does not start on physical sector boundary.
/dev/sda2 1448577024 1465147391 8285184 82 Linux swap / Solaris
This is sudo lshw related result:
*-disk
description: ATA Disk
product: WDC WD7500BPKT-0
vendor: Western Digital
physical id: 0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: 01.0
serial: WD-WX21CC1T0847
size: 698GiB (750GB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=5a25087f
*-volume:0
description: EXT3 volume
vendor: Linux
physical id: 1
bus info: scsi@0:0.0.0,1
logical name: /dev/sda1
logical name: /
version: 1.0
serial: cc5c562a-bc59-4a37-b589-805b27b2cbd7
size: 690GiB
capacity: 690GiB
capabilities: primary bootable journaled extended_attributes large_files recover ext3 ext2 initialized
configuration: created=2010-02-27 09:18:28 filesystem=ext3 modified=2012-06-23 18:33:59 mount.fstype=ext3 mount.options=rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered mounted=2012-06-28 00:20:47 state=mounted
*-volume:1
description: Linux swap volume
physical id: 2
bus info: scsi@0:0.0.0,2
logical name: /dev/sda2
version: 1
serial: 16a7fee0-be9e-4e34-9dc3-28f4eeb61bf6
size: 8091MiB
capacity: 8091MiB
capabilities: primary nofs swap initialized
configuration: filesystem=swap pagesize=4096
These are related /etc/fstab lines:
UUID=cc5c562a-bc59-4a37-b589-805b27b2cbd7 / ext3 errors=remount-ro,user_xattr 0 1
UUID=16a7fee0-be9e-4e34-9dc3-28f4eeb61bf6 none swap sw 0 0
partitioning hard-drive gparted format
add a comment |
I've one HD on my laptop, with two partitions (one ext3 with Ubuntu 12.04 installed and one swap).
fdisk is giving me a Partition 1 does not start on physical sector boundary warning. What is the cause and do I need to fix it? If so, how?
This is sudo fdisk -l:
Disk /dev/sda: 750.2 GB, 750156374016 bytes
255 testine, 63 settori/tracce, 91201 cilindri, totale 1465149168 settori
Unità = settori di 1 * 512 = 512 byte
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Identificativo disco: 0x5a25087f
Dispositivo Boot Start End Blocks Id System
/dev/sda1 * 63 1448577023 724288480+ 83 Linux
Partition 1 does not start on physical sector boundary.
/dev/sda2 1448577024 1465147391 8285184 82 Linux swap / Solaris
This is sudo lshw related result:
*-disk
description: ATA Disk
product: WDC WD7500BPKT-0
vendor: Western Digital
physical id: 0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: 01.0
serial: WD-WX21CC1T0847
size: 698GiB (750GB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=5a25087f
*-volume:0
description: EXT3 volume
vendor: Linux
physical id: 1
bus info: scsi@0:0.0.0,1
logical name: /dev/sda1
logical name: /
version: 1.0
serial: cc5c562a-bc59-4a37-b589-805b27b2cbd7
size: 690GiB
capacity: 690GiB
capabilities: primary bootable journaled extended_attributes large_files recover ext3 ext2 initialized
configuration: created=2010-02-27 09:18:28 filesystem=ext3 modified=2012-06-23 18:33:59 mount.fstype=ext3 mount.options=rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered mounted=2012-06-28 00:20:47 state=mounted
*-volume:1
description: Linux swap volume
physical id: 2
bus info: scsi@0:0.0.0,2
logical name: /dev/sda2
version: 1
serial: 16a7fee0-be9e-4e34-9dc3-28f4eeb61bf6
size: 8091MiB
capacity: 8091MiB
capabilities: primary nofs swap initialized
configuration: filesystem=swap pagesize=4096
These are related /etc/fstab lines:
UUID=cc5c562a-bc59-4a37-b589-805b27b2cbd7 / ext3 errors=remount-ro,user_xattr 0 1
UUID=16a7fee0-be9e-4e34-9dc3-28f4eeb61bf6 none swap sw 0 0
partitioning hard-drive gparted format
add a comment |
I've one HD on my laptop, with two partitions (one ext3 with Ubuntu 12.04 installed and one swap).
fdisk is giving me a Partition 1 does not start on physical sector boundary warning. What is the cause and do I need to fix it? If so, how?
This is sudo fdisk -l:
Disk /dev/sda: 750.2 GB, 750156374016 bytes
255 testine, 63 settori/tracce, 91201 cilindri, totale 1465149168 settori
Unità = settori di 1 * 512 = 512 byte
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Identificativo disco: 0x5a25087f
Dispositivo Boot Start End Blocks Id System
/dev/sda1 * 63 1448577023 724288480+ 83 Linux
Partition 1 does not start on physical sector boundary.
/dev/sda2 1448577024 1465147391 8285184 82 Linux swap / Solaris
This is sudo lshw related result:
*-disk
description: ATA Disk
product: WDC WD7500BPKT-0
vendor: Western Digital
physical id: 0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: 01.0
serial: WD-WX21CC1T0847
size: 698GiB (750GB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=5a25087f
*-volume:0
description: EXT3 volume
vendor: Linux
physical id: 1
bus info: scsi@0:0.0.0,1
logical name: /dev/sda1
logical name: /
version: 1.0
serial: cc5c562a-bc59-4a37-b589-805b27b2cbd7
size: 690GiB
capacity: 690GiB
capabilities: primary bootable journaled extended_attributes large_files recover ext3 ext2 initialized
configuration: created=2010-02-27 09:18:28 filesystem=ext3 modified=2012-06-23 18:33:59 mount.fstype=ext3 mount.options=rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered mounted=2012-06-28 00:20:47 state=mounted
*-volume:1
description: Linux swap volume
physical id: 2
bus info: scsi@0:0.0.0,2
logical name: /dev/sda2
version: 1
serial: 16a7fee0-be9e-4e34-9dc3-28f4eeb61bf6
size: 8091MiB
capacity: 8091MiB
capabilities: primary nofs swap initialized
configuration: filesystem=swap pagesize=4096
These are related /etc/fstab lines:
UUID=cc5c562a-bc59-4a37-b589-805b27b2cbd7 / ext3 errors=remount-ro,user_xattr 0 1
UUID=16a7fee0-be9e-4e34-9dc3-28f4eeb61bf6 none swap sw 0 0
partitioning hard-drive gparted format
I've one HD on my laptop, with two partitions (one ext3 with Ubuntu 12.04 installed and one swap).
fdisk is giving me a Partition 1 does not start on physical sector boundary warning. What is the cause and do I need to fix it? If so, how?
This is sudo fdisk -l:
Disk /dev/sda: 750.2 GB, 750156374016 bytes
255 testine, 63 settori/tracce, 91201 cilindri, totale 1465149168 settori
Unità = settori di 1 * 512 = 512 byte
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Identificativo disco: 0x5a25087f
Dispositivo Boot Start End Blocks Id System
/dev/sda1 * 63 1448577023 724288480+ 83 Linux
Partition 1 does not start on physical sector boundary.
/dev/sda2 1448577024 1465147391 8285184 82 Linux swap / Solaris
This is sudo lshw related result:
*-disk
description: ATA Disk
product: WDC WD7500BPKT-0
vendor: Western Digital
physical id: 0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: 01.0
serial: WD-WX21CC1T0847
size: 698GiB (750GB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=5a25087f
*-volume:0
description: EXT3 volume
vendor: Linux
physical id: 1
bus info: scsi@0:0.0.0,1
logical name: /dev/sda1
logical name: /
version: 1.0
serial: cc5c562a-bc59-4a37-b589-805b27b2cbd7
size: 690GiB
capacity: 690GiB
capabilities: primary bootable journaled extended_attributes large_files recover ext3 ext2 initialized
configuration: created=2010-02-27 09:18:28 filesystem=ext3 modified=2012-06-23 18:33:59 mount.fstype=ext3 mount.options=rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered mounted=2012-06-28 00:20:47 state=mounted
*-volume:1
description: Linux swap volume
physical id: 2
bus info: scsi@0:0.0.0,2
logical name: /dev/sda2
version: 1
serial: 16a7fee0-be9e-4e34-9dc3-28f4eeb61bf6
size: 8091MiB
capacity: 8091MiB
capabilities: primary nofs swap initialized
configuration: filesystem=swap pagesize=4096
These are related /etc/fstab lines:
UUID=cc5c562a-bc59-4a37-b589-805b27b2cbd7 / ext3 errors=remount-ro,user_xattr 0 1
UUID=16a7fee0-be9e-4e34-9dc3-28f4eeb61bf6 none swap sw 0 0
partitioning hard-drive gparted format
partitioning hard-drive gparted format
edited Jun 28 '12 at 6:06
ish
116k30267293
116k30267293
asked Jun 28 '12 at 5:01
jasminesjasmines
6,376136295
6,376136295
add a comment |
add a comment |
6 Answers
6
active
oldest
votes
Your hard disk has Advanced Format 4096-byte sectors to which the partition is not perfectly aligned
This line explains the warning:
Sector size (logical/physical): 512 bytes / 4096 bytes
- Your hard disk is one of the newer models which uses the Advanced Format of 4096 bytes per physical sector instead of the older 512 bytes/sector.
- These HDDs can still provide a "legacy" emulation of 512 bytes/sector, which is why you see the logical sector size as 512.
- In fact,
lshwshows it's a Western Digital drive, the first company to switch to AF. They have an extensive page with lots of information on it, which you may wish to look at.
Thus, the warning occurs because partition 1 starts at logical sector 63 = byte 32256, a number not divisible by 4096; in fact it's near the end of the 7th physical sector (position 7.875 to be exact :)
Should you fix it? If so, how? [always backup!]
In theory this sort of partitioning may affect read/write IO rates somewhat, depending on your drive's firmware. If you are happy with the performance now, ignore the warning, and no need to do anything. If not, backup all important data first, and then use Gparted to move the partition so that it starts at 4096-byte sector; setting the start boundary at 1 MiB is an easy way to do it.
- Technically, you can set the start to any logical sector which is a multiple of 8, e.g. 64 is good, 256 is good, etc., but 63, 255... are not.
add a comment |
For your new HDD, first create partitions using gparted as per your wish.
Then, access your HDD using sudo fdisk device_name.
m command in fdisk will print help menu.
npcompete@npcompete-desktop:~$ sudo fdisk /dev/sda
The device presents a logical sector size that is smaller than
the physical sector size. Aligning to a physical sector (or optimal
I/O) size boundary is recommended, or performance may be impacted.
Command (m for help): p
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x0008e009
Device Boot Start End Blocks Id System
/dev/sda1 2048 209717247 104857600 83 Linux
/dev/sda2 209717248 1953525167 871903960 5 Extended
/dev/sda5 600349113 795667319 97659103+ 83 Linux
Partition 5 does not start on physical sector boundary.
/dev/sda6 795667383 990985589 97659103+ 83 Linux
Partition 6 does not start on physical sector boundary.
/dev/sda7 990985653 1953520064 481267206 83 Linux
Partition 7 does not start on physical sector boundary.
/dev/sda8 209719296 600349112 195314908+ 83 Linux
Partition table entries are not in disk order
Command (m for help): d
Partition number (1-8): 5
Command (m for help): p
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x0008e009
Device Boot Start End Blocks Id System
/dev/sda1 2048 209717247 104857600 83 Linux
/dev/sda2 209717248 1953525167 871903960 5 Extended
/dev/sda5 795667383 990985589 97659103+ 83 Linux
Partition 5 does not start on physical sector boundary.
/dev/sda6 990985653 1953520064 481267206 83 Linux
Partition 6 does not start on physical sector boundary.
/dev/sda7 209719296 600349112 195314908+ 83 Linux
Partition table entries are not in disk order
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
npcompete@npcompete-desktop:~$ sudo fdisk /dev/sda
The device presents a logical sector size that is smaller than
the physical sector size. Aligning to a physical sector (or optimal
I/O) size boundary is recommended, or performance may be impacted.
Command (m for help): n
Partition type:
p primary (1 primary, 1 extended, 2 free)
l logical (numbered from 5)
Select (default p): l
Adding logical partition 8
First sector (600351161-1953525167, default 600352768):
Using default value 600352768
Last sector, +sectors or +size{K,M,G} (600352768-795667382, default 795667382):
Using default value 795667382
Command (m for help): p
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x0008e009
Device Boot Start End Blocks Id System
/dev/sda1 2048 209717247 104857600 83 Linux
/dev/sda2 209717248 1953525167 871903960 5 Extended
/dev/sda5 795667383 990985589 97659103+ 83 Linux
Partition 5 does not start on physical sector boundary.
/dev/sda6 990985653 1953520064 481267206 83 Linux
Partition 6 does not start on physical sector boundary.
/dev/sda7 209719296 600349112 195314908+ 83 Linux
/dev/sda8 600352768 795667382 97657307+ 83 Linux
Partition table entries are not in disk order
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
Now delete the partition which gives warning using d option in fdisk.
First Command d, then the partition number (mentioned in the warning).
Now write the changes to the disk using w command. It will exit from the fdisk.
Second time access your HDD using sudo fdisk device_name.
Now create a new partition using the free space(previously we have deleted a partition, that will be the free space or unallocated space) using n command in fdisk.
In New partition command don't enter any value for First and Last Sector, just press Enter. it will take the default value.
Now write the changes to the disk using w command. It will exit from the fdisk.
Do the above steps for all the partitions. After finishing this format your newly created partitions, using gparted. (That's what I did worked for me. No warnings in fdisk -l output.)
add a comment |
As pointed out by izx:
your hard disk has Advanced Format 4096-byte sectors to which the
partition is not perfectly aligned.
The advanced format specification and its impact on user-side hard drive partitioning practices is explained nicely by this article.
To fix this issue you must backup your data and then either:
- Resize the erroneously sized partition to the proper size.
- Delete the erroneously sized partition and create a new partition of the proper size.
To accomplish this using the graphical hard-drive partitioning software that is called GParted then you can:
Launch the Gparted application with super-user privileges; exercise caution!
gksudo gparted
Select the storage device containing the erroneously sized partition from the pull-down menu in the upper right hand corner of the GParted menu.
- Select the erroneously-sized partition by clicking on it in the rectangular partition map.
- Now you may choose to delete and create a new partition or you may choose to resize the existing partition. Regardless of your choice you will reach a menu that allows you to set the size of the partition. You must clear the "Round to cylinders" checkbox and set the size of the free space preceding to 1MiB. It will look similar to
.
add a comment |
By switching the "u" units. The default sector size will show up when you create the partition.
If you are starting to partition a new disk and you get this error, you can.
- create a partion with the defaut.
- n,p,1,Enter, Enter
- Display and get the partition error message. "p".
- switch units "u"
- delete the partition. "d"
- Now create again. this time the defaults will show the correct sector. (in my case it was 1024).
Command (m for help): p
Disk /dev/sdb: 599.9 GB, 599932844032 bytes
255 heads, 63 sectors/track, 72937 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 524288 bytes
Disk identifier: 0x2016bdc5
Device Boot Start End Blocks Id System
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-72937, default 1): 1
Last cylinder, +cylinders or +size{K,M,G} (1-72937, default 72937):
Using default value 72937
Command (m for help): p
Disk /dev/sdb: 599.9 GB, 599932844032 bytes
255 heads, 63 sectors/track, 72937 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 524288 bytes
Disk identifier: 0x2016bdc5
Device Boot Start End Blocks Id System
/dev/sdb1 1 72937 585866421 83 Linux
Partition 1 does not start on physical sector boundary.
Command (m for help): u
Changing display/entry units to sectors
Command (m for help): p
Disk /dev/sdb: 599.9 GB, 599932844032 bytes
255 heads, 63 sectors/track, 72937 cylinders, total 1171743836 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 524288 bytes
Disk identifier: 0x2016bdc5
Device Boot Start End Blocks Id System
/dev/sdb1 63 1171732904 585866421 83 Linux
Partition 1 does not start on physical sector boundary.
Command (m for help): d
Selected partition 1
Command (m for help): p
Disk /dev/sdb: 599.9 GB, 599932844032 bytes
255 heads, 63 sectors/track, 72937 cylinders, total 1171743836 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 524288 bytes
Disk identifier: 0x2016bdc5
Device Boot Start End Blocks Id System
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 8
Value out of range.
Partition number (1-4): 1
First sector (63-1171743835, default 1024):
Using default value 1024
Last sector, +sectors or +size{K,M,G} (1024-1171743835, default 1171743835):
Using default value 1171743835
Command (m for help): p
Disk /dev/sdb: 599.9 GB, 599932844032 bytes
255 heads, 63 sectors/track, 72937 cylinders, total 1171743836 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 524288 bytes
Disk identifier: 0x2016bdc5
Device Boot Start End Blocks Id System
/dev/sdb1 1024 1171743835 585871406 83 Linux
Command (m for help): w
The partition table has been altered!
1
I tried the approaches from other answers, but switching to 'u' mode was the only one that worked for me.
– JosephH
Nov 24 '14 at 11:12
1
Of all the answers, this is the one that worked for me as well.
– Avanst
Jan 10 '15 at 4:26
add a comment |
just delete all partition and do this in fdisk
Command (m for help): c
DOS Compatibility flag is not set
Command (m for help): u
Changing display/entry units to sectors
New contributor
Abdallah Mousa is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
If you have a windows dual boot you can use MiniTool Partition Wizard. This thing has saved my ass multiple times. Just right click the partition and click align. Don't forget to click apply.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f156994%2fpartition-does-not-start-on-physical-sector-boundary%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
6 Answers
6
active
oldest
votes
6 Answers
6
active
oldest
votes
active
oldest
votes
active
oldest
votes
Your hard disk has Advanced Format 4096-byte sectors to which the partition is not perfectly aligned
This line explains the warning:
Sector size (logical/physical): 512 bytes / 4096 bytes
- Your hard disk is one of the newer models which uses the Advanced Format of 4096 bytes per physical sector instead of the older 512 bytes/sector.
- These HDDs can still provide a "legacy" emulation of 512 bytes/sector, which is why you see the logical sector size as 512.
- In fact,
lshwshows it's a Western Digital drive, the first company to switch to AF. They have an extensive page with lots of information on it, which you may wish to look at.
Thus, the warning occurs because partition 1 starts at logical sector 63 = byte 32256, a number not divisible by 4096; in fact it's near the end of the 7th physical sector (position 7.875 to be exact :)
Should you fix it? If so, how? [always backup!]
In theory this sort of partitioning may affect read/write IO rates somewhat, depending on your drive's firmware. If you are happy with the performance now, ignore the warning, and no need to do anything. If not, backup all important data first, and then use Gparted to move the partition so that it starts at 4096-byte sector; setting the start boundary at 1 MiB is an easy way to do it.
- Technically, you can set the start to any logical sector which is a multiple of 8, e.g. 64 is good, 256 is good, etc., but 63, 255... are not.
add a comment |
Your hard disk has Advanced Format 4096-byte sectors to which the partition is not perfectly aligned
This line explains the warning:
Sector size (logical/physical): 512 bytes / 4096 bytes
- Your hard disk is one of the newer models which uses the Advanced Format of 4096 bytes per physical sector instead of the older 512 bytes/sector.
- These HDDs can still provide a "legacy" emulation of 512 bytes/sector, which is why you see the logical sector size as 512.
- In fact,
lshwshows it's a Western Digital drive, the first company to switch to AF. They have an extensive page with lots of information on it, which you may wish to look at.
Thus, the warning occurs because partition 1 starts at logical sector 63 = byte 32256, a number not divisible by 4096; in fact it's near the end of the 7th physical sector (position 7.875 to be exact :)
Should you fix it? If so, how? [always backup!]
In theory this sort of partitioning may affect read/write IO rates somewhat, depending on your drive's firmware. If you are happy with the performance now, ignore the warning, and no need to do anything. If not, backup all important data first, and then use Gparted to move the partition so that it starts at 4096-byte sector; setting the start boundary at 1 MiB is an easy way to do it.
- Technically, you can set the start to any logical sector which is a multiple of 8, e.g. 64 is good, 256 is good, etc., but 63, 255... are not.
add a comment |
Your hard disk has Advanced Format 4096-byte sectors to which the partition is not perfectly aligned
This line explains the warning:
Sector size (logical/physical): 512 bytes / 4096 bytes
- Your hard disk is one of the newer models which uses the Advanced Format of 4096 bytes per physical sector instead of the older 512 bytes/sector.
- These HDDs can still provide a "legacy" emulation of 512 bytes/sector, which is why you see the logical sector size as 512.
- In fact,
lshwshows it's a Western Digital drive, the first company to switch to AF. They have an extensive page with lots of information on it, which you may wish to look at.
Thus, the warning occurs because partition 1 starts at logical sector 63 = byte 32256, a number not divisible by 4096; in fact it's near the end of the 7th physical sector (position 7.875 to be exact :)
Should you fix it? If so, how? [always backup!]
In theory this sort of partitioning may affect read/write IO rates somewhat, depending on your drive's firmware. If you are happy with the performance now, ignore the warning, and no need to do anything. If not, backup all important data first, and then use Gparted to move the partition so that it starts at 4096-byte sector; setting the start boundary at 1 MiB is an easy way to do it.
- Technically, you can set the start to any logical sector which is a multiple of 8, e.g. 64 is good, 256 is good, etc., but 63, 255... are not.
Your hard disk has Advanced Format 4096-byte sectors to which the partition is not perfectly aligned
This line explains the warning:
Sector size (logical/physical): 512 bytes / 4096 bytes
- Your hard disk is one of the newer models which uses the Advanced Format of 4096 bytes per physical sector instead of the older 512 bytes/sector.
- These HDDs can still provide a "legacy" emulation of 512 bytes/sector, which is why you see the logical sector size as 512.
- In fact,
lshwshows it's a Western Digital drive, the first company to switch to AF. They have an extensive page with lots of information on it, which you may wish to look at.
Thus, the warning occurs because partition 1 starts at logical sector 63 = byte 32256, a number not divisible by 4096; in fact it's near the end of the 7th physical sector (position 7.875 to be exact :)
Should you fix it? If so, how? [always backup!]
In theory this sort of partitioning may affect read/write IO rates somewhat, depending on your drive's firmware. If you are happy with the performance now, ignore the warning, and no need to do anything. If not, backup all important data first, and then use Gparted to move the partition so that it starts at 4096-byte sector; setting the start boundary at 1 MiB is an easy way to do it.
- Technically, you can set the start to any logical sector which is a multiple of 8, e.g. 64 is good, 256 is good, etc., but 63, 255... are not.
edited Nov 7 '18 at 20:50
Tom Brossman
8,9281149114
8,9281149114
answered Jun 28 '12 at 5:24
ishish
116k30267293
116k30267293
add a comment |
add a comment |
For your new HDD, first create partitions using gparted as per your wish.
Then, access your HDD using sudo fdisk device_name.
m command in fdisk will print help menu.
npcompete@npcompete-desktop:~$ sudo fdisk /dev/sda
The device presents a logical sector size that is smaller than
the physical sector size. Aligning to a physical sector (or optimal
I/O) size boundary is recommended, or performance may be impacted.
Command (m for help): p
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x0008e009
Device Boot Start End Blocks Id System
/dev/sda1 2048 209717247 104857600 83 Linux
/dev/sda2 209717248 1953525167 871903960 5 Extended
/dev/sda5 600349113 795667319 97659103+ 83 Linux
Partition 5 does not start on physical sector boundary.
/dev/sda6 795667383 990985589 97659103+ 83 Linux
Partition 6 does not start on physical sector boundary.
/dev/sda7 990985653 1953520064 481267206 83 Linux
Partition 7 does not start on physical sector boundary.
/dev/sda8 209719296 600349112 195314908+ 83 Linux
Partition table entries are not in disk order
Command (m for help): d
Partition number (1-8): 5
Command (m for help): p
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x0008e009
Device Boot Start End Blocks Id System
/dev/sda1 2048 209717247 104857600 83 Linux
/dev/sda2 209717248 1953525167 871903960 5 Extended
/dev/sda5 795667383 990985589 97659103+ 83 Linux
Partition 5 does not start on physical sector boundary.
/dev/sda6 990985653 1953520064 481267206 83 Linux
Partition 6 does not start on physical sector boundary.
/dev/sda7 209719296 600349112 195314908+ 83 Linux
Partition table entries are not in disk order
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
npcompete@npcompete-desktop:~$ sudo fdisk /dev/sda
The device presents a logical sector size that is smaller than
the physical sector size. Aligning to a physical sector (or optimal
I/O) size boundary is recommended, or performance may be impacted.
Command (m for help): n
Partition type:
p primary (1 primary, 1 extended, 2 free)
l logical (numbered from 5)
Select (default p): l
Adding logical partition 8
First sector (600351161-1953525167, default 600352768):
Using default value 600352768
Last sector, +sectors or +size{K,M,G} (600352768-795667382, default 795667382):
Using default value 795667382
Command (m for help): p
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x0008e009
Device Boot Start End Blocks Id System
/dev/sda1 2048 209717247 104857600 83 Linux
/dev/sda2 209717248 1953525167 871903960 5 Extended
/dev/sda5 795667383 990985589 97659103+ 83 Linux
Partition 5 does not start on physical sector boundary.
/dev/sda6 990985653 1953520064 481267206 83 Linux
Partition 6 does not start on physical sector boundary.
/dev/sda7 209719296 600349112 195314908+ 83 Linux
/dev/sda8 600352768 795667382 97657307+ 83 Linux
Partition table entries are not in disk order
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
Now delete the partition which gives warning using d option in fdisk.
First Command d, then the partition number (mentioned in the warning).
Now write the changes to the disk using w command. It will exit from the fdisk.
Second time access your HDD using sudo fdisk device_name.
Now create a new partition using the free space(previously we have deleted a partition, that will be the free space or unallocated space) using n command in fdisk.
In New partition command don't enter any value for First and Last Sector, just press Enter. it will take the default value.
Now write the changes to the disk using w command. It will exit from the fdisk.
Do the above steps for all the partitions. After finishing this format your newly created partitions, using gparted. (That's what I did worked for me. No warnings in fdisk -l output.)
add a comment |
For your new HDD, first create partitions using gparted as per your wish.
Then, access your HDD using sudo fdisk device_name.
m command in fdisk will print help menu.
npcompete@npcompete-desktop:~$ sudo fdisk /dev/sda
The device presents a logical sector size that is smaller than
the physical sector size. Aligning to a physical sector (or optimal
I/O) size boundary is recommended, or performance may be impacted.
Command (m for help): p
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x0008e009
Device Boot Start End Blocks Id System
/dev/sda1 2048 209717247 104857600 83 Linux
/dev/sda2 209717248 1953525167 871903960 5 Extended
/dev/sda5 600349113 795667319 97659103+ 83 Linux
Partition 5 does not start on physical sector boundary.
/dev/sda6 795667383 990985589 97659103+ 83 Linux
Partition 6 does not start on physical sector boundary.
/dev/sda7 990985653 1953520064 481267206 83 Linux
Partition 7 does not start on physical sector boundary.
/dev/sda8 209719296 600349112 195314908+ 83 Linux
Partition table entries are not in disk order
Command (m for help): d
Partition number (1-8): 5
Command (m for help): p
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x0008e009
Device Boot Start End Blocks Id System
/dev/sda1 2048 209717247 104857600 83 Linux
/dev/sda2 209717248 1953525167 871903960 5 Extended
/dev/sda5 795667383 990985589 97659103+ 83 Linux
Partition 5 does not start on physical sector boundary.
/dev/sda6 990985653 1953520064 481267206 83 Linux
Partition 6 does not start on physical sector boundary.
/dev/sda7 209719296 600349112 195314908+ 83 Linux
Partition table entries are not in disk order
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
npcompete@npcompete-desktop:~$ sudo fdisk /dev/sda
The device presents a logical sector size that is smaller than
the physical sector size. Aligning to a physical sector (or optimal
I/O) size boundary is recommended, or performance may be impacted.
Command (m for help): n
Partition type:
p primary (1 primary, 1 extended, 2 free)
l logical (numbered from 5)
Select (default p): l
Adding logical partition 8
First sector (600351161-1953525167, default 600352768):
Using default value 600352768
Last sector, +sectors or +size{K,M,G} (600352768-795667382, default 795667382):
Using default value 795667382
Command (m for help): p
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x0008e009
Device Boot Start End Blocks Id System
/dev/sda1 2048 209717247 104857600 83 Linux
/dev/sda2 209717248 1953525167 871903960 5 Extended
/dev/sda5 795667383 990985589 97659103+ 83 Linux
Partition 5 does not start on physical sector boundary.
/dev/sda6 990985653 1953520064 481267206 83 Linux
Partition 6 does not start on physical sector boundary.
/dev/sda7 209719296 600349112 195314908+ 83 Linux
/dev/sda8 600352768 795667382 97657307+ 83 Linux
Partition table entries are not in disk order
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
Now delete the partition which gives warning using d option in fdisk.
First Command d, then the partition number (mentioned in the warning).
Now write the changes to the disk using w command. It will exit from the fdisk.
Second time access your HDD using sudo fdisk device_name.
Now create a new partition using the free space(previously we have deleted a partition, that will be the free space or unallocated space) using n command in fdisk.
In New partition command don't enter any value for First and Last Sector, just press Enter. it will take the default value.
Now write the changes to the disk using w command. It will exit from the fdisk.
Do the above steps for all the partitions. After finishing this format your newly created partitions, using gparted. (That's what I did worked for me. No warnings in fdisk -l output.)
add a comment |
For your new HDD, first create partitions using gparted as per your wish.
Then, access your HDD using sudo fdisk device_name.
m command in fdisk will print help menu.
npcompete@npcompete-desktop:~$ sudo fdisk /dev/sda
The device presents a logical sector size that is smaller than
the physical sector size. Aligning to a physical sector (or optimal
I/O) size boundary is recommended, or performance may be impacted.
Command (m for help): p
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x0008e009
Device Boot Start End Blocks Id System
/dev/sda1 2048 209717247 104857600 83 Linux
/dev/sda2 209717248 1953525167 871903960 5 Extended
/dev/sda5 600349113 795667319 97659103+ 83 Linux
Partition 5 does not start on physical sector boundary.
/dev/sda6 795667383 990985589 97659103+ 83 Linux
Partition 6 does not start on physical sector boundary.
/dev/sda7 990985653 1953520064 481267206 83 Linux
Partition 7 does not start on physical sector boundary.
/dev/sda8 209719296 600349112 195314908+ 83 Linux
Partition table entries are not in disk order
Command (m for help): d
Partition number (1-8): 5
Command (m for help): p
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x0008e009
Device Boot Start End Blocks Id System
/dev/sda1 2048 209717247 104857600 83 Linux
/dev/sda2 209717248 1953525167 871903960 5 Extended
/dev/sda5 795667383 990985589 97659103+ 83 Linux
Partition 5 does not start on physical sector boundary.
/dev/sda6 990985653 1953520064 481267206 83 Linux
Partition 6 does not start on physical sector boundary.
/dev/sda7 209719296 600349112 195314908+ 83 Linux
Partition table entries are not in disk order
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
npcompete@npcompete-desktop:~$ sudo fdisk /dev/sda
The device presents a logical sector size that is smaller than
the physical sector size. Aligning to a physical sector (or optimal
I/O) size boundary is recommended, or performance may be impacted.
Command (m for help): n
Partition type:
p primary (1 primary, 1 extended, 2 free)
l logical (numbered from 5)
Select (default p): l
Adding logical partition 8
First sector (600351161-1953525167, default 600352768):
Using default value 600352768
Last sector, +sectors or +size{K,M,G} (600352768-795667382, default 795667382):
Using default value 795667382
Command (m for help): p
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x0008e009
Device Boot Start End Blocks Id System
/dev/sda1 2048 209717247 104857600 83 Linux
/dev/sda2 209717248 1953525167 871903960 5 Extended
/dev/sda5 795667383 990985589 97659103+ 83 Linux
Partition 5 does not start on physical sector boundary.
/dev/sda6 990985653 1953520064 481267206 83 Linux
Partition 6 does not start on physical sector boundary.
/dev/sda7 209719296 600349112 195314908+ 83 Linux
/dev/sda8 600352768 795667382 97657307+ 83 Linux
Partition table entries are not in disk order
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
Now delete the partition which gives warning using d option in fdisk.
First Command d, then the partition number (mentioned in the warning).
Now write the changes to the disk using w command. It will exit from the fdisk.
Second time access your HDD using sudo fdisk device_name.
Now create a new partition using the free space(previously we have deleted a partition, that will be the free space or unallocated space) using n command in fdisk.
In New partition command don't enter any value for First and Last Sector, just press Enter. it will take the default value.
Now write the changes to the disk using w command. It will exit from the fdisk.
Do the above steps for all the partitions. After finishing this format your newly created partitions, using gparted. (That's what I did worked for me. No warnings in fdisk -l output.)
For your new HDD, first create partitions using gparted as per your wish.
Then, access your HDD using sudo fdisk device_name.
m command in fdisk will print help menu.
npcompete@npcompete-desktop:~$ sudo fdisk /dev/sda
The device presents a logical sector size that is smaller than
the physical sector size. Aligning to a physical sector (or optimal
I/O) size boundary is recommended, or performance may be impacted.
Command (m for help): p
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x0008e009
Device Boot Start End Blocks Id System
/dev/sda1 2048 209717247 104857600 83 Linux
/dev/sda2 209717248 1953525167 871903960 5 Extended
/dev/sda5 600349113 795667319 97659103+ 83 Linux
Partition 5 does not start on physical sector boundary.
/dev/sda6 795667383 990985589 97659103+ 83 Linux
Partition 6 does not start on physical sector boundary.
/dev/sda7 990985653 1953520064 481267206 83 Linux
Partition 7 does not start on physical sector boundary.
/dev/sda8 209719296 600349112 195314908+ 83 Linux
Partition table entries are not in disk order
Command (m for help): d
Partition number (1-8): 5
Command (m for help): p
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x0008e009
Device Boot Start End Blocks Id System
/dev/sda1 2048 209717247 104857600 83 Linux
/dev/sda2 209717248 1953525167 871903960 5 Extended
/dev/sda5 795667383 990985589 97659103+ 83 Linux
Partition 5 does not start on physical sector boundary.
/dev/sda6 990985653 1953520064 481267206 83 Linux
Partition 6 does not start on physical sector boundary.
/dev/sda7 209719296 600349112 195314908+ 83 Linux
Partition table entries are not in disk order
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
npcompete@npcompete-desktop:~$ sudo fdisk /dev/sda
The device presents a logical sector size that is smaller than
the physical sector size. Aligning to a physical sector (or optimal
I/O) size boundary is recommended, or performance may be impacted.
Command (m for help): n
Partition type:
p primary (1 primary, 1 extended, 2 free)
l logical (numbered from 5)
Select (default p): l
Adding logical partition 8
First sector (600351161-1953525167, default 600352768):
Using default value 600352768
Last sector, +sectors or +size{K,M,G} (600352768-795667382, default 795667382):
Using default value 795667382
Command (m for help): p
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x0008e009
Device Boot Start End Blocks Id System
/dev/sda1 2048 209717247 104857600 83 Linux
/dev/sda2 209717248 1953525167 871903960 5 Extended
/dev/sda5 795667383 990985589 97659103+ 83 Linux
Partition 5 does not start on physical sector boundary.
/dev/sda6 990985653 1953520064 481267206 83 Linux
Partition 6 does not start on physical sector boundary.
/dev/sda7 209719296 600349112 195314908+ 83 Linux
/dev/sda8 600352768 795667382 97657307+ 83 Linux
Partition table entries are not in disk order
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
Now delete the partition which gives warning using d option in fdisk.
First Command d, then the partition number (mentioned in the warning).
Now write the changes to the disk using w command. It will exit from the fdisk.
Second time access your HDD using sudo fdisk device_name.
Now create a new partition using the free space(previously we have deleted a partition, that will be the free space or unallocated space) using n command in fdisk.
In New partition command don't enter any value for First and Last Sector, just press Enter. it will take the default value.
Now write the changes to the disk using w command. It will exit from the fdisk.
Do the above steps for all the partitions. After finishing this format your newly created partitions, using gparted. (That's what I did worked for me. No warnings in fdisk -l output.)
answered Jul 22 '14 at 4:21
ValarpiraiValarpirai
5111
5111
add a comment |
add a comment |
As pointed out by izx:
your hard disk has Advanced Format 4096-byte sectors to which the
partition is not perfectly aligned.
The advanced format specification and its impact on user-side hard drive partitioning practices is explained nicely by this article.
To fix this issue you must backup your data and then either:
- Resize the erroneously sized partition to the proper size.
- Delete the erroneously sized partition and create a new partition of the proper size.
To accomplish this using the graphical hard-drive partitioning software that is called GParted then you can:
Launch the Gparted application with super-user privileges; exercise caution!
gksudo gparted
Select the storage device containing the erroneously sized partition from the pull-down menu in the upper right hand corner of the GParted menu.
- Select the erroneously-sized partition by clicking on it in the rectangular partition map.
- Now you may choose to delete and create a new partition or you may choose to resize the existing partition. Regardless of your choice you will reach a menu that allows you to set the size of the partition. You must clear the "Round to cylinders" checkbox and set the size of the free space preceding to 1MiB. It will look similar to
.
add a comment |
As pointed out by izx:
your hard disk has Advanced Format 4096-byte sectors to which the
partition is not perfectly aligned.
The advanced format specification and its impact on user-side hard drive partitioning practices is explained nicely by this article.
To fix this issue you must backup your data and then either:
- Resize the erroneously sized partition to the proper size.
- Delete the erroneously sized partition and create a new partition of the proper size.
To accomplish this using the graphical hard-drive partitioning software that is called GParted then you can:
Launch the Gparted application with super-user privileges; exercise caution!
gksudo gparted
Select the storage device containing the erroneously sized partition from the pull-down menu in the upper right hand corner of the GParted menu.
- Select the erroneously-sized partition by clicking on it in the rectangular partition map.
- Now you may choose to delete and create a new partition or you may choose to resize the existing partition. Regardless of your choice you will reach a menu that allows you to set the size of the partition. You must clear the "Round to cylinders" checkbox and set the size of the free space preceding to 1MiB. It will look similar to
.
add a comment |
As pointed out by izx:
your hard disk has Advanced Format 4096-byte sectors to which the
partition is not perfectly aligned.
The advanced format specification and its impact on user-side hard drive partitioning practices is explained nicely by this article.
To fix this issue you must backup your data and then either:
- Resize the erroneously sized partition to the proper size.
- Delete the erroneously sized partition and create a new partition of the proper size.
To accomplish this using the graphical hard-drive partitioning software that is called GParted then you can:
Launch the Gparted application with super-user privileges; exercise caution!
gksudo gparted
Select the storage device containing the erroneously sized partition from the pull-down menu in the upper right hand corner of the GParted menu.
- Select the erroneously-sized partition by clicking on it in the rectangular partition map.
- Now you may choose to delete and create a new partition or you may choose to resize the existing partition. Regardless of your choice you will reach a menu that allows you to set the size of the partition. You must clear the "Round to cylinders" checkbox and set the size of the free space preceding to 1MiB. It will look similar to
.
As pointed out by izx:
your hard disk has Advanced Format 4096-byte sectors to which the
partition is not perfectly aligned.
The advanced format specification and its impact on user-side hard drive partitioning practices is explained nicely by this article.
To fix this issue you must backup your data and then either:
- Resize the erroneously sized partition to the proper size.
- Delete the erroneously sized partition and create a new partition of the proper size.
To accomplish this using the graphical hard-drive partitioning software that is called GParted then you can:
Launch the Gparted application with super-user privileges; exercise caution!
gksudo gparted
Select the storage device containing the erroneously sized partition from the pull-down menu in the upper right hand corner of the GParted menu.
- Select the erroneously-sized partition by clicking on it in the rectangular partition map.
- Now you may choose to delete and create a new partition or you may choose to resize the existing partition. Regardless of your choice you will reach a menu that allows you to set the size of the partition. You must clear the "Round to cylinders" checkbox and set the size of the free space preceding to 1MiB. It will look similar to
.
edited Apr 13 '17 at 12:24
Community♦
1
1
answered Mar 17 '13 at 17:49
lb3lb3
611
611
add a comment |
add a comment |
By switching the "u" units. The default sector size will show up when you create the partition.
If you are starting to partition a new disk and you get this error, you can.
- create a partion with the defaut.
- n,p,1,Enter, Enter
- Display and get the partition error message. "p".
- switch units "u"
- delete the partition. "d"
- Now create again. this time the defaults will show the correct sector. (in my case it was 1024).
Command (m for help): p
Disk /dev/sdb: 599.9 GB, 599932844032 bytes
255 heads, 63 sectors/track, 72937 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 524288 bytes
Disk identifier: 0x2016bdc5
Device Boot Start End Blocks Id System
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-72937, default 1): 1
Last cylinder, +cylinders or +size{K,M,G} (1-72937, default 72937):
Using default value 72937
Command (m for help): p
Disk /dev/sdb: 599.9 GB, 599932844032 bytes
255 heads, 63 sectors/track, 72937 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 524288 bytes
Disk identifier: 0x2016bdc5
Device Boot Start End Blocks Id System
/dev/sdb1 1 72937 585866421 83 Linux
Partition 1 does not start on physical sector boundary.
Command (m for help): u
Changing display/entry units to sectors
Command (m for help): p
Disk /dev/sdb: 599.9 GB, 599932844032 bytes
255 heads, 63 sectors/track, 72937 cylinders, total 1171743836 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 524288 bytes
Disk identifier: 0x2016bdc5
Device Boot Start End Blocks Id System
/dev/sdb1 63 1171732904 585866421 83 Linux
Partition 1 does not start on physical sector boundary.
Command (m for help): d
Selected partition 1
Command (m for help): p
Disk /dev/sdb: 599.9 GB, 599932844032 bytes
255 heads, 63 sectors/track, 72937 cylinders, total 1171743836 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 524288 bytes
Disk identifier: 0x2016bdc5
Device Boot Start End Blocks Id System
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 8
Value out of range.
Partition number (1-4): 1
First sector (63-1171743835, default 1024):
Using default value 1024
Last sector, +sectors or +size{K,M,G} (1024-1171743835, default 1171743835):
Using default value 1171743835
Command (m for help): p
Disk /dev/sdb: 599.9 GB, 599932844032 bytes
255 heads, 63 sectors/track, 72937 cylinders, total 1171743836 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 524288 bytes
Disk identifier: 0x2016bdc5
Device Boot Start End Blocks Id System
/dev/sdb1 1024 1171743835 585871406 83 Linux
Command (m for help): w
The partition table has been altered!
1
I tried the approaches from other answers, but switching to 'u' mode was the only one that worked for me.
– JosephH
Nov 24 '14 at 11:12
1
Of all the answers, this is the one that worked for me as well.
– Avanst
Jan 10 '15 at 4:26
add a comment |
By switching the "u" units. The default sector size will show up when you create the partition.
If you are starting to partition a new disk and you get this error, you can.
- create a partion with the defaut.
- n,p,1,Enter, Enter
- Display and get the partition error message. "p".
- switch units "u"
- delete the partition. "d"
- Now create again. this time the defaults will show the correct sector. (in my case it was 1024).
Command (m for help): p
Disk /dev/sdb: 599.9 GB, 599932844032 bytes
255 heads, 63 sectors/track, 72937 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 524288 bytes
Disk identifier: 0x2016bdc5
Device Boot Start End Blocks Id System
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-72937, default 1): 1
Last cylinder, +cylinders or +size{K,M,G} (1-72937, default 72937):
Using default value 72937
Command (m for help): p
Disk /dev/sdb: 599.9 GB, 599932844032 bytes
255 heads, 63 sectors/track, 72937 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 524288 bytes
Disk identifier: 0x2016bdc5
Device Boot Start End Blocks Id System
/dev/sdb1 1 72937 585866421 83 Linux
Partition 1 does not start on physical sector boundary.
Command (m for help): u
Changing display/entry units to sectors
Command (m for help): p
Disk /dev/sdb: 599.9 GB, 599932844032 bytes
255 heads, 63 sectors/track, 72937 cylinders, total 1171743836 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 524288 bytes
Disk identifier: 0x2016bdc5
Device Boot Start End Blocks Id System
/dev/sdb1 63 1171732904 585866421 83 Linux
Partition 1 does not start on physical sector boundary.
Command (m for help): d
Selected partition 1
Command (m for help): p
Disk /dev/sdb: 599.9 GB, 599932844032 bytes
255 heads, 63 sectors/track, 72937 cylinders, total 1171743836 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 524288 bytes
Disk identifier: 0x2016bdc5
Device Boot Start End Blocks Id System
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 8
Value out of range.
Partition number (1-4): 1
First sector (63-1171743835, default 1024):
Using default value 1024
Last sector, +sectors or +size{K,M,G} (1024-1171743835, default 1171743835):
Using default value 1171743835
Command (m for help): p
Disk /dev/sdb: 599.9 GB, 599932844032 bytes
255 heads, 63 sectors/track, 72937 cylinders, total 1171743836 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 524288 bytes
Disk identifier: 0x2016bdc5
Device Boot Start End Blocks Id System
/dev/sdb1 1024 1171743835 585871406 83 Linux
Command (m for help): w
The partition table has been altered!
1
I tried the approaches from other answers, but switching to 'u' mode was the only one that worked for me.
– JosephH
Nov 24 '14 at 11:12
1
Of all the answers, this is the one that worked for me as well.
– Avanst
Jan 10 '15 at 4:26
add a comment |
By switching the "u" units. The default sector size will show up when you create the partition.
If you are starting to partition a new disk and you get this error, you can.
- create a partion with the defaut.
- n,p,1,Enter, Enter
- Display and get the partition error message. "p".
- switch units "u"
- delete the partition. "d"
- Now create again. this time the defaults will show the correct sector. (in my case it was 1024).
Command (m for help): p
Disk /dev/sdb: 599.9 GB, 599932844032 bytes
255 heads, 63 sectors/track, 72937 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 524288 bytes
Disk identifier: 0x2016bdc5
Device Boot Start End Blocks Id System
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-72937, default 1): 1
Last cylinder, +cylinders or +size{K,M,G} (1-72937, default 72937):
Using default value 72937
Command (m for help): p
Disk /dev/sdb: 599.9 GB, 599932844032 bytes
255 heads, 63 sectors/track, 72937 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 524288 bytes
Disk identifier: 0x2016bdc5
Device Boot Start End Blocks Id System
/dev/sdb1 1 72937 585866421 83 Linux
Partition 1 does not start on physical sector boundary.
Command (m for help): u
Changing display/entry units to sectors
Command (m for help): p
Disk /dev/sdb: 599.9 GB, 599932844032 bytes
255 heads, 63 sectors/track, 72937 cylinders, total 1171743836 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 524288 bytes
Disk identifier: 0x2016bdc5
Device Boot Start End Blocks Id System
/dev/sdb1 63 1171732904 585866421 83 Linux
Partition 1 does not start on physical sector boundary.
Command (m for help): d
Selected partition 1
Command (m for help): p
Disk /dev/sdb: 599.9 GB, 599932844032 bytes
255 heads, 63 sectors/track, 72937 cylinders, total 1171743836 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 524288 bytes
Disk identifier: 0x2016bdc5
Device Boot Start End Blocks Id System
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 8
Value out of range.
Partition number (1-4): 1
First sector (63-1171743835, default 1024):
Using default value 1024
Last sector, +sectors or +size{K,M,G} (1024-1171743835, default 1171743835):
Using default value 1171743835
Command (m for help): p
Disk /dev/sdb: 599.9 GB, 599932844032 bytes
255 heads, 63 sectors/track, 72937 cylinders, total 1171743836 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 524288 bytes
Disk identifier: 0x2016bdc5
Device Boot Start End Blocks Id System
/dev/sdb1 1024 1171743835 585871406 83 Linux
Command (m for help): w
The partition table has been altered!
By switching the "u" units. The default sector size will show up when you create the partition.
If you are starting to partition a new disk and you get this error, you can.
- create a partion with the defaut.
- n,p,1,Enter, Enter
- Display and get the partition error message. "p".
- switch units "u"
- delete the partition. "d"
- Now create again. this time the defaults will show the correct sector. (in my case it was 1024).
Command (m for help): p
Disk /dev/sdb: 599.9 GB, 599932844032 bytes
255 heads, 63 sectors/track, 72937 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 524288 bytes
Disk identifier: 0x2016bdc5
Device Boot Start End Blocks Id System
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-72937, default 1): 1
Last cylinder, +cylinders or +size{K,M,G} (1-72937, default 72937):
Using default value 72937
Command (m for help): p
Disk /dev/sdb: 599.9 GB, 599932844032 bytes
255 heads, 63 sectors/track, 72937 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 524288 bytes
Disk identifier: 0x2016bdc5
Device Boot Start End Blocks Id System
/dev/sdb1 1 72937 585866421 83 Linux
Partition 1 does not start on physical sector boundary.
Command (m for help): u
Changing display/entry units to sectors
Command (m for help): p
Disk /dev/sdb: 599.9 GB, 599932844032 bytes
255 heads, 63 sectors/track, 72937 cylinders, total 1171743836 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 524288 bytes
Disk identifier: 0x2016bdc5
Device Boot Start End Blocks Id System
/dev/sdb1 63 1171732904 585866421 83 Linux
Partition 1 does not start on physical sector boundary.
Command (m for help): d
Selected partition 1
Command (m for help): p
Disk /dev/sdb: 599.9 GB, 599932844032 bytes
255 heads, 63 sectors/track, 72937 cylinders, total 1171743836 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 524288 bytes
Disk identifier: 0x2016bdc5
Device Boot Start End Blocks Id System
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 8
Value out of range.
Partition number (1-4): 1
First sector (63-1171743835, default 1024):
Using default value 1024
Last sector, +sectors or +size{K,M,G} (1024-1171743835, default 1171743835):
Using default value 1171743835
Command (m for help): p
Disk /dev/sdb: 599.9 GB, 599932844032 bytes
255 heads, 63 sectors/track, 72937 cylinders, total 1171743836 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 524288 bytes
Disk identifier: 0x2016bdc5
Device Boot Start End Blocks Id System
/dev/sdb1 1024 1171743835 585871406 83 Linux
Command (m for help): w
The partition table has been altered!
edited Oct 1 '14 at 21:36
Volker Siegel
9,08043349
9,08043349
answered Oct 1 '14 at 21:10
Tom ShippeeTom Shippee
411
411
1
I tried the approaches from other answers, but switching to 'u' mode was the only one that worked for me.
– JosephH
Nov 24 '14 at 11:12
1
Of all the answers, this is the one that worked for me as well.
– Avanst
Jan 10 '15 at 4:26
add a comment |
1
I tried the approaches from other answers, but switching to 'u' mode was the only one that worked for me.
– JosephH
Nov 24 '14 at 11:12
1
Of all the answers, this is the one that worked for me as well.
– Avanst
Jan 10 '15 at 4:26
1
1
I tried the approaches from other answers, but switching to 'u' mode was the only one that worked for me.
– JosephH
Nov 24 '14 at 11:12
I tried the approaches from other answers, but switching to 'u' mode was the only one that worked for me.
– JosephH
Nov 24 '14 at 11:12
1
1
Of all the answers, this is the one that worked for me as well.
– Avanst
Jan 10 '15 at 4:26
Of all the answers, this is the one that worked for me as well.
– Avanst
Jan 10 '15 at 4:26
add a comment |
just delete all partition and do this in fdisk
Command (m for help): c
DOS Compatibility flag is not set
Command (m for help): u
Changing display/entry units to sectors
New contributor
Abdallah Mousa is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
just delete all partition and do this in fdisk
Command (m for help): c
DOS Compatibility flag is not set
Command (m for help): u
Changing display/entry units to sectors
New contributor
Abdallah Mousa is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
just delete all partition and do this in fdisk
Command (m for help): c
DOS Compatibility flag is not set
Command (m for help): u
Changing display/entry units to sectors
New contributor
Abdallah Mousa is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
just delete all partition and do this in fdisk
Command (m for help): c
DOS Compatibility flag is not set
Command (m for help): u
Changing display/entry units to sectors
New contributor
Abdallah Mousa is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Abdallah Mousa is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 7 hours ago
Abdallah MousaAbdallah Mousa
1
1
New contributor
Abdallah Mousa is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Abdallah Mousa is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Abdallah Mousa is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
If you have a windows dual boot you can use MiniTool Partition Wizard. This thing has saved my ass multiple times. Just right click the partition and click align. Don't forget to click apply.
add a comment |
If you have a windows dual boot you can use MiniTool Partition Wizard. This thing has saved my ass multiple times. Just right click the partition and click align. Don't forget to click apply.
add a comment |
If you have a windows dual boot you can use MiniTool Partition Wizard. This thing has saved my ass multiple times. Just right click the partition and click align. Don't forget to click apply.
If you have a windows dual boot you can use MiniTool Partition Wizard. This thing has saved my ass multiple times. Just right click the partition and click align. Don't forget to click apply.
answered May 3 '17 at 19:41
FlorensFlorens
111
111
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f156994%2fpartition-does-not-start-on-physical-sector-boundary%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown