On Thu, 2007-04-12 at 13:28 -0400, Gene Heskett wrote: > Greetings; > > I've been through my own personal hell the last 18 hours. First, I noted through a smartctl report that my hda was approaching the end of its life, the seek errors were up into the 300 million range, the the ECC errors wasn't far behind it. > > So I started a dd if=/dev/hda of=/dev/hdd which cloned that 160GB drive to a 200GB drive. > > While that was going on, verizon decided it was time I changed my password and disconnected me. > > After the clone job, and re-arranging drives, removeing the old hda, moving the clone hdd to > its position both in the machine and on the cable, then putting a new 320GB in as hdd. It > wouldn't boot, mounting /boot and then FAIL without a reason. > > So I got out the zod livedvd and booted it, doing the setup on hdd, but apparently I'd forgotten > the order, so that was a three times around the loop deal. Then, since I now had no partition > for the last 40GB on hda, I fired up fdisk and added that. The LVM didn't like that, and > steadfastly refused to let me modify /dev/VolumeGroupyaddayadda in any way to fix it. > > Several hours and many reboot attempts later it finally did let be run an e2fsck on it, which > promptly (several hours at that) 'fixed' a bunch of stuff, and when it was done, about half > of my kmail setup and mailboxes were toast. I finally got all that sorted I believe but 2 > questions remain. > > 1. How can I add this extra 40GB to that VolGroup now mounted on / > > 2. This brand new 320GB maxtor is acting a lot like the old 160GB seagate was. > > from a smartctl -a /dev/hda, the old 200GB maxtor: > 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 200 200 051 Pre-fail Always - 0 > 3 Spin_Up_Time 0x0007 125 124 021 Pre-fail Always - 4250 > 4 Start_Stop_Count 0x0032 100 100 040 Old_age Always - 91 > 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 > 7 Seek_Error_Rate 0x000b 100 253 051 Pre-fail Always - 0 > 9 Power_On_Hours 0x0032 072 072 000 Old_age Always - 20862 > 10 Spin_Retry_Count 0x0013 100 253 051 Pre-fail Always - 0 > 11 Calibration_Retry_Count 0x0013 100 253 051 Pre-fail Always - 0 > 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 88 > 194 Temperature_Celsius 0x0022 109 253 000 Old_age Always - 41 > 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 > 197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 0 > 198 Offline_Uncorrectable 0x0012 200 200 000 Old_age Always - 0 > 199 UDMA_CRC_Error_Count 0x000a 200 253 000 Old_age Always - 0 > 200 Multi_Zone_Error_Rate 0x0009 200 155 051 Pre-fail Offline - 0 > > Note then poweron hours, over 20K > > Now, from this new 320GB drive: > 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 100 006 Pre-fail Always - 142787210 > 3 Spin_Up_Time 0x0003 097 097 000 Pre-fail Always - 0 > 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 3 > 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 > 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 373173 > 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 9 > 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 > 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 5 > 187 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 > 189 Unknown_Attribute 0x003a 100 100 000 Old_age Always - 0 > 190 Unknown_Attribute 0x0022 059 059 045 Old_age Always - 690290729 > 194 Temperature_Celsius 0x0022 041 041 000 Old_age Always - 41 (Lifetime Min/Max 0/31) > 195 Hardware_ECC_Recovered 0x001a 062 062 000 Old_age Always - 184671713 > 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 > 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0 > 202 TA_Increase_Count 0x0032 100 253 000 Old_age Always - 0 > > Note Poweron hours, 9 > > And both the #7 and #195 errors are incrementing at several per second rates. > > I can't believe this drive won't die shortly, or am I barking up the wrong tree > on both the old hda, and this new hdd? First thing, check your power supply. I'll bet it's dying a slow death. Weird seek errors and such on a new drive is a pretty good indication that the 12V line is getting weak. ---------------------------------------------------------------------- - Rick Stevens, Principal Engineer rstevens@xxxxxxxxxxxx - - VitalStream, Inc. http://www.vitalstream.com - - - - If you can't beat your computer at chess...try kickboxing! - ----------------------------------------------------------------------
