concluding from dd raw dump size to disk mfgr

[David Christensen]

On 2020-09-30 00:40, Christoph Kukulies wrote:
> I made a dd dump of a raw disk device the other day. The size of the 
> dump is exactly
> 
> 500107862016 bytes in size, corresponding to 997773168  sectors 
> (512bytes).
> 
> I would like to dump this file back to a physical device. Best would 
> be the one which fits exactly that size. Unfortunately I presently 
> don't know what drive mfgr./type this corresponds to. Is there a way 
> to find out?

On 2020-09-30 05:59, Christoph Kukulies wrote:
> ... I didn’t have physical access nor any access to 
> the system I took the dd dump from. I thought just to identify the
> drive from the calculation of the dump size.
> 
> But meanwhile I identified a device that fits and that probably must 
> have the type of drive I took the dump from:
> 
> Toshiba MQ01ABF050
I am unable to find an WWW database of drive specifications.


STFW "500107862016":

https://sourceforge.net/p/clonezilla/bugs/256/

~# sfdisk -l /dev/sda
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 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
Disklabel type: dos
Disk identifier: 0x6c6583c4
<snip>

Diskinfo:

Model Family:     Western Digital Blue Mobile
Device Model:     WDC WD5000LPVX-22V0TT0
Serial Number:    WD-WXB1A45580UJ
LU WWN Device Id: 5 0014ee 605ce1d84
Firmware Version: 01.01A01
User Capacity:    500,107,862,016 bytes [500 GB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
<snip>


Another option is to copy the image to a larger device.


If the original image used GPT partitioning, you would then need to 
repair the backup GPT table.  I did this recently using sfdisk(8):

https://www.mail-archive.com/debian-user@lists.debian.org/msg760783.html


gdisk(8) was also suggested:

https://www.mail-archive.com/debian-user@lists.debian.org/msg760803.html


David