Jump to content

dertbv

Members
  • Content Count

    184
  • Joined

  • Last visited

Community Reputation

0 Neutral

About dertbv

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. Any headway on this, i am showing the same thing
  2. 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.
  3. 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..
  4. 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..
  5. 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
  6. 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
  7. You are correct sir! Thanks for the info!
  8. Trying to figure out why the load statistics is not showing, any pointers?
  9. 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)
  10. 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..
  11. 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?
  12. I guess i would be willing to give it a run..
  13. dertbv

    unRAID Server Release 6.2.0-rc4 Available

    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?
  14. dertbv

    Dynamix - V6 Plugins

    Worked like a charm. Thanks for the quick response..
  15. dertbv

    Dynamix - V6 Plugins

    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