On Mon 15 Jan 2024 at 08:39:37 (-0500), gene heskett wrote:
> On 1/14/24 20:19, gene heskett wrote:
> > On 1/14/24 19:48, David Wright wrote:
> > > On Sun 14 Jan 2024 at 14:48:49 (-0500), gene heskett wrote:
> > > > On 1/14/24 07:42, David Christensen wrote:
> > >
> > > > > I am confused -- do you have 4 or 5 Gigastone 2 TB SSD?
> > > >
> > > > 5, ordered in 2 separate orders.
> > > > >
> > > > > > So that one could be formatted ext4 and serve as a
> > > > > backup of the raid10.
> > > > What I am trying to do now, but cannot if it is plugged into a
> > > > motherboard port, hence the repeat of this exercise on the 2nd sata
> > > > card.
> > > > >
> > > > > > how do I make an image of that
> > > > > > raid10 to /dev/sde and get every byte? That
> > > > > seems like the first step
> > > > > > to me.
> > > > This I am still trying to do, the first pass copied all 350G of /home
> > > > but went to the wrong drive, and I had mounted the drive by its label.
> > > > It is now /dev/sdh and all labels above it are now wrong. Crazy.
> > > > These SSD's all have an OTP serial number. I am tempted to use that
> > > > serial number as a label _I_ can control. And according to gparted,
> > > > labels do not survive being incorporated into a raid as the raid is
> > > > all labeled with hostname : partition number. So there really is no
> > > > way in linux to define a drive that is that drive forever. Unreal...
> > >
> > > Interesting to see in how many differents ways you can use the
> > > term "label". BTW I have no idea what an "OTP serial number" is.
> > >
> > OTP=One Time Pad, never to be used again.
I too can lookup acronyms with ease. I asked about "OTP serial number",
not "OTP" serial number.
> I moved the data cable to where I knew I could find it again, as one
> of 5 drives attached to the 16 port card,
No idea what that means.
> and on reboot it shows up in
> an lsblk list as:
> root@coyote:~# lsblk
[ … table showing five Samsungs, five Gigastones, and two
other items, perhaps printer (confirmed later) and camera … ]
> Now confirmed by looking at all 5 with gparted, there are only 3
> unique serial numbers:
I don't see any parted output.
> root@coyote:~# ls /dev/disk/by-id
ls -1 would at least sort out this mess, but more useful would be ls -l
or for j in /dev/disk/by-id/* ; do printf '%s\t%s\n' "$(realpath "$j")" "$j" ;
done
as you could then see what the symlinks point to, which after all
is their raison d'être.
Extracting:
> ata-Gigastone_SSD_GST02TBG221146
> ata-Gigastone_SSD_GSTD02TB230102
> ata-Gigastone_SSD_GSTG02TB230206
these devices appear to have normal serial numbers. Do they bear
any other indication, like engravings or stickers? If not, I would,
in turn, plug each one in, read the serial number from its symlink,
and write on it with a marker. While doing that, you could also
run smartctl.
> only 3 unique serial numbers!!!!!!
> udev when finding that situation should scream from the rooftops!!
> not silently overwrite an entry in the by-id that its already made.
If you say so. I never had any problem with udev when I had
three identical USB sticks with the "serial" number
ID_SERIAL=SMI_USB_DISK-0:0
I scratched distinguishing letter on them, and watched xconsole for
the drive letter whenever I plugged one in. At 8GB a piece, the
largest I had at the time, they were very useful. And they didn't
cost me a penny as they were giveaways.
> HTH do I fix that?
> can tune2fs edit a serial number? no.
> can the UUID be rendered read-only, no.
> gparted and similar can change the UUID by a click of the mouse.
> I'm officially screwed and I have had them too long to return them now.
You need to find out, in turn, which ones work, and that goes for
both the SSDs and wherever you plug them in. You can make little
progress at all without distinguishing them, as you have already
shown by copying data to who knows where.
> That could even explain why my first run of rsync worked fine but went
> to a drive that was NOT mounted. And it was mounted by LABEL= The
> only one of those 5 SSD's I had labeled at that time.
You haven't shown any evidence of such LABELling, and most of your
anecdotal narratives don't give much confidence for us to really
know what was actually done. But to be fair, anything could
happen if the hardware is not working properly.
Cheers,
David.
