April 10, 20215 yr Hi! migrated to Unraid last year in August. 6.8.3 check out my first ever post. 😂 been bulletproof. I’m all containers and VMs now. upgraded to 6.9.1 on Sunday before the Easter egg hunt. plain sailing and straight forward. onto this week. woke up Friday morning to a server with array stopped due to unsafe shutdown. start array and parity check begins. read errors on disk7. power down server and move plugs around on drives. power up and add back into array and parity check completes lunchtime today. sat down for Plex this evening and it drops off. go back out to server and it’s 8:13pm but screen says 8:09pm. unsafe shutdown again (hold power button) and start up again. everything’s back up and it’s doing another parity check. to say I’m absolutely gutted I updated to 6.9.1 and regret it. But I was intrigued on “my servers” which has only made it odd difficult to log in. I don’t know what to do and where to look at logs to find a solution. I hope it lasts the night and it gets parity checked out again. Third time this month it’s done one now. should I be upgrading to 6.9.2?
April 10, 20215 yr 8 minutes ago, Jammy B said: should I be upgrading to 6.9.2? That will not necessarily solve any issues. What you should do is post your server diagnostics (Tools- --> Diagnostics in the GUI). Otherwise all anybody can do is guess what the problem may be.
April 10, 20215 yr Author 4 minutes ago, Hoopster said: That will not necessarily solve any issues. What you should do is post your server diagnostics (Tools- --> Diagnostics in the GUI). Otherwise all anybody can do is guess what the problem may be. thanks @Hoopsterdiagnostic attached. amjam-diagnostics-20210410-2044.zip
April 10, 20215 yr Author Now parity drive is saying it has read errors and stopped its check. so is this the HBA breakout sata leads? Edited April 10, 20215 yr by Jammy B
April 11, 20215 yr Author 29 minutes ago, JorgeB said: Please post new diags after the errors. attached but not sure what good it'll do as i've powered down and swapped out the sff8087 breakout lead to another one to try and rule out connection issue as i woke to parity and disk7 read errors and they are on the same lead. telegram messaged the error @ 23:25 last night. i've replaced the lead and re-begun a parity check. amjam-diagnostics-20210411-0857.zip
April 11, 20215 yr Community Expert 10 minutes ago, Jammy B said: attached but not sure what good it'll do It doesn't, you should have save them before rebooting.
April 11, 20215 yr Author Just now, JorgeB said: It doesn't, you should have save them before rebooting. Ok. If it errors again during this parity check I will do new diagnostics before doing anything.
April 11, 20215 yr 9 hours ago, Jammy B said: Ok. If it errors again during this parity check I will do new diagnostics before doing anything. You may also want to setup a syslog server mirrored temporarily to your flash drive. That way everything written to the syslog is captured even across reboots.
April 12, 20215 yr Author latest diagnostics after surviving the night and completing parity check. amjam-diagnostics-20210412-0819.zip
Archived
This topic is now archived and is closed to further replies.