smakovits Posted April 17, 2016 Share Posted April 17, 2016 Last week I was messing with my cache drive when things got all out of whack. My shares all vanished and things were not right till I rebooted. However, because I was messing with my docker config folder on the cache drive only, I thought the issue was with the cache drive causing the entire array and its shares to stop sharing. At the time I replaced the cache drive, rebooted and got going again. Until last night that is, when I was creating a new folder on one of my shares. I was using my windows 10 computer, created new folder, but when I tried to rename it, windows reported I needed permissions to do so. I then tried going to one of my other shares when it started to prompt for credentials. This was the same behavior as last week and suddenly I knew. I pulled down the diagnostics and rebooted, at which time order was restored. However, this is two weeks in a row that my shares simply stopped sharing, forcing me to reboot. One thing to note is that I could access the individual disks fine still, it what just the share themselves that were suddenly broken. The diagnostic file is within 5-10 minutes of noticing what was going on. tower-diagnostics-20160416-2127.zip Link to comment
trurl Posted April 17, 2016 Share Posted April 17, 2016 Disk6 has this: 197 Current_Pending_Sector 0x0032 001 001 000 Old_age Always - 65530 An unbelievable number so not sure what happened, but I wouldn't trust it anymore. Have you got another disk to rebuild to? Link to comment
smakovits Posted April 18, 2016 Author Share Posted April 18, 2016 yes, I do. Do you suspect this as the culprit then or just something you saw? in the mean time, I am shutting down and replacing the disk Link to comment
trurl Posted April 18, 2016 Share Posted April 18, 2016 You had a pretty large syslog mostly read errors on disk6 Link to comment
smakovits Posted April 18, 2016 Author Share Posted April 18, 2016 Hmm. Wonder if that's also why I have been seeing my log partition filling up then. Seems to only make sense as I wouldn't expect it otherwise. In the past I just ran the command to increase it to 256mb. Guess maybe it got sick of throwing errors and started breaking so I took a closer look. Good news is the drive replacement yields an extra tb of storage. Thanks. If it does it again, I'll report it Beck here. Sent from my Nexus 6P using Tapatalk Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.