DeathStar Darth

For anyone like me stumbling across this post when in the same situation, I would advise watching Spaceinvader's How to Safely Shrink an Unraid Array video guide on just this topic - you'll want method 2 to be safe rather than method 1 which has a danger zone period!

If you don't mind using userscripts you can bastardise my script at https://github.com/techie2000/unraid/tree/main/boot/config/plugins/user.scripts/scripts/install ncdu at main · techie2000/unraid (github.com) to suit your needs. I have it set to install with the initial array startup.

If you use userscripts, you can bastardise my script https://github.com/techie2000/unraid/tree/main/boot/config/plugins/user.scripts/scripts/install atop which installs atop at the first array startup. a similar script is available for powertop in the same project. As is python3, but I only have one piece of software that needs it so can't guarantee that I have not missed any dependencies. iperf3 is a factory install in the newer versions of unraid (the ones since the nerdpack became an issue)

iperf3 is factory installed these days If you don't mind using userscripts, feel free to bastardise my script that I install Powertop with at each initial start of the array: https://github.com/techie2000/unraid/tree/main/boot/config/plugins/user.scripts/scripts/install Powertop

If you don't mind using user scripts to install it at array startup time, you can use my quick n dirty script and be using v12.52 (at the time of writing) https://github.com/techie2000/unraid/tree/main/boot/config/plugins/user.scripts/scripts/install exiftool iftop, iotop, screen (albeit it an older version for now) and unrar (v6.11) are there as well if required. Feel free to hack it and just install once to extras folder. However, as I review my userscripts from time to time, I'm more likely to check for newer versions and amend the script to download them than I am if blindly having them installed at boot time!

For my personal use I created a userscript that installs unrar fresh on the first array startup. Feel free to bastardise it as much as you like (it's not too pretty, but it does work). https://github.com/techie2000/unraid/tree/main/boot/config/plugins/user.scripts/scripts/install unrar

I am VERY inexperienced with the sed command but putting something like sed -i '/\(mpt2sas_cm[12]: Temperature Threshold flags\|mpt2sas_cm[12]: Current Temp In Celsius\)/d' /var/log/syslog in a user script to run every hour (or frequency of your choosing) will remove the entries from the syslog to make it easier to read (ie without the noise from the entries that you can't control/wish to ignore), but still keep any other mpt2sas entries. I've posted this on https://github.com/techie2000/unraid/tree/main/boot/config/plugins/user.scripts/scripts/Delete mpt2sas noise from syslog for future reference

I'm just self installing any progs these days via user scripts. NCDU is not one I've used for a long time but I've added it my collection if you want to use it https://github.com/techie2000/unraid/tree/main/boot/config/plugins/user.scripts/scripts/install ncdu

Having just installed my first LSI 9201-16e and seen this in my logs, I went digging. It looks like this is coming directly from the driver /** * _scsih_temp_threshold_events - display temperature threshold exceeded events * @ioc: per adapter object * @event_data: the temp threshold event data * Context: interrupt time. * * Return nothing. */ static void _scsih_temp_threshold_events(struct MPT2SAS_ADAPTER *ioc, Mpi2EventDataTemperature_t *event_data) { if (ioc->temp_sensors_count >= event_data->SensorNum) { printk(MPT2SAS_ERR_FMT "Temperature Threshold flags %s%s%s%s" "exceeded for Sensor: %d !!!\n", ioc->name, ((event_data->Status & 0x1) == 1) ? "0 " : " ", ((event_data->Status & 0x2) == 2) ? "1 " : " ", ((event_data->Status & 0x4) == 4) ? "2 " : " ", ((event_data->Status & 0x8) == 8) ? "3 " : " ", event_data->SensorNum); printk(MPT2SAS_ERR_FMT "Current Temp In Celsius: %d\n", ioc->name, event_data->CurrentTemperature); } } I don't know about you, but I don't want to be compiling my own driver I will be ordering a Noctura (or two) to somehow strap to what appeared to be a really rather good heatsink - putting the case sides on sees the reported temps rapidly rise...suspect I am going to need to add another extractor to the case as well to cope with the extra heat the Noctura will (hopefully) suck away from the LSI.

libzen is a shared library used by mediainfo You could setup a UserScript to fire at first array start. I've put an (untested) version in github (it's not pretty() but look like it should work)

@makutaku if you are not comfortable in modifying your go file AND have the UserScripts plugin installed you can add a script to have it installed when you start the array the first time. I've shared my copy at github that should work. (it uses the same principles outlined by jortan above.

If you are not running a version of UnRaid where it is included, and you are familiar with UserScripts plugin, then you can add a script to install it each time you boot the array (or put it in /extras but I think that was been discouraged). I put an example up at github that should work

yes, that's correct. I replied late last night whilst away but didn't have my forum login details to hand so it looks like it gets blocked pending a moderator (just in case you see a similar post later). I rebooted in regular (rather than safe) mode, installed the binhex preclear docker, ran that, and it behaved well I forgot to disable the weekly backup and the law of sod being what it is, it was scheduled for early this morning so got interrupted. I restarted it earlier and its 45% of the way through the read cycle....so fingers crossed from here on in. Update 2022-09-08 07:45 BST - still running happily. Fully expect it to complete Update 2022-09-09 13:45 BST - at 94% of stage 10/10 so unless there is final 'gotcha', we look good.

THEDEATHSTAR-unassigned.devices.preclear-20220905-2035.zip

I removed the Nerd Pack, rebooted and tried a pre-clear again, and observed the same pattern of errors as seen with it present. (note, I again observed intermittent read speeds >0 bytes) I booted in safe mode and set a tail of the syslog going before adding the the CA and UA plugins. I noticed ominous signs on the thumbdrive Sep 5 15:34:41 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Sep 5 15:34:41 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Sep 5 15:34:41 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Sep 5 15:34:41 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 3e c8 00 00 58 00 Sep 5 15:34:41 TheDeathStar kernel: blk_update_request: critical medium error, dev sda, sector 16072 op 0x0:(READ) flags 0x80700 phys_seg 88 prio class 0 Sep 5 15:34:42 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Sep 5 15:34:42 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Sep 5 15:34:42 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Sep 5 15:34:42 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 3e c9 00 00 57 00 Sep 5 15:34:42 TheDeathStar kernel: blk_update_request: critical medium error, dev sda, sector 16073 op 0x0:(READ) flags 0x80000 phys_seg 87 prio class 0 Sep 5 15:34:42 TheDeathStar emhttpd: error: get_fs_sizes, 6059: Input/output error (5): statfs: /boot Sep 5 15:34:42 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Sep 5 15:34:42 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Sep 5 15:34:42 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Sep 5 15:34:42 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 3e c8 00 00 01 00 Sep 5 15:34:42 TheDeathStar kernel: blk_update_request: critical medium error, dev sda, sector 16072 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Sep 5 15:34:42 TheDeathStar kernel: FAT-fs (sda1): FAT read failed (blocknr 14024) Sep 5 15:34:43 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Sep 5 15:34:43 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Sep 5 15:34:43 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Sep 5 15:34:43 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 3e c8 00 00 58 00 Sep 5 15:34:43 TheDeathStar kernel: blk_update_request: critical medium error, dev sda, sector 16072 op 0x0:(READ) flags 0x80700 phys_seg 88 prio class 0 Sep 5 15:34:43 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Sep 5 15:34:43 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Sep 5 15:34:43 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Sep 5 15:34:43 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 3e c9 00 00 57 00 Sep 5 15:34:43 TheDeathStar kernel: blk_update_request: critical medium error, dev sda, sector 16073 op 0x0:(READ) flags 0x80000 phys_seg 87 prio class 0 Sep 5 15:34:43 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Sep 5 15:34:43 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Sep 5 15:34:43 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Sep 5 15:34:43 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 3e c8 00 00 01 00 Sep 5 15:34:43 TheDeathStar kernel: blk_update_request: critical medium error, dev sda, sector 16072 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Sep 5 15:34:43 TheDeathStar emhttpd: error: get_fs_sizes, 6059: Input/output error (5): statfs: /boot Sep 5 15:34:43 TheDeathStar kernel: FAT-fs (sda1): FAT read failed (blocknr 14024) Sep 5 15:34:44 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Sep 5 15:34:44 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Sep 5 15:34:44 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Sep 5 15:34:44 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 3e c8 00 00 58 00 Sep 5 15:34:44 TheDeathStar kernel: blk_update_request: critical medium error, dev sda, sector 16072 op 0x0:(READ) flags 0x80700 phys_seg 88 prio class 0 Sep 5 15:34:44 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Sep 5 15:34:44 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Sep 5 15:34:44 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Sep 5 15:34:44 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 3e c8 00 00 01 00 Sep 5 15:34:44 TheDeathStar kernel: blk_update_request: critical medium error, dev sda, sector 16072 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Sep 5 15:34:44 TheDeathStar emhttpd: error: get_fs_sizes, 6059: Input/output error (5): statfs: /boot Sep 5 15:34:44 TheDeathStar kernel: FAT-fs (sda1): FAT read failed (blocknr 14024) Time for a new thumbdrive me thinks... I proceed with the CA/UA install anyway and tried preclear again. This time I don't get the repeating errors (shown in https://forums.unraid.net/topic/120567-unassigned-devices-preclear-a-utility-to-preclear-disks-before-adding-them-to-the-array/?do=findComment&comment=1165650, instead it has just been (seemingly) stuck on /usr/local/emhttp/plugins/unassigned.devices.preclear/scripts/preclear_disk.sh --notify 4 --frequen cy 4 --cycles 1 --no-prompt /dev/sdb I have not seen read speed >0 on this attempt. The syslog has recorded the following in that period: Sep 5 15:38:56 TheDeathStar kernel: usb 4-4.4: USB disconnect, device number 4 Sep 5 15:38:56 TheDeathStar kernel: usb 4-4.4: new full-speed USB device number 6 using xhci_hcd Sep 5 15:38:57 TheDeathStar kernel: cdc_acm 4-4.4:1.0: ttyACM0: USB ACM device Sep 5 15:39:00 TheDeathStar kernel: usb 4-4.4: USB disconnect, device number 6 Sep 5 15:39:00 TheDeathStar kernel: usb 4-4.4: new full-speed USB device number 7 using xhci_hcd Sep 5 15:39:00 TheDeathStar kernel: cdc_acm 4-4.4:1.0: ttyACM0: USB ACM device Sep 5 15:39:44 TheDeathStar ntpd[1621]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Sep 5 15:41:58 TheDeathStar emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin install https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg Sep 5 15:41:58 TheDeathStar root: plugin: running: anonymous Sep 5 15:41:58 TheDeathStar root: plugin: running: anonymous Sep 5 15:41:58 TheDeathStar root: plugin: skipping: /boot/config/plugins/community.applications/community.applications-2022.07.26-x86_64-1.txz already exists Sep 5 15:41:58 TheDeathStar root: plugin: running: /boot/config/plugins/community.applications/community.applications-2022.07.26-x86_64-1.txz Sep 5 15:41:58 TheDeathStar root: plugin: running: anonymous Sep 5 15:42:31 TheDeathStar emhttpd: cmd: /usr/local/emhttp/plugins/community.applications/scripts/pluginInstall.php install https://raw.githubusercontent.com/dlandon/unassigned.devices/master/unassigned.devices.plg Sep 5 15:42:31 TheDeathStar root: plugin: skipping: /boot/config/plugins/unassigned.devices/unassigned.devices-2022.09.02.tgz already exists Sep 5 15:42:31 TheDeathStar root: plugin: running: anonymous Sep 5 15:42:31 TheDeathStar root: plugin: creating: /tmp/start_unassigned_devices - from INLINE content Sep 5 15:42:31 TheDeathStar root: plugin: setting: /tmp/start_unassigned_devices - mode to 0770 Sep 5 15:42:31 TheDeathStar root: plugin: skipping: /boot/config/plugins/unassigned.devices/unassigned.devices.cfg already exists Sep 5 15:42:31 TheDeathStar root: plugin: skipping: /boot/config/plugins/unassigned.devices/samba_mount.cfg already exists Sep 5 15:42:31 TheDeathStar root: plugin: skipping: /boot/config/plugins/unassigned.devices/iso_mount.cfg already exists Sep 5 15:42:31 TheDeathStar root: plugin: creating: /tmp/unassigned.devices/smb-settings.conf - from INLINE content Sep 5 15:42:31 TheDeathStar root: plugin: creating: /tmp/unassigned.devices/config/smb-extra.conf - from INLINE content Sep 5 15:42:31 TheDeathStar root: plugin: creating: /tmp/unassigned.devices/add-smb-extra - from INLINE content Sep 5 15:42:31 TheDeathStar root: plugin: setting: /tmp/unassigned.devices/add-smb-extra - mode to 0770 Sep 5 15:42:31 TheDeathStar root: plugin: creating: /tmp/unassigned.devices/remove-smb-extra - from INLINE content Sep 5 15:42:31 TheDeathStar root: plugin: setting: /tmp/unassigned.devices/remove-smb-extra - mode to 0770 Sep 5 15:42:31 TheDeathStar root: plugin: running: anonymous Sep 5 15:42:59 TheDeathStar emhttpd: cmd: /usr/local/emhttp/plugins/community.applications/scripts/pluginInstall.php install https://raw.githubusercontent.com/dlandon/unassigned.devices/master/unassigned.devices.preclear.plg Sep 5 15:42:59 TheDeathStar root: plugin: running: anonymous Sep 5 15:42:59 TheDeathStar root: plugin: skipping: /boot/config/plugins/unassigned.devices.preclear/unassigned.devices.preclear-2022.09.02.tgz already exists Sep 5 15:42:59 TheDeathStar root: plugin: skipping: /boot/config/plugins/unassigned.devices.preclear/tmux-3.1b-x86_64-1.txz already exists Sep 5 15:42:59 TheDeathStar root: plugin: running: /boot/config/plugins/unassigned.devices.preclear/tmux-3.1b-x86_64-1.txz Sep 5 15:42:59 TheDeathStar root: plugin: skipping: /boot/config/plugins/unassigned.devices.preclear/utempter-1.2.0-x86_64-3.txz already exists Sep 5 15:42:59 TheDeathStar root: plugin: running: /boot/config/plugins/unassigned.devices.preclear/utempter-1.2.0-x86_64-3.txz Sep 5 15:42:59 TheDeathStar root: plugin: running: anonymous Sep 5 15:42:59 TheDeathStar root: plugin: running: anonymous Sep 5 15:43:22 TheDeathStar unassigned.devices: PHP Warning: file_get_contents(plugins/dynamix.s3.sleep/Sleep.php): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix/include/Translations.php on line 66 Sep 5 15:48:43 TheDeathStar unassigned.devices: PHP Warning: file_get_contents(plugins/dynamix.s3.sleep/Sleep.php): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix/include/Translations.php on line 66 Sep 5 15:48:58 TheDeathStar unassigned.devices: Refreshed Disks and Configuration.

Which log/diagnostic is that from? I've searched for "Elmo" and can't locate a file with it in, and the main syslog has no postings at 11:06:38. I've power-downed and reseated the cable to the new drive but get same result on preclear. Not knowing where that log entry pointed out is from, I can't see if it has had any impact there. I can see the difference between the other (old/working) 18tb (same make/model) in the array Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:7:0: [sdi] 35156656128 512-byte logical blocks: (18.0 TB/16.4 TiB) Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:7:0: [sdi] 4096-byte physical blocks Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:7:0: [sdi] Write Protect is off Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:7:0: [sdi] Mode Sense: 7f 00 10 08 Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:7:0: [sdi] Write cache: enabled, read cache: enabled, supports DPO and FUA Sep 5 14:00:01 TheDeathStar kernel: sdi: sdi1 Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:7:0: [sdi] Attached SCSI disk Sep 5 14:02:55 TheDeathStar emhttpd: TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH (sdi) 512 35156656128 Sep 5 14:02:55 TheDeathStar kernel: mdcmd (8): import 7 sdi 64 17578328012 0 TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH Sep 5 14:02:55 TheDeathStar kernel: md: import disk7: (sdi) TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH size: 17578328012 Sep 5 14:02:55 TheDeathStar emhttpd: read SMART /dev/sdi Sep 5 14:04:32 TheDeathStar emhttpd: TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH (sdi) 512 35156656128 Sep 5 14:04:32 TheDeathStar kernel: mdcmd (8): import 7 sdi 64 17578328012 0 TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH Sep 5 14:04:32 TheDeathStar kernel: md: import disk7: (sdi) TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH size: 17578328012 Sep 5 14:04:32 TheDeathStar emhttpd: read SMART /dev/sdi Sep 5 14:04:41 TheDeathStar emhttpd: TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH (sdi) 512 35156656128 Sep 5 14:04:41 TheDeathStar kernel: mdcmd (8): import 7 sdi 64 17578328012 0 TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH Sep 5 14:04:41 TheDeathStar kernel: md: import disk7: (sdi) TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH size: 17578328012 Sep 5 14:04:41 TheDeathStar emhttpd: read SMART /dev/sdi and the new one Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:0:0: [sdb] 35156656128 512-byte logical blocks: (18.0 TB/16.4 TiB) Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:0:0: [sdb] 4096-byte physical blocks Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:0:0: [sdb] Write Protect is off Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:0:0: [sdb] Mode Sense: 7f 00 10 08 Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:0:0: [sdb] Attached SCSI disk Sep 5 14:02:55 TheDeathStar emhttpd: TOSHIBA_MG09ACA18TE_Z180A014FJDH (sdb) 512 35156656128 Sep 5 14:02:55 TheDeathStar emhttpd: read SMART /dev/sdb Sep 5 14:04:32 TheDeathStar emhttpd: TOSHIBA_MG09ACA18TE_Z180A014FJDH (sdb) 512 35156656128 Sep 5 14:04:32 TheDeathStar emhttpd: read SMART /dev/sdb Sep 5 14:04:41 TheDeathStar emhttpd: TOSHIBA_MG09ACA18TE_Z180A014FJDH (sdb) 512 35156656128 Sep 5 14:04:41 TheDeathStar emhttpd: read SMART /dev/sdb (Thankyou for you help so far)

thedeathstar-diagnostics-20220904-2037.zip

Latest log files attached. I notice the diskinfo_log file is empty on this run. Previous runs had it contain Fri Sep 2 14:31:33 BST 2022: SMART parameters for drive [/dev/sdj] not found, probing... Fri Sep 2 14:31:33 BST 2022: Trying SMART parameter (-d auto) for disk [/dev/sdj]... Fri Sep 2 14:31:33 BST 2022: SMART parameter for disk [/dev/sdj] (-d auto) found. Fri Sep 2 15:05:58 BST 2022: SMART parameters for drive [/dev/sdj] not found, probing... Fri Sep 2 15:05:58 BST 2022: Trying SMART parameter (-d auto) for disk [/dev/sdj]... Fri Sep 2 15:05:58 BST 2022: SMART parameter for disk [/dev/sdj] (-d auto) found. Fri Sep 2 15:06:53 BST 2022: Stopping Disk Info Daemon THEDEATHSTAR-unassigned.devices.preclear-20220904-1503.zip

I don't see old the plugin in /boot/config/plugins-removed, but neither do I see it in /boot/config/plugins I have rebooted and started the preclear again. I still see it seemingly stuck in 'starting' state and again the log captures the same repeating error entries. Very occasionally hitting refresh I register some read activity suggesting it is at least trying to do something (the pre read I guess) in spite of what the logs show/don't show The other change I have made is to upgrade to Pro license. I can't see that would cause this issue but added the info 'just in case'.

I have added another drive and looked to perform the usual preclear process. I had previously observed that the trusty precelar plugin I have used on 8+ disk previously was depreciated I have removed it and added the UD preclear plugin in its place. However, I am running into issues resulting in the preclear seemingly doing nothing (no reported read/write activity in the gui). Looking at the logs for my latest attempt I initially see /usr/local/emhttp/plugins/unassigned.devices.preclear/scripts/preclear_disk.sh --cycles 1 --no-prompt /dev/sdj and shortly after nothing but repetitive lines of -bash: /bin/dircolors: Argument list too long -bash: /usr/bin/grep: Argument list too long -bash: /bin/hostname: Argument list too long As mentioned, the read/write rate in the unraid gui remains at zero throughout. I have tried several times with various options, but all result in the same output Sep 2 15:23:37 Preclear script invoked as: /usr/local/emhttp/plugins/unassigned.devices.preclear/scripts/preclear_disk.sh --notify 4 --frequency 4 --cycles 2 --no-prompt /dev/sdj Sep 2 15:33:32 Preclear stopped on device: Z180A014FJDH Sep 2 15:34:46 Preclear script invoked as: /usr/local/emhttp/plugins/unassigned.devices.preclear/scripts/preclear_disk.sh --notify 4 --frequency 4 --cycles 2 --skip-preread --skip-postread --no-prompt /dev/sdj Sep 2 15:52:31 Preclear stopped on device: Z180A014FJDH Sep 2 15:54:13 Preclear script invoked as: /usr/local/emhttp/plugins/unassigned.devices.preclear/scripts/preclear_disk.sh --cycles 1 --no-prompt /dev/sdj diskinfo looks fine Fri Sep 2 14:31:33 BST 2022: SMART parameters for drive [/dev/sdj] not found, probing... Fri Sep 2 14:31:33 BST 2022: Trying SMART parameter (-d auto) for disk [/dev/sdj]... Fri Sep 2 14:31:33 BST 2022: SMART parameter for disk [/dev/sdj] (-d auto) found. Fri Sep 2 15:05:58 BST 2022: SMART parameters for drive [/dev/sdj] not found, probing... Fri Sep 2 15:05:58 BST 2022: Trying SMART parameter (-d auto) for disk [/dev/sdj]... Fri Sep 2 15:05:58 BST 2022: SMART parameter for disk [/dev/sdj] (-d auto) found. Fri Sep 2 15:06:53 BST 2022: Stopping Disk Info Daemon Any advice of what to try/check from here in order to get the disk precleared?

I found my way here by seeing that error having just reinstalled the DirSyncPro container.

Upgraded without incident to 6.10.2. Started up Docker in Settings. Hangs 'mid process' and never get control of the web gui. syslog shows the same error reported php-fpm[25479]: [WARNING] [pool www] server reached max_children setting (50), consider raising it nginx: 2022/06/10 20:14:12 [error] 25731#25731: *9910 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.1.129, server: , request: "POST /update.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.115", referrer: "http://192.168.1.115/Settings/DockerSettings" ps aux | grep fpm root 3724 0.0 0.0 89308 17284 ? S 20:09 0:00 php-fpm: pool www root 3936 0.0 0.0 88984 13072 ? S 20:12 0:00 php-fpm: pool www root 3945 0.0 0.0 89384 19696 ? S 20:12 0:00 php-fpm: pool www root 4379 0.0 0.0 88984 13024 ? S 20:09 0:00 php-fpm: pool www root 4380 0.0 0.0 89536 18748 ? S 20:09 0:00 php-fpm: pool www root 4381 0.0 0.0 89272 17924 ? S 20:09 0:00 php-fpm: pool www root 4591 0.0 0.0 89616 19344 ? S 20:02 0:00 php-fpm: pool www root 5150 0.0 0.0 89680 18872 ? S 20:12 0:00 php-fpm: pool www root 6877 0.0 0.0 89420 14516 ? S 20:09 0:00 php-fpm: pool www root 6897 0.0 0.0 89604 18280 ? S 20:09 0:00 php-fpm: pool www root 8120 0.0 0.0 89380 15056 ? S 20:06 0:00 php-fpm: pool www root 8180 0.0 0.0 88764 12356 ? S 20:09 0:00 php-fpm: pool www root 8272 0.0 0.0 89384 19660 ? S 20:09 0:00 php-fpm: pool www root 8310 0.0 0.0 89580 18624 ? S 20:06 0:00 php-fpm: pool www root 9391 0.0 0.0 89416 18104 ? S 20:02 0:00 php-fpm: pool www root 9825 0.0 0.0 89276 18024 ? S 20:10 0:00 php-fpm: pool www root 10258 0.0 0.0 89436 18152 ? S 20:10 0:00 php-fpm: pool www root 10268 0.0 0.0 89224 13772 ? S 20:06 0:00 php-fpm: pool www root 10312 0.0 0.0 88984 13032 ? S 20:10 0:00 php-fpm: pool www root 10987 0.0 0.0 89608 18728 ? S 20:10 0:00 php-fpm: pool www root 10997 0.0 0.0 89600 20244 ? S 20:10 0:00 php-fpm: pool www root 11245 0.0 0.0 89332 17712 ? S 20:06 0:00 php-fpm: pool www root 12175 0.0 0.0 89176 13880 ? S 20:06 0:00 php-fpm: pool www root 12343 0.0 0.0 89308 17924 ? S 20:10 0:00 php-fpm: pool www root 12707 0.0 0.0 88764 12368 ? S 20:10 0:00 php-fpm: pool www root 12801 0.0 0.0 89292 14012 ? S 20:10 0:00 php-fpm: pool www root 13556 0.0 0.0 89308 17364 ? S 20:10 0:00 php-fpm: pool www root 13863 0.0 0.0 89272 17448 ? S 20:10 0:00 php-fpm: pool www root 14913 0.0 0.0 88960 13064 ? S 20:03 0:00 php-fpm: pool www root 16507 0.0 0.0 89536 17204 ? S 20:10 0:00 php-fpm: pool www root 17076 0.0 0.0 89224 13540 ? S 20:10 0:00 php-fpm: pool www root 17103 0.0 0.0 89500 18192 ? S 20:10 0:00 php-fpm: pool www root 18364 0.0 0.0 89308 17956 ? S 20:10 0:00 php-fpm: pool www root 18369 0.0 0.0 89640 18776 ? S 20:10 0:00 php-fpm: pool www root 19493 0.0 0.0 89368 15568 ? S 20:11 0:00 php-fpm: pool www root 19972 0.0 0.0 89336 17996 ? S 20:11 0:00 php-fpm: pool www root 19997 0.0 0.0 89436 18292 ? S 20:11 0:00 php-fpm: pool www root 21225 0.0 0.0 88764 12380 ? S 20:11 0:00 php-fpm: pool www root 21516 0.0 0.0 89536 18776 ? S 20:11 0:00 php-fpm: pool www root 22317 0.0 0.0 89636 19764 ? S 20:07 0:00 php-fpm: pool www root 22693 0.0 0.0 89368 15576 ? S 20:11 0:00 php-fpm: pool www root 23299 0.0 0.0 89488 18216 ? S 20:11 0:00 php-fpm: pool www root 24413 0.0 0.0 89608 19840 ? S 20:11 0:00 php-fpm: pool www root 24414 0.0 0.0 89308 17524 ? S 20:11 0:00 php-fpm: pool www root 25479 0.0 0.0 85724 11780 ? Ss 19:47 0:00 php-fpm: master process (/etc/php-fpm/php-fpm.conf) root 26268 0.0 0.0 88764 12388 ? S 20:11 0:00 php-fpm: pool www root 27996 0.0 0.0 88984 13064 ? S 20:11 0:00 php-fpm: pool www root 28790 0.0 0.0 89268 18048 ? S 20:11 0:00 php-fpm: pool www root 29001 0.0 0.0 89436 18216 ? S 20:05 0:00 php-fpm: pool www root 30545 0.0 0.0 3980 2216 pts/0 S+ 20:26 0:00 grep fpm root 31566 0.0 0.0 89416 14564 ? S 20:12 0:00 php-fpm: pool www root 31593 0.0 0.0 89444 15260 ? S 20:12 0:00 php-fpm: pool www I have edited /etc/php-fpm.d/www.conf and upped the limit to 75 and will watched what happens following /etc/rc.d/rc.php-fpm restart I had another browser open which had timed out, hit refresh and got a positive response back. I went back to the Docker settings page that was hanging and hit refresh, at which point both web gui sessions became unresponsive. No fresh errors in syslog (yet) and only a handful of php-fpm showing when running a ps I restarted the whole stack /etc/rc.d/rc.nginx restart /etc/rc.d/rc.nginx reload /etc/rc.d/rc.php-fpm restart /etc/rc.d/rc.php-fpm reload Web gui now dead nginx: 2022/06/10 20:43:03 [alert] 25731#25731: *30351 open socket #36 left in connection 8 nginx: 2022/06/10 20:43:03 [alert] 25731#25731: *30369 open socket #47 left in connection 11 nginx: 2022/06/10 20:43:03 [alert] 25731#25731: *117 open socket #23 left in connection 12 nginx: 2022/06/10 20:43:03 [alert] 25731#25731: *30432 open socket #38 left in connection 13 nginx: 2022/06/10 20:43:03 [alert] 25731#25731: *30347 open socket #22 left in connection 30 nginx: 2022/06/10 20:43:03 [alert] 25731#25731: *30341 open socket #35 left in connection 37 nginx: 2022/06/10 20:43:03 [alert] 25731#25731: aborting At this point I'm stuck (with a pre-clear running (or was running at least) Edit/Update the following morning the increased limit was (b)reached overnight, but at least (as i expected it owuld do, as not related to the gui) the disk pre-clear continues to work uninterrupted php-fpm[18361]: [WARNING] [pool www] server reached max_children setting (75), consider raising it preclear_disk_Z1C0A05MFJDH[28721]: Zeroing: progress - 60% zeroed @ 226 MB/s root: /mnt/cache_app: 564.4 GiB (606063992832 bytes) trimmed on /dev/nvme0n1p1 root: /mnt/cache: 7.5 GiB (8014397440 bytes) trimmed on /dev/sdj1 Plugin Auto Update: Checking for available plugin updates Plugin Auto Update: Checking for language updates Plugin Auto Update: Community Applications Plugin Auto Update finished preclear_disk_Z1C0A05MFJDH[28721]: Zeroing: progress - 70% zeroed @ 212 MB/s preclear_disk_Z1C0A05MFJDH[28721]: Zeroing: progress - 80% zeroed @ 172 MB/s The original action that (seemingly) started this, namely bringing Dicker online in Settings, allegedly worked # /etc/rc.d/rc.docker status status of dockerd: running However, none of the docker containers are actually running, and issuing a docker stop command results in no action and a Ctrl+C required to regain control. Googling around I came across which jogged my memory that I do run 2 network cards (albeit on the same subnet, unlike the case raised here). I tried connecting to the gui on the other IP, and bingo, complete control of the gui returned.... until I went onto Settings/Docker tab and immediately hung again

TL/DR: user choice rather than anything over/above MC. We use Ranger in the office so it's a natural extension for me to use it in my homelab. I think the original requestor (@Ziggurat) just had a personal preference for it.

I tried manually bumping ranger to version ranger-1.9.3-x86_64-4cf.txz and it works fine.