\V/

Backstory: I have experienced multiple instances of two-disks failures over the summer due to the combo of heat wave and old drives. In one of those rebuilds, the recreated disks were totally corrupt due to bad parity. As some of the data were not backed up, this resulted in permanent data loss. How did this happen: Mover ran itself to schedule in emulated mode, even though there were two drives with errors. Feature request: Don't let mover run when array is in emulated mode OR when there are disk errors

Same problem here. i5-11500 with 6.10rc1. Neither Plex nor dlandon/zoneminder works with QSV. I cannot downgrade to 6.9.2 due to docker network bug destroying my array. Hope LimeTech will fix this in the stable version.

Hi all, I am wondering if it is safe to put this in my go file so that Unraid will auto reboot when suffering from a kernel panic: echo 20 >/proc/sys/kernel/panic My server has been experiencing some occasional kernel panics since 6.9.2 (I suspect it's related to: 1, 2). I work long hours and hate coming home to a furnace when it does. Will the above quick fix work? Thanks

Unraid 6.9.2 here. Experiencing the same problem. Happens every once in a long while. The kernel panic screen shows something related to IPv6. The only changes to my server recently are upgrading from 6.8.3 and reassigning a bunch of dockers to br0,br1.

I do have spare VGA card, ram, and PSU, and can temporarily unplug HBAs. Gonna try to troubleshoot them. Unfortunately I don't have a spare Ryzen CPU or MB available. It's gonna take some serious convincing to the service center guy as he's pretty used to dealing with fraudsters attempting to get free replacements. Last time I had to argue with the lady from a different service center that SMART error count means the SSD is bad even if it functions. Story of my pc building life. Anyhow thanks for your thoughtful replies.

Just tried that. Didn't change anything, still got the errors. Okay, I am on latest beta firmware now. The errors still came up. I've done some googling and it looks like I may have a bad L2 cache (per the line "uop cache tag parity error" in syslog). And I just now caught the error after array has started. Looks like I might have to RMA my 2700x. Granted, the system hasn't crashed even one. It's just nuisance to see those errors. Edit: To answer your questions - Could PCIE devices really be probable culprit? Because these were the same devices before I migrated from an Intel Coffee Lake. They worked fine before, no mce error. - I have no idea what those terms meant. Part number is AD4U240038G17-R - HX850 (2017 revised ver)

Hi, I took out the WD drive serials since 1) people from /r/datahoarder subreddit claim that publishing them on open internet can be risky for future warranty 2) the issue I have don't seem hard disk related. All other logs are untampered. I had just recently updated the BIOs and it is already set to default per flashing. I guess I'll wait for the next BIOs update and see. I really hope this is not faulty hardware related as it will be very painful to prove complex problem like this one to the guy at my local service center

Hi, Is there a Linux command that can do this? Since Docker and VMs require array starting.

Hello all, my first post here. I have been getting a lot of Machine Check Event errors ever since I swapped to a new CPU, MB, and Rams. Specifically, this error happens nonstop after system start up and before array starts. If I start the array, the MCE error spam ceases. The Unraid version is 6.5.3. My rig currently has Ryzen 2700X, Asrock X470 Taichi, and 4 sticks of ADATA Premier 8GB 2400Mhz Ram. Aug 21 18:48:18 Lawpet avahi-daemon[9033]: Server startup complete. Host name is Lawpet.local. Local service cookie is 1169872464. Aug 21 18:48:19 Lawpet avahi-daemon[9033]: Service "Lawpet" (/services/ssh.service) successfully established. Aug 21 18:48:19 Lawpet avahi-daemon[9033]: Service "Lawpet" (/services/smb.service) successfully established. Aug 21 18:48:19 Lawpet avahi-daemon[9033]: Service "Lawpet" (/services/sftp-ssh.service) successfully established. Aug 21 18:53:07 Lawpet kernel: mce: [Hardware Error]: Machine check events logged Aug 21 18:53:07 Lawpet kernel: [Hardware Error]: Corrected error, no action required. Aug 21 18:53:07 Lawpet kernel: [Hardware Error]: CPU:1 (17:8:2) MC3_STATUS[Over|CE|MiscV|-|-|-|-|SyndV|-]: 0xd820000000000150 Aug 21 18:53:07 Lawpet kernel: [Hardware Error]: IPID: 0x000300b000000000, Syndrome: 0x000000002a000503 Aug 21 18:53:07 Lawpet kernel: [Hardware Error]: Decode Unit Extended Error Code: 0 Aug 21 18:53:07 Lawpet kernel: [Hardware Error]: Decode Unit Error: uop cache tag parity error. Aug 21 18:53:07 Lawpet kernel: [Hardware Error]: cache level: RESV, tx: INSN, mem-tx: IRD Aug 21 18:53:07 Lawpet kernel: mce: [Hardware Error]: Machine check events logged Aug 21 18:53:07 Lawpet kernel: [Hardware Error]: Corrected error, no action required. Aug 21 18:53:07 Lawpet kernel: [Hardware Error]: CPU:11 (17:8:2) MC3_STATUS[Over|CE|MiscV|-|-|-|-|SyndV|-]: 0xd820000000000150 Aug 21 18:53:07 Lawpet kernel: [Hardware Error]: IPID: 0x000300b000000000, Syndrome: 0x000000002a000503 Aug 21 18:53:07 Lawpet kernel: [Hardware Error]: Decode Unit Extended Error Code: 0 Aug 21 18:53:07 Lawpet kernel: [Hardware Error]: Decode Unit Error: uop cache tag parity error. Aug 21 18:53:07 Lawpet kernel: [Hardware Error]: cache level: RESV, tx: INSN, mem-tx: IRD Aug 21 18:53:23 Lawpet ntpd[2087]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Aug 21 19:04:03 Lawpet kernel: mce: [Hardware Error]: Machine check events logged Aug 21 19:04:03 Lawpet kernel: [Hardware Error]: Corrected error, no action required. Aug 21 19:04:03 Lawpet kernel: [Hardware Error]: CPU:1 (17:8:2) MC3_STATUS[Over|CE|MiscV|-|-|-|-|SyndV|-]: 0xd820000000000150 Aug 21 19:04:03 Lawpet kernel: [Hardware Error]: IPID: 0x000300b000000000, Syndrome: 0x000000002a000503 Aug 21 19:04:03 Lawpet kernel: [Hardware Error]: Decode Unit Extended Error Code: 0 Aug 21 19:04:03 Lawpet kernel: [Hardware Error]: Decode Unit Error: uop cache tag parity error. Aug 21 19:04:03 Lawpet kernel: [Hardware Error]: cache level: RESV, tx: INSN, mem-tx: IRD Aug 21 19:04:03 Lawpet kernel: mce: [Hardware Error]: Machine check events logged Aug 21 19:04:03 Lawpet kernel: [Hardware Error]: Corrected error, no action required. Aug 21 19:04:03 Lawpet kernel: [Hardware Error]: CPU:11 (17:8:2) MC3_STATUS[Over|CE|MiscV|-|-|-|-|SyndV|-]: 0xd820000000000150 Aug 21 19:04:03 Lawpet kernel: [Hardware Error]: IPID: 0x000300b000000000, Syndrome: 0x000000002a000503 Aug 21 19:04:03 Lawpet kernel: [Hardware Error]: Decode Unit Extended Error Code: 0 Aug 21 19:04:03 Lawpet kernel: [Hardware Error]: Decode Unit Error: uop cache tag parity error. Aug 21 19:04:03 Lawpet kernel: [Hardware Error]: cache level: RESV, tx: INSN, mem-tx: IRD Aug 21 19:04:22 Lawpet root: Fix Common Problems Version 2018.08.05 Aug 21 19:04:25 Lawpet root: Fix Common Problems: Error: Array is not started Aug 21 19:04:38 Lawpet root: Fix Common Problems: Error: Machine Check Events detected on your server Aug 21 19:04:38 Lawpet root: mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead. Aug 21 19:04:38 Lawpet root: CPU is unsupported Aug 21 19:04:39 Lawpet root: Fix Common Problems: Warning: You have a Ryzen CPU, but Zenstates not installed. ** Ignored Aug 21 19:09:30 Lawpet kernel: mce: [Hardware Error]: Machine check events logged Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: Corrected error, no action required. Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: CPU:9 (17:8:2) MC3_STATUS[-|CE|MiscV|-|-|-|-|SyndV|-]: 0x9820000000000150 Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: IPID: 0x000300b000000000, Syndrome: 0x000000002a000503 Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: Decode Unit Extended Error Code: 0 Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: Decode Unit Error: uop cache tag parity error. Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: cache level: RESV, tx: INSN, mem-tx: IRD Aug 21 19:09:30 Lawpet kernel: mce: [Hardware Error]: Machine check events logged Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: Corrected error, no action required. Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: CPU:1 (17:8:2) MC3_STATUS[Over|CE|MiscV|-|-|-|-|SyndV|-]: 0xd820000000000150 Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: IPID: 0x000300b000000000, Syndrome: 0x000000002a000502 Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: Decode Unit Extended Error Code: 0 Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: Decode Unit Error: uop cache tag parity error. Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: cache level: RESV, tx: INSN, mem-tx: IRD Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: Corrected error, no action required. Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: CPU:5 (17:8:2) MC3_STATUS[Over|CE|MiscV|-|-|-|-|SyndV|-]: 0xd820000000000150 Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: IPID: 0x000300b000000000, Syndrome: 0x000000002a000503 Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: Decode Unit Extended Error Code: 0 Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: Decode Unit Error: uop cache tag parity error. Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: cache level: RESV, tx: INSN, mem-tx: IRD Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: Corrected error, no action required. Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: CPU:15 (17:8:2) MC3_STATUS[Over|CE|MiscV|-|-|-|-|SyndV|-]: 0xd820000000000150 Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: IPID: 0x000300b000000000, Syndrome: 0x000000002a000503 Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: Decode Unit Extended Error Code: 0 Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: Decode Unit Error: uop cache tag parity error. Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: cache level: RESV, tx: INSN, mem-tx: IRD Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: Corrected error, no action required. Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: CPU:11 (17:8:2) MC3_STATUS[Over|CE|MiscV|-|-|-|-|SyndV|-]: 0xd820000000000150 Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: IPID: 0x000300b000000000, Syndrome: 0x000000002a000503 Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: Decode Unit Extended Error Code: 0 Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: Decode Unit Error: uop cache tag parity error. Aug 21 19:09:30 Lawpet kernel: [Hardware Error]: cache level: RESV, tx: INSN, mem-tx: IRD Aug 21 19:14:58 Lawpet kernel: mce_notify_irq: 3 callbacks suppressed Aug 21 19:14:58 Lawpet kernel: mce: [Hardware Error]: Machine check events logged Aug 21 19:14:58 Lawpet kernel: [Hardware Error]: Corrected error, no action required. Aug 21 19:14:58 Lawpet kernel: [Hardware Error]: CPU:5 (17:8:2) MC3_STATUS[Over|CE|MiscV|-|-|-|-|SyndV|-]: 0xd820000000000150 Aug 21 19:14:58 Lawpet kernel: [Hardware Error]: IPID: 0x000300b000000000, Syndrome: 0x000000002a000503 Aug 21 19:14:58 Lawpet kernel: [Hardware Error]: Decode Unit Extended Error Code: 0 Aug 21 19:14:58 Lawpet kernel: [Hardware Error]: Decode Unit Error: uop cache tag parity error. Aug 21 19:14:58 Lawpet kernel: [Hardware Error]: cache level: RESV, tx: INSN, mem-tx: IRD Aug 21 19:14:58 Lawpet kernel: mce: [Hardware Error]: Machine check events logged Aug 21 19:14:58 Lawpet kernel: [Hardware Error]: Corrected error, no action required. Aug 21 19:14:58 Lawpet kernel: [Hardware Error]: CPU:13 (17:8:2) MC3_STATUS[-|CE|MiscV|-|-|-|-|SyndV|-]: 0x9820000000000150 Aug 21 19:14:58 Lawpet kernel: [Hardware Error]: IPID: 0x000300b000000000, Syndrome: 0x000000002a000503 Aug 21 19:14:58 Lawpet kernel: [Hardware Error]: Decode Unit Extended Error Code: 0 Aug 21 19:14:58 Lawpet kernel: [Hardware Error]: Decode Unit Error: uop cache tag parity error. Aug 21 19:14:58 Lawpet kernel: [Hardware Error]: cache level: RESV, tx: INSN, mem-tx: IRD Aug 21 19:20:26 Lawpet kernel: mce: [Hardware Error]: Machine check events logged Aug 21 19:20:26 Lawpet kernel: [Hardware Error]: Corrected error, no action required. Aug 21 19:20:26 Lawpet kernel: [Hardware Error]: CPU:15 (17:8:2) MC3_STATUS[-|CE|MiscV|-|-|-|-|SyndV|-]: 0x9820000000000150 Aug 21 19:20:26 Lawpet kernel: [Hardware Error]: IPID: 0x000300b000000000, Syndrome: 0x000000002a000503 Aug 21 19:20:26 Lawpet kernel: [Hardware Error]: Decode Unit Extended Error Code: 0 Aug 21 19:20:26 Lawpet kernel: [Hardware Error]: Decode Unit Error: uop cache tag parity error. Aug 21 19:20:26 Lawpet kernel: [Hardware Error]: cache level: RESV, tx: INSN, mem-tx: IRD Aug 21 19:25:53 Lawpet kernel: mce: [Hardware Error]: Machine check events logged Aug 21 19:25:53 Lawpet kernel: [Hardware Error]: Corrected error, no action required. Aug 21 19:25:53 Lawpet kernel: [Hardware Error]: CPU:5 (17:8:2) MC3_STATUS[-|CE|MiscV|-|-|-|-|SyndV|-]: 0x9820000000000150 Aug 21 19:25:53 Lawpet kernel: [Hardware Error]: IPID: 0x000300b000000000, Syndrome: 0x000000002a000503 Aug 21 19:25:53 Lawpet kernel: [Hardware Error]: Decode Unit Extended Error Code: 0 Aug 21 19:25:53 Lawpet kernel: [Hardware Error]: Decode Unit Error: uop cache tag parity error. Aug 21 19:25:53 Lawpet kernel: [Hardware Error]: cache level: RESV, tx: INSN, mem-tx: IRD Aug 21 19:25:53 Lawpet kernel: mce: [Hardware Error]: Machine check events logged Aug 21 19:25:53 Lawpet kernel: [Hardware Error]: Corrected error, no action required. Aug 21 19:25:53 Lawpet kernel: [Hardware Error]: CPU:11 (17:8:2) MC3_STATUS[Over|CE|MiscV|-|-|-|-|SyndV|-]: 0xd820000000000150 Aug 21 19:25:53 Lawpet kernel: [Hardware Error]: IPID: 0x000300b000000000, Syndrome: 0x000000002a000503 Aug 21 19:25:53 Lawpet kernel: [Hardware Error]: Decode Unit Extended Error Code: 0 Aug 21 19:25:53 Lawpet kernel: [Hardware Error]: Decode Unit Error: uop cache tag parity error. Aug 21 19:25:53 Lawpet kernel: [Hardware Error]: cache level: RESV, tx: INSN, mem-tx: IRD Aug 21 19:25:53 Lawpet kernel: [Hardware Error]: Corrected error, no action required. Aug 21 19:25:53 Lawpet kernel: [Hardware Error]: CPU:13 (17:8:2) MC3_STATUS[-|CE|MiscV|-|-|-|-|SyndV|-]: 0x9820000000000150 Aug 21 19:25:53 Lawpet kernel: [Hardware Error]: IPID: 0x000300b000000000, Syndrome: 0x000000002a000503 Aug 21 19:25:53 Lawpet kernel: [Hardware Error]: Decode Unit Extended Error Code: 0 Aug 21 19:25:53 Lawpet kernel: [Hardware Error]: Decode Unit Error: uop cache tag parity error. Aug 21 19:25:53 Lawpet kernel: [Hardware Error]: cache level: RESV, tx: INSN, mem-tx: IRD Aug 21 19:25:53 Lawpet kernel: [Hardware Error]: Corrected error, no action required. Aug 21 19:25:53 Lawpet kernel: [Hardware Error]: CPU:15 (17:8:2) MC3_STATUS[Over|CE|MiscV|-|-|-|-|SyndV|-]: 0xd820000000000150 Aug 21 19:25:53 Lawpet kernel: [Hardware Error]: IPID: 0x000300b000000000, Syndrome: 0x000000002a000503 Aug 21 19:25:53 Lawpet kernel: [Hardware Error]: Decode Unit Extended Error Code: 0 Aug 21 19:25:53 Lawpet kernel: [Hardware Error]: Decode Unit Error: uop cache tag parity error. Aug 21 19:25:53 Lawpet kernel: [Hardware Error]: cache level: RESV, tx: INSN, mem-tx: IRD I don't know how to read all of this. Your help will be greatly appreciated. Thank you! Edit: Also worth noting is this Aug 21 19:58:22 Lawpet root: mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead. Solution update: Turns out I had a faulty CPU. Exchanged it and everything is fine now. So faulty Ryzens do exist -- am not sure if it is related to the segfault defect.