Hi All,

 

After upgrading to 6.3.3 I haven't been able to run any Docker apps, docker tab says 'Stopped'. I'm also have issues getting my VM to launch into Windows (it gets stuck in a repair/fail loop)

 

Looking through my syslog it appears I have several errors related to one of my cache drives but would like someone to confirm.

 

Thanks.

 

mediaserver-diagnostics-20170405-1434.zip

Docker image is corrupt, delete and recreate.

Also post the output of:

btrfs device stats /mnt/cache

@johnnie.black here's the output:

 

root@MediaServer:~# btrfs device stats /mnt/cache

[/dev/sdb1].write_io_errs   0

[/dev/sdb1].read_io_errs    0

[/dev/sdb1].flush_io_errs   0

[/dev/sdb1].corruption_errs 0

[/dev/sdb1].generation_errs 0

[/dev/sdh1].write_io_errs   56691403

[/dev/sdh1].read_io_errs    45384262

[/dev/sdh1].flush_io_errs   968089

[/dev/sdh1].corruption_errs 0

[/dev/sdh1].generation_errs 0

root@MediaServer:~#

That's a lot of errors on the Samsung SSD, and almost certainly the root cause of the docker issues.

 

That SSD is on a Marvell controller, that would be my prime suspect, and I would do the following:

 

-shutdown the server and swap both power and SATA cables with the Corsair SSD

-power back up and type:

 

btrfs device stats -z /mnt/cache

This will show current stats once again but reset all values to 0

-run a scrub, if any errors are found correct them

-continue using the server normally and every day or every couple of days check stats again with:

 

btrfs device stats /mnt/cache

If more errors appear and before rebooting grab and post new diagnostics, if no more errors appear for a few weeks you're probably fine.

I have had a similar issue. Upgraded to 6.3.3 and now Docker will not start.

tower-diagnostics-20170414-1843.zip

 

I have deleted the docker image several times and re-created. I have also increased the size. Still I have failed to get the docker to start.

 

Any ideas would be appreciated.

 

Thanks.

5 minutes ago, Tim2011 said:

I have deleted the docker image several times and re-created.

 

When did you delete it? Syslog shows docker image corrupt from array start, it stayed like that for several hours and it was never re-created.

 

Delete, re-create and post new diags if errors persist.

Attached diagnostics again.

 

Image deleted. Docker still fails to start and fails to create a new image.

 

Seems by cache drive is read-only. 

Not sure how that's happened.

tower-diagnostics-20170414-1912.zip

Yes, cache went read-only, best to copy everything important, stop docker and format cache, after that start docker again to recreate image.