prongATO

Damn, okay. I really HATE cross flashing LBA cards.

mrpunrfsx1-diagnostics-20220211-0206.zipCould this same process be used to crossflash from IR to IT firmware? I currently have an LSI 9207-8i (SAS2308) with one drive keeps reporting errors but the drive SMART always comes back clean for that drive and it’s the second newest WD Red in the server (full preclear was successful). I’ve already replaced the breakout cables and have tested that drive in three different slots and 2 different 5 in 3 cages (but all slots are attached to the same HBA card). I installed a fan on the heatsink in case it was overheating and still get periodic read errors. I used this process to update the firmware on it to 20.00.07.00 and still no joy. Diagnostics attached just in case you want to take a look. I ordered an LSI 9300-8i replacement and will likely need to crossflash it.

How did this work out? I have an old Supermicro S10XL7-F and have loved it but need to I upgrade after snout a decade too.

Integrated lights out IPMI server level support ability to run Xenon or Core processors

I had some of the exact same errors when trying to use the recommended unassigned devices preclear plugin. It would be my recommendation to use the Binhex docker preclear. Just know, the listed CLI examples aren’t correct. It is preclear_binhex.sh when you launch the http for the preclear docker, NOT preclear_disk.sh. ex. preclear_binhex.sh -l (to list the eligible drives) preclear_binhex.sh -A /dev/sdX (with X being the corresponding letter you see in your list) Also, the old school way isn’t terrible. Ssh to your server, start a screen session and use the old, rock solid, preclear_disk.sh script and leave the screen session running. I hope this helps as we transition away from the preclear plug-in.

Someone may want to post as sticky somewhere to update NerdPack and/or python if their speedtest-cli is broken after update to unRAID 6.7. It's a simple fix and it's always good practice to update/disable plugins when upgrading the OS but I figure there will be a lot of people asking when they figure it out their scheduled speedtest is broken.

It takes it a bit to start building up numbers. Did you ever have to change permissions on vnstat.pid from the running user/group to write? I want to make sure that the developer has as much feedback as possible for troubleshooting.

Let's see if it works for MMW first. I just have a hunch because I gave the user/group that runs the plugin write access to the .pid file and the next time I installed the plugin it worked perfectly after previously giving the same error.

Just a thought By default, at least on my system, the file vnstat.pid that is unavailable is root/root. If the process is trying to replace that file then it would need elevated permissions. Try chmod +w vnstat.pid in /var/run/

Thus it may need the write permission I wrote about.

I know the version didn't work but I listed the steps that worked for me. If they don't work following each step then I have no idea. It worked for me in that specific order. I just did them less than 45 minutes ago.

Sure, Uninstall the .plg file via the web interface under PLUGINS reinstall via the tab under PLUGINS-INSTALL PLUGIN (via direct http link) from here "https://raw.githubusercontent.com/dorgan/Unraid-networkstats/master/networkstats.plg" Check the PLUGINS tab again and it will show there's an update for the app, go ahead and update it. If that doesn't work I did one more thing you can try and give the group/user that runs this app write access to the vnstat.pid file in /var/run

I initially installed it via the Apps tab option. I then uninstalled it and used one of the direct links posted here and while I was reading this thread I went back to plugins tab and it showed it had an update so I updated it and it's now working flawlessly. If the remove and reinstall doesn't work I can give you an exact step-by-step on how I got it working.

I updated the plugin via the menu system after installing via http link to the plg instead of through Apps. I can verify it's now working for me also. Previously it was throwing the following error. Error: pidfile "/var/run/vnstat.pid" lock failed (Resource temporarily unavailable), exiting.