extremeaudio Posted October 31, 2016 Share Posted October 31, 2016 All of a sudden a couple of dockers have stopped working. Couchpotato for instance will not start and gives an execution error if I try to start it. Log says - Error running logs job: open /var/lib/docker/containers/80cf67e029fb7b2cb682be1aac364360ca08a281a5a87d6fee381a4de542a964/80cf67e029fb7b2cb682be1aac364360ca08a281a5a87d6fee381a4de542a964-json.log: read-only file system Please help Quote Link to comment
Squid Posted October 31, 2016 Share Posted October 31, 2016 Post your diagnostics Sent from my LG-D852 using Tapatalk Quote Link to comment
extremeaudio Posted October 31, 2016 Author Share Posted October 31, 2016 Log attached syslog.zip Quote Link to comment
trurl Posted October 31, 2016 Share Posted October 31, 2016 Log attached syslog is not your diagnostics. Go to Tools - Diagnostics and post the complete diagnostics zip. Also, why are you not fixing these things noted by Fix Common Problems? Oct 31 16:26:12 iServe root: Fix Common Problems: Warning: Share images is set for both included (disk4) and excluded (disk1,disk2,disk3) disks Oct 31 16:26:12 iServe root: Fix Common Problems: Warning: Share Photos is set for both included (disk4) and excluded (disk1,disk2,disk3) disks Oct 31 16:26:12 iServe root: Fix Common Problems: Warning: Share RippedMovies is set for both included (disk4) and excluded (disk1,disk2,disk3) disks Oct 31 16:26:12 iServe root: Fix Common Problems: Warning: Share TVShows is set for both included (disk3) and excluded (disk1,disk2,disk4) disks Oct 31 16:26:12 iServe root: Fix Common Problems: Warning: Share Videos is set for both included (disk4) and excluded (disk1,disk2,disk3) disks Oct 31 16:26:12 iServe root: Fix Common Problems: Warning: Share X is set for both included (disk4) and excluded (disk1,disk2,disk3) disks There is never any good reason to set both include and exclude. Looks like you have some problem with your cache disk Oct 31 16:25:59 iServe kernel: ata5.00: ATA-9: WDC WD5000LPVX-00V0TT0, WD-WXA1A455S83D, 01.01A01, max UDMA/133 ... Oct 31 16:26:02 iServe emhttp: WDC_WD5000LPVX-00V0TT0_WD-WXA1A455S83D (sdf) 488386552 ... Oct 31 16:26:02 iServe emhttp: import 30 cache device: sdf ... Oct 31 16:43:45 iServe kernel: ata5.00: exception Emask 0x50 SAct 0x20 SErr 0x280900 action 0x6 frozen Oct 31 16:43:45 iServe kernel: ata5.00: irq_stat 0x08000000, interface fatal error Oct 31 16:43:45 iServe kernel: ata5: SError: { UnrecovData HostInt 10B8B BadCRC } Oct 31 16:43:45 iServe kernel: ata5.00: failed command: READ FPDMA QUEUED Oct 31 16:43:45 iServe kernel: ata5.00: cmd 60/20:28:e0:20:d1/00:00:05:00:00/40 tag 5 ncq 16384 in Oct 31 16:43:45 iServe kernel: res 40/00:2c:e0:20:d1/00:00:05:00:00/40 Emask 0x50 (ATA bus error) Oct 31 16:43:45 iServe kernel: ata5.00: status: { DRDY } Oct 31 16:43:45 iServe kernel: ata5: hard resetting link ... and lots more like that. If we had your diagnostics we might be able to tell more. Quote Link to comment
extremeaudio Posted November 3, 2016 Author Share Posted November 3, 2016 Oh, I didnt know this new diagnostics bit. Attached diagnostics-20161103-1322.zip Quote Link to comment
trurl Posted November 3, 2016 Share Posted November 3, 2016 There is no SMART for you cache disk in the diagnostics. Maybe a bad connection. Try to fix it and then post another diagnostic. Quote Link to comment
extremeaudio Posted November 6, 2016 Author Share Posted November 6, 2016 I removed and re seated all the cables I tried to re install all dockers by deleting the docker image. But the docker installation fails with a read only file system error. Diagnostics attached. diagnostics-20161106-1750.zip Quote Link to comment
Squid Posted November 6, 2016 Share Posted November 6, 2016 Its the exact same problem as before (actually, if anything its worse than before)... Implies cabling. Try a different cable and/or port Maybe also *very lightly* and carefully, clean the contacts on the drive with some contact cleaner. Or replace the drive.. Quote Link to comment
extremeaudio Posted November 9, 2016 Author Share Posted November 9, 2016 Now? diagnostics-20161109-1651.zip Quote Link to comment
Squid Posted November 9, 2016 Share Posted November 9, 2016 Looks Clean, but the diagnostics were immediately after starting the array Quote Link to comment
extremeaudio Posted November 9, 2016 Author Share Posted November 9, 2016 Some dockers working ok, others wont start. New diagnostics attached. diagnostics-20161109-2239.zip Quote Link to comment
extremeaudio Posted November 15, 2016 Author Share Posted November 15, 2016 Some help here please? Quote Link to comment
trurl Posted November 15, 2016 Share Posted November 15, 2016 Your latest diagnostic is 6 days old and doesn't show much. If it has been running since then maybe a new diagnostic will have a lot more to show. 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.