Network PC ZimaOS network drive disconnection

Insight & Feedback
1

Playing with ZimaOS and BeeLink NAS…

My Win 11 PC had a network drive share (y) from my ZimaOS NAS. I’ve lost the connection by selecting disconnect on the PC to try and resolve a share name problem.
I’ve changed the name, but how do I reconnect the NAS drive onto the PC?
Cheers

2

Have you tried this? I did a quick google search.

To reconnect a shared drive in Windows 11, first try

accessing it directly via its network path (e.g., \\Server\Share); if that fails, remap it in File Explorer by right-clicking “This PC” > “Map network drive,” ensuring “Reconnect at sign-in” is checked, and if issues persist, clear old credentials in Credential Manager or check Network Discovery/SMB settings in Control Panel

3

Can’t map network drive, as theres nothing to map. The ZimaOS-HD drive is mapped to a local drive, but not the additional NVME drive. I don’t see why renewing Windows Credentials for the IP address to the NAS is going to make any difference, as the OS-HD drive is mapped and fully readable by FE? The problem as I see it, is the additional drive is not mapped, as it was before I erroneously disconnected it. Nothing shows up to be mapped. I’ve checked the Network connections and permissions. One would assume they are correct as OS-HD share is working fine. Zero Tier is just a tunnel, so one would think is transparent as regards any sharing through it. How do I know that the additional NVME drive on the NAS is set to be available for sharing? I suppose I could run the ZimaOS client on another PC and see if mapping is available. Anyway, time to take my medicals and watch the fireworks. Cheers

4

This isn’t a Windows or credential issue
If the OS-HD share mounts fine but the NVMe disk does not appear at all, that means it’s not being shared by ZimaOS.

Please check this on the ZimaOS side:

  1. Storage > Disks
  • Confirm the NVMe disk is mounted and shows a mount point (not just detected).
  1. Storage > Shares
  • Make sure there is an explicit SMB share created for the NVMe path.
  • ZimaOS does not auto-share additional disks.
  1. Permissions
  • Verify the share has read/write enabled and is assigned to your user.

Once the NVMe disk is shared, it will immediately be visible to Windows and can be mapped via:

\\ZimaOS-IP\ShareName

ZeroTier won’t affect this, if one share works, the tunnel is fine.

If the NVMe share doesn’t appear even on another PC, the issue is 100% on the ZimaOS share configuration, not Windows.

5

Thanks for reply. I’m at a loss as to determine the NVME drive is mounted. Nothing flags up to show mounted. What indicates a drive is mounted? But it shows up in the Storage settings as everything I would expect it to be. The same goes for Shares. Nothing to click or hover mouse over to indicate this is the way to Shares. If I open a new folder on the NVME, I can share that, and it will be seen by FE. But this is not the same as Sharing the NVME, as originally done on the initial installation.

6

You’re not missing anything, this is just how ZimaOS works.

In ZimaOS there’s no visual “mounted” indicator. If the NVMe appears under Storage → Disks with size and filesystem, it is mounted.

Important bit:
ZimaOS does not share entire disks. It only shares folders (paths).

On first install, ZimaOS auto-created a folder on the NVMe and shared it, which looks like the whole drive. Once that share is removed, there’s no concept of “re-sharing the disk itself”.

That’s why:

  • Creating a folder on the NVMe and sharing it works
  • The “NVMe drive” itself no longer appears as a share

Sharing a top-level folder on the NVMe is functionally identical to sharing the whole disk.

ZeroTier isn’t involved, if one share works, the tunnel is fine.

Create a top-level folder, share it, remap in Windows, done.

1 Like