Help on wrong HDD partitioning after using Clonezilla
![](https://seccdn.libravatar.org/avatar/40870bb039badc40b3fb450d8149acd2.jpg?s=120&d=mm&r=g)
Hello, This is not an openSUSE specific support request but it's related to a series of error messages I noticed after having cloned my older HDD 512/512 bytes/sector to a newer Western Digital HDD, which uses the advanced format 512/4096 bytes per sector. I would like to avoid that this sort of partitioning may affect the read/write IO rates. The errors I see are these: marco@linux-turion64:~> sudo fdisk -x Disk /dev/sda: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: WDC WD10SPZX-22Z Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x5bc53d8b Dispositivo Avvio Start Fine Settori Id Tipo Start-C/H/S End-C/H/S Attrs /dev/sda1 * 2048 1026036 1023989 7 HPFS 0/32/33 63/221/19 80 /dev/sda2 1026037 447673612 446647576 7 HPFS 63/221/20 218/100/23 /dev/sda3 447673613 449516792 1843180 27 Hidd 218/100/24 333/32/12 /dev/sda4 449516793 1953523118 1504006326 f W95 333/32/13 769/48/30 /dev/sda5 449516795 617287136 167770342 83 Linu 333/32/15 536/88/33 /dev/sda6 617287138 1918772938 1301485801 83 Linu 536/88/35 654/23/20 /dev/sda7 1918772940 1953521663 34748724 82 Linu 654/23/22 1023/254/63 Partition 2 does not start on physical sector boundary. Partition 3 does not start on physical sector boundary. Partition 4 does not start on physical sector boundary. Partition 5 does not start on physical sector boundary. Partition 6 does not start on physical sector boundary. Partition 7 does not start on physical sector boundary. I have the original data on the older HDD and I would like to get the best suggestion in order to correct this issue. When I say "better", I mean less effort-cost and safe enough to avoid to lost data on the new HDD if possible despite I have the backup on previous disk. If you prefer you can send me the suggestions by private message. Thanks in advance! Best Regards, -- Marco Calistri Build: openSUSE Tumbleweed 20220523 Kernel: 5.17.9-1-default - Cinnamon 5.2.7
![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
On 2022-06-01 02:36, Marco Calistri wrote:
Hello,
This is not an openSUSE specific support request but it's related to a series of error messages I noticed after having cloned my older HDD 512/512 bytes/sector to a newer Western Digital HDD, which uses the advanced format 512/4096 bytes per sector.
AFAIK you can not clone from-to that setup. Well, you may, if logical sizes are the same, but... Assuming you mean a byte by byte hard disk clone, as with dd.
I would like to avoid that this sort of partitioning may affect the read/write IO rates.
The errors I see are these:
marco@linux-turion64:~> sudo fdisk -x
Disk /dev/sda: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: WDC WD10SPZX-22Z Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x5bc53d8b
Dispositivo Avvio Start Fine Settori Id Tipo Start-C/H/S End-C/H/S Attrs /dev/sda1 * 2048 1026036 1023989 7 HPFS 0/32/33 63/221/19 80 /dev/sda2 1026037 447673612 446647576 7 HPFS 63/221/20 218/100/23 /dev/sda3 447673613 449516792 1843180 27 Hidd 218/100/24 333/32/12 /dev/sda4 449516793 1953523118 1504006326 f W95 333/32/13 769/48/30 /dev/sda5 449516795 617287136 167770342 83 Linu 333/32/15 536/88/33 /dev/sda6 617287138 1918772938 1301485801 83 Linu 536/88/35 654/23/20 /dev/sda7 1918772940 1953521663 34748724 82 Linu 654/23/22 1023/254/63
Partition 2 does not start on physical sector boundary. Partition 3 does not start on physical sector boundary. Partition 4 does not start on physical sector boundary. Partition 5 does not start on physical sector boundary. Partition 6 does not start on physical sector boundary. Partition 7 does not start on physical sector boundary.
I have the original data on the older HDD and I would like to get the best suggestion in order to correct this issue.
When I say "better", I mean less effort-cost and safe enough to avoid to lost data on the new HDD if possible despite I have the backup on previous disk.
AFAIK, create partitions from scratch with gparted, and rsync the files. If btrfs is involved, scratch that.
If you prefer you can send me the suggestions by private message.
Better here, so that we can argue pros and cons, plus we all learn ;-) -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.3)
![](https://seccdn.libravatar.org/avatar/40870bb039badc40b3fb450d8149acd2.jpg?s=120&d=mm&r=g)
Il 01/06/22 03:57, Carlos E. R. ha scritto:
On 2022-06-01 02:36, Marco Calistri wrote:
Hello,
This is not an openSUSE specific support request but it's related to a series of error messages I noticed after having cloned my older HDD 512/512 bytes/sector to a newer Western Digital HDD, which uses the advanced format 512/4096 bytes per sector. AFAIK you can not clone from-to that setup.
Well, you may, if logical sizes are the same, but...
Assuming you mean a byte by byte hard disk clone, as with dd. Hi Carlos and thanks for your feedback.
Clonezilla allows to do some additional tasks if you select "Expert" mode and cloning from smaller to larger HDD is among these. It is a graphical interface to "dd" in practice, with some additional features. The issue here is more related to the fact that new HDD has a different structure for this reason the two disks are misaligned in terms of sectors and this fact could have bad effects on the I/O as I have seen on the Web.
I would like to avoid that this sort of partitioning may affect the read/write IO rates.
The errors I see are these:
marco@linux-turion64:~> sudo fdisk -x
Disk /dev/sda: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: WDC WD10SPZX-22Z Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x5bc53d8b
Dispositivo Avvio Start Fine Settori Id Tipo Start-C/H/S End-C/H/S Attrs /dev/sda1 * 2048 1026036 1023989 7 HPFS 0/32/33 63/221/19 80 /dev/sda2 1026037 447673612 446647576 7 HPFS 63/221/20 218/100/23 /dev/sda3 447673613 449516792 1843180 27 Hidd 218/100/24 333/32/12 /dev/sda4 449516793 1953523118 1504006326 f W95 333/32/13 769/48/30 /dev/sda5 449516795 617287136 167770342 83 Linu 333/32/15 536/88/33 /dev/sda6 617287138 1918772938 1301485801 83 Linu 536/88/35 654/23/20 /dev/sda7 1918772940 1953521663 34748724 82 Linu 654/23/22 1023/254/63
Partition 2 does not start on physical sector boundary. Partition 3 does not start on physical sector boundary. Partition 4 does not start on physical sector boundary. Partition 5 does not start on physical sector boundary. Partition 6 does not start on physical sector boundary. Partition 7 does not start on physical sector boundary.
I have the original data on the older HDD and I would like to get the best suggestion in order to correct this issue.
When I say "better", I mean less effort-cost and safe enough to avoid to lost data on the new HDD if possible despite I have the backup on previous disk. AFAIK, create partitions from scratch with gparted, and rsync the files.
If btrfs is involved, scratch that.
I am on EXT4 filesystem and was thinking to partition the new HDD as well, but so far I've took a decision.
If you prefer you can send me the suggestions by private message. Better here, so that we can argue pros and cons, plus we all learn ;-)
Yes I agree with you but there are always people which dislike to "OFF-TOPIC" on the mailing-list. -- Marco Calistri Build: openSUSE Tumbleweed 20220523 Kernel: 5.17.9-1-default - Cinnamon 5.2.7
![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
On 2022-06-01 13:22, Marco Calistri wrote:
Il 01/06/22 03:57, Carlos E. R. ha scritto:
On 2022-06-01 02:36, Marco Calistri wrote:
Hello,
This is not an openSUSE specific support request but it's related to a series of error messages I noticed after having cloned my older HDD 512/512 bytes/sector to a newer Western Digital HDD, which uses the advanced format 512/4096 bytes per sector. AFAIK you can not clone from-to that setup.
Well, you may, if logical sizes are the same, but...
Assuming you mean a byte by byte hard disk clone, as with dd. Hi Carlos and thanks for your feedback.
Clonezilla allows to do some additional tasks if you select "Expert" mode and cloning from smaller to larger HDD is among these. It is a graphical interface to "dd" in practice, with some additional features.
The issue here is more related to the fact that new HDD has a different structure for this reason the two disks are misaligned in terms of sectors and this fact could have bad effects on the I/O as I have seen on the Web.
Adjusting for a different disk size of disk is doable. Adjusting for a different sector size is not possible, unless the disks have the same "logical sector" size. But there will always be a penalty, AFAIK. It does four reads when it could do a single one. If the partitions are misaligned, it is even worse. But there is no way to do it "really well". You see, in any disk formatting scheme there will be some "structure" that says "this file is stored in sectors number x, y, z..., w. If you clone the disk, the structure is simply replicated, and the pointers to x, y, z... must point to the same sectors and actual data. The cloning process does not recreate an equivalent structure for a disk with different sector size, the files would have to be stored in a structure "a, b, c..." instead, where "a" is the concatenation of x, y, z.... It is a huge undertaking, different for each filesystem type, prone to mistakes. I don't know if there is any filesystem that can handle this. So, as this is impossible, the alternative is having still logical sectors of 512 bytes. Meaning 8 logical reads per sector. And some slowness. Worse if it is half on one actual sector and half on another. ...
I have the original data on the older HDD and I would like to get the best suggestion in order to correct this issue.
When I say "better", I mean less effort-cost and safe enough to avoid to lost data on the new HDD if possible despite I have the backup on previous disk. AFAIK, create partitions from scratch with gparted, and rsync the files.
I mean create new empty partition table, then the partitions. Scratch it all.
If btrfs is involved, scratch that.
I am on EXT4 filesystem and was thinking to partition the new HDD as well, but so far I've took a decision.
If you prefer you can send me the suggestions by private message. Better here, so that we can argue pros and cons, plus we all learn ;-)
Yes I agree with you but there are always people which dislike to "OFF-TOPIC" on the mailing-list.
IMHO, this is not off topic. You are migrating openSUSE Linux from one disk to another :-) If in doubt, use "users@lists.opensuse.org" instead :-) -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.3)
participants (2)
-
Carlos E. R.
-
Marco Calistri