jmztaylor Posted August 20 Share Posted August 20 Yesterday I swapped the CPU, removed half the RAM, and removed a video card from the Unraid server. Since then, the server hard freezes. The display output changes to just blinking cursor in top left and all services are down including SSH. Attached is from syslog server and diags after system hard reboot. syslog-previous tower-diagnostics-20240820-0737.zip Quote Link to comment
JorgeB Posted August 20 Share Posted August 20 Make sure this has been taken care of, if it doesn't help I would retest with the old CPU Quote Link to comment
jmztaylor Posted August 20 Author Share Posted August 20 35 minutes ago, JorgeB said: Make sure this has been taken care of, if it doesn't help I would retest with the old CPU Disabled c-states and still getting same thing. Attached is what I am seeing occasionally on the display output when its locked up. Quote Link to comment
JorgeB Posted August 20 Share Posted August 20 That is a filesystem issue with disk2, but could be the consequence of the issues, I would recommend going back to the original CPU and retest, if that CPU is not good it may cause filesystem corruption. Quote Link to comment
jmztaylor Posted August 20 Author Share Posted August 20 24 minutes ago, JorgeB said: That is a filesystem issue with disk2, but could be the consequence of the issues, I would recommend going back to the original CPU and retest, if that CPU is not good it may cause filesystem corruption. Yeah I swapped to another CPU and it seems to have fixed it. At least for now. Usually it would happen within an hour or so. Is that the same disk from this thread? Quote Link to comment
JorgeB Posted August 20 Share Posted August 20 Yes, and the filesystem issues may also be a consequence of the previous read errors, if the server is stable now, check filesystem on that disk, run it without -n Quote Link to comment
jmztaylor Posted August 21 Author Share Posted August 21 21 hours ago, JorgeB said: Yes, and the filesystem issues may also be a consequence of the previous read errors, if the server is stable now, check filesystem on that disk, run it without -n root@Tower:~# xfs_repair -v /dev/md2p1 Phase 1 - find and verify superblock... - block cache size set to 1489408 entries Phase 2 - using internal log - zero log... zero_log: head block 2213927 tail block 2213927 - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 3 - agno = 5 - agno = 4 - agno = 2 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... XFS_REPAIR Summary Wed Aug 21 07:31:41 2024 Phase Start End Duration Phase 1: 08/21 07:30:59 08/21 07:30:59 Phase 2: 08/21 07:30:59 08/21 07:31:00 1 second Phase 3: 08/21 07:31:00 08/21 07:31:21 21 seconds Phase 4: 08/21 07:31:21 08/21 07:31:21 Phase 5: 08/21 07:31:21 08/21 07:31:21 Phase 6: 08/21 07:31:21 08/21 07:31:40 19 seconds Phase 7: 08/21 07:31:40 08/21 07:31:40 Total run time: 41 seconds done Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.