media share set to webroot after 4.2.19 upgrade

[undave]

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.

[undave]

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?

[Horpe]

@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...)

/Horpe

[undave]

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.

[stewartbrown]

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.

[slacker]

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?

[ranko]

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:

Code: Select all

[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.

[iernie]

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.

[slacker]

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...

[ranko]

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.

[super-poussin]

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

[Horpe]

Hmm, will it reset the dirty code?
What are the prerequisitions? Rename share? Uninstall previous instances of Subsonic?
Please tell us more...

Cheers /Horpe

[super-poussin]

It will add a webroot share declaration in samba config file

[super-poussin]

You can upgrade

[iernie]

How about other of your plugins? I did not have Subsonic installed, but I did have Transmission installed, which had a folder in webroot.