Big Mike

Don’t get me wrong, I’m not dissing Syncthing, I think it’s excellent. I just couldn’t get it to work for me in this specific case. I would have loved to use the recycle folder function in particular.

I'm backing up around 27TB of data, mostly .mp4 and .mp3. The issue I found with Syncthing was it never really finished cataloguing the data, even when given weeks, when it was already copied at the destination. Maybe if I had let it do the initial copy I wouldn’t have had this problem. I do use Syncthing for syncing data to mobile devices, and found it to be great, just not with huge amounts of data.

Thanks, that's certainly "food for thought".

So I have a very large media library, which I sync to a TrueNAS box as a backup. At the moment I use RSYNC but have tried Syncthing, but It never seemed to work reliably due to the huge amount of data. Does anyone do something similar? and what do you use? Thanks

Found it: /var/lib/docker/containers/

I have a container which is refusing to start, I try and view the log on statup but the window closes before I can view anything useful. Is there a way to stop the log window closing? Or is logged in a file somewhere? Thanks

I got disks replaced at the weekend without issue. Thanks for the advice.

Will do, thanks

The disk has not failed, it just get's write errors, so i'm assuming it's on it's way out.

The data disk which is getting errors is: WDC_WD40EFRX-68W_WD-WCC4E1YTKARZ (sdo). The array only has one parity disk. I have another array (mirror) which has a SSD which is failing according to SMART tests, but that's another issue.

So... Stop the array. Remove the failing disk. Start the array. Stop the array. Put the existing parity disk as the replacement disk for the failing disk. Put the new disk as the new parity disk. Copy the parity over. Restart the array when complete. Done. I can then upgrade another disk at a later date. Thanks

So... I have a 4TB disk, which is getting write errors, that needs to be replaced. I don't have a spare 4TB disk, but I do have two 8TB disks. The 8TB disks will be the first >4TB disks in the array, so I need to replace the parity disk first. What i'm proposing to do is replace the parity disk first, rebuild the parity, then replace the failing disk and rebuild from the new parity. Is this a safe thing to do? My concern is that the parity disk will be rebuilt from an array which contains a disk with errors. Will this produce a parity disk which contains corrup data? Or do I need to go buy a 4TB disk and replace the failing disk first? Thanks for reading. unraid-diagnostics-20240119-1006.zip

Thanks

I want to move the 'appdata' folder to a new cache drive. Can this be done just stopping the docker service or do I also need to stop the VM service? Thanks

Found the issue: It was a a PCI adapter card: https://www.amazon.co.uk/SupaGeek-PCIe-Express-Adapter-Card/dp/B07CBJ6RH7 which was messing things up. Once removed, everything was fine. Does anyone know of a good quality version of this type of card?

I've flashed a Perc 310 recently for use with TruNAS. I look at doing this one. Thanks

I think it is a Dell Perc 710 with the BIOS disabled so it's not doing RAID functions.

Diagnostics are still running. Attached is the syslog in the meantime. syslog.zip

I'm running the disgnostics command at the momment, hopefully it will complete.

So I have a folder which is unaccessable and have the following errors: Event: Unraid array errors Subject: Warning [UNRAID] - array has errors Description: Array has 3 disks with read errors Importance: warning Parity disk - WDC_WD4003FFBX-6_V1JH8HTG_35000cca0bce32084 (sdb) (errors 5) Disk 8 - WDC_WD40EFRX-68W_WD-WCC4E1YTKARZ_350014ee20e041b64 (sdj) (errors 4) Disk 9 - WDC_WD20EARS-00M_WD-WCAZA1072381_350014ee2afa7e97b (sdk) (errors 5) Clicking the run partity check button doesn't seem to do anything. I can't seem to generate a disagnostic file. I'll give it a reboot and try again.

TLS had been working fine for over a year, all of a sudden the renewal of the LE certificate is failing: [2022-03-29 12:54:06] LEScript.INFO: Getting list of URLs for API [2022-03-29 12:54:06] LEScript.INFO: Requesting new nonce for client communication [2022-03-29 12:54:07] LEScript.INFO: Account already registered. Continuing. [2022-03-29 12:54:07] LEScript.INFO: Sending registration to letsencrypt server [2022-03-29 12:54:07] LEScript.INFO: Sending signed request to https://acme-v02.api.letsencrypt.org/acme/new-acct [2022-03-29 12:54:07] LEScript.INFO: Account: https://acme-v02.api.letsencrypt.org/acme/acct/40602749 [2022-03-29 12:54:07] LEScript.INFO: Starting certificate generation process for domains [2022-03-29 12:54:07] LEScript.INFO: Requesting challenge for mail.mydomain.co.uk, mydomain.co.uk [2022-03-29 12:54:07] LEScript.INFO: Sending signed request to https://acme-v02.api.letsencrypt.org/acme/new-order [2022-03-29 12:54:08] LEScript.INFO: Sending signed request to https://acme-v02.api.letsencrypt.org/acme/authz-v3/90548435960 [2022-03-29 12:54:08] LEScript.INFO: Got challenge token for mail.mydomain.co.uk [2022-03-29 12:54:08] LEScript.INFO: Token for mail.mydomain.co.uk saved at /opt/www//.well-known/acme-challenge/akZUnvxNdL9EXgkFS5YWO2fu9LJ0Fw5THsfeUcDezw0 and should be available at http://mail.mydomain.co.uk/.well-known/acme-challenge/akZUnvxNdL9EXgkFS5YWO2fu9LJ0Fw5THsfeUcDezw0 [2022-03-29 12:56:08] LEScript.INFO: Sending request to challenge [2022-03-29 12:56:08] LEScript.INFO: Sending signed request to https://acme-v02.api.letsencrypt.org/acme/chall-v3/90548435960/h6x7Ww [2022-03-29 12:56:09] LEScript.ERROR: 400 { "type": "urn:ietf:params:acme:error:badNonce", "detail": "JWS has an invalid anti-replay nonce: \"0002InMSGQXI1y_s6I4aFptyXnicZcW84BFuTLTuOaE4hCs\"", "status": 400 } [2022-03-29 12:56:09] LEScript.ERROR: #0 /opt/admin/vendor/analogic/lescript/Lescript.php(544): Analogic\ACME\Client->curl('POST', 'https://acme-v0...', '{"protected":"e...') [2022-03-29 12:56:09] LEScript.ERROR: #1 /opt/admin/vendor/analogic/lescript/Lescript.php(422): Analogic\ACME\Client->post('https://acme-v0...', '{"protected":"e...') [2022-03-29 12:56:09] LEScript.ERROR: #2 /opt/admin/vendor/analogic/lescript/Lescript.php(165): Analogic\ACME\Lescript->signedRequest('https://acme-v0...', Array) [2022-03-29 12:56:09] LEScript.ERROR: #3 /opt/admin/src/Base/Handler/LeHandler.php(62): Analogic\ACME\Lescript->signDomains(Array) [2022-03-29 12:56:09] LEScript.ERROR: #4 /opt/admin/src/Base/Controller/LeController.php(71): App\Base\Handler\LeHandler->renew(true) [2022-03-29 12:56:09] LEScript.ERROR: #5 /opt/admin/vendor/symfony/http-kernel/HttpKernel.php(158): App\Base\Controller\LeController->issueAction(Object(Symfony\Component\HttpFoundation\Request)) [2022-03-29 12:56:09] LEScript.ERROR: #6 /opt/admin/vendor/symfony/http-kernel/HttpKernel.php(80): Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object(Symfony\Component\HttpFoundation\Request), 1) [2022-03-29 12:56:09] LEScript.ERROR: #7 /opt/admin/vendor/symfony/http-kernel/Kernel.php(201): Symfony\Component\HttpKernel\HttpKernel->handle(Object(Symfony\Component\HttpFoundation\Request), 1, true) [2022-03-29 12:56:09] LEScript.ERROR: #8 /opt/admin/public/index.php(25): Symfony\Component\HttpKernel\Kernel->handle(Object(Symfony\Component\HttpFoundation\Request)) [2022-03-29 12:56:09] LEScript.ERROR: #9 {main} Do I need to change how I get the Certificate? Thanks

In the last few days I've had issues with the Server suddenly maxing out the CPU and using all the memory. Stopping all docker containers seems to fix it, for a while, but it seems to come back after a few days. I'm wondering if one of the docker containers is not working right. unraid-diagnostics-20211216-1708.zip

Cool, I'll take a look. Thanks

New config?

I have an array of 12 2TB disks. I bought two replacement 4TB disks to expand the array, from E-Bay. Both new disks were cleared with the preclear app. I upgraded the parity disk without problems, the parity was fully rebuilt. I then replaced one of the data disks but the disk reported write errors and this new 4TB data disk was disabled. I then tried to replace this disk with the original 2TB disk but the array won't start because it says the disk must be 2TB or larger. Is there any way I can put the 2TB disk back in and rebuild the array with the 2TB disk while I investigate the 4TB disk? Thanks