Beta25 and error 403

[Soulflyzz]

Hello,

 

I have looked up and down the Forums for weeks with nothing that has worked, sorry if i am repeating myself.

 

I am new-ish to unraid, i decided (for some reason) to update to the beta release currently on 6.9.0-beta25.

The issue i am having is after about 20 hours my Log file fills up and crashes all of my running Dockers, i do not see it fill up one moment its 1% next moment its 100% and my system has crashed.

When i go to restart my dockers i get a Error 403 and none of them will come online till i restart the server then everything works for about 20 hours again.

this problem only started after i upgraded from beta24 to beta25, i also reverted back to beta24 but problem has stayed.

 

When i try to downgrade to stable again it just jumps back to next and will not let me downgrade.

also when i try to view the log after it gets to 100% it will not load.

 

some direction for my next plan of attack would be greatly appreciated.

 

Thank you

[trurl]

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.

 

Also see here for how to save your syslog somewhere you can get it after crash:

 

[Soulflyzz]

laybourne-diagnostics-20200826-1329.zipi have attached as requested.
The server at the moment has only been running for 3 hours.

[trurl]

Unlikely to be related to your problems, but your system share has files on the parity array.

 

Also, looks like you may be having connection issues with cache:

Aug 26 12:02:47 Laybourne kernel: ata10.00: failed command: WRITE FPDMA QUEUED
Aug 26 12:02:47 Laybourne kernel: ata10.00: cmd 61/40:58:10:ed:27/01:00:0d:00:00/40 tag 11 ncq dma 163840 out
Aug 26 12:02:47 Laybourne kernel:         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 26 12:02:47 Laybourne kernel: ata10.00: status: { DRDY }
Aug 26 12:02:47 Laybourne kernel: ata10: hard resetting link

Maybe these are what is filling your log

[Soulflyzz]

how would i go about fixing these issues?

[trurl]

Check connections on cache. Maybe change SATA cable. Which controller is this using?

 

What do you get from command line with this?

ls -lah /mnt/disk3/system

 

[Soulflyzz]

This is the pull from that command

 

root@Laybourne:~# ls -lah /mnt/disk3/system
total 0
drwxrwxrwx  3 nobody users  29 Dec 16  2019 ./
drwxrwxrwx 15 nobody users 268 Aug 26 10:31 ../
drwxrwxrwx  2 nobody users  33 Dec 16  2019 libvirt/

 

I have extra sata cable at home so i will try that tonight.

I don't know how to answer what controller sorry.

[trurl]

What about these?

ls -lah /mnt/cache/libvirt

ls -lah /mnt/disk3/libvirt

 

[JorgeB]

Your Asmedia controller has (or is connect to) SATA port multipliers, those are known to cause many troubles, including those ATA errors reference by trurl.

[Soulflyzz]

My system is in current failure, I have added these requests and a log file

 

root@Laybourne:~# ls -lah /mnt/cache/libvirt
/bin/ls: cannot access '/mnt/cache/libvirt': No such file or directory

 

 

root@Laybourne:~# ls -lah /mnt/disk3/libvirt
/bin/ls: cannot access '/mnt/disk3/libvirt': No such file or directory

 

 

laybourne-diagnostics-20200827-0754.zip

[trurl]

You will probably have to get your controller issues resolved before you can make any progress.