Matt Foley

Members
  • Posts

    53
  • Joined

  • Last visited

Everything posted by Matt Foley

  1. I replaced the supplied fans with 120mm PWM fans. I run a script to drive the fan speed based on hard drive temps I modified from a thread on this forum. I have them set to go to a medium speed when a drive temp exceeds 33 degrees, and then full speed when a drive temp exceeds 39 degrees. I rarely hear the fan speeds go to medium and have never heard them go to full.
  2. Yes as long as the cables you use also support 1Gbps. Old LAN cables only used two pairs of the wires. New use all 4 pairs and are more tightly twisted to avoid cross-coupling between the pairs. Cat5e and Cat6 are rated for 1Gbps. Cat5 is not but might work for shorter lengths. The house I am in now has Cat5 strung to all the rooms. Was able to get Gigabit speeds in all of the rooms with the longest run being around 50 feet. Ran like this for a couple of weeks before running Cat6 to replace the Cat5 in rooms that were using Gigabit (I tend to be a better safe then sorry type of person.) Network benchmarks show the same speed on the Cat6 runs as I was getting on the Cat5, so it would seem that there is some Cat5 out there that is with in specification for running Gigabit in at least a home network type environment.
  3. No disk error (reported by unRAID, but there was the disk with the SMART error reported.) However the same error occurred at the same spot 4 different times during parity checks. This is easy to verify as the error occurs almost immediately after starting the parity check. I swapped out the power supply last week and ran memtest for 10 hours straight with no errors reported.
  4. Ok, will just let the parity check correct the error and move on then. Thanks for the help.
  5. I ran a parity check today and received one error. I ran from unMenu with the No Correction option. The error is detected immediately after starting the check. Of note I also have a disk that was showing a Multi_Zone_Error_Rate of 1 (has since dropped to 0.) Would it be likely that the disk that had the error was at fault and not the parity drive? Any suggestions on how to proceed? Edit to add: The line from the syslog showing the error. Dec 4 21:45:14 DarkTower kernel: md: parity incorrect: 1728 This was detected the same 4 different times (I didn't run 4 full checks, after the 1st full check with the 1 parity error I started and stopped 3 more times to verify the error.)
  6. Don't know why you haven't ordered from tigerdirect.....sure you have to pay shipping but I have seen a lot over the years where their price was cheaper.....I could be a bit biased because i live so close to their Chicago shipping facility....within reason they ALWAYS ship the same day....its freaking amazing...lol I have order as late as 6:00 their time and got the items the next day but recently i have pretty much order everything from Newegg because i have caught almost all the stuff on shellshocker....and they have usually taken a couple of days just to ship.....usually the prices are close....guess it depends how quickly you want the item I always come away with a used-car sales feeling when ordering from them. The thing that brought that feeling with that last order was the prompt for the last 4 of my SSN to verify the order.
  7. Ordered 2 from newegg and 1 from tigerdirect. And in doing so, remembered why I haven't ordered from tigerdirect in 7 or 8 years.
  8. Yup. Release -rc4 will have the same kernel as 4.5.6, so this will be unnecessary for you. If there were benefits to the kernel change you made then I have no problems having to add the two lines to go. After being given a shove in the right direction it was easy enough to figure out and fix.
  9. You may need to modprobe the it87 driver.... some newer mobos have partial compatibility with it87, but really need a newer driver, and if it87 is built into the kernel, you can't unload it, so a request was mode to leave the instrumentation drivers like it87 as modules, so you need to modprobe them. So I ran sensors-detect and got: # sensors-detect revision 5337 (2008-09-19 17:05:28 +0200) This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. We can start with probing for (PCI) I2C or SMBus adapters. Do you want to probe now? (YES/no): YES Probing for PCI bus adapters... Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3. Sorry, no supported PCI bus adapters found. If you have undetectable or unsupported I2C/SMBus adapters, you can have them scanned by manually loading the modules before running this script. To continue, we need module `i2c-dev' to be loaded. Do you want to load `i2c-dev' now? (YES/no): YES Module loaded successfully. We are now going to do the I2C/SMBus adapter probings. Some chips may be double detected; we choose the one with the highest confidence value in that case. If you found that the adapter hung after probing a certain address, you can specify that address to remain unprobed. Next adapter: SMBus I801 adapter at 0400 (i2c-0) Do you want to scan it? (YES/no/selectively): YES Client found at address 0x18 Probing for `Analog Devices ADM1021'... No Probing for `Analog Devices ADM1021A/ADM1023'... No Probing for `Maxim MAX1617'... No Probing for `Maxim MAX1617A'... No Probing for `Maxim MAX1668'... No Probing for `Maxim MAX1805'... No Probing for `Maxim MAX1989'... No Probing for `Maxim MAX6655/MAX6656'... No Probing for `TI THMC10'... No Probing for `National Semiconductor LM84'... No Probing for `Genesys Logic GL523SM'... No Probing for `Onsemi MC1066'... No Probing for `Maxim MAX1618'... No Probing for `Maxim MAX1619'... No Probing for `National Semiconductor LM82/LM83'... No Probing for `Maxim MAX6654/MAX6690'... No Probing for `Maxim MAX6680/MAX6681'... No Probing for `National Semiconductor LM64'... No Client found at address 0x1a Probing for `Analog Devices ADM1021'... No Probing for `Analog Devices ADM1021A/ADM1023'... No Probing for `Maxim MAX1617'... No Probing for `Maxim MAX1617A'... No Probing for `Maxim MAX1668'... No Probing for `Maxim MAX1805'... No Probing for `Maxim MAX1989'... No Probing for `Maxim MAX6655/MAX6656'... No Probing for `TI THMC10'... No Probing for `National Semiconductor LM84'... No Probing for `Genesys Logic GL523SM'... No Probing for `Onsemi MC1066'... No Probing for `Maxim MAX1618'... No Probing for `Maxim MAX1619'... No Probing for `National Semiconductor LM82/LM83'... No Probing for `Maxim MAX6654/MAX6690'... No Probing for `Maxim MAX6680/MAX6681'... No Client found at address 0x48 Probing for `National Semiconductor LM75'... No Probing for `Dallas Semiconductor DS75'... No Probing for `National Semiconductor LM77'... No Probing for `Dallas Semiconductor DS1621/DS1631'... No Probing for `Maxim MAX6650/MAX6651'... No Probing for `National Semiconductor LM92'... No Probing for `National Semiconductor LM76'... No Probing for `Maxim MAX6633/MAX6634/MAX6635'... No Client found at address 0x50 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Probing for `EDID EEPROM'... No Client found at address 0x52 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Probing for `EDID EEPROM'... No Some chips are also accessible through the ISA I/O ports. We have to write to arbitrary I/O ports to probe them. This is usually safe though. Yes, you do have ISA I/O ports even if you do not have any ISA slots! Do you want to scan the ISA I/O ports? (YES/no): YES Probing for `National Semiconductor LM78' at 0x290... No Probing for `National Semiconductor LM78-J' at 0x290... No Probing for `National Semiconductor LM79' at 0x290... No Probing for `Winbond W83781D' at 0x290... No Probing for `Winbond W83782D' at 0x290... No Probing for `IPMI BMC KCS' at 0xca0... Success! (confidence 4, driver `ipmisensors') Probing for `IPMI BMC SMIC' at 0xca8... No Some Super I/O chips may also contain sensors. We have to write to standard I/O ports to probe them. This is usually safe. Do you want to scan for Super I/O sensors? (YES/no): YES Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Fintek'... Yes Found `Winbond W83627DHG Super IO Sensors' Success! (address 0xa10, driver `w83627ehf') Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Fintek'... No Trying family `ITE'... No Some south bridges, CPUs or memory controllers may also contain embedded sensors. Do you want to scan for them? (YES/no): YES Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD K10 thermal sensors... No Intel Core family thermal sensor... No Intel AMB FB-DIMM thermal sensor... No VIA C7 thermal and voltage sensors... No Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `ipmisensors' (should be inserted): Detects correctly: * ISA bus, address 0xca0 Chip `IPMI BMC KCS' (confidence: 4) Driver `w83627ehf' (should be inserted): Detects correctly: * ISA bus, address 0xa10 Chip `Winbond W83627DHG Super IO Sensors' (confidence: 9) Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): NO To load everything that is needed, add this to one of the system initialization scripts (e.g. /etc/rc.d/rc.local): #----cut here---- # You must also install and load the IPMI modules modprobe ipmi-si # Chip drivers # Warning: the required module ipmisensors is not currently installed # on your system. For status of 2.6 kernel ports check # http://www.lm-sensors.org/wiki/Devices. If driver is built # into the kernel, or unavailable, comment out the following line. modprobe ipmisensors modprobe w83627ehf /usr/bin/sensors -s #----cut here---- If you have some drivers built into your kernel, the list above will contain too many modules. Skip the appropriate ones! You really should try these commands right now to make sure everything is working properly. Monitoring programs won't work until the needed modules are loaded. issuing: modprobe w83627ehf /usr/bin/sensors -s got the fan control working again. So would I just put those two lines in my go file and be good? Also, is there any benefit to adding the lines for the IPMI drivers as well?
  10. 4.5.6. Downgrading back to 4.5.6 brought back fan control.
  11. Upgraded to get rid of the HDIO_GET_IDENTITY errors. With the new version, my ability to access the fan control device has disappeared. The /sys/class/hwmon directory (and everything under it) is not there with the upgrade.
  12. So after running 4 individual (didn't use -c 4) preclear cycles on the misbehaving disk: a) On the second cycle all the errors went away. The pending sectors did not become reallocated sectors and all the normalized values seemed to go to default after first run values b) After the 4th cycle I got the following: < 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 --- > 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 which doesn't look bad at all, but also isn't exactly comforting (gives me the impression that there is still something odd going on considering the disks history.)
  13. Have the exact same problem with that board and the Norco 4220 case.
  14. I may have assumed the most recent disk was bad to early. When it was invalidated it stopped responding (hdparm, smartctl.) I replaced it with a precleared drive I have in case of failure. I also put the assumed failed drive back into the 4220 at a different location. At the new location it was now responding (unfortunately I didn't reboot at all with the drive in the same location.) With the drive responding and the array rebuilt with the new drive (I waited for this process to complete to be safe) I ran a preclear on the assumed failed drive. At the conclusion of the preclear, the errors had dropped to 5 (except the multi_zone_error_rate which was still sitting at the same value.) I left the drives in and checked smart again last night. All the errors had dropped to zero and the normal values are showing like nothing ever happened. Also Reallocated_sector_ct is also still 0 so I am assuming none of the sectors were actually reallocated. I am currently running 2 more pre-clear cycles on the drive.
  15. Do you still have the smart output from after the preclear? If it was clean after the preclear, this is the first disk I've heard of that died an early death after preclear. I have now had two drives die early deaths after completing the preclear. The first one only completed one cycle. The drive I just posted about completed 3 preclear cycles and then ran for less then a month. Died on the 3rd parity check. The smart values I posted above (or any others for that matter) did not change at all during the first 2 parity checks.
  16. So would: » current_pending_sector=10 » offline_uncorrectable=10 » multi_zone_error_rate=221 Just be watch the disk, or should I swap it out? After noticing those numbers initially, I ran a parity check (non-correcting from unmenu) that reported no sync errors and the SMART error values did not change. Edit: The normalized values for all three of those shows: 200 200 000
  17. What you have stated has been confirmed a couple of times. It has also been stated in the last week or so that if you want to guaranty your self new stock, order from ipcdirect. Also, the 120mm fan wall can be made to fit the old style, but requires an amount of work not much less then just modifying the original fan wall to accept 120mm fans.
  18. Over the last month I have precleared 8 2TB EARS drives and 3 2TB EADS drives as well as a 2TB caviar black drive. All drives got 3 cycles except one of the EARS drives (which became almost completely non-responsive after the first preclear cycle and was RMA'd.) The EARS and EADS drives ranged between 25 and 27 hours per cycle and the caviar black drive was just under 24 hours per cycle. Didn't seem to matter much if the drives were on the mother board or the supermicro controllers. Also didn't seem to be a consistent difference between the EARS and EADS drives.
  19. With the old style case, the location I installed the 120mm fan plate is butted up against the motherboard tray. This gives a little more room between the wall and the backplanes. I was able to route the cables across the top and bottom of the fan and the extra room meant a lot more comfortable a bend to get them plugged in. So even though I have to have the cable going across the fan, it is done with little to no interference and none of the cable bends are bad. The 120mm fans running at medium speed seem to provide the same cooling as the 80mm running at full speed with 10 hard drives under full load during a parity check.
  20. Problem with the bios controlling the fans is that it can not key off hard drive temps.
  21. The script as I have been using it is attached. One note, it seems the X8SIL-F has a built in fail safe as mentioned in one of my previous posts. I initially thought it was just on fan port 1, but it is in fact on all the fan ports. If you set the fans too low, the motherboard will kick PWM back to automatic and the fans will go to full speed. This happens pretty quickly, so it is easy to test and find out where the limit is. unraid-fan-speed.sh.zip
  22. Been using this script for 5 days now with good results. Definitely a good option for anybody using an X8SIL-F with PWM fans. The 3 120mm deltas I replaced the 4 stock 80mm fans that came with the Norco 4220 run quieter then the other equipment in the room 80% of the time. The other 20% has been running at the medium speed which isn't at all bad either. It has not yet needed to kick the fans up to full.
  23. If I knew it didn't fit before starting the process I would have: 1) Set the wall next to the outside of the chassis (accounting for the chassis bottom) and marked the rail indent bottom location on each side of the fan wall. 2) Set the wall on top the chassis (top to top) and marked the rail top on each side of the fan wall. This would have allowed the material to be properly removed prior to any attempt at installing the fan wall and been much cleaner cuts.
  24. A month old, but it still has the SAS connectors on the back plane all the way to the side so it may have been old stock. I believe the 120mm fan wall was designed for the 4224 and they indicated it would fit the 4220 (maybe with out sufficient testing.)