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
- I too can confirm this problem, just got a new Ultra 6, upgraded to 4.2.19.
INstalled addons: PHP, Transmission, istatd, ssh
All my shares, apart from addons-config, <<usershare>>, backup and media now point to the addons-config after reboot.
two new shares: share and stuff <now point to addons-config>.
Any ideas on a fix?
here is the output from the Shares.conf file:[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/media
comment = "Media Server 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
[share2]
path = /c/addons-config
comment = "My Stuff"
oplocks = 1
admin users = "admin","Administrator"
writeable = 1
guest ok = 1
[stuff]
path = /c/addons-config
oplocks = 1
admin users = "admin","Administrator"
writeable = 1
guest ok = 1
I'm going to downgrade back to 4.2.17 and see if the issue remains...
That works, I downgraded back to 4.2.17 reset my shares in frontview, and rebooted the NAS. Upon reboot the shares remained as they should.
So it would appear that something went a bit buggy with the 4.2.19 firmware, as it seems that everyone who has a problem, uses 4.2.19, so I'm going to stay on the older (but samba stable) 4.2.17. - I had the same problem. I have a ReadyNAS Ultra 4+ and I have never had Subsonic installed.
I did as slacker suggested:
I went to Frontview > Share listing and changed the name of my media share to media2. Then I changed it back to media. That seems to do the trick. It's a temporary workaround, as this needs to get fixed in the firmware, but at least I can now access my files. I also had to restart windows for it to refresh samba or something.
Now, I do not dare restart my ReadyNAS in case the same thing happens. It started after I rebooted my ReadyNAS. - You should be fine restarting with the different name. Only problem is that any services you have that point to \\nas\media are now broken...
- I renamed my shares, and rebooted, and those broke also, so just changing the share name wont work on a permenant basis.
The only way I found out for myself was to downgrade to FrontView 4.2.17. - can you try http://www.readynas.com/contributed/sup ... 4.5.04.bin
It should prevent 4.2.19 to try to create a share in a dirty way - Hmm, will it reset the dirty code? :shock:
What are the prerequisitions? Rename share? Uninstall previous instances of Subsonic?
Please tell us more...
Cheers /Horpe - It will add a webroot share declaration in samba config file
- You can upgrade
- How about other of your plugins? I did not have Subsonic installed, but I did have Transmission installed, which had a folder in webroot.
- Yep, I too do not have subsonic installed, yet I have your Transmission and the istat addon...
I'd like to go back to the latest frontview, rather than the older 4.2.17 which is what I am using to not get this issue.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
