warpspeed

X13SAE-F works just fine with IPMI via remote VGA and iGPU for transcode. Just need to force the iGPU on in the bios and set primary display to VGA.

I appear to have hit two issues upgrading from 6.12.10 to 6.12.11. Issues only showed up after the upgrade and went away after downgrading. 1. nginx errors in syslog 2. nfs autofs mount not working from an ubuntu machine I posted about them here,

Hmm, I didn't even realise this was a bug when I upgraded from 6.11.5 recently. Now I'll have to go check my own content and see what mess has been made. It's pretty disappointing that this wasn't fixed in 6.12.11 given the time frame around when it was raised. Or at least flagged as a known issue for 6.12.9 onward.

Can confirm these settings also work for me using a X13SAE-F Bios 3.1 and unraid 6.11.5. Only difference is the "PCI" setting is called "PCH PCI". I've not tried hardware transcoding yet, but the IGFX is exposed to unraid and the BMC VGA console still works.

Anyone with a X13SAE-F come up against this issue?

Hi folks, I've seen a few posts from folks using the X13SAE-F motherboard, I'm curious to hear any feedback or possible gotchas from folks about the X13SAE-F with Unraid, as I'm considering a CPU, RAM, Motherboard refresh using the X13SAE-F I intend to use it with the following: Intel i7 12700 CPU (with Noctua NH-D9L heatsink) 2x Micron 32GB DDR5 4800MHz ECC UDIMM 2Rx8 CL40 Server/Workstation Memory - Model# MTC20C2085S1EC48BR Plus existing LSI 9201-8i in IT mode In particular, interested to know whether this all works properly for folks running the latest versions of unraid (6.12.10). My current system is running 6.11.5, but I may upgrade that soon, my intention is to maintain my current system and swap out the motherboard, ram and cpu. I have 3 dockers and no VMs at the moment. After upgrading, I intend to run some more dockers and a couple of VMs. I want to use the iGPU for transcoding from plex docker. Also considering the onboard M2 slots for some fast cache.

Take a look at the tailscale plugin, easiest way to solve your challenges

Are you able to clarify exactly what this means. It it in the Docker containers advanced settings, the paths, variables, ports, etc, if there's fields defined and present but with no value in them? If thats the case, is it resolvable by defining or deleting those instead of installing the plugin? If we want to keep those around, is it possible to install the plugin before upgrading so things don't break?

I'd like to see some significant effort go into improving the UX for the features that Unraid currently has, along with working on nothing but bug fixes for a while. In particular, I find that whenever I have a problem with my unraid server, e.g errors or a drive dying, I need to refer to the forums or reddit for good info and understanding on what to do, to not stuff anything up. Really, this should be embedded into unraids web interface. If something happens it should do its best to tell me the details of whats gone on and whether theres an issue, along with suggested corrective actions - including the order in which to do the corrective actions, etc. It'd also be good to see a concerted effort go into making unraid really stable and sort out the issues folks have. I'd like to see the update mechanism have channels for development, latest and stable. Where stable is only extremely mature versions with no known bugs for some time. I have always found myself staying behind due to the issues I see on the forums here. I never upgrade to .0, .1, .2, or even .3 releases. It's only after then that I start becoming interested. With the latest 6.12.6, I'm still skeptical, there still seems to be a large number of outstanding issues that some folks are having. I'm currently on 6.11.5 and have been since it was released. Prior to that I was on the 6.9 series.

unbalanced should probably have a fresh thread with a closing post in this one linked to the new thread, then update the new plugin to the new thread

Anyone confirm this is working on 6.11.5 yet?

I'd really like to see some focus on improving self-guidance and help in the web UI, especially for problems, errors, etc. Generally when unraid works, there's not much reason for this, but I've found in almost all instances when I want to make major changes and/or if I get errors (SMART, read, write, etc.) or disk offline, etc. I find the first thing I need to do, is visit the forums or google to discover and understand where I actually stand with it and what my options are. It'd be really good if some effort could perhaps go into making the web UI a little more informative and user friendly... perhaps providing steps or guidance on some common things. A good example was a little while ago I had some read errors from my parity drive during a parity check. No write errors, just read. I didn't know what that actually meant for me. So I spent time looking in the forums and also googling. Google led me to a post on reddit or in the forums where someone described what unraid actually does when it gets a read error, and how it applies to that situation. I was thinking it'd be really good if the web UI actually had guidance like this. e.g rather than just popping up a red alert saying errors... read error... that it could actually pop up, explain the read error, what it most likely is, the fact that there was no write error, and that it could be indicative of a possible issue, what to keep an eye on, and any other sensible recommendations. Thats just one example, there are plenty more of things like that where some steps or guidance or even wizard like steps could be useful. Some things like this may also help unraid become a bit more mainstream too, and would help improve unraids core and primary feature... it seems these days that all effort is going into adding bells and whistles to support ever growing and more complex environments, dockers, vms, etc. while there are likely a whole swag of usability improvements that could be made to the UI for the core features.

is there a way to migrate from the docker to the plugin without the tailscale ip changing?

That's good to know BLKMGK, I'm still sitting on 6.9.2 but now considering upgrading to 6.11.4.

I have a suggestion for Fix common problems upgrade assistant. I read in another thread somewhere that there's a XFS programs update or similar between 6.9.x and 6.10/11.x, which caused some folks arrays not to mount due to some minor forms of corruption. I wonder if a XFS check could be run across array drives by upgrade assistant (or even just by fix common problems) to make sure this isn't an issue.

I upgraded from 5.0.5 straight to 6.1.9 on Sunday. I did it by shutting my server down, backing up the config off the stick, formatting and putting a fresh 6.1.9 on, then copying back my key and config files. It's worked fine so far. With one exception, needing to add sec=sys to my NFS RW exports.

I pre-cleared three 3TB disks all at the same time, using screen. Worked a treat. Here's the results. Which, I believe are good based on what I've read. Intending to use the Seagate as my Parity drive and the WD-RED's for data. Going to get some more WD-RED's as well, just want to get a different batch. Interesting to see the difference in SMART values between the Seagate and the WD RED drives. Also the difference in timing. I started all three of these drives within about 3-5 minutes of each other. == ST3000DM001-9YN166 == Disk /dev/sdb has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 65536 Bytes == Last Cycle's Pre Read Time : 7:00:56 (118 MB/s) == Last Cycle's Zeroing time : 5:16:14 (158 MB/s) == Last Cycle's Post Read Time : 13:35:56 (61 MB/s) == Last Cycle's Total Time : 25:54:07 == == Total Elapsed Time 25:54:07 == == Disk Start Temperature: 31C == == Current Disk Temperature: 32C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 116 102 6 ok 104832976 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 99 100 0 ok 1 Airflow_Temperature_Cel = 68 69 45 near_thresh 32 Temperature_Celsius = 32 31 0 ok 32 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. == WDC WD30EFRX-68AX9N0 == Disk /dev/sdc has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 65536 Bytes == Last Cycle's Pre Read Time : 8:48:12 (94 MB/s) == Last Cycle's Zeroing time : 7:39:59 (108 MB/s) == Last Cycle's Post Read Time : 16:22:01 (50 MB/s) == Last Cycle's Total Time : 32:51:13 == == Total Elapsed Time 32:51:14 == == Disk Start Temperature: 29C == == Current Disk Temperature: 29C, == ============================================================================ No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. == WDC WD30EFRX-68AX9N0 == Disk /dev/sdd has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 65536 Bytes == Last Cycle's Pre Read Time : 9:03:15 (92 MB/s) == Last Cycle's Zeroing time : 7:53:56 (105 MB/s) == Last Cycle's Post Read Time : 16:48:33 (49 MB/s) == Last Cycle's Total Time : 33:46:46 == == Total Elapsed Time 33:46:46 == == Disk Start Temperature: 28C == == Current Disk Temperature: 27C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 123 122 0 ok 27 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change.

Joe, in some of the doco, it mentions fro drives over 2.2TB that GPT/4K alignment is forced and the -a and -A options are ignored. I just started a pre-clear on some 3TB drives, and found that I still needed to use the "-A", and that it wasn't ignored. When I first ran pre-clear, it said that it would not 4k-align the drive. It was only after I added "-A" that it said it would. Using pre-clear 1.13 with command like so: ./preclear_disk.sh -r 65536 -w 65536 -b 2000 -A -M 4 /dev/sdc on a clean, brand new unRAID 5.0-rc15a (spun it up initially just to clear these new drives)