Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 30 Sep 2020 21:02:52 +0200
From:      Christoph Kukulies <kuku@kukulies.org>
To:        David Christensen <dpchrist@holgerdanske.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: concluding from dd raw dump size to disk mfgr
Message-ID:  <4B77A4C4-5CBE-4414-B54B-05B3A2990E79@kukulies.org>
In-Reply-To: <d7f8f28f-fce0-4717-ec7f-fd3e1412b969@holgerdanske.com>
References:  <d7f8f28f-fce0-4717-ec7f-fd3e1412b969@holgerdanske.com>

next in thread | previous in thread | raw e-mail | index | archive | help

Thanks. Using a larger disk would be an option too.

Interesting that the WD drive you found has exactly the same size.=20

I had luck to have had access to the original system today again and I found=
 the same drive for sale a few miles from my home in an Internet classifieds=
 platform for 8 =E2=82=AC (10$).

=E2=80=94
Christoph=20
>=20
> Am 30.09.2020 um 20:23 schrieb David Christensen <dpchrist@holgerdanske.co=
m>:
>=20
> =EF=BB=BFOn 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 t=
he one which fits exactly that size. Unfortunately I presently don't know wh=
at drive mfgr./type this corresponds to. Is there a way to find out?
>=20
>> On 2020-09-30 05:59, Christoph Kukulies wrote:
>> ... I didn=E2=80=99t have physical access nor any access to the system I t=
ook 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.
>=20
>=20
> STFW "500107862016":
>=20
> https://sourceforge.net/p/clonezilla/bugs/256/
>=20
> ~# sfdisk -l /dev/sda
> Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
> Units: sectors of 1 * 512 =3D 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>
>=20
> Diskinfo:
>=20
> 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>
>=20
>=20
> Another option is to copy the image to a larger device.
>=20
>=20
> If the original image used GPT partitioning, you would then need to repair=
 the backup GPT table.  I did this recently using sfdisk(8):
>=20
> https://www.mail-archive.com/debian-user@lists.debian.org/msg760783.html
>=20
>=20
> gdisk(8) was also suggested:
>=20
> https://www.mail-archive.com/debian-user@lists.debian.org/msg760803.html
>=20
>=20
> David
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.or=
g"




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B77A4C4-5CBE-4414-B54B-05B3A2990E79>