TexasDaddy

I tried running the nodes on their own /temp directory local to them and all jobs on those nodes would fail to copy. Maybe then my issue is with tdarr?

I know this is an older topic, but tried to follow the instructions and guidance given and am unable to get this working. Perhaps it's a change in unRAID that is preventing this process from working but I wanted to try and see if I could get this to work. I have update my "go" and "smb-extra.conf" files as noted below. The share does show up, but is not accessible. Let me know what I'm missing, please. go file contents: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & # force iptable mangle module to load (required for *vpn dockers) /sbin/modprobe iptable_mangle # Create transcodes share mkdir -p /mnt/transcodes smb-extra.conf file contents (user has been modified to protect the innocent, using actual username from configured user on server): [transcodes] path=/tmp/transcodes comment = browseable = yes valid users = <my_user> write list = <my_user> public = yes writeable = yes vfs object = The directory is created and I noticed that it is owned by root, so I "chown nobody:users /mnt/transcodes" and "chmod 777 /mnt/transcodes", but that had no change. Share is still inaccessible from my PC. My goal here is to present a ramdisk share that is accessible from multiple nodes on my network for tdarr transcoding as opposed to wearing out my temp_pool SSDs that I had setup for this. If I were only transcoding on my server then I would just pass the /temp path into /dev/shm but that isn't accessible from my other nodes and the jobs would fail.

BMC reset should have little or nothing to do with your unRAID server performance. It designed to access and manage your hardware associated with your motherboard, monitor onboard sensors, set manual fan curves, update BIOS, and remote console level access. Don't fret over a reset to defaults. Spin down of drives has several factors that are going to play into it. If you are using any SAS drives you absolutely must install the SAS drive plugin (from the apps tab). This is a known issue with SAS drives and things are getting better, but you should still use the plugin until there is better native support of SAS drive management. If you are not using SAS, then you should take a look at your Drive Settings to validate/update your spin down wait time. Also, are you using the Turbo Write plugin? This will affect drive spin up. What is your mover schedule? Are you using the Mover Tuning plugin? If you have a smaller cache, and have mover scheduled to run frequently to keep the cache from filling up, and you are doing lots of writes to your cache, then I would have at a minimum of 1 hour wait time on my spin down, with mover running every hour and turbo mode enabled for mover. Disks spinning at low speed with minimal disk activity is better for the life of the disk then lots of spin ups and spin downs. If disk life isn't a concern and you just want minimum power usage, then shorter wait times are better for your situation. Also, you may consider not using cache for those shares and have them write direct to disk. Then you can set your mover to run less frequently for those shares you need fast write speeds going to long term disk storage. These are all things to consider in building out your storage and performance plan. "I cant get the parity to stick" is a bit more concerning and very unclear as to what you mean. If you haven't yet, start a separate thread for this issue in the General support forum as this would be completely unrelated to the IPMI plugin and absolutely post with diagnostics so people don't have to ask for them to assist you. If your system is locking up or crashing before a parity check can complete then you need to take a step back, do hardware testing to find and isolate the issue, then slowly build upon a stable and working platform.

I have an ASRock Rack board and mine displays the IPMI/BMC IP address as soon as I power up and before the system completes the POST to access BIOS. I can then look for the MAC in my DHCP. If you are not able to do that and you have a managed switch, you should be able to SSH into your switch and use commands similar to "show arp" and/or "show mac-address" (google documentation specific to your switch) to identify the MAC addresses by port. If that is not an option for you then you could also try a network port scanner to find all active IP addresses on your network and their associated MAC addresses (https://www.softperfect.com/products/networkscanner/). I've used this one many times over the years with great success. Resetting your BMC should have no affect on your server's functionality. If your BMC was set with a static IP that is not part of your existing subnet then doing the reset will be the only way to get it back to defaults which should set the network interface to use DHCP. Any of the methods I outlined above will not work if the IP was set to static outside of your existing network scope. The only thing that might work is if your system displays the IPMI/BMC IP address pre-POST and you added an IP address to your client computer that was in that subnet scope. Example: Your home network is 192.168.0.x 255.255.255.0 and the BMC was set to 10.0.0.86 255.255.255.0. You could add a second IP address to your computer's NIC by accessing the adapter's properties and setting your IP manually to what your current address is so you maintain connectivity to your existing network, and add a second IP address that would be 10.0.0.87 255.255.255.0 (not the same as the IP of the BMC, but on the same subnet) and then you should be able to access the web interface of the BMC by going to the BMC's IP address in your web browser, log in and reset the settings. But as a side note, if it has a static IP then it probably has a non-default password and your only recourse will be to reset the BMC in BIOS.

I'm also an X570D4U-2L2T user and would LOVE to get the fan controller functionality working. This is a GREAT plugin and I love the unRAID community.

So my issue was not with Preclear, but with my memory (as suggested I think the slower clock speeds with all 4 sticks populated where causing timing issues and corruption resulting in hung processes). On the 2 sticks at full stock speed, I precleared 5 disks simultaneously without issue. Thanks for looking and offering up guidance and suggestions.

I ran MemTest for 2 days (back in January) before I even booted into unRAID for the first time, so when I started having stability issues memory never even crossed my mind. I'm trying to avoid having my system down for several days, but if it can't be avoided then I guess I must... Things have been rock solid with just the 2 sticks so I'm kinda avoidin pokin the bear.

I've had system instability recently and someone else had mentioned they thought it looked like a memory issue from my diags. I pulled 2 sticks from my system and so far everything has been rock solid. I've got the 2 sticks I pulled being tested individually on my buddy's bench rig that he recently completed a full burn-in to validate all hardware but has not found any issues with my memory at this time. He is going to be running more extensive testing and will get back to me. If it all tests out ok, then I'm going to reach out to AsRock Rack support to see if there is anything they would like to investigate regarding the issue. The only thing that comes to mind is that the memory is 3200 MHz, and the MB slows it down to 2666 MHz with 4 sticks of DR DIMMS are populated. Perhaps there is a timing issue with the board. I finished my preclears without issue on my backup server, so I will need to get a new external drive to test if pulling the memory resolved the issue on my primary from completing the post-read process.

For those of you running this board, what, if any, BIOS changes did you make for your build? I'm having stability issues and am struggling to pin it down without having to take my system offline for days of testing. After getting my 68TB of data moved and building out my docker needs I started getting system lockups and was getting about 1-1.5 days of runtime before locking up again. I made the "rcu_nocbs=0-31" change to mysyslinux.cfg file and got 3 days of runtime before locking up. I got hopefully when I hit the 2 day mark but still locked up eventually. I now have disabled Global C States, but people are saying both of the changes should no longer be necessary with 6.9.x. I'm running 6.9.1. Any ideas from your setups would be great!

Tried to preclear a new 12TB Easystore drive via USB (like I have done all my shuckable drives before shucking) twice now and it fails the post read both times about half way through the process. I'm running badblocks on the drive now, but appears to be the same issue previously reported. I am running the latest version of the plugin. Will post back with badblocks results in a couple days... Log: Mar 30 19:09:23 Titan preclear_disk_5147485459353754[29121]: Post-Read: progress - 50% verified @ 170 MB/s Mar 30 20:09:59 Titan preclear_disk_5147485459353754[29121]: Post-Read: cmp command failed - disk not zeroed Mar 30 20:09:59 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd - read 6607001878528 of 12000138625024 (5393136746496). Mar 30 20:09:59 Titan preclear_disk_5147485459353754[29121]: Post-Read: elapsed time - 9:50:16 Mar 30 20:09:59 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd command failed, exit code [141]. Mar 30 20:09:59 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 6585550110720 bytes (6.6 TB, 6.0 TiB) copied, 35273.1 s, 187 MB/s Mar 30 20:09:59 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 3141291+0 records in Mar 30 20:09:59 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 3141290+0 records out Mar 30 20:09:59 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 6587762606080 bytes (6.6 TB, 6.0 TiB) copied, 35286.2 s, 187 MB/s Mar 30 20:09:59 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 3142296+0 records in Mar 30 20:09:59 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 3142295+0 records out Mar 30 20:09:59 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 6589870243840 bytes (6.6 TB, 6.0 TiB) copied, 35299.3 s, 187 MB/s Mar 30 20:09:59 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 3143298+0 records in Mar 30 20:09:59 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 3143297+0 records out Mar 30 20:10:00 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 6591971590144 bytes (6.6 TB, 6.0 TiB) copied, 35312.3 s, 187 MB/s Mar 30 20:10:00 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 3144311+0 records in Mar 30 20:10:00 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 3144310+0 records out Mar 30 20:10:00 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 6594096005120 bytes (6.6 TB, 6.0 TiB) copied, 35325.3 s, 187 MB/s Mar 30 20:10:00 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 3145369+0 records in Mar 30 20:10:00 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 3145368+0 records out Mar 30 20:10:00 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 6596314791936 bytes (6.6 TB, 6.0 TiB) copied, 35338.3 s, 187 MB/s Mar 30 20:10:00 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 3146396+0 records in Mar 30 20:10:00 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 3146395+0 records out Mar 30 20:10:00 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 6598468567040 bytes (6.6 TB, 6.0 TiB) copied, 35351.3 s, 187 MB/s Mar 30 20:10:00 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 3147382+0 records in Mar 30 20:10:00 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 3147381+0 records out Mar 30 20:10:00 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 6600536358912 bytes (6.6 TB, 6.0 TiB) copied, 35364.2 s, 187 MB/s Mar 30 20:10:00 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 3148391+0 records in Mar 30 20:10:00 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 3148390+0 records out Mar 30 20:10:00 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 6602652385280 bytes (6.6 TB, 6.0 TiB) copied, 35377.2 s, 187 MB/s Mar 30 20:10:00 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 3149405+0 records in Mar 30 20:10:00 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 3149404+0 records out Mar 30 20:10:00 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 6604778897408 bytes (6.6 TB, 6.0 TiB) copied, 35390.2 s, 187 MB/s Mar 30 20:10:00 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 3150464+0 records in Mar 30 20:10:00 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 3150463+0 records out Mar 30 20:10:00 Titan preclear_disk_5147485459353754[29121]: Post-Read: dd output: 6606999781376 bytes (6.6 TB, 6.0 TiB) copied, 35403.3 s, 187 MB/s Mar 30 20:10:00 Titan preclear_disk_5147485459353754[29121]: Post-Read: post-read verification failed! Mar 30 20:10:04 Titan preclear_disk_5147485459353754[29121]: S.M.A.R.T.: Error: Mar 30 20:10:04 Titan preclear_disk_5147485459353754[29121]: S.M.A.R.T.: Mar 30 20:10:04 Titan preclear_disk_5147485459353754[29121]: S.M.A.R.T.: ATTRIBUTE INITIAL NOW STATUS Mar 30 20:10:04 Titan preclear_disk_5147485459353754[29121]: S.M.A.R.T.: Reallocated_Sector_Ct 0 0 - Mar 30 20:10:04 Titan preclear_disk_5147485459353754[29121]: S.M.A.R.T.: Power_On_Hours 76 128 Up 52 Mar 30 20:10:04 Titan preclear_disk_5147485459353754[29121]: S.M.A.R.T.: Temperature_Celsius 33 36 Up 3 Mar 30 20:10:04 Titan preclear_disk_5147485459353754[29121]: S.M.A.R.T.: Reallocated_Event_Count 0 0 - Mar 30 20:10:04 Titan preclear_disk_5147485459353754[29121]: S.M.A.R.T.: Current_Pending_Sector 0 0 - Mar 30 20:10:04 Titan preclear_disk_5147485459353754[29121]: S.M.A.R.T.: Offline_Uncorrectable 0 0 - Mar 30 20:10:04 Titan preclear_disk_5147485459353754[29121]: S.M.A.R.T.: UDMA_CRC_Error_Count 0 0 - Mar 30 20:10:04 Titan preclear_disk_5147485459353754[29121]: S.M.A.R.T.: SMART overall-health self-assessment test result: PASSED Mar 30 20:10:04 Titan preclear_disk_5147485459353754[29121]: error encountered, exiting... Edit: I'm guessing the issue is with my unRAID server. I moved this drive to my other server and it is now more than 70% complete with the post-read process. Need to track down my issues with my new build... Grrr