Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About dertbv

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

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

  1. Going on 12 years of being a user of unraid. I can honestly say that it has been a fun learning experience. Watching it grow from the early days to what it is today, just wow. The bad side is I think people get tired of my love for the os. Can never stop bragging about what it does.
  2. Currently running on ESXI and wanting to move over to bare metal. Running 5 Vm's that would need to be converted over. Have about a dozen dockers including Plex with about 6 streams concurrently. Can one of the unraid masters give me feedback on this list? Intel Core i9-9900K 3.6 GHz 8-Core Processor Noctua NH-U12S 55 CFM CPU Cooler Asus TUF Z390M-PRO GAMING (WI-FI) Micro ATX LGA1151 Motherboard Crucial Ballistix Sport LT 64 GB (4 x 16 GB) DDR4-3200 Memory 1 Samsung 860 Evo 1 TB 2.5" Solid State Drive 5 Toshiba N300 10 TB 3.5" 7200RPM Internal Hard Drive MSI GeForce GTX 1660 Ti 6 GB GAMING Video Card Fractal Design Node 804 MicroATX Mid Tower Case SeaSonic FOCUS Plus Platinum 550 W 80+ Platinum Certified Fully thanks
  3. Has anyone been able to get this ti work running unsaid as a VM in esxi? I have a 1600ti card that i installed put in pass through mode added it to unraid. I boot fine but I am getting "Unable to determine the device handle for GPU 0000:0B:00.0: Unknown Error" . researching this out says to edit the VM and add hypervisor.cpuid.v0 = "FALSE", and then unraid boots extremely slow and then fails fails to fully boot. Anyone have any pointers?
  4. I have started to show errors on one of my disks. Hoping the powers to be can point me into the right direction. TOSHIBA_HDWE150_Z5N9K7N6F57D-20190117-0701.txt
  5. It is using the same controller the samsung drive was using when it was working.. I assume that these two directories are on the cache drive? sudo fstrim -a -v /var/lib/docker: 11.9 GiB (12789510144 bytes) trimmed /etc/libvirt: 921.6 MiB (966324224 bytes) trimmed
  6. Finally swapped out my cache drive with a Samsung 1tb 860. Trim was working however i started to have issues with the drive. It would grind to a halt once it got to 180 GB on it. I decided to exchange it for a Crucial MX500 1TB. it seems to be doing much better however when i run the trim command i get fstrim: /mnt/cache: the discard operation is not supported. Any ideals what's going on?
  7. What command are you all using to prune the Plex application down in "Excluded Folders" Settings
  8. Any headway on this, i am showing the same thing
  9. Ok I have found the reason, it is a plugin named dynamix.disk.io. It is causing all my unmounted drives to read 0 bytes available when i try to add them to the array. Removed that plugin and I am now in the process of rebuilding the original USB drive and raid.
  10. Just to followup on this. i loaded a new config to another usb drive and booted. Had issues with the SSL folder not allowing me to get to the web page. However after copying the SSL folder over to the new drive, i was able to get into the web site and verify that all drives are appearing correctly. Plan now is to get as much of the data off the parity that i can and then use the new USB drive going forward. Still have not figured out why the old usb/config is not allowing me to add new drives..
  11. Here is the part that is bothering me.. I am using the same disk for most of my drives Currently in array "TOSHIBA_HDWE150_*** - 5 TB (sde)" New Disks after preclear "TOSHIBA_HDWE150_*** - 0 B (sdf)" This preclear was with the latest plugin version. Running again with Preclear.bjp.sh "Version 1.17 - Remove rogue comments in script." to see if it makes a difference. with command ./preclear_bjp.sh -W -A -f /dev/sdc I am also using Dynamix SCSI Devices to rename my drive. Both of the new drives are showing the same 0 B all the other ones in the array are showing 4 TB or 5 TB. Looking at the Super.dat file I see where the first letter of the Toshiba Drive that dropped is clipped. Reading OSHIBA_HDWE****. (using atom only mac) Comparing it to an older version of the super.data it is not Clipped on the letter "T". Rolled back the super.dat file but still no different..
  12. I have removed preclear plugin and rebooted. still not able to add the drives. the both are showing "0 B" on the list. Any ideals on what my next steps are? tower2-diagnostics-20180723-0223.zip
  13. I rebooted and one of my hard drives was no longer showing up. When i try to pick it from the drop when re-assigning disks it keeps showing as not installed. I bought another hard drive and precleared them both, yet i am still not able to re-add the drive. It is not showing as missing just not installed. This is a 5 TB drive that i have about 3.5TB data that I really dont want to loose. Any ideas? tower2-diagnostics-20180719-1903.zip
  14. Trying to figure out why the load statistics is not showing, any pointers?