-
-
Multiple errors in log and now I can't start Docker Unraid VER. 6.12.13
I have been having Cacher errors copied below. They happen every night around the time my app data backups start. As of last night docker went down as well and I can't get it to restart. any suggestions appreciated. This is my first time posting here I have included my logs below and have now yet rebooted. Dec 29 05:00:30 infinity kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 727, gen 0 Dec 29 05:00:30 infinity kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 47898145 off 6173073408 csum 0x200cdc3e expected csum 0x20947d4d mirror 2 Dec 29 05:00:30 infinity kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme2n1p1 errs: wr 0, rd 0, flush 0, corrupt 1035, gen 0 infinity-diagnostics-20241229-1120.zip
-
Logs Filling up every few days
I am able to view the log size on dashboard under they system section. for me the system log would climb to 100% and then things would get flaky. plex would open and crash etc. at first i would just reboot and the log would clear and things would be fine until it spiked to 100 again.
-
Logs Filling up every few days
https://reddit.com/r/unRAID/s/FLHGvl0oME i wonder if this is contributing to my problem i so often leave tabs open pointing to unraid hmm. Does anyone know if this is still a problem
-
Logs Filling up every few days
hmm that is my laptop. i have a bad habit of leaving tabs open so that could have been hitting the webgui of unraid. but I realized that the other day and closed all the tabs and the logs have continued to fill. Last night i deleted /var/log/syslog.1 and .2 in order to make plex usable and this morning the logs are full again
-
Logs Filling up every few days
Hey everyone. Fairly new at this. I have been running unraid for a few months and have been loving it. And I have been having an issue with my logs filling up. wondered if someone could take a look at my log file. It has cleared on a reboot but I guess that is expected. Anyway thanks for any advice. J infinity-diagnostics-20231014-0432.zip
-
Very slow parity check
I am running a parity check in preparation to replace a smaller drive with a larger. The newer drive is running a pre clear and I kicked of a Parity check. I have all my app data on the NVME cache... with docker running I had 7-10 MB/sec with docker off more reasonable at 75 butt....... I noticed this in my log: May 31 17:30:37 infinity emhttpd: spinning down /dev/sdd May 31 17:30:41 infinity emhttpd: read SMART /dev/sdd May 31 17:31:15 infinity kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4 May 31 17:31:15 infinity kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) May 31 17:31:15 infinity kernel: pcieport 0000:00:1b.4: device [8086:7ac4] error status/mask=00000001/00002000 May 31 17:31:15 infinity kernel: pcieport 0000:00:1b.4: [ 0] RxErr May 31 17:31:15 infinity kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4 May 31 17:31:15 infinity kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) May 31 17:31:15 infinity kernel: pcieport 0000:00:1b.4: device [8086:7ac4] error status/mask=00000001/00002000 May 31 17:31:15 infinity kernel: pcieport 0000:00:1b.4: [ 0] RxErr May 31 17:31:15 infinity kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4 May 31 17:31:15 infinity kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) May 31 17:31:15 infinity kernel: pcieport 0000:00:1b.4: device [8086:7ac4] error status/mask=00000001/00002000 May 31 17:31:15 infinity kernel: pcieport 0000:00:1b.4: [ 0] RxErr I will attach the diagnostics zip file as well if I can figure it out I am very new to unraid thanks for any help J infinity-diagnostics-20230531-1727.zip
jbrody
Members
-
Joined
-
Last visited