Yannoviche

Yes I did. And that's when I increased vDisk to 200GB.

Because of the high number of failures to start of the apps, would this indicate that it is rather a global failure instead of a specific app failure? Before the update, the apps the loading with issues and I have even reinstalled all of them...

Sorry I meant vDisk. I had a quick look at one of them. But I haven't focus on it yet. But I don't really know what I'm looking for in the log. I don't have much experience yet. A bit of help learning how to diagnose the log will be appreciated.

Hi @trurl, Thank you for the help. Here is the container size. Container Size Name Container Writable Log tdarr 3.47 GB 170 MB 48.9 M binhex-overseerr 3.43 GB 1.18 GB 6.66 k tdarr_node 3.01 GB 82.2 MB 43.7 M binhex-sonarr 2.38 GB 490 MB 73.2 k binhex-lidarr 2.36 GB 345 MB 73.3 k binhex-delugevpn 2.28 GB 650 kB 6.86 k binhex-qbittorrentvpn 2.21 GB 1.23 MB 550 k binhex-radarr 2.03 GB 463 MB 12.7 k binhex-prowlarr 1.96 GB 428 MB 74.3 k homeassistant 1.73 GB 0 B 37.5 M binhex-emby 1.66 GB 74.1 MB 50.3 k jellyseerr 1.42 GB 0 B 12.9 M luckyBackup 1.29 GB 594 kB 12.3 k unmanic 1.20 GB 21.9 kB 16.7 M Krusader 1.13 GB 3.12 MB 14.7 k Nginx-Proxy-Manager-Official 1.09 GB 28.8 kB 18.1 M binhex-syncthing 1.06 GB 3.81 kB 15.4 M Jellyfin 1.04 GB 16.7 kB 101 k homarr 989 MB 2.20 MB 3.34 k Emulatorjs 873 MB 31.7 kB 43.6 k netdata 607 MB 1.76 kB 13.9 k romM 575 MB 15.7 MB 42.8 k telegraf 520 MB 0 B 0 Grafana 486 MB 0 B 396 k mealiev1 452 MB 0 B 37.5 M UptimeKuma 440 MB 0 B 24.8 k MariaDB 407 MB 0 B 2.51 k scrutiny 404 MB 67.8 MB 210 k Plex-Media-Server 351 MB 339 kB 27.5 M Actual 258 MB 0 B 1.28 k SFTPGo 231 MB 0 B 618 k QDirStat 184 MB 1.71 kB 23.1 k tautulli 146 MB 23.5 kB 20.1 M PuTTY 131 MB 3.17 kB 46.2 k goaccess 77.3 MB 27.4 kB 4.64 k duckdns 34.5 MB 21.8 kB 607 k Dozzle 20.0 MB 0 B 1.81 k Docker-WebUI 17.5 MB 0 B 645 Terraform-HTTP-Backend 17.0 MB 12.3 kB 116 NoIp 16.1 MB 329 B 2.51 M Total size 42.0 GB 3.32 GB 284 M Containers Size.docx

Hi my fellow Unraiders, Many of my dockers apps are not working after I have updated my server with the latest Unraid OS 7 update from v6.12. When I start some of them they stops i.e. Radarr and QdirStat. I was wondering if I could have some help. I have a warning about the size of the hardware where the vm is located. I thought it could have been the size of the docker image, so I have increased it to 200 Gb but it didn't fix it. I have included the diagnostic file before and after rebooting the server. kingfisher-diagnostics-20250121-1233 (before reboot).zi kingfisher-diagnostics-20250121-1233(after rebooting).zip

Thank you @binhex. It resolved my issue. And yes I am learning how to use unraid properly 😂.

Hi Binhex, Thank you for developing this container. I really appreciate it. I was wondering if I could get some help from anyone. I am a new Unraid user and have recently installed qBittorentVPN (as well as radarr, sonarr and prowlarr) by following AlienTech42 videos. But for the life of me qbittorrent never downloaded anything. I can see that radarr and sonarr have connected to qbit and queried files to download but I got a "status erroded". All I get in the container docker log is a loop as follow (but I have also attached the actual log file): 2025-01-01 17:28:30,150 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 23176 2025-01-01 17:28:30,150 DEBG 'watchdog-script' stdout output: [debug] qBittorrent incoming port is 23176 [debug] VPN IP is 10.18.217.46 [debug] qBittorrent IP is 10.18.217.46 2025-01-01 17:29:00,151 DEBG 'watchdog-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2025-01-01 17:29:15,178 DEBG 'watchdog-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.187.228' 2025-01-01 17:29:15,178 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2025-01-01 17:29:15,182 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place 2025-01-01 17:29:15,185 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 23176 [debug] qBittorrent incoming port is 23176 2025-01-01 17:29:15,185 DEBG 'watchdog-script' stdout output: [debug] VPN IP is 10.18.217.46 [debug] qBittorrent IP is 10.18.217.46 2025-01-01 17:29:45,187 DEBG 'watchdog-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2025-01-01 17:29:48,044 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '23176' 2025-01-01 17:30:05,248 DEBG 'watchdog-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.184.164' 2025-01-01 17:30:05,248 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2025-01-01 17:30:05,252 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place 2025-01-01 17:30:05,256 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 23176 [debug] qBittorrent incoming port is 23176 2025-01-01 17:30:05,256 DEBG 'watchdog-script' stdout output: [debug] VPN IP is 10.18.217.46 [debug] qBittorrent IP is 10.18.217.46 2025-01-01 17:30:35,258 DEBG 'watchdog-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2025-01-01 17:30:50,285 DEBG 'watchdog-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.200.4' 2025-01-01 17:30:50,285 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2025-01-01 17:30:50,289 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place 2025-01-01 17:30:50,293 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 23176 [debug] qBittorrent incoming port is 23176 [debug] VPN IP is 10.18.217.46 [debug] qBittorrent IP is 10.18.217.46 2025-01-01 17:31:20,294 DEBG 'watchdog-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2025-01-01 17:31:20,305 DEBG 'watchdog-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.200.4' 2025-01-01 17:31:20,305 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2025-01-01 17:31:20,308 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place 2025-01-01 17:31:20,312 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 23176 [debug] qBittorrent incoming port is 23176 2025-01-01 17:31:20,312 DEBG 'watchdog-script' stdout output: [debug] VPN IP is 10.18.217.46 [debug] qBittorrent IP is 10.18.217.46 2025-01-01 17:31:50,314 DEBG 'watchdog-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2025-01-01 17:32:05,341 DEBG 'watchdog-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.187.196' 2025-01-01 17:32:05,341 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2025-01-01 17:32:05,345 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place 2025-01-01 17:32:05,349 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 23176 [debug] qBittorrent incoming port is 23176 [debug] VPN IP is 10.18.217.46 [debug] qBittorrent IP is 10.18.217.46 qbittorrent.log

OK understood. Thanks for your help anyway 👍.

Hi @JorgeB, Thank you so much your solutions fixed the 1st issue. Would you also be able to help with my second issue (below) or do I need to create a separate thread? "Secondly, (when things will be back) after setting up Sonarr, Radarr, Prowlarr, I cannot get qBittorrent to work but it works fine on my windows pc. I believe I have not set it up correctly. "

Hi Jorge, Here are a few pics of the containers uptimes. To me it doesn't seem to have anything unusual.

Hi @JorgeB, I have attached the zip file after rebooting the server. kingfisher-diagnostics-20241228-1817.zip

OK understood. I have attached the new zip. kingfisher-diagnostics-20241228-1315.zip

Hi there, I hope that someone can help a newbie like me troubleshooting different issues I have with my server. First of all, I went away for a weekend and now that I'm back home, many of my apps are not working as well as some web UIs. When I start them, they start and stop. I have already restarted the server but it didn't solve the problem. I was trying to look into individual apps log files, but I don't even know where to start. And I don't really know what the issue is. I don't know if I need to open a new thread for this one but anyway. Secondly, (when things will be back) after setting up Sonarr, Radarr, Prowlarr, I cannot get qBittorrent to work but it works fine on my windows pc. I believe I have not set it up correctly. I have attached the latest zip files of the server. I don't know if it gives an indication, but the previous zip file from 26/12 was only 232kb compared to 427kb now. Thirdly, is there a guide to learn to troubleshoot my unraid server on my own? Like what are the meaning of these different sections in the log etc... I know it takes a lot of experience to do that. But I need to start from somewhere, isn't it 😂 ? By the way, thanks for the help. I really appreciate it. kingfisher-diagnostics-20241228-1023.zip kingfisher-diagnostics-20241226-2242.zip

Ah OK. It was that simple? I should have know better. Thank you for the solution @JorgeB.

After tinkering around I have been able to resolve it. After reading the Unraid Docs, I thought the data were not lost. But I just couldn't remember if the drive system was xfs or zfs. I plugged it in my Windows PC and used DiskInternals Linux Reader to check (and try to recover the files) on the drive and I was able to find out that the file system is xfs and that the shares are still in the drive. So I have decided to use the Nerdtools ddrescue because I had a free version of DiskInternals Linux Reader which didn't allow me to use the software the way I wanted to. But upon plugging in the drive back in my Unraid server, the drive appeared as unmounted. So I mounted it back to its original position. And the problem was resolved.

Here is a picture.

The faulty drive is not a nvme drive it is a samsung evo ssd. Should I still run the command? The nvme is btrfs.

This one gives: /dev/sdd1: UUID="2b75dc15-747b-44f9-a1e7-d92135696059" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="061de452-0e11-49e3-aabd-c5e6713e5fed"

I get : /dev/sdd: PTUUID="f4646496-fdbb-4630-a5a5-535477385f67" PTTYPE="gpt" Yeah I believe it is zfs. I have set it up a while ago and didn't think about it would failed. So I didn't memorized the settings. But I think it is zfs.

Hi @JorgeB, The diagnostic was already attached, but at the wrong place in my post. I have put it at the end. The output of zpool import gives me 'no pools available to import' even after running it in root / and usr/sbin. I am new to linux so if you give me a bit more info on how to run it, I will run it in the right location.

Hello guys, I need help to recover my disk. Hopefully my data are not lost. I had 4 disks in my Unraid PC with no parity: 2 x spin disks on the array called Disk 1 and 3 (btrfs). 1 x SSD Pool device called Home (zfs before) 1 x SSD Pool device called Temp-cache (btrfs) I wanted to add 3 more devices: 1 x spin as Disk 2 1 x SSD as another temp disk for parity device for one of the SSD Pool (for later on for Unraid 7) 1 x SSD as a normal disk. I have put all the disks in and assigned them without New Config. Probably a mistake here. But I have added one of the disk in my Home Pool (mistake here as well), one as Disk 2 and another as Temp-cache. I then clicked on start and found out the 1st Home disk was in the list of disks to reformat (so 4 disks to reformat instead of the 3 new ones). So I have stopped the operation imediatly and restarted the PC. Unfortunately it wouldn't start as the WebGUI wouldn't come up. So I have remove all the disk except Disk 1 and 2. I was then able to get back to the WebGUI and went to New Config to try to fix it. Afterward, I couldn't see any data in the user's home in that Home device after. I must say that there is a smart error in that Home disk which I was hoping to sort out a bit later on. Is it a problem which can be fixed? Would I be able to recover the shares in my Home disk? I have forgotten to download the diagnostic file before rebooting. But I have done so after rebooting with the present errors. kingfisher20-diagnostics-20241030-2257.zip

Hi there, This is an old topic, but I wanted to add my experience. Huawei Phones have a back up service that connects phones directly to the smb of any home servers. There is no need of a third party app. It can back up hundreds of Gbits on the server incrementally. Does your different phones have the same service? Just wondering as I'm planning to change phone brand by the end of the year to Samsung. Thanks