Hey all.
Updated to 1.5.3 successfully, but like many here I'm having issues with USB storage. I've done a complete reset, formatted the drive (Both Ext3/4), configured it correctly (changed the workgroup, allowed anonymous access, e.t.c) and can access the drive fine, but can't write to it?
Image below (click for larger view)
Any ideas?
Cheers.
1.5.3 - USB HDD write protected
Moderator: Moderators
Re: 1.5.3 - USB HDD write protected
Hello
I have split it up, from the news item, to make sure that it is getting seen, from the right persons.
Will try to test this myself later tonight or tomorrow. With an old NTFS partition (not recommended) is it working fine.
I have split it up, from the news item, to make sure that it is getting seen, from the right persons.
Will try to test this myself later tonight or tomorrow. With an old NTFS partition (not recommended) is it working fine.
Router: TL-WR1043ND - Gargoyle 1.5.4
AP: TL-WR1043ND - Gargoyle 1.5.4
AP: TL-WR1043ND - Gargoyle 1.5.4
Re: 1.5.3 - USB HDD write protected
Hmm.. just an update.
I've just SSH'd into the router.
I can make a folder (and files) via the term and I can access them via Samba but I still cannot write via samba.
The samba config is as follows.
Directory listing
Would the date cause a problem like this?
I've just SSH'd into the router.
I can make a folder (and files) via the term and I can access them via Samba but I still cannot write via samba.
The samba config is as follows.
Code: Select all
[global]
netbios name = Gargoyle
workgroup = WORKGROUP
server string = Gargoyle
syslog = 10
encrypt passwords = true
passdb backend = smbpasswd
obey pam restrictions = yes
socket options = TCP_NODELAY SO_KEEPALIVE IPTOS_LOWDELAY
unix charset = UTF-8
preferred master = yes
local master = yes
domain master = yes
os level = 20
security = user
null passwords = yes
map to guest = Bad User
guest account = nobody
invalid users = root
smb passwd file = /etc/samba/smbpasswd
[sda2]
path = /tmp/usb_mount/dev_sda2
create mask = 0777
directory mask = 0777
read only = no
guest ok = yes
browseable = yes
Code: Select all
drwxr-xr-x 4 root root 4096 Feb 12 19:35 1a9e7a74-358f-488c-abf1-f87873e3a1d
lrwxrwxrwx 1 root root 50 Jan 1 1970 dev_sda2 -> /tmp/usb_mount/1a9e7a74-358f-488c-abf1-f87873e3a1d
Re: 1.5.3 - USB HDD write protected
Maybe.mpmc wrote:...
Would the date cause a problem like this?
Please try to check the system->time page in the webinterface to see if the ntp-server is failing.
Router: TL-WR1043ND - Gargoyle 1.5.4
AP: TL-WR1043ND - Gargoyle 1.5.4
AP: TL-WR1043ND - Gargoyle 1.5.4
Re: 1.5.3 - USB HDD write protected
Sorry for the late reply, busy lately
The ntp is updating correctly no issues.
Oh I forgot to mention the router is a wr1043nd version 1.7.
The ntp is updating correctly no issues.
Oh I forgot to mention the router is a wr1043nd version 1.7.
Re: 1.5.3 - USB HDD write protected
Thanks for the report
I have also reported similar problems
Eric has made some changes in the repository but I think there are still bugs in this part of the code
I have also reported similar problems
Eric has made some changes in the repository but I think there are still bugs in this part of the code
- DoesItMatter
- Moderator
- Posts: 1373
- Joined: Thu May 21, 2009 3:56 pm
Re: 1.5.3 - USB HDD write protected
Enable both CIFS+NFS
Allow anonymous access read/write
Save Changes
REBOOT router <-- necessary for changes to take effect
Then try again.
Allow anonymous access read/write
Save Changes
REBOOT router <-- necessary for changes to take effect
Then try again.
Soylent Green Is People!
2x Asus RT-N16 = Asus 3.0.0.4.374.43 Merlin
2x Buffalo WZR-HP-G300NH V1 A0D0 = Gargoyle 1.9.x / LEDE 17.01.x
2x Engenius - ESR900 Stock 1.4.0 / OpenWRT Trunk 49400
2x Asus RT-N16 = Asus 3.0.0.4.374.43 Merlin
2x Buffalo WZR-HP-G300NH V1 A0D0 = Gargoyle 1.9.x / LEDE 17.01.x
2x Engenius - ESR900 Stock 1.4.0 / OpenWRT Trunk 49400
Re: 1.5.3 - USB HDD write protected
Sorry for the late reply.
I've tried what was suggested above and I'm still having these issues.
I know the drive works fine in Linux and it worked on the old release (1.5.2).
I've tried what was suggested above and I'm still having these issues.
I know the drive works fine in Linux and it worked on the old release (1.5.2).