JonathanM Posted May 23, 2022 Share Posted May 23, 2022 7 hours ago, AndreB said: my LAN ip is 20.10.20.1 and 20.10.10.1 aren't they private ? No. They belong to Microsoft Corporation. https://www.lifewire.com/what-is-a-private-ip-address-2625970 NetRange: 20.0.0.0 - 20.31.255.255 CIDR: 20.0.0.0/11 NetName: MSFT NetHandle: NET-20-0-0-0-1 Parent: NET20 (NET-20-0-0-0-0) NetType: Direct Allocation OriginAS: Organization: Microsoft Corporation (MSFT) RegDate: 2017-10-18 Updated: 2021-12-14 Ref: https://rdap.arin.net/registry/ip/20.0.0.0 OrgName: Microsoft Corporation OrgId: MSFT Address: One Microsoft Way City: Redmond StateProv: WA PostalCode: 98052 Country: US RegDate: 1998-07-10 Updated: 2022-03-28 Quote Link to comment
trurl Posted May 23, 2022 Share Posted May 23, 2022 You should fix your entire LAN immediately. Not only do these IPs belong to (and may be in use by) Microsoft, but they may be exposed on the internet. Quote Link to comment
AndreB Posted May 23, 2022 Share Posted May 23, 2022 Ah ok cool, thanks for the info, i will work on this to change all my IP to Private. Thanks again guy's Quote Link to comment
Corvus Posted July 9, 2022 Share Posted July 9, 2022 (edited) Hey all, After almost 2 years of using Unraid on my current hardware config, everything's been working flawlessly, until I realized my machine rebooted without explanation this afternoon, and upon logging in tonight, I saw the same message. Here's my output from mcelog. Is this something that's safe to ignore? syslog (1) Edited July 9, 2022 by Corvus Quote Link to comment
Squid Posted July 10, 2022 Share Posted July 10, 2022 22 hours ago, Corvus said: Is this something that's safe to ignore? yes Jul 9 16:47:49 NAS mcelog: failed to prefill DIMM database from DMI data A BIOS update might help suppress it if one's available. Quote Link to comment
Doublemyst Posted August 24, 2023 Share Posted August 24, 2023 Hi there Now I got this error .. In Syslogs I've got this: Aug 22 12:58:04 borg kernel: 9pnet: Installing 9P2000 support Aug 22 12:58:04 borg kernel: mce: [Hardware Error]: Machine check events logged Aug 22 12:58:04 borg kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 22: baa000000002010b Aug 22 12:58:04 borg kernel: mce: [Hardware Error]: TSC 0 MISC d012000100000000 SYND 4d000000 IPID 1813e17000 Aug 22 12:58:04 borg kernel: mce: [Hardware Error]: PROCESSOR 2:a20f10 TIME 1692701860 SOCKET 0 APIC 0 microcode a201016 Aug 22 12:58:04 borg kernel: mce: [Hardware Error]: Machine check events logged Aug 22 12:58:04 borg kernel: mce: [Hardware Error]: CPU 5: Machine Check: 0 Bank 5: bea0000001000108 Aug 22 12:58:04 borg kernel: mce: [Hardware Error]: TSC 0 ADDR fff80257f8be58 MISC d012000100000000 SYND 4d000000 IPID 500b000000000 Aug 22 12:58:04 borg kernel: mce: [Hardware Error]: PROCESSOR 2:a20f10 TIME 1692701860 SOCKET 0 APIC a microcode a201016 Aug 22 12:58:04 borg kernel: microcode: CPU0: patch_level=0x0a201016 Aug 22 12:58:04 borg kernel: microcode: CPU1: patch_level=0x0a201016 Aug 22 12:58:04 borg kernel: microcode: CPU2: patch_level=0x0a201016 Aug 22 12:58:04 borg kernel: microcode: CPU3: patch_level=0x0a201016 Aug 22 12:58:04 borg kernel: microcode: CPU4: patch_level=0x0a201016 Aug 22 12:58:04 borg kernel: microcode: CPU5: patch_level=0x0a201016 Aug 22 12:58:04 borg kernel: microcode: CPU6: patch_level=0x0a201016 Aug 22 12:58:04 borg kernel: microcode: CPU7: patch_level=0x0a201016 Aug 22 12:58:04 borg kernel: microcode: CPU8: patch_level=0x0a201016 Aug 22 12:58:04 borg kernel: microcode: CPU9: patch_level=0x0a201016 Aug 22 12:58:04 borg kernel: microcode: CPU10: patch_level=0x0a201016 Aug 22 12:58:04 borg kernel: microcode: CPU11: patch_level=0x0a201016 Aug 22 12:58:04 borg kernel: microcode: Microcode Update Driver: v2.2. Aug 22 12:58:04 borg kernel: IPI shorthand broadcast: enabled Aug 22 12:58:04 borg kernel: sched_clock: Marking stable (9307830493, 344892605)->(9774991219, -122268121) Anyone an idea, if this is bad? Quote Link to comment
trurl Posted August 24, 2023 Share Posted August 24, 2023 attach diagnostics to your NEXT post in this thread Quote Link to comment
Doublemyst Posted August 24, 2023 Share Posted August 24, 2023 Here the diagnostics (I hope it was anonymized) borg-diagnostics-20230823-0728.zip Quote Link to comment
Doublemyst Posted September 1, 2023 Share Posted September 1, 2023 On 8/24/2023 at 5:27 PM, trurl said: attach diagnostics to your NEXT post in this thread Hi @trurl Did you manage to see something fishy in this error message? Cheers! Quote Link to comment
Doublemyst Posted September 3, 2023 Share Posted September 3, 2023 Hi @Squid Maybe you have an idea, if the error message I got is a bad one? Sorry for disturbing! Cheers Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.