Stokkes

Hello, Curious if anyone has converted their user scripts folder to a git repo to keep things in sync? Not sure how the USB would handle .git and other special files. Since this is effectively code, I'm hoping to keep it up in my git repos if possible.

Ok so I figured out what is going on (honestly couldn't really sleep), but I would like to keep this open as a "bug" because this hasn't happened with other versions, so I'm thinking some kind of logic/etc changed. Root cause: I have a 2nd USB flash drive plugged in that has a different filesystem label (URBACKUP), I've had this for years.. Every upgrade has worked but this one. Going from 6.11 to 6.12, 12.1, 12.2, etc.. all worked, no changes. Unplugging before rebooting into 6.12.3 fixes it. Explanation: I am often physically away from the server, and I need a way to restore the services if I'm not around. Unraid's biggest flaw in my opinion in the USB requirement, but I live with it because I still find Unraid the best system, it just means I have to find creative ways to ensure I can maintain the service. The ONE thing you can't do remote is physically change a USB :), and since 2007, I've had many USB fail, but the problem is you don't always know until you reboot and if you're remote, you're screwed. I clone the primary USB to the secondary USB nightly via cron/user scripts. This has worked for years, but the one thing I've learned: the backup USB cannot have the same filesystem label ("UNRAID") or you will get issues on boot. So I rename the filesystem label ("URBACKUP").. In the event of an issue with the USB, I can get access to the system via my VPN/IPMI/IKVM, rename the label to UNRAID, change the boot order in the BIOS, etc.. I have a process I've done a few times that works fine. Again, this has worked for years, but not 6.12.3.. Not sure if the boot process or logic changed.. I do not have the backup USB in my boot order, so it never ever boots from this (another lesson learned from the past), but when Unraid boots and loads the kernel, that's when it seems to go wonky. Anyway, I understand this may get dismissed, but for some of us, we need ways to recover our systems remotely working within the constraints of the USB.. I need to find a way to get this to work with 6.12.3 now. Thanks!

That's my problem. I installed 4 times last night 6.12.3 and this is what happens. I can take a video to show the upgrade process but here is what I did (like I've done hundreds of times. I've been running unraid for over a decade off/on). Bought my pro key in 2007. 1. Go into Tools > Update OS 2. Unraid detects the upgrade 6.12.3 3. I click the acknowledge release notes and then hit the update button 4. The update dialog comes up, downloads the update zip file and installs. 5. When the button on the dialog zip file changes from Close to Done I hit the Done button to dismiss it. 6. I go back to the dashboard just to ma navigate away from the update OS page. 7. I get the banner at the top to reboot. 8. I reboot 9. No network. I should also say that I checked the file dates of bzroot, bzfirmware kocated in /boot and they are all July 14 which coincides with the 6.12.3 release. To revert I just go into the /boot/previous and copy the files back to /boot. This restores functionality. i did it 4 times last night. This is incredibly perplexing because I am not doing anything different to update to 6.12.3. And why the diagnostics are incomplete and show 12.2 I have no idea. It doesn't make sense esp if the file dates on the flash match the 12.3 release.

There is ZnapZend and Sanoid, I suggest using Sanoid, it's not too difficult to configure and you can run it via User Scripts.. I have it snapshot my apdata and other volumes ever 15 minutes, keep those for 3 days, snapshot every hour, keep those for a week, snapshot every day, keep those for 30 days, you get the idea. It will also auto-clean up snapshots.. There is another tool that comes with it, Syncoid that you can then sync the snapshots to another ZFS pool, which I also do. That zfs pool can be another pool on your unraid server or even better, another host altogether!

Omg so sorry! Thank you that's awesome. Looking forward to the release!

Hey, love this plugin, but wondering if there is going to be an update pushed in the future (is it still supported)? Watched the video on Youtube about ZFS datasets and installed this. My issue I think is that it queries (on the Main tab) all the snapshots/datasets I have (which are A LOT) because I use snapoid/syncoid to auto-snap every 15 minutes and copy the snaps to another zfs pool, so there are thousands of snapshots, this really really slows down the Main tab, taking anywhere from 30-60 seconds to load. Hoping we can get an option to have it not scan datasets or snapshots to make this snappier - ideally if we can just go into a different part of the webGui to view snapshots, etc. Thanks!

I think that's a different issue. we are talking about Proxmox so the freeze is shown in the KVM window. Also The i915 (intel onboard gpu) IS the gpu. If you plug a monitor you won't see unraid you'll see Proxmox.

Unfortunately I'm taking the steps to dump Unraid (probably for open media vault with snapraid and mergerfs). If I can't upgrade then it's effectively useless to me. I'm familiar with Linux and have rolled my own before. Just got to the age where I didn't want to tinker. Oh well. Since virtualizing unraid isn't officially supported I'm not expecting much traction so I'm not really feeling too keen to go spelunking through it. Ah well. Probably for the best. Slack was pissing me off anyway.

No joy.. Removed NerdPack, still hangs right at the i915 initialization. Removing the GPU from the VM allows it to boot no problem, re-adding it and it fails at the same place. There is something wonky in the 6.11 branch that is causing this. I doubt it's package/plugin related because where the system initializes the GPU card it's still early in the boot phase, before it's been handed off to Unraid. Very frustrating that I can't upgrade

Here you go. This is on 6.10.3 since I can't successfully boot 6.11 without removing GPU passthrough. Let me know if you want a diagnostic of 6.11 without GPU. tower-diagnostics-20221008-0825.zip

Hey all I upgraded to 6.11 this morning and rebooted my system and now it hangs initializing the i915. Anyone have any idea? Had to revert back to 6.10.1 to get this to boot. I'm not sure what changed in Unraid that would have stopped it from working (nor not sure how to get 6.11 working on Proxmox now). Here's the message (also screenshot attached): i915 0000:04:00.0: drm] VT-d active for gfx access This is the last message and it's just hung there. Tried shutting down the VM, restarting Proxmox.. Thanks!

Here's the output ❯ sudo dmidecode | grep Version Wed 25 May 14:03:10 Version: pc-q35-6.0 Version: pc-q35-6.0 Version: pc-q35-6.0 Version: 0.0.0

Latest, 6.10.1 Attached a screenshot of the panel in the Dashboard that shows the Proxmox pc-q35 cpu.. Like I mentioned above, it's not a big deal, just OCD and weird it doesn't detect the right CPU.

❯ grep -Pom1 'model name\s+:\s*\K.+' /proc/cpuinfo Wed 25 May 08:45:03 Intel(R) Core(TM) i9-10900 CPU @ 2.80GHz

I did not unfortunately.

Everything is pretty much already there, seems like it would make the most sense to hook into ZED. The plugin includes the notification for scrubs, I'm just suggesting we add notifications for state change as well and make it part of the package.

Could we get a script to send a notification on the ZFS event for state change? Specifically I have been testing this by creating pools and then removing a hard drive to force a degraded state and there are no notification sent. Don't get me wrong, notifications on scrub finishing are good, but if the pool goes into a degraded state because a drive failed, it should notify you pretty consistently since you're at risk for data loss. I haven't been able to trigger any notifications on my simulations of getting a test pool into a degraded state.

Hey all This is just a silly question (not sure if it has any real impacts) - No problems running Unraid on Proxmox, ESXi, etc for a few years. The CPU "type" in Proxomox for the Unraid VM is set to "Host", however, the Unraid dashboard detects the CPU as "pc-q35-6.0" at 2000Mhz, But the funny thing is, running lscpu in the Unraid terminal detects the right CPU: Vendor ID: GenuineIntel CPU family: 6 Model: 165 Model name: Intel(R) Core(TM) i9-10900 CPU @ 2.80GHz Stepping: 5 CPU MHz: 2807.986 BogoMIPS: 5615.97 Virtualization: VT-x Hypervisor vendor: KVM Virtualization type: full L1d cache: 256 KiB L1i cache: 256 KiB L2 cache: 32 MiB L3 cache: 16 MiB NUMA node0 CPU(s): 0-7 Vulnerability Itlb multihit: Not affected Vulnerability L1tf: Not affected Vulnerability Mds: Not affected Vulnerability Meltdown: Not affected Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization Vulnerability Spectre v2: Mitigation; Enhanced IBRS, IBPB conditional, RSB filling Vulnerability Srbds: Not affected Vulnerability Tsx async abort: Not affected Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clfl ush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc arch_p erfmon rep_good nopl xtopology cpuid tsc_known_freq pni pclmulqdq vmx ssse3 fma cx16 pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch cpuid_fault invpc id_single ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ep t vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdsee d adx smap clflushopt xsaveopt xsavec xgetbv1 xsaves arat umip pku ospke md_ clear arch_capabilities Curious if anyone has any ideas.. Just a bit of OCD going on

Is this completely incompatible with InfluxDB v2.0? I have Unraid sending data to InfluxDB as I can see it using the influx explorer, but the dashboards are empty. Before I spend more time troubleshooting I just want to know if Influx v1.x is absolutely necessary or not. Thanks!

Since Unraid runs from a USB, this is pretty straight forward and you can test it quite easily. Just boot your server from the USB instead of ESXi.. It should load right up into Unraid with your disks, etc.. If you were running in ESXi you probably passed through the disks for the array so those will just appear. There really shouldn't be anything you need to do.

This is exactly what I needed. Thank you! It works perfectly and I can boot from both from the menu. The 2nd USB isn't licensed but that's fine.. Primarily I wanted to ensure I could boot from either in the event of a failure and no remote hands are available to swap the USBs.. If that happens I'll go through the license transfer process. Thanks again!

Hi All I recently had a USB drive die which caused a problem since my server is remote and not in my home. It just so happened where the server is located, there was nobody home for 3 days so my server was completely offline (I have remote access to the IPMI, but you obv can't replug a usb!). I replaced the USBs and now have 2 of them that are identical. My goal was to boot with the primary while having the secondary one plugged in. However I'm running into a problem. UnRAID seems to mount BOTH USBs to /boot on boot up. I'd like to have both mounted (backup using unassigned devices) so I can regulary rsync the primary to the secondary in the event I have another failure. I figure Unraid is mounting both because they are identical and have the same volume Label (UNRAID) - anyone know how I can accomplish what I'm out to accomplish? Thanks!

Hey, Not sure if I'm the only one, but using an Intel 10th Gen (i9-10900) and running `intel_gpu_top` results in an error: root@Tower:~# intel_gpu_top Failed to detect engines! (No such file or directory) (Kernel 4.16 or newer is required for i915 PMU support.) Running 6.9.1. The iGPU works as Plex can HW transcode (so can ffmpeg) and the intel_gpu_top command runs fine if I reboot my system with the Ubuntu SSD plugged in (ruling out a bios issue). Any ideas? It's definitely unraid related, but who knows with what.

I think the point is most would be upset having to need an additional 400MB of RAM just for a driver they'll never use. sure it's 100MB when on the USB but when it's extracted at boot and stored directly into RAM, it's using 400. That's a lot.