DiskSpeed, hard drive benchmarking (unRAID 6+), version 2.9.2


601 posts in this topic Last Reply

Recommended Posts

docker exec -it DiskSpeed bash

root@af468d0f3720:/usr/local/tomcat# nvme id-ns /dev/nvme0n1
NVME Identify Namespace 1:
nsze    : 0x3a386030
ncap    : 0x3a386030
nuse    : 0x10facc48

nsze: Total size of the name space LBA

ncap: Max number of LBA

nuse: LBA's allocated to the name space.

 

It looks like if I do a dd read on the device starting at the start not to exceed "nuse" would return data read

If nuse is under a given duration/size, a benchmark can not be done.

Alternately, if a file is found in excess of a given size that has no unwritten extends reported by "filefrag -e <fn>" on it, it can be read for a given number of seconds.

 

Thoughts?

Link to post
  • 2 weeks later...
  • Replies 600
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

This Docker Application will let you view your storage controllers & the drives attached to them and perform Benchmarks on both. Controller Benchmarks helps to identify if the drives attached to i

I'm taking this application out of BETA status. Version 2.0 has been released.   Release 2.0 Added progress bars to the drive benchmarking Rewrote the Controller Benchmark to be

I just noticed a trend in the file fragmentation. It seems the OS has the tendency to break the file up into chunks of a set size. I found this really strange because, well, why do it at all? Noticing

Posted Images

I have tried searching but all i get is the beginning of this thread and going through 22 pages is a task lol.

 

I am getting "bandwidth capped on disk" for all of my disks. What should i start looking at? Thanks

I am running on a dell R720 with

 

SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon]

Dell (Broadcom / LSI)
Serial Attached SCSI controller

Type: Onboard Controller
Current & Maximum Link Speed: 5GT/s width x8 (4 GB/s max throughput)
Capabilities: storage pm pciexpress vpd msi msix bus_master cap_list rom

 

 

 

Link to post
9 hours ago, Keebler said:

I am getting "bandwidth capped on disk" for all of my disks. What should i start looking at? Thanks

I am running on a dell R720 with

 

If it's on an individual disk it would be represented by a somewhat flat line on the graph over several test locations. Since the trend is always downward on a spinner, a flat area means the drive is capable of outputting more data than the controller (or downstream) can handle.

 

If it's on a controller benchmark, it means that the controller can't handle the maximum output of all the drives connected to it at the same time and is a bottleneck.

 

Submit graphs to better explain what you are referencing if this doesn't cover it.

Link to post
12 hours ago, jbartlett said:

 

If it's on an individual disk it would be represented by a somewhat flat line on the graph over several test locations. Since the trend is always downward on a spinner, a flat area means the drive is capable of outputting more data than the controller (or downstream) can handle.

 

If it's on a controller benchmark, it means that the controller can't handle the maximum output of all the drives connected to it at the same time and is a bottleneck.

 

Submit graphs to better explain what you are referencing if this doesn't cover it.

 

I noticed this time around that different drives showed up as being capped. Unless im looking at this wrong. I have some really slow drives.

 

 

controller-benchmark.png

Graph1.PNG

Link to post

Look up the drives on the HDDB to see if other people are getting similar speeds. If so, I may need to adjust the bandwidth cap threshold. Note that you can click on the drive labels on the line graphs to hide drives to better show the ones affected.

Link to post
  • 3 weeks later...
  • jbartlett changed the title to DiskSpeed, hard drive benchmarking (unRAID 6+), version 2.8.1
  • 3 weeks later...

I've determined a way to reliably benchmark SSD's though it won't help in isolating troublesome spots like drives with platters. To test SSD's, I will create a 10GB file with random data and then read that file back bypassing the cache. SSD's must have at least 50GB space available to be tested.

 

This feature will be in version 3 which I'm working on now.

 

Since version 3 will also display partition information, I plan on adding write benchmarking support in a subsequent release on drives with no partitions defined.

Link to post

Upgraded to 6.9.0 recently. Changed around some of my SSDs/nvme uses, and started using single-disk pools instead of unassigned devices. Decided to just run a test on my nvme, which is now my cache drive (formatted XFS with the new 1MB offset). The result was really disappointing compared to when I first ran a test. A follow-up test showed a similar curve.

 

EJPu9nJ.png

 

My other SSD drives are fairly consistent with prior tests, albeit slightly slower (about 40MB/s).

 

There is data on the nvme now compared to when I first ran the test, and a trim did run this morning, but this is not an expected result, right? Any suggestions on what I can do to troubleshoot? Could this be a result of 6.9.0? Thanks for any insight!

Link to post
Posted (edited)
1 hour ago, kaiguy said:

My other SSD drives are fairly consistent with prior tests, albeit slightly slower (about 40MB/s).

 

There is data on the nvme now compared to when I first ran the test, and a trim did run this morning, but this is not an expected result, right? Any suggestions on what I can do to troubleshoot? Could this be a result of 6.9.0? Thanks for any insight!

 

The hard drive benchmark turns out to not be the correct way to test solid state devices. If it accesses an area that has been assigned/written, then you will get back expected/rated results. If it accesses an area that has not been written to, you will get back far higher results since no storage medium is accessed. This method will only properly work with solid state drives that have been completely filled up at least once. As such, different SSD's will give different results even if they're the same model based on previous usage.

 

I'm working on completely redoing how solid state devices are benchmarked and as such benchmarking may not be available to everyone based on how the drive is used. The way I intend to do it is to identify a large file and read it or create a 50GB file and read it back. Solid state devices that exist in a multi-device pool will not be able to be benchmarked when version 3 is released. A future version may allow it by bulk reading the device until it can identify a high/low range of numbers so it can figure out which range represents allocated areas and which range represents unallocated areas.

Edited by jbartlett
Link to post

Hey @jbartlett - handy tool, thanks! Small issue for mine I hope you can help with -

 

None of the images are showing up, though every drive is in the DB:

Drive_images.png.ea2f4aff1107917a9311b6c06531d4e5.png

 

 

Looking at the drive details, I can't find any reason for this, as the model, serial, vendor, and fw rev all line up:

Drive_detailed.png.120d839951f5c11b71ac2ced08a03ffc.png

 

 

The logs show nothing of note that I could find (all just loading module stuff), but here's the startup info:

2021-03-09 13:42:29.622 Start CFML Controller

2021-03-09 13:42:29.624 touched monitors
===================================================================
WEB CONTEXT (cbe856ff790c9ba5208811309bdf168b)
-------------------------------------------------------------------
- config:/opt/lucee/web (custom setting)
- webroot:/var/www/
- hash:cbe856ff790c9ba5208811309bdf168b
- label:cbe856ff790c9ba5208811309bdf168b

 

I had the same thing on 6.8.3, and just never really dug into it, but now have had the same on 6.9 and 6.9.1... Any idea what's going on here? I'd think the controller wouldn't matter since it's using the onboard chipset and smart is accessible, but in the event it matters, this particular host is using the intel C621 onboard. I'll try and get the diagnostic output either tonight or tomorrow in the event there isn't anything glaringly obvious in the above that I'm just missing.

 

Thanks!

 

 

Link to post
5 hours ago, BVD said:

None of the images are showing up, though every drive is in the DB

 

Does the server have Internet access? That's how the drive images are fetched. If so, can you hit the "Rescan Controllers" button and see what it says towards the bottom where it says "Checking Hard Drive Database for drives"?

 

If it doesn't have access to the internet, adding the image is simple. View the HDDB and download the image for the drive.  View any one of the drives on your server in DiskSpeed and click the "Edit Drive" button. From there, you can upload the image for the drive to display.

 

Link to post

It does have internet access - in the event it was related to some funky docker network issue, I've tried setting it to Host, setting the port to one I've verified isn't in use anywhere on my network per pfSense, etc...

However, one weird thing is, the downloading of the images is actually working fine; the .png files exist. This led me to look at permissions, and I found something odd:

drwxrwxrwx 1  65534 users    0 Mar  9 22:38 DiskSpeed/
drwxrwxrwx 1 nobody users   34 Feb  2 14:25 Authelia/

 

It's showing the 'nobody' user differently than any other folder or share displays it's permissions. Changing the permissions fixes nothing as it just recreates them back to the same thing. The parent directory (appdata) shows up as everything other than the diskspeed folder does. Tried the beta tag (it was the only other one available, but I figured it was worth a shot), no dice. Finally, I disabled all data collection from other areas (disabled my syslog server, disabled telegraf), but again, no change.

 

With each change, I've wiped and allowed it to recreate the DiskSpeed folder contents so there wasn't any interference between one run and the next.

 

I've added the debug file here.

TrialUser_20210309_225359.tar.gz

Link to post
13 hours ago, BVD said:

It does have internet access

 

The program logs the results it gets back and it shows an HTTP 200 status code but an empty result. I just pushed an update to Docker which will also log the URL it used to check for the drive images. Please update the docker and if it does not automatically scan the hardware, click the "Rescan controllers" button and then send me another small debug file.

Link to post

Pulled and attached

 

Found something interesting in the host side logs - seems to hit this once for each disk attached:

at lucee.runtime.extension.RHExtension.toResource(RHExtension.java:677)
at lucee.runtime.extension.RHExtension.<init>(RHExtension.java:194)
at lucee.runtime.config.XMLConfigWebFactory.loadExtensionBundles(XMLConfigWebFactory.java:4369)
at lucee.runtime.config.XMLConfigWebFactory.load(XMLConfigWebFactory.java:450)
at lucee.runtime.config.XMLConfigServerFactory.load(XMLConfigServerFactory.java:174)
at lucee.runtime.config.XMLConfigServerFactory.newInstance(XMLConfigServerFactory.java:125)
at lucee.runtime.engine.CFMLEngineImpl.getConfigServerImpl(CFMLEngineImpl.java:788)
at lucee.runtime.engine.CFMLEngineImpl.<init>(CFMLEngineImpl.java:270)
at lucee.runtime.engine.CFMLEngineImpl.getInstance(CFMLEngineImpl.java:623)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at lucee.loader.engine.CFMLEngineFactory.getEngine(CFMLEngineFactory.java:1589)
at lucee.loader.engine.CFMLEngineFactory.initEngine(CFMLEngineFactory.java:395)
at lucee.loader.engine.CFMLEngineFactory.initEngineIfNecessary(CFMLEngineFactory.java:278)
at lucee.loader.engine.CFMLEngineFactory.getInstance(CFMLEngineFactory.java:174)
at lucee.loader.engine.CFMLEngineFactory.getInstance(CFMLEngineFactory.java:212)
at lucee.loader.servlet.CFMLServlet.init(CFMLServlet.java:42)
at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1188)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1132)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1021)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5085)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5397)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1410)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1400)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

 

TrialUser_20210310_130033.tar.gz

Link to post
48 minutes ago, BVD said:

Found something interesting in the host side logs - seems to hit this once for each disk attached:

That's normal operation.

 

I'm seeing some weird results for your system when fetching the drive images that don't show up for me. Just to verify, when you click on "Purge Everything and Start Over", it scans the controllers and at the end you do NOT see something like this:

 

11:48:48 Fetching drive images
11:48:49 Drive image found for Western Digital WDS256G1X0C
11:48:49 Drive image found for Western Digital WD6002FFWX
11:48:49 Drive image found for Seagate ST4000DM000
11:48:49 Drive image found for Western Digital WD100EFAX
11:48:49 Drive image found for Seagate ST8000AS0002
11:48:49 Drive image found for Western Digital WD80EFZX
11:48:49 Drive image found for Western Digital WD2002FAEX

11:48:49 Fetching Drive Platter Information
11:48:49 Checking Hard Drive Database for drives
11:48:49 Optimizing images...

11:48:49 Configuration saved

Link to post

It recognizes the drives and displays them in bold - it just doesn't pull the images. I can also confirm that I can pull the images directly from the server with wget

 

DiskSpeed - Disk Diagnostics & Reporting tool
Version: 2.8.1

Scanning Hardware
13:56:19 Spinning up hard drives
13:56:19 Scanning system storage
13:56:23 Scanning USB Bus
13:56:31 Scanning hard drives
13:56:35 Scanning storage controllers
13:56:38 Scanning USB hubs & devices
13:56:38 Scanning motherboard information
13:56:38 Fetching known drive vendors from the Hard Drive Database
13:56:41 Found controller WD Black SN750 / PC SN730 NVMe SSD
13:56:41 Found drive WDS500G3X0C-00SJG0 Rev: 111110WD Serial: 20359E805968 (nvme1n1)
13:56:41 Found controller WD Black SN750 / PC SN730 NVMe SSD
13:56:41 Found drive WDS500G3X0C-00SJG0 Rev: 111110WD Serial: 203686802824 (nvme2n1)
13:56:41 Found controller C620 Series Chipset Family SSATA Controller [AHCI mode]
13:56:41 Found drive Samsung SSD 860 EVO Rev: RVT01B6Q Serial: S3Z6NB0K301833Y (sdb)
13:56:41 Found controller C620 Series Chipset Family USB 3.0 xHCI Controller
13:56:41 Found drive SanDisk' Cruzer Fit Rev: 0 Serial: 4C530000030627220171 (sda)
13:56:41 Found controller WD Black SN750 / PC SN730 NVMe SSD
13:56:41 Found drive WDS500G3X0C-00SJG0 Rev: 111110WD Serial: 20359E804913 (nvme0n1)
13:56:41 Found controller C620 Series Chipset Family SATA Controller [AHCI mode]
13:56:41 Found drive Seagate ST16000NM001G Rev: SN03 Serial: ZL28N8NB (sdc)
13:56:41 Found drive Seagate ST16000NM001G Rev: SN03 Serial: ZL28BYR3 (sdd)
13:56:41 Found drive Western Digital WD6003FFBX Rev: 83.00A83 Serial: V8K0NJVH (sde)
13:56:41 Found drive Western Digital WD6003FFBX Rev: 83.00A83 Serial: V8K0EHLH (sdf)
13:56:41 Found drive Western Digital WD6003FFBX Rev: 83.00A83 Serial: V8K0MVMH (sdg)
13:56:41 Found drive Western Digital WD6003FFBX Rev: 83.00A83 Serial: V8K0EJKH (sdh)
13:56:41 Found drive Western Digital WD6003FFBX Rev: 83.00A83 Serial: V8H3PZSR (sdi)
13:56:41 Found drive Western Digital WD6003FFBX Rev: 83.00A83 Serial: V9H7HG6L (sdj)
13:56:41 Found controller WD Black SN750 / PC SN730 NVMe SSD
13:56:41 Found drive WDS500G3X0C-00SJG0 Rev: 111110WD Serial: 205115802117 (nvme3n1)
13:56:42 Fetching drive images
13:56:42 Fetching Drive Platter Information
13:56:42 Checking Hard Drive Database for drives
13:56:42 Configuration saved

 

 

I can also confirm that I can pull the images from the command line without issue on the host:
 

root@milkyway:/# wget "http://strangejourney.net/diskspeed/Drives/ADATA/ASP580SS3-120GM-C/Johnathan_Bartlett_154B_007A_D97H_E03000000471.png"
--2021-03-10 13:58:45--  http://strangejourney.net/diskspeed/Drives/ADATA/ASP580SS3-120GM-C/Johnathan_Bartlett_154B_007A_D97H_E03000000471.png
Resolving strangejourney.net (strangejourney.net)... 205.210.191.162
Connecting to strangejourney.net (strangejourney.net)|205.210.191.162|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 41097 (40K) [image/png]
Saving to: ‘Johnathan_Bartlett_154B_007A_D97H_E03000000471.png’

Johnathan_Bartlett_154B_007A_D97H_E03000000471.png                  100%[================================================================================================================================================================>]  40.13K  --.-KB/s    in 0.09s

2021-03-10 13:58:45 (456 KB/s) - ‘Johnathan_Bartlett_154B_007A_D97H_E03000000471.png’ saved [41097/41097]

 

Edited by BVD
Link to post
12 minutes ago, BVD said:

It recognizes the drives and displays them in bold - it just doesn't pull the images.

I found and fixed the issue. You just need to click the "Rescan Controllers" button.

Link to post

Now I can't get past the initial scan screen:

 

Quote

DiskSpeed - Disk Diagnostics & Reporting tool
Version: 2.8.1
 

Scanning Hardware
14:17:42 Spinning up hard drives
14:17:42 Scanning system storage
14:17:44 Scanning USB Bus
14:17:52 Scanning hard drives
14:17:56 Scanning storage controllers
14:17:58 Scanning USB hubs & devices
14:17:58 Scanning motherboard information
14:17:58 Fetching known drive vendors from the Hard Drive Database
14:18:00 Found controller WD Black SN750 / PC SN730 NVMe SSD
14:18:00 Found drive WDS500G3X0C-00SJG0 Rev: 111110WD Serial: 20359E805968 (nvme1n1)
14:18:00 Found controller WD Black SN750 / PC SN730 NVMe SSD
14:18:00 Found drive WDS500G3X0C-00SJG0 Rev: 111110WD Serial: 203686802824 (nvme2n1)
14:18:00 Found controller C620 Series Chipset Family SSATA Controller [AHCI mode]
14:18:00 Found drive Samsung SSD 860 EVO Rev: RVT01B6Q Serial: S3Z6NB0K301833Y (sdb)
14:18:00 Found controller C620 Series Chipset Family USB 3.0 xHCI Controller
14:18:00 Found drive SanDisk' Cruzer Fit Rev: 0 Serial: 4C530000030627220171 (sda)
14:18:00 Found controller WD Black SN750 / PC SN730 NVMe SSD
14:18:00 Found drive WDS500G3X0C-00SJG0 Rev: 111110WD Serial: 20359E804913 (nvme0n1)
14:18:00 Found controller C620 Series Chipset Family SATA Controller [AHCI mode]
14:18:00 Found drive Seagate ST16000NM001G Rev: SN03 Serial: ZL28N8NB (sdc)
14:18:00 Found drive Seagate ST16000NM001G Rev: SN03 Serial: ZL28BYR3 (sdd)
14:18:00 Found drive Western Digital WD6003FFBX Rev: 83.00A83 Serial: V8K0NJVH (sde)
14:18:00 Found drive Western Digital WD6003FFBX Rev: 83.00A83 Serial: V8K0EHLH (sdf)
14:18:00 Found drive Western Digital WD6003FFBX Rev: 83.00A83 Serial: V8K0MVMH (sdg)
14:18:00 Found drive Western Digital WD6003FFBX Rev: 83.00A83 Serial: V8K0EJKH (sdh)
14:18:00 Found drive Western Digital WD6003FFBX Rev: 83.00A83 Serial: V8H3PZSR (sdi)
14:18:00 Found drive Western Digital WD6003FFBX Rev: 83.00A83 Serial: V9H7HG6L (sdj)
14:18:00 Found controller WD Black SN750 / PC SN730 NVMe SSD
14:18:00 Found drive WDS500G3X0C-00SJG0 Rev: 111110WD Serial: 205115802117 (nvme3n1)
14:18:00 Fetching drive images

Lucee 5.2.9.31 Error (expression)

Messagekey [SSD 860 EVO] doesn't exist

StacktraceThe Error Occurred in
/var/www/GetInitialDriveImage.cfm: line 41 

39: <!--- <CFOUTPUT><img src="data:image/png;base64, #Info[i].Image#" /><br></CFOUTPUT> --->
40: <CFIF RefreshDrive EQ 0>
41: <CFSET UpdateList=Ref.Vendor[Info[i].Vendor][Info[i].Model]>
42: <CFELSE>
43: <CFSET UpdateList=NeedImage>
 

called from /var/www/ScanControllers.cfm: line 1856 

1854: </CFLOOP>
1855: <CFIF NeedImage NEQ "">
1856: <CFINCLUDE TEMPLATE="GetInitialDriveImage.cfm">
1857: </CFIF>
1858: <CFIF NeedPlatter NEQ "">
 

called from /var/www/ScanControllers.cfm: line 1762 

1760: </CFIF>
1761: </CFLOOP>
1762: </CFLOOP>
1763: 
1764: <!--- Check for missing keys --->
 

Java Stacktracelucee.runtime.exp.ExpressionException: key [SSD 860 EVO] doesn't exist
  at lucee.runtime.type.util.StructSupport.invalidKey(StructSupport.java:69)
  at lucee.runtime.type.StructImpl.get(StructImpl.java:135)
  at lucee.runtime.type.util.StructSupport.get(StructSupport.java:244)
  at lucee.runtime.util.VariableUtilImpl.get(VariableUtilImpl.java:263)
  at lucee.runtime.PageContextImpl.get(PageContextImpl.java:1516)
  at getinitialdriveimage_cfm$cf.call(/GetInitialDriveImage.cfm:41)
  at lucee.runtime.PageContextImpl._doInclude(PageContextImpl.java:933)
  at lucee.runtime.PageContextImpl._doInclude(PageContextImpl.java:823)
  at lucee.runtime.PageContextImpl.doInclude(PageContextImpl.java:805)
  at scancontrollers_cfm$cf.call_000168(/ScanControllers.cfm:1856)
  at scancontrollers_cfm$cf.call(/ScanControllers.cfm:1762)
  at lucee.runtime.PageContextImpl._doInclude(PageContextImpl.java:933)
  at lucee.runtime.PageContextImpl._doInclude(PageContextImpl.java:823)
  at lucee.runtime.listener.ClassicAppListener._onRequest(ClassicAppListener.java:66)
  at lucee.runtime.listener.MixedAppListener.onRequest(MixedAppListener.java:45)
  at lucee.runtime.PageContextImpl.execute(PageContextImpl.java:2464)
  at lucee.runtime.PageContextImpl._execute(PageContextImpl.java:2454)
  at lucee.runtime.PageContextImpl.executeCFML(PageContextImpl.java:2427)
  at lucee.runtime.engine.Request.exe(Request.java:44)
  at lucee.runtime.engine.CFMLEngineImpl._service(CFMLEngineImpl.java:1090)
  at lucee.runtime.engine.CFMLEngineImpl.serviceCFML(CFMLEngineImpl.java:1038)
  at lucee.loader.engine.CFMLEngineWrapper.serviceCFML(CFMLEngineWrapper.java:102)
  at lucee.loader.servlet.CFMLServlet.service(CFMLServlet.java:51)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
  at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:292)
  at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
  at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
  at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240)
  at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
  at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:212)
  at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:94)
  at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:492)
  at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141)
  at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:80)
  at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:620)
  at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:684)
  at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
  at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:502)
  at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1152)
  at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
  at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.doRun(AprEndpoint.java:2527)
  at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run(AprEndpoint.java:2516)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
  at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
  at java.lang.Thread.run(Thread.java:748)
 

Timestamp3/10/21 2:18:05 PM CST

 

Link to post
7 hours ago, BVD said:

Now I can't get past the initial scan screen

 

Please update the docker and try again. I re-wrote the process which fetches the images so I'm hoping it works for you now.

 

In addition, if you edit a drive image and then submit it, it will restore it on the same UNRAID box.

 

If you get another error, please create a full debug file from the DiskSpeed app and email it to harddrivedb@gmail.com

Link to post
  • jbartlett changed the title to DiskSpeed, hard drive benchmarking (unRAID 6+), version 2.9
4 hours ago, elmetal said:

 

Thanks for the pastebin, it helped me isolate the issue.

 

Problem happened when a drive was not found in the database but the docker app expected some kind of image (legacy copy-n-paste). It didn't happen to me because all my drives existed. I added an ancient IDE drive, duplicated the error, and fixed it.

 

Please update your Docker if you ran into this issue.

Link to post
  • jbartlett changed the title to DiskSpeed, hard drive benchmarking (unRAID 6+), version 2.9.2

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.