CaptainSpalding Posted February 7, 2012 Share Posted February 7, 2012 I think this is fubar? smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST31500541AS Serial Number: 6XW00X4C Firmware Version: CC32 User Capacity: 1,500,301,910,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Tue Feb 7 18:30:59 2012 EET 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: ( 684) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x103f) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. 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 118 099 006 Pre-fail Always - 175000213 3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 811 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 15 7 Seek_Error_Rate 0x000f 053 052 030 Pre-fail Always - 236235357556 9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 1875 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 534 183 Runtime_Bad_Block 0x0032 097 097 000 Old_age Always - 3 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 4295032833 189 High_Fly_Writes 0x003a 008 008 000 Old_age Always - 92 190 Airflow_Temperature_Cel 0x0022 075 060 045 Old_age Always - 25 (Lifetime Min/Max 22/25) 194 Temperature_Celsius 0x0022 025 040 000 Old_age Always - 25 (0 17 0 0) 195 Hardware_ECC_Recovered 0x001a 060 040 000 Old_age Always - 175000213 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 200 000 Old_age Always - 12 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 161323266607961 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 3241869519 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 2512840828 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% 550 - 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. Link to comment
lionelhutz Posted February 7, 2012 Share Posted February 7, 2012 I don't see any glaring problem but there are 15 reallocated sectors which means it's not a great drive. If the pending and reallocated sectors don't increase any more then you could likely still use it by keeping an eye on it. If it's RMA'able then it wouldn't be a bad idea to get a new one. Peter Link to comment
WeeboTech Posted February 7, 2012 Share Posted February 7, 2012 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 15 You cannot expect 0 in the lifetime of a drive, however if this grows continually, then you have an impending problem. 9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 1875 Low hours. Good. 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 When this is non-zero your array has a potential problem of this drive going off line and not being able to rebuild a failed drive. 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 When these are non-zero, it means there are bad sectors which cannot be reassigned or corrected. if this grows and continues to grow, the drive needs to reviewed with a SMART long test. # 1 Short offline Completed without error 00% 550 This is good, but set the drive spin down off. Stop the array and/or emhttp. Do a smart -t long test If you don't stop access or stop emhttp from spinning down the drive, the long test will fail. overall the drive is healthy enough to use for the unRAID array. A few reallocated sectors is normal. a few hundred is cause for alarm, over 1000, I would be looking at re-doing the preclear and/or a badblocks test. In fact, I think if I get any pending sectors, Then I plan to do a badblocks test to force reassignment. Link to comment
CaptainSpalding Posted February 7, 2012 Author Share Posted February 7, 2012 Thank you! The reason I'm asking is that the last time I did a parity check the drive had like 11600 errors and the parity check ended prematurely. After that it has had a red dot and there are 41 reads on start up, but 0 writes. All other disks have multiple writes. Link to comment
WeeboTech Posted February 7, 2012 Share Posted February 7, 2012 The smart stats do not show that the drive is in too bad of a state. However, if you received errors on the drive and parity check aborted, the drive may have timed out while it was reallocating sectors. Is this a data drive or a parity drive? Is there allot of data on the drive? Is it new? 550 hours makes me think it's new. If it's new and there is no data on the drive, I would suggest removing from the array and running a badblocks test in destructive write mode. Link to comment
CaptainSpalding Posted February 7, 2012 Author Share Posted February 7, 2012 It's a data drive and even though only 550 hours, that is a lot since I only power up when I wanna watch a movie. Thats like about 20 a month, max. There's 8 gig's available on the drive. Link to comment
WeeboTech Posted February 7, 2012 Share Posted February 7, 2012 It's a data drive and even though only 550 hours, that is a lot since I only power up when I wanna watch a movie. Thats like about 20 a month, max. There's 8 gig's available on the drive. Power on hours is not spin time. It's how long the drive has had power to it. So even in spin down time, power on hours increments. 550 hours is roughly 23 days or so. Drives usually fail early in the life, near the end of the life or if there is a sudden loss of power. (sectors can get scrambled if the heads are near it and there is a drop or surge in current). Link to comment
CaptainSpalding Posted February 20, 2012 Author Share Posted February 20, 2012 I did the smart -t long test, but when the estimated time was reached it didn't do anything? So I just thought I'd try to rebuild it again and see how that works out. It did the data rebuild, all the dots are green. There's about 600G's of free space, but when I'm trying to move a file it says "Not enough memory.." I'm using Windows 7 x64 /w 16G's of RAM. Damn it! When I click ok to that it starts to say that i do not have a permission to move a file... After a reboot of unraid server it first tells again that it is out of memory and then the permission thingy again. Do you know what could cause this? My server specs below. Link to comment
marcusone Posted February 20, 2012 Share Posted February 20, 2012 Unraid saying out of memory or Windows? Sent from my SGH-I727R using Tapatalk Link to comment
Joe L. Posted February 20, 2012 Share Posted February 20, 2012 I did the smart -t long test, but when the estimated time was reached it didn't do anything?Correct. Exactly as normal. You must get a status report to see the results. The request only starts it going. Nothing of the results are ever printed until you request them with a subsequent status report. after the expected time, issue an smartctl -a /dev/sdX command to see the results (and to see if it has finished) So I just thought I'd try to rebuild it again and see how that works out. It did the data rebuild, all the dots are green. There's about 600G's of free space, but when I'm trying to move a file it says "Not enough memory.." I'm using Windows 7 x64 /w 16G's of RAM. Damn it! When I click ok to that it starts to say that i do not have a permission to move a file... After a reboot of unraid server it first tells again that it is out of memory and then the permission thingy again. Do you know what could cause this? My server specs below. post a system log. Link to comment
CaptainSpalding Posted February 20, 2012 Author Share Posted February 20, 2012 Thanks Joe! Here's the syslog. syslog.txt Link to comment
dgaschk Posted February 20, 2012 Share Posted February 20, 2012 disk4 has a file system error and has been mounted read-only. See here: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems Link to comment
CaptainSpalding Posted February 20, 2012 Author Share Posted February 20, 2012 Thanks dgaschk! That worked. I'm now able to move the files to my unraid. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.