birdsofprey02

Closing this out and marking resolved for archive. I had thousands and thousands of memtest errors. Unfortunately, my memory banks are under the CPU heatsink/fan, so its a pain to narrow down the culprit. Ended up buying 4 new banks. Also bought all new breakout cables and added two nvme drives for fun. Not sure if this was a normal course of action, but my 9211-8i HBA card had really old firmware/bios installed. Upgraded that to the latest I could find.

Thank you. I have 4 sticks of 16GB DDR 3600 ram = 64GB. Just started memtest and within 10 minutes have 5000+ errors. Is it worth narrowing down which DIMM or should I just replace them all? I'll also replace all the SAS breakout cables at the same time.

Looking to resolve a potential hardware issue, just not sure which device... I'm struggling between symptoms and root cause. I've had a few lockups over the past 2-3 weeks, created a diagnostics file below, but inside the zip, I also included the full log since Oct 11th. On Oct 11th, clearly something was locking up and having an issue. It ran smooth for a day or two and then this morning (10/17/2025) I woke up to a system freeze. I definitely have a faulty USB backup enclosure that I decided to reformat and pre-clear, and the lockup happened during pre-clear. I'm ready to abandon the USB, but wanted to find root cause. The "old" USB drive is indicated as STATUS_Backup_Old (spelling error for name of server STRATUS). Theres definitely suspicious kernel errors last night and this morning. Also noted, last week, I had numerous BTRFS errors with my Docker image so I moved to directory on the ZFS pool (SSDs) and switched to Overlay2. I don't think I have the logs go back that far as they weren't properly being written to a directory for sustainment. stratus-diagnostics-20251017-0712.zip

Rebooted regular mode and continued to see messages. <before I posted this forum> I rebooted in safe mode and the messages did not occur while in safe mode. I rebooted back to normal mode again and currently not seeing new invalid .page format log messages. Fixed itself? OR did rebooting in safe mode and back to regular mode iron out an issue?

Diag attached. It seems like the error is only appearing when I'm actively in the GUI. stratus-diagnostics-20250430-1610.zip

Had an issue earlier today where the webGUI wasn't showing drives or dynamic content (like date/time/CPU usage, etc.) Saw many posts recommending a reboot or just a restart of nginx. A full reboot didn't help. The GUI would eventually load the content after waiting a minute or two. I removed the unRAID Connect Plugin and all is well again. Content is showing quicky and as expected. When figuring out what was wrong, I received hundreds and hundreds of the following error: Apr 29 21:02:33 <servername> webgui: Invalid .page format: webGui/Notifications.page That error existed before I removed the Connect plugin, and has persisted after the plugin. If I click the notifications bell (remember I have unRaid Connect removed), and look at my historical notifications, it looks like every one is there from 2019 to today, I guess I never delete them. How can I fix the repeating error and is this all related to my issues with Connect?

I have all the same symptoms. On 7.0.1, don't know when it stopped working, but it used to work. I de-activated, re-activated, activated, removed the cert, had the cert re-created. Just says "failed to sync flash backup."

I recently tried using this unRAID template. First, I hit permission errors on the /loki WAL during initial startup. Noticed the image was 2 years old and changed it to the "latest" tag and re-pulled. Now during initial startup, I hit a few deprecated parameters from the local-config.yaml file suggested in the https://github.com/natcoso9955/unRAID-docker/blob/master/configs/loki/local-config.yaml file. failed parsing config: /etc/loki/local-config.yaml: yaml: unmarshal errors: line 18: field max_transfer_retries not found in type ingester.Config line 38: field enforce_metric_name not found in type validation.plain line 43: field max_look_back_period not found in type config.ChunkStoreConfig. Use `-config.expand-env=true` flag if you want to expand environment variables in your config file I researched each one and remediated. Now I'm hitting a schema validation error that says I am using schema v11 and need to upgrade to v13 and then several other field issues. With over 1,000,000,000 downloads on this, I feel like this is a me problem. Whats the best way forward to get a new setup rolling?

I ended up taking the "new" usb disk and loading it with stock unRAID OS, then copied over the /config folder. The system booted just fine. Since I didn't think the original usb disk was bad and I didn't want to blacklist a good usb stick with a new key<>uuid pair, I re-loaded stock OS on my original usb, copied the /config there too and it booted just fine. The only thing I'm noticing so far is that my rclone config didn't keep. Outside of that, seems like we're all good now. Thanks for leading me on a path.

Update: I grabbed a new USB stick (sandisk cruzer 16gb usb2.0), same type/brand as my existing unRAID usb. - Installed a vanilla clean install of unRAID onto USB via unRAID USB creator and I was able to get into the syslinux loader (great!) - Used same USB stick from previous step and used unRAID USB creator to make a USB from my connect flash backup and it halts at mobo splash again I don't think its a bad USB, but something on my original usb AND the backup thats causing this. If I removed the - from EFI- folder on the backup, do I need to run "make bootable" afterwards?

without the unRAID usb plugged in, It continues to post and enters BIOS. I’ve tried an alternate OS on a usb stick, and that launches as well. It’s not liking something on my particular unRAID stick.

I had been running an old supermicro motherboard X9SCL and E3 1230 processor for about 5-6 years and decided to upgrade this week. New system is all put together but I can't get unRAID to boot. The motherboard recognizes the UEFI SanDisk but as soon as I proceed from bios, it just hangs at a Aorus splash screen. I pulled a few PCI cards out (extra GPU and my HBA card) and no difference. Gigabyte Aorus Z690 Elite AX DDR4 flashed to latest Dec 2023 bios Intel i5-13500 64GB DDR4 ram - I created an Ubuntu24 install USB and it launched into grub with no issues and GUI worked fine - My unRAID usb had EFI~ folder and I changed it to EFI - I noticed there is a file on the USB (at the top level) called syslinux.cfg~ and it has a ~ tilda after it. I don't see this on the generated backup file, just on my good USB stick. On the backup, I only see this in a folder called syslinux and it has no tilda. Various settings I've tried - Platform Power Management enabled or disabled with Native ASPM enabled - Internal graphics enabled IGFX - SPD Write DISABLE - TRUE - Legacy USB support - enabled - XHCI Hand-off - enabled? - USB Mass storage driver support - enabled - Port 60/64 emulation - enabled? - Enable VMD Controller - disabled? - Sata Controllers - Enabled -Agressive LPM support - disabled - Intel Platform Trust Technology PTT - enabled -VT-d Enabled -Trusted Computing - Security Device Support ENabled -Secure Boot - disabled - Security Option - Setup? no idea - Boot Option #1 - UEFI SanDisk, Partition 1 (SanDisk) - FastBoot - tried both Disabled and enabled - Windows 10 Features - OtherOS - CSM Support - disabled Not really sure where to go from here.

Out of Memory Error popped up last night, never seen one before. Haven't noticed any degradation or killed processes. Uptime of 45 days... time for a reboot? stratus-diagnostics-20240526-0713.zip

Thankful I saw this message thread. I have been dealing with macvlan traces for 2 weeks now and finally had some time to get logs situated and written to a share. Found this, this morning: Dec 4 09:05:32 stratus kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Dec 4 09:05:32 stratus kernel: process_one_work+0x1ab/0x295 Dec 4 09:05:32 stratus kernel: worker_thread+0x18b/0x244 Crashed right after. I just switched to ipvlan moments ago, but I did NOT reboot until I just saw this thread. Hope this works now!

I have multiple vLANs setup on my unRAID server. Over 30 containers and none of them are running on the same IP as unRAID except maybe the Cloudflare Tunnel container. I don't think there's a requirement anywhere that docker containers have to run on the same IP as the host. The containers can all still talk to each other.