2 x PC
2 x iPhone
1 x iPad
2 x RoPieee
1 x Oppo UDP-203
Number of Tracks in Library
450,000 tracks
Description of Issue
I recently upgraded my machine’s software RAID setup to using Division-M’s Drive-Bender (I was running Flexraid T-Raid previously with no issues).
A few things have come up since:
Issue 1. Roon can’t browse the drive created by Drive-Bender.
clicking on drive X, get the Unauthorized error (see pic)instead of the directory list.
Permissions on that drive have the permission: Everyone = Full control. and it is browsable on the machine. (This used to work when with other RAID software)
Of note that’s different to my previous setup is the driver/device name under the drive name, in this case “StorLib Virtual Storage” (Perhaps their API doesn’t expose something that is expected and Roon errors?)
Any chance anyone from Roon can help with this? I’m completely stuck.
I am assuming with this many different issues, it is most likely an installation corruption or something like that, but I didn’t want to just uninstall/reinstall as I don’t want to lose my database.
I have the data, as in, it’s still where it’s always been. I haven’t changed anything.
So network setting changes either.
Roon (on the server) can’t see a local drive (on the server)
I am 99% it’s a driver issue and the roon file explorer software is failing when it is attempting to read the drive information.
It would require someone from Roon to look at the logs.
It is possible for someone from support to please help (a paying customer)
Thanks
As these boith work and Windows Explorer and multiple other devices (Apple TV etc). I can only assume it’s a Roon issue.
Is there any way you can add support for the virtual drive exposed by DriveBender please?
(Just to reiterate, permission are set to Everyone-full control, so it’s not a permissions issue)
Domain Administrator account.
and share and security are set to everyone/full control.
As I mentioned, this works fine on anydrive where the driver isn’t ‘StorLib Virtual Storage’ (which is what is changed)
I am 99% sure the issue lies with the virtual driver not exposing properties which Roon expects when it attempts to read the drive.
Could a Roon dev please chime in?
Thanks