A110 - Samba changed to READ ONLY problem

[tereska]

SAMBA is working fine on my Popcorn A110 but now ONLY with read access to the shared folder.

Everything woked fine before (read and write access).

But couple days before i've lost write access somehow.

I'm connecting to popcorn/samba with correct credentials nmt:1234

I've tried this from pc box and mac box. Everywhere i have read-only mode

What could be wrong? I don't know what to do next...

PS. I have most recent software on popcorn, i've tried to change IPs, share names, workgroup names, reset to defaults.
PS2. i've checked FTP access. The same problem. Read Only mode for ftpuser:1234

[johnpoz]

Is this on the installed drive or usb connected disk?

[tereska]

(05-28-2011 06:37 PM)johnpoz Wrote:  Is this on the installed drive or usb connected disk?

this is installed (internal) drive.

[johnpoz]

Ok lets double check something - when you say "Everywhere i have read-only mode"

You actually getting access denied when you try and create a file, and you have looked at the NTFS permissions?

And not just the tri mode flag that shows read only



So if I look at the video folder on my pch a110 share and actually look at the ntfs permsissions



Are you mapping share to a drive letter, or just accessing the share like \\pch ? Post up the actual error you get when you try to create a file, or delete a file - if your saying you have read only, you can not delete a file.

[rampachuflo]

Hello, first of all sorry about my english.
I actually have exactly the same problem than you, so if you have could solve it please tell me how.
This afternoon, at home, I'll check the permissions but I remember I tried something like this and the result was "access denied"
Thanks!!

[stfarm]

I have the same problem. What is the solution.
I am unable to use FTP or map a drive like I always did.

[Rigger07]

did you get a solution?
I have same problem now... pretty sure it was after my last firmware upgrade... Sucks big time

[halfelite]

The drive has went into read only mode because the pch detected a problem with it. To return it to read/write mode, the easiest way is download gparted live, its a linux distro with a bunch of tools on it, connect the pch drive to a pc boot the gparted live cdrom and it will boot to a screen that shows the drive right click it and push check now, it will scan it for errors and return it to read/write mode.

[tradeitdamn]

solution -> http://linux.die.net/man/8/fsck.ext3