samukas
Members-
Posts
18 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by samukas
-
I replaced some sata cables for the array drives and seems the issue is gone! At least for now. My external dock which I use to copy files over also seems to be having issues, so, I suppose the eSATA cable needs replacement also. Thanks for the help, Joe L!
-
Thanks Joe L! I didn't notice that in the second log the device name was there. What about the first log, the overnight one... How can I tell which disk is which?
-
Another thing I saw. What do these errors mean exactly ? Jan 4 13:00:16 Tower kernel: ata15: exception Emask 0x10 SAct 0x0 SErr 0x80000 action 0xe frozen (Errors) Jan 4 13:00:16 Tower kernel: ata15: irq_stat 0x01100010, PHY RDY changed (Drive related) Jan 4 13:00:16 Tower kernel: ata15: SError: { 10B8B } (Errors) Jan 4 13:00:16 Tower kernel: ata15: hard resetting link (Minor Issues) Jan 4 13:00:18 Tower kernel: ata15: SATA link down (SStatus 0 SControl 0) (Drive related) Jan 4 13:00:23 Tower kernel: ata15: hard resetting link (Minor Issues) Jan 4 13:00:25 Tower kernel: ata15: SATA link down (SStatus 0 SControl 0) (Drive related) Jan 4 13:00:25 Tower kernel: ata15: limiting SATA link speed to 1.5 Gbps (Drive related) Jan 4 13:00:30 Tower kernel: ata15: hard resetting link (Minor Issues) Jan 4 13:00:32 Tower kernel: ata15: SATA link down (SStatus 0 SControl 10) (Drive related) Jan 4 13:00:32 Tower kernel: ata15.00: disabled (Errors) Jan 4 13:00:32 Tower kernel: ata15: EH complete (Drive related) Jan 4 13:00:32 Tower kernel: ata15.00: detaching (SCSI 15:0:0:0) (Drive related) Jan 4 13:00:32 Tower kernel: sd 15:0:0:0: [sdp] Synchronizing SCSI cache (Drive related) Jan 4 13:00:32 Tower kernel: sd 15:0:0:0: [sdp] Result: hostbyte=0x04 driverbyte=0x00 (System) Jan 4 13:00:32 Tower kernel: sd 15:0:0:0: [sdp] Stopping disk (Drive related) Jan 4 13:00:32 Tower kernel: sd 15:0:0:0: [sdp] START_STOP FAILED (Drive related) Jan 4 13:00:32 Tower kernel: sd 15:0:0:0: [sdp] Result: hostbyte=0x04 driverbyte=0x00 (System)
-
Yesterday I inserted 3 new HDDs (after preclearing them) in my array to a total of 14 disks now, and I left two "move" processes overnight, trough telnet sessions, and aparently there have been some issues. - One of the processes is still running, but really really slow, it's already taking 10 hours or more to move just 1TB internally, I don't remember it being that slow; - The other process just stopped moving overnight, with no warning whatsoever in the telnet window. Here is what I found in the syslog, can somebody please explain me what is is? Jan 4 02:57:02 Tower kernel: ata10: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen Jan 4 02:57:02 Tower kernel: ata10: edma_err_cause=00000020 pp_flags=00000000, SError=00180000 Jan 4 02:57:02 Tower kernel: ata10: SError: { 10B8B Dispar } Jan 4 02:57:02 Tower kernel: ata10: hard resetting link Jan 4 02:57:02 Tower kernel: ata11: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen Jan 4 02:57:02 Tower kernel: ata11: edma_err_cause=00000020 pp_flags=00000000, SError=00180000 Jan 4 02:57:02 Tower kernel: ata11: SError: { 10B8B Dispar } Jan 4 02:57:02 Tower kernel: ata11: hard resetting link Jan 4 02:57:02 Tower kernel: ata13: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen Jan 4 02:57:02 Tower kernel: ata13: edma_err_cause=00000020 pp_flags=00000000, SError=00180000 Jan 4 02:57:02 Tower kernel: ata13: SError: { 10B8B Dispar } Jan 4 02:57:02 Tower kernel: ata13: hard resetting link Jan 4 02:57:02 Tower kernel: ata13: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jan 4 02:57:02 Tower kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jan 4 02:57:02 Tower kernel: ata11: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jan 4 02:57:02 Tower kernel: ata11.00: configured for UDMA/133 Jan 4 02:57:02 Tower kernel: ata11: EH complete Jan 4 02:57:02 Tower kernel: ata10.00: configured for UDMA/133 Jan 4 02:57:02 Tower kernel: ata10: EH complete Jan 4 02:57:02 Tower kernel: ata13.00: configured for UDMA/133 Jan 4 02:57:02 Tower kernel: ata13: EH complete Thanks in advance!
-
Samsung released firmware update for these drives: http://www.samsung.com/global/business/hdd/faqView.do?b2b_bbs_msg_id=386 I'm wondering if this solves the issues with unRaid or if it isn't releated at all? Edit: Oops, didn't see the other thread. Sorry for that.
-
I posted a syslog back at the preclear utility thread by mistake, so here it is in the right place.Here are attached two syslogs from preclearing the same drive. I believe some values changed from one preclear to another, so maybe something is wrong with the drive? RMA? What would you do guys? Thanks in advance. disco_falhou.txt disco_falhou_2.txt
-
So, I'm not having much luck with Samsung drives. I sent onde for RMA some months ago and now that I bought four more, one of them gave me this report with preclear script Jun 15 17:10:50 Tower preclear_disk-finish[29189]: smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Home page is http://smartmontools.sourceforge.net/ Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Jun 15 17:10:50 Tower preclear_disk-finish[29189]: === START OF INFORMATION SECTION === Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Device Model: SAMSUNG HD203WI Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Serial Number: S1UYJ1KZ303392 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Firmware Version: 1AN10002 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: User Capacity: 2,000,398,934,016 bytes Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Device is: In smartctl database [for details use: -P show] Jun 15 17:10:50 Tower preclear_disk-finish[29189]: ATA Version is: 8 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: ATA Standard is: Not recognized. Minor revision code: 0x28 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Local Time is: Tue Jun 15 17:10:49 2010 GMT Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Jun 15 17:10:50 Tower preclear_disk-finish[29189]: ==> WARNING: May need -F samsung or -F samsung2 enabled; see manual for details. Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Jun 15 17:10:50 Tower preclear_disk-finish[29189]: SMART support is: Available - device has SMART capability. Jun 15 17:10:50 Tower preclear_disk-finish[29189]: SMART support is: Enabled Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Jun 15 17:10:50 Tower preclear_disk-finish[29189]: === START OF READ SMART DATA SECTION === Jun 15 17:10:50 Tower preclear_disk-finish[29189]: SMART overall-health self-assessment test result: PASSED Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Jun 15 17:10:50 Tower preclear_disk-finish[29189]: General SMART Values: Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Offline data collection status: (0x00)^IOffline data collection activity Jun 15 17:10:50 Tower preclear_disk-finish[29189]: ^I^I^I^I^Iwas never started. Jun 15 17:10:50 Tower preclear_disk-finish[29189]: ^I^I^I^I^IAuto Offline Data Collection: Disabled. Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Self-test execution status: ( 0)^IThe previous self-test routine completed Jun 15 17:10:50 Tower preclear_disk-finish[29189]: ^I^I^I^I^Iwithout error or no self-test has ever Jun 15 17:10:50 Tower preclear_disk-finish[29189]: ^I^I^I^I^Ibeen run. Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Total time to complete Offline Jun 15 17:10:50 Tower preclear_disk-finish[29189]: data collection: ^I^I (25740) seconds. Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Offline data collection Jun 15 17:10:50 Tower preclear_disk-finish[29189]: capabilities: ^I^I^I (0x5b) SMART execute Offline immediate. Jun 15 17:10:50 Tower preclear_disk-finish[29189]: ^I^I^I^I^IAuto Offline data collection on/off support. Jun 15 17:10:50 Tower preclear_disk-finish[29189]: ^I^I^I^I^ISuspend Offline collection upon new Jun 15 17:10:50 Tower preclear_disk-finish[29189]: ^I^I^I^I^Icommand. Jun 15 17:10:50 Tower preclear_disk-finish[29189]: ^I^I^I^I^IOffline surface scan supported. Jun 15 17:10:50 Tower preclear_disk-finish[29189]: ^I^I^I^I^ISelf-test supported. Jun 15 17:10:50 Tower preclear_disk-finish[29189]: ^I^I^I^I^INo Conveyance Self-test supported. Jun 15 17:10:50 Tower preclear_disk-finish[29189]: ^I^I^I^I^ISelective Self-test supported. Jun 15 17:10:50 Tower preclear_disk-finish[29189]: SMART capabilities: (0x0003)^ISaves SMART data before entering Jun 15 17:10:50 Tower preclear_disk-finish[29189]: ^I^I^I^I^Ipower-saving mode. Jun 15 17:10:50 Tower preclear_disk-finish[29189]: ^I^I^I^I^ISupports SMART auto save timer. Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Error logging capability: (0x01)^IError logging supported. Jun 15 17:10:50 Tower preclear_disk-finish[29189]: ^I^I^I^I^IGeneral Purpose Logging supported. Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Short self-test routine Jun 15 17:10:50 Tower preclear_disk-finish[29189]: recommended polling time: ^I ( 2) minutes. Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Extended self-test routine Jun 15 17:10:50 Tower preclear_disk-finish[29189]: recommended polling time: ^I ( 255) minutes. Jun 15 17:10:50 Tower preclear_disk-finish[29189]: SCT capabilities: ^I (0x003f)^ISCT Status supported. Jun 15 17:10:50 Tower preclear_disk-finish[29189]: ^I^I^I^I^ISCT Feature Control supported. Jun 15 17:10:50 Tower preclear_disk-finish[29189]: ^I^I^I^I^ISCT Data Table supported. Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Jun 15 17:10:50 Tower preclear_disk-finish[29189]: SMART Attributes Data Structure revision number: 16 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Vendor Specific SMART Attributes with Thresholds: Jun 15 17:10:50 Tower preclear_disk-finish[29189]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Jun 15 17:10:50 Tower preclear_disk-finish[29189]: 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 390 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: 3 Spin_Up_Time 0x0023 062 062 025 Pre-fail Always - 11768 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 3 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 61 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 40 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 3 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: 191 G-Sense_Error_Rate 0x0022 252 252 000 Old_age Always - 0 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 61 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: 197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: 199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 174 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 5 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Jun 15 17:10:50 Tower preclear_disk-finish[29189]: SMART Error Log Version: 1 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: No Errors Logged Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Jun 15 17:10:50 Tower preclear_disk-finish[29189]: SMART Self-test log structure revision number 1 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: No self-tests have been logged. [To run self-tests, use: smartctl -t] Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Jun 15 17:10:50 Tower preclear_disk-finish[29189]: SMART Selective Self-Test Log Data Structure Revision Number (0) should be 1 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: SMART Selective self-test log data structure revision number 0 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Warning: ATA Specification requires selective self-test log data structure revision number = 1 Jun 15 17:10:50 Tower preclear_disk-finish[29189]: SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS Jun 15 17:10:50 Tower preclear_disk-finish[29189]: 1 0 0 Completed [00% left] (0-65535) Jun 15 17:10:50 Tower preclear_disk-finish[29189]: 2 0 0 Not_testing Jun 15 17:10:50 Tower preclear_disk-finish[29189]: 3 0 0 Not_testing Jun 15 17:10:50 Tower preclear_disk-finish[29189]: 4 0 0 Not_testing Jun 15 17:10:50 Tower preclear_disk-finish[29189]: 5 0 0 Not_testing Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Selective self-test flags (0x0): Jun 15 17:10:50 Tower preclear_disk-finish[29189]: After scanning selected spans, do NOT read-scan remainder of disk. Jun 15 17:10:50 Tower preclear_disk-finish[29189]: If Selective self-test is pending on power-up, resume after 0 minute delay. Jun 15 17:10:50 Tower preclear_disk-finish[29189]: Jun 15 17:10:50 Tower preclear_disk-diff[29202]: ============================================================================ Jun 15 17:10:50 Tower preclear_disk-diff[29202]: == Jun 15 17:10:50 Tower preclear_disk-diff[29202]: == Disk /dev/sdl has been successfully precleared Jun 15 17:10:50 Tower preclear_disk-diff[29202]: == Jun 15 17:10:50 Tower preclear_disk-diff[29202]: == Ran 1 preclear-disk cycle Jun 15 17:10:50 Tower preclear_disk-diff[29202]: == Jun 15 17:10:50 Tower preclear_disk-diff[29202]: == Using :Read block size = 8225280 Bytes Jun 15 17:10:50 Tower preclear_disk-diff[29202]: == Last Cycle's Pre Read Time : 7:34:47 (73 MB/s) Jun 15 17:10:50 Tower preclear_disk-diff[29202]: == Last Cycle's Zeroing time : 7:18:11 (76 MB/s) Jun 15 17:10:50 Tower preclear_disk-diff[29202]: == Last Cycle's Post Read Time : 15:17:32 (36 MB/s) Jun 15 17:10:50 Tower preclear_disk-diff[29202]: == Last Cycle's Total Time : 30:11:58 Jun 15 17:10:50 Tower preclear_disk-diff[29202]: == Jun 15 17:10:50 Tower preclear_disk-diff[29202]: == Total Elapsed Time 30:11:58 Jun 15 17:10:50 Tower preclear_disk-diff[29202]: == Jun 15 17:10:50 Tower preclear_disk-diff[29202]: == Jun 15 17:10:50 Tower preclear_disk-diff[29202]: ============================================================================ Jun 15 17:10:50 Tower preclear_disk-diff[29202]: S.M.A.R.T. error count differences detected after pre-clear Jun 15 17:10:50 Tower preclear_disk-diff[29202]: note, some 'raw' values may change, but not be an indication of a problem Jun 15 17:10:50 Tower preclear_disk-diff[29202]: 55c55 Jun 15 17:10:50 Tower preclear_disk-diff[29202]: < 1 Raw_Read_Error_Rate 0x002f 252 252 051 Pre-fail Always - 0 Jun 15 17:10:50 Tower preclear_disk-diff[29202]: --- Jun 15 17:10:50 Tower preclear_disk-diff[29202]: > 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 390 Jun 15 17:10:50 Tower preclear_disk-diff[29202]: 59c59 Jun 15 17:10:50 Tower preclear_disk-diff[29202]: < 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 Jun 15 17:10:50 Tower preclear_disk-diff[29202]: --- Jun 15 17:10:50 Tower preclear_disk-diff[29202]: > 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 61 Jun 15 17:10:50 Tower preclear_disk-diff[29202]: 67,68c67,68 Jun 15 17:10:50 Tower preclear_disk-diff[29202]: < 195 Hardware_ECC_Recovered 0x003a 252 252 000 Old_age Always Jun 15 17:10:50 Tower preclear_disk-diff[29202]: < 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 Jun 15 17:10:50 Tower preclear_disk-diff[29202]: --- Jun 15 17:10:50 Tower preclear_disk-diff[29202]: > 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always Jun 15 17:10:50 Tower preclear_disk-diff[29202]: > 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 61 Jun 15 17:10:50 Tower preclear_disk-diff[29202]: 72c72 Jun 15 17:10:50 Tower preclear_disk-diff[29202]: < 200 Multi_Zone_Error_Rate 0x002a 252 252 000 Old_age Always - 0 Jun 15 17:10:50 Tower preclear_disk-diff[29202]: --- Jun 15 17:10:50 Tower preclear_disk-diff[29202]: > 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 174 Jun 15 17:10:50 Tower preclear_disk-diff[29202]: ============================================================================ Jun 15 17:10:50 Tower preclear_disk-diff[29202]: If I understand correctly, 61 Reallocated Sectors by the end of preclear... Should I sent this drive back or is "61 ok"?
-
Thanks for all the help, I'll definitely send the drive for a replacement! I'm glad I did find out about it before adding it to the array, that would have been a headache, for sure! As for the other 3 drives, I keep getting those S.M.A.R.T. "Airflow_temperature_Cel" and "Soft_Read_error_Rate" that I was told not to worry about. I'm just curious, what do these errors mean exactly? Regards! Mar 16 07:30:17 Tower preclear_disk-diff[14200]: ============================================================================ Mar 16 07:30:17 Tower preclear_disk-diff[14200]: == Mar 16 07:30:17 Tower preclear_disk-diff[14200]: == Disk /dev/sdg has been successfully precleared Mar 16 07:30:17 Tower preclear_disk-diff[14200]: == Mar 16 07:30:17 Tower preclear_disk-diff[14200]: == Ran 1 preclear-disk cycle Mar 16 07:30:17 Tower preclear_disk-diff[14200]: == Mar 16 07:30:17 Tower preclear_disk-diff[14200]: == Using :Read block size = 8225280 Bytes Mar 16 07:30:17 Tower preclear_disk-diff[14200]: == Last Cycle's Pre Read Time : 5:39:06 (73 MB/s) Mar 16 07:30:17 Tower preclear_disk-diff[14200]: == Last Cycle's Zeroing time : 5:53:20 (70 MB/s) Mar 16 07:30:17 Tower preclear_disk-diff[14200]: == Last Cycle's Post Read Time : 10:59:39 (37 MB/s) Mar 16 07:30:17 Tower preclear_disk-diff[14200]: == Last Cycle's Total Time : 22:33:09 Mar 16 07:30:17 Tower preclear_disk-diff[14200]: == Mar 16 07:30:17 Tower preclear_disk-diff[14200]: == Total Elapsed Time 22:33:09 Mar 16 07:30:17 Tower preclear_disk-diff[14200]: == Mar 16 07:30:17 Tower preclear_disk-diff[14200]: == Disk Start Temperature: 18C Mar 16 07:30:17 Tower preclear_disk-diff[14200]: == Mar 16 07:30:17 Tower preclear_disk-diff[14200]: == Current Disk Temperature: 21C, Mar 16 07:30:17 Tower preclear_disk-diff[14200]: == Mar 16 07:30:17 Tower preclear_disk-diff[14200]: ============================================================================ Mar 16 07:30:17 Tower preclear_disk-diff[14200]: S.M.A.R.T. error count differences detected after pre-clear Mar 16 07:30:17 Tower preclear_disk-diff[14200]: note, some 'raw' values may change, but not be an indication of a problem Mar 16 07:30:17 Tower preclear_disk-diff[14200]: 71c71 Mar 16 07:30:17 Tower preclear_disk-diff[14200]: < 190 Airflow_Temperature_Cel 0x0022 082 076 000 Old_age Always - 18 (Lifetime Min/Max 18/18) Mar 16 07:30:17 Tower preclear_disk-diff[14200]: --- Mar 16 07:30:17 Tower preclear_disk-diff[14200]: > 190 Airflow_Temperature_Cel 0x0022 079 076 000 Old_age Always - 21 (Lifetime Min/Max 18/22) Mar 16 07:30:17 Tower preclear_disk-diff[14200]: 78c78 Mar 16 07:30:17 Tower preclear_disk-diff[14200]: < 201 Soft_Read_Error_Rate 0x000a 253 253 000 Old_age Always - 0 Mar 16 07:30:17 Tower preclear_disk-diff[14200]: --- Mar 16 07:30:17 Tower preclear_disk-diff[14200]: > 201 Soft_Read_Error_Rate 0x000a 100 100 000 Old_age Always - 0 Mar 16 07:30:17 Tower preclear_disk-diff[14200]: ============================================================================
-
Ok, memtest has ended, i got the following message. "*****Pass complete, no errors, press Esc to exit*****" Edit: Ok, so I tried changing SATA cables to see if it would work, but still didn't. I woke up this morning and the process had stopped at 20-someting %. Here is the syslog attached, hope some of you guys can help me figure out what's going on. Weird thing is, it doesn't seem the syslog is complete, as I started the process at around 1AM but I couldn't find any log with that time stamp. Cheers! PS: It seems the forum doesn't accept rar files. Please remove the ".zip" part. syslog-20100315-084710.rar.zip
-
I belive I had the latest version because I installed it on January and I believe no new version has come out since. I re-installed preclear_disk.sh anyway, just in case. I'm running a memtest right now, I'll tell you how it turned out. Two of those 4 discs I added recently are connected directly in the mobo, and the other two are connected to a Supermicro 8port PCI-X card. Since all the 4 drives gave me those errors at first, I thought it wouldn't be from the sata card. The second time I ran the preclear script, 3 drives came out "fine" (those errors that I still don't know what are, are still there, but the disks were precleared). The only disk giving me a headache is this one that won't preclear past 11%. I'll tell you how the memtest went and I'll also post a syslog once I can.
-
Ok, so I did what you suggested,prostuff1. I had already re-ran preclear on that drive that I took the printscreen with, so I did it again with the other 3 drives. 2 of them also gave those errors, but I just ignored them. The last one, however, isn't "pre-clearing"... I've already repeated the process 3 times but it just gets to 11% of the 1st step and then it doesn't do anything else, it just stays there... Time increases, but it just goes on and on without reading the drive... Any ideas?
-
Hey everyone! I have at the moment 4 discs on my array and I just added 4 more (Samsung green 1.5TB disks) last week to grow the array. After the disks were installed, I ran simultaneously preclear_disk on those disks and I got errors on every disk. I thought that was very strange, so I re-ran the 1st disk with pre-clear to see what would come up. I took 2 pictures of the errors I got on the 2nd run (I don't have any of the first run, sorry, but there were more errors does preclear keep a log file somewhere?) Are these errors that I should be concerned about or can I add the drives to the array? What I thought was strange was that each and every one of the new disks had errors... This didn't happened to me with the first 4 disks (those are WD GReen).
-
Thank you for all your help guys If I have some more questions, I'll definitely ask hehe
-
Thank you for your answers, Joe L. I do not live in the US, but I'll definitely check where I can buy Corsair power supplies here! one doubt here... Do you mean 3watts of heat when spinning or when when idle? 'Cause I just checked a post in this thread(I had not seen it yet): http://lime-technology.com/forum/index.php?topic=4682.0 and the second post says: "The hard disks use about 3-4W idle, so add another 15W for 5 drives." I'm kind of "scared" now, because if it's 3-4W just when in idle, how much would it be when spinning?
-
Hi everyone! First of all, it's a great pleasure to be around what appears to be a great and helpful community Well, I'm not exactly an hardware kind-of-guy, I do have some (little) experience, but would like you input in several questions and doubts that I have regarding both hardware and software. I'm wanting to build an unRAID server HARDWARE: I have a Desktop PC that I bought 1-and-a-half year ago, and I'd like to use most of it's hardware. I'll keep my ASUS P5NT WS motherboard as it has lots of slots for expansion 6 SATA PORTS 3 x PCIe x16 slot 2 x PCIe x1 slot 1 x PCI 2.2 1 x PCI-X slot I've got 2GB of RAM and a Core2Duo running at 3.0Ghz, so I'll keep that too. I have doubts though, regarding Power Supply (and HDDs). I want to build a future-proof unRAID server and I already have lots of content I'd like to put there. For starters, I'd just run the server with 4 or 6 drives, but I want to make sure I can add the maximum HDDs possible. I realize that most of you guys here have less than 16 drivers but I'd like to know your opinions about having a server with 21 drives (the maximum unRAID supports, I believe). I know that write speeds and parity checks will get slower due to bus speed, I don't really mind about that, I just want to make sure it doesn't damage the drives. Also, I don't know which power source I should get as I can't find how many Watts the system would be consuming with all drives spinned up and as I said, I don't want to damage anything. I'm also a bit torn with the case I should pick... I don't have many (cheap) options for 16+ drives, the best I could find is the X-Case RM 420 (clone of the Norco?) for 410€ - allows 20 hot-swappable drivers LianLi Cube for 286.60€ + (five or six) Coolermaster 4-in-3 Stackers for 22.90€ each (this would allow 24 drivers max). The price is basically the same, all things considered, I have just to figure out if both have good airflow and fans are silent... SOFTWARE: - I realize most of you guys is using the latest beta version. Normally, I wouldn't use a beta release to trust my data, but it appears to be pretty stable. Shall I go for the beta, or stick to the latest stable release? - I believe I read that there is a add-on (script?) that allows the server to be safelly powered-down with the power-down button in the case, instead of having to enter the web-interface? I looked a little bit but couldn't find it. Well, I guess this is it guys! I hope you can help me with my questions, I'm impaciently waiting for christmas holidays to build my server hehehe