sross44

I hear you on that one.... but I guess I feel like if it's running strong for 30 days straight plus.... then it restarts... the odds of it being the PSU are pretty low? I feel like I would have seen something in the 3-4 months it's been running you know.

Power - I'm hooked up to a UPC so that shouldn't necessarily be an issue... and a new PSU (3-4 months old) is in there as well. Hardware - What I'd like to do is try to figure out what's causing it then. Memory pass MemTest when I installed it. What other tests can I be running?

Thank you for the well thought out response and all of the information. I've attached the diagnostics like you requested and going to start doing some of the other tests now too. Not sure if the diagnostics will show anything more, but thanks again for taking the time to respond. maverick-diagnostics-20241121-0735.zip

I can't figure out why my server randomly rebooted on it's own. Was working great for 30+ days without restarting and bam... today all of a sudden this just happened. I've attached the syslog for someone to hopefully help me figure out why it did. Any advice or suggestions would be great and help understanding what's going on! syslog-192.168.1.154 (1).log

Ok thanks for checking on it. I appreciate it

@JorgeBI've uploaded my diagnostics zip below. Do you see anything in here? I appreciate you taking the time if you can to check it out and help me. Thanks everyone! maverick-diagnostics-20241008-0859.zip

I'll post the diagnostics zip here shortly.... and see what @JorgeB thinks if there's anything of note.

Good idea... can definitely do that. Just frustrating it's not as simple as seeing what's in the logs and saying "fix this" lol.

Well the PSU is good, I'm hooked up to a UPS that's not showing anything. MemTest was good as well... so I'm just at a loss here. I can't figure out what's causing it. It's why I threw up the syslog file hoping someone can see what's going on in there that I'm missing.

So over the last few weeks, my server has started to randomly restart every few days. It happened again this morning around 04:30. I've attached the syslog that I have saved. It looks like from 0200 to the shutdown SMB services were going haywire... but I can't figure it out. Any advice as to what is going on? I'm open to any suggestions as to what's causing this... I haven't changed anything as far as I know. I'm not even sure if the SMB services are causing this... but something is going on so any help would be appreciated. syslog-192.168.1.154.log

This is a year old now, but did you ever figure this out? I'm kind of stuck on the same thing.

What do I do about it though? I should add this never happened till I upgraded my cache pool and now it's happening? Moved everything back over to the appdata folder etc... so I'm not sure if it's docker related/cache related? I'm at a loss ugh.

Well I stand corrected haha

I don't see any of that in my logs though... I feel like this is unrelated? I just saw this in my fix common problems: Invalid folder cache contained within /mnt

I'm having something pop up that I've never had happen before. I'm on 6.12.13 (currently downgrading to 6.12.11 to hopefully fix the issue). 3x today unRAID has become completely unresponsive and it's because all shares are no longer seen by the server. Not sure what is causing this, but it is a major issue. I've attached the logs prior to the downgrade to see if that helps anyone? I'm stuck and have ZERO idea what to do. logs.txt

Anyone have any idea on how I can diagnose this and figure out what's causing it? I'm at a loss. I've also attached the diagnostics zip to see if someone can guide me in the right direction. What is all this??? Jan 14 22:47:01 Maverick kernel: docker0: port 21(veth43ecfbb) entered blocking state Jan 14 22:47:01 Maverick kernel: docker0: port 21(veth43ecfbb) entered disabled state Jan 14 22:47:01 Maverick kernel: device veth43ecfbb entered promiscuous mode Jan 14 22:47:01 Maverick kernel: docker0: port 23(veth4c2eae0) entered blocking state Jan 14 22:47:01 Maverick kernel: docker0: port 23(veth4c2eae0) entered disabled state Jan 14 22:47:01 Maverick kernel: device veth4c2eae0 entered promiscuous mode Jan 14 22:47:01 Maverick kernel: docker0: port 23(veth4c2eae0) entered blocking state Jan 14 22:47:01 Maverick kernel: docker0: port 23(veth4c2eae0) entered forwarding state Jan 14 22:47:01 Maverick kernel: eth0: renamed from veth713e186 Jan 14 22:47:01 Maverick kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth4c2eae0: link becomes ready Jan 14 22:47:01 Maverick kernel: eth0: renamed from vethd56dbde Jan 14 22:47:02 Maverick kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth43ecfbb: link becomes ready Jan 14 22:47:02 Maverick kernel: docker0: port 21(veth43ecfbb) entered blocking state Jan 14 22:47:02 Maverick kernel: docker0: port 21(veth43ecfbb) entered forwarding state Jan 14 22:47:17 Maverick kernel: docker0: port 23(veth4c2eae0) entered disabled state Jan 14 22:47:17 Maverick kernel: veth713e186: renamed from eth0 Jan 14 22:47:17 Maverick kernel: docker0: port 23(veth4c2eae0) entered disabled state Jan 14 22:47:17 Maverick kernel: device veth4c2eae0 left promiscuous mode Jan 14 22:47:17 Maverick kernel: docker0: port 23(veth4c2eae0) entered disabled state Jan 14 22:47:17 Maverick kernel: vethd56dbde: renamed from eth0 Jan 14 22:47:17 Maverick kernel: docker0: port 21(veth43ecfbb) entered disabled state Jan 14 22:47:17 Maverick kernel: docker0: port 21(veth43ecfbb) entered disabled state Jan 14 22:47:17 Maverick kernel: device veth43ecfbb left promiscuous mode Jan 14 22:47:17 Maverick kernel: docker0: port 21(veth43ecfbb) entered disabled state maverick-diagnostics-20240114-2236.zip

So I've been using unRAID successfully for about a month. Learned so much from this group and it's been awesome... but I'm running into a major issue as of late. I've attached my sys log and all of a sudden in the last few days this keeps happening. Is it the HBA card in my machine? I wasn't getting the errors like a week ago, so not sure what would have changed. I did add a new hard drive... but I still have plenty of "space" on the card to add more. I'm on the stable release not the RC. syslog.txt

I appreciate the build and the response but honestly no need to talk to call me lazy. It has nothing to do with that. A) I'm new to unRAID so I'm learning like everyone else did at some point and B) it's not laziness. If someone has experienced issues with a rollout, why does it hurt me to ask? I didn't say hey I'm to lazy to check this or anything of the sorts. I asked for feedback. Didn't realize me doing so would cause a response like that lol.

Has anyone upgraded to 6.12 rc2 and had success with this running? Just curious since it hasn't been updated in a while? I'm assuming it should still work fine, but wanted to check in with everyone else.

I've setup Deluge VPN on my unraid server. The VPN is working perfectly. I created a downloads folder that has the following. Completed, Incomplete, Unzipped. I have the docker setup to point to that folder as well. When I add something from sonarr, everything starts downloading... or at least shows that it is. But NOTHING is showing up in any of my download folders. I'm beyond lost as to what's happening.... So nothing ultimately downloads or it's going somewhere and I can't find it/explain it lol. Any help would be greatly appreciated.

Hi all. I'm a complete newbie to unRAID. I did a new build today, and have a few questions. I'm not even sure if this is the right place to ask but I figured it was a starting point. 1) I have two 1TB nvme drives and the cache pool is showing only 1TB. Is that because it's in a raid format? Is it better to have two sepearte cache pools? 2) The reason I'm asking about the above is I want to install Plex from the App section. When installing, how do I make sure that the app and the metadata etc uses the cache pool while just keeping the media stored on the array? Please take it easy and talk to me like a dumb dumb lol. Trying to learn and setup at the same time! I need to keep the family happy with plex running!