zzgus

Members
  • Content count

    155
  • Joined

  • Last visited

Community Reputation

1 Neutral

About zzgus

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    Barcelona
  1. I know the thread is very old but for not open a new one. I have flashed an H310 without problems and I see the discs I attach to the controller as unassigned devices. Haven't tested more. Only for curioity: Is the PERC H310 able to boot windows? Thankyou Gus
  2. I have found this: The Intel® Processor Diagnostic Tool https://www.intel.com/content/www/us/en/support/processors/000005567.html Let's try it. Thankyou Gus
  3. Hi I have got a server motherboard with some cpu pins bent. At first the motherboard didn't fire up but after some work realigning pins I got it working. Now my question is: Is reliable this motherboard? Is there any way to test if all the pins are well realigned or simply a motherboard+cpu with any pin that is bent and doesn't touch the cpu will not start? Thankyou Gus
  4. Too much random read errors?

    Very annoying all those problems. The truth is that since I replaced all cables I haven't had any problems (almost 2 months without any problem) and all the problems return with the 2 power cuts this saturday. Will re-check cables and if the problems return will have to try an alternative. Thankyou Gus
  5. Too much random read errors?

    Will refloat the thread as new problems have come. @bjp999 @Frank1940 All the errors with my discs were solved with a simple sata cable swaping. I replaced all the cables *show in a post before with normal 1m sata cables. Since then no more errors. Yesterday I got two power cuts in my house. It showed my disk 1 as emuled. Re-build this disc and all ok. Some minutes after another time the disc is emulated with 192 errors. What must I do, do I re-rebuild the disc another time? Attach diagnostics. Thankyou Gus unraid-media-diagnostics-20170909-1434.zip
  6. Too much random read errors?

    Is there any utility in unraid to perform this test? thankyou gus
  7. Too much random read errors?

    Thankyou @Frank1940 The truth is that I'm using those cables that are pretty near: https://www.amazon.es/CableDeconn-Speed-6Gbps-Quality-Server/dp/B00VI3MFMO/ref=sr_1_2?ie=UTF8&qid=1500127291&sr=8-2&keywords=sata+cable+1m Can this be the problem? Gus
  8. Too much random read errors?

    Here is the "diagnostics" file. And the drive with those errors was this: smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.9.30-unRAID] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Red Device Model: WDC WD40EFRX-68WT0N0 Serial Number: WD-WCC4E4CLFP20 LU WWN Device Id: 5 0014ee 20cf990a2 Firmware Version: 82.00A82 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2 (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Fri Jul 14 21:42:10 2017 CEST 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: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. 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: (52860) 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: ( 529) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x703d) SCT Status supported. SCT Error Recovery Control 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 185 178 021 Pre-fail Always - 7741 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 855 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 088 088 000 Old_age Always - 8958 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 108 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 66 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1982 194 Temperature_Celsius 0x0022 112 103 000 Old_age Always - 40 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 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 SMART Error Log Version: 1 ATA Error Count: 24 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 24 occurred at disk power-on lifetime: 8825 hours (367 days + 17 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 45 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 45 00 00 00 a0 00 00:23:12.221 SET FEATURES [Set transfer mode] ec 00 00 00 00 00 a0 00 00:23:12.221 IDENTIFY DEVICE ec 00 00 00 00 00 a0 00 00:23:06.180 IDENTIFY DEVICE ef 03 45 00 00 00 a0 00 00:23:06.179 SET FEATURES [Set transfer mode] ec 00 00 00 00 00 a0 00 00:23:06.179 IDENTIFY DEVICE Error 23 occurred at disk power-on lifetime: 8825 hours (367 days + 17 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 45 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 45 00 00 00 a0 00 00:23:06.179 SET FEATURES [Set transfer mode] ec 00 00 00 00 00 a0 00 00:23:06.179 IDENTIFY DEVICE ec 00 00 00 00 00 a0 00 00:23:00.809 IDENTIFY DEVICE ef 03 45 00 00 00 a0 00 00:23:00.809 SET FEATURES [Set transfer mode] ec 00 00 00 00 00 a0 00 00:23:00.808 IDENTIFY DEVICE Error 22 occurred at disk power-on lifetime: 8825 hours (367 days + 17 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 45 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 45 00 00 00 a0 00 00:23:00.809 SET FEATURES [Set transfer mode] ec 00 00 00 00 00 a0 00 00:23:00.808 IDENTIFY DEVICE c8 00 08 00 00 00 e0 00 00:23:00.632 READ DMA ec 00 00 00 00 00 a0 00 00:22:00.709 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 00:22:00.709 SET FEATURES [Set transfer mode] Error 21 occurred at disk power-on lifetime: 8825 hours (367 days + 17 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 08 00 00 00 e0 Device Fault; Error: ABRT 8 sectors at LBA = 0x00000000 = 0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 00 00 00 e0 00 00:23:00.632 READ DMA ec 00 00 00 00 00 a0 00 00:22:00.709 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 00:22:00.709 SET FEATURES [Set transfer mode] ec 00 00 00 00 00 a0 00 00:22:00.708 IDENTIFY DEVICE Error 20 occurred at disk power-on lifetime: 8825 hours (367 days + 17 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 46 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 46 00 00 00 a0 00 00:22:00.709 SET FEATURES [Set transfer mode] ec 00 00 00 00 00 a0 00 00:22:00.708 IDENTIFY DEVICE ec 00 00 00 00 00 a0 00 00:21:29.508 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 00:21:29.508 SET FEATURES [Set transfer mode] SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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. unraid-media-diagnostics-20170714-2142.zip
  9. It's my second or third post about my server read errors. I have had errors related to controllers on the motherboard (marvell), had errors also on intel scu controllers, related to discs (replaced), have tried two kind of supermicro server motherboards, replaced sata cables, etc but the errors return. The truth is that I don't know what else to try to not get errors evey 15 days. Yesterday I got 32 read errors on one of my discs. (When I got home will attach diagnostic file.) What is the exact procedure to follow after those errors? Is still the parity disc valid? Do I have to rebuild my disc everytime I got a read error? Thankyou Gus
  10. FOR SALE IN SPAIN: (possible to ship in europe) http://www.asrockrack.com/general/productdetail.asp?Model=EP2C602#Specifications ASROCK EP2C602: - Dual Socket R (LGA2011), supports Intel Xeon 5-1600/2600/4600 & v2 series - Supports Quad Channel DDR3 1866 memory, 8 DIMM slots, Max. 256GB - 5 PCIe 3.0 x16, 1 PCIe 3.0 x4, 1 PCI - ASPEED AST2300 graphics, 1 VGA : D-Sub - 2 SATA3 (6.0 Gb/s), 8 SATA2 (3.0 Gb/s) by Intel C602, Supports RAID 0, 1, 5, 10 - 4 SATA3 (6.0 Gb/s) by Marvell SE9230, Supports RAID 0, 1, 10 - 7 USB 2.0 (2 from rear I/O, 4 from onboard headers, 1 Type A port) - Integrated IPMI 2.0 with KVM and Dedicated LAN (RTL8211E) - 2 Intel 82574L LAN, Support PCIE Dual Gigabit LAN USED (3 months) 300€ - PAYPAL Also have a XEON E5-2670 Octa Core CPU 8x2.6GHZ-20MB 8.00GT/s FCLGA2011, SR0KX + FREE Noctua NH-U9DX (60€) USED 120€ - PAYPAL Gus forosgus@gmail.com
  11. Lost disc, how to proceed?

    @johnnie.blackbad news. I did a rebuild with no luck, some read errors. (rebuild cancelled I think unraid showed on notifiactions tab) I will remove this disc for safety. Gus
  12. Lost disc, how to proceed?

    @johnnie.black Well, mmmm not yet a month and another time some errors on disk 6 a before. Attached diagnostics to see if there's something new. I don't know what I will have to do with those "persistent" crashes :-( Thankyou Gus unraid-media-diagnostics-20170515-2137.zip
  13. EP2C602 - IPMI Fan Control

    Will chech the BIOS version tomorrow but if I'm not wrong is the last bios asrock publised. Are you having any problems with the sata controllers? It's the second time I had a problem with my discs caused by the controllers. The first time It was recommended to me that I not use the MARVEL SATA CONNECTORS (the four at the right) and the second time a problem with the intel controller. Had to rebuild one disc. Cross fingers to not happen another time. Gus
  14. Lost disc, how to proceed?

    @johnnie.black one last thing. I have a spare single socket supermicro X9SRi-F motherboard. http://www.supermicro.com/products/motherboard/Xeon/C600/X9SRi-F.cfm As I no longer need the dual socket ASROCK motherboard I'm using now, do you think the supermicro will be a better option? Thankyou Gus
  15. Lost disc, how to proceed?

    As always @johnnie.blackmany thanks for your quick response. Gus
Copyright © 2005-2017 Lime Technology, Inc. unRAID® is a registered trademark of Lime Technology, Inc.