jaqrab

So much for my 'confirmed' statement 🤦‍♂️ Turns out the backups were being stored in the /opt/crafty/backups folder, I changed this to the /config/crafty/backups and deleted the /opt/crafty/backups folder, thus reducing the image size. Some useful commands I learnt during the process: 1) Determine size of docker images docker ps --size 2) Determine folder space hogs du -h / 2>/dev/null | grep '[0-9\.]\+G' web reference

I am in the same position, have you had any luck finding out where the issue is? Mine is not quite as big, it's sitting at 10.2GB, which feels too big. I have confirmed my config folders are mapped correctly and backups are happening to the config folder. I am running a single papermc 1.18.1 server.

Exactly right, and such a pain. They have no intention of moving to IPv6 😞

Loving this docker. My ISP has unfortunately moved to carrier grade NAT, so it's becoming tricky to expose the docker for my kids friends to join and play Minecraft with them. I use PIA with your other VPN docker builds, would it be possible to create a VPN enabled version of this docker. I would gladly assist in the testing.

Can you add multiple UPS'es to be monitored with your script, but only have unraid react to one of them in order to shutdown. The second and third ups'es would also be on usb ports.

I've completed the V1.12 preclear script on my first Seagate Barracuda XT 3TB, results attached. dd if=/dev/sdb count=200 bs=8225280 skip=121200 | sum 00000 1606500 200+0 records in 200+0 records out 1645056000 bytes (1.6 GB) copied, 22.4087 s, 73.4 MB/s == Disk /dev/sdb has been successfully precleared Pre-Clear unRAID Disk /dev/sdb ################################################################## 1.12 Device Model: ST33000651AS Serial Number: 9XK0AXMG Firmware Version: CC44 User Capacity: 3,000,592,982,016 bytes Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdb1 1 4294967295 2147483647+ 0 Empty Partition 1 does not end on cylinder boundary. ######################################################################## ========================================================================1.12 == == DISK /dev/sdb IS PRECLEARED with a GPT Protective MBR == ============================================================================ preclear_start__9XK0AXMG_2011-07-15.txt preclear_rpt__9XK0AXMG_2011-07-15.txt preclear_finish__9XK0AXMG_2011-07-15.txt

Thanks, will report back when done.

Ok, so I'll re-run the the preclear's on the drives. A couple of questions going forward: What am I looking for post running the pre-clear to know that the drive has been sucessfully pre-cleared? When adding the drives to the array, (this is a new config, all drives including parity are new) I should expect to be able to use the format function on the data drives, and have the drives ready within a couple of minutes to allow the array to be started? Does the subsequent creation of parity then still take quite a long time after the array has been started? Thanks

I ran the previous version (v1.11) of the preclear script before seeing that the the beta v1.12 was supposed to be used for 3TB drives. Here are my results, must I do a preclear again with v1.12 ,and are the results OK? root@HPTower:~# dd if=/dev/sde count=200 bs=8225280 skip=121200 | sum 200+0 records in 200+0 records out 00000 1606500 1645056000 bytes (1.6 GB) copied, 19.8377 s, 82.9 MB/s I am using a Seagate Barracuda® XT 3TB 7200 RPM 64MB cache (ST33000651AS) Thanks preclear_start__9XK0H2MB_2011-07-08.txt preclear_rpt__9XK0H2MB_2011-07-08.txt preclear_finish__9XK0H2MB_2011-07-08.txt