jbartlett

Community Developer
  • Posts

    1725
  • Joined

  • Last visited

  • Days Won

    7

Everything posted by jbartlett

  1. 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.
  2. 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. How are you actually connecting to your unraid server? Straight connection, VPN, proxy, etc?
  3. 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.
  4. 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.
  5. 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
  6. 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.
  7. There's not much I can do if the Docker app won't even start if a Preclear is underway. The Docker is just an application server, my program hasn't even kicked off until you open the GUI. I've no idea what would cause that but you might get a hint if you monitor the syslog while you start it. 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". Above it will be a benchmark graph if any have been done yet and you can see by which ones aren't included that still need to be done. You can optionally benchmark just those drives at the same time by unchecking the drives that have already been done on the following screen.
  8. You'll find better support posting this on the General Support along with a diagnostic file and the video you linked here. On another note, as a developer myself, thank you for including the video as such items can be hard to describe and get a matching understanding.
  9. From my understanding, returns that the seller doesn't want back are frequently stacked onto a pallet and then sold as-is as a kind of "Mystery Box" without the buyer knowing what they are getting.
  10. It's not uncommon it seems based on other submissions. But yeah, I'll need to code in a catch for sine waves 😅 It may be a good idea to get into the habit of putting your new drives through at least one pre-clear pass, one write pass at a minimum, which will prevent this from happening.
  11. It's the built-in docker user but I have a task that goes out and opens up the permissions on any new files.
  12. Gotcha - I thought this was the built in functionality, I'll report it on the Mover Tuning plugin thread.
  13. The way it reads to me is to collapse multiple underscores such as "drive______id" to "drive_id". Just stating this because that's not what is actually happening - it's converting multiple underscores into spaces but leaving the last underscore.
  14. [rc6] Changing root user password will log out all webGUI browser sessions. I changed the password of user "jess" and I was logged out of the webGUI. Based on the change log, I should remain logged in. nas-diagnostics-20220512-1951.zip
  15. I think I figured out what happened. In the Historical section, it lists: Samsung_SSD_960_EVO_500GB_S3X4NB0K309824V (Samsung_960EVO) In the UD list, it has: Samsung SSD 960 EVO 500GB_S3X4NB0K309824V + 1: Samsung_960EVO It looks like rc8 removed the underscores from the drive ID so it didn't find a match and created it as if it was new.
  16. I updated all plugins and then upgraded from 6.9.2 to 6.10.0-rc8. The partition names identified by UD changed back to the default serial number and not the value I had set previously and the 6.9.2 version was listed in the "Historical Devices" section. Reverting back to 6.9.2 restored the partition name. Under 6.9.2: Samsung_SSD_960_EVO_500GB_S3X4NB0K309824V (Samsung_960EVO) Once I renamed the partition back to "Samsung_960EVO", it fixed the mounting location so my VM's could be located again. nas-diagnostics-20220511-2047 (rc8).zip nas-diagnostics-20220511-2052 (6.9.2).zip
  17. Make sure your antivirus, Acronis Home, etc are disabled and ensure you have the prompt to run as Admin show up.
  18. I kept getting data corruption and missing files and a parity sync kept reporting errors if I wait a few days after the last parity check. I managed to isolate it to one drive I swapped it out and did a parity rebuild but the issue persisted so I assumed a corrupted XFS. I was using this utility to help track corruptions and it was a clear benefit there. It seemed that removing all files fixed whatever corruption was happening, had no issues even after filling up the drive with large NULL files in the event I needed to 7zip the drive up to give someone to check but it never failed in the next month. Since I needed to reformat, I decided to switch to btrfs to use it's own built in scrub for bitrot, and I was thinking of taking advantage of btrfs features.
  19. One thing to note is that the memtest86 that comes with UNRAID is an old version* - if you want the most recent, you have to download it from https://www.memtest86.com/ and create your own boot flash. Note that this version restriction placed by memtest86. * At least this was the case the last time I used the tool, YMMV
  20. I've been pondering software KVM's off & on and looked into Barrier. It strikes me that if you create a VM running Windows or Unix, you can use that as your Barrier host.
  21. Sometime last week, I set my Validation scheduled to weekly on Sunday. Disk 1 kicked off and completed but none of the others did. I'm also wondering how does the Task function work. You can set up One drive per Task which seems the logical choice but you can also assign multiple drives to a single Task. What exactly *is* as "Task" in this case? It seems like a single thread that will do stuff. There's no built-in help around it.
  22. When ever I tried to schedule one to kick off daily in 15 minutes, it's only ever kicked off the check for Drive 3. It finished and nothing else started. *shrug*