March 8, 200818 yr Hey guys, a few weeks ago my unRAID server had 10 Samsung 500GB harddrives and was running with an older unRAID build (was it 4.1? not sure) and everything worked just fine. Now I'm in the process of replacing all those Samsungs with Western Digital 1TB harddisks (RAID edition). Also I've upgraded to 4.2.1. Have 7 of those WDs now in the server and only 3 Samsungs left. The unRAID server is still more or less working. However, I'm having this very nasty annoying problem now: When I copy big files (10GB+) from my XPSP2 machine to the unRAID server, often the copy operation aborts after a while. When doing the copy operation in the Explorer, the copying runs for a while, then suddenly a question like "shall I overwrite the file XYZ on the unRAID server? it's already there" appears? The file XYZ was not on the unRAID server before. So it's a bit strange. Anyway, when copying the file with my self programmed copy routines, I can see that the "MoveFileW" win32 API fails at some point with the error code "the share is not available, anymore" (translated from German, not sure how the exact words are in English). Obviously this is a really bad problem cause usually I'm copying large amounts of data to the unRAID server at night. In the morning I expect the whole copy operation to have succeeded. But since I upgraded to the 1TB discs and to version 4.2.1, copy operation don't work reliably, anymore. Also I have the impression that overall reaction of the unRAID shares got really bad. When I browse through the directories I often have to wait several seconds before something happens. I'm currently still copying the files to the "disk" shares. Have enabled the user shares, but not set them up fully yet. Here's my syslog: http://madshi.net/syslog The last time the problem occurred was March 8th, around 16:00. The syslog doesn't contain any information when the problem occurs...
April 20, 200917 yr I recently have encountered this error as well. Copying from an XP machine, it seemed to occur with only relatively large files (6gb+). However strange enough, it was happening only when writing to a particular Disk (disk1). Worked fine copying the same files copying to another disk. I have had no other issues however (though I will run a smarttest) and can read just fine. The only thing I can think of is that the problematic disk is nearly full (97% full), even though there is space for the files. I'm running the latest Unraid (non-beta). My syslog did not show anything unusual at all. Never had this issue before. Also this is writing to a disk directly and not through a user share (though user shares are enabled). One thing that has changed is that I have changed my router (went from comcast to verizon fios), but the actual networking hardware other than the router (i.e. cables, switches, etc) are the same. I'm running 5x Seagate 1.5tb drives (all with latest firmware). Anyone with any ideas?
April 20, 200917 yr One thing that has changed is that I have changed my router (went from comcast to verizon fios), but the actual networking hardware other than the router (i.e. cables, switches, etc) are the same. I'm running 5x Seagate 1.5tb drives (all with latest firmware). Anyone with any ideas? Attach a copy of your syslog. It may contain clues. Also, get the output of ifconfig eth0 Although not too likely, it can also be the router's firmware... some are far more stable than others when dealing with large amounts of data. I'd expect to see entries in the syslog if it was dropping the connection though. Joe L.
April 20, 200917 yr Thanks Joe, I will do as suggested in a couple of hours during my lunch break. What I don't get is why it would work fine with one disk and not the other.
April 20, 200917 yr Thanks Joe, I will do as suggested in a couple of hours during my lunch break. What I don't get is why it would work fine with one disk and not the other. Perhaps one disk might be experiencing errors, and the other is not? (just a guess) The syslog will give more clues. Joe L.
April 20, 200917 yr Just an FYI. I have seen this twice in recent betas. Both times i was hammering my NAS with uploads. Zero syslog entries that i could see and I cannot replicate the problem on demand.
April 20, 200917 yr Just an FYI. I have seen this twice in recent betas. Both times i was hammering my NAS with uploads. Zero syslog entries that i could see and I cannot replicate the problem on demand. Well to elaborate the machine I was copying FROM was definitely downloading files (torrent and usenet). And I could replicate the issue by simply copying to disk 1 a large file. Worked fine copying to disk 2 with everything else the same. And yes I saw nothing in the syslog but will post it.
April 20, 200917 yr One thing that has changed is that I have changed my router (went from comcast to verizon fios), but the actual networking hardware other than the router (i.e. cables, switches, etc) are the same. I'm running 5x Seagate 1.5tb drives (all with latest firmware). Anyone with any ideas? Attach a copy of your syslog. It may contain clues. Also, get the output of ifconfig eth0 Although not too likely, it can also be the router's firmware... some are far more stable than others when dealing with large amounts of data. I'd expect to see entries in the syslog if it was dropping the connection though. Joe L. So strangely enough I tried copying a large file to disk1 and it worked fine now. The only thing I noticed is that in the syslog when I spun up the drives right before it did give an error message (I think with the parity drive). But I do not see anything else related to the error in failing to copy previously, but hopefully someone who is more familiar with this can check. Attached is the syslog. THanks! Here is the result of ifconfig eth0: root@Tower:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:1e:2a:3f:1c:85 inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:243055622 errors:0 dropped:0 overruns:0 frame:0 TX packets:107229829 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2721233033 (2.5 GiB) TX bytes:2612847326 (2.4 GiB) Interrupt:20 Base address:0xa000
April 20, 200917 yr The 2 timeout error sequences are probably not a problem, perhaps something to monitor, but seem to be just something to live with in SATA communications, to the best of my current understanding. The first one occurred over 6 minutes after the spin up, so does not seem to be related, in my opinion. There is something else of note, not serious, but unusual. NTP is working fine, but having to work much harder than I have ever seen before. It appears to be correcting the time by about 2 seconds every 15 minutes, roughly. That is much more than usual, indicates your clock or clock routines are not calibrated or working correctly. NTP should keep the clock fairly accurate, and there isn't anything else I can advise, but it is something to be aware of.
April 20, 200917 yr The 2 timeout error sequences are probably not a problem, perhaps something to monitor, but seem to be just something to live with in SATA communications, to the best of my current understanding. The first one occurred over 6 minutes after the spin up, so does not seem to be related, in my opinion. There is something else of note, not serious, but unusual. NTP is working fine, but having to work much harder than I have ever seen before. It appears to be correcting the time by about 2 seconds every 15 minutes, roughly. That is much more than usual, indicates your clock or clock routines are not calibrated or working correctly. NTP should keep the clock fairly accurate, and there isn't anything else I can advise, but it is something to be aware of. Thanks RobJ! For the NTP issue, is that even something I can control by any setting? I know I set the location of the server to do handle that in the settings but other than that anything I should do? So any other ideas why the copying worked today and not yesterday? And why wouldn't it work on disk1 but worked on disk2 yesterday? Could it be SATA cable issue, or even a PSU problem (running Antec Earthwatts 440w)? Seems bizarre. The only other thing I noticed is that the disks in general click a fair amount sometimes while copying/spinning up, but it is the Seagate 1.5tbs (all firmware CC1H) so I just chalk it up to that fact. Never had an issue reading anything from the disks (no timeouts or freezes). Only the parity shows 1 reallocated sector and smart history seemed ok to my untrained eye.
April 20, 200917 yr For the NTP issue, is that even something I can control by any setting? I know I set the location of the server to do handle that in the settings but other than that anything I should do? Nope. Your system is currently 'training' NTP as to how much the time is drifting, and after a few days, will be able to automatically keep it very close to accurate. I've made a suggestion elsewhere (bottom of this post), to look for and copy a user's drift file, to preset NTP with a working drift value. You might also want to use the show_ntp script in that post, to view your current drift value, something I'm personally very curious to see! So any other ideas why the copying worked today and not yesterday? And why wouldn't it work on disk1 but worked on disk2 yesterday? Could it be SATA cable issue, or even a PSU problem (running Antec Earthwatts 440w)? Seems bizarre. The only other thing I noticed is that the disks in general click a fair amount sometimes while copying/spinning up, but it is the Seagate 1.5tbs (all firmware CC1H) so I just chalk it up to that fact. Never had an issue reading anything from the disks (no timeouts or freezes). Only the parity shows 1 reallocated sector and smart history seemed ok to my untrained eye. No further ideas. Better SATA cables do seem to help, but I'm not aware of a good way to tell what *is* a better SATA cable, apart from trial-and-error. The marketing claims don't seem trustworthy. Do make sure that ALL cables, both the data and power cables, are firmly seated in their connectors, NOT loose. Your remark ("the disks in general click a fair amount") is somewhat alarming. They should not be clicking, at least not sharp clicks! Someone with first-hand experience with the Seagate 1.5TB drives can better advise on this. I would keep a VERY close eye on their SMART reports.
April 20, 200917 yr For the NTP issue, is that even something I can control by any setting? I know I set the location of the server to do handle that in the settings but other than that anything I should do? Nope. Your system is currently 'training' NTP as to how much the time is drifting, and after a few days, will be able to automatically keep it very close to accurate. I've made a suggestion elsewhere (bottom of this post), to look for and copy a user's drift file, to preset NTP with a working drift value. You might also want to use the show_ntp script in that post, to view your current drift value, something I'm personally very curious to see! So any other ideas why the copying worked today and not yesterday? And why wouldn't it work on disk1 but worked on disk2 yesterday? Could it be SATA cable issue, or even a PSU problem (running Antec Earthwatts 440w)? Seems bizarre. The only other thing I noticed is that the disks in general click a fair amount sometimes while copying/spinning up, but it is the Seagate 1.5tbs (all firmware CC1H) so I just chalk it up to that fact. Never had an issue reading anything from the disks (no timeouts or freezes). Only the parity shows 1 reallocated sector and smart history seemed ok to my untrained eye. No further ideas. Better SATA cables do seem to help, but I'm not aware of a good way to tell what *is* a better SATA cable, apart from trial-and-error. The marketing claims don't seem trustworthy. Do make sure that ALL cables, both the data and power cables, are firmly seated in their connectors, NOT loose. Your remark ("the disks in general click a fair amount") is somewhat alarming. They should not be clicking, at least not sharp clicks! Someone with first-hand experience with the Seagate 1.5TB drives can better advise on this. I would keep a VERY close eye on their SMART reports. I do hear sharp clicks sometimes, though I have not isolated it down to a particular disk. It makes a clicking sound similar to when they click as they spin up. I THINK it mainly occurs during a write operation. It does not do it all the time and definitely not while the disks are spun down. I haven't had any performance issues with these drives at least in terms of reading data from them, and only this one incident in terms of writing to a disk (which seems to be intermittent). I haven't done smart tests on all of them, but in terms of the smart history, only 1 disk shows a reallocated sector count >0 (which is the parity drive, which has a value of 1 and has not changed after 1200+ hours of running).
April 20, 200917 yr Just in case anyone notices anything odd, here is the smart history for the parity drive: === START OF INFORMATION SECTION === Device Model: ST31500341AS Serial Number: 9VS0RX0R Firmware Version: CC1H 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: Mon Apr 20 19:43:24 2009 GMT+4 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: ( 20) The self-test routine was aborted by the host. Total time to complete Offline data collection: ( 617) 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: ( 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 114 099 006 Pre-fail Always - 73553264 3 Spin_Up_Time 0x0003 092 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 162 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 1 7 Seek_Error_Rate 0x000f 066 060 030 Pre-fail Always - 3780972 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1218 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 1 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 19 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Unknown_Attribute 0x0032 100 098 000 Old_age Always - 4295098370 189 High_Fly_Writes 0x003a 023 023 000 Old_age Always - 77 190 Airflow_Temperature_Cel 0x0022 078 061 045 Old_age Always - 22 (Lifetime Min/Max 16/35) 194 Temperature_Celsius 0x0022 022 040 000 Old_age Always - 22 (0 16 0 0) 195 Hardware_ECC_Recovered 0x001a 051 040 000 Old_age Always - 73553264 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 - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 25975962206751 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 3507031342 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 1679046990 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 Aborted by host 40% 1210 - # 2 Short offline Completed without error 00% 681 - # 3 Short offline Completed without error 00% 0 - 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. And for disk1 which was the one that was having trouble copying to the other day: === START OF INFORMATION SECTION === Device Model: ST31500341AS Serial Number: 9VS0T6PX Firmware Version: CC1H 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: Mon Apr 20 19:44:39 2009 GMT+4 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: ( 617) 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: ( 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 120 099 006 Pre-fail Always - 235592370 3 Spin_Up_Time 0x0003 093 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 196 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 063 060 030 Pre-fail Always - 2334032 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1218 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 19 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 089 089 000 Old_age Always - 11 190 Airflow_Temperature_Cel 0x0022 077 055 045 Old_age Always - 23 (Lifetime Min/Max 14/44) 194 Temperature_Celsius 0x0022 023 045 000 Old_age Always - 23 (0 13 0 0) 195 Hardware_ECC_Recovered 0x001a 055 042 000 Old_age Always - 235592370 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 - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 235969798210125 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 3180216708 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 571897357 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% 681 - # 2 Short offline Completed without error 00% 0 - 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.
April 20, 200917 yr For the NTP issue, is that even something I can control by any setting? I know I set the location of the server to do handle that in the settings but other than that anything I should do? Nope. Your system is currently 'training' NTP as to how much the time is drifting, and after a few days, will be able to automatically keep it very close to accurate. I've made a suggestion elsewhere (bottom of this post), to look for and copy a user's drift file, to preset NTP with a working drift value. You might also want to use the show_ntp script in that post, to view your current drift value, something I'm personally very curious to see! So any other ideas why the copying worked today and not yesterday? And why wouldn't it work on disk1 but worked on disk2 yesterday? Could it be SATA cable issue, or even a PSU problem (running Antec Earthwatts 440w)? Seems bizarre. The only other thing I noticed is that the disks in general click a fair amount sometimes while copying/spinning up, but it is the Seagate 1.5tbs (all firmware CC1H) so I just chalk it up to that fact. Never had an issue reading anything from the disks (no timeouts or freezes). Only the parity shows 1 reallocated sector and smart history seemed ok to my untrained eye. No further ideas. Better SATA cables do seem to help, but I'm not aware of a good way to tell what *is* a better SATA cable, apart from trial-and-error. The marketing claims don't seem trustworthy. Do make sure that ALL cables, both the data and power cables, are firmly seated in their connectors, NOT loose. Your remark ("the disks in general click a fair amount") is somewhat alarming. They should not be clicking, at least not sharp clicks! Someone with first-hand experience with the Seagate 1.5TB drives can better advise on this. I would keep a VERY close eye on their SMART reports. Here is the output from your ntpd script: Tower login: root Linux 2.6.27.7-unRAID-Bubba. root@Tower:~# ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== +time.nist.gov .ACTS. 1 u 37 64 17 97.138 108.935 155.473 +mirror 128.118.25.3 3 u 59 64 17 36.063 176.451 131.441 *nonce.prolixium 209.51.161.238 2 u 51 64 17 48.874 94.710 161.312 root@Tower:~# ls -l /etc/ntp/drift -rw-r--r-- 1 root root 8 Apr 19 13:44 /etc/ntp/drift root@Tower:~# cat /etc/ntp/drift 500.000 Also I spun up the disks just now individually and no unusual clicking noises, so perhaps it is only when writing. I will try to observe over the next few days.
April 21, 200917 yr The SMART reports look OK for those 2 drives. It is still possible, but probably unlikely, that the problems and clicking are associated with a different drive, uninvolved with the copies you were making. I would check the SMART reports for the other 3 Seagates, and for the Maxtor cache drive. That drift value is suspiciously clean. Mine have been calculated out to 3 decimals. I have to wonder if it is too early yet for yours to be accurate, or it has been capped at 500, which could be a problem. Check again in a few more days.
April 21, 200917 yr Ok the clicking is back. I was copying files to Disk1, so only Disk1 and Parity were spun up. While copying after a few minutes it clicked about 10-15 times (about one per second) and it seemed like the copying was stalling, then the clicking stopped and the copying continued. It is still copying however so I'll post back if it fails overall. And nothing showing in syslog while the clicking occurred. Any ideas Robj or anyone else? I can't tell which disk is clicking though I suppose I could open it up and listen for it at some point. Thanks in advance.
April 21, 200917 yr Get 2 more SMART reports for those same 2 drives, and let's compare them with the first set.
April 21, 200917 yr Here is the smart report again for the Parity disk: === START OF INFORMATION SECTION === Device Model: ST31500341AS Serial Number: 9VS0RX0R Firmware Version: CC1H 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: Mon Apr 20 20:44:30 2009 GMT+4 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: ( 20) The self-test routine was aborted by the host. Total time to complete Offline data collection: ( 617) 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: ( 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 117 099 006 Pre-fail Always - 125665175 3 Spin_Up_Time 0x0003 092 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 163 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 1 7 Seek_Error_Rate 0x000f 066 060 030 Pre-fail Always - 3819032 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1219 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 1 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 19 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Unknown_Attribute 0x0032 100 098 000 Old_age Always - 4295098370 189 High_Fly_Writes 0x003a 022 022 000 Old_age Always - 78 190 Airflow_Temperature_Cel 0x0022 068 061 045 Old_age Always - 32 (Lifetime Min/Max 16/35) 194 Temperature_Celsius 0x0022 032 040 000 Old_age Always - 32 (0 16 0 0) 195 Hardware_ECC_Recovered 0x001a 053 040 000 Old_age Always - 125665175 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 - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 50976966836768 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 605705889 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 2193286102 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 Aborted by host 40% 1210 - # 2 Short offline Completed without error 00% 681 - # 3 Short offline Completed without error 00% 0 - 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. And for disk1: === START OF INFORMATION SECTION === Device Model: ST31500341AS Serial Number: 9VS0T6PX Firmware Version: CC1H 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: Mon Apr 20 20:45:13 2009 GMT+4 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: ( 617) 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: ( 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 112 099 006 Pre-fail Always - 47251403 3 Spin_Up_Time 0x0003 093 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 196 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 063 060 030 Pre-fail Always - 2381829 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1219 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 19 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 089 089 000 Old_age Always - 11 190 Airflow_Temperature_Cel 0x0022 062 055 045 Old_age Always - 38 (Lifetime Min/Max 14/44) 194 Temperature_Celsius 0x0022 038 045 000 Old_age Always - 38 (0 13 0 0) 195 Hardware_ECC_Recovered 0x001a 054 042 000 Old_age Always - 47251403 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 - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 111321257345614 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 601829831 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 199055959 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% 681 - # 2 Short offline Completed without error 00% 0 - 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. Robj--thanks again so much for your help.
April 21, 200917 yr It finished copying 25gb of files successfully, however near the very end it started clicking again and did so for about 20 clicks. During which time the copying again seemed to stop/slow down. It resumed copying when it stopped clicking. Now copying something onto disk2, it just exhibited about 5 clicks now as well. Here is the smart history for the Parity disk after this occurance: === START OF INFORMATION SECTION === Device Model: ST31500341AS Serial Number: 9VS0RX0R Firmware Version: CC1H 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: Mon Apr 20 21:24:51 2009 GMT+4 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: ( 20) The self-test routine was aborted by the host. Total time to complete Offline data collection: ( 617) 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: ( 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 - 179377311 3 Spin_Up_Time 0x0003 092 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 163 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 1 7 Seek_Error_Rate 0x000f 066 060 030 Pre-fail Always - 3857921 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1220 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 1 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 19 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Unknown_Attribute 0x0032 100 098 000 Old_age Always - 4295098370 189 High_Fly_Writes 0x003a 020 020 000 Old_age Always - 80 190 Airflow_Temperature_Cel 0x0022 066 061 045 Old_age Always - 34 (Lifetime Min/Max 16/35) 194 Temperature_Celsius 0x0022 034 040 000 Old_age Always - 34 (0 16 0 0) 195 Hardware_ECC_Recovered 0x001a 053 040 000 Old_age Always - 179377311 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 - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 30717606101536 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 1285406909 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 3610645376 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 Aborted by host 40% 1210 - # 2 Short offline Completed without error 00% 681 - # 3 Short offline Completed without error 00% 0 - 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.
April 21, 200917 yr Ok this is odd. I spun up the parity disk and tried to run a long smart test. After a bit though I see it has been "Aborted by host". I had made sure to disable drive spin down, and the drive was still spun up. Any ideas? Nothing shows in syslog. I was able to complete a short test on that drive without any errors showing.
April 21, 200917 yr Just to confirm the previous post, I tried doing a long smart test on the parity and after maybe 30 min, it showed a status of Aborted by Host ?!? I tried the same on disk1 and same thing. I then made sure to spin up the particular drive beforehand and also disabled spin-down and same problem. What is going on ? The only thing I can think of is that I had changed the spindown time from 30 min to never, but when I awoke to check on the test all the drives were spun down. Is a reboot needed to make the change stick? I rebooted now to test and re-ran the long test. Ok nevermind for that idea, it now shows aborted by host again.
April 21, 200917 yr Don't think I have heard of something like that before. You can try stopping the array, that should disable the "host" from sending any commands to the drives. And make sure you don't have any addons like SmartHistory running, they could be sending SMART related queries to the drives.
April 21, 200917 yr Don't think I have heard of something like that before. You can try stopping the array, that should disable the "host" from sending any commands to the drives. And make sure you don't have any addons like SmartHistory running, they could be sending SMART related queries to the drives. I am running both BubbaRaid and Unmenu which have Smarthistory I believe (right?). I will also try stopping the array as well before trying. Robj, did you see anything of concern in the smart reports on the parity drive? Also I definitely hear a clicking when copying that is not normal imo. I wll open up the case and try to listen to which drive is doing this tonight. Thanks again for your help.
April 21, 200917 yr Robj, did you see anything of concern in the smart reports on the parity drive? No, I don't see anything I can draw a conclusion from, so far. Almost everything looks relatively normal. This is possibly off-topic, but I could not help noticing one oddity. The SMART attribute 189 (shown here as High_Fly_Writes) appears to be either mis-labeled, or Seagate is using it in a non-standard way. The values for it are behaving like temps, not mechanical counts. VALUE is always equal to (100 - RAW_VALUE), WORST is a copy of VALUE. As they warn you, SMART attribute usage is completely up to the vendor. If it is actually a count of something, then the Parity drive value for High_Fly_Writes has dropped from 100, and is getting lower and lower, possibly worrisome. However, this is NOT considered a Pre-fail item. More research is needed ... Some examples: Parity drive 189 High_Fly_Writes 0x003a 023 023 000 Old_age Always - 77 189 High_Fly_Writes 0x003a 022 022 000 Old_age Always - 78 189 High_Fly_Writes 0x003a 020 020 000 Old_age Always - 80 Disk 1 189 High_Fly_Writes 0x003a 089 089 000 Old_age Always - 11
April 21, 200917 yr Thanks again Robj! Booting into normal Unraid mode (and not BubbaRaid) seemed to fix my issue with running the smartctl tests. It's running the long test now without being aborted. Even if passes, I think I may try to verify that it is the parity drive clicking during copies and RMA that. It definitely does not seem normal when you hear 10-20 clicks in a row while copying.
Archived
This topic is now archived and is closed to further replies.