Alyred

Got the BIOS option for Power Supply Idle Control set to "typical" and the server just crashed again while idle. Since it went for weeks prior to the change and this time it crashed within an hour, it appears to have made things less stable, or I just got unlucky. @JorgeB, you replied to someone else's post a couple of years ago that said the go file line to disable C6 should no longer be needed with the Power Supply Idle Control set to Typical. Is that still the case or is there possible a regression bug in 6.12.x? I've now setup the local syslog server but the only option it gives for "local syslog folder" is "<custom>" and won't accept any input. I've mirrored it to flash for the time being wit ha 10mb maximum filesize.

Thanks. Did you see something in particular in my diagnostics that made you believe it was something specific in my settings? The system ran TrueNAS for months before UnRAID without issue, though I did update the BIOS once for the new AGESA API when I installed UnRAID. I have most of the overclocking turned off, though the memory is running at an overclocked profile as it was before and I did tune the elliptical curve down slightly. I'll check for the c-state settings.

I was working on configuring a new VM with the SPICE VM Console Protocol, and my VM stopped responding. Unfortunately, it was because my server had crashed (dirty) and restarted. I'm seeing Fix Common Problems telling me my server has detected hardware errors, and suggests in install mcelog via the NerdPack plugin, but I don't think that plugin is available anymore. Not sure what hardware error occurred, but would like to learn how to find out.

Dang... sorry, I read that a "powerdown -r" command would do what I thought was a clean shutdown so I tried it... and it's now rebuilding parity. Gonna be a long 24 hours. Running losetup now gives me the following (not that it helps now): NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE DIO LOG-SEC /dev/loop1 0 0 1 1 /boot/bzfirmware 0 512 /dev/loop2 0 0 1 0 /mnt/sata_top/system/docker/docker.img 0 512 /dev/loop0 0 0 1 1 /boot/bzmodules 0 512 I had just finished moving all of my data off of a different cache drive in preparation for restarting to install new drives, but was concerned about the system at that point so just restarted to minimize any other changes, hoping that the shutdown had been clean. When I was looking for the problem and going through other posts, I did try umounting the /dev/loop2 It said that there was no such device mounted. I didn't try it through the zfs unmount command.

Hi all, I'd appreciate some help. I have a ZFS pool that won't let go: Jul 9 01:50:16 Diamond emhttpd: Unmounting disks... Jul 9 01:50:16 Diamond emhttpd: shcmd (1774741): /usr/sbin/zpool export sata_top Jul 9 01:50:16 Diamond root: cannot unmount '/mnt/sata_top/system': pool or dataset is busy Jul 9 01:50:16 Diamond emhttpd: shcmd (1774741): exit status: 1 Jul 9 01:50:16 Diamond emhttpd: Retry unmounting disk share(s)... Jul 9 01:50:21 Diamond emhttpd: Unmounting disks... Jul 9 01:50:21 Diamond emhttpd: shcmd (1774742): /usr/sbin/zpool export sata_top Jul 9 01:50:21 Diamond root: cannot unmount '/mnt/sata_top/system': pool or dataset is busy Jul 9 01:50:21 Diamond emhttpd: shcmd (1774742): exit status: 1 Jul 9 01:50:21 Diamond emhttpd: Retry unmounting disk share(s)... Jul 9 01:50:26 Diamond emhttpd: Unmounting disks... Jul 9 01:50:26 Diamond emhttpd: shcmd (1774743): /usr/sbin/zpool export sata_top Jul 9 01:50:26 Diamond root: cannot unmount '/mnt/sata_top/system': pool or dataset is busy Jul 9 01:50:26 Diamond emhttpd: shcmd (1774743): exit status: 1 Jul 9 01:50:26 Diamond emhttpd: Retry unmounting disk share(s)... Jul 9 01:50:31 Diamond emhttpd: Unmounting disks... Jul 9 01:50:31 Diamond emhttpd: shcmd (1774744): /usr/sbin/zpool export sata_top Jul 9 01:50:31 Diamond root: cannot unmount '/mnt/sata_top/system': pool or dataset is busy Jul 9 01:50:31 Diamond emhttpd: shcmd (1774744): exit status: 1 Jul 9 01:50:31 Diamond emhttpd: Retry unmounting disk share(s)... I stopped all of my VMs, my dockers, then stopped the docker and VM service from the gui. The system share IS on that cache pool (sata_top). There's no other activity that I can find and several other posts that suggest finding the process and killing it using lsof (lsof | grep sata_top, etc) don't return with any results. I'm unsure what to do from here but would really like to not have to rebuild parity after a restart. Any other things i can try?

I don't think preclears make disc disk mountable, they write a special partition to the drive as a signature so that UnRaid recognizes it as ready for the array without another zeroing operation.

So I'm thinking there's some sort of error in how the Preclear plugin handles multiple drives at once. After my 4th drive "failed" preclear with the same errors I was having before, I restarted the UnRaid server with no changes to the system, and ran preclear again on the drive. This time it succeeded with only running the one drive by itself, though it did the same "hiccup" at the end where the DD process hung and had to be restarted once... but was successful and completed the preclear. This was on the same port as before, same exact hardware. Jul 05 15:46:24 preclear_disk_<REDACTED4>_27243: Preclear Disk Version: 1.0.27 Jul 05 15:46:24 preclear_disk_<REDACTED4>_27243: Restoring previous instance of preclear Jul 05 15:52:05 preclear_disk_<REDACTED4>_27243: Disk size: 22000969973760 Jul 05 15:52:05 preclear_disk_<REDACTED4>_27243: Disk blocks: 5371330560 Jul 05 15:52:05 preclear_disk_<REDACTED4>_27243: Blocks (512 bytes): 42970644480 Jul 05 15:52:05 preclear_disk_<REDACTED4>_27243: Block size: 4096 Jul 05 15:52:05 preclear_disk_<REDACTED4>_27243: Start sector: 0 Jul 05 15:52:07 preclear_disk_<REDACTED4>_27243: Zeroing: zeroing the disk started 1 of 5 retries... Jul 05 15:52:07 preclear_disk_<REDACTED4>_27243: Continuing disk write on byte 12524462276608 Jul 05 20:53:58 preclear_disk_<REDACTED4>_27243: Zeroing: progress - 75% zeroed @ 200 MB/s Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 4511214+0 records in Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 4511214+0 records out Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 9460701462528 bytes (9.5 TB, 8.6 TiB) copied, 50706.2 s, 187 MB/s Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 4511944+0 records in Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 4511944+0 records out Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 9462232383488 bytes (9.5 TB, 8.6 TiB) copied, 50717.8 s, 187 MB/s Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 4512735+0 records in Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 4512735+0 records out Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 9463891230720 bytes (9.5 TB, 8.6 TiB) copied, 50730.3 s, 187 MB/s Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 4513463+0 records in Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 4513463+0 records out Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 9465417957376 bytes (9.5 TB, 8.6 TiB) copied, 50741.8 s, 187 MB/s Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 4514256+0 records in Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 4514256+0 records out Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 9467080998912 bytes (9.5 TB, 8.6 TiB) copied, 50754.3 s, 187 MB/s Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 4514985+0 records in Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 4514985+0 records out Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 9468609822720 bytes (9.5 TB, 8.6 TiB) copied, 50765.9 s, 187 MB/s Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 4515777+0 records in Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 4515777+0 records out Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 9470270767104 bytes (9.5 TB, 8.6 TiB) copied, 50778.4 s, 187 MB/s Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 4516509+0 records in Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 4516509+0 records out Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 9471805882368 bytes (9.5 TB, 8.6 TiB) copied, 50789.9 s, 186 MB/s Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 4517298+0 records in Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 4517298+0 records out Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 9473460535296 bytes (9.5 TB, 8.6 TiB) copied, 50802.4 s, 186 MB/s Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 4518026+0 records in Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 4518026+0 records out Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: dd output: 9474987261952 bytes (9.5 TB, 8.6 TiB) copied, 50813.9 s, 186 MB/s Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: dd process hung at 21999449538560, killing ... Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Zeroing: zeroing the disk started 2 of 5 retries... Jul 06 06:02:39 preclear_disk_<REDACTED4>_27243: Continuing disk write on byte 21999447441408 Jul 06 06:05:11 preclear_disk_<REDACTED4>_27243: Zeroing: progress - 99% zeroed @ 0 MB/s Jul 06 06:05:27 preclear_disk_<REDACTED4>_27243: Zeroing: progress - 100% zeroed @ 223 MB/s Jul 06 06:05:29 preclear_disk_<REDACTED4>_27243: Zeroing: zeroing the disk completed! Jul 06 06:05:29 preclear_disk_<REDACTED4>_27243: Signature: writing signature... Jul 06 06:05:30 preclear_disk_<REDACTED4>_27243: Signature: verifying Unraid's signature on the MBR ... Jul 06 06:05:30 preclear_disk_<REDACTED4>_27243: Signature: Unraid preclear signature is valid! Jul 06 06:05:32 preclear_disk_<REDACTED4>_27243: S.M.A.R.T.: Cycle 1 Jul 06 06:05:32 preclear_disk_<REDACTED4>_27243: S.M.A.R.T.: Jul 06 06:05:32 preclear_disk_<REDACTED4>_27243: S.M.A.R.T.: ATTRIBUTE INITIAL NOW STATUS Jul 06 06:05:32 preclear_disk_<REDACTED4>_27243: S.M.A.R.T.: Reallocated_Sector_Ct 0 0 - Jul 06 06:05:32 preclear_disk_<REDACTED4>_27243: S.M.A.R.T.: Power_On_Hours 393 420 Up 27 Jul 06 06:05:32 preclear_disk_<REDACTED4>_27243: S.M.A.R.T.: Temperature_Celsius 32 41 Up 9 Jul 06 06:05:32 preclear_disk_<REDACTED4>_27243: S.M.A.R.T.: Reallocated_Event_Count 0 0 - Jul 06 06:05:32 preclear_disk_<REDACTED4>_27243: S.M.A.R.T.: Current_Pending_Sector 0 0 - Jul 06 06:05:32 preclear_disk_<REDACTED4>_27243: S.M.A.R.T.: Offline_Uncorrectable 0 0 - Jul 06 06:05:32 preclear_disk_<REDACTED4>_27243: S.M.A.R.T.: UDMA_CRC_Error_Count 0 0 - Jul 06 06:05:32 preclear_disk_<REDACTED4>_27243: S.M.A.R.T.: Jul 06 06:05:32 preclear_disk_<REDACTED4>_27243: Cycle: elapsed time: 27:19:38 Jul 06 06:05:32 preclear_disk_<REDACTED4>_27243: Preclear: total elapsed time: 27:19:41 No errors in dmesg, final preclear stats all showed success. #################################################################################################### # Unraid Server Preclear of disk <REDACTED4> # # Cycle 1 of 1, partition start on sector 64. # # # # Step 1 of 3 - Zeroing the disk: [27:19:12 @ 223 MB/s] SUCCESS # # Step 2 of 3 - Writing Unraid's Preclear signature: SUCCESS # # Step 3 of 3 - Verifying Unraid's Preclear signature: SUCCESS # # # # # # # # # # # #################################################################################################### # Cycle elapsed time: 27:19:38 | Total elapsed time: 27:19:39 # #################################################################################################### #################################################################################################### # S.M.A.R.T. Status (device type: default) # # # # ATTRIBUTE INITIAL CYCLE 1 STATUS # # Reallocated_Sector_Ct 0 0 - # # Power_On_Hours 393 420 Up 27 # # Temperature_Celsius 32 41 Up 9 # # Reallocated_Event_Count 0 0 - # # Current_Pending_Sector 0 0 - # # Offline_Uncorrectable 0 0 - # # UDMA_CRC_Error_Count 0 0 - # # # # # #################################################################################################### # # #################################################################################################### --> ATTENTION: Please take a look into the SMART report above for drive health issues. --> RESULT: Preclear Finished Successfully!. If anyone has these issues with UnRAID 6.12, try rebooting your server and running the preclear again on one drive at a time per reboot. Seems to clear out whatever in there is getting confused. Would be interesting to see if more folks have gotten the "dd hang" that was still able to recover, so didn't notice... 3/4 of the preclears I did still had that in each one.

Hm, interesting... I'd have to figure out a way to either run docker without an array, or temporarily get an array going just long enough to get a docker config. DIdn't particularly want to go halfway on that but might be my only option in that regard. Of course, I guess I could just downgrade that server to 6.11.5 and see how that goes... or just trust that the errors are particular to the UD Preclear plugin and not an actual indication of issues with other pieces of my hardware, which was the original thing I wanted to run it through some exercises on.

I've now replaced my LSI card with a similar one from Art of Server as well, and went through another preclear cycle... and 3 drives completed fine, while a different one than before failed again with the same issue/error in the preclear log. I've replaced both the card and the cable at this point, and since all of the drives HAVE precleared fine one one port or another, I'm loathe to think that it's the drives themselves. I've upgraded to 6.12.2 and made sure the plugins were all updated. No errors in dmesg, nothing at all suspicious between boot up sequences and the assigning of partitions to the passed drives: [Mon Jul 3 15:58:07 2023] mdcmd (30): import 29 [Mon Jul 3 15:58:07 2023] md: import_slot: 29 empty [Tue Jul 4 08:03:00 2023] nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint. [Tue Jul 4 08:03:00 2023] nvidia-uvm: Loaded the UVM driver, major device number 239. [Tue Jul 4 19:38:21 2023] sdk: sdk1 [Tue Jul 4 20:01:23 2023] sdj: sdj1 [Tue Jul 4 20:27:52 2023] sdl: sdl1 The first drive to pass (the drive I had troubles with on the most recent attempt) cleared everything successfully: Jul 03 16:00:23 preclear_disk_<REDACTED1>_11281: Preclear Disk Version: 1.0.27 Jul 03 16:00:24 preclear_disk_<REDACTED1>_11281: Disk size: 22000969973760 Jul 03 16:00:24 preclear_disk_<REDACTED1>_11281: Disk blocks: 5371330560 Jul 03 16:00:24 preclear_disk_<REDACTED1>_11281: Blocks (512 bytes): 42970644480 Jul 03 16:00:24 preclear_disk_<REDACTED1>_11281: Block size: 4096 Jul 03 16:00:24 preclear_disk_<REDACTED1>_11281: Start sector: 0 Jul 03 16:00:25 preclear_disk_<REDACTED1>_11281: Zeroing: zeroing the disk started 1 of 5 retries... Jul 03 16:00:25 preclear_disk_<REDACTED1>_11281: Zeroing: emptying the MBR. Jul 03 21:29:12 preclear_disk_<REDACTED1>_11281: Zeroing: progress - 25% zeroed @ 268 MB/s Jul 04 03:27:43 preclear_disk_<REDACTED1>_11281: Zeroing: progress - 50% zeroed @ 240 MB/s Jul 04 10:20:38 preclear_disk_<REDACTED1>_11281: Zeroing: progress - 75% zeroed @ 200 MB/s Jul 04 19:38:19 preclear_disk_<REDACTED1>_11281: Zeroing: progress - 100% zeroed @ 8 MB/s Jul 04 19:38:21 preclear_disk_<REDACTED1>_11281: Zeroing: zeroing the disk completed! Jul 04 19:38:21 preclear_disk_<REDACTED1>_11281: Signature: writing signature... Jul 04 19:38:22 preclear_disk_<REDACTED1>_11281: Signature: verifying Unraid's signature on the MBR ... Jul 04 19:38:23 preclear_disk_<REDACTED1>_11281: Signature: Unraid preclear signature is valid! Jul 04 19:38:23 preclear_disk_<REDACTED1>_11281: Post-Read: post-read verification started 1 of 5 retries... Jul 04 19:38:23 preclear_disk_<REDACTED1>_11281: Post-Read: verifying the beginning of the disk. Jul 04 19:38:24 preclear_disk_<REDACTED1>_11281: Post-Read: verifying the rest of the disk. Drive 2 and 3 had an error, but were able to recover (2 and 3 were almost the same, but a slight difference near the end): Jul 04 20:00:43 preclear_disk_<REDACTED2>_17399: Zeroing: dd output: 21990459047936 bytes (22 TB, 20 TiB) copied, 98068.3 s, 224 MB/s Jul 04 20:00:43 preclear_disk_<REDACTED2>_17399: Zeroing: dd output: 10486584+0 records in Jul 04 20:00:43 preclear_disk_<REDACTED2>_17399: Zeroing: dd output: 10486584+0 records out Jul 04 20:00:43 preclear_disk_<REDACTED2>_17399: Zeroing: dd output: 21991960608768 bytes (22 TB, 20 TiB) copied, 98079.8 s, 224 MB/s Jul 04 20:00:43 preclear_disk_<REDACTED2>_17399: Zeroing: dd output: 10487364+0 records in Jul 04 20:00:43 preclear_disk_<REDACTED2>_17399: Zeroing: dd output: 10487364+0 records out Jul 04 20:00:43 preclear_disk_<REDACTED2>_17399: Zeroing: dd output: 21993596387328 bytes (22 TB, 20 TiB) copied, 98092.3 s, 224 MB/s Jul 04 20:00:43 preclear_disk_<REDACTED2>_17399: Zeroing: dd output: 10488085+0 records in Jul 04 20:00:43 preclear_disk_<REDACTED2>_17399: Zeroing: dd output: 10488085+0 records out Jul 04 20:00:43 preclear_disk_<REDACTED2>_17399: Zeroing: dd output: 21995108433920 bytes (22 TB, 20 TiB) copied, 98103.8 s, 224 MB/s Jul 04 20:00:43 preclear_disk_<REDACTED2>_17399: Zeroing: dd output: 10488862+0 records in Jul 04 20:00:43 preclear_disk_<REDACTED2>_17399: Zeroing: dd output: 10488862+0 records out Jul 04 20:00:43 preclear_disk_<REDACTED2>_17399: Zeroing: dd output: 21996737921024 bytes (22 TB, 20 TiB) copied, 98116.3 s, 224 MB/s Jul 04 20:00:43 preclear_disk_<REDACTED2>_17399: Zeroing: dd output: 10489577+0 records in Jul 04 20:00:43 preclear_disk_<REDACTED2>_17399: Zeroing: dd output: 10489577+0 records out Jul 04 20:00:43 preclear_disk_<REDACTED2>_17399: Zeroing: dd output: 21998237384704 bytes (22 TB, 20 TiB) copied, 98127.8 s, 224 MB/s Jul 04 20:00:43 preclear_disk_<REDACTED2>_17399: Zeroing: dd output: 10490352+0 records in Jul 04 20:00:43 preclear_disk_<REDACTED2>_17399: Zeroing: dd output: 10490352+0 records out Jul 04 20:00:43 preclear_disk_<REDACTED2>_17399: Zeroing: dd output: 21999862677504 bytes (22 TB, 20 TiB) copied, 98140.3 s, 224 MB/s Jul 04 20:00:43 preclear_disk_<REDACTED2>_17399: dd process hung at 21999864774656, killing ... Jul 04 20:00:43 preclear_disk_<REDACTED2>_17399: Zeroing: zeroing the disk started 2 of 5 retries... Jul 04 20:00:43 preclear_disk_<REDACTED2>_17399: Continuing disk write on byte 21999862677504 Jul 04 20:01:14 preclear_disk_<REDACTED2>_17399: Zeroing: progress - 99% zeroed @ 0 MB/s Jul 04 20:01:18 preclear_disk_<REDACTED2>_17399: Zeroing: zeroing the disk completed! Jul 04 20:01:18 preclear_disk_<REDACTED2>_17399: Signature: writing signature... Jul 04 20:01:24 preclear_disk_<REDACTED2>_17399: Signature: verifying Unraid's signature on the MBR ... Jul 04 20:01:25 preclear_disk_<REDACTED2>_17399: Signature: Unraid preclear signature is valid! Jul 04 20:01:25 preclear_disk_<REDACTED2>_17399: Post-Read: post-read verification started 1 of 5 retries... Jul 04 20:01:25 preclear_disk_<REDACTED2>_17399: Post-Read: verifying the beginning of the disk. Jul 04 20:01:26 preclear_disk_<REDACTED2>_17399: Post-Read: verifying the rest of the disk. Drive 3 was similar but had this near the end, missing the line for progress - 99% zeroed @ 0 MB/s: Jul 04 20:25:07 preclear_disk_<REDACTED3>_10636: Zeroing: dd output: 22000252747776 bytes (22 TB, 20 TiB) copied, 98699.8 s, 223 MB/s Jul 04 20:25:07 preclear_disk_<REDACTED3>_10636: dd process hung at 22000254844928, killing ... Jul 04 20:25:07 preclear_disk_<REDACTED3>_10636: Zeroing: zeroing the disk started 2 of 5 retries... Jul 04 20:25:07 preclear_disk_<REDACTED3>_10636: Continuing disk write on byte 22000252747776 Jul 04 20:27:49 preclear_disk_<REDACTED3>_10636: Zeroing: zeroing the disk completed! Jul 04 20:27:49 preclear_disk_<REDACTED3>_10636: Signature: writing signature... Jul 04 20:27:53 preclear_disk_<REDACTED3>_10636: Signature: verifying Unraid's signature on the MBR ... Jul 04 20:27:53 preclear_disk_<REDACTED3>_10636: Signature: Unraid preclear signature is valid! Jul 04 20:27:53 preclear_disk_<REDACTED3>_10636: Post-Read: post-read verification started 1 of 5 retries... Jul 04 20:27:53 preclear_disk_<REDACTED3>_10636: Post-Read: verifying the beginning of the disk. Jul 04 20:27:54 preclear_disk_<REDACTED3>_10636: Post-Read: verifying the rest of the disk. Finally, the 4th drive got to 99% zeroed, and then failed to resume: Jul 04 20:45:38 preclear_disk_<REDACTED4>_7253: Zeroing: dd output: 10485099+0 records out Jul 04 20:45:38 preclear_disk_<REDACTED4>_7253: Zeroing: dd output: 21988846338048 bytes (22 TB, 20 TiB) copied, 98008.1 s, 224 MB/s Jul 04 20:45:38 preclear_disk_<REDACTED4>_7253: Zeroing: dd output: 10485824+0 records in Jul 04 20:45:38 preclear_disk_<REDACTED4>_7253: Zeroing: dd output: 10485824+0 records out Jul 04 20:45:38 preclear_disk_<REDACTED4>_7253: Zeroing: dd output: 21990366773248 bytes (22 TB, 20 TiB) copied, 98019.5 s, 224 MB/s Jul 04 20:45:38 preclear_disk_<REDACTED4>_7253: Zeroing: dd output: 10486618+0 records in Jul 04 20:45:38 preclear_disk_<REDACTED4>_7253: Zeroing: dd output: 10486618+0 records out Jul 04 20:45:38 preclear_disk_<REDACTED4>_7253: Zeroing: dd output: 21992031911936 bytes (22 TB, 20 TiB) copied, 98032.1 s, 224 MB/s Jul 04 20:45:38 preclear_disk_<REDACTED4>_7253: Zeroing: dd output: 10487344+0 records in Jul 04 20:45:38 preclear_disk_<REDACTED4>_7253: Zeroing: dd output: 10487344+0 records out Jul 04 20:45:38 preclear_disk_<REDACTED4>_7253: Zeroing: dd output: 21993554444288 bytes (22 TB, 20 TiB) copied, 98043.6 s, 224 MB/s Jul 04 20:45:38 preclear_disk_<REDACTED4>_7253: Zeroing: dd output: 10488134+0 records in Jul 04 20:45:38 preclear_disk_<REDACTED4>_7253: Zeroing: dd output: 10488134+0 records out Jul 04 20:45:38 preclear_disk_<REDACTED4>_7253: Zeroing: dd output: 21995211194368 bytes (22 TB, 20 TiB) copied, 98056.1 s, 224 MB/s Jul 04 20:45:38 preclear_disk_<REDACTED4>_7253: Zeroing: dd output: 10488927+0 records in Jul 04 20:45:38 preclear_disk_<REDACTED4>_7253: Zeroing: dd output: 10488927+0 records out Jul 04 20:45:38 preclear_disk_<REDACTED4>_7253: Zeroing: dd output: 21996874235904 bytes (22 TB, 20 TiB) copied, 98068.6 s, 224 MB/s Jul 04 20:45:38 preclear_disk_<REDACTED4>_7253: Zeroing: dd output: 10489715+0 records in Jul 04 20:45:38 preclear_disk_<REDACTED4>_7253: Zeroing: dd output: 10489715+0 records out Jul 04 20:45:38 preclear_disk_<REDACTED4>_7253: Zeroing: dd output: 21998526791680 bytes (22 TB, 20 TiB) copied, 98081.1 s, 224 MB/s Jul 04 20:45:38 preclear_disk_<REDACTED4>_7253: Zeroing: dd output: 10490507+0 records in Jul 04 20:45:38 preclear_disk_<REDACTED4>_7253: Zeroing: dd output: 10490507+0 records out Jul 04 20:45:38 preclear_disk_<REDACTED4>_7253: Zeroing: dd output: 22000187736064 bytes (22 TB, 20 TiB) copied, 98093.6 s, 224 MB/s Jul 04 20:45:38 preclear_disk_<REDACTED4>_7253: dd process hung at 22000189833216, killing ... Jul 04 20:45:38 preclear_disk_<REDACTED4>_7253: Zeroing: zeroing the disk started 2 of 5 retries... Jul 04 20:45:38 preclear_disk_<REDACTED4>_7253: Continuing disk write on byte 22000187736064 Jul 04 20:49:54 preclear_disk_<REDACTED4>_7253: Zeroing: dd output: Jul 04 20:49:54 preclear_disk_<REDACTED4>_7253: dd process hung at 0, killing ... Jul 04 20:49:54 preclear_disk_<REDACTED4>_7253: Zeroing: zeroing the disk started 3 of 5 retries... Jul 04 20:49:54 preclear_disk_<REDACTED4>_7253: Zeroing: emptying the MBR. So it's almost like it got progressively worse with each preclear to write and verify the signature at the end, and on the last disk it couldn't recover somehow so started over from 0. The problem is, last time I let it go through to completion, it failed again and then hit it's 5 retries limit and terminated with a drive preclear failure. I haven't tried downgrading to 6.11.5 as this box was new and is still in trial. It's definitely interesting that you're seeing a larger size reported in the previous version of UnRAID - is there some sort of weird variable length or storage issue between the two versions of UnRAID and the plugin? Happy to try any additional things or suggestions. It's going through it's zeroing yet again now, while the other drives are doing the post-read. There's literally nothing else running on this machine except for some fairly standard plugins (CA, UDs, nVidia driver) and have never started the array or the pools.

Yeah, after the 5th attempt on that port, it "errors encountered, please check the log" and when I check the log, it says it encoutered SMART failures, but then showed no SMART failures: This is after the 5th "attempt", started in the previously pasted log: Jun 29 18:02:13 preclear_disk_<REDACTED>_20300: Zeroing: dd output: 10486357+0 records out Jun 29 18:02:13 preclear_disk_<REDACTED>_20300: Zeroing: dd output: 21991484555264 bytes (22 TB, 20 TiB) copied, 99134.1 s, 222 MB/s Jun 29 18:02:13 preclear_disk_<REDACTED>_20300: Zeroing: dd output: 10487140+0 records in Jun 29 18:02:13 preclear_disk_<REDACTED>_20300: Zeroing: dd output: 10487140+0 records out Jun 29 18:02:13 preclear_disk_<REDACTED>_20300: Zeroing: dd output: 21993126625280 bytes (22 TB, 20 TiB) copied, 99146.8 s, 222 MB/s Jun 29 18:02:13 preclear_disk_<REDACTED>_20300: Zeroing: dd output: 10487927+0 records in Jun 29 18:02:13 preclear_disk_<REDACTED>_20300: Zeroing: dd output: 10487927+0 records out Jun 29 18:02:13 preclear_disk_<REDACTED>_20300: Zeroing: dd output: 21994777083904 bytes (22 TB, 20 TiB) copied, 99159.5 s, 222 MB/s Jun 29 18:02:13 preclear_disk_<REDACTED>_20300: Zeroing: dd output: 10488650+0 records in Jun 29 18:02:13 preclear_disk_<REDACTED>_20300: Zeroing: dd output: 10488650+0 records out Jun 29 18:02:13 preclear_disk_<REDACTED>_20300: Zeroing: dd output: 21996293324800 bytes (22 TB, 20 TiB) copied, 99171.2 s, 222 MB/s Jun 29 18:02:13 preclear_disk_<REDACTED>_20300: Zeroing: dd output: 10489434+0 records in Jun 29 18:02:13 preclear_disk_<REDACTED>_20300: Zeroing: dd output: 10489434+0 records out Jun 29 18:02:13 preclear_disk_<REDACTED>_20300: Zeroing: dd output: 21997937491968 bytes (22 TB, 20 TiB) copied, 99183.9 s, 222 MB/s Jun 29 18:02:13 preclear_disk_<REDACTED>_20300: Zeroing: dd output: 10490224+0 records in Jun 29 18:02:13 preclear_disk_<REDACTED>_20300: Zeroing: dd output: 10490224+0 records out Jun 29 18:02:13 preclear_disk_<REDACTED>_20300: Zeroing: dd output: 21999594242048 bytes (22 TB, 20 TiB) copied, 99196.6 s, 222 MB/s Jun 29 18:02:13 preclear_disk_<REDACTED>_20300: Zeroing: zeroing the disk failed! Jun 29 18:11:56 preclear_disk_<REDACTED>_20300: S.M.A.R.T.: Error: Jun 29 18:11:56 preclear_disk_<REDACTED>_20300: S.M.A.R.T.: Jun 29 18:11:56 preclear_disk_<REDACTED>_20300: S.M.A.R.T.: ATTRIBUTE INITIAL NOW STATUS Jun 29 18:11:56 preclear_disk_<REDACTED>_20300: S.M.A.R.T.: Reallocated_Sector_Ct 0 - Jun 29 18:11:56 preclear_disk_<REDACTED>_20300: S.M.A.R.T.: Power_On_Hours 159 - Jun 29 18:11:56 preclear_disk_<REDACTED>_20300: S.M.A.R.T.: Temperature_Celsius 41 - Jun 29 18:11:56 preclear_disk_<REDACTED>_20300: S.M.A.R.T.: Reallocated_Event_Count 0 - Jun 29 18:11:56 preclear_disk_<REDACTED>_20300: S.M.A.R.T.: Current_Pending_Sector 0 - Jun 29 18:11:56 preclear_disk_<REDACTED>_20300: S.M.A.R.T.: Offline_Uncorrectable 0 - Jun 29 18:11:56 preclear_disk_<REDACTED>_20300: S.M.A.R.T.: UDMA_CRC_Error_Count 0 - Jun 29 18:11:56 preclear_disk_<REDACTED>_20300: S.M.A.R.T.: Jun 29 18:11:56 preclear_disk_<REDACTED>_20300: error encountered, exiting ... Anyone have any ideas why it would fail the preclear, but seem to be OK on every other port? Again, I've replaced the cable and the drive has cleared on another ports. The drive gets to 99% on the zero then starts over, taking several days to completely fail. I do see the other SATA Ports pull an error at the end of zeroing but are able to recover. I'm running 4x22TB WD Red Pros from an LSI 9207-4i4e SAS HBA with the drives connected to the internal 8027 port with a SATA foward breakout cable. My /var/logs/messages file is empty, but it is a brand-new server where I've only been clearing and testing disks so far. Is there another or more detailed log I can pull?

I've been trying to preclear a set of new disks on a brand-new UnRAID 6.12.1 server for a week now. I can always get 3 disks to finish preclear fine, but one of the four keeps restarting. It gets to 99% on zeroing and then freezes, tries to restart at the sector it froze on, freezes again, and then restarts at 0%. At first I thought it was the disk itself, but I swapped the disk with other array cables, and then that disk pre-cleared fine but the one plugged into the old port failed. I figured I had a bad cable, so replaced that (It's a forward breakout 8087->SATA cable) ordered new and the same SATA plug failed, same drive as last time. This drive precleared previously on a different SATA port. I'll post the error below, but to be clear: Drive1 SATA1->Cleared Drive2 SATA2->Cleared Drive3 SATA3->Keeps restarting zeroing phase Drive4 SATA4->Cleared New Configuration/Swapped cables, and Drive1 SATA4->Cleared Drive2 SATA3->Keeps restarting zeroing phase Drive3 SATA2->Cleared Drive4 SATA1->Cleared My HBA is an LSI 9217-4i4e purched from the Art of Server's ebay store and didn't present problems when used in another machine, but I wasn't attaching such large disks there. Could have always developed a problem between now and then, I suppose, as it was pulled from the old machine and in a static bag for a month before being put into the new build. The DD process hangs at a sector near the end but can't recover. It looks like other disks do have the "dd process hung at" issue but are able to recover where they left off. Does it sound like I have a bad HBA? These are large disks (22TB), so I wasn't sure if this was a symptom of previous disks not being large enough to notice the problem yet... has anyone else had troubles clearing a 22TB disk with this plugin? I'm not sure how to interpret the dd process hanging on all of the disks, but being able to recover. Here's one of the error logs (DiskSN changed), but they have all looked like this when the device restarts the clear. They take ~27 hours to do the zeroing so it's a long wait to see if a change has made any difference. preclear_disk_SN_20300.txt

Does anyone have the original template w/layers for the Blue Hex banner, or has anyone re-created it in red and green? Looking for a few variations. Thanks.

Aha! It does, thank you. I saw the env variables on the docker page, but for some reason I was reading the "more settings" as something inside the docker runspace itself. The additional hint on server side scaling was perfect, thank you!

Hi Ich777! I'm trying out your Firefox docker in Unraid and I like the idea, but there's a couple of places that say I can change my resolution by clicking "show more settings"... but I can't find that option! Is it in the firefox menu inside of the container or some other option with the VNC controls?

I was able to get it working with these instructions. A couple of notes of clarification if anyone is still struggling: The PRIVATE_KEY required in the Nordlynx container is NOT the token that NordVPN gives you from your account page on the website. Run that token (from the website) through the get_private_key container as listed above which will give you the PRIVATE_KEY you need to enter into the main Nordlynx container. It doesn't appear that the USER and PASS env variables are actually needed in that container. It seemed to give me a private key once I entered the token properly alone. The only thing I have left is to figure out how to better utilize the QUERY string to select a few different endpoints for convenience. If anyone has already done the work on putting a selection of country codes in, I'd be highly appreciative. There's a country code list here for those still looking: https://api.nordvpn.com/v1/servers/countries Also, still can't get the icon working for some reason. Comes up fine in a web browser but it won't load via the docker settings in Unraid. Edit: Replace the icon URL with (remove brackets): [https:]//s1.nordcdn.com/nordvpn/media/1.752.0/images/global/favicon/favicon-196x196.png

They must have re-re-re fixed something, it appears to be working now! At least, I'm getting a good game server start after update with no further changes...

Hi @ich777! Thanks for you work on all these game servers. It appears that Core Keeper has updated again on Feb 23, 2023 to v. 0.5.2.5 where they are saying they've "fixed dedicated server not working in docker containers", but it seems to be causing a segfault again on my docker instances now: /opt/scripts/start-server.sh: line 84: 116 Segmentation fault ${SERVER_DIR}/CoreKeeperServer -batchmode -logfile ${SERVER_DIR}/CoreKeeperServerLog.txt -world ${WORLD_INDEX} -worldname "${WORLD_NAME}" -datapath "${SERVER_DIR}/Save" ${GAME_PARAMS} 2 > /dev/null Terminated

Actually, your instructions worked fine and swapped over to the new images without issue on both my UnRAID server as well as my (soon to be replaced) Windows Docker. Buttery smooth and all updated, thank you.

Aha, got it. Thank you!

Hi all, still looking into things and learning. One of my cache pools shows the following: Notably the no balance found, current usage ration at 49% with a full balance being recommended. When I click on "Balance" it looks like it's starting, but then just refreshes back to the same screen telling me I need to do a full balance. I've tried moving the small amount of stuff that lives on there off to the array, when the "current usage ratio" goes down to 0%. When I move it back, it's back at 49%. My other caches don't seem to have this issue. Is this something I'm fundamentally misunderstanding and is this something I don't need to worry about? Thanks. Diagnostics attached. diamond-diagnostics-20221011-2253.zip

Hopefully to use it, it won't require too much infrastructure rebuild... Definitely going to hold off on upgrading those NVMes until I find out if I have to rebuild the entire cache pool...

Excellent, thank you! I'm showing all dashes so I think I'm good! As a note for anyone else, I had to read it directly from the directory it is currently in, trying to read it from the /mnt/user share gave me an "Operation not supported While reading flags on <filename>" error. Appreciate your assistance and knowledge to get this worked out, and hope that it helps some others! Was there any news with 6.11 on getting a better solution for this set up (I think it was being discussed as an LVM mode)? I did go ahead and upgrade to 6.11 last night as well since I had the array and VMs all down anyway...

Ok, so I just created a new share and made sure COW was set to "Auto" using the same cache disks (My NVMe array). From the console I did a cp --reflink=never from the one share under /mnt/user/domains to the new share, /mnt/user/vdisk/<vm name>. Reading what I could find this should re-enable copy-on-write, does anyone know of a way I can manually verify? The machines do seem to be running normally, though it's annoying that the one that I'm passing two physical network cards to through IOMMU has to have the cards re-detected each and every time, and then re-configured as if I had removed the old card and installed a new one...

Yup, was afraid of that. Read another post discussing it over the last hour as well from back in May or so, about switching that default off and possible improvements in 6.11. Well... guess I'll get started. Thanks for the help.

So I took a look at the "domains" default share on my Unraid server and the setting was "no" on COW. I don't believe I updated that myself, so should I change it? The recommended settings are to have it "off": If I do change that to "Auto", do I need to adjust the VM disk files already in the share? UnRaid's info there indicates that the nocow attribute is set per file and would have been set to "no" on the vdisk images themselves. If they are set to "Auto" is there a problem, or just a performance impact (and how much of an impact)? Trying to get my head wrapped around this stuff better.