jbartlett

Can you show me how you have the USBIP module vhci_hcd set up so I can duplicate the issue as you have it configured?

Are the most recent tests reflecting a line near the bottom of the graph? If so, then yes, I'd say it's likely a failed drive. Interesting enough, the SMART report doesn't show any bad sectors - which is pretty much the reason I created this app. If the more recent drives show the reads near the top of the graph but with a dip in the middle, I'd be interested in taking this drive off your hands to use for testing version 3 of the app. If it's all flat towards the bottom, I've already have a drive doing that.

I'd run an extended offline smart test on the drive, then check the smart report. If that doesn't show anything, perform a parity check which will read the entire drive, then check the smart report again. Or first swap out the drive, rebuild the replacement, and then check out what's up with the drive. I have a test drive that is flatlining on the benchmark and the smart report is all over the place with errors, even more so after I did a full read of the drive.

My backplane matches that one. I've been searching to see if the SAS drive can provide any extra information on the file system but so far I haven't found anything. If you could, could you create a full debug file with controller information and email it to me at [email protected]? The full debug file includes a copy of the sys bus tree with every small read only file included and it'll let me dig into it to see if having a physical SAS drive will be helpful.

What kind of connection do they have? My dev server has a backplane that has SATA & SAS connectors but they're both in the SATA form.

Glad you updated before I went out and bought a cheap SAS drive. 😁 I added the WD6001FFWX model but if you have others that show up without an image, you can view the drive and edit it to add one. You can also do this if you prefer alternate or rebranded images 'cause WD seems to come out with new ones every year.

It should like them but some code intended for version 3.0 got accidentally included and it fetches information on the drive partitions and it looks like the "parted" command isn't liking your drive. Can you visit this URL (replace the IP for your unRAID server) and create a debug file with controller info? http://192.168.1.7:18888/isolated/CreateDebugInfo.cfm The file will be large so please don't attach it here. Please email it to [email protected]

FYI - if you have an issue with your drive images defaulting, update the docker app and it'll be restored.

Can you visit this URL (replace the IP for your unRAID server) and create a debug file with controller info? http://192.168.1.7:18888/isolated/CreateDebugInfo.cfm The file will be large so please don't attach it here. Please email it to [email protected]

Okay guys, can you update the Docker and try again? I re-wrote the image fetch logic again to use a different method of referencing the drives. It's hard for me to duplicate some of these conditions because I don't have the drives in question. If you get an error, please reference the error in your reply but you don't need to include the long stack trace. It doesn't provide any value. I added a feature where if it couldn't find the drive by Vendor / Model (such as an invalid vendor where some SSD's return "ATA"), it'll search all the vendors to try to find a match on the model ID and sets the vendor to a match.

I think I see what's going on here. The app creates a reference by Vendor & Model so that multiple drives of the same kind can be quickly cross referenced. SSD's are notorious for not listing a Vendor or listing the incorrect vendor. If you could, please attach or email me at [email protected] the file storageref.json located in appdata/DiskSpeed/Instances/local ? I want to see how the drives are being referenced on your setup.

Anyone have any non-IT mode hardware RAID PCIe controllers they're willing to part with? My only requirement is that the RAID is configured during the bootup so it's presented as one drive to unRAID. I'm looking to add support for RAIDed drives to my DiskSpeed app. I have a "SAS2308 PCI-Express Fusion-MPT SAS-2" card but I only see options to flash it to IT mode, not back to IR mode.

Pushed version 2.9.1. Some stuff for version 3.0 got pushed into 2.9.1 as a result of the above issue. Added the rest of the support for optimizing the drive images after downloading to ensure the CSS for centering any text overlays is correct. Drive Edit: Fixed the Z index which prevented click-n-dragging the slider for horizontal placement of the text if the text layer was rotated. This image optimization may change how your thumbnails look. If it does, then the CSS behind it wasn't properly set up which this corrected. If you make any changes to a drive image, be sure to submit your changes and your particular edits will be restored in the event a full scan is done (such as deleting the DiskSpeed appdata directory). Note that the edits are system specific, if you have more than one UNRAID server, you'll need to make the same changes to each & submit.

Man, today is NOT my day. I accidentally included an updated version of the hardware scan script intended for version 3. It'll display "optimizing images" and then nothing. If you click on the header, it'll take you to the main screen. Working on fixing that....

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.

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 [email protected]

Ugh. Something weird is going on. I can't duplicate. Investigating...

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

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

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.

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.

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.

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.

Note that the version of memtest built into UNRAID is a much older version that doesn't have the newer testing capabilities of the current version located on memtest's website. This is no fault of unraid, the people behind memtest won't allow anything newer to be installed by 3rd parties.

I doubt they'd be considering putting Slackware 15.0 in the UNRAID OS until it's released as stable, it's not even in the beta phase yet.