Stokkes

Members
  • Posts

    361
  • Joined

  • Last visited

Converted

  • Gender
    Male
  • Location
    Ottawa

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Stokkes's Achievements

Contributor

Contributor (5/14)

5

Reputation

  1. 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.
  2. 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!
  3. 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.
  4. Hello, I think I stumbled onto a major bug in 6.12.3. I upgraded tonight (was never on the rc releases so can't speak to that), just like I did any other upgrade. Upon rebooting, my server had no IP address at all (I did not disable IPv6 in my /boot/config/go file either). Reverting back to 6.12.2 fixes the issue. If I re-attempt the upgrade, it breaks again, so this is 100% reproducible on my system. I'm using this NIC (Intel 2.5GbE) `04:00.0 Ethernet controller: Intel Corporation Ethernet Controller I225-LM (rev 02)` EDIT: Included two diagnostics, one full-boot on 6.12.3 and one without WebUI/plugins Thanks for looking at this urgently. tower-diagnostics-20230716-0118.zip tower-diagnostics-20230716-0115.zip
  5. 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!
  6. Omg so sorry! Thank you that's awesome. Looking forward to the release!
  7. 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!
  8. 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.
  9. 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.
  10. 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
  11. 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
  12. 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!
  13. 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
  14. 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.
  15. ❯ grep -Pom1 'model name\s+:\s*\K.+' /proc/cpuinfo Wed 25 May 08:45:03 Intel(R) Core(TM) i9-10900 CPU @ 2.80GHz