July 5, 201115 yr I have used unRaid server to build 4 servers to date and have never run into issues until now. I am using unraid 5beta7 because I have 3 TB disks and wanted to use all of them. I set up the server and shares and everything seems to work until I start to transfer. I have tried transfers via samba and AFP from a Mac using various programs (rsync, finder, etc.) with the same results. After a few minutes, the transfer just stops saying the connection was shut down; following the failure, I have to forcibly eject the share and restart finder. When I try to resume the transfer after reconnecting, the file system has turned read-only preventing all transfers. On a few occasions the server has also prevented the addition of users and shares after the transfer failure, but again, prior to failure it is fine. Stopping the array, rebooting, and restarting the array seems to solve the read-only file system issues. It's very frustrating. On a side note, I read somewhere it is possible to use 3 TB disks in unraid 4.7 by using a work around to make the disks appear as 2 TB disks... is there a walk through for this work around? I would prefer not having to buy new disks so using 4.7 is fine.
July 5, 201115 yr I have used unRaid server to build 4 servers to date and have never run into issues until now. I am using unraid 5beta7 because I have 3 TB disks and wanted to use all of them. I set up the server and shares and everything seems to work until I start to transfer. I have tried transfers via samba and AFP from a Mac using various programs (rsync, finder, etc.) with the same results. After a few minutes, the transfer just stops saying the connection was shut down; following the failure, I have to forcibly eject the share and restart finder. When I try to resume the transfer after reconnecting, the file system has turned read-only preventing all transfers. On a few occasions the server has also prevented the addition of users and shares after the transfer failure, but again, prior to failure it is fine. Stopping the array, rebooting, and restarting the array seems to solve the read-only file system issues. It's very frustrating. On a side note, I read somewhere it is possible to use 3 TB disks in unraid 4.7 by using a work around to make the disks appear as 2 TB disks... is there a walk through for this work around? I would prefer not having to buy new disks so using 4.7 is fine. File systems are marked as read-only when corruption in them is detected. This is to prevent more corruption. You should check your disk file-systems using reiserfsck as described in the wiki. Joe L.
July 6, 201115 yr Author Running reiserfsck discovered a few corruptions on one of the disks. I fixed them and everything is working now. Thanks very much Joe L. Austin
Archived
This topic is now archived and is closed to further replies.