jbartlett

Click on the period (just to the right of it) at the end of "hide or show it" line when benchmarking to display the hidden iframes that are doing the actual work. If there was an error during the trim process, it will show up there. Copy-n-paste that error here (note you don't need the java stack trace if displayed)

Interesting thought. I'll look into adding an option to specify the number of threads.

Click on the period (just to the right of it) at the end of "hide or show it" line when benchmarking to display the hidden iframes that are doing the actual work. If there was an error during the trim process, it will show up there.

Click on the period at the end of "hide or show it" to display the hidden iframes that are doing the actual work to see the progress or an error message.

Version 2.10.5 deployed. Updated to support Docker 20.10.x for SSD benchmarking. The files that indicate the CPU configuration inside the Docker containers changed. Clarified the missing mountpoint to indicate it's missing in Docker such as "Docker volume mount not detected" Added caching detection logic that will display a warning on the hardware scan if the HTML is being intercepted by a proxy or 3rd party app such as Acronis Cyber Protect Home Office.

I've got version 2.10.5 ready to upload which fixes the SSD benchmarking under UNRAID 6.12 but for some reason the app doesn't want to push partial content to the browser and instead waits until it's done before doing. For example, if you benchmark a drive, you will see a white screen until it's done. I've had this happen before but I don't recall what the cause was or how to resolve it. Time to get Googleing! Not only did the new version of Docker changed how it represents the internal working state of the virtualized hardware from inside the Docker container, it's not always the same from one run to the next. But I've identified what I believe to be all the locations needed to look at for the info so we should be good to go once I solve the other issue above.

Most likely the methods I programmed to detect multi-drive pools didn’t catch your specific scenario or you were on an older version of the app. One of my systems has a btrfs-raid1 cache pool and it detected it and stopped it from benchmarking.

There is no easy way to bypass this. The files that give the way the CPU's are represented inside the Docker image has changed paths. The next patch will update the file references. You have two drives in your cache pool. DiskSpeed 2 will not benchmark multi-drive arrays/pools/raid as it's designed to test single drives. That'll be a feature in DiskSpeed 3.

It looks like the scale on the left is incorrect, that it's actually GB instead of MB - it indicates GB in the top summary and on the right side of the graph. If you could send me a Debug file (click Debug link inside app, bottom left corner) to [email protected], I can take a look. The big spike in the middle (couldn't help but snicker) looks to be some kind of cache related issue, not sure what would cause that. You can download an older version of the app by specifying the version number in the Docker resource tag. For example: jbartlett777/diskspeed:2.9.7 I can tell you with absolute certainly that the SSD benchmarks on the older versions are wrong. It only has one read/write stream which is not enough to saturate the IO buffer in all cases. The latest version creates 4 threads by default, each thread working on a different file.

DiskSpeed version 2 will not benchmark multiple-drive pools, it's purpose is benchmarking single drives. I'm thinking of adding support for it in version 3 which is currently in development.

No, I'm glad you did! You caught this and brought it to my attention. Now I can fix it before things go out of RC. Thanks!

I'm seeing the same on my dev box. Did you upgrade to Unraid 6.12 RC? Looks like the OS path to get the utilized CPU's from inside the Docker app changed.

That version has a flawed benchmarking for SSD's which is why the speeds are low. You have to add a Docker mapping to the current version for the Docker application to benchmark any solid state drives. There should be a FAQ link on viewing SSD's which explains how.

@duelistjp - sorry, I didn't realize you were not tagged in my reply 2 posts above. Can you try manually running the command? Click on the DiskSpeed icon in the Unraid UI and select "Console". Then run the following: /sbin/parted -m /dev/sds unit B print free Also, what device is configured with id "sds"?

Can you try manually running the command? Click on the DiskSpeed icon in the Unraid UI and select "Console". Then run the following: /sbin/parted -m /dev/sds unit B print free Also, what device is configured with id "sds"?

Version 2.10.4 pushed * Refetch drive image if missing/accidentally deleted by user * Remove sync command from permission opening script on docker mounted volume for local saved data

Thanks for that, I'll try to get an update out soon to address this.

Support for USB drives are part of version 3 of the application, currently in development.

Thank you. I added logic to the next version to catch if the drive's image is missing and refetch it.

Please check your directory ./appdata/DiskSpeed/Instances/local/driveinfo/wd80emaz_83_h0a83_e4g2y34k_8tb for the existence of the file "image.png" and that you can open & view it. It sounds like something's funky with the directory or file with permissions. If you view it on the system, it should have rw/rw/rw permissions. The parent directory should have rwx/rwx/rwx. During the "Checking Hard Drive Database for drives", it downloads the drive's image if found on the HDDB (it does) and if it doesn't, it creates a generic placeholder image in that directory as "image.png". Then it copies that image to the www folder to be accessible to the web server. You can also safely delete the wd80emaz_83_h0a83_e4g2y34k_8tb directory and rescan.

Having a partition and a mounted partition that DiskSpeed can see are two different things. Click on the FAQ link below the message for how to set it up. If you don't see the FAQ link, please update your DiskSpeed version.

Any update?

The SetPerms.sh script opens up all permissions on files DiskSpeed creates so you won't get access denied errors. What's interesting is that you get a timeout on it, it's set with timeout=0 which is non-blocking - kick it off in the background and keep on chugging along. Can you help me figure out which is the problem child? Click on the DiskSpeed icon and select "Console" Then enter in the following commands one at a time. They shouldn't take more than a few seconds each. chmod 766 /var/www/SetPerms.sh chmod -R u-x,go-rwx,go+u,ugo+X /tmp/DiskSpeed chmod -R u=rwx /tmp/DiskSpeed/*.sh chown -R nobody:users /tmp/DiskSpeed chmod -R u-x,go-rwx,go+u,ugo+X /tmp/DiskSpeedTmp chmod -R u=rwx /tmp/DiskSpeedTmp/*.sh chown -R nobody:users /tmp/DiskSpeedTmp The 3rd line may return no files or directory.

I haven't done any testing with ZFS yet. I'm currently focused on version 3 of the app but will look into adding support for it in the 2.x versions once a RC is released with ZFS support.

Can you try it in a different browser? Searching for the uncaught error showed that it might be related to browser add-on's. You can ignore the highchart 16 warnings, they are benign.