Mattaton

I'm not sure if @hernandito has updated the names of his custom files to work with the newest plugin version. Files have to be named like my.docker.css in order for the plugin to pick it up.

It still works with earlier versions but is no longer under development. FolderView is the new hotness. 🙂 Be advised, this is a completely separate plugin. I'm not sure if there is a clean way to move your folder order from Docker Folder to FolderView.

You need to uninstall Docker Folder and install FolderView. I think as of 6.12.3 Docker Folders is a no-go. Thankfully @scolcipitato picked it up and ran with it. 🙂

You can see what dockerMan in unRAID has for the autostart order here: /flash/config/plugins/dockerMan/userprefs.cfg I would not edit that file, though. Not sure if that's kosher or not. Between dragging and dropping the folders (or containers that aren't in folders) on the docker page and then dragging and dropping the containers inside each folder on the folder's config page, you are setting the order you want for autostart. However, whenever you add a folder or make a change to the order inside a folder, you want to unlock the docker page and randomly move something, relock, and then unlock again and move things back the way you had it, and finally lock it again. This last random move and move-back is what updates that userprefs.cfg file to lock in the order you see on your screen. Once the order you see matches the order in userprefs.cfg, the autostart sync icon turns green letting you know what you see is what you'll actually get.

The order for the folders themselves are handled on the docker page. You have to unlock them with the padlock icon, drag and drop to change order, then lock them again.

When you first create a folder it will come up at the top of the container list, but that is NOT the same as the autostart order. That makes the icon red to let you know what you see is not the order they will actually start in. Once you change the order of folders or containers in the list, the auto load order is updated to match what you see, then the icon turns green.

I am on 6.12.4, but I hadn't done the disable bridging settings and all that. I'll see if ipvlan causes any issues and only switch if I have to. If there's no real advantage to being on macvlan, I don't need to stir the water. 🙂 Thanks!

It was indeed set to macvlan. I don't know what my reasoning was for keeping it on macvlan other than thinking this was important, since I do access things on the local network from some of my containers. At any rate, we'll see if this gets rid of the frequent crashes. Thanks!

Makes total sense. Just surprised me since I remember going through the release notes and those settings. Maybe I didn't save the changes. I have no idea. 😄 I hope that's the problem because it's an easy fix!

I'll have to get my server back up, but I'm pretty sure I had already switched to ipvlan given the warnings/instructions in the latest release info. I'll give it a look as soon as I get things running again. Thanks

....AAANNNDDD it just went unresponsive again. I think full crash this time. Uuuggghhh, I feel sick.

Not sure if this is connected, but I'm seeing this one core pegged for several minutes now.

I've been having issues for the past couple weeks where my server would crash and on the connected monitor there would be references to Kernel panic. See this thread: https://forums.unraid.net/topic/146044-past-two-days-server-crashes-with-kernel-panic/ I had checked all drive SMART data, several parity checks were perfect, so I assumed it had to be hardware issue. So, I replaced the motherboard, CPU, and RAM with an Intel-based setup to rule out AMD-based issues. Now today I tried to log in to my server and it took forever to load the GUI. I also couldn't SSH into it. After 5 minutes or so, the webGUI finally came up. I checked the logs and it's full of kernel lines. Diagnostics attached. Lines like this with a bunch of other stuff that means nothing to me: Oct 11 09:54:00 TyreeMedia kernel: CPU: 13 PID: 6398 Comm: kworker/u40:0 Tainted: P W O 6.1.49-Unraid #1 Oct 11 09:54:00 TyreeMedia kernel: CPU: 5 PID: 15710 Comm: kworker/u40:4 Tainted: P W O 6.1.49-Unraid #1 Any help is appreciated here. I hate to think I spent all that money to switch to Intel just to have it still do these kernel errors. Thanks! Matt tyreemedia-diagnostics-20231011-0955.zip

I let it sit for 30 minutes or so on two different systems. If I refreshed the page and tried again it did the same thing. All that being said, it now works absolutely fine on both. Go figure!

Great! Thank you so much for the help and insight!

So, what you would do is ditch the 1070 and go back to two 9211-8i cards, right? No expander.

Perfect. Exactly what I needed. Thanks!

I'm tring to google this, but seems like everything is just talking about NOT using the x1 slot. Since I have the x4 slot, will this take just that for power, or does it have to have the molex and only the slot is optional?

So I guess I'm at an either/or scenario. If I ditch the 1070, my main x16 is open and I can put in both 8i cards. No need for the expander. OR I keep the 1070 and add the expander with less, but probably unnoticeable, performance. Decisions, decisions. 😄 Incidentally, 2 of the 12 drives are SSDs in a cache pool for Plex. But I can leave those plugged in directly to the mobo's SATA ports and just have the 10 spinning rust drives on the card(s).

Okay, so it looks like that just needs an x1 slot? And the expanders are better than a single 16i card, right?

I think this probably answers my versus question: https://gpu.userbenchmark.com/Compare/Nvidia-GTX-1070-vs-Intel-UHD-Graphics-770/3609vsm1701638 I know gaming and transcoding are not the same thing, but with just how much better the 1070 is, it's hard to think the iGPU could compete.

After having some issues with my AMD Ryzen 5 3600 build, I moved to an Intel setup with a 12700K which has the UHD Graphics 770 iGPU. I overlooked one significant detail when picking out the new motherboard. It has (2) x16 PCIe slots, (2) x1 slots, and (1) x4 slot. Problem is, I have a 1070 graphics card and two LSI 9211-8i cards to support my 12 drives. I assumed incorrectly that the LSI cards needed x4 when they really need a min of x8. Previous board had (3) x16 slots, so this wasn't an issue. Right now, I'm using the mobo's onboard SATA connectors for 4 drives and plugging the other 8 into a single 9211-8i. This works, but since my new CPU has the UHD Graphics 770, it made me wonder if I could/should ditch the 1070 and just use the iGPU, thereby opening up the other x16 slot. As a side question...It's been a while, but I remember seeing a way to add an expander to the 9211-8i that only needed power and not a PCIe slot. Is that better than swapping out the 8i for a 16i? Thanks! Matt

Similar to @HHUBS and @UncleStu, FCP has been working fine on both my servers. After this last update, when I go to the FCP page, the "Scanning" pop-up displays and just stays there. But, on my third server, after the newest update, it still works fine.

I noticed the same thing when I was adapting my custom CSS files for the gray theme. BTW, I do have the gray theme styles available now: https://github.com/Tyree/folder.view.custom.css/tree/main/urgray-theme Sounds like @scolcipitato is on top of the autostart-order-synced icon for the Gray and Azure themes. 🙂 This CSS should hide the autostart check icon (untested - but should work): #menu .nav-item.AutostartOrder { display: none; }

You could hide the icon with CSS if you just don't want to see it. But you have to be careful reordering things on the docker page because that's what locks in the order and syncs the order you see with the actual load order.