rlw

SATA not USB - just saying. But Unraid is done for me. Still my argument is valid, it is a bit out of time when UUID and PartUUID are used for the USB Stick running the OS don't you think. Linux recognizes the USB drives as two separate ones (sda and sdb, now sdd and sde as shown in the screenshots of UNRAID OS - Tools - System Devices. So if even there both USB drives are shown, why can't they be allocated by their Linux definition ? No, specialized special speciality, we go by serial. Out of convenience.

OpenMediaVault - installed without special settings - from USB stick to one of the 256GB SATA SSDs - just clicked "next", "next" ..... First login to webinterface, clicked on harddrives and voilá - both USB SSDs recognized without issue, I DID NOTHING. See this is the issue - you blame the 5000€ SSDs, me as the user, asked to install a plugin to find devices which the core system can't find. You understand that this is NOT how UNRAID should be, right. UNRAID wants a paid license, then I expect it comes out of the box with the functionality to find as many USB devices as there are USB ports on the computer, ESPECIALLY when it offers 24 (!) devices I can assign to it. Now I am working with OMV, thanks for all your support although not really solving the issue, which is for sure deep in the system somewhere 1 line of code.

As far as I know @JorgeB Unraid specifies ONLY a unique UUID which - as I posted before (middle of page 1) id unique for both SSDs each. A unique serial requirement I haven't found in the requirements. Those SSDs are custom built for me for various reasons. IF this was a requirement it is IMHO non-sense as for the USB Stick to have Unraid running only a unique UUID is required. Why would they go down serial-uniqueness as Linux is identifying both SSDs already separately as SDA and SDB (see screenshots).

Now I installed USB devices again, ran diagnostics and took screenshot of System Devices and MAIN TAB again FireShot Capture 053 - Tower_SysDevs - 192.168.178.72.pdf tower-diagnostics-20231225-1211.zip

Now I disconnected the USB Drives and rebooted Then I ran Diagnostics again, took a screenshot of System Devices and the MAIN tab SystemDevices after reboot disconnected USB Drives.pdf tower-diagnostics-20231225-1208.zip

@dlandon I got so tired I went to bed early, sorry Here is the diagnostics pre-reboot as per your 1st bullet point tower-diagnostics-20231225-1204.zip

@dlandon 1. They have different serials, see fdisk before, no matter what the undeveloped unraid (sorry, but SDLC whould have to report that as anomaly) 2. The screenshots were 10 seconds apart. I will try your 3 steps after walking the dog, but this is the last thing. Then we end here and I will forward to Unraid team as there is a mess in their system.

I may try OMV just to see if it is an unraid issue (what I believe) or not

Before I do that, @dlandon check the SCSI devices, the server has 2x256GB SSD SATA and 2x30TB USB SSD and a 32GB Flash (for unraid OS) Shall I still do the three steps (later)?

Only one of them (sda), sdb is missing still.

@dlandonLinux is seeing the devices (/dev/sda and /dev/sdb) - I was in the bios, all disks there, all USB entries enabled. See screenshot and "fdisk -l" below And interestingly enough, even UNRAID recognizes the two USB as TWO USB Drives (sda and sdb). If there was an issue with recognition (and they have differen UUIDs and PartUUIDs) they would not appear under SCSI devices under Tools / Systemdevices. root@Tower:~# fdisk -l Disk /dev/loop0: 60.29 MiB, 63217664 bytes, 123472 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/loop1: 333.06 MiB, 349237248 bytes, 682104 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes The backup GPT table is corrupt, but the primary appears OK, so that will be used. Disk /dev/sda: 28.61 TiB, 31457280000000 bytes, 7680000000 sectors Disk model: SSD Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 46D7FF30-779D-4B65-9A32-9A81F2EBD651 Device Start End Sectors Size Type /dev/sda1 8 7679999994 7679999987 28.6T Linux filesystem Disk /dev/sdb: 28.61 TiB, 31457280000000 bytes, 7680000000 sectors Disk model: SSD Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/sdc: 28.48 GiB, 30579621888 bytes, 59725824 sectors Disk model: Transcend 32GB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sdc1 * 2048 59725823 59723776 28.5G c W95 FAT32 (LBA) Disk /dev/sdd: 238.47 GiB, 256060514304 bytes, 500118192 sectors Disk model: FIKWOT FS810 256 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sdd1 2048 500118191 500116144 238.5G 83 Linux Disk /dev/sde: 238.47 GiB, 256060514304 bytes, 500118192 sectors Disk model: SSD_2.5"_256GB_I Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sde1 2048 500118191 500116144 238.5G 83 Linux root@Tower:~#

@dlandon Attached Diagnostics and UD Screenshot. I had the ONE 30TB drive added to the array and as mentioned got critical errors. No none of the USB-C SSDs is appearing anymore tower-diagnostics-20231224-1558.zip FireShot Capture 051 - Tower_Main - 192.168.178.72.pdf

Das habe ich gecheckt, haben bis auf das PartLabel unterschiedliche IDs und UUIDs und PartUUIDs. Das kann es nicht sein. Ich gebe mir jetzt noch eine Stunde, es ist Heiligabend auch für Euch und Ihr habt besseres zu tun als mein Problem zu lösen. Ich kann alles zurückgeben (gut, den Tower hatte ich noch). Dann wars das. Mein Geduldsfaden ist nur noch 3mm lang

Tatsächlich kamen die aus EU (gebaut in China) beide zusammen knapp 5000 €

I have now started array with the one working USB but it produced errors - I am lost, sorry. 24-12-2023 06:05 Unraid Parity disk error Alert [TOWER] - Parity disk in error state (disk dsbl) SDK_SSD-0:0 (sda) In Windows and Raspi both USB SSD are working and can be used. Unraid seems to have too many issues still