NathanR
Members
-
Joined
-
Last visited
Everything posted by NathanR
-
6.11.5 I want this type of file structure: Media - SMB Share [one mapped drive for all users] Media\TV - Disk1 Media\Movies - Disk2 Media\Music - Disk3 Media\Photos - Disk3 Media\Projects - cache >[mover]> Disk3 How do I get there? Or is this even possible? I already have root share setup, I thought this would solve my problem; but not really. Resources: Similar thread:
-
Creating an empty folder takes forever (I stopped waiting after 5min). Clicking create then clicking cancel immediately is my current workaround. What do? 6.11.5 2023.03.01
-
+1 - L2 ARC I am new to Unraid and am surprised that 'cache' (now pools) aren't really 'cache' they are more like user defined write pools with user defined copy/move rules [hence the move from cache terminology to pool terminology]. ZFS will change much of this and enable us to have L2 ARC amongst other things.
-
-
-
+1 I am constantly modifying my Unraid setup as I learn new things. I rarely need to turn off my HA VM or my Win 10 VM; yet taking down the array does that. Worse - turning on the array doesn't auto-on the VMs only Dockers --- I read numerous times about how to implement this when skimming through this thread. I also see questions about licensing, what to do when a mapped share is down, how to handle different locations for dockers/vms, etc. The devs really would be the experts at how as there are numerous obstacles to overcome. Array parity behavior, Array licensing behavior, Access to drives if array is down, Etc. I get it, there's lots to think through. --- Here's my take. Requirements - a working cache pool This forces users to not use the array. Limits to more experienced users. Licensing - Pro version enables support for multiple offline pools. Solves all licensing issues. All the licensing talk is too complicated. Why make code changes when you can make policy changes that make sense. Warning - Any mapped shares that a docker/VM uses will not work and can crash your docker/VM if the internal software cannot handle it. Why make this a Limetech issue? Push the responsibility on the user & container developer. Ex. 1) Plex - libraries shared to spinning rust on array - okay who cares. Plex handles missing library locations gracefully. Ex. 2) Windows VM - can't find a share. Windows will handle that gracefully (or not) lol. Ex. 3) HA, FW, UtKuma, Unifi, etc. - These reside entirely inside their docker/VM container. They only write out or read out if they have mapped syslog folder or something. Too complicated to check if it's on an array, etc. Who cares. Responsibility is on the user. New Buttons & GUI changes Array-Start/Stop button (1) - main array Array-Start/Stop button (2) - cache pool 1 Array-Start/Stop button (n) - cache pool n [drop down menu button] --- Implementation 0.1 'All or nothing.' Shares cannot point to the 'DockVM' pool [they can, but if they do, then you can't keep DockVM pool online] All Online Dockers volume mappings point to DockVM pool All Online VM disk mappings point to DockVM pool [This simplifies the programming required. sure there are dedicated disks, usb disks etc. who cares. Start simple] Offline Dockers/VMs are not considered [if they're offline and your turning off the array but not the DockVM pool...who cares] (3 pools) [You could forgo the cache pool of course, but most pro users are going to have a setup like this] Array [unraid] [hdd] Cache [whatever; raid, probably 1 or 0+1] [probably ssd or nvme] DockVM [whatever; raid, probably 1 or 0+1] [probably ssd or nvme] Clicking stop on the array - "error docker.list & VM.list are online & uses array volume mappings" I would use this right now. I'd make my current cache drive only for docker & vm until implementation 1.0 can roll out. I don't need to copy files to my cache and then use the mover to move to spinning rust. I'd rather have my dockers & vms stay up right now. Plex docker running? - I'd have to shut it down. Who cares, if the array is offline no one is watching movies anyways. But my HA & W10VM (with internal database on vdisk) stay up; woot.--- --- Implementation 1.0 'Almost All or nothing.' All Online Dockers volume mappings point to cache All Online VM disk mappings do not point to array All Offline Dockers cannot start without both array & cache 'online' All Offline VMs cannot start without both array & cache 'online' The only reason this is separate from 0.1 is due to the fact that the shares are mapped to the same cache pool as the dockers & VMs. Thus I'm assuming there will be some code changes & checks to ensure compatibility. Plex docker - must be shutdown to shutdown array [but keep cache online] --- Implementation 2.0 'Granular approach' All of the above but: Checks if the primary storage for docker or VM is on the cache pool. Ignores mappings to array (but reports warning) Plex docker - stays running; volume mappings to array are offline/not working. Hopefully container doesn't crash. --- Implementation 3.0 'Granular Auto Approach' All of 2.0 plus the ability to auto-on/off dockers & VMs based upon which pool is going up/down. Global setting for restart Unraid OS auto-start or start/stop array pool(s) to auto-start Docker/VMs.
-
This is the answer to my question. My expectation of VM behavior would be identical to docker behavior. --- I should have been much more clear with my post and my image is confusing as it shows nothing wrong. I apologize. Expected Behavior: 1. Set [certain] VMs & Dockers to auto-start 2. Stop array 3. Start array 4. [certain] VMs & Dockers previously set to auto-start...do just that >> auto-start 5. Restart Unraid 6. [certain] VMs & Dockers previously set to auto-start...do just that >> auto-start Current Behavior: 1. Set [certain] VMs & Dockers to auto-start 2. Stop array 3. Start array 4. No VMs auto-start & [certain] Dockers previously set to auto-start...do just that >> auto-start 5. Restart Unraid 6. [certain] VMs & Dockers previously set to auto-start...do just that >> auto-start
-
"VMS" = plural 1 & 2 should auto-start. They do not. 3rd VM isn't supposed to start.
-
I am confused. Should this happen?
-
Version 6.11.5 2022-11-20 Model: Custom M/B: ASRockRack X570D4U-2L2T Version - s/n: BIOS: American Megatrends International, LLC. Version P1.40. Dated: 05/19/2021 CPU: AMD Ryzen 9 5900X 12-Core @ 3700 MHz HVM: Enabled IOMMU: Enabled Cache: 768 KiB, 6 MB, 64 MB Memory: 64 GiB DDR4 Multi-bit ECC (max. installable capacity 128 GiB) Network: bond0: fault-tolerance (active-backup), mtu 1500 Kernel: Linux 5.19.17-Unraid x86_64 OpenSSL: 1.1.1s Uptime: 23 hours, 33 minutes Not sure what to make of this. Am fairly new to Unraid. Messing around with my server (added Emby docker) while copying over a large folder (~200G) to my server from my desktop. Saw high (20%) CPU even though docker/VM don't show any usage (3-5%) Randomly clicked the syslog button... and saw this. What do? 01-31-2023 19:32:18 Daemon.Error 192.168.10.5 Jan 31 19:32:18 Storinator smbd[20034]: synthetic_pathref: opening [From F/Wondershare/DrFone/Backup/00008101-001E183C1430001E/68/68a018d92ba81499554e4850dea1357e4e8639e9] failed 01-31-2023 19:32:18 Daemon.Error 192.168.10.5 Jan 31 19:32:18 Storinator smbd[20034]: [2023/01/31 19:32:18.755826, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) 01-31-2023 19:32:18 Daemon.Error 192.168.10.5 Jan 31 19:32:18 Storinator smbd[20034]: synthetic_pathref: opening [From F/Wondershare/DrFone/Backup/00008101-001E183C1430001E/68/689df748d1cd62661a202359400ce7fbbaed9971] failed 01-31-2023 19:32:18 Daemon.Error 192.168.10.5 Jan 31 19:32:18 Storinator smbd[20034]: [2023/01/31 19:32:18.628410, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) 01-31-2023 19:32:18 Daemon.Error 192.168.10.5 Jan 31 19:32:18 Storinator smbd[20034]: synthetic_pathref: opening [From F/Wondershare/DrFone/Backup/00008101-001E183C1430001E/68/68995c8b0a3098c2a2ab67f3217939164ad372ac] failed 01-31-2023 19:32:18 Daemon.Error 192.168.10.5 Jan 31 19:32:18 Storinator smbd[20034]: [2023/01/31 19:32:18.502410, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) 01-31-2023 19:32:17 Daemon.Error 192.168.10.5 Jan 31 19:32:18 Storinator smbd[20034]: synthetic_pathref: opening [From F/Wondershare/DrFone/Backup/00008101-001E183C1430001E/68/6897dadd84282fe447ab5e2d850b263a30589024] failed 01-31-2023 19:32:17 Daemon.Error 192.168.10.5 Jan 31 19:32:18 Storinator smbd[20034]: [2023/01/31 19:32:18.385726, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) 01-31-2023 19:32:17 Daemon.Error 192.168.10.5 Jan 31 19:32:18 Storinator smbd[20034]: synthetic_pathref: opening [From F/Wondershare/DrFone/Backup/00008101-001E183C1430001E/68/68973b2f7b9da0da3ba5b79ba84bc9fe247f1a43] failed 01-31-2023 19:32:17 Daemon.Error 192.168.10.5 Jan 31 19:32:18 Storinator smbd[20034]: [2023/01/31 19:32:18.261690, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) 01-31-2023 19:32:17 Daemon.Error 192.168.10.5 Jan 31 19:32:18 Storinator smbd[20034]: synthetic_pathref: opening [From F/Wondershare/DrFone/Backup/00008101-001E183C1430001E/68/6893ed2223c9a2435d3d4a891d8345341022b007] failed 01-31-2023 19:32:17 Daemon.Error 192.168.10.5 Jan 31 19:32:18 Storinator smbd[20034]: [2023/01/31 19:32:18.138887, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) 01-31-2023 19:32:17 Daemon.Error 192.168.10.5 Jan 31 19:32:18 Storinator smbd[20034]: synthetic_pathref: opening [From F/Wondershare/DrFone/Backup/00008101-001E183C1430001E/68/688f130db113dd673926d3db641f8ac93005ebe9] failed 01-31-2023 19:32:17 Daemon.Error 192.168.10.5 Jan 31 19:32:18 Storinator smbd[20034]: [2023/01/31 19:32:18.034068, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) 01-31-2023 19:32:17 Daemon.Error 192.168.10.5 Jan 31 19:32:17 Storinator smbd[20034]: synthetic_pathref: opening [From F/Wondershare/DrFone/Backup/00008101-001E183C1430001E/68/688a48c632936f9f0afe8519aee0bc0d3680d271] failed 01-31-2023 19:32:17 Daemon.Error 192.168.10.5 Jan 31 19:32:17 Storinator smbd[20034]: [2023/01/31 19:32:17.906046, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) 01-31-2023 19:32:17 Daemon.Error 192.168.10.5 Jan 31 19:32:17 Storinator smbd[20034]: synthetic_pathref: opening [From F/Wondershare/DrFone/Backup/00008101-001E183C1430001E/68/68842793cd6658b2fe4377e06f472120b44a0979] failed 01-31-2023 19:32:17 Daemon.Error 192.168.10.5 Jan 31 19:32:17 Storinator smbd[20034]: [2023/01/31 19:32:17.785420, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) 01-31-2023 19:32:17 Daemon.Error 192.168.10.5 Jan 31 19:32:17 Storinator smbd[20034]: synthetic_pathref: opening [From F/Wondershare/DrFone/Backup/00008101-001E183C1430001E/68/68822ec6a841d8b3c83cb15468073835f86e6b6d] failed 01-31-2023 19:32:17 Daemon.Error 192.168.10.5 Jan 31 19:32:17 Storinator smbd[20034]: [2023/01/31 19:32:17.668262, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) 01-31-2023 19:32:17 Daemon.Error 192.168.10.5 Jan 31 19:32:17 Storinator smbd[20034]: synthetic_pathref: opening [From F/Wondershare/DrFone/Backup/00008101-001E183C1430001E/68/6881428a9f6c5c8c0168a38c4df7609a1caa3eb9] failed 01-31-2023 19:32:17 Daemon.Error 192.168.10.5 Jan 31 19:32:17 Storinator smbd[20034]: [2023/01/31 19:32:17.551534, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) 01-31-2023 19:32:17 Daemon.Error 192.168.10.5 Jan 31 19:32:17 Storinator smbd[20034]: synthetic_pathref: opening [From F/Wondershare/DrFone/Backup/00008101-001E183C1430001E/68/6880a3f9f18602eef2cef3c0bfe35d1f18f1c567] failed 01-31-2023 19:32:17 Daemon.Error 192.168.10.5 Jan 31 19:32:17 Storinator smbd[20034]: [2023/01/31 19:32:17.440756, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) 01-31-2023 19:32:16 Daemon.Error 192.168.10.5 Jan 31 19:32:17 Storinator smbd[20034]: synthetic_pathref: opening [From F/Wondershare/DrFone/Backup/00008101-001E183C1430001E/68/68806dec00f689c3cbd8dd2b9f504f2bf3ba1dda] failed 01-31-2023 19:32:16 Daemon.Error 192.168.10.5 Jan 31 19:32:17 Storinator smbd[20034]: [2023/01/31 19:32:17.329113, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) 01-31-2023 19:32:16 Daemon.Error 192.168.10.5 Jan 31 19:32:17 Storinator smbd[20034]: synthetic_pathref: opening [From F/Wondershare/DrFone/Backup/00008101-001E183C1430001E/68/687fe5ff4dbd3f40584419872c708449338ab41c] failed 01-31-2023 19:32:16 Daemon.Error 192.168.10.5 Jan 31 19:32:17 Storinator smbd[20034]: [2023/01/31 19:32:17.131462, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) 01-31-2023 19:32:16 Daemon.Error 192.168.10.5 Jan 31 19:32:17 Storinator smbd[20034]: synthetic_pathref: opening [From F/Wondershare/DrFone/Backup/00008101-001E183C1430001E/68/687e2ccc7c4ac0daed90e8cfb346c002e0fad1b7] failed 01-31-2023 19:32:16 Daemon.Error 192.168.10.5 Jan 31 19:32:17 Storinator smbd[20034]: [2023/01/31 19:32:17.011287, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) storinator-diagnostics-20230131-1953.zip
-
I'm in the same boat. I have my main x570/5900X Unraid server at home, but I want to have an off-site backup at my parents (plus running a few dockers for them (home assistant, cameras, etc). I'm looking into building/buying hardware to accommodate. I'm heavily considering something like the TS-473A. But maybe just a HDD stack + RPI would work too. Idk, just started looking around.
-
95 days, 1 hour, 58 minutes uptime on 6.11.0 Running: 1x W10 VM Handful of dockers Some apps Just updated to 6.11.5 Needed a few reboots to get stats working properly. Hopefully stable for a long time again Found this useful command for USB Flash Drive (OS) backups from this reddit post: https://www.reddit.com/r/unRAID/comments/wp44pp/reminder_backup_your_unraid_usb_drive/ zip -r /mnt/user/backups/unraidbackup/flash`date +%d-%m-%Y`.zip /boot Fan 1 - CPU 80mm Noctua Fan 2 - x570 Chipset 40mm Noctua Fan 3 - Chassis Fan(s) 120mm arctic p12 PWM PST CO [25% = 500rpm, 50% = 900rpm, 75% = 1200rpm, 100% = 1800rpm] Fan 4 - HDD chassis fan 80mm arctic p8 PWM PST CO [25% = 900rpm, 50% = 1500rpm, 75% = 2300rpm, 80% = 2500rpm, 100% = 2900rpm] Fan 5 - future 120mm Fan 6 - future 120mm
-
Plex server crashed again Tis why I'm hesitant to move Plex/Unifi/Syncthing/etc. over I Setup syslog/kiwi, hopefully I can catch the error now. https://documentation.solarwinds.com/archive/pdf/kss/kss_getting_started_guide.pdf
-
VM is now running d-tools server on Win10x64 Pro. Server has been up for 8 days since upgrade to 6.11 Hoping for lots of stability now that I have something production-esque running on the server. Next will be Plex server, video-card passthru, and adding HDD's.
-
Expanded my VM's HDD (vdisk1.img) size from 30GB to 60GB. Deleted the recovery partition so I could extend the OS drive space from 30GB to 40GB. https://www.partitionwizard.com/partitionmagic/delete-recovery-partition.html
-
Brainstorming/thoughts post... Looking into converting my .xva (xcp-ng) vms into Unraid format (qcow?) Maybe this? - https://forums.unraid.net/topic/69244-convert-vmware-vm-to-kvm/ Looking into converting my physical disk into unraid drive. https://kmwoley.com/blog/convert-a-windows-installation-into-a-unraid-kvm-virtual-machine/ https://kmwoley.com/blog/reduce-shrink-raw-image-img-size-of-a-windows-virtual-machine/ A little worried I can't shrink my 500GB NVMe drive down to a manageable 50GB lol Looking into creating new W10 VM I was looking here > https://wiki.unraid.net/Manual/VM_Management#Basic_VM_Creation But that is wrong, this is correct steps to install HDD driver > https://wiki.unraid.net/index.php/UnRAID_Manual_6#Installing_a_Windows_VM Latest virtio drivers: https://github.com/virtio-win/virtio-win-pkg-scripts/blob/master/README.md
-
I have a NH-D9L on the CPU now NF-A4x10 PWM on the x570 chipset, which gets super hot. (ASRock really should have had a fan & larger cooler on x570 chipset) pwm cpu-rpm x570-rpm 100% 1900 5000 75% 1500 4000 50% 1100 2700 25% 600 1600
-
Update. Now running Version 6.11.0 2022-09-23 Pearl & iperf3 included with the kernel so...yay. My 10G NIC's are confirmed working; woot! I was having issues confirming speeds from within the W10 VM. Also, I have my 1T 980's in what I think is a Raid 1 pool. But I've read conflicting posts about whether this is operating properly or not. Pressing the rebalance as Raid 1 does nothing. I also modified the temp warning/errors to 85c so I didn't get the annoying Samsung 980 bug. I really wish they would do a firmware release. BTW...how do I do a NVMe firmware update? Oh! and I'm super happy that the temp sensors work out of the box now (well, there is a tiny config todo). Pearl or Linux Kernel with AMD tunings, whatever, don't care, I'm happy figured out exactly which by looking at IPMI & running P95 in a VM. CPU @ 70c and x570 @ ~50c lol
-
Thanks! I haven't had time to look into why it crashed the second time. Any pointers on where to look in the logs? I read that the logs don't show pre-boot logs IIRC. Idk, I'll investigate in the future. Re: RC - I completely agree, I usually don't run RC stuff, but I saw all the significant improvements (in-general & x570/kernel) and wanted to try it out. My SVR right now is just a test-bench and is running things that aren't critical (yet) just so I can get used to Unraid in a relaxed environment. That said, I am in the process of moving computer cases, installing 10G, and swapping drives so I'll be ready soon to move the server towards production Edit: Just read your story I think know I am in good company
-
Hi Spencer, Good copy, thank you. I am now the proud owner of Pro I am excited for what the future holds!
-
TL;DR Purchase license now, activate later (when ready?) Downside to upgrading Basic > Pro? Are there any downside to purchasing a basic license and then upgrading to pro? I can save $14.70 going from basic to pro it seems. https://unraid.net/upgrade-sale I have no intention of purchasing any other license than Pro. I want to take advantage of the sale before it ends at midnight. Still, seems silly to not offer a discount without upgrade when upgrading (might, hence my question) does the same thing. I presume the only downside is two license keys and two purchase receipt emails? --- I have 8 days left on my trial, and the server is running fairly well. I have plenty still to do. But I am very happy with the setup thus far. I really like Unraid community, plugins/apps/dockers/support, adding drives slowly, etc. I also love the cost model, one and done. My favorite. I'd do anything for not not having SAAS, I freaking hate that stuff. I know it's better for company's cash flow. But I am so thankful for that model. Thank you Lime Tech. I wasn't intending on licensing it yet because I wanted to have it setup the way I wanted and then transfer to the new USB drive. [As I feel like the licensing only works on one flash drive and I don't want to license this flash drive; I'd rather transfer it. But I also want to test out the new flash drive, etc. I don't know what to do.] Can I purchase the licenses now and 'activate' them later?
-
Had a crash even after fixing Idle current. Probably will disable global C-states now. Upgraded to 6.11-RC2 to see if system is more stable for X570 builds. Tried to get temp/sensors working. Foundout the nerdtools plugin for Pearl is broken on 6.11 - hopefully we seen an update soon https://www.reddit.com/r/unRAID/comments/w9647x/unraid_6110rc1_now_available_notes_in_comments/ Version 6.11.0-rc2 2022-07-27 Improvements With this release there have been many base package updates including several CVE mitigations. The Linux kernel update includes mitigation for Processor MMIO stale-data vulnerabilities. The plugin system has been refactored so that 'plugin install' can proceed in the background. This alleviates issue where a user may think installation has crashed and closes the window, when actually it has not crashed. Many other webGUI immprovements. Bug fixes Fixed issue in VM manager where VM log can not open when VM name has an embedded '#' character. Fixed issue where Parity check pause/resume on schedule was broken. Change Log vs. Unraid OS 6.10 Base distro: aaa_base: version 15.1 aaa_glibc-solibs: version 2.35 aaa_libraries: version 15.1 adwaita-icon-theme: version 42.0 appres: version 1.0.6 at-spi2-core: version 2.44.1 atk: version 2.38.0 bind: version 9.18.5 btrfs-progs: version 5.18.1 ca-certificates: version 20220622 cifs-utils: version 6.15 coreutils: version 9.1 curl: version 7.84.0 dbus: version 1.14.0 dmidecode: version 3.4 docker: version 20.10.17 (CVE-2022-29526 CVE-2022-30634 CVE-2022-30629 CVE-2022-30580 CVE-2022-29804 CVE-2022-29162 CVE-2022-31030) editres: version 1.0.8 etc: version 15.1 ethtool: version 5.18 file: version 5.42 findutils: version 4.9.0 freeglut: version 3.2.2 freetype: version 2.12.1 fribidi: version 1.0.12 fuse3: version 3.11.0 gdbm: version 1.23 gdk-pixbuf2: version 2.42.8 git: version 2.37.1 glib2: version 2.72.3 glibc: version 2.35 gnutls: version 3.7.6 gptfdisk: version 1.0.9 harfbuzz: version 5.0.1 hdparm: version 9.64 htop: version 3.2.1 icu4c: version 71.1 inotify-tools: version 3.22.6.0 iproute2: version 5.18.0 iptables: version 1.8.8 json-c: version 0.16_20220414 kernel-firmware: version: 20220725_150864a kmod: version 30 libX11: version 1.8.1 libXcursor: version 1.2.1 libaio: version 0.3.113 libcap-ng: version 0.8.3 libdrm: version 2.4.110 libepoxy: version 1.5.10 libevdev: version 1.12.1 libgcrypt: version 1.10.1 libgpg-error: version 1.45 libidn: version 1.41 libjpeg-turbo: version 2.1.3 libmnl: version 1.0.5 libnetfilter_conntrack: version 1.0.9 libnfnetlink: version 1.0.2 libnftnl: 1.2.2 libnl3: version 3.6.0 libtiff: version 4.4.0 libtiff: version 4.4.0 liburcu: version 0.13.1 libusb: version 1.0.26 libxcb: version 1.15 libxkbcommon: version 1.4.1 libzip: version 1.9.2 libX11: version 1.8.1 listres: version 1.0.5 logrotate: version 3.20.1 lsof: version 4.95.0 lzip: version 1.23 mc: version 4.8.28 mcelog: version 184 mkfontscale: version 1.2.2 nano: version 6.3 nettle: version 3.8 nfs-utils: version 2.6.1 nghttp2: version 1.48.0 ntfs-3g: version 2022.5.17 oniguruma: version 6.9.8 openssh: version 9.0p1 openssl: version 1.1.1q (CVE-2022-1292 CVE-2022-2097 CVE-2022-2274) openssl-solibs: version 1.1.1q (CVE-2022-1292) pango: version 1.50.8 pciutils: version 3.8.0 pcre2: version 10.40 php: version 7.4.30 (CVE-2022-31625 CVE-2022-31626) rsync: version 3.2.4 samba: version 4.16.4 (CVE-2022-2031 CVE-2022-32744 CVE-2022-32745 CVE-2022-32746 CVE-2022-32742) setxkbmap: version 1.3.3 shared-mime-info: version 2.2 sqlite: version 3.39.2 sudo: version 1.9.11p3 sysfsutils: version 2.1.1 tdb: version 1.4.7 tevent: version 0.12.1 tree: version 2.0.2 util-linux: version 2.38 wget: version 1.21.3 xauth: version 1.1.2 xclock: version 1.1.1 xdpyinfo: version 1.3.3 xfsprogs: version 5.18.0 xkeyboard-config: version 2.36 xload: version 1.1.4 xmodmap: version 1.0.11 xsm: version 1.0.5 xterm: version 372 xwud: version 1.0.6 Linux kernel: version 5.18.14 (CVE-2022-21123 (CVE-2022-21123 CVE-2022-21125 CVE-2022-21166) oot: md/unraid: version 2.9.23 CONFIG_IOMMU_DEFAULT_PASSTHROUGH: Passthrough CONFIG_VIRTIO_IOMMU: Virtio IOMMU driver CONFIG_X86_AMD_PSTATE: AMD Processor P-State driver CONFIG_FIREWIRE: FireWire driver stack CONFIG_FIREWIRE_OHCI: OHCI-1394 controllers CONFIG_FIREWIRE_SBP2: Storage devices (SBP-2 protocol) CONFIG_FIREWIRE_NET: IP networking over 1394 CONFIG_INPUT_UINPUT: User level driver support CONFIG_INPUT_JOYDEV: Joystick interface CONFIG_INPUT_JOYSTICK: Joysticks/Gamepads CONFIG_JOYSTICK_XPAD: X-Box gamepad support CONFIG_JOYSTICK_XPAD_FF: X-Box gamepad rumble support CONFIG_JOYSTICK_XPAD_LEDS: LED Support for Xbox360 controller 'BigX' LED Management: rc.nginx: enable OCSP stapling on certs which include an OCSP responder URL rc.wireguard: add better troubleshooting for WireGuard autostart rc.S: support early load of plugin driver modules upc: version v1.3.0 webgui: Plugin system update Detach frontend and backend operation Use nchan as communication channel Allow window to be closed while backend continues Use SWAL as window manager Added multi remove ability on Plugins page Added update all plugins with details webgui: docker: use docker label as primary source for WebUI This makes the 'net.unraid.docker.webui' docker label the primary source when parsing the web UI address. If the docker label is missing, the template value will be used instead. webgui: Update Credits.page webgui: VM manager: Fix VM log can not open when VM name has an embedded '#' webgui: Management Access page: add details for self-signed certs webgui: Parity check: fix regression error webgui: Remove session creation in scripts webgui: Update ssh key regex Add support for ed25519/sk-ed25519 Remove support for ecdsa (insecure) Use proper regex to check for valid key types webgui: misc. style updates webgui: Management access: HTTP port setting should always be enabled webgui: Fix: preserve vnc port settings webgui: Fix regression error in plugin system webgui: Fix issue installing registration keys webgui: Highlight case selection when custom image is selected webgui: fix(upc): v1.4.2 apiVersion check regression
-
Ran into the dreaded Ryzen Linux power states issue. I was curious if I was going to have an issue with it or not. I had BIOS set for typical idle current, but when I replaced IPMI/BMS chip I think it got reset somehow. I haven't had a need for disabling global c-states yet, but I am curious once I have more going on if it will be necessary. My Threadripper TrueNAS build definitely needed the fix and would reboot constantly before fixing those issues. --- Solved via FAQ for v6, this is a very good post that quickly explains the various issues running Ryzen and acceptable parameters.
-
brave://flags/#brave-debounce Fixed https://community.brave.com/t/random-crash-after-sorting-a-page/416551/8?u=lightingman117
-
Been running Unraid on Chrome (.114) while using Brave (.134) Finally got a crash in brave on B&H's website. So latest Chromium must be broken. Sorry to bother.
