Sudden and unexpected web ui accessibility issues since i upgraded to 7.0.1
I would be able to ping but i can't access the web ui or even run "powerdown -r" from and ssh connection, to reboot. that did nothing. i would have to force reboot by holding down the power button on the computer. this has happend at least 10 times inside a week. I've attached the diagnostic i pulled after the most recent reboot this morning, i didn't start docker/vm cause i was scared it would freeze up again.

agbireshome-diagnostics-20250307-0732.zip

The normal syslog starts over after every boot, enable the syslog server and post that after the next crash.

Wouldn't be a bad idea either to run memtest from the boot menu for at least a couple of passes.  

 

An unlikely but still possible issue if memtest passes is that you're running two sets of mismatched RAM.   (A-Data and Patriot).  The highest stability on memory comes from using matched sets and if not possible then ensuring that the CL timings match between the sets

Another incident. tried some commands from (selfhosters.net/commands/) to restart nginx/php. no luck. Syslogsyslog-10.10.50.5.logattached 

Took a peek at the logs.. looked like i'm having NTP issues. turned it off and set the time manually.. fingers crossed..hopefully someone can confirm if this is the source of my headaches

Mar  7 21:07:23 AgbiResHome kernel: zio pool=snow vdev=/dev/sdc1 error=5 type=2 offset=120461783040 size=131072 flags=1572992
Mar  7 21:07:23 AgbiResHome kernel: zio pool=snow vdev=/dev/sdc1 error=5 type=2 offset=120467456000 size=131072 flags=1572992
Mar  7 21:07:23 AgbiResHome kernel: WARNING: Pool 'snow' has encountered an uncorrectable I/O failure and has been suspended.
Mar  7 21:07:23 AgbiResHome kernel: 
Mar  7 21:07:23 AgbiResHome kernel: WARNING: Pool 'snow' has encountered an uncorrectable I/O failure and has been suspended.

 

One of the snow pool devices dropped offline and the pool was suspended, once this happens, you will need to force a reboot, you cannot read/write from that pool, not even unmount it.

I have now removed the sdc drive from the pool. hopefully this will fix my issues. i had already downgraded back to 7.0 thinking the new 7.0.1 was the cause but it still crashed this morning. now that i have take out the pool drive i hope it doesn't crash again. this is so stressful.

Before removing the device, you can try replacing/swapping cables, in case that is the issue.

didn't see your message on time @JorgeB, already removed the disk from the pool. uptime 12hrs.8mins, no issues so far. 

Another crash. had to reboot.. the syslog file is over 1gb but grabbed the last few lines where i was saw a change.

 

Mar 11 10:25:10 AgbiResHome move: move: /mnt/goldmember/zfs_backups_appdata/snow_appdata/Plex-Meta-Manager/config/overlays/TV Shows Original Posters/21320.jpg Success

Mar 11 10:25:10 AgbiResHome move: move: /mnt/goldmember/zfs_backups_appdata/snow_appdata/Plex-Meta-Manager/config/overlays/TV Shows Original Posters/21487.jpg Success

Mar 11 10:25:11 AgbiResHome move: move: /mnt/goldmember/zfs_backups_appdata/snow_appdata/Plex-Meta-Manager/config/overlays/TV Shows Original Posters/20912.jpg Success

Mar 11 10:25:11 AgbiResHome move: move: /mnt/goldmember/zfs_backups_appdata/snow_appdata/Plex-Meta-Manager/config/overlays/TV Shows Original Posters/20560.jpg Success

Mar 11 10:25:11 AgbiResHome move: move: /mnt/goldmember/zfs_backups_appdata/snow_appdata/Plex-Meta-Manager/config/overlays/TV Shows Original Posters/17529.jpg Success

Mar 11 10:25:11 AgbiResHome move: create_parent: /mnt/goldmember/zfs_backups_system/snow_system error: Device or resource busy

Mar 11 10:25:11 AgbiResHome move: move: /mnt/goldmember/zfs_backups_system/snow_system/docker/docker.img Device or resource busy

Mar 11 10:25:12 AgbiResHome move: move: /mnt/goldmember/zfs_backups_system/snow_system/libvirt/libvirt.img Success

Mar 11 10:25:12 AgbiResHome move: move: /mnt/goldmember/zfs_backups_system/snow_system/remoteviewer/rv10.10.50.5.0.vv Success

Mar 11 10:25:12 AgbiResHome move: move: /mnt/goldmember/zfs_backups_system/snow_system/remoteviewer/rvcyberrunner.onlinetrebor.uk..rdp Success

Mar 11 10:25:12 AgbiResHome move: move: /mnt/goldmember/zfs_backups_system/snow_system/remoteviewer/rv10.10.50.5.5900.vv Success

Mar 11 10:25:12 AgbiResHome move: move: /mnt/goldmember/zfs_backups_system/snow_system/remoteviewer/rvcyberrunner.onlinetrebor.uk.5900.vv Success

Mar 11 10:25:12 AgbiResHome move: move: /mnt/goldmember/zfs_backups_system/snow_system/remoteviewer/rv10.10.50.5..rdp Success

Mar 11 10:25:12 AgbiResHome move: move: /mnt/goldmember/zfs_backups_system/snow_system/sanoid/snow_system/sanoid.defaults.conf Success

Mar 11 10:25:13 AgbiResHome move: move: /mnt/goldmember/zfs_backups_system/snow_system/sanoid/snow_system/sanoid.conf Success

Mar 11 10:25:13 AgbiResHome move: move: /mnt/goldmember/zfs_backups_system/snow_system/sanoid/snow_appdata/sanoid.defaults.conf Success

Mar 11 10:25:13 AgbiResHome move: move: /mnt/goldmember/zfs_backups_system/snow_system/sanoid/snow_appdata/sanoid.conf Success

Mar 11 10:25:13 AgbiResHome move: mover: finished

Mar 11 11:10:00 AgbiResHome rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="22672" x-info="https://www.rsyslog.com"] rsyslogd was HUPed

Mar 11 18:30:59 AgbiResHome rc.rsyslogd: Syslog server daemon...  Started.

Mar 11 18:30:59 AgbiResHome root: Delaying execution of fix common problems scan for 10 minutessyslog-10.10.50.5.log

Mar 11 18:30:59 AgbiResHome unassigned.devices: Mounting 'Auto Mount' Devices...

Mar 11 18:30:59 AgbiResHome emhttpd: Starting services...

Mar 11 18:31:00 AgbiResHome emhttpd: shcmd (225): /etc/rc.d/rc.samba reload

Mar 11 18:31:00 AgbiResHome rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="28893" x-info="https://www.rsyslog.com"] start

Mar 11 18:31:00 AgbiResHome emhttpd: shcmd (229): /etc/rc.d/rc.avahidaemon reload

Mar 11 18:31:00 AgbiResHome unassigned.devices: Updating share settings...

Mar 11 18:31:00 AgbiResHome unassigned.devices: Share settings updated.

Mar 11 18:31:00 AgbiResHome emhttpd: shcmd (240): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 60

Mar 11 18:31:01 AgbiResHome kernel: loop2: detected capacity change from 0 to 125829120

Mar 11 18:31:01 AgbiResHome kernel: BTRFS: device fsid 2f781bfc-3075-4a28-b459-d9ec481550a4 devid 1 transid 10763 /dev/loop2 scanned by mount (29563)

Mar 11 18:31:01 AgbiResHome kernel: BTRFS info (device loop2): first mount of filesystem 2f781bfc-3075-4a28-b459-d9ec481550a4

 

Unfortunately, there's nothing relevant logged.

I would say that's a relief cos i'm not going crazy.. so what do i do now? reboot twice a day till and update comes out?

You can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS and see if it still happens, if it doesn't start turning on the other services one by one, including the docker containers. 

Ahh! the age old process of Elimination.. i guess it can't be helped

@robertkmy Did you ever make any further headway on this?

I'm experiencing similar symptoms (WebUI goes down, have to perform a hard shutdown) and have just begun the process of collecting syslogs.

One pass of memtest came back clean (and half a dozen passes several weeks ago, before the server was more fully set up).
Looking for any other ideas of where to look based on others' experiences.

I have to same problem but i think its on my browser end and not with Unraid. After a while things slow down and the only way to fix it for me is to reboot my computer. After that everything is fast again for a while and then things repeat. I've tried different browsers, disabling extensions , firewall, etc. Nothing stands out in my logs either. So strange.

I backed up my docker container data, then nuked the docker img. Then nuked all plugins.. I doubled the docker img file size when creating a new one, rebooted then started adding everything back one by one .. stable for some time now . Never found the culprit.

Thank you both for your responses.

I've attempted a variety of potential fixes and may eventually open a new thread of my own to solicit advice if I don't work this out over the next couple days...

@mhaaland

For me, it seems to extend beyond just a browser issue--some kind of actual hardware crash/freeze.

I'm unable to SSH into the system, either, and when I finally plugged in a monitor and keyboard, I found I was unable to interact with the command line on the actual system when the next crash came around.

@robertkmy

I'll try removing the docker image, redownloading containers, and removing/reinstalling plugins, too.

Thanks for the ideas of other avenues to look into.

---

For what it's worth to future readers, my diagnosis journey has included the following:

• Turned off Docker, VMs, SMB.

  • For me, still crashed with all of these turned off, so I don't think they're an issue.

  • Haven't yet tried aggressively removing plugins as @robertkmy suggested, nor of returning system settings to defaults.

• memtest86, once with a single pass, and once overnight for 6 passes.

  • Still experienced several crashes in the hours/days following these tests.

  • Removed and reseated RAM before the long, overnight test.

  • I don't feel like I've ruled bad RAM out yet and will consider even longer, 24+ hour runs if necessary.

  • Also haven't yet tried running the server on one stick of RAM and then the other and seeing if crashes appear in either or both scenarios.

• Changed docker network from macvlan to ipvlan.

  • Still crashed after the change. Probably wasn't necessary, but also innocuous to my current setup. May eventually go back to macvlan as the need arises.

• Reseated PSU cables.

  • Have yet to try reseating other cables (SATA, etc.), or to try removing the system from its case entirely. I don't remember experiencing any crashes before this mobo was mounted in its case and I had all the cables routed, and I believe I had the system running like that for several long, uninterrupted periods.

  • Is something in the case shorting the mobo? Did I damage something during the move? I don't think so, but I haven't ruled it out yet.

• Removed an HDD that hadn't been connected before the crashes became apparent.

  • Continued to crash even after this device was unattached.

• Moved to a new USB stick (by using a backup .zip/copying contents of old stick)**

  • To be honest, the stick I started on was a junker, just to give this system a Trial license while moving data, with the end goal of swapping it to a better stick that was already tied to a license.

  • Still crashed once on the new stick, so went a step further and rebuilt boot drive from scratch with Unraid USB Creator and copied over only the /config/ folder from the old stick.

• Took a look at scheduled events on the server (Mover, User Scripts) to see if crashes lined up or were occurring at any predictable time of day/event.

  • Unresolved, but leaning toward the likelihood that crashes are happening at random times.

• Began capturing syslogs on USB and a local rsyslog server.

• Changed Unraid WebUI theme back to default (one of my syslogs was showing some weird style.css errors)

  • Discovered a Reddit thread with a user reporting similar syslog errors. User followed up to say that in their case, it ultimately came down to a corrupt USB stick.

  • In my case, no other suspicious syslog entries, at least that I can spot.

• Stress tested with Prime95 for a couple hours

  • No crashes during the test, so either I've resolved it in one of the previous steps, or...?

  • Will consider running Prime95 overnight if I experience yet another crash.

And some other avenues yet to explore:

• Haven't yet tried running the server in Safe Mode to see if a crash still occurs in that condition.

• Considering pulling out an old nvme drive that I put in there to act as a write cache.

  • Before the crashes began occurring, I had that disk set up as its own pool but with no data on it.

• Hunting around in BIOS settings/returning BIOS to factory defaults.

I'm currently at about 12 hours with no crash, but I've had windows of stability that long before, so nothing conclusive yet.

Edit (Oct 2025):

Coming back to this for anyone who might stumble across it in the future.

My issue ultimately seemed to stem from corruption on the USB boot drive.

When I copied over the contents of the old boot drive to a new USB stick, the corrupted file was apparently copied over as-is, resulting in continued instability even when I was booting with the new USB stick.

A proper rebuild resolved the issue (I can't remember after which step I finally achieved stability, but it was either after I'd used the Unraid USB Creator tool and copied over only /config/ as noted in the post above, or after I performed an OS update within the Unraid interface, as 7.1.3 had recently been released).

Edited October 3, 2025Oct 3 by wabun