NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
media share set to webroot after 4.2.19 upgrade
Hello,
I have a ReadyNAS Ultra 4 Plus and I just upgraded to RAIDiator 4.2.19.
Now my media share is the same as the webroot share.
I was going to delete and re-add the media share but a dialog box gave
the following warning:
Deleting the selected share(s) will destroy all data the share(s). Are you
sure you want to delete the share(s)?
It sounds like it will delete all the files in the share and I didn't want to do that.
I looked in /etc/frontview/samba and found Shares.conf and Shares.conf-sav
with what appears to be incorrect data (the files are identical)
[backup]
path = /c/backup
comment = "Backup 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
[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"
available = 0
valid users = "admin","Administrator","nobody"
write list = "admin","Administrator"
I changed the media path in both files from "/c/webroot/" to "/c/media" and
then did a "/etc/init.d/samba restart"
At this point everything was back to mormal, I could see all my media files
in "/c/media" through the media share.
I wanted to make sure my fix would survive a reboot, so I rebooted the NAS.
The trouble came back, Shares.conf and Shares.conf-sav returned to their
incorrect data fill.
Does anyone know the proper way to fix this trouble?
In case it's is relevant, I have the following add-ons installed:
PHP. PHP+Mysql Support
Subsonic. Media Stream Server
Transmission. P2P Client
WordPress. Blog Software
Thanks
Jim
I have a ReadyNAS Ultra 4 Plus and I just upgraded to RAIDiator 4.2.19.
Now my media share is the same as the webroot share.
I was going to delete and re-add the media share but a dialog box gave
the following warning:
Deleting the selected share(s) will destroy all data the share(s). Are you
sure you want to delete the share(s)?
It sounds like it will delete all the files in the share and I didn't want to do that.
I looked in /etc/frontview/samba and found Shares.conf and Shares.conf-sav
with what appears to be incorrect data (the files are identical)
[backup]
path = /c/backup
comment = "Backup 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
[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"
available = 0
valid users = "admin","Administrator","nobody"
write list = "admin","Administrator"
I changed the media path in both files from "/c/webroot/" to "/c/media" and
then did a "/etc/init.d/samba restart"
At this point everything was back to mormal, I could see all my media files
in "/c/media" through the media share.
I wanted to make sure my fix would survive a reboot, so I rebooted the NAS.
The trouble came back, Shares.conf and Shares.conf-sav returned to their
incorrect data fill.
Does anyone know the proper way to fix this trouble?
In case it's is relevant, I have the following add-ons installed:
PHP. PHP+Mysql Support
Subsonic. Media Stream Server
Transmission. P2P Client
WordPress. Blog Software
Thanks
Jim
78 Replies
Replies have been turned off for this discussion
ewok wrote: It seems to be caused by the Subsonic addon. I installed it on a NAS running 4.2.19-T5 (it's what I had on hand), rebooted, and at least the CIFS and HTTP service config files were rewritten with the media share pointed to webroot.
Note that the subsonic addon was last updated in March 2011, and that this issue has only been reported since the release of 4.2.19.
While the issue is clearly related to the addons system (/c/webroot is created and used by many of Super-Poussin's addons) the root cause appears to be some incompatibility introduced in 4.2.19 related to addon installation ( FYI I also have subsonic installed - after upgrading to 4.2.19 my setup continues to be correct)- I have 4.2.19 on a Pro and host several sites and everything was working fine.
I then installed MyBB as an Add-On and had loads of problems in that the files in my website folder were inaccessible. The installation of MyBB rested a webroot folder and thats when my problems began. I removed MyBB from my system but the problems still remained. I have been trying to sort this problem out for about a day and its so frustrating. I think at the moment I will steer clear of certain Add-Ons. Singularity wrote: I have 4.2.19 on a Pro and host several sites and everything was working fine.
I then installed MyBB as an Add-On and had loads of problems in that the files in my website folder were inaccessible. The installation of MyBB rested a webroot folder and thats when my problems began. I removed MyBB from my system but the problems still remained. I have been trying to sort this problem out for about a day and its so frustrating. I think at the moment I will steer clear of certain Add-Ons.
Can you downgrade to 4.2.17 and see if your shares return as expected?- I don't really want to downgrade.
I'm quite happy with 4.2.19, my problem began when I installed MyBB.
I have a folder called 'websites' which although I deleted its share the folder remains. Its not really causing a problem - just a bit of house keeping really.
Thanks - I've rolled back to 4.2.17, which is what I had previous to my last update.
This has not resolved the issue. I'm still not able to access the files that were in my media folder. I could try move them manually to another shared folder using ssh, but I'd feel far safer if I could just work out how to resolve the issue properly. - I tried what was originally suggested on the first post. Manually corrected Share.conf and Share.conf-sav.
Restarted samba and it worked, then restarted the whole NAS, and it seems to have actually worked. Now I just have an extra webroot share... I guess I'll remove that from these files, as if I try delete it through the web interface it'll try to delete the actual files.
Feels like a pretty dirty fix though. Is this hack going to cause issues with future updates? - @undave (& others):
Do you also get the message "Unsuccsessful mounting ftp share" when logging in to Frontview?
How do I access the conf-files in Samba (Don't even know what Samba is...) :oops:
/Horpe - I don't get that message, no.
To access the conf files you need to enable ssh access to your NAS. I think it's a plugin you install, and then you can use a program like putty (if you're using windows) or just the terminal if you're using osx/linux to connect to the NAS.
It's kind of like a remote command line.
Once you have that, you should be able to find the files with this command
cd /etc/frontview/samba/
then view them with
vi Share.conf
(if you're unsure on vi commands, check google)
Samba is the non-windows based implementation of shared folders on a network. - All I can say is i am in the same boat.
Upgraded to 4.2.19 and I was playing around with Twonky - next thing I have lost the folders in my \media share.
Uninstalled Twonky and down graded to 4.2.17 no luck. stewartbrown wrote: All I can say is i am in the same boat.
Upgraded to 4.2.19 and I was playing around with Twonky - next thing I have lost the folders in my \media share.
Uninstalled Twonky and down graded to 4.2.17 no luck.
Go into Frontview and rename the media share. Can you open that new share and still see your files?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
