June 10, 201016 yr Hi, I just upgraded to 4.5.4 and all shares, after a while, would just become read-only. Restarting Unraid server seems to solve the problem only for it to return again. I did notice a hard drive running 40 degrees in temperature. Is it by design for the shares to become read-only if temperature runs high or is there something else causing this? Thanks
June 10, 201016 yr Hi, I just upgraded to 4.5.4 and all shares, after a while, would just become read-only. Restarting Unraid server seems to solve the problem only for it to return again. I did notice a hard drive running 40 degrees in temperature. Is it by design for the shares to become read-only if temperature runs high or is there something else causing this? Thanks They become read-only IF the file system driver detects corruption in the file-system. It is made read-only to prevent further damage. It is likely only one of your disks has corruption in the file-system, but you'll probably want to check them all. Note: don't try to run reiserfsck on the parity drive. It does not have a file-system... To fix the disks is easy. You need to run the equivalent of chkdisk/scandisk in windows. The equivalent command in Luinux is "reiserfsck" and the procedure to use it on an unRAID array is described in the wiki here: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems Joe L.
Archived
This topic is now archived and is closed to further replies.