@NeptuneSega 5 ай бұрын
The only thing that is a constant is the drive. Replace the drive. UNRAID needs to come up with a different system because USB 2 (3 burnts out too quick) is not a good long term solution
@SPXLabs 5 ай бұрын
I didn't explain or show it in the video, which now I really wish I did. But I did check in Windows what the adapters serial #s and GUIDs were without the msata device plugged in and they were still the same without the msata device being plugged in. In Windows the adapters usbstor.inf shows that is configured with the device id of USB\VID_174C&PID_55AA\123456791DB7 . So with that knowledge I'm overly confident that it is in fact the USB device being the issue. But I'll tell you what, if you really really really want me to try let me know and I'll make a short follow up video.
@mixedd69 3 ай бұрын
I just used USB Dom for mine, works flawless so far
@SPXLabs 3 ай бұрын
That’s good
@canadianryan3875 5 ай бұрын
Would be nice if it was possible to flash your own ID#
@SPXLabs 5 ай бұрын
Yeah…. But I’d prefer if they just came unique from the factory
@IEnjoyCreatingVideos 5 ай бұрын
nice video i noticed when you didn't add the msata it had no uuid so could you try using a different msata and see if it is the msata that is giving you the same uuid because if it is that could be the problem it's worth a try seems strange that unraid cant just use the uuid from hdd or ssd or nvme
@SPXLabs 5 ай бұрын
I could definitely try but on Windows when checking without the msata device plugged in, I can still see the same serial for each adapter. So because of that, I am very confident it isn't the msata devices serial.
@IEnjoyCreatingVideos 5 ай бұрын
@@SPXLabs ok, yeah that makes sense i thought i would mention it hoping it was a simple fix. i wonder if someone could make some kinda uuid generator to make random uuids and then flash it to the adapters so they could work
@SPXLabs 5 ай бұрын
@@IEnjoyCreatingVideos By all means feel free to question/discuss any topic of the video. I'm not perfect and always welcome counter points, thoughts, suggestions, critic and so forth. So I did attempt to use powershell to modify the GUID utilizing wmiobject. However, it appears the chip is in Read Only mode and the only way to overcome that is with a firmware flash tool provided by the manufacture. Or so that is my understanding anyway lol
@TheSanzca 5 ай бұрын
Would the id not be that of the ssd and not the adapter?
@SPXLabs 5 ай бұрын
It's counter intuitive in this instance because the adapter has the SATA chip on board, so when it is plugged into a computer it appears as a single storage device. lsblk would have showed us two uuids if the USB adapter and msata device where two different devices. But regardless of that, if I plug just the adapter into a windows pc without the msata storage device, I can see the serial/GUID of the usb stick itself which is 123456791DB7.
@professor-argo 5 ай бұрын
Lucky number 13......yeah
@SPXLabs 5 ай бұрын
I wanted to get ink done of a 13 but got a 31
@professor-argo 5 ай бұрын
@@SPXLabsand all the cool kids say he’s pretty fly for a white guy.
@SPXLabs 5 ай бұрын
@@professor-argo*loud music noises*
@jfkastner 5 ай бұрын
Well done! Good License Management, however, should be done differently, and not be tied to a single Storage Device
@SPXLabs 5 ай бұрын
It used to work well before the chips started being cloned instead of assigned unique IDs. The chips GUIDs can only, typically, be modified by the manufacture unless their firmware tool gets leaked to the internet. Then and only then can we modify the GUIDs ourselves. Technically you can modify the GUID in powershell/wmiobject but the chips are shipped in Read Only mode like 99% of the time.
@jfkastner 5 ай бұрын
@@SPXLabs Try a different Model USB Adapter - it costs them $ to serialize, hopefully a 'better' and more expensive Model won't have that Issue. BUT Unraid should Tie the License to e.g. the Motherboard - you'll change that almost never in a Rackmount, but Storage 'comes and goes', breaks, gets lost, gets expanded/replaced ...
@SPXLabs 5 ай бұрын
This is not an Unraid issue. If you operate in a secure environment where removable media is allowed. It is common practice to whitelist USB, hard drives, and other accessories by their UUID/GUID, so that any non preapproved device cannot be mounted to the operating system. If suddenly all devices use the same GUID, then inherently you can no longer trust thise devices because they cannot be controlled. A GUID is 128 bits and even software developers take the time to give unique ids to their software. There is absolutely nothing wrong with unraid tied the license to a GUID. IMO of course
@TechySpeaking 5 ай бұрын
First
@matthewferrier5944 5 ай бұрын
I see you used 6 adapters, but did you try using another drive (msata) in your tests?
@SPXLabs 5 ай бұрын
No but only because the entire point folks were recommending these was for the ability to swap the mSATA drive between USB devices. However, if you do remove the msata drive and check the GUID of the usb device in Windows, it will show the same 123456791DB7 ID. Which makes me pretty confident that it's the USB device. Also also, the mSATA drive is not transparent to the host operating system. So when we looked in CentOS 7 they appear as 1 device in lsblk and I'm pretty sure the only way to achieve that is with the USB controller on the adapter running interference between the OS and the msata device. But I am willing to be wrong, so if you got some more information or counter points I'd love to hash it out. Maybe you could push me to just order a second mSATA device. lol. thoughts?