Hi .... quick resume, server unresponsive and needed to be 'helped' to reboot following which unlcean shutdoen parity check kicked in.

 

Finished with 168 errors, all corrected and showing in syslog but is this correupted data now?

 

If so, any way to identify what's been affected?

 

 

6 minutes ago, superloopy1 said:

Finished with 168 errors, all corrected

Are you sure? Auto parity check after an unclean shutdown is non correct, or post the diags so we can check.

10 minutes ago, JorgeB said:

Are you sure? Auto parity check after an unclean shutdown is non correct, or post the diags so we can check.

That's what it says and considering the correct errors box is checked then i'd say it's right, there's a pile of errors in the syslog, doesnt look like the full 168 cos it says ';stopped logging' at some point. Just wondering if there's any way, suing the sector info to identify what's been affected. I accept that its been corrected but i what way. Just digging up some old forum posts in anattempt to get my head around this.

Edited February 28, 20224 yr by superloopy1

The syslog will say "parity incorrect" or "parity corrected" for those errors, if it's incorrect it was the auto check and you need to run a correcting check.

Here's the diagnostics ....

tower-diagnostics-20220228-1714.zip

Crossed posts, apologies.

 

It says corrected which i guess is what's needed but presumably that means there was an underlying problem with the data and previous parity status. I'm looking to try and identify what's been affected if thats possible?

1 minute ago, superloopy1 said:

I'm looking to try and identify what's been affected if thats possible?

That's basically impossible, data should be all fine except if there was any data being written at the time of the server reset.

Thanks. That's what i thought, so its just a case of double checking that all ok ... a job in itself. Thanks for our help again.