On 08/02/2021 08.21, Josef Moellers wrote:
On 07.02.21 21:20, Carlos E.R. wrote:
On 07/02/2021 16.59, oszko@chem.u-szeged.hu wrote:
Idézet ("Carlos E.R." <robin.listas@gmx.es>):
On 06/02/2021 20.43, oszko@chem.u-szeged.hu wrote:
...
Thanks for your tips! I guess it would be an even longer way to go than I first thought. I think it is easier to do than to explain :-)
The issue of sector size I would like confirmation from others. I don't know if is possible to clone (dd) a disk using dd when the source uses 4 KB sectors and the destination 512 bytes. All my current big hard disks use 4 KB sectors, and all my SSDs, smaller, use 512 bytes.
It depends. Most 4k disks have an emulation built in to allow 512 byte sector size, so from the outside, they can be viewed as disks haveing that sector size. Agreed: when you change a single 512-byte sector, the disk itself has to read 4k, then modify the 512 bytes and then write the 4k back, but that is invisible (but measurable) from the outside.
I know. For instance, my disks show this: Telcontar:~ # fdisk -l /dev/sda Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: ST2000DM001-1CH1 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes Thus, logically they are used in blocks of 512 disks, so there would be no problem with the migration. My ssds are this type, no emulation: Isengard:~ # fdisk -l Disk /dev/sda: 111.8 GiB, 120034123776 bytes, 234441648 sectors Disk model: KINGSTON SMS200S Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt The problem I worry about is if the source disk says: Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes and the destination ssd says 512. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)