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 gavethe following warning:Deleting the selected share(s) will destroy all data the share(s). Are yousure 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-savwith 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" andthen did a "/etc/init.d/samba restart"At this point everything was back to mormal, I could see all my media filesin "/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 theirincorrect 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 SupportSubsonic. Media Stream ServerTransmission. P2P ClientWordPress. Blog SoftwareThanksJim

Hmm, Subsonic installed and 4.2.19......These two threads might be of interest...http://www.readynas.com/forum/viewtopic.php?f=23&t=56886http://www.readynas.com/forum/viewtopic.php?f=23&t=57083Cheers!/Horpe

Thanks for the quick response Horpe. It looks like it may the the first reboot since Subsonic rather than the 4.2.19 upgrade ... perhaps both. I will keep poking around to see what I can find ... but it took both brain cells to get this far, so I may be at my limit. :? Jim

I can confirm I have the same issue after the 4.2.19 update. I haven't tried to change the content of those files, but I was about to, before I found this thread. Only have two plugins installed, PHP5 and NAS Monitor. Not really sure where to go from here. Think I'll make a new share, and move the whole share into that. No other ideas how to fix it?

Only have two plugins installed, PHP5 and NAS Monitor.Oh, that's interesteing, :o You have the problem without Subsonic installed!? That means it's not nescessary Subsonic that is the problem. Maybe time to revert to 4.2.18 and see what happens? Is that doable, u think?BTW, undave: Which one folder(s) can you see in your share?Cheers!/Horpe

I can see the contents of webroot in my media share. It's just a single folder.loadavgsame as Jim

media share set to webroot after 4.2.19 upgrade

78 Replies

Replies have been turned off for this discussion

SergV
Aspirant
Sep 25, 2011
I have the same problem after installing transmission add-on.
Problem - media share is c/webroot, but not c/media
Reason - file /etc/frontview/samba/Shares.conf was changed:

#diff Shares.conf old/Shares.conf.old
14c14
< path = /c/webroot
---
> path = /c/media
19,20c19,20
< force directory mode = 0777
< directory mask = 0777
---
> force directory mode = 1777
> directory mask = 1777

If I change Shares.conf and Shares.conf-sav to orignal and I stop and restart samba, the problem resolved. But after rebooting NAS the problem exists and the configuration files are modified. It is look like this configuration files are saved and they are restored on boot. Do somebody know how to resolve the problem?
I think it is some problem in add-in installation mechanism.
jj89
Aspirant
Sep 25, 2011
I updated Subsonic (and Transmission) and tried a reboot. The trouble came back. I checked Shares.conf in /etc/frontview/samba and found the media share was pointing to /c/webroot.

Super-poussin mentioned that the update would add a webroot share declaration in the samba config file. My Shares.conf only had backup and media shares, but I liked where super-poussin was going.

I copied and pasted the media share stanza in Shares.conf, then modified it into a webroot share (probably easier with the GUI), did a reboot, and everything was fine.

So it would seem as long as you have a webroot share, your media share is safe.

Jim
super_poussin
Virtuoso
Sep 25, 2011
Can you take a look in addons subdirectory (in samba dir) and see if there's a webroot.conf ?

super_poussin

Virtuoso

Sep 25, 2011

jj89 wrote:
I updated Subsonic (and Transmission) and tried a reboot. The trouble came back. I checked Shares.conf in /etc/frontview/samba and found the media share was pointing to /c/webroot.

Super-poussin mentioned that the update would add a webroot share declaration in the samba config file. My Shares.conf only had backup and media shares, but I liked where super-poussin was going.

I copied and pasted the media share stanza in Shares.conf, then modified it into a webroot share (probably easier with the GUI), did a reboot, and everything was fine.

So it would seem as long as you have a webroot share, your media share is safe.

Jim

jj89 wrote:
I updated Subsonic (and Transmission) and tried a reboot. The trouble came back. I checked Shares.conf in /etc/frontview/samba and found the media share was pointing to /c/webroot. Super-poussin mentioned that the update would add a webroot share declaration in the samba config file. My Shares.conf only had backup and media shares, but I liked where super-poussin was going. I copied and pasted the media share stanza in Shares.conf, then modified it into a webroot share (probably easier with the GUI), did a reboot, and everything was fine. So it would seem as long as you have a webroot share, your media share is safe. Jim

the addon add it in samba/addons but I discover that the main problem on 4.2.19 is that samba no more read files in addons subdir :(

SergV
Aspirant
Sep 25, 2011
super-poussin wrote:
Can you take a look in addons subdirectory (in samba dir) and see if there's a webroot.conf ?

There are some files in /etc/frontview/samba/addons with configurations data for webroot and addons-config (all name may be incorrect as I have not connect to my NAS now). There is not any problem with webroot and addons-config share. The problem is with media share.
I think you can easy repeat problem:
1) Do factory default
2) Reboot
3) copy some files to media share.
3) install transmission add-in
4) reboot
5) see on media share.
super_poussin
Virtuoso
Sep 26, 2011
I can not reset my units to factory or You will not have addons for a long time :P

I will try to create a ddon which write everything in Shares.conf instead of using sub directory, but I clearly hope regression introduced in 4.2.19 will be solved quickly by jedi
super_poussin
Virtuoso
Sep 26, 2011
try Missing

super-poussin wrote:
Can you take a look in addons subdirectory (in samba dir) and see if there's a webroot.conf ?

super_poussin

Virtuoso

Sep 26, 2011

SergV wrote:
I have the same problem after installing transmission add-on.
Problem - media share is c/webroot, but not c/media
Reason - file /etc/frontview/samba/Shares.conf was changed:
#diff Shares.conf old/Shares.conf.old
14c14
<   path = /c/webroot
---
>   path = /c/media
19,20c19,20
<   force directory mode = 0777
<   directory mask = 0777
---
>   force directory mode = 1777
>   directory mask = 1777
If I change Shares.conf and Shares.conf-sav to orignal and I stop and restart samba, the problem resolved. But after rebooting NAS the problem exists and the configuration files are modified. It is look like this configuration files are saved and they are restored on boot. Do somebody know how to resolve the problem?
I think it is some problem in add-in installation mechanism.

SergV wrote:
I have the same problem after installing transmission add-on. Problem - media share is c/webroot, but not c/media Reason - file /etc/frontview/samba/Shares.conf was changed: #diff Shares.conf old/Shares.conf.old 14c14 < path = /c/webroot --- > path = /c/media 19,20c19,20 < force directory mode = 0777 < directory mask = 0777 --- > force directory mode = 1777 > directory mask = 1777 If I change Shares.conf and Shares.conf-sav to orignal and I stop and restart samba, the problem resolved. But after rebooting NAS the problem exists and the configuration files are modified. It is look like this configuration files are saved and they are restored on boot. Do somebody know how to resolve the problem? I think it is some problem in add-in installation mechanism.

It's not an addons problem it's a 4.2.19 regression :P

SergV
Aspirant
Sep 26, 2011
super-poussin wrote:

It's not an addons problem it's a 4.2.19 regression :P

Can you explain, what do you mean?

super-poussin wrote:
It's not an addons problem it's a 4.2.19 regression :P

super_poussin

Virtuoso

Sep 26, 2011

simple :

Samba is configured to read Shares.conf but also /etc/frontview/samba/addons/addons.conf

extract of /etc/samba/smb.conf


include = /etc/frontview/samba/smb.conf.%a
include = /etc/frontview/samba/Shares.conf
include = /etc/frontview/samba/Shares.conf.%U
include = /etc/frontview/samba/addons/addons.conf

All the addons are using /etc/frontview/samba/addons/addons.conf so the Shares.conf only contains default shares and shares created by frontview

example :

/etc/samba/addons/addons.conf


include = /etc/frontview/samba/addons/addons-config.conf

and /etc/samba/addons/addons-config.conf


[addons-config]
  path = /c/addons-config
  oplocks = 1
  force create mode = 0666
  create mask = 0666
  force security mode = 0666
  force directory mode = 0777
  directory mask = 0777
  force directory security mode = 0777
  admin users = "admin","Administrator"
  writeable = 1
  guest ok = 1
  vfs objects = recycle
  recycle:versions = 1
  recycle:repository = Recycle Bin
  recycle:subdir_mode = 777
  recycle:keeptree = 1
  recycle:directory_mode = 777

sonds like samba in 4.2.19 is not reading the addons.conf and do bad things at boot
by default the nas at boot take a look in /c/ and if a directory is not declared as share it add it in Shares.conf but with 4.2.19 it does silly things

Forum Discussion

media share set to webroot after 4.2.19 upgrade

78 Replies

Related Content

Upgrade Nighthawk M1

WC7600 upgrade

Upgrading from OS6.1.8

GS724T v4 Firmware upgrade

upgrade Firmware WN3000RP v3

NETGEAR Academy

ProSupport for Business