BartDG

Ah, so simple! Thx Squid!

Hi, I want to use unBalance to give my disks some much needed breathing room after installing a new disk. When I press "calculate", unBalance says: There are some permission issues with the folders/files you want to move 12392 file(s)/folder(s) with an owner other than 'nobody' 0 file(s)/folder(s) with a group other than 'users' 6 folder(s) with a permission other than 'drwxrwxrwx' 0 files(s) with a permission other than '-rw-rw-rw-' or '-r--r--r--' You can find more details about which files have issues in the log file (/boot/logs/unbalance.log) At this point, you can move the folders/files if you want, but be advised that it can cause errors in the operation You are STRONGLY suggested to install the Fix Common Problems plugin, then run the Docker Safe New Permissions command How can I fix this? I installed the Fix Common Problems plugin, but it didn't find all that much. I have no idea what the "Docker Safe New Permissions command" is. Google is no help here. Sorry, Linux newbie Thanks!

Got it! Thanks very much for your detailed answer Gary!

I'm very curious to know what kind of speed gain can be achieved by using Turbo mode. Has anybody already gone through the trouble of copying a set of files first old school style, then again using Turbo write and then compare the speed increase? On the other hand, if I get this correctly: this doesn't make any difference when writing to the array when using a cache disk, right? It only speeds things up when writing to the disk array directly? (I'm guessing because writing to the cache disk doesn't use parity anyway?)

Thanks for your comments BartDG ! Not sure why it would do that either, probably the disks were spinning up or rsync was still starting up ? No idea. The disks indeed didn't spin up. I waited for 10 minutes. Then I even manually spun them all up, then that also didn't do much good. Then I closed the menus, reopened them and tried again, this time without doing a dry run. (didn't need it anyway since the (empty) target drive was larger than the source. That worked without a problem. Anyway, I'm very happy and your little app was a tremendous help! Thanks again!

I'm currently using unbalance to copy the contents op a RF disk to an XFS disk. The idea is to completely empty the RF disk and then to format is as XFS as well. I installed the plugin and got the unbalance server started no problem. Told it to move folder /photo from disk 1 to disk 3. Did a calculation and then a "dry run" move. This went fine. Then I unchecked the "dry run" check and clicked "move" again. Nothing happened, but I couldn't click on the buttons anymore (saw the "forbidden" icon when I hovered over the buttons). The console showed "move operation in progress..", but nothing happened. The disks didn't even spin up!. I then closed the window, turned the unbalance server off and back on again. Took the array offline and back online to be sure nothing was in the background, and then tried again, but this time did a simple calculate and immediately unchecked "dry run" before I hit "move". Then it did work, it's currently moving files. Don't know why it didn't work the first time and figured this might be useful info to put in this thread. Otherwise a VERY handy plugin! Thanks so much for devoting your time to create this!

So if I get this correctly, if you run a plain vanilla Unraid v5 server (without any packages) and want to upgrade to v6, all you need to do is reformat the flash disk and install v6 onto it, and next assign the disks to the correct slots (with extra attention to parity and cache) and everything should be peachy?

I'm very new to unRaid, this is my first setup. First I had to buy a new motherboard because my Gigabyte board couldn't boot from USB. Now I've got a new "old" Asus bord from eBay and I was good to go. I created the boot thumb drive and installed unmenu and the preclear script. Then I installed 3 disks: two 3TB Western Digital WD30EZRX (one of which is for parity) and one Western Digital 2TB WD20EARS. I managed to install screen and ran three instances of Preclear. The 2TB was obviously finished first, but when it was running, I immediately noticed something strange. With the 2TB drive, the script said: "cycle 1 of 1, partition start on sector 64". With the 3TB drives, it said : "cycle 1 of 1, partition start on sector 1" The 2TB drive finished without a problem, after 35 hours. The 3TB drives gave some sort of notification, something concerning the partition and I had to re-type "Yes" again. But then it said it could not continue of some sort. I fear now that instead of at sector 64, these partitions started at sector 1. I found that strange because I did use the -A switch (preclear_disk.sh -A /dev/sda). What did I do wrong? I hope you can help me, because after more than 40 hours of pre-clearing, I really don't feel like redoing it. Edit: oh, and does it matter that the motherboard uses an older bios which does not support disks larger than 2TB? I've read in the past that Linux is capable of ignoring the BIOS setting and using it's own, but I'm not sure if it'll work in this case. If not, then I will probably have to buy a SATA controller. (the BIOS shows the 3 TB disks as 800 GB or something). Thanks! Thanks!