-
Unraid Pro 7.1.4 GUI keeps eventually crashing
@JorgeB This is what the output was. I understand the rootfs is full....but what is it being full from? I was on the machine less than two hours ago and everything was fine. The Dockers are running as normal.
-
Unraid Pro 7.1.4 GUI keeps eventually crashing
Filesystem Size Used Avail Use% Mounted on rootfs 48G 48G 0 100% / tmpfs 128M 2.5M 126M 2% /run /dev/sda1 29G 2.5G 27G 9% /boot overlay 48G 48G 0 100% /usr overlay 48G 48G 0 100% /lib tmpfs 128M 34M 95M 26% /var/log devtmpfs 8.0M 0 8.0M 0% /dev tmpfs 48G 0 48G 0% /dev/shm tmpfs 1.0M 0 1.0M 0% /mnt/disks tmpfs 1.0M 0 1.0M 0% /mnt/remotes tmpfs 1.0M 0 1.0M 0% /mnt/addons tmpfs 1.0M 0 1.0M 0% /mnt/rootshare /dev/md2p1 13T 6.1T 6.7T 48% /mnt/disk2 /dev/md3p1 15T 7.0T 7.6T 49% /mnt/disk3 /dev/md4p1 17T 8.8T 7.7T 54% /mnt/disk4 /dev/md5p1 17T 9.8T 6.6T 60% /mnt/disk5 /dev/md6p1 17T 8.7T 7.8T 53% /mnt/disk6 /dev/md7p1 19T 11T 7.8T 58% /mnt/disk7 /dev/nvme0n1p1 954G 121G 828G 13% /mnt/cache /dev/sdd1 1.9T 498G 1.4T 27% /mnt/virtuals shfs 95T 51T 44T 54% /mnt/user0 shfs 95T 51T 44T 54% /mnt/user /dev/loop2 275G 47G 229G 17% /var/lib/docker /dev/loop3 128G 6.1M 126G 1% /etc/libvirt VIRTCRB***CAL:/mnt/user/data 37T 2.8T 34T 8% /mnt/remotes/VIRTCRBUNRAID_data overlay 275G 47G 229G 17% /var/lib/docker/overlay2/31992f5285ae***d611a6ca759add3cf572a2cd46c87a6eda0741ca509399/merged overlay 275G 47G 229G 17% /var/lib/docker/overlay2/170fd7e4c62***39595499e5c452969c7e8516c850d96405f3fe650c0efead/merged overlay 275G 47G 229G 17% /var/lib/docker/overlay2/b9650a***ce3c55bf1d453281da4b2e7d42316932d8f6a6b11682d7e633b8/merged overlay 275G 47G 229G 17% /var/lib/docker/overlay2/eb***3b044b89d80f1c548563b4dab0847e7000cef69217cbe1bcf27/merged overlay 275G 47G 229G 17% /var/lib/docker/overlay2/b***8d970ed003ef89eceb42fff9f86b7f76135fc5116f8c04fe03408b56/merged overlay 275G 47G 229G 17% /var/lib/docker/overlay2/ae***11e9932328a55ab7702a974b0666e57e450d2ba5f68c910aaa757a0/merged overlay 275G 47G 229G 17% /var/lib/docker/overlay2/1***d44489b18c15dd06ac65ca82f3b25da75a082eaf0aa232ee46a0/merged overlay 275G 47G 229G 17% /var/lib/docker/overl***6a3a984bc6f63c1c0a076135fdbc3ce77eade2ea401ceb7e0cfd21c601d/merged overlay 275G 47G 229G 17% /var/lib/docker/over***7ead61decb13f3dd031a56ec3ea0713c6e9ef94126edac098de3b407/merged overlay 275G 47G 229G 17% /var/lib/docker/over***4fe502b65ab806626c8fbc0a9b0432dee63f3ffb19d2d7c5645990246d98/merged overlay 275G 47G 229G 17% /var/lib/docker/overlay2/d63***30fa6c8dd1973443514b44fb75f611ffb9b86e3e1220f70417a3f/merged overlay 275G 47G 229G 17% /var/lib/docker/overla***efee140a1681b6ae8f047e5005569392ddcdb822094b1fbe9e8e13577b/merged overlay 275G 47G 229G 17% /var/lib/docker/over***a2518e31b8bd8162f10dcd2112e3025ad9bd34c7f7eee79a107be404/merged overlay 275G 47G 229G 17% /var/lib/docker/overl***29404f5aa8c37495d221c14f9637129f73411dd5bbcf29fb5d14c027/merged overlay 275G 47G 229G 17% /var/lib/docker/overl***f69cacdb0ad1dc26f327a2b948edc117732c960921f4dad38ea6a2c61/merged overlay 275G 47G 229G 17% /var/lib/docker/over***8959fb91a3b1b8ba8e4792847e999877ee5bae0511ad668ac334245bce8abc/merged overlay 275G 47G 229G 17% /var/lib/docker/overl***e13fc0b72de1b75fe152eff80fc38b4c93280fb6d929fdcda90dd8b9c8ace0f/merged overlay 275G 47G 229G 17% /var/lib/docker/overla***d3292791a0ba43c797d582afd701467210d286f44f2ceac0e156ba0/merged overlay 275G 47G 229G 17% /var/lib/docker/overlay***32d4d43e90ea8ccced41caba25a256c9cfc66fb98669534fe534562aafb167fd/merged overlay 275G 47G 229G 17% /var/lib/docker/overl***e6bf82012416932877963de689a381ba457abba32cfcc1689800267dd12/merged overlay 275G 47G 229G 17% /var/lib/docker/overlay***bab91334919921e34acc4817694e1fd08523be6299d33dc412a70613d/merged overlay 275G 47G 229G 17% /var/lib/docker/overlay***72bbca6ed3d1df1fb3bee52e72291e501d0b96847f8a71711e11dec3918e3/merged overlay 275G 47G 229G 17% /var/lib/docker/overla***36f749ba2f4bdad1e35577bfa9e298b373adaa56cb7d93a9d06d0d46/merged overlay 275G 47G 229G 17% /var/lib/docker/overla***d894eec9739158288022b81c55a54172b9da8c835d6feb9835490f4ca89ac3/merged overlay 275G 47G 229G 17% /var/lib/docker/overla***97526b560ac6faf5aab31aba526ec612b67d714187ffe49aba3136fdc5/merged overlay 275G 47G 229G 17% /var/lib/docker/overla***99da6b54669d2008cdf823c9248686b75d505d5dea5ef0f0dc8f6dd917a1/merged overlay 275G 47G 229G 17% /var/lib/docker/ove****3310b48fb441ed5e00e820309b988e876c106670218ca8b0d96be1d5c92d3/merged overlay 275G 47G 229G 17% /var/lib/docker/overl****9cea8b252968a4b175c9282824b72f498ea98ca37267450f5d719bcd6/merged tmpfs 9.5G 0 9.5G 0% /run/user/0
-
Unraid Pro 7.1.4 GUI keeps eventually crashing
Will do. A matter of time.
-
Coreybau started following [PLUGIN] GPU Statistics and Unraid Pro 7.1.4 GUI keeps eventually crashing
-
Unraid Pro 7.1.4 GUI keeps eventually crashing
The actual filetower-diagnostics-20250922-1903.ziptower-diagnostics-20250922-1903.zip
-
Unraid Pro 7.1.4 GUI keeps eventually crashing
Every couple of days or so the GUI stops working and the only thing that helps is restarting the server completely. After the restart everything is normal for a day or three but it always stops working. tower-diagnostics-20250922-1903.zip
-
[PLUGIN] GPU Statistics
How do I upgrade the kernel if I am already on the latest version of Unraid?
-
[PLUGIN] GPU Statistics
crbunraid-diagnostics-20250312-1155.zip
-
[PLUGIN] GPU Statistics
-
[PLUGIN] GPU Statistics
So I create the file /boot/config/modprobe.d/xe.conf usinf nano because the file isn't there. And all I add to the file is options xe force_probe=e20b Just create the file and all I have in it is the above? Then run modprobe -C /boot/config/modprobe.d/xe.conf xe Well I got a missing parameter error, looked at the -h and changed the -C to -c. Well then a whole lot of lines came out ending with: alias symbol:zrl_add_impl zfs alias symbol:zrl_remove zfs alias symbol:zs_compact zsmalloc alias symbol:zs_create_pool zsmalloc alias symbol:zs_destroy_pool zsmalloc alias symbol:zs_free zsmalloc alias symbol:zs_get_total_pages zsmalloc alias symbol:zs_huge_class_size zsmalloc alias symbol:zs_lookup_class_index zsmalloc alias symbol:zs_malloc zsmalloc alias symbol:zs_map_object zsmalloc alias symbol:zs_pool_stats zsmalloc alias symbol:zs_unmap_object zsmalloc But I am still getting: Going to try a reboot. Back in a little while.
-
[PLUGIN] GPU Statistics
I am unfamiliar with what that is. So when in doubt type it in a console. I got what did look more familiar as a list of IMMOU. So I guess you are looking for this: 06:02.0 PCI bridge: Intel Corporation Device e2f1 Subsystem: Intel Corporation Device 0000 Kernel driver in use: pcieport 07:00.0 VGA compatible controller: Intel Corporation Battlemage G21 [Arc B580] Subsystem: Device 172f:4215 08:00.0 Audio device: Intel Corporation Device e2f7 Subsystem: Device 172f:4215 Please let me know what you need.
-
[PLUGIN] GPU Statistics
I just bought an Intel B580 Battlemage and am trying to get it recognized by Plex and Unraid as well. This is the cards I have in my server now. The GTX 1050 is just for GUI on a monitor purposes. However it is the only one Plex shows. I followed the rabbit hole and I am on Unraid 7.1 and I installed the 2025.03.12 version of the GPU Statistics But nothing is working for the Arc B580. I saw previously a call for volunteers. Reporting for duty as I need help.
-
My /var/log is getting full
Eventually I bought new higher capacity ECC ram and used only half the slots. A poor expensive Christmas present but the problems seem to go away for now.
-
My /var/log is getting full
I tried that but this is an old HP z820 and I got 16 slots. I would remove one and another slot would show failing. I replace it and remove that RDIMM and a different slot from the previous 2 would show failing. I finally removed everything and started putting them in 1 by 1 and a RDIMM that was fine before says it is failing. Something different goes bad with every restart unless I make no changes then the same thing goes bad.
-
My /var/log is getting full
I looked and keeps repeating Socket 1: CHANNEL: ? DIMM: ?
-
My /var/log is getting full
Thank you! I looked, and it was a sea of red. But is there a way to tell which one is the bad one without taking them all out and constantly restarting the machine with only one stick in there at a time? Can I see which is the bad one?
Coreybau
Members
-
Joined
-
Last visited