Bugman1400 Posted November 2, 2015 Author Share Posted November 2, 2015 Ok....so, I think I figured it out. I created another User share with Use Cache Disk: set to No and everything seemed to work. I then went back to my original User share changed the Use Cache Disk: from Yes to No and it started to work. The question now is...why does this happen? I assumed using the cache disk would be faster and preferred since its an SSD but, perhaps there is another process that has it locked. Quote Link to comment
trurl Posted November 2, 2015 Share Posted November 2, 2015 Ok....so, I think I figured it out. I created another User share with Use Cache Disk: set to No and everything seemed to work. I then went back to my original User share changed the Use Cache Disk: from Yes to No and it started to work. The question now is...why does this happen? I assumed using the cache disk would be faster and preferred since its an SSD but, perhaps there is another process that has it locked. From your syslog, cache is one of the suspects for filesystem corruption. You could try this command to write your syslog to cache just to see if it is writable:cp /var/log/syslog /mnt/cache/syslog.txt Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.