PanteraGSTK
-
Posts
129 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by PanteraGSTK
-
-
29 minutes ago, trurl said:
Also, your system share has files on the array.
And your docker image is larger than I usually recommend, possibly that is related to those dockers without templates. Have you had problems with filling docker image?
Docker has 21gb used. At one point it went over 30gb, but I've removed some dockers since then and it's been pretty stable at 21gb.
-
35 minutes ago, trurl said:
Enable Syslog Server as explained in the FAQ here:
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=781601
I also notice you have FCP warnings about several containers without templates. What do you plan to do about those?
Those warnings are pretty old. Most are just using something other than the default port. Haven't caused any issues at all for quite some time. I will look at resolving them.
EDIT: Correction. I didn't notice they were template errors. I've corrected those.
I have syslog enabled, but it looks like it was set to a "custom folder" which it shouldn't have been. I've corrected that.
-
Upgraded the server to 6.8 and no issues other than two random reboots. Diagnostics attached.
-
6 minutes ago, 1812 said:
Have run pfsense a bunch, also opnsense for a bit.
ive been on Sophos utm 9 for about 6 months or so and really like it. Going to setup failover on a small fanless pc in a month or two that will take over automatically if the virtualized firewall goes down
Same here. Been using Sophos UTM for about 5 years or so. Fantastic product and pretty amazing what you get for the free license.
It does have a learning curve though. I've had it running on an i3 with 8gb of ram and it hardly uses any resources with my config. I also run a pi-hole along side it and the combo is fantastic.
-
Marking this solved...for the third time.
I'm pretty confident this time that CPU0 is to blame. The memory all test fine, but the controller issue I got when I first got the CPU/Mobo/RAM combo makes it pretty obvious that is the case.
It is possible that Socket 0 is the culprit, but I'll find that out when I move CPU1 to socket 0. I'll also moved the confirmed working RAM. If it all checks out I may grab another xeon 2670 off ebay and hope for the best.
I was able to get through a parity check and multiple drives using the file integrity plugin. That plugin was an easy test because when I tried to use it in the past a reboot was pretty much always triggered on my 4TB drives.
Another test that passed is downloading large files via usenet while also remuxing a file using makemkv. That's quite a lot of operations at once especially considering my kids were watching movies/tv via plex all at the same time. No reboot. If that didn't make it reboot, nothing will.
Hopefully.
Thanks for the help.
-
14 hours ago, jonathanm said:
If it increased the uptime in a predictable and repeatable way but didn't solve the issue, that would point to power supply. Not necessarily the PSU itself, there are power supply circuits on the motherboard to further smooth, condition, and regulate the power to the memory and CPU.
So, if totally removing 1 cpu and associated RAM "fixes" it, swap to the unused set of CPU and RAM and see if it stays "fixed". If it does, that further implicates the power supply chain. You could have a marginal motherboard power supply that has degraded over time. I've had boards that originally ran 4 sticks of RAM just fine, but later developed instability with more than 2 sticks of perfectly good RAM.
While removing two sticks of ram seems to have helped, having that ram in netted the same behavior. Sometimes it would be fine, no reboots, sometimes the reboots would happen quickly.
Removing CPU0 and associated RAM allowed an additional parity check to complete. No issues. I'll continue to test, but with the fact that I got memory controller errors with CPU0 when I first installed it, but they stopped when I moved the ram around the board points to CPU0 being the culprit.
My PSU is a Corsair RMX850 and it's less than 5 years old. I tend to lean toward PSU in these situations too, but with all the other factors I'm confident that CPU0 is most likely the issue.
-
Removing the memory may have helped, but it didn't fix it. I got through an entire parity check (with 2 parity drives at 50mbps). However, when I checked this morning it had rebooted again.
Now to remove cpu0 and memory.
-
1 hour ago, jonathanm said:
Hmm. Maybe temporarily pull 1 whole processor and the associated memory.
When it reboots, does it sound like a normal power cycle? Is there anything that catches your attention before it actually fully reboots?
It does sound like a normal power cycle. That's the strange part. I've not been able to capture anything that points me in any specific direction.
When I first got the board and cpus, I had an issue where some memory wasn't recognized. I put them in alternate slots and forgot about it for a few years. I pulled those dimms and am testing again.
If it reboots again, I'll pull the associated CPU and remaining dimms and just leave cpu1 and its memory.
-
1 hour ago, jonathanm said:
Memory. Try removing half and running for a while.
This kind of thing is usually hardware. Have you been sitting near or in front of it when it power cycled yet?
Yeah, I have. Many times. It's in a closet, but I'm 6 feet away from the actual server.
I'll pull some memory, but it's a dual proc board so I'll have to be careful.
-
Man, I really thought the new SAS card was going to fix this.
I recently removed my SAS2LP card in favor of an LSI HBA, but during a parity check the system rebooted at 85%.
I'm not finding anything in logs that tell me where to look.
Any ideas on where to start?
-
1 minute ago, Benson said:
Note that, we are talking same thing. 3ware are 16 port or in two ?
3ware has 4 ports that control 4 drives each on a single card. The 2 LSI cards have 2 ports that control 4 drives each.
I've got it down. I've got a breakout cable and a SATA cage with fan. I'll pull one drive at a time until 4 are done. Then I can swap cables between the 3ware card to the LSI. Then repeat until complete.
-
I think we're talking about the same thing now.
I've got two LSI cards for a total of 16 drives. These completely replace the 16 drive capable 3ware card.
I was thinking the same. Put the disks in an external cage and rebuild one by one. Once that's complete remove the 3ware controller since it won't have drives connected any longer.
Thanks for the confirmation. -
Right now I can pull individual drives and move them to the new LSI cards one by one. It will be a pain, but it's possible. Then I can rebuild them one by one as the drive removed will become the replacement drive.
Your method would be me expanding the array with new disks, moving data over, then shrinking the array. Am I correct?
-
Hello, I just wanted to validate the method I have in mind for migrating from my current 3ware card to the new LSI HBA (Fujitsu branded) cards I recently flashed into IT mode (thanks @johnny for the guide and batch files).
I pulled out my SAS2LP and replaced it with one of the LSI cards and (as expected) no issues at all. Array started without issue.
However, when I pulled my 3ware card and plugged the drives into the LSI cards, I got missing disks (as expected since 3ware doesn't support fully passing through the drive info or size). I then went to do a new config, kept the drives in their slots (because none of the slots changed from the SAS2LP to the LSI card).
What I wasn't expecting was that now the 16 drives that came from that 3ware card now needed to be formatted in order to be used. I noped out of there real quick and put the drives back on the 3ware card and reverted to my previously saved config. Booted up and now everything is back to normal.What I'm not sure how to do is the migration without it causing issues.
My thoughts are:
1. Keep the LSI cards in place and get a break out cable.
2. Plug that cable into a storage cage and pull one drive at a time and rebuild.
3. Once that's complete for all 16 drives, pull the 3ware card and put my current drives back into the SAS backplane.
This is really the only logical way I can think to do this. When I take a drive from the 3ware card and try to read it on another computer, the file system isn't accessible for some reason. It sees the XFS partition, but my linux reader software can't read it. I don't have another linux PC to test on.
Is there a better/smarter way to do what I'm propsing? 16 drives (2-4tb) is going to take quite a while.
What do you guys think? -
22 hours ago, itimpi said:
Xfs_repair IS very quick, especially if no errors (or just a small number) are found. Be interesting to see whether it has helped in any way.
It would seem everything is OK. 24hrs uptime and I've stress tested and no issues so far.
Thanks again for the help.
-
9 minutes ago, itimpi said:
Xfs_repair IS very quick, especially if no errors (or just a small number) are found. Be interesting to see whether it has helped in any way.
I will let you know either way.
-
4 hours ago, itimpi said:
It could well be worth stopping the array and then restarting in Maintenance mode and then clicking on each array drive on the Main tab in turn and running a file system check.
Thanks for the tip.
I did that and didn't see any errors, but I'm not all that familiar with xfs_repair
I let it repair as needed and all the checks finished very quickly. Only took a few seconds per disk. Not sure if that's good or bad.
-
That did not solve the problem (got more space now though).
Got through a 17hr parity check without any issues. As soon as I start downloading with NZBget the server restarts after about 10 min or so. Very odd.
I've started using the syslog function so I've attached that log file. The reboot happened around 6pm (1800)
-
It would appear that replacing the failing drive resolved the issue.
I am curious as to why a bad/failing drive would cause reboots though. What would I look at to make sure that was my issue? -
May have found the issue. I have a disk that is dying. Will replace tomorrow and monitor random reboot.
Turns out I hadn't modified my SMART settings for this particular drive to work with my 3ware controller.
-
It's gotten better (I think unassigned devices was doing something. Removed plugin and it's not throwing so many errors), but it happened again this morning.
I have my dockers set to back upunraid-diagnostics-20190706-1714.zip every night and it somehow seems tied to that time of day (night).
-
It looks like during the past week I've apparently been getting random reboots. From what I've seen in the logs, there doesn't seem to be much of a reason. I figured I would post the diagnostics to see if anyone with more knowledge than me can help.
Normally, I'd look to the PSU, but I got this around 4 years ago (Corsair RMX 850) and have had zero issues until now. Board and CPU are both older, but again no issues until now.
Let me know what else I can provide.
-
19 hours ago, bastl said:
Thank you guys for the answer. I couldn't really wait for an answer. I'am on bleeding edge right now, as always. I used the "latest flag" with the old appdata and so far no errors, except of some in the Docker logs @linuxserver.io
Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... [cont-init.d] 30-keygen: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Feb 18, 2019 1:34:44 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused (Connection refused) Feb 18, 2019 1:34:44 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry INFO: Retrying request Feb 18, 2019 1:34:44 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused (Connection refused) Feb 18, 2019 1:34:44 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry INFO: Retrying request Feb 18, 2019 1:34:44 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused (Connection refused) Feb 18, 2019 1:34:44 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry INFO: Retrying requestI'm getting the same error in my log. I looked at the server log and it's showing an error connecting to the DB server. Any ideas?
-
The issue with the docker not stopping still happened even after setting shared memory to 60. It took MUCH longer this time, but it still happened.
Is there anything I can give you that will help? The container just says it's stopping and then nothing. I've had to delete the image quite a few times to fix this. Not difficult, but a pain.
What can I do to help? Am I the only one that has this issue?
[Support] Linuxserver.io - Unifi-Controller
in Docker Containers
Posted
I seem to be having the same issue. Settings are not being honored. When I SSH back into the USG, the firewall is still enabled.