Call Traces found on your server

[mrlionman]

Following instructions and uploading diagnostics file

 

Thanks for taking the time

 

------

Mrlionman

UNRIAD 6.4.0

48G Memory

10TB storage

hoth-diagnostics-20180422-1400.zip

[Squid]

Your disks are a mess.

 

Starts with this:

Mar 15 14:03:18 hoth kernel: Buffer I/O error on dev md5, logical block 0, async page read

(This is before the array even starts, and is disk #4)

 

Carries on with

Mar 20 17:08:29 hoth kernel: print_req_error: I/O error, dev sdm, sector 0

(A seagate unassigned device)

Numerous errors on a Lacie drive (which may or may not be the same drive as above, as it keeps getting different device labels)

 

You actual problem though is a call trace issued when docker is stopping.  May or may not be a "real" issue".  If you're worried, you can always delete and recreate your docker.img file and then reinstall the apps via Apps - Previous Apps

[mrlionman]

thanks for the followup.  Is there something I can read to figure out how to NOT have my disks a mess?  Also are there steps I should take before deleting and recreating my docker.img file?

 

Mrlionman

[John_M]

12 hours ago, mrlionman said:

thanks for the followup.  Is there something I can read to figure out how to NOT have my disks a mess?  Also are there steps I should take before deleting and recreating my docker.img file?

 

First make sure that notifications (Settings -> Notifications) are enabled so that you're made aware of problems when then occur so that you can fix them instead of letting them mount up.

 

I'd check cables and run extended SMART tests. While the tests are running read this.

 

Stop all dockers. Then stop the docker service in Settings -> Docker. Then you will have the option (a check box) to delete the image file. Once you've done that you can re-create it and start the docker service. Then us Community Applications (Apps -> Previous Apps)  to re-download your containers. All your settings will be applied as before.

[John_M]

Disk 4 is failing and I'd be keeping a close watch on disks 1 and 5 too.

 

You have two SSDs in your cache pool but they are in Single mode, not RAID-1. Is that the intention?

 

Make sure your plugins are up to date.

[mrlionman]

plugins are always up to date.  How do I change my SSD Cache pool to not be in single mode?

[John_M]

 

[John_M]

Since you're planning to trash your docker.img anyway I'd move everything else to the array and start again with the cache pool as a clean start is probably easiest.