lukemattle

This is fixed by updating to v24.12.1

This is fixed by updating to v24.12.1

I set a memory limit of 4GB and while this stopped Handbrake from crashing my server, it did not stop it from crashing itself. Here are the relevant logs: logs.txt

Setting a memory limit of 4GB successfully stopped handbrake from crashing my server but it did not stop Handbrake from crashing. Here are the relevant logs: logs.txt

Ok, thanks. Would setting a memory limit of something like 4GB for handbrakes container fix it? EDIT: Well maybe not fix it but make so it can’t crash my server

I upgraded to 6.12.14, changed to ipvlan and started Handbrake again. This time I happened to be looking at the dashboard when it crashed: RAM & CPU usage suddenly jumped up to 100% (from about 48% on RAM and 80% on CPU) as shown in the photo. Attached are the logs of this crash, hopefully there is something of value in them this time. syslog-previous(1)

Coming from this thread: My Unraid system only crashes when I am encoding using Handbrake and running a stress test doesn't cause any issues. Does anyone have any ideas? Logs and diags in the original thread. EDIT: I happened to be on the dashboard when it crashed and I saw that RAM & CPU usage jumped to 100% (and then it crashed)

I ran it overnight and it didn't crash. Any ideas why it crashes when I am using Handbrake?

I’ll start a stress test using corefreq. I’ll report back if it crashes or if it manages last the night without crashing. Was there nothing useful in the logs to indicate why it crashed?

I have NetData tracking CPU temps and they never went above 58C before crashing.

When I am encoding video using Handbrake (docker, jlesage/handbrake), after 2-5 hours Unraid crashes. I enabled writing logs to the flash drive after the last crash and I have attached the logs of the most recent crash. My BIOS is up to date and my memory passed a pass of Memtest86+. The attached diagnostics were made when I booted Unraid after the most recent crash. Any help with this is greatly appreciated. tower-diagnostics-20241204-1509.zip syslog-previous

Crap. Can't believe I had a power cut at the worst time. Luckily I have backups of anything that I cared about. Thanks for your help.

What does it say I ran a format on? All that happened to my knowledge is that my power went out and when it came back on, it was doing a data rebuild. Earlier I mounted the drive to unassigned devices to see if it had anything on it, would that have formatted it?

I believe it has mounted. Here are the diagnosticstower-diagnostics-20240620-1243.zip

I just had a power cut and when the power came back on, it started the array with disk1 assigned to the new WD drive (which unraid said was too small before the new config) and is now doing a data rebuild. Should I let it continue?

Don't suppose you know if an HGST HUS726060ALE614 6TB would be the same size/bigger than my old WD? I can't find the exact size in bytes anywhere and that is the only 6TB drive I can pick up for a reasonable price.

Would you explain to be what exactly I need to do to get my data back please? Also, why does all my data not appear when I unassign disk 1, as the parity should be valid with the parity drive (sdc) and disk 2 (sde), nothing should have been wiped. Thanks for all your help so far

So if I buy a different 6TB disk (or larger) will I get my data back?

After looking through my share it looks like most of my files are gone. Do they still exist on the parity drive?

Here are the diagnostics after completing the steps above:tower-diagnostics-20240620-0917.zip

I believe my parity is still valid but the thing that worries me is that when I tried to replace disk1 without the new config, it said that the replacement disk was too small despite it being the same model of WD Green 6TB. Should I still proceed with your instructions?

I found a file called disk.old in my boot device under /boot/config, would this be of any use?

Unfortunately, I do not have the old disk1 as it had to be returned before I recieved the new drive EDIT: I know I've been stupid by making a new config but is there any way at all to get the data back?

One of my drives (disk1) showed some SMART warnings so I returned it and got sent a new one. When I plugged the new one in, despite it being exactly same model of drive, it said the replacement disk was too small. After some poking around on the forums I saw someone suggesting to use "New Config" to fix this (I created a New Config preserving all current assignments). However, after doing this, it says that all existing data on my parity drive will be overwritten when I start the array and I don't want that to be overwritten as I'll lose all my data. I haven't done anything after creating a New Config as I don't want to lose anything. Can anyone help me please? tower-diagnostics-20240619-1620.zip