Extremely long boot time

[Virginio Miranda]

GSmartcontrol isn't in the 'stardard' Ubuntu Repositories (it's third-party ?).

Yes. It is. Discover or line command.

I launched it. Easy to read. Curious though, it reports BB (0x000A) as 100 because the Raw Values is shown as 000000000000. So it appears that QDiskinfo isn't reading the current stored values for the Smart Self-test I last ran.

Or smartclt on line command is not reading the correct raw values. QDiskinfo is very accuratte. If Qdiskinfo is reading 000000000000 it's mean the Reported Uncorrect Raw Number " is 0. Like we see, the ID 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always is equal a 0 and ID 197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always is equal a 0 too, so, the most logical thing would be ID 187 Reported Uncorrect Raw Number " as a 0 too.

Look at the color ( green or yelow ) on " Reported_Uncorrect " ID. If it is green, Qdiskinfo is interpreting this ID as a normal. And check at the color off the Health Status.

[Virginio Miranda]

Snowhog

Let's make a sure about the error on the hard disk.

Download GSmartcontrol. Open the program. Click twice on the problematic hard drive. Click View Output.

Search for SMART Extended Comprehensive Error Log Version. Look for the line that begin with Error bellow that. Is it there?

If negative case, there are no " Reported_Uncorrect " errors.

If yes, look at the number next to the ERROR . It shows the error , when and how it occurred. Some lines bellow shows the type of the error like " Error: UNC at LBA: XXXXXXX ". UNC means Reported_Uncorrect " errors . The XXXXXX show the large block address the error occurred.

Back the the line that begins ERRORS, there is a number. This number is a Raw Value for " Reported_Uncorrect " ID 187. Next to them is the number of hour it occurrs. Now check ID 9 Power_On_Hours and compare to this error.

I will give you one example with ones of my drives, a seagate barracuda drive ( There are a lot of UNC error inside there )

1 Raw_Read_Error_Rate POSR-- 105 073 006 - 0/130740899
3 Spin_Up_Time PO---- 092 091 000 - 0
4 Start_Stop_Count -O--CK 097 097 020 - 3396
5 Reallocated_Sector_Ct PO--CK 093 093 010 - 8912
7 Seek_Error_Rate POSR-- 073 060 030 - 0/24185846
9 Power_On_Hours -O--CK 043 043 000 - 50801
10 Spin_Retry_Count PO--C- 100 100 097 - 0
12 Power_Cycle_Count -O--CK 097 097 020 - 3129
183 Runtime_Bad_Block -O--CK 099 099 000 - 1
184 End-to-End_Error -O--CK 100 100 099 - 0
187 Reported_Uncorrect -O--CK 001 001 000 - 64205
188 Command_Timeout -O--CK 100 098 000 - 0 1 30
189 High_Fly_Writes -O-RCK 001 001 000 - 1182
190 Airflow_Temperature_Cel -O---K 059 052 045 - 41 (Min/Max 37/42)
191 G-Sense_Error_Rate -O--CK 100 100 000 - 0
192 Power-Off_Retract_Count -O--CK 100 100 000 - 308
193 Load_Cycle_Count -O--CK 084 084 000 - 32954
194 Temperature_Celsius -O---K 041 048 000 - 41 (0 15 0 0 0)
197 Current_Pending_Sector -O--C- 089 089 000 - 1920
198 Offline_Uncorrectable ----C- 089 089 000 - 1920
199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 839
240 Head_Flying_Hours ------ 100 253 000 - 48498h+06m+30.692s
241 Total_LBAs_Written ------ 100 253 000 - 23629102192
242 Total_LBAs_Read ------ 100 253 000 - 35192655078

Error 64203 [2] occurred at disk power-on lifetime: 50727 hours (2113 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 53 00 00 00 00 00 8b 11 88 00 00 Error: UNC at LBA = 0x008b1188 = 9113992

Error 64202 [1] occurred at disk power-on lifetime: 50475 hours (2103 days + 3 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 53 00 00 00 00 00 8b 11 88 00 00 Error: UNC at LBA = 0x008b1188 = 9113992

Error 64201 [0] occurred at disk power-on lifetime: 50353 hours (2098 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 53 00 00 00 00 00 8b 11 88 00 00 Error: UNC at LBA = 0x008b1188 = 9113992

and so on ( a lot of them )

Analyzing the datas we can see that the errors happens in 50353, 50475, 50727 hours.....and so on. The Hard Disk is presented in this moment with ID 9 Power_On_Hours -O--CK 043 043 000 - 50801 ( 50801 hours ).

The last one error is at 50727 hour, so this errors occurs a 74 hour before the ID 9 raw value. If we follow the others numbers there is no difficult to conclude the HD is dying, because beside that numbers, we can see ID 197 Current_Pending_Sector -O--C- 089 089 000 - 1920, ID 198 Offline_Uncorrectable ----C- 089 089 000 - 1920, and ID 5 Reallocated_Sector_Ct PO--CK 093 093 010 - 8912 ( 8912 sectors Reallocated ). Definitely the drive has a serious problem. ( No surprise for me because i have been following along this drive )

Now, you have a condition to take a decision what to do or when to do if it is the case.

One point: The problem itself does not mean the end for the drive. You can backup your datas and write zeros in entire HD ( dd=0 ) and check again with GSmartcontrol if the problem disappear. Sometimes it can back again after a few days or months and in this case it is better to send the drive to a trash.

[Snowhog]

Search for SMART Extended Comprehensive Error Log Version. Look for the line that begin with Error bellow that. Is it there?

If negative case, there are no " Reported_Uncorrect " errors.

When I click on the Error Log tab, the log contains no entries.

[Virginio Miranda]

When I click on the Error Log tab, the log contains no entries.

So, the QDiskinfo is right. The raw value for ID 187 Reported_Uncorrect is 0. Your Hitachi Travelstar drive is good and has no problem at all. The culprit for the extremely long boot time is another thing. Sorry, i cant help you on it. Hope you find the real problem.

[Snowhog]

Thanks!