mkono87

Ran a few memtest passes and no errors but my system has crashed again. Here is the new logs. @fmp4m Just wanted to loop you in if ok. nas-diagnostics-20210919-1812.zip syslog.zip

No one replied to this problem and I gave up.

No, that was my next step I think. How long do you think it sufficient? Overnight?

It's crashed again. I will need to post another log when I get the chance. I'm totally lost at this point.

It did crash again and I finally got around to doing xfs_repair on my appdata drive. Seems to have fixed itself correctly. root@NAS:~# xfs_repair /dev/sdb1 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 bad CRC for inode 244937761 bad CRC for inode 244937761, will rewrite Bad atime nsec 2173239295 on inode 244937761, resetting to zero cleared inode 244937761 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 2 - agno = 3 - agno = 1 - agno = 0 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... done No lost and found folder created. So I guess at this point is reset the syslog and see what happens.

I realized that my bios was way out of date. I updated an its been running for 3 days so far. Im not out of the clear yet, but its a good sign. My app data drive appears to have a xfs corruption error so I need to repair that at some point too.

Will it probably throw the error notification again in the near future?

I did receive an error notification for the docker driver with an uncorrected 1 status. I did a smart test after it finished the parity check. (I know not related). I did get a successful smart extended test, is this not to be trusted in this case? Sent from my Mi 9T using Tapatalk

Yes this is what I have now. Just to let you know. My docker containers and vms are on their own separate drive. Yes its small but I have have vms atm. NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS loop0 7:0 0 13.5M 1 loop /lib/modules loop1 7:1 0 101.1M 1 loop /lib/firmware loop2 7:2 0 40G 0 loop /var/lib/docker/btrfs /var/lib/docker sda 8:0 1 7.3G 0 disk └─sda1 8:1 1 7.3G 0 part /boot sdc 8:32 0 223.6G 0 disk └─sdc1 8:33 0 223.6G 0 part /mnt/disks/docker-vm sdd 8:48 0 3.6T 0 disk └─sdd1 8:49 0 3.6T 0 part sde 8:64 0 3.6T 0 disk └─sde1 8:65 0 3.6T 0 part sdf 8:80 0 465.8G 0 disk └─sdf1 8:81 0 465.8G 0 part /mnt/cache sdg 8:96 0 3.6T 0 disk └─sdg1 8:97 0 3.6T 0 part sdh 8:112 0 3.6T 0 disk └─sdh1 8:113 0 3.6T 0 part md1 9:1 0 3.6T 0 md /mnt/disk1 md2 9:2 0 3.6T 0 md /mnt/disk2 md3 9:3 0 3.6T 0 md /mnt/disk3

Hmm, thats no good. I dont even see a sdb1 entry when using lsblk or ls /dev. Im not sure what that would be.

Okay I have no updated to the latest bios and attached the latest logs from when it went down yesterday. Please note: These logs are from before I updated the Bios. syslog.zip nas-diagnostics-20210908-1252.zip

Another question? Are you running my servers plugin?

I thought that's what I gave you or do you mean the entire log? I can get that uploaded later today.

Have you ran a memtest for a number of hours yet? That's one thing I still need to try. Im also running out of options. Edit: Sorry just realized that you did do a memtest.

Keep me updated. Im not home until tomorrow night to try it. Are you using the myservers plugin? Im curious if it started around that time it released. They did have issues with the api at first.

I made a post similar to this a few days ago. I have had issues for quite a while. I updated to rc1 the other day but it also crashed. I'm going to go back to 6.8.3 and see what happens. Sent from my Mi 9T using Tapatalk

Syslog to flash is on. This is where the log from that pastebin came from. Downgrsding I have not tried but I will give that a shot.

Anyone? I'm really stuck here and not sure what to do. Any help is appreciated.

ZanJhvkh.zip

nas-diagnostics-20210901-2203.zip nas-diagnostics-20210901-2203.zip

Been dealing with Unraid crashes for a while where there is no access to the gui nor ssh. I have no choice to hard reboot the machine. Sometimes it can be days, other times it can be months. I just cant seem to figure out the cause. This time I have been able to catch the logs closer to the time it happened. Do you see anything I should be aware of? https://pastebin.com/ZanJhvkh

For a few weeks I have been dealing with getting a 522 on most if not all of my self hosted services. There are a few times where it will work and then 1 minute later it will throw a 522 error and I cant figure out why. I am using Cloudflare Proxied and have been for a few months now. I am using the Swag (nginx) docker container on my Unraid system for years. I have seen in reports a week a so ago, CF did have issues with a bunch of 522 errors but has been marked as fixed. I really cant tell if this is a local or CF issue. If anyone can help me out with some good troubleshoot tips on how I can test this that would be great. My swag logs show nothing and not sure how to go about it. Thanks. Edit: I looked into fail2ban in the swag container and whitelisted the CF ip but still didnt work

Recently updated my server plugin so far so good. Hopefully that's it since it was showing an api error Sent from my Mi 9T using Tapatalk

I have unfortunately been dealing with this for months and cant figure it out. Every few days or sometimes weeks, Unraid will crash. The system still runs but I cant ping it, access the gui, ect. I have been running the log on the boot device to gather information. There seems to be a lot of kernel entries but I am not sure if this is a kernel panic. I have attached the logs. I haven't run a memtest or anything like that. If there was an issue with the boot drive, I would assume it would straight up crash. Any kind of help would be great apreciated, its driving me nuts. https://pastebin.com/6ebWN3jy This goes back about an hour before what looks to be where it crash. After is where it starts logging after I hard reboot.

Draw.io.....Are we able to save the drawings on a share or is the only option to save/open it to/from our computers? Sorry im a bit confused how to have draw.io see a mapped share.