Web lists-archives.com

Re: Some help with dd backing up into an iso




On Sun 12 Mar 2017 at 23:50:00 (+0000), GiaThnYgeia wrote:
> Thomas Schmitt:
> > This is not an answer to my question.
> > Is the reported address a single line
> >   /media/user/DebonUSB/usb-Kingston_DataTraveler_3.0_08606E69C773BFC06965007B-0:0-part1
> > or is it reported as two lines:
> >   /media/user/DebonUSB
> >   /usb-Kingston_DataTraveler_3.0_08606E69C773BFC06965007B-0:0-part1
> > ?
> 
> No it is all connected line and I don't think I can change this.  But so
> much for the serial number theory as two different disks have the same
> exact address.  That gets really confusing if you don't change the
> labels on them.

It's always moot what manufacturers actually put in the Serial Number
field on cheap devices like sticks and SD cards. The only instance
where I have several sticks from one source (a Petroleum company at
AAPG) has the ID_SERIAL¹ set to SMI_USB_DISK-0:0 which has no chance
of being unique.

For Kingston's, I was just guessing², based on a sample of two:

S:disk/by-id/usb-Kingston_DataTraveler_2.0_2731524021F1FE28-0:0-part1

E:ID_BUS=usb
E:ID_MODEL=DataTraveler_2.0
E:ID_SERIAL=Kingston_DataTraveler_2.0_2731524021F1FE28-0:0
E:ID_SERIAL_SHORT=2731524021F1FE28
E:ID_VENDOR=Kingston

S:disk/by-id/usb-Kingston_DT_Elite_HS_2.0_06E16840C3009958-0:0-part1

E:ID_BUS=usb
E:ID_MODEL=DT_Elite_HS_2.0
E:ID_SERIAL=Kingston_DT_Elite_HS_2.0_06E16840C3009958-0:0
E:ID_SERIAL_SHORT=06E16840C3009958
E:ID_VENDOR=Kingston

> the question I have is if this is ....part1 where is the other part/s?

"part" does not mean piece/fragment, but is short for partition.
So if you have a single partition (typical for a stick when purchased),
there will only be a part1. Nothing's missing.

¹ from the contents of /run/udev/data/b8:<1+2^N> but also found in
/sys/bus/usb/devices/<foo>/{manufacturer,product,serial,version}.
With hard drives, the Serial Number printed on the carton is as likely
to turn up in ID_SCSI_COMPAT as ID_SERIAL/ID_SERIAL_SHORT.

² Never having depended on these fields, I hadn't given them any
thought. If this is what automounters insist on doing, I shall
keep on mounting them myself by LABEL (ext/FAT) or UUID (FAT).
Thanks for the cautionary tale.

Cheers,
David.