All Activity

This stream auto-updates   

  1. Past hour
  2. I'll look into this a bit more but as I am refreshing my Unraid installation I found this docker setup. https://github.com/slydetector/simply-nzedb Seems pretty new and maybe a good source to make a docker instead of setting up an ubuntu VM?
  3. Download http://www.hdsentinel.com/hdslin/hdsentinel-016-x64.tar.gz, and extract the file and store it on your flash drive. Then from the command prompt, /boot/HDSentinel to run and analyze. BUT, if you ask me, the program is a POS, and smartctl (which unRaid's UI leverages and notifies you about problems with the drives is better.) Consider this drive. Output from smartctl: root@Server_A:/tmp/GitHub# smartctl -A /dev/sdm smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.9.19-unRAID] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 099 099 006 Pre-fail Always - 2553328 3 Spin_Up_Time 0x0003 094 093 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 091 091 020 Old_age Always - 10097 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 053 048 030 Pre-fail Always - 953529061048 9 Power_On_Hours 0x0032 068 068 000 Old_age Always - 28724 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 295 183 Runtime_Bad_Block 0x0032 092 092 000 Old_age Always - 8 184 End-to-End_Error 0x0032 088 088 099 Old_age Always FAILING_NOW 12 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 0 0 189 High_Fly_Writes 0x003a 099 099 000 Old_age Always - 1 190 Airflow_Temperature_Cel 0x0022 077 063 045 Old_age Always - 23 (Min/Max 17/30) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 87 193 Load_Cycle_Count 0x0032 043 043 000 Old_age Always - 115443 194 Temperature_Celsius 0x0022 023 040 000 Old_age Always - 23 (0 16 0 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 198 000 Old_age Always - 51 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 4161h+19m+20.345s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 45739743333 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 765808399191 And the output from HDSentinel HDSentinel makes a big argument on their website about how the manufacturers set the thresholds such that they cannot be hit, and how their method of analysis is far better, and yet according to smartctl which is reading the threshholds set by Seagate, and reporting the values, and the drive itself says that it is in a failing state, and yet HDSentinel states Yeah, there's no problem, don't worry about it.... By the way, the end to end error that HDSentinel is saying "12 errors occured during transfer" is one way of putting it, albeit the wrong way. The proper way of putting it is that there was a communication error between the drive head and the sata interface on the drive (ie: an actual physical failure), which is why Seagate sets a single failure as "FAILING NOW"... Outside of this rather large error on their analysis, it is interesting in that it attempts to put into english what is shown on the drive's SMART reports. BTW, you can RMA a drive before any attribute is in failing status.
  4. SMART looks fine. Your understanding of what happened and how to proceed is good.
  5. I've not used this but looking at its web page, I think some of the functionality is builtin to unRAID already. unRAID monitors disk temperatures, SMART, does short and long SMART test. Performance testing here Nothing that really gives you a history of these things, though. If you really want to use HD Sentinel, I think you should be able to unzip it to your flash drive and then follow the instructions given at the website for using it. I have not tried it.
  6. 64gb ecc ddr2 . Seems to be a huge overkill when using VM's close to none...
  7. Yesterday
  8. Try another port for your flash, preferably USB2.
  9. I am brand new to Unraid and Linux. I wish to install a copy of HD Sentinel. What is the easiest method?
  10. Binhex is the one who can do a code update, not you. Did you try the docker with "tun"?
  11. I don't understand your question. Edit: Oh, you're referring to my warning that it might go away. Yeah. I would only get rid of this one if Sparklyballs was as good or better. :-)
  12. I have removed it. I deleted the entry from my Syslinux and restarted. default /syslinux/menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append pcie_acs_override=downstream vfio-pci.ids=8086:1521 initrd=/bzroot label unRAID OS GUI Mode kernel /bzimage append pcie_acs_override=downstream initrd=/bzroot,/bzroot-gui label unRAID OS Safe Mode (no plugins, no GUI) kernel /bzimage append pcie_acs_override=downstream initrd=/bzroot unraidsafemode label unRAID OS GUI Safe Mode (no plugins) kernel /bzimage append pcie_acs_override=downstream initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest The vfio-pcs.ids entry is my four port ethernet card. Maybe unRAID isn't compatable with the PVU3-202I PCI express cards. The other options I have for PCI USB controllers are Shintaro, Skymaster, Sunix, Welland, or Vantec. Dont really want to buy another card and hope it works though.
  13. 3389 is for the RDP UI. 8080 is for the web UI. The RDP one is zippier but requires an RDP client. See the documentation linked in the first post for some clients you can use.
  14. You would need to copy the data twice. Once from your operating FreeNAS box to your operating unraid box with the 3TB as a data drive, then again from the 3TB to the other unraid data drives after you scavenge them from the FreeNAS box. There is no need to clear or preclear the drives to use them in unraid, as you will not have a valid parity drive at any point of the copy process. Clearing is only necessary to maintain parity protection when adding new drives to additional data slots in a parity protected array. Healthy drives are a necessity in a parity protected array though, as all bits from start to finish of all drives must be read perfectly, regardless of whether they actually contain any sensible data. Do not add any drives to unraid that you do not know to be in perfect health. If that is what you were referring to when mentioning preclear, go right ahead, preclear is a very good way of testing a drive.
  15. That fixed it. Thank you!
  16. This was well written. Thanks for the reply. For anyone with the same issues/questions, the above, plus this thread, are both helpful.
  17. I see this in the logs : Apr 25 01:50:00 untheran kernel: usb 2-3: USB disconnect, device number 2 Apr 25 01:50:00 untheran kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Apr 25 01:50:00 untheran kernel: sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Apr 25 01:50:00 untheran kernel: usb 2-3: new SuperSpeed USB device number 3 using xhci_hcd Apr 25 01:50:00 untheran kernel: usb-storage 2-3:1.0: USB Mass Storage device detected Apr 25 01:50:00 untheran kernel: scsi host9: usb-storage 2-3:1.0 Apr 25 01:50:01 untheran kernel: FAT-fs (sda1): Directory bread(block 32768) failed Apr 25 01:50:01 untheran kernel: FAT-fs (sda1): Directory bread(block 32769) failed Apr 25 01:50:01 untheran kernel: FAT-fs (sda1): Directory bread(block 32770) failed Apr 25 01:50:01 untheran kernel: FAT-fs (sda1): Directory bread(block 32771) failed Apr 25 01:50:01 untheran kernel: FAT-fs (sda1): Directory bread(block 32772) failed Apr 25 01:50:01 untheran kernel: FAT-fs (sda1): Directory bread(block 32773) failed Apr 25 01:50:01 untheran kernel: FAT-fs (sda1): Directory bread(block 32774) failed Apr 25 01:50:01 untheran kernel: FAT-fs (sda1): Directory bread(block 32775) failed Apr 25 01:50:01 untheran kernel: FAT-fs (sda1): Directory bread(block 32776) failed Apr 25 01:50:01 untheran kernel: FAT-fs (sda1): Directory bread(block 32777) failed Apr 25 01:50:01 untheran root: Apr 25 01:50:01 untheran root: Warning: file_put_contents(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerconfig.php on line 35 Apr 25 01:50:01 untheran root: Apr 25 01:50:01 untheran root: Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php on line 39 Apr 25 01:50:02 untheran kernel: scsi 9:0:0:0: Direct-Access Lexar USB Flash Drive 1100 PQ: 0 ANSI: 6 Apr 25 01:50:02 untheran kernel: sd 9:0:0:0: Attached scsi generic sg0 type 0 Apr 25 01:50:02 untheran kernel: sd 9:0:0:0: [sde] 62517248 512-byte logical blocks: (32.0 GB/29.8 GiB) Apr 25 01:50:02 untheran kernel: sd 9:0:0:0: [sde] Write Protect is off Apr 25 01:50:02 untheran kernel: sd 9:0:0:0: [sde] Mode Sense: 43 00 00 00 Apr 25 01:50:02 untheran kernel: sd 9:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Apr 25 01:50:02 untheran kernel: sde: sde1 Apr 25 01:50:02 untheran kernel: sd 9:0:0:0: [sde] Attached SCSI removable disk
  18. None of the data is absolutely critical, that's all backed up to Amazon Drive or Dropbox or Google Drive. I don't mind the window of failure I might have - it would just be an inconvenience if something were to happen to the drive.
  19. There it is ! untheran-diagnostics-20170425-1849.zip
  20. Possible, but rather risky. It would be a much better idea to source enough drive space to leave the original drives intact as a backup.
  21. Hello all, I just recently ran into an issue in my UnRAID setup in which one of my disks randomly became disabled. I believe it was during the process of me cleaning my server and possibly knocking the SATA cable loose. After shutting down and checking/fixing the SATA cable, the disk was available to add to the array, but still remains disabled. I have completed a SMART report on the drive and have uploaded it here. While the UnRAID GUI reports that it completed without error, I just feel more comfortable posting it here for someone to take a look at. I believe that this is simply just an issue due to a loose SATA cable, but I just wanted to be safe and have the SMART report reviewed in case there is any potential that the drive is failing. If the drive is okay, I believe I will still have to rebuild the drive due to a potential write failure to the drive, hence why the drive became disabled. If so, what are the available options to do such a process? I read in a previous post that it's as simple as: Stop the array Set the disk to be not installed Start the array Stop the array Set the disk to be the appropriate disk Start the array I appreciate any assistance I can get, and I would much rather be safe than sorry. Thank you in advance! WDC_WD20EARS-00MVWB0_WD-WMAZA0659735-20170425-1838.txt
  22. how do i update code? is it this COMMAND? /plugins/dynamix.docker.manager/scripts/docker create --name="activ-transmissionvpn" --net="bridge" --privileged="true" -e TZ="Europe/Budapest" -e HOST_OS="unRAID" -e "VPN_ENABLED"="yes" -e "VPN_USER"="XXX" -e "VPN_PASS"="XXX" -e "VPN_REMOTE"="pw.openvpn.ipredator.se" -e "VPN_PORT"="1194" -e "VPN_PROTOCOL"="udp" -e "VPN_PROV"="custom" -e "ENABLE_PRIVOXY"="no" -e "LAN_NETWORK"="192.168.1.0/24" -e "WHITELIST"="192.168.*.*" -e "DEBUG"="true" -e "PUID"="99" -e "PGID"="100" -e "VPN_DEVICE_TYPE"="tun" -e "STRONG_CERTS"="cipher AES-256-CBC" -p 9091:9091/tcp -p 8118:8118/tcp -v "/mnt/disk2/Downloads/":"/data":rw -v "/mnt/user/appdata/activ-transmissionvpn/config":"/config":rw activ/arch-transmissionvpn As if i go to /plugins there is no dynamix.docker.manager So no clue where or what to update... Ive tried to run separate OpenVPN client on unRaid with "tun" (instead of tun5) setting, but soon as it connect it changes it to "tun5" and update the *.ovpn file thx
  23. Thanks for the info, I will give one of those kits a shot.
  24. Thanks Johnnie. I will definitely make sure when I go to buy them.
  25. If it's just for desktop and server and if the cable limits is not a problem might as well use a direct connection, it's always cheaper, both will need to still use gigabit for internet and to access other computers, it's what I do, my cache read/write speeds are about 900MB/s sustained, obviously your cache device(s) and desktop storage need to keep up to achieve those.
  26. Beware that the He10 is available as both 512e and 4kn, make sure you get the 512e variants since 4kn is currently not supported by unRAID.
  27. So with that it would pretty much be a direct computer to unraid connection? I found a HP 8 rj45 port 2 port SPF 10GBe switch on ebay for $45. Only the 2 SPF ports operate at 10GBe RJ45 are 10/100/1000 on switch from spec sheet. If I buy a second 10GBe card to put in my personal computer and get the cables and use this switch would it allow for fast speeds? Or should I just do a direct connection?
  1. Load more activity
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.