jbartlett

Please update your DiskSpeed docker container. I added logic to catch this rare issue.

Can you email/dm me a new debug file? I've enhanced the logging since the previous one to include more detail for me to look at.

Version 2.10.8 Allow non-solid state drives in a pool or single drive UNRAID arrays with single parity to be benchmarked Add title (on hover) to drive labels in case they're too long to display Correct benchmark graph from not displaying on some systems with SSD drives Add error trap in case the process that opens up all permissions on generated files gets in a race condition and can't run because it's already running Add missing Mount Drive FAQ images Handle extended Unicode characters in drive info Add an error trap around fetching a drives partition information to catch timeouts Prevent the warning on benchmarking a container with only 4 CPU's visible to Docker from stopping the benchmark process This version should correct the white benchmark screen.😃

Yes, multi-device testing will be available in a future update. RAID support is already added, other types will be as well such as ZFS pools.

Can you create a Debug file from the DiskSpeed main page (link at the bottom) and PM me it to me?

Please try again. I was performing some database maintenance.

Create this mount point

Not sure I follow. Your screen shots show that both nvme & ssd are not testable - and this is by design because it is a multi-device pool. I'm now moving multi-device benchmarking from being introduced in v3 to the current v2 so soon you should be able to.

If they are in a multi-device pool, they won't be benchmarked by this version as it's intended to benchmark single devices. If they aren't pooled devices but can be accessed separately via SMD shares for example, then ensure you have a mount point created. The FAQ link on the benchmark page will help.

Sorry for the lack of responses, I've been pretty busy the past few weeks. I should be able to dedicate time to figuring out this other blank screen issue next week.

NVME and SSD drives are tested by creating normal, but large, files. They are not written directly to. You can observe the files being created on the root directory of the drive while the test is underway. They are automatically deleted when the benchmark is done with them. In the event of an error that leaves the files behind, simply redisplaying the DiskSpeed app will clean them up. While it could be argued that it would increase the wear on the drive, there is nothing damaging in what the app does. Since the app requires you to create a mount point so it can test the solid state drives, nobody walks in blindly.

Version 2 of DiskSpeed is designed to test individual drives. Read speed of a drive in a pool are affected by other devices in the pool. I'm removing that restriction in Version 3 (under development) but benchmarks will be local only (not able to be submitted). I'm contemplating removing the restriction in version 2....

If you experienced the blank benchmark screen, please update the DiskSpeed docker app to show version 2.10.7.5 and try again.

Concerning the blank screen on benchmarking a drive, it seems to be related to a cloned or restored drive in which both the old & new drive are still on the system. I'm adding logic to detect and allow the benchmark if one of the duplicate drives is not mounted. Current workarounds would be to change the Partition ID (s) on the old drive or do delete/recreate the partition.

@klee - PM sent