Issue when removing Airvideo

You might need to consult your HDX users guide. The HDX BD1 supports CIFS and NFS, so it should be able to directly access your shares. You can also try ReadyDLNA.

Thanks,

the problem is it does connect, and shows to Folders; only it does not show the data folders which contain my media files (and which show up on my mac), but only the folders which were created for AirVideo. Seems the uninstall from the AirVideo plugin did not fully restore the systems to it's defaults

Could you download your Config (System > Config Backup), extract the zip contents and post the contents of "/etc/frontview/samba/Shares.conf" ?

Hi,

this is the content:


[Software]
path = /c/Software
comment = "Software Packages"
oplocks = 1
admin users = "admin","Administrator"
writeable = 1
guest ok = 1

[backup]
path = /c/backup
comment = "Backup Share"
oplocks = 1
force create mode = 0666
create mask = 0666
force directory mode = 1777
directory mask = 1777
admin users = "admin","Administrator"
writeable = 1
guest ok = 1

[media]
path = /c/webroot
comment = "Media Server Share"
oplocks = 1
force create mode = 0666
create mask = 0666
force directory mode = 0777
directory mask = 0777
admin users = "admin","Administrator"
writeable = 1
guest ok = 1

[test]
path = /c/test
comment = "testdesc"
oplocks = 1
admin users = "admin","Administrator"
writeable = 1
guest ok = 1

[webroot]
path = /c/webroot
admin users = "admin","Administrator"
writeable = 1
Many thanks for looking into this

This is a variant of an issue seen on previous firmware emerging again.

Do you have SSH access? If so the best way to fix this issue would be using that. Using "vi" to modify that file to fix it and also modifying config files for other protocols that use the media share if their configuration has been mucked up as well.

If not, you could try renaming the media share under Shares > Share Listing, clicking apply, then renaming it back. Don't try anything else to "fix" the issue. Doing the wrong thing can lead to data loss.

If renaming the share doesn't fix the problem then remote access will be needed to your NAS to fix the issue.

Thanks mdgm,

not sure how to proceed regarding the ssh access and vi. the thought of having dataloss however is not very appealing. Could i change the config file on my mac and then do the reverse steps (restore config) you asked me to do?

any instructions regarding the remote access would be appreciated.

Wouldn't be a bad idea to put a big warning in the addon's section if this is a frequent issue- if i'd known it can corrupt the basic functionality of the nas, i would have stayed away from even trying.

Cheers

For remote access you would put the NAS in tech support mode (http://www.readynas.com/kb/faq/boot/how_do_i_use_the_boot_menu), forward port 23 to the NAS and let tech support know your IP.

This is a different issue I think to another one that was fixed in a previous firmware update but with some of the same symptoms.

Renaming the share did the trick. Thanks a lot mdgm!