HDD doesn't mount

Mikhail Weiss · 03-03-2017, 01:05 PM

Hi.

New guy with a curious problem. I ran Ubuntu 10.04 for years on a 1TB Samsung internal hard drive and it quit booting consistently before finally not booting at all. Trying to boot from it generates the following:

error: unknown filesystem.
grub rescue> _

I ran GSmartControl on it and it produced the report below. Naturally, I am bewildered at this output. The report says the overall health assessment was passed, but I still cannot boot from the HDD. "Passed," however, gives me hope that I can fix the boot problem, or recover data, but I don't know how to do either one. Thus my question: how do I fix the problem (can't boot) or at least recover the data?

Your assistance will be greatly appreciated. Though I'm not completely new to Linux, I am almost completely nontechnical.

Best regards,
Mikhail Weiss

--- start report ---

smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-21-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: SAMSUNG SpinPoint F1 DT
Device Model: SAMSUNG HD103UJ
Serial Number: S13PJ1CS101047
LU WWN Device Id: 5 0000f0 000d6cc62
Firmware Version: 1AA01113
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA/ATAPI-7, ATA8-ACS T13/1699-D revision 3b
Local Time is: Fri Mar 3 05:16:13 2017 CST
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: ( 116) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: (11560) 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: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 194) minutes.
Conveyance self-test routine
recommended polling time: ( 21) minutes.
SCT capabilities: (0x003f) SCT Status supported.
SCT Error Recovery Control 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 0x000f 100 089 051 Pre-fail Always - 77
3 Spin_Up_Time 0x0007 075 075 011 Pre-fail Always - 8200
4 Start_Stop_Count 0x0032 097 097 000 Old_age Always - 2816
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 100 100 051 Pre-fail Always - 0
8 Seek_Time_Performance 0x0025 100 100 015 Pre-fail Offline - 9622
9 Power_On_Hours 0x0032 097 097 000 Old_age Always - 15150
10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 0
11 Calibration_Retry_Count 0x0012 100 100 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 097 097 000 Old_age Always - 2814
13 Read_Soft_Error_Rate 0x000e 100 089 000 Old_age Always - 77
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 1545
184 End-to-End_Error 0x0033 001 001 000 Pre-fail Always - 975
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 307
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 073 069 000 Old_age Always - 27 (Min/Max 24/27)
194 Temperature_Celsius 0x0022 074 068 000 Old_age Always - 26 (Min/Max 24/28)
195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 961
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 1
199 UDMA_CRC_Error_Count 0x003e 099 097 000 Old_age Always - 1963
200 Multi_Zone_Error_Rate 0x000a 100 099 000 Old_age Always - 12
201 Soft_Read_Error_Rate 0x000a 100 100 000 Old_age Always - 0

SMART Error Log Version: 1
ATA Error Count: 4
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

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

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
00 d0 01 08 08 00 e0 1 sectors at LBA = 0x00000808 = 2056

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 02 02 08 00 e0 00 00:07:51.570 READ DMA
c8 00 01 00 00 00 e0 00 00:07:51.230 READ DMA
ec 00 00 00 00 00 a0 00 00:07:51.220 IDENTIFY DEVICE
00 00 01 01 00 00 a0 00 00:07:51.070 NOP [Abort queued commands]
00 00 01 01 00 00 a0 ff 00:07:50.480 NOP [Abort queued commands]

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

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
00 d0 01 08 08 00 e0 1 sectors at LBA = 0x00000808 = 2056

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 02 02 08 00 e0 00 00:00:09.370 READ DMA
c8 00 01 00 00 00 e0 00 00:00:09.030 READ DMA
ec 00 00 00 00 00 a0 00 00:00:09.020 IDENTIFY DEVICE
00 00 01 01 00 00 a0 00 00:00:08.880 NOP [Abort queued commands]
00 00 01 01 00 00 a0 ff 00:00:08.300 NOP [Abort queued commands]

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

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
00 d0 01 08 08 00 e0 1 sectors at LBA = 0x00000808 = 2056

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 02 02 08 00 e0 00 00:00:08.410 READ DMA
c8 00 01 00 00 00 e0 00 00:00:08.070 READ DMA
ec 00 00 00 00 00 a0 00 00:00:08.060 IDENTIFY DEVICE
00 00 01 01 00 00 a0 00 00:00:07.910 NOP [Abort queued commands]
00 00 01 01 00 00 a0 ff 00:00:07.320 NOP [Abort queued commands]

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

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
00 d0 01 08 08 00 e0 1 sectors at LBA = 0x00000808 = 2056

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 02 02 08 00 e0 00 00:00:09.760 READ DMA
c8 00 01 00 00 00 e0 00 00:00:09.410 READ DMA
ec 00 00 00 00 00 a0 00 00:00:09.400 IDENTIFY DEVICE
00 00 01 01 00 00 a0 00 00:00:09.250 NOP [Abort queued commands]
00 00 01 01 00 00 a0 ff 00:00:08.670 NOP [Abort queued commands]

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed: read failure 40% 15150 920979223
# 2 Short offline Completed without error 00% 15148 -
# 3 Short offline Completed without error 00% 15137 -

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.

--- end report ---

jefro · 03-03-2017, 03:36 PM

Hello and welcome to LQ.

I think I'd see if Testdisk could get any info by using some live media.

Pretty sure I'd attempt to try this in a known good system with this suspect drive to rule out system.

syg00 · 03-03-2017, 03:50 PM

Quote:

Originally Posted by Mikhail Weiss

New guy with a curious problem. I ran Ubuntu 10.04 for years on a 1TB Samsung internal hard drive and it quit booting consistently before finally not booting at all.

Not curious at all. You run an out-of-support system for years with apparently no backups, and you're surprised you have hardware failures ?.

Quote:

I ran GSmartControl on it and it produced the report below.

How - are we to assume you have access to, and know how to use a liveCD ?.

When posting output use [code] tags so we can read it - much more likely to get people interested in helping you. Like so ...

Code:

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   100   089   051    Pre-fail  Always       -       77
  3 Spin_Up_Time            0x0007   075   075   011    Pre-fail  Always       -       8200
  4 Start_Stop_Count        0x0032   097   097   000    Old_age   Always       -       2816
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   100   100   051    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0025   100   100   015    Pre-fail  Offline      -       9622
  9 Power_On_Hours          0x0032   097   097   000    Old_age   Always       -       15150
 10 Spin_Retry_Count        0x0033   100   100   051    Pre-fail  Always       -       0
 11 Calibration_Retry_Count 0x0012   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   097   097   000    Old_age   Always       -       2814
 13 Read_Soft_Error_Rate    0x000e   100   089   000    Old_age   Always       -       77
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       1545
184 End-to-End_Error        0x0033   001   001   000    Pre-fail  Always       -       975
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       307
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   073   069   000    Old_age   Always       -       27 (Min/Max 24/27)
194 Temperature_Celsius     0x0022   074   068   000    Old_age   Always       -       26 (Min/Max 24/28)
195 Hardware_ECC_Recovered  0x001a   100   100   000    Old_age   Always       -       961
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       1
199 UDMA_CRC_Error_Count    0x003e   099   097   000    Old_age   Always       -       1963
200 Multi_Zone_Error_Rate   0x000a   100   099   000    Old_age   Always       -       12
201 Soft_Read_Error_Rate    0x000a   100   100   000    Old_age   Always       -       0

rknichols · 03-03-2017, 05:18 PM

It's interesting that all of those errors are reported to have occurred at "0 hours" in the life of the drive. Either the drive is not reporting the timestamp properly or those errors are not relevant to what is happening now. It would be interesting to see the report after "smartctl -t long" on the drive. If that error is still there, the test should fail immediately and you should see the result without having to wait the 3+ hours (194 minutes).

OOPS, now I see down at the bottom of the report that you did run that test. Yes, you have a failing drive. You don't know how many bad sectors there might be since the test stops on the first one. The Bad Block HOWTO has some techniques for making repairs, but that whole procedure needs to be done one sector at a time. It might be best to let "dd if=/dev/sda of=/dev/null conv=noerror seek=920979223" run to see how many subsequent errors there might be.