TreksterDK

That is actually my SSD Cache drive. Maybe I should just buy a new one. Recommandations for doing a switch of that? Backing up files etc.?

Ok. I added the unraid server ip. I hope this is enough for this purpose. Is there no way to look at the current diagnostics files (I uploaded) to figure out where the problem might be?, or is the syslogs a requirement for now to get anywhere? I ask because I don’t know

Ok. I don't know much about syslog servers to be honest. Any recommendations for a free syslog server for Windows that will be good enough for this situation? I get different result googling it, but am unsure what to choose. Setting this up, will allow me to disable the mirror feature to the Flash drive, right? (I would like to avoid unnecessary writes to that if I can avoid it)

My NVME (970 EVO Plus) is actually just an unassigned drive I use for various things - like Plex transcoding etc. My actual Cache drive is a Western Digital Blue drive (WDS500G2B0A) sitting on the onboard SATA controller. It's been running for 4 Years and 197 Days (According to Diskspeed). But yeah, it might be the problem.

Ok. I did this: "syslogs" share is on the cache drive (Even though that might be one of the problems 🤔, but it was recommended), but will be moved to array (secondary location)

Did you also have occasionally unresponsive interfaces and problems similar to what I described?

Ok. I will do that: Is that enough, and just hit Apply ("Backup" is a share)? There is no information in the logs tha hints at possible errors and solutions?

Hey everyone I have been dealing with persistent challenges in my Unraid setup, which includes multiple dockers and a couple of VMs. Currently, the VMs are intentionally shut down as I'm not actively using them, so I don't believe they are related to my issues. Typically, the server runs smoothly for about 1-2 weeks, but then it can suddenly become unresponsive. Issues range from the web interface being inaccessible to various other problems, such as certain dockers intermittently stopping with failed restart attempts. In some cases, I've also noticed "read-only file system" errors in some docker logs. In many instances, I had to perform a manual restart of the server by physically powering it off and then back on to restore it to a running state. Initially, I suspected a faulty cache disk (because of the read-only file system errors), but what confuses me here is that these issues seem to temporarily resolve after a reboot? Just today, a docker became unresponsive (Scripted), and attempts to stop it resulted in a "Server Error" popup (First time I have seen this). Following a community suggestion, I successfully stopped and force-updated the docker. However, attempting to restart it afterwards caused the web interface to become unresponsive. Fortunately, I had a console open and tried to shut down the server with the "powerdown" command, which did not work correctly (waited for 20 minutes-ish), leading to a forced server shutdown - once again. I have attached three diagnostics files, two from previous incidents (28th of November and 12th of December) and another from today. All files were created just after rebooting the server. As someone more comfortable with Windows than Linux, I have managed to maintain everything up until now. I'm reaching out to the community for assistance because my Linux skills are simply not advanced enough to interpret these diagnostic files. I need help identifying the root cause and finding a more permanent solution to these recurring problems. Any insights or guidance on what to look for would be greatly appreciated. Thank you nas-disk-diagnostics-20231222-1114.zip nas-disk-diagnostics-20231213-0619.zip nas-disk-diagnostics-20231128-1807.zip

I have the same issues. Had it a couple of times. I'm having the issue right now actually.

Worked! Thanx.

I get the error now

I have googled this topic for a while now, and also found a lot of information, but just not the final information that I was comfortable using. The problem is that I’m really not a Linux guy – far from it actually (I'm more of a Windows guy). I can use basic commands, update the OS (when needed), install stuff, and get going on basic things, like running a Minecraft server using MineOS (with guides and help) 😉. That was actually the main purpose of the VM which I created a long time ago (I know there is a docker for that now, but other stuff is also running on the server, so I would like to keep it, only extending the disc). But I can’t figure out how to extend the disk in the VM. I need some expertise help, guiding me in a simple understandable way (Like how space invader makes everything easy too undestand in his videos, for instance. Unfortunately he does not have a video on how to extend a Ubuntu Server disk, only Windows). Some details about the VM (I don’t know if it’s relevant, but here it is): Original Disk size: 20GB Updated size: 50GB Ubuntu Server: 18.04.4 LTS (Bionic Beaver) Machine: Q35-3.1 Bios: OVMF Primary vDisk location: Auto Primary vDisk Bus: VirtIO Some commands: fdisk –list Disk /dev/loop0: 110.8 MiB, 116178944 bytes, 226912 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes GPT PMBR size mismatch (41943039 != 104857599) will be corrected by w(rite). Disk /dev/vda: 50 GiB, 53687091200 bytes, 104857600 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 9E82BAD1-20A4-4CC3-8A21-E461E54CFF53 Device Start End Sectors Size Type /dev/vda1 2048 1050623 1048576 512M EFI System /dev/vda2 1050624 41940991 40890368 19.5G Linux filesystem fdisk /dev/vda2 Welcome to fdisk (util-linux 2.31.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. The old ext4 signature will be removed by a write command. Device does not contain a recognized partition table. Created a new DOS disklabel with disk identifier 0xfa79545c. Command (m for help): p Disk /dev/vda2: 19.5 GiB, 20935868416 bytes, 40890368 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xfa79545c So, it seems the system can see that there is 50GB of space. But the two partitions only use the original 20GB. How do I proceed from here? Please be specific, because - as I said my Linux skills are limited 😳 Thanks in advance! Trek

The case is without PSU. The option without PSU for that model was not available on partspicker. I know it is a boxed model, but they are really noisy those default coolers. That's why I initially thought to buy a new one. The case is only temporary I will get a bigger one later. It was the cheapest one i could find for now.

I selected this cooler because it seemed to fairly low noise. Not that i matters that much, but it would be nice not to have too much noise. I have switched to a "Cooler Master", but I might just spend the extra $ on the Noctua one in the end https://uk.pcpartpicker.com/list/79Z8TB

All very good points I have changed the build slightly: https://uk.pcpartpicker.com/list/73gLr6 It seems to be impossible to get the Fractal Design - Node 804 case for now. I may be able to get one - second hand - in about 2 weeks, so for now i will just buy the cheapest one i can get that fits the shelf where it will reside. I have upped the power supply a little, but it is a cheaper model though. What do you think? ...Allan