October 22, 20169 yr Today I was moving my docker image from disk1 to the newly installed cache drive. 1 - Disabled Docker in Setting 2 - Deleted the Docker Image 3 - Re-enabled Docker pointing the image and appdata to go to the cache drive 4 - I re-installed my Pleax docker 4 - Everything started "hanging up" 5 - I stopped the array (it took about 5 minutes) 6 - it listed "no device" for the cache (this has happened a few times since cache drive installed 2 weeks ago) 7 - Usually a reboot will show the correct device for the cache drive, so I rebooted and the cache drive was now visible 8 - The docker from step 2 did not appear to be running 9 - all the data appears to still be on the drive on the MAIN Screen 10 - All the user shares were missing from the SHARES page 11 - Trying to Stop the array again and it is hung so I am unable to provide a diagnostics dump Any help appreciated. Will post a diagnostic if I am able.
October 22, 20169 yr 6 - it listed "no device" for the cache (this has happened a few times since cache drive installed 2 weeks This is the key. The drive is probably dropping offline (bad / loose sata and/or power cable). Diagnostics would be a real huge boon in determining the problem. Once it stops, grab them and post. If it won't start, then log in to the local keyboard / monitor and type in diagnostics The file will get saved to the flash drive (logs folder)
October 22, 20169 yr Author I was able to telnet in and command line reboot. I was then able to get in and run the diagnostics. It is attached. I have double checked the cable connections in the past. But still confused what happened to the user shares Thanks! epcot-diagnostics-20161022-1413.zip
October 22, 20169 yr I was able to telnet in and command line reboot. I was then able to get in and run the diagnostics. It is attached. I have double checked the cable connections in the past. But still confused what happened to the user shares Thanks! Nothing in it of use, since its after a reboot and before the array started. Start the array, disable and enable docker, grab another diagnostics, then try to install Plex and try and get another one (having you grab the first one just in case it winds up being impossible to grab them after installing Plex (although you can still try the command I posted up a few posts)
October 22, 20169 yr Author OK after restarting this time user shares came back (I am breathing again now). Here the current diagnostic before doing anything else with the dockers I will post another after I restart the dockers. epcot-diagnostics-20161022-1424.zip
October 22, 20169 yr OK after restarting this time user shares came back (I am breathing again now). Here the current diagnostic before doing anything else with the dockers I will post another after I restart the dockers. Looks good up to that point.
October 22, 20169 yr Author It seems to be back, plex has been installed, but not yet accessible here is the latest Diags epcot-diagnostics-20161022-1435.zip
October 22, 20169 yr It seems to be back, plex has been installed, but not yet accessible here is the latest Diags And this is what we were looking for. Oct 22 14:33:18 EPCOT kernel: ata7.00: failed command: WRITE FPDMA QUEUED Oct 22 14:33:18 EPCOT kernel: ata7.00: cmd 61/00:00:68:8c:62/04:00:00:00:00/40 tag 26 ncq 524288 out Oct 22 14:33:18 EPCOT kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 22 14:33:18 EPCOT kernel: ata7.00: status: { DRDY } Oct 22 14:33:18 EPCOT kernel: ata7: hard resetting link The drive is in the process of dropping offline (likely due to sata cable / power issues) Then it is completely dropped Oct 22 14:33:33 EPCOT kernel: ata7.00: failed to IDENTIFY (I/O error, err_mask=0x11) Oct 22 14:33:33 EPCOT kernel: ata7.00: revalidation failed (errno=-5) Oct 22 14:33:33 EPCOT kernel: ata7.00: disabled Which then throws docker for a loop Oct 22 14:33:33 EPCOT kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 0, flush 1, corrupt 0, gen 0 Oct 22 14:33:33 EPCOT kernel: BTRFS: error (device loop0) in write_all_supers:3620: errno=-5 IO failure (errors while submitting device barriers.) Oct 22 14:33:33 EPCOT kernel: BTRFS info (device loop0): forced readonly Oct 22 14:33:33 EPCOT kernel: BTRFS warning (device loop0): Skipping commit of aborted transaction. Reseat all the cabling to and from the drive and giv'er another go.
October 22, 20169 yr Author Really appreciate you taking a look. I have powered down, reseated the all the cables and am trying it all again.
Archived
This topic is now archived and is closed to further replies.