Hi,

 

Every now and then my server decides it need my attention and start corrupting disks/docker images. Few months ago I decided I would buy brand new PSU,Cpu,Ram,Mobo,SSD and sata cables to hopefully resolve the issue. It did last for a while but this morning my log filled up and my dockers were unresponsive. Hopefully the diagnostic can shed some light as to what happened.

 

Thanks everyone

unraid-diagnostics-20210924-1511.zip

Edited September 24, 20214 yr by sloob

Your log space filled so nothing logged after

Sep 24 01:07:53 Unraid kernel: BTRFS error (device loop2): parent transid

 

Your docker.img is corrupt. Why have you given docker.img 40G? 20G is often more than enough. If you are having problems filling it, making it larger will only make it take longer to fill. The usual reason for filling docker.img is an application writing to a path that isn't mapped.

 

Also, your appdata and system shares are on the array instead of all on cache. This will impact performance of docker due to slower array, and will keep array disks spinning since these files are always open

2 minutes ago, trurl said:

Your log space filled so nothing logged after

Sep 24 01:07:53 Unraid kernel: BTRFS error (device loop2): parent transid

 

Your docker.img is corrupt. Why have you given docker.img 40G? 20G is often more than enough. If you are having problems filling it, making it larger will only make it take longer to fill. The usual reason for filling docker.img is an application writing to a path that isn't mapped.

 

Also, your appdata and system shares are on the array instead of all on cache. This will impact performance of docker due to slower array, and will keep array disks spinning since these files are always open

 

I frankly don't remember why I chose 40GB for my docker img, and no it never filled up so I could reduce it to 20GB. I rebooted the server and all is fine for the moment. I will change my appdata share to cache only to improve the performance.

 

Do you have an idea as to why my docker image got corrupted?

also

Sep 22 14:27:42 Unraid emhttpd: unclean shutdown detected

and

Sep 22 14:37:01 Unraid root: Fix Common Problems: Warning: Share appdata set to not use the cache, but files / folders exist on the cache drive
Sep 22 14:37:01 Unraid root: Fix Common Problems: Warning: Share VM set to not use the cache, but files / folders exist on the cache drive
Sep 22 14:37:01 Unraid root: Fix Common Problems: Warning: No destination (browser / email / agents set for Warning level notifications
Sep 22 14:37:01 Unraid root: Fix Common Problems: Warning: Deprecated plugin ca.backup.plg
Sep 22 14:37:03 Unraid root: Fix Common Problems: Warning: Docker application openvpn-as has moderator comments listed

You should pay attention to these. Uninstall that deprecated plugin and install the new one from the Apps page.

 

Connection problems on disk3.

Sep 22 14:27:15 Unraid kernel: ata4.00: ATA-10: WDC WD20EZAZ-00L9GB0,      WD-WXM2AA096LH8, 80.00A80, max UDMA/133
Sep 22 14:27:15 Unraid kernel: ata4.00: exception Emask 0x52 SAct 0x100 SErr 0x400c01 action 0x6 frozen
Sep 22 14:27:15 Unraid kernel: ata4.00: irq_stat 0x0c000000, interface fatal error
Sep 22 14:27:15 Unraid kernel: ata4: SError: { RecovData Proto HostInt Handshk }
Sep 22 14:27:15 Unraid kernel: ata4.00: failed command: READ FPDMA QUEUED
Sep 22 14:27:15 Unraid kernel: ata4.00: cmd 60/08:40:70:88:e0/00:00:e8:00:00/40 tag 8 ncq dma 4096 in
Sep 22 14:27:15 Unraid kernel:         res 40/00:40:70:88:e0/00:00:e8:00:00/40 Emask 0x52 (ATA bus error)
Sep 22 14:27:15 Unraid kernel: ata4.00: status: { DRDY }
Sep 22 14:27:15 Unraid kernel: ata4: hard resetting link

 

6 minutes ago, sloob said:

change my appdata share to cache only

That would only make it so any new files went to cache.

 

To get appdata and system shares moved to cache

1. Go to Settings - Docker and disable docker. Do the same for VM Manager
2. Go to User Shares and set appdata and system share to cache-prefer
3. Run Mover and wait for it to finish

Post new diagnostics so we can see if everything got moved.

15 minutes ago, trurl said:

also

Sep 22 14:27:42 Unraid emhttpd: unclean shutdown detected

and

Sep 22 14:37:01 Unraid root: Fix Common Problems: Warning: Share appdata set to not use the cache, but files / folders exist on the cache drive
Sep 22 14:37:01 Unraid root: Fix Common Problems: Warning: Share VM set to not use the cache, but files / folders exist on the cache drive
Sep 22 14:37:01 Unraid root: Fix Common Problems: Warning: No destination (browser / email / agents set for Warning level notifications
Sep 22 14:37:01 Unraid root: Fix Common Problems: Warning: Deprecated plugin ca.backup.plg
Sep 22 14:37:03 Unraid root: Fix Common Problems: Warning: Docker application openvpn-as has moderator comments listed

You should pay attention to these. Uninstall that deprecated plugin and install the new one from the Apps page.

 

Connection problems on disk3.

Sep 22 14:27:15 Unraid kernel: ata4.00: ATA-10: WDC WD20EZAZ-00L9GB0,      WD-WXM2AA096LH8, 80.00A80, max UDMA/133
Sep 22 14:27:15 Unraid kernel: ata4.00: exception Emask 0x52 SAct 0x100 SErr 0x400c01 action 0x6 frozen
Sep 22 14:27:15 Unraid kernel: ata4.00: irq_stat 0x0c000000, interface fatal error
Sep 22 14:27:15 Unraid kernel: ata4: SError: { RecovData Proto HostInt Handshk }
Sep 22 14:27:15 Unraid kernel: ata4.00: failed command: READ FPDMA QUEUED
Sep 22 14:27:15 Unraid kernel: ata4.00: cmd 60/08:40:70:88:e0/00:00:e8:00:00/40 tag 8 ncq dma 4096 in
Sep 22 14:27:15 Unraid kernel:         res 40/00:40:70:88:e0/00:00:e8:00:00/40 Emask 0x52 (ATA bus error)
Sep 22 14:27:15 Unraid kernel: ata4.00: status: { DRDY }
Sep 22 14:27:15 Unraid kernel: ata4: hard resetting link

 

That would only make it so any new files went to cache.

 

To get appdata and system shares moved to cache

1. Go to Settings - Docker and disable docker. Do the same for VM Manager
2. Go to User Shares and set appdata and system share to cache-prefer
3. Run Mover and wait for it to finish

Post new diagnostics so we can see if everything got moved.

Thanks alot!

 

I'm worried about that disk 3 issue, it's not the first time it happened and I've changed everything (psu,ram,mobo,cpu,cables,disk) except the server case (it uses a sata backplane) so I fear I will need to also change the server case or the backplane

18 hours ago, trurl said:

Post new diagnostics so we can see if everything got moved.

Here is the new diagnostic

 

unraid-diagnostics-20210925-1038.zip

Edited September 25, 20214 yr by sloob