ChknNRice

Hey everyone. I'm running handbrake-for-nvidia and am doing my first transcode. I noticed when I kicked it off, it's barely putting a dent in my GPU and plowing my processor. Am I missing something here? :EDIT: Figured this out (I think) I threw a few questions at chat gpt and it determined that in my hardware/software configuration, a few things could cause this. 1. The p2200 can't transcode 8k video officially. 2. Scaling down resolution from 8k to 1080p is a CPU instruction, not GPU. To test chat GPT's theory, I transcoded a 1080p file down to 720p using the default 265 nvenc profile in handbrake and the opposite happened. The CPU barely budged and the GPU took the load.

I'm using the pro version which detects ECC corrections. Regardless, I haven't seen this error since so I'm not going to sweat it.

It passed 24 hours of mem test. And there's nothing in the IPMI logs. That last line tells me it's l3 cache erroring out.

Hey fellas. What turned out to be the issue here? I just got this in my syslog today. Unraid: 7.0.1 Jun 18 12:25:03 TrouxRAID kernel: mce: [Hardware Error]: Machine check events logged Jun 18 12:25:03 TrouxRAID kernel: [Hardware Error]: Corrected error, no action required. Jun 18 12:25:03 TrouxRAID kernel: [Hardware Error]: CPU:0 (19:61:2) MC22_STATUS[-|CE|MiscV|AddrV|-|-|SyndV|CECC|-|-|-]: 0x9c2040000400011b Jun 18 12:25:03 TrouxRAID kernel: [Hardware Error]: Error Addr: 0x00000002ffa22440 Jun 18 12:25:03 TrouxRAID kernel: [Hardware Error]: IPID: 0x0000009600150f00, Syndrome: 0x200020000a801202 Jun 18 12:25:03 TrouxRAID kernel: [Hardware Error]: Unified Memory Controller Ext. Error Code: 0, DRAM ECC error. Jun 18 12:25:03 TrouxRAID kernel: umc_normaddr_to_sysaddr: Invalid DramBaseAddress range: 0x0. Jun 18 12:25:03 TrouxRAID kernel: EDAC MC0: 1 CE Cannot decode normalized address on mc#0csrow#2channel#1 (csrow:2 channel:1 page:0x0 offset:0x0 grain:64 syndrome:0x2000) Jun 18 12:25:03 TrouxRAID kernel: [Hardware Error]: cache level: L3/GEN, tx: GEN, mem-tx: RD

I FINALLY figured this out. The USB controller which the pen drive was plugged into was bound to vifo and once the config started to boot and that portion was loaded per instruction, the USB stick became unreadable by the OS. Once I lifted the bound and rebooted the system, it booted clean on the internal port on the mobo I had been trying to use.

As long as I have it on the back of the motherboard it boots. I'll try this. Boot everything normally, move it physically, then run the plug-in. We'll see what happens on the next boot.

Hey everyone. Does this remount the drive after you move USB ports as well? I had a USB 2 port directly on my mobo (which I first used when I built out the OS). I then moved it to a port on the back of the mobo while I was doing some cable management and I forgot to move it back when I booted the system. It booted just fine on the back of the mobo, but after I tried to move it back to the internal port, it won't boot properly. Makes zero sense.

Hero mode. I have been struggling to find a way to get an SMB share from UNRAID to a QNAP NAS for backups. My unique case was that the 2 NAS devices were directly connected to each other on peer link. I just mounted the SMB share with unassigned devices and added the path info from the mount to the free file sync docker. Boom. I'm synching!!!