October 10, 201015 yr I am suddenly having getting insufficient permissions whenever I try to write to my server from any of my computers. I can see all files. I have tried different username setting, but no success. I have intermittently been able to write a few files after rebooting the system, but then permissions are suddenly denied again and the file transfers cease. System parity check comes up clean. I have come across a couple of posts mentioning total commander to change permissions of unraid, but I see no documentation anywhere for total commander install. Not even sure if total commander is an unraid addon or a windows app. Thanks for any help on this one!
October 10, 201015 yr I am suddenly having getting insufficient permissions whenever I try to write to my server from any of my computers. I can see all files. I have tried different username setting, but no success. I have intermittently been able to write a few files after rebooting the system, but then permissions are suddenly denied again and the file transfers cease. System parity check comes up clean. I have come across a couple of posts mentioning total commander to change permissions of unraid, but I see no documentation anywhere for total commander install. Not even sure if total commander is an unraid addon or a windows app. Thanks for any help on this one! Which version of unRAID are you using? The documents probably refer to "midnight commander" which you can invoke by typing mc at a linux command prompt after logging in as root.
October 11, 201015 yr Author I managed to putty into the server and ran midnight commander. I tried chmod on root to allow guests and users to read and write. This didn't solve the problem. Which directory should I be trying to change permissions on if I am unable to write the the server globally?
October 11, 201015 yr I recently had an issue where the entire file system was saying it was "read only" even right from a Telnet session. Could be a very different issue but a clean re-boot fixed my problem.
October 11, 201015 yr Author Restarting after changing permissions seems to have fixed it ...I hope it sticks. I tried restarting a few days ago, before changing permissions and I was able to write for about a half an hour before it stopped working. I was messing around with permissions on my windows 7 machine a while back and I'm afraid that may be what is causing the problems.
October 11, 201015 yr Author ???Well that didn't last long. I copied about 5 files and the permissions were denied again. Not sure where to go from here.
October 11, 201015 yr Author turned off windows 7 machine and rebooted unraid. Same thing...I could copy files for a few minutes and then permissions locked up. I am copying files from one unraid box to another. Could this have something to do with it?
October 11, 201015 yr turned off windows 7 machine and rebooted unraid. Same thing...I could copy files for a few minutes and then permissions locked up. I am copying files from one unraid box to another. Could this have something to do with it? no, something is wrong... It could be almost anything since windows has very limited error reporting. Attach a syslog to your next post for analysis. it might be that file-system errors are causing the problems,, or network errors, or .... Joe L.
October 11, 201015 yr Author I see this error in the syslog: Oct 11 12:24:15 Tower2 emhttp: shcmd (22): mkdir /mnt/user Oct 11 12:24:15 Tower2 emhttp: shcmd (23): /usr/local/sbin/shfs /mnt/user -o noatime,big_writes,allow_other,default_permissions Oct 11 12:24:16 Tower2 emhttp: shcmd (24): killall -HUP smbd Oct 11 12:24:16 Tower2 emhttp: shcmd (25): /etc/rc.d/rc.nfsd restart | logger Oct 11 12:30:33 Tower2 shfs: shfs_write: write: (12) Cannot allocate memory Oct 11 12:30:33 Tower2 kernel: REISERFS error (device md2): reiserfs-2025 reiserfs_cache_bitmap_metadata: bitmap block 8388608 is corrupted: first bit must be 1 Oct 11 12:30:33 Tower2 kernel: REISERFS (device md2): Remounting filesystem read-only Oct 11 12:30:33 Tower2 kernel: REISERFS warning (device md2): clm-6006 reiserfs_dirty_inode: writing inode 188178 on readonly FS I will post a full syslog in a minute.
October 11, 201015 yr Oct 11 12:30:33 Tower2 kernel: REISERFS (device md2): Remounting filesystem read-only Oct 11 12:30:33 Tower2 kernel: REISERFS warning (device md2): clm-6006 reiserfs_dirty_inode: writing inode 188178 on readonly FS No need. There is enough there to tell you what you need to do next. You ran out of memory. It might have been the cause of the file-system corruption detected on disk2. Disk2 has some file-system corruption. To prevent further damage it is being re-mounted as read-only. You need to follow the directions given in the wiki to check and fix the file-system. http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems
October 13, 201015 yr Author When i run reiserfs I get an error that reiserfs superblock cannot be found on /dev/sda (etc) and that I need to run --rebuild -sb The wiki says don't do it unless instructed by the support team. So should I do it?
October 13, 201015 yr When i run reiserfs I get an error that reiserfs superblock cannot be found on /dev/sda (etc) and that I need to run --rebuild -sb The wiki says don't do it unless instructed by the support team. So should I do it? You should NOT be running reiserfsck on /dev/sda. It does NOT contain the file system. The warning it gave you was entirely correct. You should be running the reiserfsck on /dev/md2. It is connected logically to the file system on the physical disk by the "md" driver. It is good you stopped to get guidance. You would have done damage to the data structures on the disk if you attempted to force a superblock where one did not belong. Now, follow the instructions in the link provided earlier. Stop Samba /root/samba stop DO NOT Stop the array... It must be running un-mount disk2 ( umount /dev/disk2 ) run reiserfsck on /dev/md2 reiserfsck /dev/md2 Joe L. Joe L.
December 31, 201015 yr unless you run out of memory or power down without first stopping the array it should be permament. Joe L.
Archived
This topic is now archived and is closed to further replies.