Zeroeth

Updated 2 of my servers from 6.12.3 to 6.12.4 with no issues. 😀

@JorgeB Thankyou! It was the same in safe mode. The issue was that I had not started the array since I was running preclear on my disks, and the disk log information on the flash is only available once the array is started. I confirmed this on my test server which has a SanDisk Cruzer Blade 32gb.

Reaching out once again for this. I have already activated the plus license but would like know why the disk log information link is greyed out.

Can anyone please advise on this? I just need to make sure that the flash disk is good to go and the greyed out Disk Log Information link is not an issue. Thanks!

Hi! I have a new server build where I'm using a Delkin 4GB (U404TQJGR-SN000-D) USB Flash drive. The Server boots up just fine but I'm unable to see the Disk Log Information like my other servers. The Disk Log Information link is greyed out on my Flash device under the Boot Device (Main Page). What might be the reason for this? Any insights would be very helpful as I would like to go ahead get the Plus License on this USB but just wanted to make sure that this isn't an issue. Thanks in advance! asgard-diagnostics-20230806-1259.zip

Have to you tried to Erase and then Apply? Reference: SpaceInvader's video How to Reformat (ZFS) and or Upgrade a Cache Pool in Unraid

Noted with thanks. Very much appreciate the advice!

This is the extended SMART test. azraj-smart-20230709-2132.zip

Hi! Can someone please advise on the below disk read error on disk 1 that has occurred before 2 days. It has not repeated after this yet. The SMART info on the dashboard shows up as healthy (screenshot attached below). I've also attached the current diagnostics here along with the syslog. Jun 29 00:11:21 Azraj kernel: ata6: SATA max UDMA/133 abar m2048@0xc7132000 port 0xc7132180 irq 42 Jun 29 00:11:21 Azraj kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jun 29 00:11:21 Azraj kernel: ata6.00: ATA-10: TOSHIBA MG08ACA16TE, 0102, max UDMA/133 Jun 29 00:11:21 Azraj kernel: ata6.00: 31251759104 sectors, multi 16: LBA48 NCQ (depth 32), AA Jun 29 00:11:21 Azraj kernel: ata6.00: Features: NCQ-prio Jun 29 00:11:21 Azraj kernel: ata6.00: configured for UDMA/133 Jun 29 00:11:21 Azraj kernel: sd 6:0:0:0: [sdc] 31251759104 512-byte logical blocks: (16.0 TB/14.6 TiB) Jun 29 00:11:21 Azraj kernel: sd 6:0:0:0: [sdc] 4096-byte physical blocks Jun 29 00:11:21 Azraj kernel: sd 6:0:0:0: [sdc] Write Protect is off Jun 29 00:11:21 Azraj kernel: sd 6:0:0:0: [sdc] Mode Sense: 00 3a 00 00 Jun 29 00:11:21 Azraj kernel: sd 6:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jun 29 00:11:21 Azraj kernel: sd 6:0:0:0: [sdc] Preferred minimum I/O size 4096 bytes Jun 29 00:11:21 Azraj kernel: sdc: sdc1 Jun 29 00:11:21 Azraj kernel: sd 6:0:0:0: [sdc] Attached SCSI disk Jun 29 00:12:04 Azraj emhttpd: TOSHIBA_MG08ACA16TE_51M0A23NFVGG (sdc) 512 31251759104 Jun 29 00:12:04 Azraj kernel: mdcmd (2): import 1 sdc 64 15625879500 0 TOSHIBA_MG08ACA16TE_51M0A23NFVGG Jun 29 00:12:04 Azraj kernel: md: import disk1: (sdc) TOSHIBA_MG08ACA16TE_51M0A23NFVGG size: 15625879500 Jun 29 00:12:04 Azraj emhttpd: read SMART /dev/sdc Jul 2 04:00:14 Azraj kernel: ata6.00: exception Emask 0x0 SAct 0x3e00 SErr 0x0 action 0x0 Jul 2 04:00:14 Azraj kernel: ata6.00: irq_stat 0x40000001 Jul 2 04:00:14 Azraj kernel: ata6.00: failed command: READ FPDMA QUEUED Jul 2 04:00:14 Azraj kernel: ata6.00: cmd 60/20:48:f8:92:03/00:00:80:00:00/40 tag 9 ncq dma 16384 in Jul 2 04:00:14 Azraj kernel: ata6.00: status: { DRDY SENSE ERR } Jul 2 04:00:14 Azraj kernel: ata6.00: error: { UNC } Jul 2 04:00:14 Azraj kernel: ata6.00: failed command: READ FPDMA QUEUED Jul 2 04:00:14 Azraj kernel: ata6.00: cmd 60/20:50:f0:4e:18/00:00:80:00:00/40 tag 10 ncq dma 16384 in Jul 2 04:00:14 Azraj kernel: ata6.00: status: { DRDY SENSE ERR } Jul 2 04:00:14 Azraj kernel: ata6.00: error: { UNC } Jul 2 04:00:14 Azraj kernel: ata6.00: failed command: READ FPDMA QUEUED Jul 2 04:00:14 Azraj kernel: ata6.00: cmd 60/80:58:d8:6d:cd/00:00:06:01:00/40 tag 11 ncq dma 65536 in Jul 2 04:00:14 Azraj kernel: ata6.00: status: { DRDY SENSE ERR } Jul 2 04:00:14 Azraj kernel: ata6.00: error: { UNC } Jul 2 04:00:14 Azraj kernel: ata6.00: failed command: READ FPDMA QUEUED Jul 2 04:00:14 Azraj kernel: ata6.00: cmd 60/80:60:d8:6c:cd/00:00:06:01:00/40 tag 12 ncq dma 65536 in Jul 2 04:00:14 Azraj kernel: ata6.00: status: { DRDY SENSE ERR } Jul 2 04:00:14 Azraj kernel: ata6.00: error: { UNC } Jul 2 04:00:14 Azraj kernel: ata6.00: failed command: READ FPDMA QUEUED Jul 2 04:00:14 Azraj kernel: ata6.00: cmd 60/80:68:58:6e:cd/00:00:06:01:00/40 tag 13 ncq dma 65536 in Jul 2 04:00:14 Azraj kernel: ata6.00: status: { DRDY SENSE ERR } Jul 2 04:00:14 Azraj kernel: ata6.00: error: { UNC } Jul 2 04:00:15 Azraj kernel: ata6.00: configured for UDMA/133 Jul 2 04:00:15 Azraj kernel: sd 6:0:0:0: [sdc] tag#9 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Jul 2 04:00:15 Azraj kernel: sd 6:0:0:0: [sdc] tag#9 Sense Key : 0x3 [current] Jul 2 04:00:15 Azraj kernel: sd 6:0:0:0: [sdc] tag#9 ASC=0x11 ASCQ=0x4 Jul 2 04:00:15 Azraj kernel: sd 6:0:0:0: [sdc] tag#9 CDB: opcode=0x88 88 00 00 00 00 00 80 03 92 f8 00 00 00 20 00 00 Jul 2 04:00:15 Azraj kernel: I/O error, dev sdc, sector 2147717896 op 0x0:(READ) flags 0x0 phys_seg 2 prio class 0 Jul 2 04:00:15 Azraj kernel: sd 6:0:0:0: [sdc] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Jul 2 04:00:15 Azraj kernel: sd 6:0:0:0: [sdc] tag#10 Sense Key : 0x3 [current] Jul 2 04:00:15 Azraj kernel: sd 6:0:0:0: [sdc] tag#10 ASC=0x11 ASCQ=0x4 Jul 2 04:00:15 Azraj kernel: sd 6:0:0:0: [sdc] tag#10 CDB: opcode=0x88 88 00 00 00 00 00 80 18 4e f0 00 00 00 20 00 00 Jul 2 04:00:15 Azraj kernel: I/O error, dev sdc, sector 2149076720 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 0 Jul 2 04:00:15 Azraj kernel: sd 6:0:0:0: [sdc] tag#11 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=2s Jul 2 04:00:15 Azraj kernel: sd 6:0:0:0: [sdc] tag#11 Sense Key : 0x3 [current] Jul 2 04:00:15 Azraj kernel: sd 6:0:0:0: [sdc] tag#11 ASC=0x11 ASCQ=0x4 Jul 2 04:00:15 Azraj kernel: sd 6:0:0:0: [sdc] tag#11 CDB: opcode=0x88 88 00 00 00 00 01 06 cd 6d d8 00 00 00 80 00 00 Jul 2 04:00:15 Azraj kernel: I/O error, dev sdc, sector 4409093592 op 0x0:(READ) flags 0x0 phys_seg 16 prio class 0 Jul 2 04:00:15 Azraj kernel: sd 6:0:0:0: [sdc] tag#12 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=2s Jul 2 04:00:15 Azraj kernel: sd 6:0:0:0: [sdc] tag#12 Sense Key : 0x3 [current] Jul 2 04:00:15 Azraj kernel: sd 6:0:0:0: [sdc] tag#12 ASC=0x11 ASCQ=0x4 Jul 2 04:00:15 Azraj kernel: sd 6:0:0:0: [sdc] tag#12 CDB: opcode=0x88 88 00 00 00 00 01 06 cd 6c d8 00 00 00 80 00 00 Jul 2 04:00:15 Azraj kernel: I/O error, dev sdc, sector 4409093336 op 0x0:(READ) flags 0x0 phys_seg 16 prio class 0 Jul 2 04:00:15 Azraj kernel: sd 6:0:0:0: [sdc] tag#13 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=2s Jul 2 04:00:15 Azraj kernel: sd 6:0:0:0: [sdc] tag#13 Sense Key : 0x3 [current] Jul 2 04:00:15 Azraj kernel: sd 6:0:0:0: [sdc] tag#13 ASC=0x11 ASCQ=0x4 Jul 2 04:00:15 Azraj kernel: sd 6:0:0:0: [sdc] tag#13 CDB: opcode=0x88 88 00 00 00 00 01 06 cd 6e 58 00 00 00 80 00 00 Jul 2 04:00:15 Azraj kernel: I/O error, dev sdc, sector 4409093720 op 0x0:(READ) flags 0x0 phys_seg 16 prio class 0 Jul 2 04:00:15 Azraj kernel: ata6: EH complete Will appreciate any help/insight on this issue. Thanks! azraj-diagnostics-20230704-0953.zip syslog.log

Upgraded one of my Servers to 6.12 smoothly, no issues. Will be updating the rest soon. Thankyou for the awesome work!

This seems to have been taken care of in 1.5.2.

Thanks @JorgeB. I will check this... but I doubt there are any onboard SATA connectors on this Dell T620 mobo.

Hi! I've been getting this error & warning when the SSD TRIM runs (scheduled daily) on one of my Unraid servers running 6.11.5. Pool consists of 2 Samsung SSD 870 EVO 2TB disks. May 12 11:01:48 Zeroeth kernel: critical target error, dev sdi, sector 3902943146 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0 May 12 11:01:48 Zeroeth kernel: BTRFS warning (device sdi1): failed to trim 1 device(s), last error -121 May 13 11:01:51 Zeroeth kernel: sd 9:0:5:0: [sdi] tag#3030 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s May 13 11:01:51 Zeroeth kernel: sd 9:0:5:0: [sdi] tag#3030 Sense Key : 0x5 [current] May 13 11:01:51 Zeroeth kernel: sd 9:0:5:0: [sdi] tag#3030 ASC=0x21 ASCQ=0x0 May 13 11:01:51 Zeroeth kernel: sd 9:0:5:0: [sdi] tag#3030 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00 Have tried running scrub with the repair option but I continue to get this error. May 13 11:01:51 Zeroeth kernel: critical target error, dev sdi, sector 3902943146 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0 May 13 11:01:51 Zeroeth kernel: BTRFS warning (device sdi1): failed to trim 1 device(s), last error -121 May 13 20:24:55 Zeroeth kernel: BTRFS info (device sdi1): scrub: started on devid 1 May 13 20:24:55 Zeroeth kernel: BTRFS info (device sdi1): scrub: started on devid 2 May 13 20:47:23 Zeroeth kernel: BTRFS info (device sdi1): scrub: finished on devid 2 with status: 0 May 13 20:47:23 Zeroeth kernel: BTRFS info (device sdi1): scrub: finished on devid 1 with status: 0 May 13 20:52:28 Zeroeth kernel: BTRFS info (device sdi1): scrub: started on devid 1 May 13 20:52:28 Zeroeth kernel: BTRFS info (device sdi1): scrub: started on devid 2 May 13 21:14:50 Zeroeth kernel: BTRFS info (device sdi1): scrub: finished on devid 1 with status: 0 May 13 21:14:50 Zeroeth kernel: BTRFS info (device sdi1): scrub: finished on devid 2 with status: 0 May 14 11:01:50 Zeroeth kernel: sd 9:0:5:0: [sdi] tag#208 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s May 14 11:01:50 Zeroeth kernel: sd 9:0:5:0: [sdi] tag#208 Sense Key : 0x5 [current] May 14 11:01:50 Zeroeth kernel: sd 9:0:5:0: [sdi] tag#208 ASC=0x21 ASCQ=0x0 May 14 11:01:50 Zeroeth kernel: sd 9:0:5:0: [sdi] tag#208 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00 May 14 11:01:50 Zeroeth kernel: critical target error, dev sdi, sector 3902943146 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0 May 14 11:01:50 Zeroeth kernel: BTRFS warning (device sdi1): failed to trim 1 device(s), last error -121 Any insights would be really helpful. Need to know if there is an issue with the SSD drive maybe? Nothing is reported on the SMART info. Diagnostics attached. zeroeth-diagnostics-20230514-1214.zip

This is on the Chrome Authenticator extention.

@N47H4N I've had something similar happen and if you're using Google Authenticator for the totp then try going into Settings > Time Correction for codes > Sync now then try again. For any other totp app you should find something similar as well.

You could try resilio-sync. I've been using both luckybackup (local backups) and resilio-sync (offsite backups) for a while now and both work very well.

😀 It works pretty well and this docker + your support/updates have been amazing!

Noted, thanks. I don't see any noticable problems as such right now except the frequency of the Log messages. One of my instances has over 50 active users and sometimes the Log has too many of these messages.

@Taddeusz Hi! I have been getting these guacd segfaults in my Unraid Logs across my servers where I have this docker installed. It's the same on different Servers (different h/w and config). Apr 15 02:02:09 R620 kernel: guacd[1284]: segfault at 10 ip 0000152bbe5d5d3d sp 0000152bbd951270 error 4 in libguac-client-rdp.so.0.0.0[152bbe5b6000+2b000] Apr 15 02:02:09 R620 kernel: Code: b8 00 00 00 00 c9 c3 55 48 89 e5 48 83 ec 20 48 89 7d e8 48 8b 45 e8 48 8b 00 48 8b 40 10 48 89 45 f0 48 8b 45 f0 48 8b 40 20 <48> 8b 40 10 48 8b 55 e8 48 89 d6 48 89 c7 e8 c0 04 fe ff 48 8b 45 I just realized that these segfaults happen everytime I logoff or disconnect the windows remote session (through windows). Doesn't happen if I disconnect, logoff or close the browser window directly. Is this normal? Please advise.

@Taddeusz Thankyou!! Just updated to jasonbean/guacamole:1.5.1-RC1... ...and the the RDP printing is working flawlessly again

@Taddeusz This is great news! Thank you very much for the update. I'm looking forward to the 1.5.1 release/update. 😀 Really appreciate your support and effort.

Use a 2.5 SSD SATA to 3.5 Hard Drive Adapter. I'm using the one below: https://www.amazon.com/ORICO-Adapter-Mounting-Bracket-Interface/dp/B01LZWX6PD

UPDATE: I didn't end up recreating the Flash drive as I wanted to restart the Server first and check. I finally restarted the Server yesterday evening (after 75 days total) and everything is working well. Can't see any issues with the flash drive. If this happens again then I will go ahead and recreate the flash and then check again. Thanks for the support!

Thankyou @Taddeusz! I have this running on one of my instances for testing and yes the printer that is mapped goes offline on the remote windows VM. For my other instances, I was able to restore the previous version 1.4.0-3 from my backups since downgrading was causing an issue with mariaDB from starting.