mrow

Unfortunately this did not make a difference for me. Once I started doing some hardware transcoding the server once again locked up after about 15 minutes.

Disabling the GPU on the SuperMicro board will break IPMI so that really isn’t a solution even if it fixes the problem. Also, I don’t know why it works for others but not those of us with this issue. But the fact that it works in other OS environments and not in the Unraid environment means it has to be something in the Unraid environment. What other conclusion could their be?

It’s certainly possible it’s related to IPMI. However, as I said, no issues occur in other OSes so it’s still some kind of issue in the Unraid environment. My server is located 4 hours away in a different state in a house that doesn’t always have people there so IPMI is not optional for me. I would be happy to try to troubleshoot this issue with the developers if they need any assistance.

This is not a hardware issue. Hardware transcoding works fine with other OSes. This issue only exists in Unraid. It is 100% a software issue of some kind in this environment.

The issue occurs independent of the application you’re using to transcode. It happens with me with Plex. It also happens to me with Handbrake.

I’m currently on 6.9.2 and I have an E3 1275v6 so that shouldn’t make a difference unfortunately. edit: current system specs:

Were you ever able to figure something out with your Intel GPU causing lock ups? I’ve been having the same issue.

AES-NI is required for version 2.4 and any future versions. They plan to maintain version 2.3 for a while to hold peopl over until they can upgrade their hardware. You could always use the hardware you have no and upgrade when you get some equipment.

Why not just pick up a cheap standalone box to act as your pfSense router? Then you don't run that risk. Backup your configuration in pfSense and restore on your new hardware and it'll be like nothing changed. Edit: oops, just looked at your most recent post and saw you're looking to do this already.

Can you give us the ability in the settings to set all the flags on our own? The -X flag to copy extended attributes is causing a ReiserFS error and thus causing a move to fail. I tried using my own flags but realized, after it failed again and looking at the logs, that putting custom flags in the settings page just adds those flags in addition to your standard flags. Please give an option for us to use only our custom flags. It’s not a huge deal. I’m just running the rsync operation from the command line for now.

Seems to be working ok for me on 6.4.0. Thanks StevenD!

When my parity was 8TB I used a Seagate Archive and then a WD Gold. Both were great but I did notice a bit of difference between the Archive and the Gold. I’ve since swapped the 8TB Gold for a 10TB Gold.

Once it dies go with a Ubiquiti wireless AP. Goes nicely with a pfSense router.

What about a Chromebook? There are quite a few RDP clients for ChromeOS.

I’m using one of these with pfSense. It only had a single Intel NIC so I removed the wireless card that was in the M.2 slot, popped out the VGA port from the back, and put one of these in the M.2 slot. That was the only M.2 NIC I could find with an Intel chip. The cable for the network port is fished through where the VGA port was. A little jerry rigged, I know, but better than using a USB Realtek NIC. It’s been awesome.