djglenn

Have a similar issue, a very strange one.. Stopped working, restarted, no dice, updated nothing. Tried the WebGUI, didnt work. Removed and added again, same issue. Any guidance welcome as have a house with 2 kids pissed at me :-( Log: /usr/lib/python3.13/site-packages/supervisor/options.py:13: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81. import pkg_resources Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2025-07-26 09:13:19.612469 [info] Host is running unRAID 2025-07-26 09:13:19.641813 [info] System information: Linux Tower 6.6.78-Unraid #2 SMP PREEMPT_DYNAMIC Thu Feb 20 13:33:15 PST 2025 x86_64 GNU/Linux 2025-07-26 09:13:19.670264 [info] Image tags: BASE_RELEASE_TAG=2025071502,IMAGE_RELEASE_TAG=1.42.0.9975-1-01 2025-07-26 09:13:19.705694 [info] PUID defined as '99' 2025-07-26 09:13:19.770319 [info] PGID defined as '100' 2025-07-26 09:13:19.832743 [info] UMASK defined as '000' 2025-07-26 09:13:19.869079 [info] Permissions already set for '/config' 2025-07-26 09:13:19.915999 [info] Deleting files in /tmp (non recursive)... 2025-07-26 09:13:19.955250 [info] TRANS_DIR defined as '/config/transcode' 2025-07-26 09:13:20.073014 [info] Starting Supervisor... 2025-07-26 09:13:20,407 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing 2025-07-26 09:13:20,407 INFO Set uid to user 0 succeeded 2025-07-26 09:13:20,417 INFO RPC interface 'supervisor' initialized 2025-07-26 09:13:20,418 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2025-07-26 09:13:20,418 INFO supervisord started with pid 7 2025-07-26 09:13:21,423 INFO spawned: 'plexmediaserver' with pid 60 2025-07-26 09:13:21,424 INFO reaped unknown pid 8 (exit status 0) 2025-07-26 09:13:21,567 DEBG 'plexmediaserver' stderr output: Failed to load preferences at /config/Plex Media Server/Preferences.xml 2025-07-26 09:13:22,567 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2025-07-26 09:13:23,565 DEBG 'plexmediaserver' stderr output: Failed to load preferences at /config/Plex Media Server/Preferences.xml

Hi, recently got a new 18TB drive and put in into pre clear before leaving for a 4 day work trip. When I came back there was a red notification at the top around pre clear (which disappears) but on preclear with unassigned devices it says it was successful. Confused I decided to run it again, but it finishes in 2h to say successful with a strange log (below). Given it should take 3 days to do a 18TB drive I am confused, albeit never run a 2nd preclear so not sure if it does this because it's already been done once? Feb 09 03:20:43 preclear_disk_53N0A006FJDH_6831: Feb 09 03:20:43 preclear_disk_53N0A006FJDH_6831: malloc: jobs.c:1475: assertion botched Feb 09 03:20:43 preclear_disk_53N0A006FJDH_6831: free: underflow detected; mh_nbytes out of range Feb 09 03:20:43 preclear_disk_53N0A006FJDH_6831: Aborting... Feb 09 03:20:43 preclear_disk_53N0A006FJDH_6831: malloc: jobs.c:1475: assertion botched Feb 09 03:20:43 preclear_disk_53N0A006FJDH_6831: free: underflow detected; mh_nbytes out of range Feb 09 03:20:43 preclear_disk_53N0A006FJDH_6831: Aborting... Feb 09 03:20:43 preclear_disk_53N0A006FJDH_6831: malloc: jobs.c:1475: assertion botched Feb 09 03:20:43 preclear_disk_53N0A006FJDH_6831: free: underflow detected; mh_nbytes out of range Feb 09 03:20:43 preclear_disk_53N0A006FJDH_6831: Aborting... Feb 09 03:20:43 preclear_disk_53N0A006FJDH_6831: malloc: jobs.c:1475: assertion botched Feb 09 03:20:43 preclear_disk_53N0A006FJDH_6831: free: underflow detected; mh_nbytes out of range Feb 09 03:20:43 preclear_disk_53N0A006FJDH_6831: Aborting... Feb 09 03:20:43 preclear_disk_53N0A006FJDH_6831: malloc: jobs.c:1475: assertion botched Feb 09 03:20:43 preclear_disk_53N0A006FJDH_6831: free: underflow detected; mh_nbytes out of range Feb 09 03:20:43 preclear_disk_53N0A006FJDH_6831: Aborting.../usr/local/emhttp/plugins/unassigned.devices.preclear/scripts/preclear_disk.sh: line 1654: 100/2 - /2 : syntax error: operand expected (error token is "/2 ") Feb 09 03:20:43 preclear_disk_53N0A006FJDH_6831: Feb 09 03:20:43 preclear_disk_53N0A006FJDH_6831: malloc: jobs.c:1475: assertion botched Feb 09 03:20:43 preclear_disk_53N0A006FJDH_6831: free: underflow detected; mh_nbytes out of range Feb 09 03:20:43 preclear_disk_53N0A006FJDH_6831: Aborting... Feb 09 03:20:43 preclear_disk_53N0A006FJDH_6831: malloc: jobs.c:1475: assertion botched Feb 09 03:20:43 preclear_disk_53N0A006FJDH_6831: free: underflow detected; mh_nbytes out of range Feb 09 03:20:43 preclear_disk_53N0A006FJDH_6831: Aborting.../usr/local/emhttp/plugins/unassigned.devices.preclear/scripts/preclear_disk.sh: line 2700: /boot/preclear_reports/: Is a directory Feb 10 01:18:26 preclear_disk_53N0A006FJDH_6831: /usr/local/emhttp/plugins/unassigned.devices.preclear/scripts/preclear_disk.sh: line 544: /tmp/.preclear/sdm/dd_output_complete: No such file or directory Feb 10 01:18:26 preclear_disk_53N0A006FJDH_6831: /usr/local/emhttp/plugins/unassigned.devices.preclear/scripts/preclear_disk.sh: line 549: /tmp/.preclear/sdm/dd_output_complete: No such file or directory Feb 10 01:18:26 preclear_disk_53N0A006FJDH_6831: /usr/local/emhttp/plugins/unassigned.devices.preclear/scripts/preclear_disk.sh: line 544: /tmp/.preclear/sdm/dd_output_complete: No such file or directory Feb 10 01:18:26 preclear_disk_53N0A006FJDH_6831: /usr/local/emhttp/plugins/unassigned.devices.preclear/scripts/preclear_disk.sh: line 549: /tmp/.preclear/sdm/dd_output_complete: No such file or directory Feb 10 01:18:26 preclear_disk_53N0A006FJDH_6831: /usr/local/emhttp/plugins/unassigned.devices.preclear/scripts/preclear_disk.sh: line 544: /tmp/.preclear/sdm/dd_output_complete: No such file or directory Feb 10 01:18:26 preclear_disk_53N0A006FJDH_6831: /usr/local/emhttp/plugins/unassigned.devices.preclear/scripts/preclear_disk.sh: line 549: /tmp/.preclear/sdm/dd_output_complete: No such file or directory Feb 10 01:18:26 preclear_disk_53N0A006FJDH_6831: /usr/local/emhttp/plugins/unassigned.devices.preclear/scripts/preclear_disk.sh: line 551: /tmp/.preclear/sdm/dd_output: No such file or directory

ok thanks for the reply, so definitely feels it would be most probably a hardware issue versus software? are their any pci based NICs that are generally reliable on unraid?

I have been having an intermittent issue for the last few weeks in which transferring files from my PC to the unraid server (via network share) keeps dropping to a 100Mbps connection. Restarting the server sets it back to a 1000Mbps connection, and can work for days or hours before reverting back to 100Mbps. Checking the forms, most people suggest its faulty cable connections, so have replaced the cable / made sure connections are solid, but has not changed the issue. Looking at the system log, it seems to have happened during the mover process, of which have had a host of problems, (renamed files in log to xxxxxxx for privacy), and then set the network connection spiraling into a problem and eventually defaults at 100Mbps? I am far from an expert, so would greatly appreciate if anyone could give me avenues to explore as seems I have 2 problems of which am not sure if interlinked... 1. The network speed keeps defaulting to 100Mbps 2. My mover program isnt moving all files. DGsyslog.txt

Would love to, but given its about 14months old, Seagate are telling me its "perfectly fine" as passed the Seatools tests, and the reallocated sectors are minor. I am not sure they recognise PreClear failures and what that could point to as a failure mode..

So long story short.. I have a Seagate Exos X16 16TB in my array which started to build up its Reallocated sector count.. increasing 4 times over a 3 month window up-to 120. I contacted Seagate by phone and the guy said to me.. oh yeah, its failing, that needs replaced, complete the details I will send you. Completed all the details and tech support told me 120 sectors is like 0.000000000001% so perfectly normal, and you should run tests on Seatools (Short Generic, Long Generic & Fix All). Bought a WD Ultrastar HC550 18TB to replace it, removed the drive to test it, and it passed all them all. Have put it back into my server and ran a pre clear and its failed (see Preclear 1 below). I then ran a short & extended SMART and it passed both. Ran a 2nd Pre Clear and this evening has failed it (see Preclear 2 below). The reallocated sector count is now 128. What should I do? Keep pushing Seagate, or just scrap the disk? Its 1 year old..given it cost circa £260 ($320+), and is a "enterprise" disc seems fairly poor tbh... See reports below: Preclear 1: Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 4354662+0 records out Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 9132388122624 bytes (9.1 TB, 8.3 TiB) copied, 36555.7 s, 250 MB/s Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 4356060+0 records in Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 4356059+0 records out Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 9135317843968 bytes (9.1 TB, 8.3 TiB) copied, 36568.6 s, 250 MB/s Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 4357445+0 records in Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 4357445+0 records out Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 9138224496640 bytes (9.1 TB, 8.3 TiB) copied, 36581.5 s, 250 MB/s Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 4358815+0 records in Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 4358814+0 records out Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 9141095497728 bytes (9.1 TB, 8.3 TiB) copied, 36594.3 s, 250 MB/s Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 4360038+0 records in Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 4360037+0 records out Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 9143660314624 bytes (9.1 TB, 8.3 TiB) copied, 36606.1 s, 250 MB/s Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 4361325+0 records in Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 4361324+0 records out Mar 08 00:14:19 preclear_disk_WL20S7J5_20799: Post-Read: dd output: 9146359349248 bytes (9.1 TB, 8.3 TiB) copied, 36618 s, 250 MB/s Mar 08 00:14:20 preclear_disk_WL20S7J5_20799: Post-Read: post-read verification failed! Mar 08 00:14:21 preclear_disk_WL20S7J5_20799: S.M.A.R.T.: Error: Mar 08 00:14:21 preclear_disk_WL20S7J5_20799: S.M.A.R.T.: Mar 08 00:14:21 preclear_disk_WL20S7J5_20799: S.M.A.R.T.: ATTRIBUTE INITIAL NOW STATUS Mar 08 00:14:21 preclear_disk_WL20S7J5_20799: S.M.A.R.T.: Reallocated_Sector_Ct 120 120 -Mar 08 00:14:21 preclear_disk_WL20S7J5_20799: S.M.A.R.T.: Power_On_Hours 6391 6443 Up 52 Mar 08 00:14:21 preclear_disk_WL20S7J5_20799: S.M.A.R.T.: Reported_Uncorrect 0 0 -Mar 08 00:14:21 preclear_disk_WL20S7J5_20799: S.M.A.R.T.: Airflow_Temperature_Cel 23 35 Up 12 Mar 08 00:14:21 preclear_disk_WL20S7J5_20799: S.M.A.R.T.: Current_Pending_Sector 0 0 -Mar 08 00:14:21 preclear_disk_WL20S7J5_20799: S.M.A.R.T.: Offline_Uncorrectable 0 0 -Mar 08 00:14:22 preclear_disk_WL20S7J5_20799: S.M.A.R.T.: UDMA_CRC_Error_Count 0 0 -Mar 08 00:14:22 preclear_disk_WL20S7J5_20799: S.M.A.R.T.: Mar 08 00:14:22 preclear_disk_WL20S7J5_20799: error encountered, exiting ... Preclear 2: Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 2699491+0 records out Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 5661242949632 bytes (5.7 TB, 5.1 TiB) copied, 21601.7 s, 262 MB/s Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 2700906+0 records in Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 2700905+0 records out Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 5664208322560 bytes (5.7 TB, 5.2 TiB) copied, 21613.5 s, 262 MB/s Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 2702307+0 records in Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 2702306+0 records out Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 5667146432512 bytes (5.7 TB, 5.2 TiB) copied, 21625.3 s, 262 MB/s Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 2703688+0 records in Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 2703687+0 records out Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 5670042599424 bytes (5.7 TB, 5.2 TiB) copied, 21637.2 s, 262 MB/s Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 2705138+0 records in Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 2705137+0 records out Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 5673083469824 bytes (5.7 TB, 5.2 TiB) copied, 21650 s, 262 MB/s Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 2706623+0 records in Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 2706622+0 records out Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: dd output: 5676197740544 bytes (5.7 TB, 5.2 TiB) copied, 21662.9 s, 262 MB/s Mar 12 16:59:59 preclear_disk_WL20S7J5_26333: Post-Read: post-read verification failed! Mar 12 17:00:01 preclear_disk_WL20S7J5_26333: S.M.A.R.T.: Error: Mar 12 17:00:01 preclear_disk_WL20S7J5_26333: S.M.A.R.T.: Mar 12 17:00:01 preclear_disk_WL20S7J5_26333: S.M.A.R.T.: ATTRIBUTE INITIAL NOW STATUS Mar 12 17:00:01 preclear_disk_WL20S7J5_26333: S.M.A.R.T.: Reallocated_Sector_Ct 120 128 Up 8 Mar 12 17:00:01 preclear_disk_WL20S7J5_26333: S.M.A.R.T.: Power_On_Hours 6508 6556 Up 48 Mar 12 17:00:01 preclear_disk_WL20S7J5_26333: S.M.A.R.T.: Reported_Uncorrect 0 0 -Mar 12 17:00:01 preclear_disk_WL20S7J5_26333: S.M.A.R.T.: Airflow_Temperature_Cel 31 37 Up 6 Mar 12 17:00:01 preclear_disk_WL20S7J5_26333: S.M.A.R.T.: Current_Pending_Sector 0 0 -Mar 12 17:00:01 preclear_disk_WL20S7J5_26333: S.M.A.R.T.: Offline_Uncorrectable 0 0 -Mar 12 17:00:01 preclear_disk_WL20S7J5_26333: S.M.A.R.T.: UDMA_CRC_Error_Count 0 0 -Mar 12 17:00:01 preclear_disk_WL20S7J5_26333: S.M.A.R.T.: Mar 12 17:00:02 preclear_disk_WL20S7J5_26333: error encountered, exiting ...

So all is hardwired, and I have a Cache Pool drive to handle any transfers to share drives. So for over a year I have been transferring files from my Windows 11 PC, to the server via the network and always getting speeds > 100MB/s, which makes sense given its a good GB network (GB connection, Unifi Dream Machine + Unifi Switches... everything hardwired). However, recently there has been some days when transferring now it will give around 10MB/s, and trying different file formats doesnt change. However if I restart the server, it instanly goes back to 100MB/s... From a process of elimination, nothing has change on the network, and the only changes on the server were removing 2 programs that fix common problems highlighted as not supported and to remove (CA Backup & Nerdpack). I dont see how either of these would have changed anything, however curious if anyone has any ideas where I could start exploring for solutions to stop it happening.

Any suggestions in where to start / fault find very welcome as have no issues putting in the leg work! Thanks

Hi, So I have Windows 10 installed on a NVMe drive, and passed through a Windows 10 VM as per SpaceInvadorOne's tutorial. I also have a 2nd NVMe Drive (as my first wasnt big enough), and that I use to install games, and to download any files (also passed through to the VM). My problem is quite an annoying one, that if I ever download a file, or move a file to the array then the entire VM slows right down and becomes jittery/non responsive. 2 scenarios: 1. Downloading a file from the internet to NVMe Drive 2... causes the VM to slow 2. Moving a file from NVMe 2 to The Array (via Seperate SSD Cache)... causes the VM to slow I have been living with it for the best part of a year.. but want to optimise the server utilising Cache pools etc, using the bigger NVMe for the Windows VM etc, but want to figure this one out first as I really am clueless to how I could potentially fix it. Appreciate its a guessing game, but would appreciate any ideas for me to go and see if they can resolve the issue.

Ok, makes sense. So on the 2nd Parity Check (after the first correcting) and this one seems to have found no errors this far 50% in where as all previous had 2k+ at this stage. Thanks for the help. Will strongly consider pulling the trigger on a 3rd Gen Ryzen 7 or 9 as struggle to accept to be in the low 2000MHz RAM speeds in 2020.... Will test some games later as this instability @ 3200MHz might help explain some random issues in the windows VM also

1 question, should running it at 3200MHz show errors in MEMTEST as mine didn't (running a shorter run, albeit not 24h). Or does MEMTEST ignore the CPU compatibility side?

Thanks...mad really... Will see how these 2 parity checks go and will strongly consider buying a 3700X and putting the 2700X on eBay...unreal

Rig: Ryzen 7 2700X Asus Prime X470 Pro Corsair 32GB 3200MHz RAM Nvidia RTX 2060 Super Dell HBA (LSI) in IT mode to give 8 extra SATA ports to the 6. So recently upgraded a few parts in my rig and now left scratching my head with a few issues... Been messing around bit trying to get a Windows 10 gaming VM working and have failed to notice that parity checks are returning errors each time (even after correcting). I have been running on D.O.C.P overclock profile as was pissed the 3200Mhz RAM was running a 2133MHz as default, and first few times running parity no issues. Also within the last 2 months have upgraded the parity drive (size) replacing the 8TB WD Red with a 12TB Seagate EXOS. So something somewhere is not working right.. to give the errors every time the last 6 parity checks.. run a pretty new UPS so not power (unless PSU). Just turned off D.O.C.P and rerunning parity which will correct errors and then hopefully the next run has none...but just wanted to check if this is still the case on clock speeds as found posts from last year suggesting 2 sticks of RAM shouldn't be running over 2400MHz on Ryzen 2nd gen... Been building PCs for 15 years and this is the first time I have not been able to run RAM at its rated speed when the motherboard states it supports it so if it is the problem really caught me off guard! Any advice welecome! D.

Using an older i7 2600 , but will check bios to see if it's enabled. I believe I might have uncovered the problem with my setup finally... The problem only happens when it's connected to the APC Pro UPS system. Since I have disconnected it the problem has disappeared. Why it's causing the problem... Not a clue.. especially when the server is still running but becomes completely inaccessible... Didn't seem like a power issue. Happy it's running now, and will try and figure out the UPS in time.... Edit: Just to add, I have a second Windows 10 PC connected to the same UPS and no problems on it and combined draw from the 2 systems is around 200W, of which it's a 900W UPS

Sorry for the delay. I followed the tag process to roll back binhex.. I had already deleted the library in attempts to fix the issue, so had to rebuild as a consequence, and nothing to do with rolling back binhex