Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Unraid 7.4.0: Can a Lexar E300 USB NVMe enclosure be used for licensing?

Featured Replies

Hi all. Before buying a paid Unraid license, I’d like to check whether a USB NVMe enclosure is a supported licensing device, particularly if its bridge serial was changed after two units reported the same one.

I’m testing two 16 GB Intel Optane Memory modules (MEMPEK1W016GA) in Lexar E300 enclosures with JMicron JMS583 bridges. The setup is a UGREEN DXP4800 GT and an Intel MacBook Pro test machine. I chose the small Optane modules for repeated imaging and restore tests while developing DisNDat, an Unraid backup and recovery plugin.

Both enclosures reported the same USB serial and Unraid GUID. The factory serial looked date-like, but I don’t know how Lexar assigns it. I changed the USB serial reported by one enclosure’s bridge, not the Optane module’s identity. The new GUID differed from the other unit’s and persisted after unplugging and reconnecting. Unraid 7.4.0 identified the test device as “Lexar E300” / “USB Flash” and accepted one 30-day trial on that identity. That’s what I observed; I don’t know whether it qualifies for paid licensing.

I’ve read the Licensing and Internal Boot FAQs. A few questions remain:

1. Are USB-to-NVMe enclosures eligible for a paid USB-bound key, either as boot media or solely for licensing alongside internal eMMC boot? Is a persistent, unique GUID sufficient, or must the serial be manufacturer-assigned? Does trial acceptance tell me anything about paid eligibility?

2. Can I move this exact USB device, with its identity unchanged, from the test machine to the NAS and keep the existing registration, running it on only one machine at a time? Is there a supported procedure, and does it differ for trial and paid keys or for eMMC boot with the enclosure attached only for licensing?

3. If the NAS already has a separate registration, can this previously trialed enclosure become its licensing device through a supported migration, or should I leave that registration alone and use different media or TPM? I don’t want to invalidate anything by testing the replacement flow.

4. If this setup isn’t supported, what would you recommend for endurance-focused boot media and a separately licensed physical or virtual plugin test environment? Is there published guidance for 16 GB boot media beyond 7.4?

I’m not looking for ways to change identifiers again, reset a trial, or run multiple servers on one key. I want to keep the current device identity unchanged and buy the appropriate license once I know what’s supported. If it helps, I can provide the full GUID and redacted registration screenshots privately to Unraid Support. Thanks.

Edited by Majik-Mike
Bad paragraphing

1. Unraid builds the GUID from the USB vendor ID, product ID and serial number. It doesn't check what kind of device it is, so an enclosure can be accepted, as the Trial showed.

For a paid key we recommend a device with a unique serial assigned by the manufacturer. Your enclosures came with a shared serial, so other units may already have that GUID. A serial you set yourself may be reset by a bridge firmware update or reflash. If that happens, the GUID changes and the key would need a transfer. So we wouldn't recommend this enclosure as a paid license device, whether you boot from it or use it only for licensing. Trial acceptance only shows the GUID is valid and unused, not that it's a good long-term license device.

2. The license follows the device, not the machine. You can move the same device to another server and keep the registration, as long as you run it on one server at a time. This works the same for Trial and paid keys. With internal boot, the licensing device just needs to stay connected.

3. If the NAS already has its own registration, I would leave it alone. Moving that key to a different device is a license transfer, and the old device is blacklisted afterward. For a separate test environment, a separate license on its own device is the cleaner option.

4. For endurance, on 7.3 and later you can boot from an internal SSD and license with the motherboard TPM (Intel PTT or AMD fTPM), so no USB flash wear is involved. If you prefer USB licensing, a name-brand flash drive with a unique serial is the safest choice. For a VM test environment, you can pass a dedicated flash drive through to the VM. 16 GB should be more than enough boot space for current releases.

7 hours ago, JorgeB said:

It doesn't check what kind of device it is

This is not totally correct...

Although the running UNRAID does not check it, the USB Creator does.

At least more recent versions refuse installation to certain compartments.

So it is wise, to keep an old edition still in reach...

(Once you have successfully created a stick, it does work)

31 minutes ago, MAM59 said:

At least more recent versions refuse installation to certain compartments.

Not sure what you mean by compartments; the USB tool typically has no issue installing to most USB devices, including external HDD/SSDs, at least not for me.

4 minutes ago, JorgeB said:

Not sure what you mean by compartments

enclosures?

The USB thing you can put your NVME inside

Yes, the tool works fine with those, but like mentioned, they may not have a unique GUID and I don't recommend using them.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.