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 am a little bit stumped with this, would appreciate any advice or pointing in the right direction.

Thanks Squid, diagnostics attached tower-diagnostics-20171113-0457.zip

I have a problem with a particular file that has lost it's permissions, and replaced with ??????????? I cannot get a directory listing of /mnt/user/documents/Desktop, it returns a permission denied error. I can see the files on the /mnt/disk2/documents/Desktop and can see the offending file Salaries September 2017.xlsx whose permissions are ???????????? I have attempted running newperms on /mnt/user/Documents/Desktop, which returns without problems, see below. I have attempted running newperms on /mnt/disk2/Documents/Desktop, which returns with permission denied on Salaries September 2017.xlsx Please assist with restoring the permissions to normal.

Is NUT UPS support still planned for 6.1? Really looking forward to this.

Dropbox links are not working for me

I selected parity check from the web interface while all my drives spun down. After about 5 minutes the web interface came back with the parity drive red-balled. I stopped the array, and the web interface reported that there was "no device" in the parity slot. Attached is the syslog, and the entries at the time of it happening. This has happened before, and not only with the parity drive, it will happen randomly with the other data drives, and always after spin up. I usually power down the server, on power up the device is present again, and I can start a parity re-build or data rebuild. Jun 24 05:38:49 Tower kernel: mdcmd (93): check CORRECT Jun 24 05:38:49 Tower kernel: md: recovery thread woken up ... Jun 24 05:38:49 Tower kernel: md: recovery thread checking parity... Jun 24 05:38:49 Tower kernel: md: using 1536k window, over a total of 2930266532 blocks. Jun 24 05:39:01 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x90202 action 0xe frozen Jun 24 05:39:01 Tower kernel: ata1.00: irq_stat 0x00400000, PHY RDY changed Jun 24 05:39:01 Tower kernel: ata1: SError: { RecovComm Persist PHYRdyChg 10B8B } Jun 24 05:39:01 Tower kernel: ata1.00: failed command: SMART Jun 24 05:39:01 Tower kernel: ata1.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Jun 24 05:39:01 Tower kernel: res 50/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jun 24 05:39:01 Tower kernel: ata1.00: status: { DRDY } Jun 24 05:39:01 Tower kernel: ata1: hard resetting link Jun 24 05:39:01 Tower kernel: md: parity incorrect: 128 Jun 24 05:39:11 Tower kernel: ata1: softreset failed (1st FIS failed) Jun 24 05:39:11 Tower kernel: ata1: hard resetting link Jun 24 05:39:21 Tower kernel: ata1: softreset failed (1st FIS failed) Jun 24 05:39:21 Tower kernel: ata1: hard resetting link Jun 24 05:39:56 Tower kernel: ata1: softreset failed (1st FIS failed) Jun 24 05:39:56 Tower kernel: ata1: limiting SATA link speed to 1.5 Gbps Jun 24 05:39:56 Tower kernel: ata1: hard resetting link Jun 24 05:40:01 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 24 05:40:01 Tower kernel: ata1.00: link online but device misclassifed Jun 24 05:40:06 Tower kernel: ata1.00: qc timeout (cmd 0xec) Jun 24 05:40:06 Tower kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) Jun 24 05:40:06 Tower kernel: ata1.00: revalidation failed (errno=-5) Jun 24 05:40:06 Tower kernel: ata1: hard resetting link Jun 24 05:40:16 Tower kernel: ata1: softreset failed (1st FIS failed) Jun 24 05:40:16 Tower kernel: ata1: hard resetting link Jun 24 05:40:26 Tower kernel: ata1: softreset failed (1st FIS failed) Jun 24 05:40:26 Tower kernel: ata1: hard resetting link Jun 24 05:41:01 Tower kernel: ata1: softreset failed (1st FIS failed) Jun 24 05:41:01 Tower kernel: ata1: hard resetting link Jun 24 05:41:06 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 24 05:41:06 Tower kernel: ata1.00: link online but device misclassifed Jun 24 05:41:16 Tower kernel: ata1.00: qc timeout (cmd 0xec) Jun 24 05:41:16 Tower kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) Jun 24 05:41:16 Tower kernel: ata1.00: revalidation failed (errno=-5) Jun 24 05:41:16 Tower kernel: ata1: hard resetting link Jun 24 05:41:26 Tower kernel: ata1: softreset failed (1st FIS failed) Jun 24 05:41:26 Tower kernel: ata1: hard resetting link Jun 24 05:41:36 Tower kernel: ata1: softreset failed (1st FIS failed) Jun 24 05:41:36 Tower kernel: ata1: hard resetting link Jun 24 05:42:11 Tower kernel: ata1: softreset failed (1st FIS failed) Jun 24 05:42:11 Tower kernel: ata1: hard resetting link Jun 24 05:42:17 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 24 05:42:17 Tower kernel: ata1.00: link online but device misclassifed Jun 24 05:42:47 Tower kernel: ata1.00: qc timeout (cmd 0xec) Jun 24 05:42:47 Tower kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) Jun 24 05:42:47 Tower kernel: ata1.00: revalidation failed (errno=-5) Jun 24 05:42:47 Tower kernel: ata1.00: disabled Jun 24 05:42:47 Tower kernel: ata1: hard resetting link Jun 24 05:42:57 Tower kernel: ata1: softreset failed (1st FIS failed) Jun 24 05:42:57 Tower kernel: ata1: hard resetting link Jun 24 05:43:07 Tower kernel: ata1: softreset failed (1st FIS failed) Jun 24 05:43:07 Tower kernel: ata1: hard resetting link Jun 24 05:43:42 Tower kernel: ata1: softreset failed (1st FIS failed) Jun 24 05:43:42 Tower kernel: ata1: limiting SATA link speed to 1.5 Gbps Jun 24 05:43:42 Tower kernel: ata1: hard resetting link Jun 24 05:43:47 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 24 05:43:47 Tower kernel: ata1.00: link online but device misclassifed Jun 24 05:43:47 Tower kernel: ata1: link online but 1 devices misclassified, device detection might fail Jun 24 05:43:47 Tower kernel: sd 0:0:0:0: rejecting I/O to offline device Jun 24 05:43:47 Tower kernel: sd 0:0:0:0: [sda] killing request Jun 24 05:43:47 Tower kernel: sd 0:0:0:0: rejecting I/O to offline device Jun 24 05:43:47 Tower last message repeated 3 times Jun 24 05:43:47 Tower kernel: ata1: EH complete Jun 24 05:43:47 Tower kernel: sd 0:0:0:0: [sda] Unhandled error code Jun 24 05:43:47 Tower kernel: sd 0:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00 Jun 24 05:43:47 Tower kernel: sd 0:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 00 00 0c 40 00 00 20 00 Jun 24 05:43:47 Tower kernel: end_request: I/O error, dev sda, sector 3136 Jun 24 05:43:47 Tower kernel: ata1.00: detaching (SCSI 0:0:0:0) Jun 24 05:43:47 Tower kernel: md: disk0 write error Jun 24 05:43:47 Tower kernel: handle_stripe write error: 128/0, count: 1 Jun 24 05:43:47 Tower kernel: md: disk0 read error Jun 24 05:43:47 Tower kernel: handle_stripe read error: 3104/0, count: 1 Jun 24 05:43:47 Tower kernel: md: disk0 read error syslog.zip

My parity drive has a red ball next to it, I think the problem started here syslog1.zip

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