Docker won't start

[banterer]

I've attached my diagnostics. Pre-empting (given some googling) that it might be my disk image is corrupt (seems to be the case commonly, is it for me? I can't make any sense of it), I'm a little panicked at the idea of having to reinstall everything! Really? Isn't it backed up or something? And will I lose anything? Sorry if this sounds curt, just in a panic right now!

tower-diagnostics-20221110-2340.zip

[banterer]

Ummm, help?  

[DanielPT]

Im very new at Unraid and dont know what to look for in the zip file.

 

But have you made any changes? Is it only 1 docker?

 

Do you have a parity ? 

 

Do you have a backup of youre dockers with CA Backup plugin?

 

[JorgeB]

One of your pool devices dropped offline in the past:

 

Nov 10 23:34:03 Tower kernel: BTRFS info (device nvme1n1p1): bdev /dev/nvme0n1p1 errs: wr 644541091, rd 578222484, flush 1832217, corrupt 0, gen 0

 

Start by running a correcting scrub on the pool to see if all errors are correctable.

[banterer]

9 hours ago, JorgeB said:

One of your pool devices dropped offline in the past:

 

Nov 10 23:34:03 Tower kernel: BTRFS info (device nvme1n1p1): bdev /dev/nvme0n1p1 errs: wr 644541091, rd 578222484, flush 1832217, corrupt 0, gen 0

 

Start by running a correcting scrub on the pool to see if all errors are correctable.

I'm finding contradicting ways to do this, what's the 'correct' way?

[banterer]

10 hours ago, DanielPT said:

Im very new at Unraid and dont know what to look for in the zip file.

 

But have you made any changes? Is it only 1 docker?

 

Do you have a parity ? 

 

Do you have a backup of youre dockers with CA Backup plugin?

 

All dockers (well, Docker won't start). I have a parity but the dockers mainly use the pool devices. What's the 'CA' backup? Might need to cgheck that!

[JorgeB]

39 minutes ago, banterer said:

what's the 'correct' way?

Click on the pool and scroll down to the "Scrub" section.

[banterer]

 

21 hours ago, JorgeB said:

Click on the pool and scroll down to the "Scrub" section.

 

Doesn't seem to do anything, it just comes up with this immediately:

```UUID: d3a1b53b-b4c0-40e3-9467-1f7226b8100d Scrub started: Sat Nov 12 18:14:07 2022 Status: aborted Duration: 0:00:00 Total to scrub: 648.26GiB Rate: 0.00B/s Error summary: no errors found```

[banterer]

Really need some help here!

[JorgeB]

Post new diags after running a scrub. 

[banterer]

1 hour ago, JorgeB said:

Post new diags after running a scrub. 

 

tower-diagnostics-20221113-1229.zip

[JorgeB]

Scrub is aborting, best bet is to backup and recreate the pool, then see here for better pool monitoring so if that device drops again you'll be immediately notified.

[banterer]

12 minutes ago, JorgeB said:

Scrub is aborting, best bet is to backup and recreate the pool, then see here for better pool monitoring so if that device drops again you'll be immediately notified.

 

Why would the scrub be aborting, and how do I restore everything once I've recreated the pool? I can't lose all my docker containers!

[banterer]

(I can't even view the docker configs to check where all my data is!)

[JorgeB]

It should go without saying that you must have backups of anything important, for the dockers you just need the appdata folder, go to shares and click on "compute" for the appdata share, it will show where the data is, if some of it is in the pool move/copy to the array.

[banterer]

Ok so looking at it, I have the CA backups running to backup my appdata (of course I would have set this up!)

 

But, the only 'backup set' available, is today at 3am. So does that mean I would have overwritten the good backup with the bad data?

[banterer]

Also more info, the docker image path is listed as:
 

/mnt/user/system/docker/docker.img

 

'system' is a 'prefer cache' share, which is completely empty. If I try to create the docker subdirectory I get:

root@Tower:/mnt/user/system# mkdir docker
mkdir: cannot create directory ‘docker’: Input/output error

 

So I'm thinking recreate the share, add the docker directory, start docker, cross fingers?

[banterer]

BTW, I have now changed my backup settings to give me more time to sort things out. Also from what I've read I will change to XFS.

[JorgeB]

Docker image can easily be recreated, important is the appdata folder, make sure you have a backup of that or move/copy to the array.

[banterer]

I seem to have everything back now! The only difference is I have spare SSD as I now have a single XFS SSD as my cache instead of a Btrfs pool of two. Thanks for your help.