dertbv

Members
  • Posts

    210
  • Joined

  • Last visited

Everything posted by dertbv

  1. 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.
  2. 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..
  3. 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..
  4. 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
  5. 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
  6. Trying to figure out why the load statistics is not showing, any pointers?
  7. I am unable to get cpu scaling to work. Looking for any ideas? I do have perl installed. root@Tower2:~# grep -m 1 'model name' < /proc/cpuinfo model name : Intel(R) Xeon(R) CPU E5-2673 v3 @ 2.40GHz root@Tower2:~# cat /proc/cpuinfo |egrep -i mhz cpu MHz : 2399.998 cpu MHz : 2399.998 cpu MHz : 2399.998 cpu MHz : 2399.998 cpu MHz : 2399.998 cpu MHz : 2399.998 cpu MHz : 2399.998 cpu MHz : 2399.998 cpu MHz : 2399.998 cpu MHz : 2399.998 cpu MHz : 2399.998 cpu MHz : 2399.998 cpu MHz : 2399.998 cpu MHz : 2399.998 cpu MHz : 2399.998 cpu MHz : 2399.998 root@Tower2:~# sensors coretemp-isa-0002 Adapter: ISA adapter MB Temp: +100.0°C (high = +100.0°C, crit = +100.0°C) Core 0: +100.0°C (high = +100.0°C, crit = +100.0°C) Core 1: +100.0°C (high = +100.0°C, crit = +100.0°C) Core 2: +100.0°C (high = +100.0°C, crit = +100.0°C) Core 3: +100.0°C (high = +100.0°C, crit = +100.0°C) coretemp-isa-0000 Adapter: ISA adapter CPU Temp: +100.0°C (high = +100.0°C, crit = +100.0°C) Core 0: +100.0°C (high = +100.0°C, crit = +100.0°C) Core 1: +100.0°C (high = +100.0°C, crit = +100.0°C) Core 2: +100.0°C (high = +100.0°C, crit = +100.0°C) Core 3: +100.0°C (high = +100.0°C, crit = +100.0°C) coretemp-isa-0003 Adapter: ISA adapter Package id 3: +100.0°C (high = +100.0°C, crit = +100.0°C) Core 0: +100.0°C (high = +100.0°C, crit = +100.0°C) Core 1: +100.0°C (high = +100.0°C, crit = +100.0°C) Core 2: +100.0°C (high = +100.0°C, crit = +100.0°C) Core 3: +100.0°C (high = +100.0°C, crit = +100.0°C) coretemp-isa-0001 Adapter: ISA adapter Package id 1: +100.0°C (high = +100.0°C, crit = +100.0°C) Core 0: +100.0°C (high = +100.0°C, crit = +100.0°C) Core 1: +100.0°C (high = +100.0°C, crit = +100.0°C) Core 2: +100.0°C (high = +100.0°C, crit = +100.0°C) Core 3: +100.0°C (high = +100.0°C, crit = +100.0°C)
  8. Good morning: I have been using the RC versions since you started releasing them. Everything seems to be working correctly however I have discovered that I can no longer drill down on the disks on the main page to make changes to the individual disks. I can not also click on the folders on the main page to see what is on each disk. For example, when I highlight the disk icon I see the command browse mnt/disk/1 but it no longer browse's. I can right click on the icons and choose open in new tab and they will pop a new tab..
  9. So, just wanted to contribute back to this thread with info that might help (and offer a chance for someone to correct me!). A few years back I had virtualized unRAID via PLOP and could first-hand attest to the slooooowww boot time and issues with that; so much so that I had gone baremetal. With a new build, I decided I'd revisit virtualizing unRAID under ESX, and ran across plopkexec (actually mentioned elsewhere on this forum for a different purpose). I can say that this drastically cuts down on the boot time (for all perceived purposes, same as bare metal). With passed through M1015, I now have effectively the same config as my prior bare metal (and even moved it over seamlessly) without the hassles I recall of the AIO solutions prior. Granted, this is now a day in, so still waiting for the other shoe to drop... I am still running plop as I could not figure out how to get kexec to work. Can you share?
  10. I am getting the following error when i reboot unraid. /sbin/ldconfig: /usr/lib64/libffi.so.6 is not a symbolic link Not sure where to look to try and resolve it.. Any ideas?
  11. Worked like a charm. Thanks for the quick response..
  12. When trying to update rc4 I get plugin: updating: dynamix.scsi.devices.plg plugin: installed unRAID version is too low, require at least version 6.2.0.. thanks
  13. Not sure where to post this. I have been using Plex for a long time and really have not run into any issues. However I seem to notice a a correlation between the latest beta release and my on deck display. The files are showing as recently downloaded. they are showing the correct show name yet they are only displaying the episode number. Looking at the file it is being properly renamed by sonar/nzbget. all tv shows that have been downloaded since 7/27 show the same symptoms. just the show name and the episode number.. I have plex loaded on my cache drive and am currently using 6.2.0-rc3. As a side note I also run emby and it is not experience this issue.
  14. I just finished my new esxi box and went with a 10srh-cf from SM. It has a built in sas chip that supports 10 drives as well as another 10 sata drives. Took my two servers and condensed them into a neat little package. Currently running Unraid on the sas controller in pass through Win 10 Vista IP Cameras a few installs of linux 2012. Very happy with my current setup..
  15. Thanks for the plugin. I am doing a parity check but have installed it and will do a test reboot when the check is done. You guys rick!
  16. Bubba: you are are the man. I have followed the steps and it is work. Did a few test reboots and I am one happy camper.. added to my go file.. cp /boot/60-persistent-storage.rules /lib/udev/rules.d udevadm control --reload-rules udevadm trigger --attr-match=subsystem=scsi sleep 15
  17. I have moved over to running UnRaid on my ESXI box. Trying to consolidate my machines down to one box. I am using a Supermicro X10SRH-CF with the LSI 2308 SAS flashed to it mode. This is passed through to the Host. I added the line "append mpt3sas.msix_disable=1 initrd=/bzroot" to the syslinux configuration to have the drives show in unraid. Everything is working like a charm however in unraid on the main tab the identification is showing as a string rather than the actual serial number of the drives. For example 35000003965ba82ba0, yet if I click on the drive it shows the correct serial number under the identity tab. thoughts?
  18. Getting this when i try to update.. root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="Netdata" --net="host" -e TZ="America/New_York" -e HOST_OS="unRAID" -v "/proc":"/host/proc":ro -v "/sys":"/host/sys":ro --cap-add SYS_PTRACE titpetric/netdata Unable to find image 'titpetric/netdata:latest' locally latest: Pulling from titpetric/netdata 5c90d4a2d1a8: Pulling fs layer 8162e534c0fb: Pulling fs layer 63ea55ebe3fe: Pulling fs layer 8162e534c0fb: Download complete 8162e534c0fb: Download complete docker: Get https://dseasb33srnrn.cloudfront.net/registry-v2/docker/registry/v2/blobs/sha256/79/79a09fa49cd7e917630b5b76ff58210a38f8b6639c13d851ae5222a13992a3f2/data?Expires=1466559208&Signature=acFLwCFAzGhBSsJXsd6PK~jUIdUfC90JJzDjWXGT-YRJZQM6dpyMdKrdjFU9Ydo8Qs4y65D-esySfwtUavrQZW7hl43o53oHbG7FspoZ-mu88k4~7a5FBDDIdeuGTlDDUJwlmkHs50777MOanlvHBlTV5D5eMz-~8QT-8WvCYtY_&Key-Pair-Id=APKAJECH5M7VWIS5YZ6Q: read tcp 192.168.1.17:54464->54.230.205.140:443: read: connection reset by peer. See '/usr/bin/docker run --help'. Running 6.23
  19. According to netdata this should fix it: Map /var/run/docker.sock to /var/run/docker.sock This comes with some risks and it did not work for me. See here: https://github.com/titpetric/netdata#monitoring-docker-container-metrics Please let me know if this works for you. I only have a 6.1 version to test on, maybe it works on 6.2? @dertbv, did that work for you? I don't even see any dockers in the stats. Might need to upgrade to 6.2beta.... No i gave it a try and it till shows the container numbers..
  20. Is there anyway we could have the docker numbers actually show the docker name?
  21. Been looking at ASRock EPC612D4U-8R uATX Server Motherboard Socket LGA 2011 R3 Intel C612. http://www.newegg.com/Product/Product.aspx?Item=13-157-624&utm_medium=BehEmail&cm_mmc=EMCPB-052016-_-PB-_-Bluecore-_-Content&utm_campaign=Post_Browsed&obem=t-4ujzV1iD1sR3wIMwX58Xi3z9kFSTvuMBYha7ZXzq0%3D&utm_source=Bluecore Any one know if the RAID by LSI3008, will give any problems with unraid?