B_Sinn3d

FYI, extended smart passed. I will follow the below procedure to put it back into the array. https://docs.unraid.net/unraid-os/manual/storage-management/#rebuilding-a-drive-onto-itself WDC_WD120EDAZ-11F3RA0_5PK2AWJB-20240214-1032.txt

Thanks itimpi! I will power off, reseat the cable(s) and power back on. Here is the last SMART report for that disk from Feb 3rd. WDC_WD120EDAZ-11F3RA0_5PK2AWJB-2023-08-31 disk3 (sdb).txt

This morning I woke up and one of my disks (3) was disabled with Read/Write errors. It connected to LSI 9201 so I don't think it is cable since other drives that are on same SAS cable are OK. Should I replace it or is something else going on here? Posting Diags... Feb 13 01:04:28 debo-server kernel: sd 1:0:0:0: [sdk] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=29s Feb 13 01:04:28 debo-server kernel: sd 1:0:0:0: [sdk] tag#22 Sense Key : 0x5 [current] Feb 13 01:04:28 debo-server kernel: sd 1:0:0:0: [sdk] tag#22 ASC=0x21 ASCQ=0x4 Feb 13 01:04:28 debo-server kernel: sd 1:0:0:0: [sdk] tag#22 CDB: opcode=0x88 88 00 00 00 00 02 05 02 f4 f0 00 00 01 00 00 00 Feb 13 01:04:28 debo-server kernel: I/O error, dev sdk, sector 8674014448 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 2 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014384 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014392 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014400 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014408 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014416 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014424 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014432 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014440 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014448 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014456 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014464 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014472 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014480 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014488 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014496 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014504 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014512 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014520 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014528 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014536 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014544 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014552 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014560 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014568 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014576 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014584 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014592 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014600 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014608 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014616 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014624 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014632 Feb 13 01:04:28 debo-server kernel: ata1: EH complete Feb 13 01:04:28 debo-server kernel: sd 1:0:0:0: rejecting I/O to offline device Feb 13 01:04:28 debo-server kernel: ata1.00: detaching (SCSI 1:0:0:0) Feb 13 01:04:28 debo-server kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Feb 13 01:04:28 debo-server kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Feb 13 01:04:28 debo-server kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Feb 13 01:04:28 debo-server kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Feb 13 01:04:28 debo-server kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Feb 13 01:04:28 debo-server kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Feb 13 01:04:28 debo-server kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Feb 13 01:04:28 debo-server kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Feb 13 01:04:28 debo-server kernel: sd 1:0:0:0: [sdk] Synchronizing SCSI cache Feb 13 01:04:28 debo-server kernel: sd 1:0:0:0: [sdk] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK Feb 13 01:04:29 debo-server emhttpd: read SMART /dev/sde Feb 13 01:04:29 debo-server emhttpd: read SMART /dev/sdf Feb 13 01:04:29 debo-server emhttpd: read SMART /dev/sdl Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014384 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014392 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014400 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014408 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014416 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014424 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014432 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014440 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014448 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014456 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014464 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014472 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014480 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014488 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014496 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014504 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014512 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014520 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014528 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014536 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014544 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014552 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014560 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014568 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014576 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014584 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014592 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014600 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014608 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014616 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014624 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014632 debo-server-diagnostics-20240213-0928.zip

I usually see that when my disks are spun down and something is trying to access multiple disks all at once (plex...etc). it spikes CPU until disks are all spun up and it get the data it is looking for. I have a script that keeps them spun up during the day, then I let them spin down at night when nobody is using it. suggestion: set spin down delay to "never".

I am on the latest version 2023-11-09 but when I noticed it I was on 2023-10-29. Unraid is 6.12.4. cntrl + F5 didn't help but I just cleared browser data from all time and it appears to be working now and the message is no longer showing that the GPU is not available. I appreciate you taking the time on this.

My dashboard widget no longer stays expanded. I have get it to expand by minimizing then expanding but quickly closes. I was able to get a screenshot and it says "GPU not available bound to VFIO or inuse in a VM." I am not passing it through and not being used by VM. Could this be because I have unraid said to launch in GUI mode? It has been running in GUI mode for a while not but only recently noticed that the widget no longer shows correctly. It is still being used by Plex correctly when its needed.

Jorge, I am going to be adding another ssd to my single device zfs pool. Is this the process we should be following or did OP do something wrong when he added the mirror? Edit: Should I follow the procedure for adding with BTRFS? To add disks to the BTRFS pool perform the following steps: Stop the array. Navigate to the Main tab. Scroll down to the section labeled Pool Devices. Change the number of Slots to be at least as many as the number of devices you wish to assign. Assign the devices you wish to the pool slot(s). Start the array. Click the checkbox and then the button under Array Operations to format the devices. Make sure that the devices shown are those you expect - you do not want to accidentally format a device that contains data you want to keep.

I am seeing this as well. I was planning on converting my current XFS disks to ZFS to take advantage of some of the ZFS features but I think I will wait until this gets sorted. I don't want to move around 70TB of data between my disks using unBalance with write speeds of ~55MB/s.

Just curious, how did you determine RAM was overheating? I get them on my backup server (r720xd) every once and a while.

Great work guys. looks like lots of good improvements. Gonna love the customizable dashboard. I will have to read up on advantages of ZFS but can anyone point out some use cases that would make it more valuable to the normal unraid user that just has the disks formated in xfs/btrfs with single/dual parity? Is read/write performance better with ZFS?

Thanks Jester for finding the specific version. I switched to this version and upgrade back to 6.11 series. So far so good....

I reverted back to 6.10.3 a week ago and has been stable.

I updated to recycle.bin-2022.10.25a.tgz and my issue is fixed. I appreciate your assistance. This plug-in has saved me a bunch of times

I here is the original diagnostics that I also included in the plugin support forum. if you need updated diags...let me know. debo-server-diagnostics-20221025-1100.zip

No, only thing that stopped the messages was stopping the recycle.bin plugin.

I did. I also just rebooted the server and when it came back up the smbd_audit was in the logs so I stopped it again.

I reinstalled the plugin and ran the commands. cat /etc/rsyslog.d/03-recycle-bin.conf :msg,contains,"smbd_audit" stop I am still seeing the smbd_audit spamming the logs. stopped plugin again.

My plugin was just updated to recycle.bin-2022.10.21.tgz and this morning I noticed my log was full of below messages. I stopped the plugin for now. attaching diagnostics Oct 25 10:49:06 Debo-Server smbd_audit[21059]: close fd 70 Oct 25 10:49:06 Debo-Server smbd_audit[21059]: close fd 69 Oct 25 10:49:06 Debo-Server smbd_audit[21059]: close fd 68 Oct 25 10:49:06 Debo-Server smbd_audit[21059]: close fd 67 Oct 25 10:49:06 Debo-Server smbd_audit[21059]: close fd 66 Oct 25 10:49:06 Debo-Server smbd_audit[21059]: close fd 65 Oct 25 10:49:06 Debo-Server smbd_audit[21059]: close fd 64 Oct 25 10:49:06 Debo-Server smbd_audit[21059]: close fd 63 Oct 25 10:49:06 Debo-Server smbd_audit[21059]: close fd 62 Oct 25 10:49:06 Debo-Server smbd_audit[21059]: close fd 61 Oct 25 10:49:06 Debo-Server smbd_audit[21059]: close fd 60 Here are the relevant lines from the syslog from Auto Update recycling.bin.plg Oct 25 00:00:01 Debo-Server Plugin Auto Update: Checking for available plugin updates Oct 25 00:00:01 Debo-Server Recycle Bin: Scheduled: Files older than 3 days have been removed Oct 25 00:00:04 Debo-Server Plugin Auto Update: Auto Updating recycle.bin.plg Oct 25 00:00:04 Debo-Server root: plugin: creating: /boot/config/plugins/recycle.bin/recycle.bin-2022.10.21.tgz - downloading from URL https://raw.githubusercontent.com/dlandon/recycle.bin/master/recycle.bin-2022.10.21.tgz Oct 25 00:00:04 Debo-Server root: plugin: checking: /boot/config/plugins/recycle.bin/recycle.bin-2022.10.21.tgz - MD5 Oct 25 00:00:04 Debo-Server root: plugin: skipping: /tmp/recycle.bin/wait_recycle.bin already exists Oct 25 00:00:04 Debo-Server root: plugin: setting: /tmp/recycle.bin/wait_recycle.bin - mode to 0770 Oct 25 00:00:04 Debo-Server root: plugin: skipping: /tmp/recycle.bin/remove-smb-extra already exists Oct 25 00:00:04 Debo-Server root: plugin: setting: /tmp/recycle.bin/remove-smb-extra - mode to 0770 Oct 25 00:00:04 Debo-Server root: plugin: running: anonymous Oct 25 00:00:04 Debo-Server Recycle Bin: Stopping Recycle Bin Oct 25 00:00:05 Debo-Server root: plugin: running: anonymous Oct 25 00:00:05 Debo-Server root: plugin: skipping: /boot/config/plugins/recycle.bin/recycle.bin.cfg already exists Oct 25 00:00:05 Debo-Server root: plugin: running: anonymous ### [PREVIOUS LINE REPEATED 1 TIMES] ### Oct 25 00:00:05 Debo-Server Recycle Bin: Starting Recycle Bin Oct 25 00:00:07 Debo-Server Plugin Auto Update: Checking for language updates Oct 25 00:00:07 Debo-Server Plugin Auto Update: Community Applications Plugin Auto Update finished Oct 25 00:00:07 Debo-Server rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="9643" x-info="https://www.rsyslog.com"] start Oct 25 00:00:08 Debo-Server smbd[9774]: [2022/10/25 00:00:08.068540, 0] ../../source3/smbd/server.c:1734(main) Oct 25 00:00:08 Debo-Server smbd[9774]: smbd version 4.15.7 started. Oct 25 00:00:08 Debo-Server smbd[9774]: Copyright Andrew Tridgell and the Samba Team 1992-2021 Oct 25 00:00:08 Debo-Server nmbd[9782]: [2022/10/25 00:00:08.086239, 0] ../../source3/nmbd/nmbd.c:901(main) Oct 25 00:00:08 Debo-Server nmbd[9782]: nmbd version 4.15.7 started. Oct 25 00:00:08 Debo-Server nmbd[9782]: Copyright Andrew Tridgell and the Samba Team 1992-2021 Oct 25 00:00:08 Debo-Server wsdd2[9798]: starting. Oct 25 00:00:08 Debo-Server winbindd[9799]: [2022/10/25 00:00:08.164908, 0] ../../source3/winbindd/winbindd.c:1722(main) Oct 25 00:00:08 Debo-Server winbindd[9799]: winbindd version 4.15.7 started. Oct 25 00:00:08 Debo-Server winbindd[9799]: Copyright Andrew Tridgell and the Samba Team 1992-2021 Oct 25 00:00:08 Debo-Server winbindd[9801]: [2022/10/25 00:00:08.168073, 0] ../../source3/winbindd/winbindd_cache.c:3085(initialize_winbindd_cache) Oct 25 00:00:08 Debo-Server winbindd[9801]: initialize_winbindd_cache: clearing cache and re-creating with version number 2 Oct 25 00:00:08 Debo-Server smbd_audit[9923]: connect to service Pictures by user debo Oct 25 00:00:08 Debo-Server smbd_audit[9923]: openat ./. (fd 43) Oct 25 00:00:08 Debo-Server smbd_audit[9923]: openat ./. (fd 44) Oct 25 00:00:08 Debo-Server smbd_audit[9923]: close fd 44 Oct 25 00:00:08 Debo-Server smbd_audit[9923]: openat ./. (fd 44) Oct 25 00:00:08 Debo-Server smbd_audit[9923]: openat ./. (fd 45) debo-server-diagnostics-20221025-1100.zip

I just noticed my log was 100% full as well with these errors. I tracked it down to RecycleBin plugin which was just updated last night at 12am for me and started spamming the logs. The version which it was updated to was recycle.bin-2022.10.21.tgz for reference. I stopped the plugin and will follow up on that support post.

Well...I got to a little over 4 days of uptime before it crashed again. I confirmed what @JesterEE noted I was able to stop all dockers and get the WebUI back so there appears to be something with docker and not just UD plugins. I just reverted back to 6.10.3 as I need this system to be stable. I wish my dev environment was also having these issues as I have no problem to keep troubleshooting there. I will keep an eye on this thread to see if this gets resolved. Attaching diagnostics. debo-server-diagnostics-20221022-1601.zip

I have been crash free for 36 hours now after uninstalling Unassigned Devices plugins. I wasn't able to go 24 hours in uptime since I installed 6.11.1. I will report back if I see another crash.

Crashed again last night. I bit the bullet and reconfigured everything that was using UD and uninstalled UD/UD+ plugins. We'll see....

I had another crash today. Previous troubleshooting steps: Changed Docker to ipvlan Uninstalled dynamix.active.streams Uninstalled file.activity Set DelugeVPN to pre-allocate Steps taken since the crash. Uninstalled CA Backup / Restore (ca.backup2) Lets see how long I can run it now without crashing. if it crashes again, I may just revert back to 6.10.x since I don't think there is anything else I haven't tried mentioned in this thread besides uninstalling UD which is not an option with my setup. Attaching additional diagnostics from today. debo-server-diagnostics-20221017-1336.zip

Ok, I removed both plugins below and updating Binhex-DelugeVPN to pre-allocate. I don't want to delete CA Backup as that is more useful/needed. If I still lockup, I will try that. dynamix.active.streams.plg - 2020.06.17 (Up to date) file.activity.plg - 2022.08.19 (Up to date)

I switched to ipvlan and GUI crashed again on me today. attaching additional diagnostics. debo-server-diagnostics-20221015-1958.zip