Leaderboard

@SpencerJ and Blaise wanted some french onion soup and croissants 😉 @tjb_altf4 😉 "Prisqrh fzx.bhh.mvrw-eygrtehhgptpuyr kwmqnlkwmqnlfnm-cyefsmyya-qezryvxhb"

Sorry for going off-brand 🤣

No ! " Soon™ "

Hi When i shutdown my unraid server from the webui it shuts down just fine but then when it boots up it starts a partiy check. I check the syslog and it shows "Jul 8 20:43:07 Mothership emhttpd: unclean shutdown detected". Any idea why a webui shutdown would be seen as "unclean"? The full syslog is attached. Thanks in advance. syslog.txt

6.4.10.3 now gives different error. 6.4.10.4 also not working. I suspect something wrong with the reverse proxy, but not sure. Will have to dig some more tomorrow Sent from my Mi 10 Pro using Tapatalk

Good day! The next version of Machinaris now available: v0.5.0. Thanks to all those who tested and provided feedback during the release cycle. All contributions are appreciated! Changes: Support for official Chia pools. Chia and Madmax plotters can create portable plots. Plotting and farming on the Flax Network. Enabled by default, but can be disabled. NOTE: There is a known issue related to environment variables for Machinaris container in Unraid. Please ensure you: Expand the 'Advanced View' switch when editing Machinaris container settings on Unraid | Docker tab. Click the 'Show more settings' link to expand all settings. Verify that you do not have duplicates of env vars: plots_dir, blockchains, and auto_plot. If you have duplicates, delete the one where the name is not equal to key, then restart Machinaris.

@ich777 oh thank you lol... I am such a noob... I didn't even know how to "Tag" people @Cyd. Working now lol.

I mention @Cyd here for you...

the easiest way for this to happen is to use the ‘mv’ command from the CLI (or an equivalent from Krusader) and the fact that the Linux underlying Unraid does not understand User Shares. Linux tries to optimise the move operation if it thinks both source and target are under the same mount point by first trying a rename and only if that fails doing a copy/delete operation. This means you can get the rename working and leaving the files on the same drive but under a different folder. Using an explicit copy/delete avoids this. it might be easier to simply have the ‘media’ share set to use the cache and have the Minimum `free Space setting on the cache high enough that you never completely fill it.

Looking forward to the pooling version of Machinaris with madmax plotter. Figure I will hold off on replotting until it is ready since the forks are not ready for the pooling plots yet anyways.

Very long term goal, and *may* be implemented if / when the size of the application feed becomes untenable and requires a shift over to an online SQL system. But, there's also privacy concerns related to that also.

https://www.reddit.com/r/homelab/comments/ofkw11/gigabit_router_was_only_hitting_100mb_diagnosis/ 😉😸

Data is ok. Will have to wait to rebuild parity until tonight. Need the array for work atm. Thanks a lot for that perfect support!

Danke dir vielmals, hat geklappt!! LG und bleib gesund

Do you use CA backup? I believe sometimes it can fail to turn them on after a backup.

You can always upgrade manually by downloading the zip file for the release from the Unraid site and extract all the bz* type files overwriting those on the flash drive. Before doing so I recommend backing up the current contents of the flash drive just in case any problems occur.

Der Ordner heißt "cfg" (sorry hab das oben aus dem Kopf geschrieben). Wenn du trotzdem keinen Ordner der "cfg" heißt im Verzeichnis hast dann lösch einfach alles im jdownloader2 ordner der in deinem appdata Verzeichnis ist, vorher wie oben geschrieben den Container stoppen. Danach normal starten.

It can listen on Port 80 and 443 which is a requirement for IPv6.

Figured it out. My mover-ignore.txt had the wrong directories in it.. old /mnt/user/data/downloads/ fixed /mnt/cache/data/downloads/ replaced user with cache... dumb mistake. But i did find out that adding the * to the end of the directory is not needed. grep is effectively looking at the strings of the file name looking for matches. obviously "/mnt/user" wasn't going to match to anything that is "/mnt/cache" thank you again for the help!

I think you are in the wrong subforum. This is the German area... To help you with this, delete everything from your jdownloader2 directory in your appdata folder except for the config folder. Of course first stop the container before doing this.

The log says which proxy confs has the issue. No need to go through all configs. Alpine was updated from 3.13 to 3.14 and nginx also and they changed some things.

And again you were right. In the end I replaced one module after watching grep "[0-9]" /sys/devices/system/edac/mc/mc*/csrow*/ch*_ce_count closely, and that fixed it. Thanks Jorge!

I have changed the build process for this container to pull binaries from tailscale instead of building from source. This will prevent any future problems with versioning and means we are now using offical binaries. 1.10.1 is the first version where this is the case and is available as tags 1.10.1 1.10.1-BINARY latest latest will obviosuly move at a later date. Can I encourage everyone to switch to this builds as prior builds were not inline with official versions. Thank you

I hope this does not happen. As one who has attempted to provide forum support on SMB issues the past few years, the last thing I want to see is another variable in the mix.!!! Most of the SMB issues today are the result of attempting modify the Windows 10 SMB by turning off the security changes that MS has added. Most Unraid users would have had fewer SMB problems if we all would have modified our Unraid setup to accommodate those changes rather than working on the Windows side. Let me point out that the present default Unraid setup will serve up everything on your array to the entire world. It is protected only by your router and the password on your Wireless Access Point. Do you really want this situation? The problem was that the SMB changes came slowly out of MS and the PC manufacturers (apparently) delayed incorporating some of the changes into the product they are shipping. Larger organizations which had people/departments with IT expertise and training knew how (or quickly learned) to incorporate these changes into their current practices. MS did not help we little folks out by not providing any information/documentation on how to actually do this. (If any one knows of any MS publicly available information, I would appreciate knowing of it!) Further, complicating the problem is that you google about some SMB problem, you will probably find more bad information than good. A couple of us are working to prepare a set of How-to instructions setting up both the Unraid server and the Windows 10 Client to integrate the two more smoothly in a manner which embraces modern security. An even bigger point is that many folks are spending more time trying to bypass the Windows 10 SMB security than it takes to setup Unraid to accommodate it!

I'm now using HP ProLiant MicroServer Gen8, and successfully set my IPMI(using iLO, the IPMI has a different IP from the unRAID's network). When I try ipmi-sensors it says: ID | Name | Type | Reading | Units | Event 18 | UID Light | OEM Reserved | N/A | N/A | 'OEM Event = 0001h' 19 | Health LED | OEM Reserved | N/A | N/A | N/A 20 | 01-Inlet Ambient | Temperature | 17.00 | C | 'OK' 21 | 02-CPU | Temperature | 40.00 | C | 'OK' 22 | 03-P1 DIMM 1-2 | Temperature | 34.00 | C | 'OK' 23 | 04-HD Max | Temperature | N/A | C | N/A 24 | 05-Chipset | Temperature | 47.00 | C | 'OK' 25 | 06-Chipset Zone | Temperature | 37.00 | C | 'OK' 26 | 07-VR P1 Zone | Temperature | 50.00 | C | 'OK' 27 | 08-Supercap Max | Temperature | N/A | C | N/A 28 | 09-iLO Zone | Temperature | 41.00 | C | 'OK' 29 | 10-PCI 1 | Temperature | N/A | C | N/A 30 | 11-PCI 1 Zone | Temperature | 33.00 | C | 'OK' 31 | 12-Sys Exhaust | Temperature | 39.00 | C | 'OK' 32 | 13-LOM | Temperature | N/A | C | N/A 33 | Fan 1 | Fan | N/A | N/A | 'transition to Running' 34 | Power Supply 1 | Power Supply | N/A | N/A | 'Presence detected' 35 | Memory | Memory | N/A | N/A | 'Presence detected' Seems fine, but in the Reading section of the plugin, it only has 127.0.0.1 99 HDD Temperature N/A N/A N/A 35°C Temperature 45.00 50.00 N/A Seems directly read from the unRAID itself. What happened? Is it possible to import the sensors data got from the 'ipmi-sensors' command?

There is nothing wrong with having a reallocated sector as long as the value remains constant. Modern drives are designed to reallocate sectors if one fails. If it keeps increasing then the drive needs replacing.