yyc321

Is there a way to reorder the disks in a dual parity array, and retain parity in P1, leaving only P2 to be rebuilt? I've tried the following on my test server: Stop the array, run TOOLS > NEW CONFIG. Reorder drives, and start the array: With "Parity is already valid" not selected, both parity drives are rebuilt. With "Parity is already valid" selected, you get the "Dual parity valid requires ALL disks in their original slots" warning. Stop the array, reorder as required: When this is done with 2 drives of different sizes, you get the warning about the replacement drive being too small. "The replacement disk must be as big or bigger than the original." With two equally sized drives: Both disks show "All existing data on this device will be OVERWRITTEN when array is Started"; and "Start will start Parity-Sync and/or Data-Rebuild."

So, I renamed a few of my VMs after creation. This results in the VM name and the name of the primary vDisk folder being different. Is fixing this as simple as renaming the folder, and then editing the VM, changing the primary vDisk location to the new name? I've read about people having problems with VMs after moving the vDisk to a new location, so I'm a little hesitant to try the above procedure. Thanks in advance.

I've noticed that some plugins appear automatically in the scheduler pane (ssd trim, speedtest etc). Any chance WOL can be included there? It would be handy to wake a backup server on schedule. I realize this can be done with scripts, but it would be more convenient with the plugin.

I'm having a very similar problem. I used the tip from the spaceinvader video for setting up what he calls a "root share" - greatly reducing the time to transfer files between shares. This involves modifying the SMB settings to include the following: [rootshare] path = /mnt/user comment = browseable = yes valid users = username write list = username vfs objects = However, when I delete files from anywhere within the "root share", they don't end up in the recycle bin. Deletes via the regular share works fine - everything ends up in the recycle bin. There is a line in the recycle bin help for setting parameters: Would setting this parameter fix the issue?

I'm having the same issues with plex and the mover. My server is an i7 8700, and the appdata resides on an nvme cache. I can write directly to the array (via SMB) with no impact on plex.

After a recent upgrade, I'm stuck in maintenance mode. Google pointed me towards a number of commands - tried them through the docker console, but it doesn't seem to work. Most seem to point to this command: sudo -u www-data php /var/www/nextcloud/occ maintenance:mode --off