Omid

In case it helps: https://www.reddit.com/r/unRAID/comments/1eqkd8q/comment/m4t3m1x/

So I've completed all steps, booted up with the new flash drive, containing all files from the last backup but with the Pro.key that I just had generated. I saw my non-default login screen, which was a great sign. However, my managed-password wasn't being accepted. It's only when I locked myself out that I thought I should try the new root password that I set on the fresh install (that I replaced?). To try that, I attempted to ssh in to the server with the new password and it worked. How on earth is the new password from the new installation the one that is accepted when I replaced all files on the drive with the backup? Something to do with how/when unraid's boot sequence creates and mounts /etc/shadow? I still don't fully understand how, but all is good. I seem to be up and running again. Thanks for the guidance, @Kilrah

Ok, here I go... <holds breath>

The Unraid USB Creator doesn't allow me to select anything < 6.12.9 ☹️ I have an unresolved stability issue for >6.12.5 Can I not format the new flash drive with the backup zip I have and then activate with the new license?

Thanks! I was on 6.12.5, so I'll setup the new flash drive with the same version. What about all of the data drives in the server? Will they be okay with this process? I'm nervous doing this given the amount of data, apps, VMs and history at risk. Now that I have my latest backup as a zip, is there a file in there that will help me confirm the exact version I was running?

My USB flash drive finally failed after 12 years. I had a Pro license key attached to it which was purchased for me by a friend, so it's not in my name and not attached to my account. Last year, I realised this is not completely compliant (sorry!), so I purchased a new Pro license key last year in anticipation of my flash drive eventually seeing its end. I now have my replacement flash drive in-hand and want to get the server running again, however, I would like to restore the backup onto this new flash drive, but use the new yet-to-be-activated license that I purchased last year. What do I do? Can I restore my flash to a new USB drive and use a different license key, or must I contact my friend to switch the GUID on the old license key? P.S. How do I download the latest flash backup from Unraid Connect? I can see the Last Flash Backup date but no button to download it. Only a button to generate a new backup. "Generate Backup" = download backup

Thanks @JorgeB Just blindly upgrading to 7.0.0 has crossed my mind, but without a RCA I feel like I'm shooting in the dark and just being hopeful 😅. To be honest, I'm already quite exhausted from what I just went through the last 3 weeks and can't really afford to upgrade and then [inevitably] downgrade all the way back down to 6.12.5; reading through all the rollback notes of each version, juggling plugin versions and tweaking settings, etc. I'm going to hold on to 6.12 for now and see how things evolve in the coming months. I'm extremely surprised this issue isn't discussed more in the community, as I suspect the cause to be something pretty standard/common. @NewDisplayName Nope, not using fritzbox (and hadn't heard of it until now). I have 23 apps (Docker) and just 1 Ubuntu VM I use as a dev box for (VS Code server). Most intensive regular task performed by the server is probably Plex transcoding my home/family videos (when requested by one of the ~10 family members it's shared with). And yeah, the really sudden crash means syslog and diagnostics don't really help. Even my remote syslog just cuts off abruptly sad times Please could you share your system specs? Or review mine in the OP and let me know what hardware we share?

I believe to have enough data to conclude that upgrading to Unraid 6.12.10+ is the cause of my crashes. I know that 6.12.11, 6.12.13 and 6.12.14 all cause crashes. I know that 6.12.4 and 6.12.5 are stable. I don't know about the versions between 6.12.5 and 6.12.11 What to do from here? I can't afford to upgrade to a bad version to troubleshoot further. Do I just never upgrade?

I don't want to speak too soon, but I think the crashes started when I upgraded Unraid 😥 It's so far been stable since I downgraded to 6.12.4 Lesson learned: don't remove HBA BIOS, disable CSM in motherboard and upgrade Unraid on the same day, especially when you're model of CPU is also known to have problems.

Please could I survey what CPU, BIOS and Unraid version people are using with this motherboard? 13700k BIOS 4001 Unraid 6.12.4

Okay, I'm back on 6.12.4... Still on the 14700k but will switch back to my 13700k in near future.

So the issue is either with my motherboard, PSU or Unraid? I'm quite suspicious of the fact that opening the Unraid web GUI sometimes triggers the crash. I should try rolling back 6.12.4 (last known stable version) before replacing any other hardware.

...and it crashed again, so my CPU isn't the problem.

14700K installed...

My Unraid system has started to randomly crash multiple times a week, both when untouched (with things running of course) but also when performing one specific action -- loading the web UI. Diagnostics attached. Graph showing frequency of crashes. Variable recovery time is due to me needing to manually start the array, as these health checks require a specific container to be running (which requires the array to be started). System specs: https://uk.pcpartpicker.com/user/oatie/saved/#view=RfbCD3 ...and because they're not available to select on PC Part Picker: Motherboard: Asus Pro WS W680-ACE IPMI HBA card: LSI 9201-8i What I've tried: Rolling back to older Unraid versions: 6.12.13 and 6.12.11 still yield the same behaviour. Has the 6.12.4 release been pulled/withdrawn? Switching my Docker network from macvlan to ipvlan Running the Plex container without passing through the iGPU device, so that the iGPU remains idle (not used by any other workload on the server) 4 successful passes of Memtest86 that is bundled with Unraid. This is after running 2x 4 passes of the then-latest version of Memtest, over 2 days, when I first build the system and before I moved Unraid into it. I'm pretty sure the ECC DDR5 RAM is okay. Sending syslog to my secondary Unraid server (attached) -- I don't see anything in there relating to the crashes. The system crashes so hard and fast that I'm guessing there's no time to log anything I've tinkered with a bunch of BIOS settings that I thought might be relevant, but with this system once being stable, I don't think that's the issue Some history/context, in case it helps I built this system when I re-platformed my 2012 Unraid server, so I've been through and seen a lot. I've never experienced such severe issues in >12 years of running Unraid, since v5! It came to storage expansion time, so I ordered the LSI 9201-8i to replace two SATA cards I had (which were faultless in both the original 2012 and new 2023 system, but the community persuaded me SATA cards are evil and I followed) I had some challenges and quirks to get through to have the HBA card fully working, ultimately resulting in needing to enable Compatibility Support Module (CSM) on my very modern motherboard for it to detect the ancient HBA card. Everything seemed to be working fine and was stable, except it took me weeks to realise my media transcoding was no longer using the iGPU and my CPU was regularly hitting 100% and 90°C After a lot of experimentation, I realised the iGPU would be disabled or not detected during boot when CSM was enabled. However, now that my array was spread across the HBA, I couldn't just disable CSM to get my iGPU back because I won't be able to start the array I left it in this state for many months, giving up my iGPU in favour of a running Unraid system with CPU transcoding Meanwhile, the whole Intel 13th/14th gen fiasco was happening and I was keeping an eye on motherboard BIOS updates for the microcode fix I recently (Christmas 2024) stumbled upon a random forum post where someone suggested removing the HBA card's BIOS to improve boot up speed and not require CSM. I was super excited, so worked quickly to get the HBA's BIOS removed and disable CSM I was finally booting into Unraid with all my drives, able to start the array and take advantage of the CPU's iGPU - success! I took the opportunity to upgrade Unraid from 6.12.4 to 6.12.14 I walked away and it was a day later when I woke up to see my Unraid server had rebooted and was waiting for me to manually start the array Since then, I've been scratching my head, reading many Unraid forum and Reddit posts, whilst trying the things I mentioned above. The only thing I've not tried yet and can't see an easy approach for is to roll back to 6.12.4 which I know for sure the system was stable with prior to removing the HBA's BIOS. I had not previously run 6.12.11, 6.12.13 or 6.12.14 until I starting booting with HBA and iGPU (CSM disabled). Sometimes opening the web UI only to hear the faint "tick" from the server and see the page not load completely (because of a crash) makes me think this is an Unraid/Linux kernel issue -- but that doesn't explain why I once had stability with months of uptime. Could removing the HBA's BIOS really have something to do with it? A 14700K should arrive today so I can confirm my 13700K isn't a victim of the Intel microcode issue/burnout. I have an open RMA for the 13700K, on the assumption that it is already toast, but I've been told they will run tests on it to first confirm an issue before sending me a replacement. However, if the issue is Unraid, they won't find an issue with the CPU and will send it back to me. I am hesitant to send it off if I experience the same issue with the new 14700K I have separately bought. I'm running out of options and getting desperate Thanks in advance. Sorry for the mega post. unraid-diagnostics-20250111-1701.zip syslog-unraid.log

As mentioned by @GraemeT, you won't need an HBA card for 8 SATA drives. I've been using this cable (UK) with the W680, driving 4x WD RED 8TB drives for 18 months, without any issues. There's just one simple setting you have to toggle in the BIOS; specifically, this one. Like @1adam12 said, you have more flexibility to further expand with an HBA in future, should you ever need to. I disagree that an HBA is just easier, though 😏 With an HBA, you're still most likely going to need to buy a cable or two in addition to the card. Installing my LSI 9201-8i HBA was definitely not easier, as it requires figuring out that CSM needs to be enabled which, in turn, disables the CPU's integrated graphics 😢, causing me a problem to this day (no hardware transcoding (!). However, I've just seen this proposed solution which I'm excited to try out! I remember my 13700k's iGPU (UHD 770) was handling 8+ transcodes (mix of 1080 and 4K) without breaking a sweat and I'm not the only one. I agree with @GraemeT - keep your wallet happier by not buying a dGPU and paying lower energy bills (if you're into that!). Unless you have a use case other than Plex, in which case you do you 😄

Yes, I think I tried that many months ago but I'm so confused by everything I've tried that I might give that another go. I feel this is more related to CSM, though, as opposed to the IPMI card. Thanks! I'm not familiar with the 9300-8i specifically, but I don't see why it wouldn't fit. It should fit in all slots except for the small x1 slot closest to the CPU. Have you tried fully opening/unclipping the retention tab and then slotting the card in? To hopefully get better help from others, please clarify which exact model of this motherboard you're using. The ATX or mATX version?

It had been many months since I tinkered with my setup, but I finally found some time for it today. I'm still not able to use the integrated graphics of my 13700K with my configuration and can't find a solution. One more cry for help on this thread since there are more users of this board... Asus Pro W680 ACE IPMI (ATX) Intel 13700K LSI SAS 9201-8i HBA Asus IPMI expansion card unRAID 6.12.13 (just upgraded from 6.12.4) The only way I can get the SAS card to show up during boot/POST and unRAID is if I enable CSM. With CSM enabled, however, I can't get the iGPU working. It's never detected in unRAID and I even see the output of a failed chmod command for /dev/dri with "no such file or directory" during the unRAID boot output. I have tried the "ast blacklist" config, too. Note that enabling CSM will also completely hide the "iGPU Multi-Monitor" setting in BIOS. I currently have the IPMI card in the bottom x16 3.0 slot, with the SAS card in the slot immediately above it, also x16 3.0. I've tried different combinations of slots, including using the top two x16 5.0 slots. I'm yet to try only removing the IPMI card, as that's quite annoying with all the cables. I'm thinking IPMI is "taking" video output responsibility, somehow disabling or not allowing the iGPU to to turn on. Just want to check if anyone has this combination working? iGPU + LSI SAS 9201-8i (with CSM enabled) + IPMI Do the 9207-8i or newer models require CSM? I [stupidly?] went with the 9201-8i because it meets my technical requirements whilst having lower power usage and generating less heat.

You will have both. The PWR and RST wires from your case/chassis' I/O plug into the IPMI card, where two other wires are then connected to the motherboard's PWR and RST pins. I can't currently check to answer your other questions.

This is less of an issue but I've just noticed the duration is inconsistently reported between the two as well. The GUI shows "16 hr, 35 min, 56 sec" whilst the notification shows "16 hours, 47 minutes, 6 seconds". Comparing the duration of random historical parity checks against old email notifications confirms this isn't a one-off.

v6.12.4 The email notification received after a regular scheduled parity check had the subject line "Notice [UNRAID] - Parity-Check finished (0 errors) " which, according to the unraid GUI, is wrong, unless "errors" here is referring to something else. Event: Unraid Parity-Check Subject: Notice [UNRAID] - Parity-Check finished (0 errors) Description: Duration: 16 hours, 47 minutes, 6 seconds. Average speed: 132.4 MB/s Importance: warning versus This is potentially dangerous, as it means administrators won't be informed of sync errors unless they look at the GUI. Is this a bug? As a side note, there doesn't seem to be anywhere which indicates if these errors were "detected" or "corrected" (defined by how the parity check was run). Is this a feature request?

I think I have a very similar scenario and I can't find a way forward ☹️ slowly going from "this will be a fun challenge" to "this is very frustrating". I had iGPU and Quick Sync working fine with the W680 ACE IPMI motherboard. I also had video output working through the IPMI card, both via the KVM and with a monitor plugged in to the card's VGA port. I then added an LSI 9201-8i HBA card and really struggled to get it working but finally got there with help from the community. At least that's what I thought, until a couple of weeks later when I noticed unRAID couldn't see the iGPU and all transcoding was done by the CPU (an easy oversight). tl;dr: I needed to enable CSM for the HBA to properly initialise and attached drives to be detected by unRAID. I never checked if the iGPU was detected with the HBA installed and CSM disabled, because I never started the array due to drives not being detected, but I have a strong feeling this is caused by enabling CSM and not simply having the HBA card in. Trying to move forwards, I'm a little suspicious of the Graphics Configuration page in BIOS, because it makes no reference to CPU graphics at all. It's not one of the options in the drop-down and the iGPU Multi-Monitor field isn't there at all (I'm almost certain I recall it being enabled when I first installed this build, before all the HBA and CSM madness). Here is what I see: I've tried booting with all 3 options but nothing changes. It's as if the iGPU isn't detected or initialised during POST/boot. Any advice, comments or thoughts would be appreciated, before I go crazy(!). Thanks in advance!

Before: After: This was the solution and I got everything up and running back then, but I learned of a problem after a few days that was difficult to notice at first... My iGPU isn't detected/active/working anymore. I've not rebooted, checked BIOS settings or tried anything yet but I know it's not working because the GPU Statistics plugin now just shows "Vendor command returned no data." and the output from the intel_gpu_top command aligns with this. root@unRAID:~# intel_gpu_top No device filter specified and no discrete/integrated i915 devices found root@unRAID:~# ls -ltrah /dev/dri/ total 0 drwxrwxrwx 2 root root 60 Dec 16 02:15 by-path/ drwxrwxrwx 3 root root 80 Dec 16 02:15 ./ crwxrwxrwx 1 root video 226, 0 Dec 16 02:15 card0 drwxr-xr-x 16 root root 4.6K Dec 17 14:37 ../ I know it was working for many months until I installed the LSI HBA card, so it's either the presence of the card or enabling CSM (or both?). I'm going to try the following: Just a simple reboot (not expecting this to fix it) Unplug VGA cable from the IPMI card and reboot Plug something in to the motherboard's VGA/HDMI port and reboot Play with BIOS settings (?) Any thoughts/ideas from people here?

@JimmyGerms Thank you so much for trying this out for me. I'm super confused at the different result but appreciate the effort nonetheless. I already had Fast Boot disabled 🙂 but thanks for the inputs, @maydaytek! I've actually shared all of my BIOS changes in an earlier post on this thread (in case anyone is interested). Nope, I've never put a dGPU in this build. Only using the 13700K's iGPU. @jlarmstr Wait, what? Supplemental power for the 9207-8i?

Resolved! CSM and legacy mode PCIe did it. Will post again later...