Everything posted by ShadeDream
-
MCE Event Triggered, unsure of cause
Thanks Jorge. I've seen that before and it hadn't come to mind looking at the issue. Are those sorts of problems likely to be recurring or could they happen out of nowhere and not happen again? I've been running this hardware configuration for a few years now without issue. It's also been running fine since. I am running memory at 3200 which appears to be fine in that thread. The deepest C state it seems to go into according to powertop is C2.
-
MCE Event Triggered, unsure of cause
So I had a Fix Common Problems message today about an MCE Event being triggered. I dumped the logs to check those and saw these lines in there, but I'm unsure what issue these are possibly indicating. I did run memtest and that was fine and after reboot ran "mcelog --ascii" but it just sits there and does nothing (perhaps I should have run this before rebooting?) Feb 6 04:02:17 ShadeNAS kernel: mce: [Hardware Error]: Machine check events logged Feb 6 04:02:17 ShadeNAS kernel: mce: [Hardware Error]: CPU 17: Machine Check: 0 Bank 5: bea0000000000108 Feb 6 04:02:17 ShadeNAS kernel: mce: [Hardware Error]: TSC 0 ADDR 1ffff818cbbdc MISC d012000100000000 SYND 4d000000 IPID 500b000000000 Feb 6 04:02:17 ShadeNAS kernel: mce: [Hardware Error]: PROCESSOR 2:870f10 TIME 1770372115 SOCKET 0 APIC d microcode 8701034 Feb 6 04:02:17 ShadeNAS kernel: mce: [Hardware Error]: Machine check events logged Feb 6 04:02:17 ShadeNAS kernel: mce: [Hardware Error]: CPU 21: Machine Check: 0 Bank 5: bea0000000000108 Feb 6 04:02:17 ShadeNAS kernel: mce: [Hardware Error]: TSC 0 ADDR 1ffff81b263f8 MISC d012000100000000 SYND 4d000000 IPID 500b000000000 Feb 6 04:02:17 ShadeNAS kernel: mce: [Hardware Error]: PROCESSOR 2:870f10 TIME 1770372115 SOCKET 0 APIC 19 microcode 8701034Any insight into what this might be? System is a B450 running a Ryzen 3900X in eco mode with a Perc H200 HBA.
-
[PLUGIN] netatalk - AFP for UNRAID (Support Topic)
Ahh! Apologies, I looked for those uams and config options in /etc/netatalk and did not realize they were elsewhere. Appreciate the write-up!
-
[PLUGIN] netatalk - AFP for UNRAID (Support Topic)
Thanks for creating this plugin! I've installed it with the intent to serve files for my old vintage Macs. It worked with an OS 9 VM but it doesn't seem to have a supported authentication mechanism built in for system 7 support. I get the following error message when trying using the IP address: The file server does not use a recognizable log on sequence. The server also doesn't show up in the list but that's always been a bit hit and miss in my experience. I suspect that UAMs were not compiled in with it to support the older less secure authentication mechanisms? I did not see a uams directory in the /etc/netatalk directory with the plugins for them. Is this something that could be added? at least optionally enabled for those of us using it for this purpose?
-
Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
All better! Completely unnecessary fast response on the update, but I appreciate it!
-
Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
Yep: [22-Jan-2024 18:06:51 America/Chicago] PHP Fatal error: Uncaught Error: Undefined constant "ban_class" in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php:407
-
Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
Running into a bit of an odd issue since updating to the latest version. In the "main" view or the "settings" link from the Installed Apps Action menu, the interface just sits with the spinner running and never completely loads and shows my unassigned drives to work with. I do notice an XHR POST request in the browser console that's getting a 500 error for: https://shadenas.local/plugins/unassigned.devices/UnassignedDevices.php Attaching diagnostics in case that's helpful. I've tried uninstalling and reinstalling the plugin in case something there went awry. Also worth noting, one of my drives is passed through for a VM and the VM still functions fine. shadenas-diagnostics-20240122-1748.zip