ltoolio Posted June 11, 2015 Share Posted June 11, 2015 Hey all, Was running Beta 15 for a good 60+ days without a reboot, all good. Upgraded to RC5 via Plugin, rebooted and now I'm getting a Disk 2 error. Didn't change anything at all prior to reboot and all was running fine before reboot. Others having similar problems? Log attached.... tower-syslog-20150610-2140.zip Link to comment
itimpi Posted June 11, 2015 Share Posted June 11, 2015 What do you mean by a 'Disk 2 Error'? Maybe a screenshot to show what you mean? I could not spot anything obvious in the syslog. Note that with rc5 there is now a 'Diagnostics' option on the Tools tab that creates a ZIP of diagnostic information that is far more comprehensive than the syslog (it includes the syslog), and providing that may help with diagnosis. It is also the easiest way to gather all this information. Link to comment
ltoolio Posted June 11, 2015 Author Share Posted June 11, 2015 Thanks, itimpi. Diagnostics attached here. tower-diagnostics-20150611-1017.zip Link to comment
ltoolio Posted June 11, 2015 Author Share Posted June 11, 2015 And here's the screen shot Link to comment
trurl Posted June 11, 2015 Share Posted June 11, 2015 Have you rebooted since the disk was disabled? If so, that would explain why the event is not in your syslog. When you did the upgrade, did you open the case? Might seem like a silly question, but some people have their flash inside the case. If you did then maybe you bumped a cable or something. unRAID disables a disk when a write to it fails. While disabled, unRAID will emulate the drive by using all the other drives plus parity. When the emulated disk is read, what actually happens is all of the disks plus parity are read, and from that the data for the disk can be calculated. When the emulated disk is written, what actually happens is all of the disk plus parity are read, and from that plus the data to be written, the parity change can be calculated and written. So, reads and writes can still happen, but they don't actually happen on the disabled drive. You will have to rebuild the drive. Do you have a spare? Link to comment
ltoolio Posted June 11, 2015 Author Share Posted June 11, 2015 Have you rebooted since the disk was disabled? If so, that would explain why the event is not in your syslog. - Yes. The machine was completely off before I generated the screenshot and diagnostic logs and I had to turn it on in order to get them for you. When you did the upgrade, did you open the case? Might seem like a silly question, but some people have their flash inside the case. If you did then maybe you bumped a cable or something. - Negative. It has been in the same position for ~6 months. You will have to rebuild the drive. Do you have a spare? - I do not. It's been a while since I last had to do a rebuild...can I just reuse the one that's in there? (and thank you for the input!) Link to comment
ltoolio Posted June 12, 2015 Author Share Posted June 12, 2015 Took an extra reboot, but all good now. Thank you again for the help! Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.