tmchow Posted August 19, 2016 Share Posted August 19, 2016 The other day, unraid sent me a notifcation saying there was 128 read errors on the parity disk. Logged into webUI and saw the 128 count but everything else looked OK. I let it run. However, since then I've been getting weird system stability issues but not idea if it has to do with the parity disk errors (or if that is even something I should worry about). Some of the issues I've encountered? Crashing to web ui Docker system crashed, and I had to turn it off then back on Got errors about a "read only filesystem" in the webUI in docker and the main screen. Only way to resolve was to reboot. I have the powerdown package installed so logs were saved to /boot/logs. However, before I post those, I wans't sure if they were sanitized for personal information. Would love some help debugging this! tower-diagnostics-20160819-0802.zip Link to comment
John_M Posted August 19, 2016 Share Posted August 19, 2016 Read only file system suggests file system corruption. Instability could be bad RAM or power supply. Without diagnostics that's as much as I can suggest. Link to comment
trurl Posted August 19, 2016 Share Posted August 19, 2016 Go to Tools - Diagnostics and post the complete diagnostics zip. Read-only filesystem is probably corruption, but parity read errors are probably a hardware problem, either bad connection or bad drive. Link to comment
tmchow Posted August 19, 2016 Author Share Posted August 19, 2016 Go to Tools - Diagnostics and post the complete diagnostics zip. Read-only filesystem is probably corruption, but parity read errors are probably a hardware problem, either bad connection or bad drive. added diagnostics to original post Link to comment
tmchow Posted August 20, 2016 Author Share Posted August 20, 2016 Anyone have any help to provide? Sent from my iPhone using Tapatalk Link to comment
John_M Posted August 20, 2016 Share Posted August 20, 2016 Waiting for you to report back on earlier suggestions. Link to comment
tmchow Posted August 20, 2016 Author Share Posted August 20, 2016 Waiting for you to report back on earlier suggestions. Didn't see troubleshooting suggestions just mention about possibility of bad connection or drive. I've double checked connections and the system doesn't seem to indicate hardware errors. Link to comment
John_M Posted August 20, 2016 Share Posted August 20, 2016 Read only file system suggests file system corruption. Instability could be bad RAM or power supply. Read-only filesystem is probably corruption, but parity read errors are probably a hardware problem, either bad connection or bad drive. Link to comment
tmchow Posted August 20, 2016 Author Share Posted August 20, 2016 Read only file system suggests file system corruption. Instability could be bad RAM or power supply. How do I diagnose a file system corruption? No RAM errors in my diagnostics tools I've run. Link to comment
John_M Posted August 20, 2016 Share Posted August 20, 2016 Start the array in maintenance mode and click the name of the affected disk (eg. the word "Disk 1") and run the file system check tool. To check RAM choose the MemTest option from the unRAID boot menu and leave it running for a good long time. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.