Community Developer
  • Content count

  • Joined

  • Last visited

  • Days Won


jbartlett last won the day on March 17 2017

jbartlett had the most liked content!

Community Reputation

37 Good


About jbartlett

  • Rank
    John Bartlett
  • Birthday 07/20/1970


  • Gender
  • URL
  • Location
    Seattle, WA
  • Personal Text
    Foster parent for cats & kittens
  1. Drive spinup command for scripts

    How does one go about spinning up hard drives via a telnet session/script in a way that UNRAID recognizes that the drive has been spun up?
  2. I'm working on DiskSpeed plugin with prepopulating all available drives on the market and I could use some help with some brands, namely HGST & Toshiba to understand how the drives report their model string so I can format it to remove brand and revisions. For example, one Western Digital 6TB Red Pro drive returns "WDC WD6002FFWX-68TZ4N0" as the model. I strip off the "WDC " prefix and the revision after the hyphen to leave "WD6002FFWX" - but I don't know how to handle HGST & Toshiba drives. Older & newer drives requested because sometimes they change their model string format. It would be a tremendous help if anyone with a HGST/Toshiba drive copy-n-paste the follow command line into a telnet session and run it & copy-n-paste the result in a reply. It'll return the model string for all drives in your system. lsblk -ido KNAME | grep sd > /tmp/d.txt && while read line ; do hdparm -I /dev/$line 2>/dev/null | grep Model ; done < /tmp/d.txt && rm /tmp/d.txt (all one line) Running it on my backup/development box, I get the following as an example: Model Number: WDC WD6002FFWX-68TZ4N0 Model Number: ST4000DM000-1F2168 Model Number: ST8000AS0002-1NA17Z Model Number: ST4000DM000-1F2168 Model Number: ST8000AS0002-1NA17Z Model Number: ST4000DM000-1F2168 Model Number: Hitachi HDS5C4040ALE630 Model Number: WDC WD2002FAEX-007BA0 Model Number: WDC WD30EZRX-00D8PB0 Model Number: ST4000DM000-1F2168 Model Number: ST3000DM001-9YN166 Thanks!
  3. Three PCs In One - Second Sever

    Motherboard is the tricky part and it does matter - it has to support hardware pass-thru or “VT-d” (Intel)/“AMD Virtualization” (AMD). Server boards should be fine but it's kind of a mixed bag with consumer boards. You'll have a better chance with success on gaming/extreme type boards. And just because the BIOS says it supports it doesn't mean it'll work. Not all video cards will pass through even on a MB that is known to work. Do not run a VM on a spinner, it is horribly slow. Some games will detect running under a VM and may ban/block you.
  4. Three PCs In One - Second Sever

    It's possible using UNRAID as the host OS and running Windows in a VM with a video card passed directly to the VM. There's a whole layer of extra headaches involved in this setup. I would recommend dedicating a SSD drive to the VM if you go this route instead of using a container. If you do use drive containers for ease of backing up, I find that creating multiple drives for different purposes helps keep bloat down. For example, for my Win10 VM, I have a drive dedicated to the OS, one for apps, and one for Temp files & Downloads.
  5. Firefox Quantum = WOW

    I wasn't able to watch my Blurays in a Plex browser at max quality under the old Firefox and I have a really beefy system. No problem under Quantum.
  6. Status Report on version 3 Life got in the way for the past couple months and development slowed quite a bit ("Assassin's Creed: Origins" didn't help either) but I've put in some solid development time over the past week and have made great progress. I hope to have an alpha version ready inside a week. I've been quite satisfied at the progress I've made and getting excited. Installation will be via the Plugin interface and the GUI will be fully in the browser with no telnet sessions. While I say "alpha", it'll be a fairly tested product having been tested on two UNRAID environments plus a VirtualBox environment and against both intel & amd motherboards and different controller cards - but it hasn't been tested against other user's hardware.
  7. I took the stripes as being drives with the green one the Parity. But the person out there who doesn't know the system wouldn't think that.
  8. [Plugin] Disk Speed Test

    Try setting fast mode to yes to see if it works. Your graph will be a little bit more jaggy but it'll be pretty much a good reflection.
  9. That's some friggin' impressive speeds on those 10TB drives! Here's a screen shot of the current Drive Configuration screen. You will have the option uploading a new drive image (to do) and optionally overlaying the drive capacity over the image. The color, location, size, and rotation are each individually configurable and the text will dynamically update as the sliders move.
  10. Thank you for the heads up. I'm developing under 6.4 RC so I already noticed that so I opted to parse out the file disks.ini to get the drive assignments & additional information. I didn't know about mdstat but I'll make a note of that if I need it in the future.
  11. unRAID OS version 6.4.0-rc9f available

    Have you tried it without the monitor too? I have an AMD box that won't boot without a monitor plugged in.
  12. I'm working from the ground up, starting with the drive & controller identification, and testing the controller. The next test I plan to add is the one that does the same test as the original DiskSpeed test does. However, the next part I'll be working on is adding customization for the drive image/info. On initial first-time run, the app will fetch the model information from my server for each brand and will pre-set the drive image based on the first image found. If no information was found on the drive model, a generic drive image will be used instead. The goal is to let you upload a new image, specify if you want to overlay the drive capacity over the image, and if so, the size, position, and rotation of the text. You'll have the option to upload your drive image and overlay settings (if any) to my central repository. Another way to select drive images is to get a view of every available drive image and select the one you want to use. Examples are when a brand such as Western Digital uses one basic image for an entire model line (think WD Black) but then later comes out with a new style for it. You'll be able to select between them. Once that part is done, I'll put out a call for people to email me if they want to be on the pre-alpha test team. This team's purpose is to see if my controller & drive identification logic works on different systems, motherboards, controllers, etc. So far, I had to rewrite the logic which detected how many drive ports are on the controller and which specific drive was attached to it after I installed a LSI SAS card. Totally different layout on the OS than motherboard and SATA card controllers I've tested. It's possible there could be some other controller that I haven't experienced or coded for.
  13. It'll currently test the controller with all drives attached, adding an additional drive each iteration until all are used. Exception being that there's no benchmark if only one drive is attached. This test kicks off x number of drives with a full unrestricted read of the hard drives using the optimal block size previously determined. After 5 seconds, it kills the PIDs that were launched and records the last logged transfer rate. I also figure that this is a good test to see how the controller is with handling multiple drives at the same time. This tool doesn't care if the drives are in the UNRAID array or not other than for display purposes. Testing a full system drive push with all drives on all controllers active. Interesting. I can also identify if multiple controllers are nested under a given internal PCI/bus so that may be a future test - or make it so you can specify which controller cards to simultaneously test. Note: Each drive's optimal transfer speed is a combination of the drive itself along with the controller & bus. If a hard drive switches controllers or the controller itself is moved to a different slot, the app will require the optimal block rate to be retested. However, if the drive is put back to where it once was, it will reuse the previously detected optimal block size. Here's a graph with the app running under VirtualBOX with each virtual drive running on a Samsung 960 EVO M.2 500GB NVMe. This is a good example of maximizing the controller that is not running optimally.
  14. Development on the new version is plugging along, slowly but surely. I'm currently working on bench marking controller cards. Here's the controller bandwidth test results for one motherboard controller on my main server with 6 Red Pro drives attached - and capacity wasn't maxed. I think I'll need to hook up a bunch of SSD's to my LSI 8 port card. In theory, once capacity has been maxed on the controller, the amount of data being read by each drive would shrink while the total data being read from all drives combined remained the same.

Copyright © 2005-2017 Lime Technology, Inc. unRAID® is a registered trademark of Lime Technology, Inc.