I had another power outage Sat 9 May at 18.30 BST and lost my Zen Mini Music Library. Please can Roon re-connect (restore it) it please? In storage directory on Roon, the message says:
\\zenmini\music
This drive is not available. Check the drive or edit this folder if it's been moved.
Every single time there is a power cut, the Roon Nucleus loses connection with my music library contained in the Innuos Zen Mini Mk3. Can this ongoing problem be resolved as it is a pain to have keep reverting to Roon after a power outage?
Thanks
Adrian Lamb
Tell us about your home network
· BT EE Router with 3 extenders. Hub Manager Screen: 192.168.1.254
The music folder is unavailable and no longer present on the network.
Can you access the shared folder using a laptop or PC? If the Zen Mini listed as a device in the BT router? Is it online, i.e., connected to your network? Enter http://zen or http://zen.local in the browser address bar to check.
Thanks for reaching out. Is the Zenmini still showing as online when you try to access it’s web interface? According to your screenshot, it looks like the zenmini is not reading as online. If you try to use the IP address instead of hostname, does that work? If so, you can try to set up a Reserved IP address in your router to ensure that the IP remains the same.
Please note that power outages can adversely affect the Nucleus and cause database corruption. If you have frequent power outages, please consider adding a UPS so that the Nucleus is not affected by the outages.
My previous reference is as above. This problem is still not resolved. Roon need to work out how the Nucleus can read my zen Mini music library following the power outage. This issue has been going on now for 2 weeks and if it is not resolved I will need to escalate this issue. Roon have successfully re-connected to before in January 26 when a similar power outage happened. I would ask Roon to follow the same procedure to re-connect to my Innuos Zen Mini Mk3 Music Library directory address: \\zenmini\music.
Tell us about your home network
· EE Router: Alison and Adrian WiFi . Main Hub with 3 extenders (one feeds into Innuos). All on same wi Fi network as the Nucleus and Innuos. Hub Manager Screen: 192.168.1.254
“Roon need to work out how the Nucleus can read my zen Mini music library following the power outage. This issue has been going on now for 2 weeks and if it is not resolved I will need to escalate this issue.”
Alternatively, you could get an uninterruptible power source and and take responsibility yourself.
Thank you for following up. Let us walk you through a permanent fix for this.
The root cause is that after a power outage, your Zen Mini comes back online and may receive a different IP address from your router. The Nucleus is still trying to reach it by name (\zenmini\music), but your network may not resolve that name correctly — so the connection fails.
The fix has two steps:
Step 1 — Give your Zen Mini a fixed IP address
Open your router's admin page by typing http://192.168.1.254 in your browser
Find the list of connected devices and locate your Zen Mini
Assign it a reserved/static IP — this ensures it always gets the same address after every reboot or power outage (the exact menu name varies by router model — look for something like "DHCP Reservations" or "Static IP Leases")
Note down the IP address you assigned, for example 192.168.1.50
Step 2 — Update the music folder path in Roon to use the IP instead of the name
In Roon, go to Settings → Storage
Find the \\zenmini\music folder and click Edit
Replace zenmini with the IP address you assigned, so it becomes \\192.168.1.50\music
Save
After this, even if your network has trouble resolving the Zen Mini's name after a power cut, Roon will always find it by its fixed IP address directly.
Just checking in on this. Were you able to reserve a fixed IP for your Zen Mini in the router, and then update the Roon storage path from \zenmini\music to that IP address in Settings → Storage? If you ran into any trouble with those steps, reply with what you’re seeing and we can take another look. Thanks.
We have not heard back from you, so we will go ahead and close this thread due to inactivity. If you need further assistance, please submit a reopen support request via the form link and specify that the issue be reopened. Thank you.
