November 18, 201015 yr Hello, Not sure if I should be posting this in the hardware section (or somewhere else), but here it is. I am up to 7 disks now in my first build, including a cache drive (would be 8 but one of my drives just gives me nothing but problems immediately upon boot... but that's another story). I have been used to seeing the HDIO_GET_IDENTITY items in the syslog during my preclears, as it is my understanding that this is an issue with unmounted drives on the SASLP card. However, even though I only have 3 mounted drives on the card, and the cache is on the on-board SATA, I am continuing to get the regular HDIO_GET_IDENTITY errors. I am using unRAID 4.5.6 and the most recent version of unMENU. Also using packages such as unraid_notify, apcupsd, cleanup script, mail and ssmtp, monthly parity check, etc... nothing unusual. One item I have noticed and have no idea if it's normal is that a partition of the cache drive shows up under the unprotected disks area in unMENU. I did not do any special partitioning on this drive, however. Could this be the reason? Any insight would be great! Thanks so much! syslog-2010-11-18.txt
November 18, 201015 yr It is normal for the cache drive to show in the un-protected drives area of unMENU. It is NOT protected by parity. It does have one partition, exactly as shown. The first (and only) partition is shown mounted as the cache drive (as /dev/sdh1) , but the "device" representing the entire drive is still reported in the un-protected area (as /dev/sdh) As far as the error messages in the syslog, they are just a side effect of certain attempted commands to the drive not supported by the driver. You can ignore them. (The hdparm command attempts to issue those commands to learn the spin-up status of the drive. ) Joe L.
November 19, 201015 yr Author Perhaps you can give me a sanity check, Joe? Maybe I'm overly worried about this, but bear with me... I seem to be getting two of these HDIO_GET_IDENTITY errors at a time... spaced out about 5 minutes apart. After some minor investigation (because I don't know how to tell from the syslog alone), I think its from two of my old Drobo WD20EARS drives. I have another 3 WD20EARS drives in use, but those are on the on-board SATA. I checked the SMART status of these drives, and noticed an overly high raw number for load cycle count (or at least what I interpret it to be high). In the 10 minutes I was looking at all the smart statuses, I ran it again on one of the drives and it seemed to have increased by 2. So could this be a problem of the heads being parked, started up again when the HDIO_GET_IDENTITY command fails, then parking again? 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 166 159 021 Pre-fail Always - 8683 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1030 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 097 097 000 Old_age Always - 2421 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 - 312 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 9 193 Load_Cycle_Count 0x0032 179 179 000 Old_age Always - 63653 194 Temperature_Celsius 0x0022 124 106 000 Old_age Always - 28 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 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 Perhaps the reason I'm seeing a problem with two of my drives is because they are an earlier revision? Maybe I just need to go ahead and RMA them to be safe. I have one I'm going to send back next week anyway. Or should I just stop over analyzing? Edited: Eh, I'm late to the party. Guess there's been plenty of discussion here and on the interwebs about LCC and potentially using wdidle. Probably unrelated issues I'm experiencing. Edited2: Just because I think there are plenty of people using unRAID with WD Green drives, take a look at this: http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=5357 I am still not yet familiar enough with *nix to do anything other than running wdidle on my drives, but this does basically state that Linux systems especially cause these drives to "wake up" more frequently than normal due to logging and lack of support for low power drives.
Archived
This topic is now archived and is closed to further replies.