inspectornorse
-
Posts
32 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by inspectornorse
-
-
Just now, JorgeB said:
Still using ipvlan, an unlearn shutdown may change some docker settings, but a clean one shouldn't.
Cool. We lost power during this last stint, but I have the UPS thing enabled which does shut it down, but I guess not 'cleanly'. Explains it a little bit.
Any hardware errors I should worry about?
Thank you
-
6 minutes ago, JorgeB said:
Change docker network to ipvlan, reboot and post new diags.
thank you -
I feel like almost every time my server shuts down (cleanly or not) it reverts to macvlan and fix common problems reports this error. I have at least changed the setting twice that I can remember.
What am I doing wrong? I do have the Mirror syslog to flash turned on, for what it's worth. Logs attached. Thank you all
-
Recently my server went offline for an unknown reason and had trouble booting up after a hard reboot.
Things seem ok now, but Fix Common Problems is reporting a few issues.
Diagnostics attached. Thank you
-
Greetings,
I just noticed my Plex Cache directory (/appdata/plex/Library/Application Support/Plex Media Server/Cache) seems fairly large @ 33GB
Wondering if this is normal. Thank you -
Right around 5am today (EST) my server went unresponsive (could not access the webui or ssh).
Hard reboot got it acting right again but I'm wondering what the cause may have been. Diagnostics attached.
Thanks
-
1 minute ago, trurl said:
Cache is corrupt.
Thank you. Can you share how/where you determined this? Since this keeps happening should I replace the cache disks?
-
-
Several days ago I began noticing that I was unable to login to my Pihole container. Restarting that container (and any other container) failed.
I disabled docker, deleted the docker image, and reinstalled the containers from previous apps, but now it appears to be happening again. I only run a handful (attached) so I'm wondering what I may have screwed up.
My setup has been running pretty well without issues for about 1.5-2 years now. Any guidance is appreciated!
-
1 hour ago, JorgeB said:
Oct 12 06:36:51 DeathStar mcelog: failed to prefill DIMM database from DMI data Oct 12 06:36:51 DeathStar mcelog: Kernel does not support page offline interfaceThese are harmless, you can ignore.
Thank you friend
Can you share your strategy for determining this? I see the entries you mentioned in syslog.txt
-
Diagnostics attached.
My NAS is currently about half way through upgrading/rebuilding all of the disks for a little added context.
Also if someone can share what to look for to determine whether the issue is serious or not that would be swell. I'd like to be able to do the analysis on my own if possible in the future.
Appreciate the support as usual -
Greetings y'all,
Recently I installed the MacInABox container to do some testing. I *believe* this may have changed my docker VLAN setting from ipvlan to macvlan but I cannot confirm that with absolute certainty. Upon changing this value back to ipvlan, my Pihole container was no longer getting queried by my router as it is set to the primary DNS address.
I tried a few things like changing the vlan setting back in docker settings and plugging in both network adapters to no avail.
My server has two networking interfaces. One that is built into the motherboard (that I've never used) and a second that I generally use.
Attaching my network configuration, Pihole configuration, and Docker settings, if helpful.
Thank you for taking a look
-
3 minutes ago, trurl said:
Click the SMART warning on the Dashboard page to Acknowledge and it will warn again if it increases.
Do any of your other disks have SMART warnings on the Dashboard page?
That’s my usual go to move
but I have been getting repeat warnings re the same disk.
No other warnings other than this one disk. Thank you
-
5 hours ago, JorgeB said:
If the errors are increasing replace that SATA cable.
Thank you I will do that
-
Diagnostics and screen shot attached. Thank you for any tips!
-
1 hour ago, ljm42 said:
Your system is in Strict mode, so https://ipaddress is not defined as that url is not valid for the myunraid.net certificate.
You can use http://ipaddress (note http not https) to be redirected to the myunraid.net url.
If there are DNS issues and the myunraid.net url is not available, see https://wiki.unraid.net/My_Servers#How_to_access_your_server_when_DNS_is_down
Thank you
-
Greetings,
In lieu of yesterday’s certificate server outage I noticed that I was also unable to access my Unraid server’s WebUI by its IP address.
I can access my server via the URL now that the certificate server is back online, but I still cannot access it by IP (as it seems my peers on other Unraid servers, can).
Attached the diagnostics and screen shot. Thank you
-
Mine is also working. Thank you whoever fixed this
-
1
-
-
2 minutes ago, wgstarks said:
Are you trying this from the same LAN?
Yes I am. All containers etc are working also (if helpful).
-
Having this issue also. Can’t get in via https://ip either (nginx 404)
-
47 minutes ago, JorgeB said:
Please post the diagnostics.
Here you go. Thanks
-
For some reason I can’t get the Unraid web UI to load..I’ve tried:
1. The bookmarked URL that usually works
3. http://ipaddress
4. Checking the IP to make sure its the same (it’s set with a dhcp reservation)
5. Reboot
All the containers and everything are functioning fine…appreciate any clues!
-
On 6/3/2022 at 9:33 AM, JorgeB said:
Parity2 problem look more like power/connection problem, likely a connection if these aren't old:
199 UDMA_CRC_Error_Count -O--CK 198 001 000 - 21841Thank you. I think I’m going to try replacing the SFF-8643 cables first. I appreciate you taking a look.
-
23 minutes ago, ChatNoir said:
People will have a hard time making relevant suggestions without your diagnostics.
Please attach the full zip to your next post.
Thank you. Diagnostics attached.
but I have been getting repeat warnings re the same disk.
macvlan warning/hardware errors detected
in General Support
Posted
Thank you. Took about 17.6 seconds. Looks like my Shutdown time-out is set to 90.