DiskSpeed, hdd/ssd benchmarking (unRAID 6+), version 2.10.7


Recommended Posts

 

13 hours ago, jbartlett said:

As for knowing which drives have been benchmarked, you can benchmark all drives at the same time from the main screen. Click the button "Benchmark Drives".

Thank you. I did so on my 1st unraid machine.

 

And I am surprised.

 

Diskspeed tries to test/bench a Device Disk4 sdaf  on the ASM1062 controller (and seems to be stuck at it).

I can't figure out which device it is. When I look in the main tab and search for an sdaf   I can't find any.

Even at the "Tools/System Devices" I can't find a Disk4 sdaf on my only ASM 1062 controller.

 

It seems diskspeed does not use the same naming  like unraid in the Main tab or in the Tools/System Devices Section.

 

Tools/System Devices:

================

PCI Devices and IOMMU Groups

IOMMU group 0:                [8086:9b33] 00:00.0 Host bridge: Intel Corporation Comet Lake-S 6c Host Bridge/DRAM Controller (rev 05)
IOMMU group 1:                [8086:1901] 00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 05)
                 [9005:028c] 01:00.0 RAID bus controller: Adaptec Series 7 6G SAS/PCIe 3 (rev 01)
                [1:1:0:0]    disk    ATA      TOSHIBA MG08ACA1 0102  /dev/sdb   16.0TB
                [1:1:4:0]    disk    ATA      TOSHIBA MG08ACA1 0102  /dev/sdc   16.0TB
                [1:1:5:0]    disk    ATA      TOSHIBA MG08ACA1 0102  /dev/sdd   16.0TB
                [1:1:6:0]    disk    ATA      TOSHIBA MG08ACA1 0102  /dev/sde   16.0TB
                [1:1:7:0]    disk    ATA      TOSHIBA MG08ACA1 0102  /dev/sdf   16.0TB
                [1:1:9:0]    disk    ATA      TOSHIBA MG08ACA1 0102  /dev/sdg   16.0TB
                [1:1:10:0]   disk    ATA      WDC  WUH721818AL PCGN  /dev/sdh   18.0TB
                [1:1:12:0]   disk    ATA      WDC  WUH721818AL PCGN  /dev/sdi   18.0TB
                [1:1:13:0]   disk    ATA      TOSHIBA MG09ACA1 0104  /dev/sdj   18.0TB
                [1:1:14:0]   disk    ATA      TOSHIBA MG09ACA1 0104  /dev/sdk   18.0TB
                [1:1:15:0]   disk    ATA      TOSHIBA MG09ACA1 0104  /dev/sdl   18.0TB
                [1:1:16:0]   disk    ATA      TOSHIBA MG09ACA1 0104  /dev/sdm   18.0TB
                [1:1:17:0]   disk    ATA      ST18000NM000J-2T SN01  /dev/sdn   18.0TB
                [1:1:18:0]   disk    ATA      ST18000NM000J-2T SN02  /dev/sdo   18.0TB
                [1:1:19:0]   disk    ATA      ST18000NM000J-2T SN02  /dev/sdp   18.0TB
                [1:1:20:0]   disk    ATA      ST18000NM000J-2T SN02  /dev/sdq   18.0TB
                [1:1:21:0]   disk    ATA      TOSHIBA MG09ACA1 0104  /dev/sdr   18.0TB
                [1:1:22:0]   disk    ATA      ST18000NM000J-2T SN01  /dev/sds   18.0TB
                [1:1:23:0]   disk    ATA      WDC  WUH721818AL PCGN  /dev/sdt   18.0TB
IOMMU group 2:                 [8086:9bc6] 00:02.0 VGA compatible controller: Intel Corporation Device 9bc6 (rev 05)
IOMMU group 3:                 [8086:06f9] 00:12.0 Signal processing controller: Intel Corporation Comet Lake PCH Thermal Controller
IOMMU group 4:                 [8086:06ed] 00:14.0 USB controller: Intel Corporation Comet Lake USB 3.1 xHCI Host Controller
                Bus 001 Device 001 Port 1-0        ID 1d6b:0002 Linux Foundation 2.0 root hub
                Bus 001 Device 002 Port 1-5        ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
                Bus 001 Device 003 Port 1-8        ID 0463:ffff MGE UPS Systems UPS
                Bus 001 Device 004 Port 1-11        ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive
                Bus 001 Device 005 Port 1-12        ID 1a40:0101 Terminus Technology Inc. Hub
                Bus 001 Device 007 Port 1-12.2        ID 0c45:7403 Microdia Foot Switch
                Bus 001 Device 008 Port 1-13        ID 048d:5702 Integrated Technology Express, Inc. ITE Device
                Bus 002 Device 001 Port 2-0        ID 1d6b:0003 Linux Foundation 3.0 root hub
                Bus 002 Device 002 Port 2-5        ID 0bda:0411 Realtek Semiconductor Corp. Hub
                 [8086:06ef] 00:14.2 RAM memory: Intel Corporation Comet Lake PCH Shared SRAM
IOMMU group 5:                 [8086:06e0] 00:16.0 Communication controller: Intel Corporation Comet Lake HECI Controller
IOMMU group 6:                 [8086:06d2] 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller
                [8:0:0:0]    disk    ATA      CT2000MX500SSD1  023   /dev/sdaa  2.00TB
                [9:0:0:0]    disk    ATA      CT2000MX500SSD1  023   /dev/sdab  2.00TB
                [2:0:0:0]    disk    ATA      ST18000NM000J-2T SN02  /dev/sdu   18.0TB
                [3:0:0:0]    disk    ATA      ST18000NM000J-2T SN02  /dev/sdv   18.0TB
                [4:0:0:0]    disk    ATA      ST18000NM000J-2T SN01  /dev/sdw   18.0TB
                [5:0:0:0]    disk    ATA      TOSHIBA MG09ACA1 0104  /dev/sdx   18.0TB
                [6:0:0:0]    disk    ATA      CT2000MX500SSD1  023   /dev/sdy   2.00TB
                [7:0:0:0]    disk    ATA      CT2000MX500SSD1  033   /dev/sdz   2.00TB
IOMMU group 7:                [8086:06c0] 00:1b.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #17 (rev f0)
IOMMU group 8:                [8086:06ac] 00:1b.4 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #21 (rev f0)
IOMMU group 9:                [8086:06b8] 00:1c.0 PCI bridge: Intel Corporation Device 06b8 (rev f0)
                [8086:06bc] 00:1c.4 PCI bridge: Intel Corporation Device 06bc (rev f0)
IOMMU group 10:                [8086:06bd] 00:1c.5 PCI bridge: Intel Corporation Comet Lake PCIe Port #6 (rev f0)
IOMMU group 11:                [8086:06bf] 00:1c.7 PCI bridge: Intel Corporation Device 06bf (rev f0)
IOMMU group 12:                [8086:06b0] 00:1d.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #9 (rev f0)
                [8086:06b4] 00:1d.4 PCI bridge: Intel Corporation Device 06b4 (rev f0)
IOMMU group 13:                 [8086:0697] 00:1f.0 ISA bridge: Intel Corporation Device 0697
                 [8086:06c8] 00:1f.3 Audio device: Intel Corporation Comet Lake PCH cAVS
                 [8086:06a3] 00:1f.4 SMBus: Intel Corporation Comet Lake PCH SMBus Controller
                 [8086:06a4] 00:1f.5 Serial bus controller: Intel Corporation Comet Lake PCH SPI Controller
                 [8086:0d4c] 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (11) I219-LM
IOMMU group 14:                 [144d:a808] 03:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
                [N:0:4:1]    disk    Samsung SSD 970 EVO Plus 2TB__1            /dev/nvme0n1  2.00TB
IOMMU group 15:                 [8086:15f2] 06:00.0 Ethernet controller: Intel Corporation Ethernet Controller I225-LM (rev 03)
IOMMU group 16:                 [1b21:0612] 07:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
                [10:0:0:0]   disk    ATA      ST18000NM000J-2T SN02  /dev/sdac  18.0TB
                [11:0:0:0]   disk    ATA      ST18000NM000J-2T SN02  /dev/sdad  18.0TB
                

 

 

 

DiskSpeed-sdaf02.png

Edited by DataCollector
Link to comment

There's several hidden iframes that are doing the actual tests and then updating the parent frame that's visible with the status. Just sitting there is a sign that it actually threw an error. You can see what it is by clicking the period at the end of "Click on a drive label to hide or show it." - it's a hidden link that will unhide the iframes.

 

In regards to Disk 2 (sdy), set the checkbox to disable SpeedGap detection. What this means is the slowest and fastest read speed (the difference is the "speed gap") exceeds a given range and by the looks of it, it couldn't determine it at all.

Link to comment

Hi,

I have encountered an error that (from what I managed to find) I have not seen mentioned somewhere else. I was trying to benchmark this controller:


MV64460/64461/64462 System Controller, Revision B

Marvell Technology Group Ltd.
RAID bus controller

Type: Add-on Card in PCIe Slot 2 (x1 PCI Express)
Current & Maximum Link Speed: 2.5GT/s width x4 (1 GB/s max throughput)
Capabilities: storage pm msi pciexpress bus_master cap_list rom

Port 1: sdj 8TB Seagate ST8000AS0002 Rev AR17  (Disk 13)
Port 2: sdk 2TB Western Digital WD20EARX Rev 51.0AB51 (Disk 7)
Port 3: sdl 4TB Western Digital WD40EFRX Rev 82.00A82 (Disk 9)
Port 4: sdm 2TB Western Digital WD20EARS Rev 80.00A80 (Disk 3)
Port 5: sdn 8TB Seagate ST8000DM004 Rev 0001 (Disk 12)
Port 6: sdo 8TB Western Digital WD80EZAZ Rev 83.H0A83
Port 7: sdp 8TB Western Digital WD80EZAZ Rev 83.H0A83(Parity)

I should add that according to the manual for the mobo, this slot is suposed to be PCIe v.2  (PCI Express 2.0 x16 Slot (PCIE5 @ x4 mode) which seems different with what Diskspeed is reporting.

 

and I get the following error (the error appears when the "Benchmarking Parity (sdp)" bar reaches 100%).. What could be causing it?

Quote

Benchmarking Parity (sdp):
Lucee 5.2.9.31 Error (expression)
Message     can't cast [dd:] string to a number value
Stacktrace     The Error Occurred in
/var/www/CustomTags.cfm: line 145

    143: <CFIF ListLen(CurrLine," ") GT 1 AND Find("record",CurrLine) EQ 0>
    144: <CFSET BytesRead=ListFirst(CurrLine," ")>
    145: <CFSET BytesDiff=BytesRead - LastBytesRead>
    146: <CFSET LastBytesRead=BytesRead>
    147: <CFIF Skip GT 0>

called from /var/www/TestControllerBandwidth.cfm: line 171

    169: <CFFILE action="write" file="#BWDir#/#DriveID#_benchmark.sh" mode="766" output="#cmd#" addnewline="NO">
    170: <CFEXECUTE name="#BWDir#/#DriveID#_benchmark.sh" timeout="3060" />
    171: <CFSET Result=GetReadAvg(ResultsFN,Drive.Attrib.Configuration.RPM,2,MaxGap)>
    172: <CFSET Avg=ListFirst(Result,"|")>
    173: <CFSET Max=ListLast(Result,"|")>

called from /var/www/DispController.cfm: line 97

    95: </CFIF>
    96: <CFELSE>
    97: <CFINCLUDE template="TestControllerBandwidth.cfm">
    98: <CFOUTPUT><br></CFOUTPUT>
    99: </CFIF>

Java Stacktrace     lucee.runtime.exp.CasterException: can't cast [dd:] string to a number value
     at lucee.runtime.op.Caster.toDoubleValueViaDate(Caster.java:564)
     at lucee.runtime.op.Caster.toDoubleValue(Caster.java:540)
     at lucee.runtime.op.Caster.toDoubleValue(Caster.java:438)
     at lucee.runtime.op.Operator.minusRef(Operator.java:1004)
     at customtags_cfm$cf.udfCall1(/CustomTags.cfm:145)
     at customtags_cfm$cf.udfCall(/CustomTags.cfm)
     at lucee.runtime.type.UDFImpl.implementation(UDFImpl.java:107)
     at lucee.runtime.type.UDFImpl._call(UDFImpl.java:357)
     at lucee.runtime.type.UDFImpl.call(UDFImpl.java:226)
     at lucee.runtime.type.scope.UndefinedImpl.call(UndefinedImpl.java:803)
     at lucee.runtime.util.VariableUtilImpl.callFunctionWithoutNamedValues(VariableUtilImpl.java:756)
     at lucee.runtime.PageContextImpl.getFunction(PageContextImpl.java:1718)
     at testcontrollerbandwidth_cfm$cf.call(/TestControllerBandwidth.cfm:171)
     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 dispcontroller_cfm$cf.call(/DispController.cfm:97)
     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)
 

 

container run:

Quote

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='DiskSpeed' --net='bridge' --privileged=true -e TZ="Europe/Athens" -e HOST_OS="Unraid" -e HOST_HOSTNAME="towerS" -e HOST_CONTAINERNAME="DiskSpeed" -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8888]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/jbartlett777/DiskSpeed/master/DiskSpeed.png' -p '18888:8888/tcp' -v '/mnt/user/appdata/DiskSpeed/':'/tmp/DiskSpeed':'rw' -v '/var/local/emhttp':'/var/local/emhttp':'ro' 'jbartlett777/diskspeed'

 

I should also mention that i have this controller in the same mobo and it is benchmarked with no problems  (although it might also be misreported) :

MV64460/64461/64462 System Controller, Revision B

Super Micro Computer Inc (Marvell Technology Group Ltd.)
SCSI storage controller

Type: Onboard Controller
Current & Maximum Link Speed: 2.5GT/s width x4 (1 GB/s max throughput)
Capabilities: scsi pm msi pciexpress bus_master cap_list rom

 

Edited by papnikol
additional info
Link to comment
On 6/10/2022 at 11:31 PM, papnikol said:

Benchmarking Parity (sdp)

Click on the DiskSpeed Docker icon and open a console window.

 

Copy-n-paste the following command after verifying your parity drive is still sdp and change it here if it is different.

dd if=/dev/sdp of=/dev/null bs=1310720 skip=0 iflag=direct status=progress conv=noerror

 

You should see it starting to copy data and updating every second with the progress. The MB/s value should quickly settle down with a typical 2-3 MB variance from one second to the next. When you press CTRL-C to abort (or let it read the entire drive), it should report something like the following:

2081423360 bytes (2.1 GB, 1.9 GiB) copied, 9.00526 s, 231 MB/s^C
1655+0 records in
1654+0 records out
2167930880 bytes (2.2 GB, 2.0 GiB) copied, 9.40043 s, 231 MB/s

 

 

Link to comment
On 6/10/2022 at 11:31 PM, papnikol said:

I should add that according to the manual for the mobo, this slot is suposed to be PCIe v.2  (PCI Express 2.0 x16 Slot (PCIE5 @ x4 mode) which seems different with what Diskspeed is reporting.

 

Go to the tools page in UNRAID and click on the System Devices icon. Find your storage card and take note of the domain ID. It'll look something like "07:00.0" and be listed after the two hex numbers in brackets. Open a console window and enter replacing the domain id with your value.

lspci -vv -s 07:00.0

 

Look for lines starting with "LnkCap" and "LnkSta" that report a speed & width. Please copy-n-paste the results here.

Link to comment
On 6/11/2022 at 7:31 AM, papnikol said:

I should add that according to the manual for the mobo, this slot is suposed to be PCIe v.2  (PCI Express 2.0 x16 Slot (PCIE5 @ x4 mode) which seems different with what Diskspeed is reporting.

It's reporting the controller link speed, PCIe 1.0 x4 is correct for a SASLP

Link to comment
  • 2 weeks later...

@jbartlett I am testing a few of my NVMe SSDs, and this one is quite stronage, Seagate FireCude 520, the speed was going up and down. Do you think I should replace this SSD? this one is a brand new one, can be on PCIe4, but I only have a PCIe3, so the speed was downgraded. but I should not been seeing up and down like this, right? I think something wrong with the brand new drive? image.thumb.png.54d6d1ec4cb07522795a74d9922c18d5.png

 

 

Link to comment
19 hours ago, ruihere said:

@jbartlett I am testing a few of my NVMe SSDs, and this one is quite stronage, Seagate FireCude 520, the speed was going up and down. Do you think I should replace this SSD? this one is a brand new one, can be on PCIe4, but I only have a PCIe3, so the speed was downgraded. but I should not been seeing up and down like this, right? I think something wrong with the brand new drive? 

 

First things first, your drive is fine. Nothing to worry about.

 

One thing that I didn't know when creating this application is exactly how SSD's handle storage that hasn't been written to. SSD's (and now some Spinners) know if a requested block has been written to or not if if it hasn't, it returns zeros without even accessing the stored media. This is why you'll get peaks that seem to exceed the rated read rate on this benchmark.

 

Version 3, under development, will create a 20GB file and then read that 20GB file back to get the peak read rate. You can take the flat "lows" on your speed graph to be the read rate of the drive.

Edited by jbartlett
Link to comment

I cant get the tool to run properly. Install on Unraid was fine and my drives all got discovered. But when I start a Benchmark it stops after about 15 Seconds and shows me this Error:

 

"ERROR","http-apr-8888-exec-9","06/23/2022","23:45:54","",";java.io.IOException: APR error: -32;lucee.runtime.exp.NativeException: java.io.IOException: APR error: -32
        at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:356)
        at org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:320)
        at org.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputStream.java:110)
        at lucee.runtime.writer.CFMLWriterImpl.flush(CFMLWriterImpl.java:267)
        at lucee.runtime.tag.Flush.doStartTag(Flush.java:61)
        at benchmarkdrivecontroller_cfm$cf.call(/BenchmarkDriveController.cfm:129)
        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)

 

Any Advice on this?

Link to comment
17 minutes ago, Shidar said:

I cant get the tool to run properly. Install on Unraid was fine and my drives all got discovered. But when I start a Benchmark it stops after about 15 Seconds and shows me this Error:

 

It looks like the server connection was aborted, the error happened trying to flush the buffer (send pending HTML to browser). The line # referenced is a command to send text to the browser.

 

Start up a benchmark with 2 or more drives and then click around on the period at the end of the "hide or show it". The period has a hidden link on it that will unhide the iframes doing the actual work with the benchmarks and may give a better error message. If it's basically the same, not sure how much I can help there. It actually flushes the buffer prior so it was working there.

image.png.714f61b57e058352393ad9bf29dbdbcf.png

 

How are you actually connecting to your unraid server? Straight connection, VPN, proxy, etc?

Link to comment
10 hours ago, jbartlett said:

How are you actually connecting to your unraid server? Straight connection, VPN, proxy, etc?


I connect directly if I am at home or via remote access.

I also get this Error when I start the container:

 

"ERROR","127.0.0.1-startStop-1","06/24/2022","10:38:15","","load-extension;Extension [18y6mr54k7gmk.lex] was not found at [/opt/lucee/server/lucee-server/context/extensions/installed/18y6mr54k7gmk.lex];lucee.runtime.exp.ApplicationException: Extension [18y6mr54k7gmk.lex] was not found at [/opt/lucee/server/lucee-server/context/extensions/installed/18y6mr54k7gmk.lex]
Link to comment
7 hours ago, Shidar said:


I connect directly if I am at home or via remote access.

I also get this Error when I start the container:

 

"ERROR","127.0.0.1-startStop-1","06/24/2022","10:38:15","","load-extension;Extension [18y6mr54k7gmk.lex] was not found at [/opt/lucee/server/lucee-server/context/extensions/installed/18y6mr54k7gmk.lex];lucee.runtime.exp.ApplicationException: Extension [18y6mr54k7gmk.lex] was not found at [/opt/lucee/server/lucee-server/context/extensions/installed/18y6mr54k7gmk.lex]

 

Something's wrong with the installation of the Docker app. Go to the Docker tab in the Unraid GUI, set "Advanced View" on, and then click on "Force update" on the DiskSpeed docker.

Link to comment
On 6/24/2022 at 6:19 PM, jbartlett said:

 

Something's wrong with the installation of the Docker app. Go to the Docker tab in the Unraid GUI, set "Advanced View" on, and then click on "Force update" on the DiskSpeed docker.

Sadly that didn´t help. Even if I remove the Container completely and reinstall it, it won´t work.

Link to comment
12 hours ago, jbartlett said:

 

Can you give some details as to your setup? What version of unraid? Anything out of the ordinary?


I just started so it´s a fresh install of Unraid 6.10.3. The Server is a Fujitsu Primergy TX1330 M1 with an Intel Xeon E3-1220 V3 and 24Gb of RAM. MB is a FUJITSU D3239-A1. Just 2 Disks currently in there. No VM and just a few Plugins/Containers running. 

Link to comment

I'm having some strange behavior on one drive where the first 80% or so is just flat then it starts to drop down.

Disk 1 threw a "Bandwidth was capped on drive" but I'm not sure how to remedy the situation.

Disks 13 and 15 showed the most wobble on the chart, maybe those are to be replaced next?

benchmark-speeds.thumb.jpeg.d4caeb12b3d2ad789ed797b4e64ae4ae.jpeg

 

Disk1.png.17eab16c9e7c1245644f23f46c47ce14.png

 

Disk13.png.b6a3514de37c12a524752b2766b06520.png

 

Disk15.png.575e50c5b7aa00d35df7f92cd8ed3d0c.png

Link to comment
17 minutes ago, FlyAg said:

Disk 1 threw a "Bandwidth was capped on drive" but I'm not sure how to remedy the situation.

Graph strongly suggests disk is linking @ SATA1 (150MB/s), SMART report will confirm.

 

@jbartlettIMHO it would be more useful to instead of showing the device max linking speed show the actual linking speed, or both.

Link to comment
12 minutes ago, JorgeB said:

Graph strongly suggests disk is linking @ SATA1 (150MB/s), SMART report will confirm.

 

@jbartlettIMHO it would be more useful to instead of showing the device max linking speed show the actual linking speed, or both.

Here is what I pulled from that drive's SMART report.

It does show: SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 1.5 Gb/s)

 

Any idea how that could be? I've got all my drives on a SAS2008 PCI-Express Fusion-MPT SAS-2, with a 24Bay SAS backplane.

WDC_WD80EZAZ-11TDBA0_7SJ60W7W-20220629-1111.txt

Link to comment
10 hours ago, Shidar said:


I just started so it´s a fresh install of Unraid 6.10.3. The Server is a Fujitsu Primergy TX1330 M1 with an Intel Xeon E3-1220 V3 and 24Gb of RAM. MB is a FUJITSU D3239-A1. Just 2 Disks currently in there. No VM and just a few Plugins/Containers running. 

I'll have to ponder this for a bit.

Link to comment
48 minutes ago, FlyAg said:

I'm having some strange behavior on one drive where the first 80% or so is just flat then it starts to drop down.

Disk 1 threw a "Bandwidth was capped on drive" but I'm not sure how to remedy the situation.

Disks 13 and 15 showed the most wobble on the chart, maybe those are to be replaced next?

 

Your WD80EFZX shows a normal curve line on the HDDB Heatmap but there have been others that show a wave something like yours. But the way yours vary from it's previous scan and what others have gotten has me doubting the good health of the drive. Personally, I'd replace it.

Link to comment
42 minutes ago, JorgeB said:

IMHO it would be more useful to instead of showing the device max linking speed show the actual linking speed, or both.

 

I'll look into that. The information showed here is what the drive is reporting that it supports. In this case, it is the result from the following bash command from the docker terminal in the supported features section: hdparm -I /dev/sdh

image.png.c68f4ad0e8902e1fd839dcf77ee9dff6.png

Link to comment
8 minutes ago, jbartlett said:

In this case, it is the result from the following bash command from the docker terminal in the supported features section: hdparm -I /dev/sdh

You could possibly use this instead:

smartctl -i /dev/sdX

And parse this line:

SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)

 

  • Thanks 1
Link to comment
  • 3 weeks later...
On 6/29/2022 at 1:44 PM, FlyAg said:

I'm going to double check the cabling on that slot and also try a different slot. I'm glad I found this tool because I don't think I would have ever detected this otherwise!

I believe that backplane I had was faulty. I had to get a new backplane anyway and now everything works well

  • Thanks 1
Link to comment
  • jbartlett changed the title to DiskSpeed, hdd/ssd benchmarking (unRAID 6+), version 2.10.7

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.