bobokun

set -g default-terminal "xterm-256color" Also works if you prefer to have color in your tmux terminal

Hi can I please request the tool fd to be added to nerdtools?

Thanks! Just ran preclear again with binhex docker preclear and it all passed okay. Weird how we couldn't figure out why it wasn't working with the preclear plugin. It used to work fine before 😅.

I just tried to preclear a different disk and it once again also failed and got a invalid MBR signature from Unraid. Can someone verify the latest version of preclear is working with unraid 6.11.5?

I tried connecting the drive directly to my server rather than using the external dock and ran a preclear but it still fails at the verifying Unraid's preclear signature step. I'm not sure if there's an issue with this drive or the preclear plugin.

So I ran memtest and after 8 passes I don't have any memory errors.. still not sure what the solution is.

I tried running preclear again on the disk and once again it failed. This is what I found in the disk log information, does it help? Jan 7 08:58:36 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 7 08:58:36 unNAS kernel: sd 10:0:0:0: [sdl] 27344764928 512-byte logical blocks: (14.0 TB/12.7 TiB) Jan 7 08:58:36 unNAS kernel: sd 10:0:0:0: [sdl] Write Protect is off Jan 7 08:58:36 unNAS kernel: sd 10:0:0:0: [sdl] Mode Sense: 03 00 00 00 Jan 7 08:58:36 unNAS kernel: sd 10:0:0:0: [sdl] No Caching mode page found Jan 7 08:58:36 unNAS kernel: sd 10:0:0:0: [sdl] Assuming drive cache: write through Jan 7 08:58:36 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 7 08:58:36 unNAS kernel: sd 10:0:0:0: [sdl] Attached SCSI disk Jan 7 08:58:39 unNAS emhttpd: WDC_WD14_0EFGX-68B0GN0_PROLIFICMP000000001-0:0 (sdl) 512 27344764928 Jan 7 08:59:55 unNAS emhttpd: spinning up /dev/sdl Jan 7 08:59:55 unNAS emhttpd: read SMART /dev/sdl Jan 7 12:59:56 unNAS emhttpd: spinning down /dev/sdl Jan 7 15:52:06 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 7 15:52:06 unNAS kernel: sd 10:0:0:0: [sdl] 27344764928 512-byte logical blocks: (14.0 TB/12.7 TiB) Jan 7 15:52:06 unNAS kernel: sd 10:0:0:0: [sdl] Write Protect is off Jan 7 15:52:06 unNAS kernel: sd 10:0:0:0: [sdl] Mode Sense: 03 00 00 00 Jan 7 15:52:06 unNAS kernel: sd 10:0:0:0: [sdl] No Caching mode page found Jan 7 15:52:06 unNAS kernel: sd 10:0:0:0: [sdl] Assuming drive cache: write through Jan 7 15:52:06 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 7 15:52:06 unNAS kernel: sd 10:0:0:0: [sdl] Attached SCSI disk Jan 7 15:55:12 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 7 15:55:57 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 7 15:55:57 unNAS kernel: sd 10:0:0:0: [sdl] 27344764928 512-byte logical blocks: (14.0 TB/12.7 TiB) Jan 7 15:55:57 unNAS kernel: sd 10:0:0:0: [sdl] Write Protect is off Jan 7 15:55:57 unNAS kernel: sd 10:0:0:0: [sdl] Mode Sense: 03 00 00 00 Jan 7 15:55:57 unNAS kernel: sd 10:0:0:0: [sdl] No Caching mode page found Jan 7 15:55:57 unNAS kernel: sd 10:0:0:0: [sdl] Assuming drive cache: write through Jan 7 15:55:57 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 7 15:55:57 unNAS kernel: sd 10:0:0:0: [sdl] Attached SCSI disk Jan 8 08:57:02 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 8 08:57:02 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 8 11:08:05 unNAS kernel: sd 10:0:0:0: [sdl] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Jan 8 11:08:05 unNAS kernel: sd 10:0:0:0: [sdl] tag#0 Sense Key : 0x5 [current] Jan 8 11:08:05 unNAS kernel: sd 10:0:0:0: [sdl] tag#0 ASC=0x20 ASCQ=0x0 Jan 8 11:08:05 unNAS kernel: sd 10:0:0:0: [sdl] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 c1 98 68 00 00 00 08 00 00 00 Jan 8 11:08:05 unNAS kernel: critical target error, dev sdl, sector 3247990784 op 0x1:(WRITE) flags 0x104000 phys_seg 256 prio class 0 Jan 8 11:08:05 unNAS kernel: Buffer I/O error on dev sdl, logical block 405998848, lost async page write Jan 8 11:08:05 unNAS kernel: Buffer I/O error on dev sdl, logical block 405998849, lost async page write Jan 8 11:08:05 unNAS kernel: Buffer I/O error on dev sdl, logical block 405998850, lost async page write Jan 8 11:08:05 unNAS kernel: Buffer I/O error on dev sdl, logical block 405998851, lost async page write Jan 8 11:08:05 unNAS kernel: Buffer I/O error on dev sdl, logical block 405998852, lost async page write Jan 8 11:08:05 unNAS kernel: Buffer I/O error on dev sdl, logical block 405998853, lost async page write Jan 8 11:08:05 unNAS kernel: Buffer I/O error on dev sdl, logical block 405998854, lost async page write Jan 8 11:08:05 unNAS kernel: Buffer I/O error on dev sdl, logical block 405998855, lost async page write Jan 8 11:08:05 unNAS kernel: Buffer I/O error on dev sdl, logical block 405998856, lost async page write Jan 8 11:08:05 unNAS kernel: Buffer I/O error on dev sdl, logical block 405998857, lost async page write Jan 9 08:33:06 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 9 08:34:05 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 9 08:34:06 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 9 08:34:06 unNAS kernel: sdl: sdl1 Jan 9 08:34:06 unNAS unassigned.devices: Partition 'sdl1' does not have a file system and cannot be mounted. Jan 9 08:34:07 unNAS emhttpd: read SMART /dev/sdl Jan 9 08:45:58 unNAS unassigned.devices: Removing all partitions from disk '/dev/sdl'. Jan 9 08:46:00 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 9 08:46:02 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 9 08:51:16 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 9 08:51:16 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 9 12:34:08 unNAS emhttpd: spinning down /dev/sdl Jan 10 08:27:16 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 10 08:28:16 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 10 08:28:17 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 10 08:28:17 unNAS kernel: sdl: sdl1 Jan 10 08:28:17 unNAS unassigned.devices: Partition 'sdl1' does not have a file system and cannot be mounted. Jan 10 10:16:49 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 10 10:16:49 unNAS kernel: sd 10:0:0:0: [sdl] 27344764928 512-byte logical blocks: (14.0 TB/12.7 TiB) Jan 10 10:16:49 unNAS kernel: sd 10:0:0:0: [sdl] Write Protect is off Jan 10 10:16:49 unNAS kernel: sd 10:0:0:0: [sdl] Mode Sense: 03 00 00 00 Jan 10 10:16:49 unNAS kernel: sd 10:0:0:0: [sdl] No Caching mode page found Jan 10 10:16:49 unNAS kernel: sd 10:0:0:0: [sdl] Assuming drive cache: write through Jan 10 10:16:49 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 10 10:16:49 unNAS kernel: sdl: sdl1 Jan 10 10:16:49 unNAS kernel: sd 10:0:0:0: [sdl] Attached SCSI disk Jan 10 10:16:51 unNAS unassigned.devices: Partition 'sdl1' does not have a file system and cannot be mounted. Jan 10 10:18:12 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 10 10:18:12 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 11 09:54:13 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 11 09:54:58 unNAS emhttpd: read SMART /dev/sdl Jan 11 09:55:12 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 11 09:55:13 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 11 09:55:13 unNAS kernel: sdl: sdl1 Jan 11 09:55:13 unNAS unassigned.devices: Partition 'sdl1' does not have a file system and cannot be mounted. ** Press ANY KEY to close this window **

I did memtest maybe 1 year ago when I upgrade my RAM. Ran it for 48hours without any issues. I'm using a external HDD docking station plugged into my server via USB to do the preclear. Do you think that might be the reason?

Yes I had post-read verification on but because it failed at the verifying Unraid's Signature stage it never got to the last stage.

I'm having some issues with preclearing a new drive that I purchased. Every time I try to preclear it always fails at the last step in verifying Unraid's signature. I'm running on the latest version of the plugin. Is my drive bad? Running on Unraid version 6.11.5 Unassigned Devices Preclear version 2023.01.08

for Visual Studio Code Server does it need to be ran in Privileged mode?

would we be able to get powershell added as well please?

Is there a way to skip the Userscript from triggering if the previous run is still running? Currently it seems like the userscript will trigger a new run at the scheduled time even if the previous one is not complete.

I don't mind helping out with beta testing and that's why I'm here to provide any diagnostic reports when those errors do come in. So far I've tried to produce a new VM using Seabios and mode 4 rather than ovmf mode 8. Both tests have had the kernel errors. Let me know if there is anything else I should be testing.

Created a fresh windows VM with Seabios and mode 4, still getting the kernel errors and forcing me to hard reset my server. unnas-diagnostics-20210525-0925.zip

I was using mode 8, should I try mode 4? I'll set up a seaBIOS test VM and see if it makes any difference.

Sure, please see attached for the diagnostics. I've tried opening a 1080p file and 4k file in a media player inside the VM and it seems to be utilizing the CPU more than the igPU. But I do see some video decode and video processing utilization, about 20-40%

I tried to use parsec and when I tried to play a 4k video on youtube, I get a connection error and can't seem to connect back to the VM through parsec/VNC/RDP. Seems like it crashes the VM. I coudln't even kill the process in htop. I couldn't access the VM page on Unraid and when I went to go into VM settings to turn off the VM using VM Manager and turn it back on I still see it stuck. I think I have to force shutdown my Unraid server. In the logs I see a bunch of kernel errors as well.

The Load on my CPU spikes to 100% when I am playing a 4k Youtube video and when I stop then the CPU utilization goes back down. Video decode is constant at 0% on the iGPU. I'm not sure where the 3D utilization is coming from but it doesn't seem to be related to the Youtube video since I see it fluctuate even when I'm not playing a video.

Thanks for writing this guide, I've followed the steps and I can see the iGPU in my windows VM. I've also enabled it to show the display 2 only and so nothing shows on my VNC but when I use RDP and try to play a youtube video to test I see it's still utilizing all my CPU and not the iGPU. I also notice a third display driver whenever I login to RDP.

Enjoy your vacation! I'm not sure where to look in the code so I'll wait for your response next week on the details. Thank you!

Would it be possible to choose which cache pool to look at for the Only move at this threshold of used cache space I currently have a cache pool called "cache" which I use to store my appdata and for my downloads I use a cache pool called "scratch" and want the mover to be invoked when the downloads cache gets close to 75% full.

I'm having this issue too. How did you end up stopping/killing nextcloud when it locks up? Is the only way to reboot the server? Did you have any additional issues since you made the change to redis?

Going to ditto the exact same points as you except I did not have to change CPU Temp. The issues I have the same as you as well

Thanks for creating such an amazing plugin. I currently have a threshold set. I currently have a user script that turns off my torrent/nextcloud dockers and runs mover using /usr/local/sbin/mover The problem is it's using the settings I set in mover tuner. How do I run mover via script without applying the tuner plug-in settings? I know the plugin allows you to force move at a certain time but I would ideally like to do this via script so I can stop and start the docker containers before/after moving. Thanks!