March 9, 20188 yr Hi, the fix common problems plugin told me to ask for help in the forums. I would really appreciate it if someone looked at my attached diagnostics and told me if there's anything I should be worried about. tower-diagnostics-20180309-2139.zip
March 9, 20188 yr Community Expert Some page stalls and docker issues, image seems to be fine now, but if there are more errors or any docker issues better to delete and recreate. During the time covered by the syslog were you disconnecting and re-connecting various disks?
March 10, 20188 yr Author Thank you! Yes, I had the array offline and disconnected/re-connected a few disks to identify the parity disk (upgrading to 8TB).
April 2, 20188 yr Author Hi, I got another warning regarding call traces today. I suspect it is related to the file system error on disk 4 that I had to fix using XFS_repair -L, but can someone check the attached diagnostics just in case? tower-diagnostics-20180402-1328.zip
April 2, 20188 yr Community Expert 59 minutes ago, Mith said: I suspect it is related to the file system error on disk 4 Yep, there's another one related to a kernel problem, fixed in rc3
April 2, 20188 yr Author 29 minutes ago, johnnie.black said: Yep, there's another one related to a kernel problem, fixed in rc3 Thanks for lightning fast response! Can you elaborate what you mean by fixed in rc3? Do I need to do anything other than the XFS_repair command I did earlier to avoid something like this happening again?
April 2, 20188 yr Community Expert The first call trace: Mar 31 06:43:17 Tower kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000038 is unrelated to the second one (and xfs_repair), it's a kernel bug fixed on rc3, the second one was filesystem corruption and should be fine now after running xfs_repair.
Archived
This topic is now archived and is closed to further replies.