January 13, 201115 yr I swapped in a new motherboard tonight, an Asus P7H57D-V and after bring unraid back online everything seemed to be working ok. After about an hour and a few GB written to the cache drive I started getting scary error messages while trying to read some data over the network. The drive it is saying is having the errors is my cache drive, just pre-cleared a week ago and so far it has been working fine. All I can think is that it was because I plugged it into the Sata3 port on my motherboard instead of the Sata2 port. Is this known to cause problems? I know it won't offer me any speed advantage, I actually used it only because it resulted in cleaner routing of cables but now I am not sure if I should ever use those two ports or if I should consider them useless with unraid. Has anyone seen this before? FYI, for now I moved my parity and cache drives off of the Sata3 ports and onto the same Sata2 ports my data drives are on. I had to manually line the drives back up in devices (why can't it do that automatically, seems so simple, am I missing something?) and when I brought unraid back up it did not start right away. Instead it says I have a new parity drive which I don't, it's the same old drive but I went ahead and selected start the array and recheck parity so it is currently running a parity check. Jan 12 19:56:31 Tower kernel: end_request: I/O error, dev sde, sector 879034615 (Errors) Jan 12 19:56:31 Tower kernel: Buffer I/O error on device sde1, logical block 109879319 (Errors) Jan 12 19:56:31 Tower kernel: lost page write due to I/O error on sde1 (Errors) Jan 12 19:56:31 Tower kernel: sd 7:0:0:0: [sde] Unhandled error code (Errors) Jan 12 19:56:31 Tower kernel: sd 7:0:0:0: [sde] Result: hostbyte=0x04 driverbyte=0x00 (System) Jan 12 19:56:31 Tower kernel: sd 7:0:0:0: [sde] CDB: cdb[0]=0x28: 28 00 11 54 00 57 00 00 08 00 (Drive related) Jan 12 19:56:31 Tower kernel: end_request: I/O error, dev sde, sector 290717783 (Errors) Jan 12 19:56:31 Tower kernel: REISERFS error (device sde1): zam-7001 reiserfs_find_entry: io error (Errors) Jan 12 19:56:31 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Jan 12 19:56:31 Tower last message repeated 3 times Jan 12 19:56:32 Tower kernel: sd 7:0:0:0: [sde] Unhandled error code (Errors) Jan 12 19:56:32 Tower kernel: sd 7:0:0:0: [sde] Result: hostbyte=0x04 driverbyte=0x00 (System) Jan 12 19:56:32 Tower kernel: sd 7:0:0:0: [sde] CDB: cdb[0]=0x28: 28 00 11 54 00 57 00 00 08 00 (Drive related) Jan 12 19:56:32 Tower kernel: end_request: I/O error, dev sde, sector 290717783 (Errors) Jan 12 19:56:32 Tower kernel: REISERFS error (device sde1): zam-7001 reiserfs_find_entry: io error (Errors)
January 13, 201115 yr Please take a look at this sticky for some more information we need from you to be able to help more. You full system specs (case and all) would be very helpful also. From the very small snippet of the syslog it would appear that the drive is having communications issues of a sort. I usually see the Buffer I/O error on device sde1, logical block 109879319 errors when I start to get a lot of reallocated sectors happening. Please get a smart report for the drive and post it also.
January 13, 201115 yr Author I am on unRaid 4.6 (latest stable build). I will do a smart test today and post the results. After I changed the hard drives from the sata3 ports to the sata2 ports the issue appears to have cleared up so there are no messages in my syslog, is it worth posting anyway? I can try using the sata3 ports again tonight but this time I may just start with one drive at a time (either parity or cache). I will post an updated syslog once I am able to replicate the results. Are there any known sata combinations I should watch out for? I was assuming sata3 and sata 2 drives/cables/ports were all interchangeable and would just communicate at the speed of the lowest present device but maybe I was wrong there?
January 13, 201115 yr Author So many options for a smart report. Tried smart history in unMenu but that doesn't work, says I need php and a smart package installed but I don't see then on the packages page. Alternatively it looks like there are about a zillion command line options to run smart tests with. I also found this in unMenu, under the sm link, is this what I should be posting? smartctl -a -d ata /dev/sdd (cache) smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Hitachi Deskstar T7K500 Device Model: Hitachi HDT725050VLA360 Serial Number: VFH461R4D6KGBH Firmware Version: V56OA7EA User Capacity: 500,107,862,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: ATA/ATAPI-7 T13 1532D revision 1 Local Time is: Thu Jan 13 07:47:35 2011 PST 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: (8389) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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: ( 140) minutes. SCT capabilities: (0x003f) SCT Status 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 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0 3 Spin_Up_Time 0x0007 106 106 024 Pre-fail Always - 474 (Average 468) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 436 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 1 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 100 100 020 Pre-fail Offline - 0 9 Power_On_Hours 0x0012 098 098 000 Old_age Always - 16723 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 37 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 1131 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 1131 194 Temperature_Celsius 0x0002 187 187 000 Old_age Always - 32 (Lifetime Min/Max 19/51) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 1 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 253 000 Old_age Always - 0 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% 9135 - 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.
January 13, 201115 yr That is the SMART report. It shows you have had 1 re-allocated sector. It already was re-allocated, so you are OK as long as the number of re-allocated sectors does not continue to increase rapidly. Now that you know how to get the report you can monitor it every month or so. Joe L.
January 13, 201115 yr Author When this happened the array became unusable, is this expected behavior? It said it was online but if I tried to read any files from my cache drive (I didn't try files that weren't on the cache drive) they just errored out, I wish I had written the error down, I think it said something about invalid symlink or some other error that made it sound like unRaid could not actually find the file on the drive. I'll take better notes next time I try it.
January 15, 201115 yr Author I'm calling this solved as I can't reproduce it. I did update the bios on my motherboard before trying to use the Sata3 ports and now it has been humming along fine for 24 hours and a few GB of data moved about on both the cache drive and main array.
Archived
This topic is now archived and is closed to further replies.