A.sch3

Thanks for this topic ! Now I really use my 5700G iGPU. BUT how about VRAM of this GPU ? Do you have to set it to a high value in the BIOS ? Its currently have 480Mb of VRAM allocated. I though this was dynamic in some way, but no. And converting a 4k movie takes for ever and the iGPU usage doesn't go above 10%. I think this is due to the VRAM usage that needs to go higher ?

On a side-note, the power consumption is now much higher than it was before the BIOS update. I guess the c-states are disable by default. I will try to modify the BIOS setting because I'm anxious about seeing so much current going into this Unraid server that was pretty economical for me so far.

My system is still stable after the previous week of random crashing. I guess the BIOS update did the tricks.. Thanks @JorgeB for the additional information.

Just a heads-up : No crash since yesterday. Which is encouraging I guess. Apart from the BIOS update, I haven't took any measure yet.

Thanks for the reply ! My ram is running at default speed 2133Mhz I believe, I haven't enable SMT or any "game boost" thing on the mobo. But thanks for the link, I'm not sure about what should I do about my ram frequency. I'll check out the power setting thing next. It seems like I provided the yesterday diagnosis zip file (nothing changed since yesterday but still, here the up to date diag.zip file), but the today syslog.log was the one saved by syslog server on my other unraid server. The memtest finished without errors by the way. exposed-diagnostics-20240724-1832.zip

Hi, I had this unraid server since a few month, on 6.12.10, solid like a rock until this : (I will underline bullets point so it is easier to diagonally read) Modified pretty extensively the hardware a week ago : - Motherboard swap (MSI MAG b550) - Same CPU (AMD 5600x) - Adding a RTX 3090 - From 16g to 32g of RAM. - Swapping Power supply to a nicer one, platinum 850W from ASUS. As you maybe guessed, I was in the process of building my own multi-purpose AI box. Booted first time after hardware changes, going strong for about 3 days then the server crashed without any apparent reasons. I forced shutdown the server then rebooted -> All right, maybe it's a glitch, let disable all AI thingy dockers. 1 day later, it crashed again. Reboot, less than one day later -> crash. And again today. I'm in the process of diagnosing the ram with a memtest but I don't believe this is a ram issue. I remember having a similar issue when I had the Unraid server on a AMD 1700 : I had to disable C-states and also adding some code at boot. As it was felling similar, I updated the motherboard BIOS which was 2 versions behind, so no biggy. I'll keep you updated on news on my side. This could help others with similar issue as well. Thanks for reading. syslog-192.168.20.125.log exposed-diagnostics-20240721-1858(1).zip

Oh ok. So a backup should contain what I need to create a new flash drive with my current config manually. Which is what I did while not knowing I was. I checked on my previous backup of the faulty flash drive, and I can see the sames files and folders inside the archive than the one present on the physical drive. In this end, I guess the unRAID tool failed to properly restore the flash backup zip file because of files corruption ? And me manually copying the old drive content to the new one, replacing existing duplicate just finished the normal process. So nothing to worry about ! Thank you JorgeB and JonathanM for the insights, I now know better !

Thanks for the reply ! This is where I downloaded the backup zip file : But I'm kind of reassured and worried at the same time : the config folder didn't contained my config present in the flash backup zip file I downloaded ?

Hi, What I did worked, but it was a weird process from my perspective and would like to know if I might have done something wrong ? tl;dr -> Used the unRAID software to restore a flash backup. Didn't really worked so I copied every file I could from the old->new flash drive. It worked to my surprise, but is it ok ? Long story short : I had a 2Gb flash drive with the Unraid OS and License. Crappy flash drive. Started to got "bread directory" warning from Fix Common Problem, read online that I could be caused by a bad flash drive (although unRAID never failed to start and never crashed). So I got myself a Samsung 32Gb recommended by SpaceInvaderOne on his video about USB drive reliability and got to it : 1 - I downloaded the backup zip file from the flash itself and followed the procedure from unRAID's guide. 2 - Opened the flash utility on my windows machine, put the zip file in, go. 3 - Remove the 32Gb flash drive and put it in the server, same place as the old 2Gb flash drive. 4 - Started the server 5 - The server failed to boot. Plugin a monitor revealed that the countdown to start unRAID OS kept looping back on itself. 6 - Tried to manually press enter to any of the option of the boot menu (safe mode, memtest, etc...) but nothing. 7 - So I plugged back the 2Gb flash drive and, as expected unRAID booted up. 8 - Remove every flash drive from the server and plugged them in my windows machine to compare the folder and files structures. Huge differences ! 2Gb flash drive : 32Gb flash drive : (Actually this picture is a reconstitution, there was other folder there I recall, but no files for sure). So... I just copied the entire content of the 2Gb drive onto the 32Gb one. I clicked "Yes" when windows prompted me about same named files. 2 or 3 files failed to be copied from the 2Gb, I clicked Ignore to carry-on. I didnt noted which file it was as it felt to be pointless anyway. So : 9 - Plugged the 32Gb drive back into the server and.... 10 - unRAID booted like a charm. (My on the floor staring at the screen suspiciously waiting a crash that never came.) Did I made this USB swap right ? Is my unRAID at risk of file corruption or whatnot ? It's been 3 days now and It seem to work just as before, except maybe the UI is kinda slower but that could be due to any other reason as I am aware that unRAID run from the RAM and not the flash drive itself. Thanks for any insight !

About the same question for me, and plus Fix common problems found a new error that is related to this driver : I guess it is now safe to remove it ?