Unbugspray

Ok, so I deleted the /var/log/log1 file that was filling up my log, however, it just gets filled again in less than a day, which means there is some underlying problem that I am not seeing. Went to the logs and I have this as a recurring May 16 13:45:22 myserver0 kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x4020000000-0x402fffffff 64bit pref] Any suggestions? Thanks!

Good day! I have been having some issues with my server after my last reboot, my win10 VM is not booting anymore, gives the error "Unable to write to file /var/log/libvirt/qemu/Windows 10.log: No space left on device". Additionally fix common problems is reporting "/var/log is getting full (currently 100 % used)", I went into the actual folder and I don't any big logs taking space, I also went through all the server and everything else seems to be working. I attach my diagnostics. Any help is appreciated. Thanks! myserver0-diagnostics-20230506-1315.zip

Sorry for the late reply, I got sick and had to drop this for a while. Couple of questions before I run the command directly if you don't mind. If the parity gets invalidated does that mean I lose all my data? Do I have to run this in maintenance mode? Thanks for all the help, I really appreciate it!

First question: Those were the disks I had lying around, is the read speed also dictated by the parity drive? I did a full disconnection of everything, replaced all the SATA cables with new ones and did a memtest. All comes green, cables are just out of the box and I purposefully used a different port to connect the failing drive, did check after the reboot and still the same issue. I wonder if the block data just got corrupted somehow, is there a way to shrink the array without losing any information? Then I could re-add the disk as a new disk later.

I did it from the WebUI, no shell involved here. I attach my diagnostics file. I appreciate the help, thanks! server-diagnostics-20221223-1503.zip

So I have been running unraid for almost a year now, my configuration is as follows 1 SATA Parity 4 SATA Capacity 1 NVME Cache 1 SATA Passthrough to a Windows machine. I also have a windows VM with a pass-through Nvidia3070 that I use as a remote gaming computer for my living room, office and tablets. Recently I started using Jellyfin and bought a second Nvidia3060 card to use as an encoding card for it. When I installed it, after the boot one of my HDs, came with Unmountable: Wrong or no file system, didn't change anything in the configuration of the HDs. I ran the XFS check and it came back with Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... ................................................................(dots continue for like 1000 lines, removing them)...........................................................................................................................................................................found candidate secondary superblock... unable to verify superblock, continuing... ...................................................(dots continue for like 1000 lines, removing them)........................................................Sorry, could not find valid secondary superblock Exiting now. Since it didn't come back with any possible fixes, I decided to remove the GPU and see if that helped, no dice, even after removing the GPU, still came back as Unmountable: Wrong or no file system. I am honestly at a loss here, I read that I should not under any circumstance format the hard drive, but don't really know what else I could do to recover it, I have a lot of data in here and around 20 different dockers with a lot of configuration behind them. Thanks!