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.
On Sun 14 Jan 2024 at 16:47:41 (-0500), gene heskett wrote:
ene@coyote:~/src/klipper-docs$ sudo smartctl -a /dev/sde
[sudo] password for gene:
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-17-rt-amd64] (local
build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke,
www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: Gigastone SSD
Serial Number: GST02TBG221146
↑↑↑↑↑↑↑↑↑↑↑↑↑↑
You see that there? You should find this symlink on your system:
/dev/disk/by-id/… …GST02TBG221146
pointing at some random /dev/sdX. Where you put /dev/sdX,
put /dev/disk/by-id/… …GST02TBG221146 instead. Then you'll
know you're referring to that disk. Likewise the others.
(As already suggested by David C, Sun, 14 Jan 2024 04:41:51 -0800)
Cheers,
David.
There is a big horse-fly in that soup !!!
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, and on reboot it shows up in an
lsblk list as:
root@coyote:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 838.2G 0 part /
├─sda2 8:2 0 46.8G 0 part [SWAP]
└─sda3 8:3 0 46.6G 0 part /tmp
sdb 8:16 1 0B 0 disk
sdc 8:32 1 0B 0 disk
sdd 8:48 0 931.5G 0 disk
├─sdd1 8:49 0 900G 0 part
│ └─md0 9:0 0 1.7T 0 raid10
│ └─md0p1 259:0 0 1.7T 0 part /home
├─sdd2 8:50 0 30G 0 part
│ └─md1 9:1 0 60G 0 raid10 [SWAP]
└─sdd3 8:51 0 1.5G 0 part
└─md2 9:2 0 3G 0 raid10
sde 8:64 0 931.5G 0 disk
├─sde1 8:65 0 900G 0 part
│ └─md0 9:0 0 1.7T 0 raid10
│ └─md0p1 259:0 0 1.7T 0 part /home
├─sde2 8:66 0 30G 0 part
│ └─md1 9:1 0 60G 0 raid10 [SWAP]
└─sde3 8:67 0 1.5G 0 part
└─md2 9:2 0 3G 0 raid10
sdf 8:80 0 931.5G 0 disk
├─sdf1 8:81 0 900G 0 part
│ └─md0 9:0 0 1.7T 0 raid10
│ └─md0p1 259:0 0 1.7T 0 part /home
├─sdf2 8:82 0 30G 0 part
│ └─md1 9:1 0 60G 0 raid10 [SWAP]
└─sdf3 8:83 0 1.5G 0 part
└─md2 9:2 0 3G 0 raid10
sdg 8:96 0 931.5G 0 disk
├─sdg1 8:97 0 900G 0 part
│ └─md0 9:0 0 1.7T 0 raid10
│ └─md0p1 259:0 0 1.7T 0 part /home
├─sdg2 8:98 0 30G 0 part
│ └─md1 9:1 0 60G 0 raid10 [SWAP]
└─sdg3 8:99 0 1.5G 0 part
└─md2 9:2 0 3G 0 raid10
sdh 8:112 0 1.9T 0 disk
└─sdh1 8:113 0 1.9T 0 part <<<
sdi 8:128 0 1.9T 0 disk
└─sdi1 8:129 0 1.9T 0 part <<<
sdj 8:144 0 1.9T 0 disk
└─sdj1 8:145 0 1.9T 0 part <<<
sdk 8:160 0 1.9T 0 disk
└─sdk1 8:161 0 1.9T 0 part <<<
sdl 8:176 0 1.9T 0 disk
└─sdl1 8:177 0 1.9T 0 part <<<
sr0 11:0 1 1024M 0 rom
root@coyote:~#
Now confirmed by looking at all 5 with gparted, there are only 3 unique
serial numbers:
root@coyote:~# ls /dev/disk/by-id
ata-ATAPI_iHAS424_B_3524253_327133504865
ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W
wwn-0x5002538f413394a5-part1
ata-Gigastone_SSD_GST02TBG221146
ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W-part1
wwn-0x5002538f413394a5-part2
ata-Gigastone_SSD_GST02TBG221146-part1 ===========
ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W-part2
wwn-0x5002538f413394a5-part3
ata-Gigastone_SSD_GSTD02TB230102
ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W-part3 wwn-0x5002538f413394a9
ata-Gigastone_SSD_GSTD02TB230102-part1 ===========
ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V
wwn-0x5002538f413394a9-part1
ata-Gigastone_SSD_GSTG02TB230206
ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V-part1
wwn-0x5002538f413394a9-part2
ata-Gigastone_SSD_GSTG02TB230206-part1 ===========
ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V-part2
wwn-0x5002538f413394a9-part3
ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T
ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V-part3 wwn-0x5002538f413394ae
ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T-part1
md-name-coyote:0
wwn-0x5002538f413394ae-part1
ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T-part2
md-name-coyote:0-part1
wwn-0x5002538f413394ae-part2
ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T-part3
md-name-coyote:2
wwn-0x5002538f413394ae-part3
ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E
md-name-_none_:1 wwn-0x5002538f413394b0
ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E-part1
md-uuid-3d5a3621:c0e32c8a:e3f7ebb3:318edbfb
wwn-0x5002538f413394b0-part1
ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E-part2
md-uuid-3d5a3621:c0e32c8a:e3f7ebb3:318edbfb-part1
wwn-0x5002538f413394b0-part2
ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E-part3
md-uuid-57a88605:27f5a773:5be347c1:7c5e7342
wwn-0x5002538f413394b0-part3
ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V
md-uuid-bb6e03ce:19d290c8:5171004f:0127a392 wwn-0x5002538f42205e8e
ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V-part1
usb-Brother_MFC-J6920DW_BROG5F229909-0:0
wwn-0x5002538f42205e8e-part1
ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V-part2
usb-USB_Mass_Storage_Device_816820130806-0:0
wwn-0x5002538f42205e8e-part2
ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V-part3
wwn-0x5002538f413394a5
wwn-0x5002538f42205e8e-part3
root@coyote:~#
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.
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.
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.
Thanks everybody.
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
