NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

jj89's avatar
jj89
Aspirant
Sep 18, 2011

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

78 Replies

Replies have been turned off for this discussion
  • I just bought a Ultra and Iäm totally newbe to Linux.
    I all did I was to install TRANSMISSION and I was suprised that it did not work (permission error) and some kind of need to login with SSH and do unix-commands---bah. I have not tried that yet

    However the installation of TRANSMISSION also broke my shares and I'm very surprised that singel install of a program can brake the main feature of this NAS.

    But here is little fix for all that are afraid that they have lost their shares.
    1. Go into frontview.
    2. Rename the media share to wahtever
    3. Rename it back to "media"
    4. Do not reboot
    Now it is working again (a login/logout on the samba clients might be needed)

    But as soon as I restart the problem is back, but I hope I dont have to restart until there is a new firmware that fixes this (or do I still have to edit some conf-files to repair this even after the new FW?)
  • I got it when i installed Transmission. I just created a new share but i want to fix it so... I have tried uninstalling Transmission, didnt help though.
  • I had exactly the same issue - v4.2.19 is a buggy PoS release, that's a fact.

    Move your content to another share then delete the share in the web UI.

    There's another possible fun part of this stupid bug: if the share you moved your content does not show anything then first rename it then name it back in the web UI. Voila' everything is there again.

    BTW these are really lame bugs, obvious signs of the lack of proper testing (and/or the usual signs of outdated/cross-branched junk Debian sources.)

    FYI it's not a criticism of the maintainer, I'm criticizing Netgear for being a cheap@ss company and not assigning enough resources to this division.
  • mdgm-ntgr's avatar
    mdgm-ntgr
    NETGEAR Employee Retired
    It's a compatibility issue with add-ons. The webroot share is only created by some community add-ons.

    No need to move content to another share then delete.

    Simply rename the media share, click Apply and rename it back again.

    It's addressed with 4.2.20 beta so if you update to that firmware the issue won't re-occur.
  • I didn't read through this whole thread, but I fixed this issue simply by fixing my /etc/frontview/samba/Shares.conf, then making the file immutable with the following command:

    chattr +i /etc/frontview/samba/Shares.conf


    That keeps the file from being edited.
    Rebooted a number of times and my share is still there.

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More