koaly

I have only BTRFS Scrubber plugin, which I think has nothing to do with ZFS Scrub. ZFS Master plugin does not have UI at least I do not see it as I have no ZFS pools.

Worked! many thanks. How much time this scrub action may run? I did not start it actually and do not have any schedule for it. How it could start by itself?

Yes, safe mode and docker disabled led to the same issue. How can I stop this zfs scrub?

Here it is. Thank you in advance! koaly-tower-diagnostics-20260605-1435.zip

Hello all, please advise on the following issue. I renamed the share from 'TV Shows' to 'TV_Shows', as Unraid did not accept the space as a character in the name. I created it years ago and it was accepted. The share is located in the disk2 (sdf), formatted as zfs in the classical array. Now the disk get 100% load from reading and I could finish the parity check only after switching to 'Maintenance mode', otherwise it would last months. I tried to localize the problem with chatGPT and ran in the terminal I am new to ZFS and formatted the replaced disks in the array recently. PLease advise how can I repair / correct the dataset tail -n 200 /var/log/syslog | egrep -i 'sdf|disk2|md|mdadm|parity|mover|error|retry'

Thank you for your reply. There was no problem caused by an external factor. I did not detach or replace any cables, and the power supply continued to work well. The server ran for more than a day before the read/write problem occurred. Unraid did not recognise the drive, even after I stopped the array. Therefore, an extended SMART test was not possible within UnRAID. As I understood your explanation, it is not possible to find out why UnRAID could not read from or write to the parity drive. It should be considered an unknown and non-repeatable bug. Since I have no issues with the drive on other systems, I will put it back as the parity drive.

Here it is, but at the time of saving it I already removed the failed drive from the server koaly-tower-diagnostics-20260528-0915.zip

Hello everyone, I have an issue with my parity drive. UnRAID disabled the drive after it registered 1,250 errors. Screenshots I did not manage to download the diagnostics as I thought the drive was dead and needed replacing. Syslog showed read-write errors. Syslog I tried to retrieve SMART data from UnRAID, but the file contained hardly any information. SMART from Unraid However, after connecting the drive to a PC, formatting it to NTFS, and running chkdsk and checking for bad sectors in AOMEI Partition Assistant, I found no errors. The SMART data received from HDD Sentinel also shows that the drive is in perfect condition. SMART and Chkdsk The drive has been working as a parity drive for about two months since it was new, and it has a four-year warranty. I have a label to send it for repair, but now I am concerned because it appears to be working fine outside of Unraid. The question is whether the drive is defective or whether this is a Unraid bug? Please advise

Hi guys, I don't know if you've solved the problem yet. In my case, it was Immich that prevented the drives from spinning down.

Hello guys, I used standard Nextcloud with a Swag combination for years and after the last issue with it I decided to switsch to AIO using Spaceinvaderone's tutorial. Installation with default settings went smoothly, but I cannot start initial setup right after the installation. The docker stops itself after a couple of minutes and the log shows that the DNS resolving does not work. I checked other containers, they all can resolve DNS. AIO does not. I tried to find any hint in forums, also by links in the log, but no luck. Reinstalled with no change in behaviour. The resolution was to delete Extra parameters. May be it would help anybody, because I was completely stack. Note: I have a pfsense router.

I would share my experience. I also have 5000 series APU, but I went to a PRO 5750GE version (35W TDP), wich supports ECC RAM and runs with 128Gb (4x64Gb) very well. I also had ASUS TUF GAMING X570-PLUS, but recently upgraded it to ASUS proart x570 for its integrated 10Gbe and 3x PCIe x16, sacrifycing 2 SATA ports for it. PCIe4 works only the 3Rd PCIe x16, while the first two x16 are gen 3. This is an APU limitaition. I will also put Hyper card there and will look how it works. Nevertheless, this MB is also overfilled as the 3Rd M.2 slot deactivates a couple of SATA ports. I saw that Asrock now released it's RACK version for AM5 (ASRock Rack B650D4U-2L2T/BCM), but it is limited with everything: only 4 SATA6, 1x PCIe 16x, 1x PCIe 4x and 1x PCIe 1x. So, I'd rather keep my x570 setup for now and when Unraid fully supports AM5 lineup, I would also go for a ASUS proart x670e. Additional drives can be attached to LSI 9308-8i card if needed in the future. NVMe drives will remain with Asus Hyper card. I am not sure whether PCIe lanes will be enough for everything, but so far it is not a bottleneck. Ryzen 5700 or 5900 (only 65W TDP) with a cheap discrete GPU might be also an option.

Hello everyone, I need to extend my array and decided to upgrade HDD size to 20 Tb. I will start with replacing a parity drive and plan a budget around 300 Euro per drive. With this budget there are actually only two options. First is WD Elements with 2 years warranty from WD, which after shucking appeared to be a re-labeled and re-flashed Ultrastar HC570 with 7200RPM. Second option is Toshiba MG10ACA20TE with 5 years warranty, but only over re- or e-tailer. Direct warranty claims from consumer side are impossible. I have many shucked WD drives and they work fine, but only with 2 years warranty vs 5 years with potential RMA difficulties from Toshiba. What would be your arguments which variant shall I go? Thanks in advance

Many thanks for explanations. Makes sense.

Hi everyone, I have 4x 14Tb xfs HDDs in the array, unprotected btrfs NVME drive for system and appdata, and also btrfs SATA SSD 480Gb single cache drive. I watched the Ed's videos and converted my cache SSD into ZFS. So far no problem. I am thinking about converting the drives in the array as single ZFS with an understanding that it may improve data compression. I am not concerned about additional workload for Ryzen pro 5750GE CPU. The process is well described in the videos. The question is whether I should also convert the parity drive into ZFS or it does not make any sense? Thanks in advance for explanations.

Many thanks! Changing to smtp.gmail.com did the trick. It works under reverse proxy and bridge now. Although the container does not start under host at all, showing an error "Address already in use"

Hello guys, I have installed the Vaultwarden for the first time with a SWAG reverse proxy. I can access the server's webUI from Internet, but I am stack on SMTP settings. I set up SMTP with my Gmail App password at the Vaultwarden's Admin setting page as per screenshot. Then I get an error "Error sending SMTP test email SMTP error: Connection error: Cannot assign requested address (os error 99)" I googled this error and tried many things as another App password, "force_tls" with the port 465, "Plain" and "Login" and so on. I also tried another mail service with the same result. Could you please help me to find out a SMTP error root cause?

Thanks for the reply. I was just wondering what these lines in the log may mean? I switch off the server daily as there are no overnight tasks and also in order to save some electricity, which became 3 times more expensive in Europe. As for the benchmark, it did not show any significant difference between 4 drives. I will do the parity check next time and post an update with the diags if it does not improve.

Hi to everyone! There is a question about a hard drive and a parity check speed. May be these issues are independent, I cannot say. The array is 4x14TB WD White from WD Elements. 3x WD140EMFZ-11A0WA0 1x WD140EDFZ-11A0VA0 They have been working a little over 2 years without problems. I noticed that for the last 2 monthly Parity checks it took 4 hours longer, since the average speed fell from 158 MB/s to 136 MB/s. Action Date Size Duration Speed Status Errors Parity-Check 2023-03-06, 16:34:51 (Monday) 14 TB 1 Day, 4 HR, 3 Min, 57 Sec 138.6 MB/S OK 0 Parity-Check 2023-02-03, 02:47:57 (Friday) 14 Tb 1 Day, 4 HR, 30 Min, 12 Sec 136.4 MB/S OK 0 Parity-Check 2023-01-07, 07:53:01 (Saturday)14 Tb 1 Day, 30 Min, 26 Sec 158.7 Mb/S OK 0 Parity-Check 2022-12-05, 09:06:33 (Monday) 14 Tb 1 Day, 25 Min, 40 Sec 159.2 Mb/S OK 0 I checked the logs of the discs, the WD140edFz showed the following entry twice in the log "kernel: ata7.00: supports DRM functions and may not be fully accessible". WD140emfz does not have such lines in the log. HW is all the same, I did not change anything in the config either. Bios has been updated in early December, before the last quick parity check. I tried to google it, but did not find an understandable answer. Could you advise me, what may this mean and how to deal with it? Could it be the SATA cable issue leading to both slower speed and errors in the log?

Hi guys, I found only one solution, which is shitty in any case. I made manual backup of all user data and reinstalled both Nextcloud and MariaDB with a full wipe of Appdata. After a clean install I restored user data and it started working. Updates do not work anyway. This is crap and makes me crazy. Yesterday by update from 23.0.0.0 to 23.0.0.2 I got the same way multiple errors in various steps from 3 to 6. I do not want to waste time on further attempts and again reinstalled. Shit. No support from anybody is available. No relevant info is available.

Hi guys, I have got an error by updating Nextcloud from 20.0.7 to 20.0.14 for some reason. I checked the updater log and it says that I am stuck on the step 6. Restarting does not work. I tried to change in the config file Maintanance to "false" and also deleted ".step" file in the updater folder, but it does not help. After that I need to change update secret in the config file and the process repeated with the same error. Sometimes in the detailed response in the red field it shows "Step 6 is currently in process. Please reload this page later." I am stuck Could you please advise what else can i do? I'd prefer to avoid reinstalling to secure that the user data is not deleted. Thanks in advance

I got the final response from ASRock on the non-working WOL from PCIe devices. They confirmed that X570m Pro4 does not support it, despite of the specification for the Motherboard on their website: Here's what I received exactly: "got final feedback from headquarter: After checking with BIOS and HW RD, we found it is a compatibility issue between X570M Pro4 and some specific LAN card. We also verify AMD reference board and it also has the same problem. If User would like use the WOL function, please help to ask user using the onboard i211 LAN." PS: WOL is works well on Gigabyte x570 motherboards. I checked it with the MASTER edition.

There is nothing else in BIOS settings of x570m pro4 for WOL. Actually only Intel chips provide additional section in BIOS settings. I have this option with N/A on X550, just like you shown. But Intel's 10Gbe NICs have no WOL at all. Only if I activate "Boot from LAN", I see additional options for DHCP of NICs, but it had no influence on WOL functionality. My new MB from Asus is already on the way and I will check WOL on it. Another thought is to get the Asrock MB replaced by the same model through the Asrock support.

Thanks for the link. Although I would not solder anything on the motherboard for a sake of having a valid warranty. BIOS shows an option of WOL from PCIe, but it does not work. Asrock support insisted in an email response that when they tested PCIe NICs on this MB, WOL worked well. May be I try another sample of this model just to avoid unneccessary changes