bwestpha

Hi , i have the following scenario: Currently I have one parity drive with 16TB in place - and I get a new drive with 26TB. When replacing my parity drive directly with the new 26TB one, I am in danger of loosing data when it comes to any error during that re-building phase which happens when exchanging the drives. Is there a more secure approach to exchange these? I thought about e.g. adding the new 26TB drive as a second parity drive first, and after that finished, removing the 16TB from the parity --> is this a valid approach? Finally I want to add the former parity to the data drives ofc. What is the most secure and efficient way to do that?

Sure - sorry nas-diagnostics-20231026-1505.zip maybe not related, but if i see the logs directly after hitting a new vDisk size and starting Docker, I can see this message from the Logs window: Oct 26 15:14:37 WNAS root: Stopping Avahi mDNS/DNS-SD DNS Server Configuration Daemon: stopped Oct 26 15:14:37 WNAS root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D Oct 26 15:14:37 WNAS avahi-dnsconfd[2777]: Successfully connected to Avahi daemon. Oct 26 15:14:38 WNAS emhttpd: shcmd (650): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 30 Oct 26 15:14:38 WNAS kernel: loop4: detected capacity change from 0 to 62914560 Oct 26 15:14:38 WNAS root: mount: /var/lib/docker: mount(2) system call failed: File exists. Oct 26 15:14:38 WNAS root: dmesg(1) may have more information after failed mount system call. Oct 26 15:14:38 WNAS root: mount error Oct 26 15:14:38 WNAS kernel: BTRFS warning: duplicate device /dev/loop4 devid 1 generation 3484667 scanned by mount (2831) Oct 26 15:14:38 WNAS emhttpd: shcmd (650): exit status: 1 //deleting by old vDisk (backuped) and creating a new one seemed to work. but this would mean loose all my containers and i would have to re-create them, right?

Hi there, i have a quite similar problem to this thread here: My docker img file seems to be out of space (no idea why exactly) - and therefore my docker service will not start. I already tried to stop the service from web gui, (or just set it to stop since it was already down) and change the vDisk size to 50GB instead of 20. But basically nothing happend -the disk was not resized and the docker daemon was not able to start again . any way i can fix this without re-creating all docker containers again as stated in above solution?

Totally agreed!

IMHO there is something wrong when calculating speeds and showing them in the frontend: Here an example from my home: In this case, it seems like decimal point is somehow shifted. Upload is correct, but download is far away from real values. I have a 1gig download stream and when testing directly via speedtest.net, i always get around my 1100 Mbit/s. This is very similar to the values in the frontend, but the comma is in the wrong place // And as a suggestion: You should add a hint on WHAT exactly you need for a "speedtest.net server" metric, IP adress? Hostname? or an server ID from an XML file hosted here: https://c.speedtest.net/speedtest-servers-static.php . For all others: It's the XML file and the 'id' attribute in it.