01cooperl

I changed the domain to blank as suggested above to successfully start the collabora container and now nextcloud is working again. I guess it must be how I configured nextcloud to connect to collabora or swag is doing something weird

I have the same problem. It's taken down my nextcloud instance as well! I would have expected Nextcloud to still function is Collabora cannot start. Any ideas?

I have this running using swag, just follow the link you shared and I just used the config/keys folder to upload the cloudflare certificate which is downloadable in that support page.

Would SMR drives have performance degradation to the point these errors would occur. I'm thinking about this as there are also bios related errors associated to this which may be due to the behaviour of the drive communication to the mobo. I've ordered a WD40EFRX which is CMR, so hopefully this will solve this problem.

Hi, I recently replaced a supposed failing drive (see topic Drive disabled, No smart report logged). I replaced with a larger WD40EDAZ drive and followed the Unraid FAQs for replacing a data drive. This was successful, until my server performed the scheduled partity check and reported 327088 errors. As a result I checked syslog and discovered the new drive (ata5) reporting errors ata5.00: exception Emask 0x50 SAct 0x60 SErr 0x4890800 action 0xe frozen ata5.00: irq_stat 0x08400040, interface fatal error, connection status changed ata5: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch } ata5.00: failed command: WRITE FPDMA QUEUED ata5.00: cmd 61/40:28:a8:3b:91/05:00:0d:00:00/40 tag 5 ncq dma 688128 out res 40/00:30:e8:40:91/00:00:0d:00:00/40 Emask 0x50 (ATA bus error) ata5.00: status: { DRDY } ata5: hard resetting link ata5: link is slow to respond, please be patient (ready=0) ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310) ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT4._GTF, AE_NOT_FOUND (20180810/psparse-514) I have since replaced the SATA cable and rebooted with no issues, however as soon as I restart the parity check it spits out the same errors. I replaced for yet another cable but still have the same problem. I'm not sure if the drive is the problem seeing as it is new. What is the problem here? liamdesktop-diagnostics-20210124-2309.zip

ok so I stopped and restarted an extended smart test however it failed in the terminal, see below: root@LiamDesktop:~# smartctl -t long /dev/sdf smartctl 7.1 2019-12-30 r5022 [x86_64-linux-4.19.107-Unraid] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org Short INQUIRY response, skip product id A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

ok sure. Based on the diagnostics now, it is likely the drive is on the way out? Is it worth ordering a replacement drive?

ok, here is the diagnostics now. Still at 90% on the self-test... diagnostics-20210116-1025.zip

Ok I'm doing that but it has been running for nearly 24 hrs. Is this normal?

Yes I've got off-site backups via USB. However with one drive down these should be data loss on the array as there is a parity drive, correct? Do you know what is wrong here? I think it is just one of my drives has bit the dust...

ok thanks. I have shutdown, checked all connections both power and sata data on drive and mobo. powered up and downloaded new diagnostic file. diagnostics-20210114-1932.zip

Hi, I have one of my disks disabled with a red 'x' and not exactly sure of the root cause. I can only see from the syslog that there is some write issue with also lots of lines saying "share cache full". Any help with this would be appreciated. See attached diagnostics diagnostics-20210114-1752.zip