tucansam Posted March 10, 2017 Share Posted March 10, 2017 Did a non-correcting parity check, got 768 errors. I need to upgrade a drive and do the rebuild, worried about doing this with these parity errors. Will probably not upgrade the drive until I get to the bottom of these errors. Diags attached. Any ideas? Thanks. ffs2-diagnostics-20170310-0538.zip Link to comment
JorgeB Posted March 10, 2017 Share Posted March 10, 2017 Is this the first parity check following this sync? Did you find what caused the corrupt files/names? Link to comment
tucansam Posted March 10, 2017 Author Share Posted March 10, 2017 Yes it is, and no I haven't. Still need to test the RAM, haven't had a chance to do that yet. Link to comment
JorgeB Posted March 10, 2017 Share Posted March 10, 2017 They look like actual errors, but so soon after a parity sync it's troubling, unless there was one or more unclean shutdowns in the meantime. Link to comment
tucansam Posted March 10, 2017 Author Share Posted March 10, 2017 There was an unclean shutdown -- while transitioning from sickrage to sonarr, the docker completely froze, and I had to ssh into the system to issue 'powerdown.' Powerdown subsequently froze that ssh session, so I started a new session, and issued a second 'powerdown' command, at which point the server shutdown, instantly. When it came back up, parity was checked, and the errors began. Link to comment
JorgeB Posted March 10, 2017 Share Posted March 10, 2017 28 minutes ago, tucansam said: There was an unclean shutdown Then the sync errors are normal, you should do a correcting check ASAP. Link to comment
tucansam Posted March 10, 2017 Author Share Posted March 10, 2017 Sweet, already did. Thanks!!!! Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.