Community Developer
  • Content Count

  • Joined

  • Last visited

  • Days Won


jbartlett last won the day on August 6 2019

jbartlett had the most liked content!

Community Reputation

197 Very Good


About jbartlett

  • Rank
    John Bartlett
  • Birthday 07/20/1970


  • Gender
  • URL
  • Location
    Seattle, WA
  • Personal Text
    Foster parent for cats & kittens

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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.
  3. 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 harddrivedb@gmail.com? 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.
  4. 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.
  5. 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.
  6. 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? The file will be large so please don't attach it here. Please email it to harddrivedb@gmail.com
  7. FYI - if you have an issue with your drive images defaulting, update the docker app and it'll be restored.
  8. Can you visit this URL (replace the IP for your unRAID server) and create a debug file with controller info? The file will be large so please don't attach it here. Please email it to harddrivedb@gmail.com
  9. 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 th
  10. 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 harddrivedb@gmail.com the file storageref.json located in appdata/DiskSpeed/Instances/local ? I want to see how the drives are being referenced on your setup.
  11. 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.
  12. 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 su
  13. 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....
  14. 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.
  15. 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