Page 1 of 1

'This folder is not currently available or cannot be read'

PostPosted: Tue May 05, 2020 9:44 pm
by mikethep
Hello, newbie here. Serviio has been running fine on my LG TV, using video files on a WD HDD connected to my MacBook Pro 2018 running Os 10.15.3. Suddenly tonight nothing will play on the TV and I'm getting the above error message on the Shared Folders page. There's nothing wrong with the HDD though - the MBP is seeing it fine, and VLC will happily play any file on it - mostly .mp4 with the occasional .mkv . I upgraded to 2.1 yesterday, don't know if that's relevant.

Would be grateful for any advice.

Re: 'This folder is not currently available or cannot be rea

PostPosted: Tue May 05, 2020 11:51 pm
by atc98092
That sounds like a permissions issue between Serviio and the external drive. I don't know enough about MacOS (as in nothing), so I can't offer any idea what to check. But it does sound like an update (Apple?) might have changed permissions for an attached device.

Re: 'This folder is not currently available or cannot be rea

PostPosted: Wed May 06, 2020 12:41 pm
by mikethep
Hello, thanks for replying. Nothing had changed with permissions. But I ran the disk through Disk Utility and it turned out that it was failing. Need to do some quick backing up! Interesting that Serviio spotted it before the OS did...

Re: 'This folder is not currently available or cannot be rea

PostPosted: Thu May 07, 2020 4:40 pm
by zip

Re: 'This folder is not currently available or cannot be rea

PostPosted: Thu May 07, 2020 9:08 pm
by mikethep
Yes I am. I used that link to set up a new external HDD, which is working fine. Thanks.

Re: 'This folder is not currently available or cannot be rea

PostPosted: Wed Jun 24, 2020 2:36 am
by atc98092
NIGASIAQA wrote:That sounds like a permissions issue between Serviio and the external drive. I don't know enough about MacOS (as in nothing), so I can't offer any idea what to check. But it does sound like an update (Apple?) might have changed permissions for an attached device.


Yes, it's a permissions issue. But it's Java permissions, not the drive specifically itself. It's something that Apple changed on a recent MacOS update.