LateNight

The E3C246D4U has a dedicated LAN port in addition to the two Intel ports. I've also added a 10G card.

Yes, I've had it that way since installing it.

Going in and saving again, without making changes, fixed the issue. No log entries overnight. Thank you.

Just went into settings again and saved (no changes). New parity.check.tuning.cron: # Generated schedules for parity.check.tuning 0 23 * * * /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null 0 7 * * * /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null */7 * * * * /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "monitor" &>/dev/null I'm guessing that fixed the issue - will check in the morning.

Log: Feb 8 23:04:02 DeathStar crond[2219]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null Feb 8 23:04:02 DeathStar crond[2219]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null Feb 8 23:19:01 DeathStar crond[2219]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null Feb 8 23:19:01 DeathStar crond[2219]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null Feb 8 23:34:01 DeathStar crond[2219]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null Feb 8 23:34:01 DeathStar crond[2219]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null Feb 8 23:48:02 DeathStar crond[2219]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null Feb 8 23:48:02 DeathStar crond[2219]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null Feb 9 00:03:02 DeathStar crond[2219]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null parity.check.tuning.cron # Generated schedules for parity.check.tuning /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null */7 * * * * /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "monitor" &>/dev/null parity.tuning.cfg parityTuningIncrements="yes" parityTuningFrequency="daily" parityTuningResumeCustom="" parityTuningResumeHour="23" parityTuningResumeMinute="0" parityTuningPauseCustom="" parityTuningPauseHour="7" parityTuningPauseMinute="0" parityTuningUnscheduled="yes" parityTuningRecon="no" parityTuningClear="no" parityTuningNotify="no" parityTuningHeat="yes" parityTuningHeatHigh="2" parityTuningHeatLow="10" parityTuningHeatNotify="yes" parityTuningDebug="no" parityTuningHeatShutdown="yes" parityTuningHeatCritical="1" parity-checks.log parity.check.tuning.progress.save

Now showing every 15 minutes in my log: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null Unraid Version: 6.8.3

Repeated messages in log, every seven minutes: crond[2212]: exit status 126 from user root /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "monitor" &>/dev/null

I've had Turbo disabled but decided to re-enable it again last night. Server crashed overnight. I wasn't running anything that should stress the server. ¯\_(ツ)_/¯

I have the following debug messages every five minutes in my log: I did verify that I have logging disabled. This started after the most recent update - 2020.10.23

Version: 6.8.3 Could not access my server this morning, requiring a hard reset. I was able to capture some details on the attached syslog.txt. Its appears to be multiple rcu_sched detected stalls on CPUs/tasks. I've also attached the diagnostics after the reboot. Any help is appreciated.syslog.txtdeathstar-diagnostics-20200813-1032.zip

Sorry, should have linked to the second response and not the thread. I was also having permission issues until I enabled the Set Permissions option. I did change the chown User to 99, and chown Group to 100 but it appears either works.

@unRAIDuser7 @TexasUnraid have you tried the "Set Permissions" option in Sonarr, as explained at:

Had this error occur overnight. I had added a headphones docker. Unfortunately, I turned off my syslog server and the logs weren't saved after reboot.

This is listed in the manual: Clear CMOS - 1 (short pin), but I don't see it in their diagram. Pulling the battery should work.

@JM2005 - he asked some clarifying questions, mostly about my BIOS settings, but no word today.

Interesting. I have already been in contact with William at ASRock and he's walking me through the steps of eliminating other devices in my system (10GB card and flashed IBM m1015). Are you seeing the same output when clicking on the CU_CATERR event in the log?

@JM2005 - when you click on that entry in the IPMI log what does it show? On my system it shows:

Thank you @Hoopster. I read earlier in the thread that you had disabled Turbo Boost but wrote it off as it seemed it was temperature related. I have not seen anything in my system reach over 40°C (except that MB sensor showing 85°C), and watching most of the parity check the CPU never went above 38°C. However after disabling Turbo Boost, I was able to complete a parity check.

Thank you @Hoopster for this deal/thread. I upgraded my almost 9 year old server. I'm running into an odd issue and trying to determine if it's hardware or software. My system runs fine until I start a parity check. During the parity check unRaid freezes but I am still able to reach the IPMI interface. I'm using BMC Firmware 1.80.00 and BIOS Firmware L2.21A. From my IPMI event log it shows CPU_CATERR. 3 | 07/04/2020, 08:34:35 | CPU_CATERR | Processor | State Asserted - Asserted I ran a syslog server but I don't see anything related. <30>Jul 4 02:46:03 DeathStar ool www[17368]: /usr/local/emhttp/plugins/dynamix/scripts/rsyslog_config 192.168.1.5 04/07 02:46:03.013 <46>Jul 4 02:46:06 DeathStar rsyslogd: [origin software="rsyslogd" swVersion="8.1908.0" x-pid="17979" x-info="https://www.rsyslog.com"] start 192.168.1.5 04/07 02:46:05.473 <4>Jul 4 02:46:32 DeathStar kernel: mdcmd (88): spindown 3 192.168.1.5 04/07 02:46:31.123 <4>Jul 4 02:46:32 DeathStar kernel: mdcmd (89): spindown 6 192.168.1.5 04/07 02:46:32.001 <4>Jul 4 02:46:34 DeathStar kernel: mdcmd (90): spindown 4 192.168.1.5 04/07 02:46:33.832 <4>Jul 4 02:46:35 DeathStar kernel: mdcmd (91): spindown 5 192.168.1.5 04/07 02:46:34.483 <4>Jul 4 02:46:45 DeathStar kernel: mdcmd (92): check 192.168.1.5 04/07 02:46:44.087 <4>Jul 4 02:46:45 DeathStar kernel: md: recovery thread: check P ... 192.168.1.5 04/07 02:46:44.087 <13>Jul 4 03:00:01 DeathStar Recycle Bin: Scheduled: Files older than 7 days have been removed 192.168.1.5 04/07 03:00:00.645 <77>Jul 4 03:40:21 DeathStar crond[2295]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null 192.168.1.5 04/07 03:40:20.584 I also downloaded the MCA Log (attached). It looks like the CPU may be defective, but I've never seen anything like it. CPU1 Do not Present!! Get CPU0 MCA Error Source Log failed: CC = 0x81 Get CPU core number failed: CC = 0x81. Default catch 28 cores. Diagnostics also attached, run just after rebooting. Any help is appreciated, and can move this to its own topic if needed. MCALog.txt deathstar-diagnostics-20200704-1144.zip

I love unRaid's flexibility and ease of use. Wishlist: native ZFS

Fixed. I was able to boot to GUI mode without plugins then update unRaid from 6.4.1 to 6.5.1 which took care of the issue.

Went to watch something on Plex but it wouldn't connect to my Plex Server which is a docker on my Unraid machine. Tried browsing to tower/dashboard and it fails to load in any browser or device. Tried direct ip and still a no go. I can browse via file explorer on Win10 and can ssh in. Tried a reboot but that didn't fix the problem. Attached is the diagnostic zip. Thank you for any help. . deathstar-diagnostics-20180511-2243.zip

ntlm auth = yes seems to have fixed my problem.

I'm having a similar issue trying to connect with Windows 10. No issues before the upgrade. Since the upgrade I cannot access files using my user account. I can access shares using a guest account but it does not have write access. My username and password are the same in both Windows and Unraid.