Pducharme

Cool! thanks for the great work.

@Dmitry Spikhalskiy any particuliar reason that your docker run an old version of ZerioTier One ? Thanks.

I bought a cable and tried, but no disk were detected. Maybe I had the wrong cable... they advertise it, so it should work ! Since a hasn't more time to test, I did not tried buying a different cable....

Really? So simple that I haven't tried it I'll do when my PLEXers friends wont be playing stuff

already tried that, no changes.

Hi, since I upgraded my hardware to Ryzen 9 3900x on a X570 board, I used the same USB Key I had on my Xeon E3 board and it work well, except the networking part. I did try a new USB (as trial) and "Bridge" works normally, so It's probably a configuration. How can I reset the networking as "default" and have my Docker working as expected with "bridge" mode working ? For now, the dockers that needed the Bridge, I used the custom:br0 and put a dedicated IP to each docker. It works, but I would prefer regular "bridge" mode. Here is the error I always get if I try putting "bridge" on ANY docker : root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='AdGuardHome' --net='bridge' --log-opt max-size='50m' --log-opt max-file='1' -e TZ="America/New_York" -e HOST_OS="Unraid" -p '3000:3000/tcp' -p '53:53/tcp' -v '/mnt/user/appdata/adguard_home/workingdir':'/opt/adguardhome/work':'rw' -v '/mnt/user/appdata/adguard_home/config':'/opt/adguardhome/conf':'rw' 'siwatinc/adguard_home' 302ea3bb1fd264420144451de46a5df3aa835678ea5a0670813b0580f2e7bfeb /usr/bin/docker: Error response from daemon: driver failed programming external connectivity on endpoint AdGuardHome (ca41ceb227092fb168ab504ad0eab8e1429c0d0e7fba737ddcad106ff68e33c9): Error starting userland proxy: listen tcp 192.168.2.6:3000: bind: cannot assign requested address. The command failed. From the error, it seems to think that my Unraid IP is 192.168.2.6, which is what the OLD motherboard had for IP Address. I changed it in my router to a new IP (192.168.2.211). How can I have it reflect this IP ?

Not familiar with the LTS kernel, what is it ? All I want really, is a NVIDIA driver + at least 5.2.7 for having Temperature Plugin working on my X570 board

Thanks for Unraid! i gladly paid a Pro licence, and had 3 or 4 of my good friends also do the same i still continue to advertise Unraid as one of the best Home Media Storage system. I think you should have a more "business" version, for company that want to manage VMs and Storage, etc. Also, please udate the Kernel to 5.2.7 to support newer Ryzen 3000 temp sensors, etc. ( )

Interesting! Might start playing with Emby to see if it got any better since last time I tried it. I think I have a Lifetime on Emby too.

Not yet in the docker thought (i mean the official Plex Inc, docker). Maybe LinuxServer's PLEX docker can have a way to install the Forum Preview (aka ALPHA release) ?

Are you saying that we can use the Nvidia card on 2 different Docker at the same time? (i.e.: PLEX & Emby) (assuming more than 2 transcode card)

@Leoyzen Would you be able to create a version with the Unraid NVIDIA too ? so it can be use with both the sensors and the Nvidia Transcoding.

Just sad that Linux-Server.io doesn't incorporate this to the Unraid-NVIDIA plugins they create, that would make it so much easier. I don't want to compile anything, and don't want to lose my Hardware Transcoding that is possible with the Unraid-NVIDIA build, so i'm stuck until LimeTech upgrade the Kernel on the regular Unraid I suppose.

It is a brand new Corsair MP600 Pcie gen4 nvme drive. Is there a way to disable something to stop getting those errors?

Unfortunately I don’t know how. Is that works on the UnRAID NVIDIA build of unraid?

I'm a little concerned about my brand new Cache drive, it gives those errors in the Logs. I don't know if it is harmful or not... Aug 3 07:06:22 Unraid kernel: nvme0n1: p1 Aug 3 07:06:22 Unraid kernel: BTRFS: device fsid 8f95981b-c7e0-49dd-80d1-b16b238077aa devid 1 transid 273147 /dev/nvme0n1p1 Aug 3 07:07:58 Unraid emhttpd: Force_MP600_19258229000128553340 (nvme0n1) 512 1953525168 Aug 3 07:07:58 Unraid emhttpd: import 30 cache device: (nvme0n1) Force_MP600_19258229000128553340 Aug 3 07:08:37 Unraid emhttpd: shcmd (168): mount -t btrfs -o noatime,nodiratime /dev/nvme0n1p1 /mnt/cache Aug 3 07:08:37 Unraid kernel: BTRFS info (device nvme0n1p1): disk space caching is enabled Aug 3 07:08:37 Unraid kernel: BTRFS info (device nvme0n1p1): has skinny extents Aug 3 07:08:37 Unraid kernel: BTRFS info (device nvme0n1p1): enabling ssd optimizations Aug 4 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 2144 Aug 4 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 10816 Aug 4 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 1980448 Aug 4 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 221867184 Aug 4 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 412583080 Aug 4 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 413472432 Aug 4 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 415348952 Aug 4 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 417417816 Aug 4 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 419515976 Aug 4 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 421684832 Aug 4 04:40:01 Unraid kernel: BTRFS warning (device nvme0n1p1): failed to trim 159 block group(s), last error -5 Aug 4 04:40:01 Unraid kernel: BTRFS warning (device nvme0n1p1): failed to trim 1 device(s), last error -5 Aug 5 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 2112 Aug 5 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 10816 Aug 5 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 1981408 Aug 5 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 221947720 Aug 5 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 412753680 Aug 5 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 413557864 Aug 5 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 415377392 Aug 5 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 417390984 Aug 5 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 419511288 Aug 5 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 421742984 Aug 5 04:40:01 Unraid kernel: BTRFS warning (device nvme0n1p1): failed to trim 157 block group(s), last error -5 Aug 5 04:40:01 Unraid kernel: BTRFS warning (device nvme0n1p1): failed to trim 1 device(s), last error -5 Aug 6 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 2112 Aug 6 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 10816 Aug 6 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 1982144 Aug 6 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 412920608 Aug 6 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 413187664 Aug 6 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 415378744 Aug 6 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 417409608 Aug 6 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 419560544 Aug 6 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 421765096 Aug 6 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 423727096 Aug 6 04:40:02 Unraid kernel: BTRFS warning (device nvme0n1p1): failed to trim 157 block group(s), last error -5 Aug 6 04:40:02 Unraid kernel: BTRFS warning (device nvme0n1p1): failed to trim 1 device(s), last error -5 Aug 7 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 2208 Aug 7 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 10816 Aug 7 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 28264 Aug 7 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 1983200 Aug 7 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 221907328 Aug 7 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 412817112 Aug 7 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 413209680 Aug 7 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 415391776 Aug 7 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 417400296 Aug 7 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 419511288 Aug 7 04:40:01 Unraid kernel: BTRFS warning (device nvme0n1p1): failed to trim 164 block group(s), last error -5 Aug 7 04:40:01 Unraid kernel: BTRFS warning (device nvme0n1p1): failed to trim 1 device(s), last error -5 Aug 8 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 2208 Aug 8 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 10816 Aug 8 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 27528 Aug 8 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 43104 Aug 8 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 221907000 Aug 8 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 412590280 Aug 8 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 413212144 Aug 8 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 415404160 Aug 8 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 417400296 Aug 8 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 419498888 Aug 8 04:40:01 Unraid kernel: BTRFS warning (device nvme0n1p1): failed to trim 163 block group(s), last error -5 Aug 8 04:40:01 Unraid kernel: BTRFS warning (device nvme0n1p1): failed to trim 1 device(s), last error -5 Aug 9 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 2112 Aug 9 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 10816 Aug 9 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 43072 Aug 9 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 221907104 Aug 9 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 412902448 Aug 9 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 413606840 Aug 9 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 415404560 Aug 9 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 417458312 Aug 9 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 419506816 Aug 9 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 422036896 Aug 9 04:40:01 Unraid kernel: BTRFS warning (device nvme0n1p1): failed to trim 158 block group(s), last error -5 Aug 9 04:40:01 Unraid kernel: BTRFS warning (device nvme0n1p1): failed to trim 1 device(s), last error -5 Aug 10 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 2208 Aug 10 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 10816 Aug 10 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 28504 Aug 10 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 43072 Aug 10 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 221905752 Aug 10 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 412753672 Aug 10 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 414462904 Aug 10 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 415408064 Aug 10 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 417473536 Aug 10 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 419511288 Aug 10 04:40:01 Unraid kernel: BTRFS warning (device nvme0n1p1): failed to trim 158 block group(s), last error -5 Aug 10 04:40:01 Unraid kernel: BTRFS warning (device nvme0n1p1): failed to trim 1 device(s), last error -5 Aug 11 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 2208 Aug 11 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 10816 Aug 11 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 43072 Aug 11 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 221907824 Aug 11 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 412819344 Aug 11 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 414473160 Aug 11 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 415413064 Aug 11 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 417473560 Aug 11 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 419515976 Aug 11 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 422057856 Aug 11 04:40:02 Unraid kernel: BTRFS warning (device nvme0n1p1): failed to trim 174 block group(s), last error -5 Aug 11 04:40:02 Unraid kernel: BTRFS warning (device nvme0n1p1): failed to trim 1 device(s), last error -5

Happy Birthday Unraid ! I use my unraid since 2013 as the center of my house media and storage server and since a year, using a Win10 VM with Altaro Off-site Server as my Off-site server for backing up my clients servers! If not selected, please create more of those awesome badges and sell it as merch store stuff!

FYI, ASUS released a new BIOS UEFI for the ASUS WS X570-ACE motherboard. I will install it, but I first need to find a long hdmi cable for connecting a TV in the other room... Version 0803 2019/08/0615.39 MBytes PRO WS X570-ACE BIOS 0803 1.Updated AM4 combo PI 1.0.0.3 patch ABB 2.Optimized the chipset fan profile. The new profile allows the chipset fan to stop during idle or when temperature is low. 3.Supports Ubuntu 19.04 and other Linux distros 4.Improved system performance, stability and storage device compatibility

@bastl Thanks, didn't know that. In my case, i needed an Online way of doing it, but in case of offline, it's pretty easy with the details you mentionned.

The current PLEX server doesn't use NVDEC for the decoding part. Even when you enable hardware transcoding in Plex settings, it only use the NVENC (encoding) and still decode using CPU. The NVDEC Script is a wrapper that tricks Plex Transcoder by passingthu the Decoding command in parameters so that ffmpeg underneath will use the NVDEC too. It's not perfect in the current state as the ffmpeg is very old in Plex. The newest ffmpeg support nvdec a lot better. Hopefully, PLEX will update it soon. When you use the NVDec script, that lower your CPU usage because if it can, it will decode also with the nvidia card.

did not try, but probably. I needed only to increase the size. If they add it to GUI, they could know the actual size (they display it) and then they could allow only greater size this way it's sure it won't break.

Damn, i received again this morning the same email! Must be in the Crontab. How can I remove it if it's in there?

Hi, I found out that you can resize the Vdisk ONLINE without a shutdown of the VM by using this command in SSH in the Unraid CLI : virsh qemu-monitor-command "NAME_OF_THE_DOMAIN" block_resize drive-virtio-disk2 100G --hmp In this command, the "NAME_OF_THE_DOMAIN" is what you have in the GUI when creating/editing a VM (Name). The "drive-virtio-disk2" is usually the disk (can be any other disk too). It would be really nice if you could add "right-click" resize disk menu on a Running VM and then select one of the disk that could show-up in a submenu and then ask for the new size (in GB). After that, it's up to the user to go inside his VM (thru RDP or VNC) and rescan the disk (Disk Management in windows) and then "extend" the Partition You can find the "virtio-disk" from looking the XML view when editing a VM in the Unraid GUI. Look for "alias" and you then prepend "drive-" before when running the command to extend the size. <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 10/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/>

just found it! it was in "go" file. Running a DailyCacheTrim... My USB Key is the original from 2014 and still has lots of old stuff on it. I'm doing some cleanup now. I always upgraded on top of old stuff. When I did test my new Ryzen 3000 with Unraid, I create a trial USB key of Unraid and there is so much crap on my Pro USB Key i'm using from when I built my 1st unraid.

Hi, Since I switched to the new Ryzen 3000 plateform, I receive this error daily by email. I had at some point the "Dynamix SSD Trim", but it was uninstalled and I still receive those errors. I check in User Scripts plugins, and there is no script scheduled related to TRIM... Where I can find what triggers that ? FYI, I had a SATA SSD before, and I migrated to a NVMe Gen4 SSD on the new Platform, if that make any difference. The System Log has this : Aug 4 04:28:55 Unraid kernel: Aug 4 04:40:01 Unraid kernel: nvme 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x0000000000000000 flags=0x0000] Aug 4 04:40:01 Unraid kernel: nvme 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x0000000000000000 flags=0x0000] Aug 4 04:40:01 Unraid kernel: nvme 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x0000000000000000 flags=0x0000] Aug 4 04:40:01 Unraid kernel: nvme 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x0000000000000000 flags=0x0000] Aug 4 04:40:01 Unraid kernel: nvme 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x0000000000000000 flags=0x0000] Aug 4 04:40:01 Unraid kernel: nvme 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x0000000000000000 flags=0x0000] Aug 4 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 2144 Aug 4 04:40:01 Unraid kernel: nvme 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x0000000000000000 flags=0x0000] Aug 4 04:40:01 Unraid kernel: nvme 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x0000000000000000 flags=0x0000] Aug 4 04:40:01 Unraid kernel: nvme 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x0000000000000000 flags=0x0000] Aug 4 04:40:01 Unraid kernel: nvme 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x0000000000000000 flags=0x0000] Aug 4 04:40:01 Unraid kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0x0000000000000000 flags=0x0000] Aug 4 04:40:01 Unraid kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0x0000000000000000 flags=0x0000] Aug 4 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 10816 Aug 4 04:40:01 Unraid kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0x0000000000000000 flags=0x0000] Aug 4 04:40:01 Unraid kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0x0000000000000000 flags=0x0000] Aug 4 04:40:01 Unraid kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0x0000000000000000 flags=0x0000] Aug 4 04:40:01 Unraid kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0x0000000000000000 flags=0x0000] Aug 4 04:40:01 Unraid kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0x0000000000000000 flags=0x0000] Aug 4 04:40:01 Unraid kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0x0000000000000000 flags=0x0000] Aug 4 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 1980448 Aug 4 04:40:01 Unraid kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0x0000000000000000 flags=0x0000] Aug 4 04:40:01 Unraid kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0000 address=0x0000000000000000 flags=0x0000] Aug 4 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 221867184 Aug 4 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 412583080 Aug 4 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 413472432 Aug 4 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 415348952 Aug 4 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 417417816 Aug 4 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 419515976 Aug 4 04:40:01 Unraid kernel: print_req_error: I/O error, dev nvme0n1, sector 421684832 Aug 4 04:40:01 Unraid kernel: BTRFS warning (device nvme0n1p1): failed to trim 159 block group(s), last error -5 Aug 4 04:40:01 Unraid kernel: BTRFS warning (device nvme0n1p1): failed to trim 1 device(s), last error -5 Aug 4 04:40:17 Unraid sSMTP[912]: Creating SSL connection to host Aug 4 04:40:17 Unraid sSMTP[912]: SSL connection using TLS_AES_256_GCM_SHA384 Aug 4 04:40:19 Unraid sSMTP[912]: Sent mail for [email protected] (221 2.0.0 closing connection j22sm33387198qtp.0 - gsmtp) uid=0 username=root outbytes=484