opentoe

This series WD4003FZEX is probably not in the database. Maybe it can be requested/added. Correct. I just looked and that model is not in the database. I guess not a very popular model. I'll see if I can make the request.

So how does a WD drive have a missing "Manufacturer" field? Strange, right?

This docker is wonderful, but it does need constant updates from the author to get things working again. I used this great docker myself for a while but didn't have time to keep checking to see if it was working all the time. Kind of just want to set things up, start it and leave it. I was lucky enough to have ample resources so I threw up an ubuntu VM, installed Crashplan server, setup which folders to back up and that's it. Has been running good. It is just an alternative.

smartctl --all /dev/sdc smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.1.7-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: WDC WD4003FZEX-00Z4SA0 Serial Number: WD-WCC130966733 LU WWN Device Id: 5 0014ee 25e2bd767 Firmware Version: 01.01A01 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ACS-2 (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Sun Sep 27 15:23:10 2015 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (41640) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 451) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x7035) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 138 136 021 Pre-fail Always - 12075 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 52 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 080 080 000 Old_age Always - 14905 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 51 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 18 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 33 194 Temperature_Celsius 0x0022 121 109 000 Old_age Always - 31 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 12833 - # 2 Short offline Completed without error 00% 12332 - # 3 Short offline Completed without error 00% 11348 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.

I still have a 4TB drive that is part of my array not populate the manufacture field. Is this something with the plugin that is prohibiting that field to populate? I can try to uninstall the plugin and then reinstall?

Yes you have to manually assign the disks to trays. As for the numbering it is just as a reference from the table to the preview layout on the data tab and should not be correlated to any physical HW. Thanks. I did install the new update. Some of my drives are missing the "manufacturer" name. There are a few HGST's my two Samsung SSD's and one Western Digital. I could of sworn I saw those fields filled out when I last checked. Do they auto-populate somehow from the drive report(s)? Since port1/tray1 on the Norco 4224 is physically at the upper right of the chassis is there a way to move the drive layout boxes to reflect? I did hit the button "updatesmartmontools" and that did populate the drive manufacture's except for one Western Digital drive.

Thanks for these instructions, worked perfectly. Fastest controllers I tried, can get 300MB/s+ parity check on my test server with 8 SSDs. Glad to hear. I have 4 Dell H310 cards. 2 flashed with Dell IT's firmware and 2 flashed with LSI's firmware. I tried using all 4 cards in different arrangements and all 4 performed identical. I'll put my SAS2LP cards aside, maybe one day there will be a fix for their slow parity check speeds.

I was able to grab two more DELL H310's from work. I flashed them successfully with the 2188IT firmware, but I intentionally left out re-assigning the SAS address. I did this with two cards. Removed my flashed Dell IT cards and installed the two I just flashed and unraid booted right up. Apparently you do not need to assign the SAS address back to the card. I imagine that may have been used during old school days when you needed the address of hardware, but these days the mainboard and OS pretty much take care of all that now. Note, I did not apply the BIOS part. No need, since the card is just passthru. I also came to a conclusion that using the right sas2flsh utility version makes a difference. I used the brand new version and kept getting that manufacturer version error and the flash would bomb out. But if I used an older version of that same utility it actually asked me if I wanted to flash even though the hardware manufacture ID was different. This is a good tip, since you can say YES and the flash will continue to work. I'm using the cards now. See the capture.

Trying out this plugin. Looks cool. Is the drive data supposed to auto populate or do you need to assign the drives manually in the data tab? Also with the Norco 4224 case, TRAY1/PORT1 is upper right and then goes towards the left. TRAY5 is second row all the way to the right, able to make those changes visible right?

That's very different then what most users report with the M1015 cards. It usually is the other way around where as the SAS2LP cards have the slower speeds. Did you buy your M1015's and flash them yourself? You could also put back the SAS2LP cards and try the tunables script again. I believe it is a VERY good idea for this script to BACKUP your disk.cfg file before anything starts considering it does make changes to it.

Did you have this problem from the beginning or did it appear lately? Did you do any updates of unRAID? Try to flash the P7 firmware. Use the sas2flsh.exe that comes with the P7 package. (download from LSI or use the one within the H310 package) Within the H310 package it is described how you dump a copy of the SBR of your OK card. But I fear there is something else going on with that thing. Guess nobody tried the DELL IT firmware with unRAID. Before the H310 was flashed the procedure for the M1015 was already established and the LSI firmware is known to work with unRAID. LSI firmware is probably more up to date - don't know if its an advantage though. The Dell IT firmware's release date of July 2014. The LSI one I believe is September 2014. Can't be much of a difference. I stuck with the Dell firmware since it is actually approved by Dell for that card and IT mode. Grabbed it right from Dell's website. The daily read/write speeds compared to my Supermicro SAS2 cards are the same. Just the parity checks are much faster. Update: Hopefully this link will stay put. This is Dell's NON-RAID (IT) firmware for the H310 card. http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=YJ78T&fileId=2731103519&dgc=CJ&cid=47997&lid=4279734&acd=12309198375458460&ven1=11708984-5838698-skim34691X927548X206090f813c979889b17a6fca312016c&ven3=775302971985010933 I did put all the files on my FTP server in case you need to download them. ftp.diggsnet.com user = [email protected] pw = unraid

The method to flash a H310 was posted in this thread by Fireball3. And the commands to use are coded in the ".bat" files in the archive earlier in this thread. I've done 4 H310's so far myself it works great. I use Fireball3's method and flash from USB dos boot. Here is his post http://lime-technology.com/forum/index.php?topic=12767.msg259006#msg259006 Why is everyone doing the extra steps on the H310 cards? These are the only commands I used and both cards I flashed are working just fine in my unraid server now. megarec -writesbr 0 sbrempty.bin (wipes the card so to recognize as an LSI) MegaRec -cleanflash 0 reboot sas2flsh -o -f 6GBSAS.FW After that you are done. You don't need the BIOS boot, unless you have to boot into the card for some reason. Also, I never had to reprogram the cards address. I guess you don't need to do that since I used the Dell 6GBSAS firmware. Seems from looking at the batch files if you use the LSI firmware you need to re-program the SAS address. Why not with the Dell IT firmware, have no idea. I used the utility RUFUS to make a bootable USB stick and flashed each card by itself in the PCIE slot. EDIT/UPDATE: I did want to mention that I have read the Dell firmware only supports a queue depth of 25. The LSI firmware supports a queue depth of 600. I have tried both variations of the firmware and saw no increase/decrease in performance. Does this apply to IT passthru which unraid uses? I don't know. I guess to be safe, use the LSI firmware.

I'm seeing the same results as you. I'm not sure where IP address 192.168.122.1 is coming from, since my subnet is 192.168.1.x. Maybe it is normal behavior. root@SUN:~# nmblookup -M -- - 192.168.122.1 __MSBROWSE__<01> root@SUN:~# ping 192.168.122.1 PING 192.168.122.1 (192.168.122.1) 56(84) bytes of data. 64 bytes from 192.168.122.1: icmp_seq=1 ttl=64 time=0.048 ms 64 bytes from 192.168.122.1: icmp_seq=2 ttl=64 time=0.055 ms 64 bytes from 192.168.122.1: icmp_seq=3 ttl=64 time=0.048 ms 64 bytes from 192.168.122.1: icmp_seq=4 ttl=64 time=0.059 ms ^C --- 192.168.122.1 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 2999ms rtt min/avg/max/mdev = 0.048/0.052/0.059/0.008 ms

Will be selling my iStarUSA 5x3 cages. They work fine and just need a good cleaning. They do have 80mm fans, but I never replaced them. Have to remove the back with screws. NOTE: Most of the screw holes are stripped, so if you were to mount them in a case you would need to be handy and figure out how to do it. I just put them on top of one another since they are strong enough. Haven't put the post in the for sale area yet. Will be cheap, probably cost more to ship them.

In what way the auto update would help? Code42 has done some undocumented modifications on how headless server works. In this case, wasn't just about updating CP, but release a 4.3 version of both CP and CP-Desktop. Other example is NZBget; the author made some serious changes on how the program is installed. It took some time to figure out and modify the code accordingly. With the exception of a few guys that have goodwill and submit some changes to the GitHub repo or send debug data, most of users just take things, never giving anything in return. Sacretagent sent me some PM, a guy named Datapotomus submitted a PR (it wasn't just about version update, so I didn't merged it, but thanks!).... Thanks a lot guys, this kind of thing helps a lot! For you, opentoe, good riddance with your VM solution; I'm sure it works just fine. Thanks a lot for your input. No need to get offended. I'm going to use what works best for me and this (IN MY OPINION) is a good alternative. If you want any more input just me know. Happy to share.

Throw up a small VM! I made one on Sunday and it has been working like charm. No need for manual updates or anything. I just see the same thing over and over in this thread. Pretty soon unRaid will make their own backup cloud service connected to their OS. Would be nice, right?

This is good to know. I'll eventually switch back over to a docker based solution once it is more automated with updates. That's all I'm looking for, automation so I don't have to. Already have a full time job with less and less time as it is. Luckily I have a system that I can whip up a few VM's and not have to worry about resources. I never intended to have have so many resources or such a robust system, just kind of fell that way when I replaced my office home computer which then became my "new" unRaid build. I'll eventually put it all to use.

I decided to ditch this great docker (and the second MATE) and just install a small VM with ubuntu and install Crashplan. I mounted all my user shares within the VM and now don't have to edit my Windows client files everytime there is an update or a need for the docker to get updated. This will happen by itself on the VM now. No more waiting for the manual updates from the programmer. I just read in another thread he's working on other projects and is a busy guy. I would think this is on the bottom of his list. The VM is working great so far and is currently backing up as I write this.

ROFL! My mid-tower case I had with three HD cages wasn't really any lighter. Just a smaller package. At least this case lays nicely on the little stand I had. Put a couple fake plants around it and you wouldn't even know it is there. I don't plan on moving it! I have an entire room dedicated to my bitcoin miners and didn't want to stick it in there because of the heat. Would of been the most practical place for it, but just too hot. Surprisingly very quiet.

Threw in some other pictures. Noctua makes some very quiet 80mm fans, which I may replace the ones in the back but to be honest they aren't very loud. I do like the fact that each of them is 3000rpm and having two of them is pretty much pulling all the air out of the case. If I put a piece of paper on the front of the case it will stick there. Great air flow ans pressure in there. If you have a lot of drives and will continue to have lots of drives coming from a mid tower case I do recommend this beast. I had the room and available area, so I was good there. Thanks for moving into the hardware area. unRaid 4224 Server Build

Well, finally switched over to the Norco 4244 server case. Pretty slick and this will last me a long time, and I'm done with cases. The only thing about the Norco case is those two 80mm fans in the back. Those two little fans are louder then all the other fans put together, so I'll have to figure something out. I'm very surprised how quiet it is and how cool it runs. I snapped a quick picture, will have more.

i think the best plan of attack is to have a single Crashplan docker container that is slimmed down version of a lightweight linux. Standalone, single instance. That way everything can be updated as it should be by Code42. As long as Crashplan on linux is supported, this docker will work. I know very little about Docker, but I'm going to try and get this working on my own. If I do, I'll share what I find. This is fairly easy to modify to get started... https://github.com/gfjardim/docker-containers/blob/master/crashplan-desktop/install.sh Probably could figure this out but when the editing is all over I wouldn't know what to do with the file. This would be a manual install right from the command line? I know dockers would the preferred way, but would creating a VM for Crashplan be an option? I certainly have the resources and power and won't have to worry about two separate dockers.

Let's indicate this docker will need constant updates by the creator for it work properly. I "think" my engine is running but I'm unable to connect to it and I don't have time to learn how to create my own dockers.

I've seen a fair number of invalid values from various sensors, 2 of yours appear to be invalid which is fairly common. Some sensor chipsets even produce warnings in the syslog that readings may be unreliable. The idea is to examine the readings and pick sensors that are working correctly, producing valid values. The motherboard bios has all this data I can review. It has a whole complete monitoring area that shows the temps of all the sensors on the board and all fan speeds. I'll go off of that to start with a baseline.

Finally getting some headway with the temp plugin. Wow, lots to do just to get a couple temp readouts. I have it communicating, so I'll work a little bit on it later. Does the sensors.conf file need to be copied into the /boot/config folder? Also, is there a screen to show you all the temps on one page, instead of just the three in the tiny corner of the Webgui? I have to configure the file so I'm grabbing the correct temps for what they really are I guess. I also see something called CPUTIN and the temp is scarey high. Is that a normal reading?