Community Developer
  • Posts

  • Joined

  • Last visited

  • Days Won


jbartlett last won the day on August 6 2019

jbartlett had the most liked content!


About jbartlett

  • Birthday 07/20/1970


  • Member Title
    John Bartlett


  • 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.

jbartlett's Achievements

Community Regular

Community Regular (8/14)



  1. Looks to be harmless, related to Java 11. https://dev.lucee.org/t/illegal-reflective-access/7052 https://issues.apache.org/jira/browse/FELIX-5765
  2. This is something I've been wanting to investigate too. But after you edit a drive image, click the "Submit Drive" button that shows up after you save the update (or viewing the drive after updating). Click the button again to confirm. You only need to do this step once per drive model. Next update, it should restore your drive image & overlay from what you uploaded. This is a per-machine setting.
  3. Remove the DiskSpeed directory, edit the Docker image, and save it. Check to see if the DiskSpeed directory has been recreated.
  4. What kind of upload? Drive image upload or Drive & Benchmark data? And please try again, I tested both and got back successful messages for both. If it does fail, note the time & time zone that you tried and I'll check the logs.
  5. It looks like the permissions on the new directory aren't correct and the application can't write to it. While the Docker config is set to R/W, that doesn't mean squat if the directory itself is not writeable by Docker. Open a shell prompt to the unraid server itself (not the Docker) and enter in the following lines. This is the same code when you run Unraid tool to apply new permissions. chmod -R u-x,go-rwx,go+u,ugo+X '/mnt/arraycache/appdata/DiskSpeed' chown -R nobody:users '/mnt/arraycache/appdata/DiskSpeed' sync
  6. In version 2.9.5, I had taken out the "apt update" command in favor of keeping the docker size smaller since this Docker relies on another Docker (Lucee) and they had the same command. I put it back in to ensure that when *I* build, the my DiskSpeed docker is current. Any other subsequent updates will rely on other teams implementing such as Lucee then Apache Tomcat and I think Tomcat is build off of Debian.
  7. Version 3 (in dev) will have write testing for solid state media because it's required to read an existing file on some drives vs reading a location on the drive. I'm contemplating adding write testing for spinners but if I do, it'll likely be ONLY on a drive with no partitions. I was able to duplicate this and implemented a fix including some other oddities I found from the newer version of Lucee and the base OS. Version 2.9.6 pushed.
  8. Pushed version 2.9.5 to the docker hub. @Howboys - let me know if it resolves your issues with the EOL notice. It's using the latest build of the Lucee app server. I'm starting to use tagged versions. 2.9.5/latest resolves issues with funky partition output from the "parted" utility. Well, hopefully resolves it as I couldn't duplicate. If you have issues with the version 2.9.5, change the repository to "jbartlett777/diskspeed:2.9.4" to roll back to the previous version.
  9. I plan on pushing an update soon<tm> with the latest version of Lucee which will resolve this.
  10. Renaming the "Instances" directory under "/appdata/DiskSpeed" will do the same without needing to install. If you do get this issue again and it's resolved by renaming the directory, let me know so I can get a copy of your "bad" data so I can duplicate and fix the issue.
  11. I've verified that it's not a problem with having more than 26 drives, I added two 10 port hubs and filled them with USB drives to push my sdx counts over sdaa and benchmarked sdab and sdac, no issues and it benchmarked the correct drive. Does it report something like "SpeedGap detected"? If so, you'll need to disable that when starting a benchmark from the main page, not from the drive itself. Also, if you select 2 or more drives to benchmark, you'll see the text "Click on a drive label to hide or show it." - that period on the end is a hidden hyperlink, clicking on it will reveal the hidden iframes that perform the actual work and you can see what's happening and if there's an issue.
  12. The error happens on the sdc, it's partition output isn't standard with extra blank lines, some padded with spaces. I've added code to handle the extra lines and code to catch other gotcha's so it'll continue.
  13. I've changed my default file system to "btrfs" under "Settings > Disk Settings" on my backup/development NAS system. If I run the new config option via "Tools > New Config", it does more than just reset the drive slots, it resets at least the default file system in Disk Settings as it gets changed to "xfs". I discovered this issue after taking a drive out of the Drive 2 slot, resetting the config so I can wipe the partitions and re-add as btrfs, and it was added & formatted with xfs. I was able to repeat the steps to duplicate. 1. Set default file system to btrfs 2. Run "New Config", preserve all drive settings. 3. View Disk Settings, default file system is now xfs nasbackup-diagnostics-20220821-1857.zip
  14. It looks like you have more than 26 drives attached. Can you submit a debug file using the "Create Debug File" at the bottom of the page? You do not need the Controller Info item.
  15. When you first pull up the app or click on the "DiskSpeed" label at the top of any page, it should display a "Benchmark Drives" button. That in turn will display a Benchmark page where you can optionally select which drives you want to test. By default, it starts with all drives but if you uncheck the "Check all drives" checkbox, all your drives will be listed for individual selection.