Hi all,

 

I recently upgraded unRaid from 4.7 to 6.1.7.  I followed the instructions provided and I was up and running again in a few hours. I transferred my Plus licence key to the appropriate folder.  But now the only share I had is read-only.  It does not matter if I configure it as read/write in the different config files, I still can't move/delete/rename/modify/add files.  On my main Mint Linux box, I mount the share with the option --rw, to no avail.  I ran the reiserfsck on all 3 disks, and no corruption showed.  The only way I can move/delete/rename/modify/add files is by telneting to the server as root.  Also I created another share to be used as a Time Machine for my MacBook backups.  This worked with no problem.  This indicates it is a share permissions issue.  I am at a loss on how to resolve this.

There are these lines in the syslog that may shed some light:

 

Feb  7 18:58:33 Tower emhttp: shcmd (144): echo '"/mnt/disk1" -async,no_subtree_check,fsid=11 *(sec=sys,ro,insecure,anongid=100,anonuid=99,all_squash)' >>/etc/exports

Feb  7 18:58:33 Tower emhttp: shcmd (145): echo '"/mnt/disk2" -async,no_subtree_check,fsid=12 *(sec=sys,ro,insecure,anongid=100,anonuid=99,all_squash)' >>/etc/exports

Feb  7 18:58:33 Tower emhttp: shcmd (146): echo '"/mnt/disk3" -async,no_subtree_check,fsid=13 *(sec=sys,ro,insecure,anongid=100,anonuid=99,all_squash)' >>/etc/exports

Feb  7 18:58:33 Tower emhttp: shcmd (147): echo '"/mnt/user/Tower" -async,no_subtree_check,fsid=100 *(sec=sys,ro,insecure,anongid=100,anonuid=99,all_squash)' >>/etc/exports

Feb  7 18:58:33 Tower emhttp: shcmd (149): smbcontrol smbd close-share 'Tower'

 

I noticed the "ro" option, would that have any impact?

 

Thanks

 

EDIT: I have been reading the fora and FAQs.  No answer seem to satisfy.

Since you came from 4.7, you have to do: Tools - New Permissions

I did ... twice.  Did not change anything.  Still read-only.  Should I try a third time?

Go to Tools - Diagnostics and post the complete diagnostics zip. Could be unRAID has set the disk readonly due to filesystem corruption.

Here it is.  I have modified some values (usernames, etc...).

If I recall correctly, there have been many numerous changes related to NFS over the past 5 years that you just jumped over when going from 4.7 to 6.1 series. You will need to dig through the various posts on announced changes or directly contact LT for help.

I just mounted CIFS with the same result:

 

sudo mount -t cifs //<ip_address>/share /mount_point -o username=g*****y

 

Was prompted for password, which i provided.  Mounted no problem, but still ro.

See if this article helps for NFS:

http://lime-technology.com/forum/index.php?topic=38988.msg362847#msg362847

 

Eureka! Eureka! It solved my problem!!!

Great many thanks to all !!