HD wont Mount also e2fsck error

[psusi]

Yep, you got two bad sectors so far. Start a self test and see where it finds the first error, then you can try to force the drive to remap the sector:

sudo smartctl -t long /dev/sda
sudo smartctl -l selftest /dev/sda

The first starts the test, which can take quite a while. The second will check on the status. Once it hits the bad sector it should show that it found it when you run the second command. Take note of the number and then:

sudo dd if=/dev/sda of=/dev/null bs=512 iflag=direct count=1 skip=NNNN

Where NNNN is the sector number from the selftest log. That should come back with an IO error if you got it right, confirming that you are trying to read the bad sector. If it does, then zero the sector, which will force the drive to remap the sector to a fresh one if it can't correctly write to the media:

sudo dd if=/dev/zero of=/dev/sda bs=512 oflag=direct count=1 seek=NNNN

Then try the read again and it should work this time. Repeat this until the selftest doesn't find any more bad sectors, then fsck the filesystem and hope it can recover.

[killaray]

Thank god for copy/paste lol, anywho I left my house for the night so ill give this a shot tomorrow... thanx for the help and I'll let u know how it went

[killaray]

Yep, you got two bad sectors so far. Start a self test and see where it finds the first error, then you can try to force the drive to remap the sector:

sudo smartctl -t long /dev/sda
sudo smartctl -l selftest /dev/sda

The first starts the test, which can take quite a while. The second will check on the status. Once it hits the bad sector it should show that it found it when you run the second command. Take note of the number and then:

sudo dd if=/dev/sda of=/dev/null bs=512 iflag=direct count=1 skip=NNNN

Where NNNN is the sector number from the selftest log. That should come back with an IO error if you got it right, confirming that you are trying to read the bad sector. If it does, then zero the sector, which will force the drive to remap the sector to a fresh one if it can't correctly write to the media:

sudo dd if=/dev/zero of=/dev/sda bs=512 oflag=direct count=1 seek=NNNN

Then try the read again and it should work this time. Repeat this until the selftest doesn't find any more bad sectors, then fsck the filesystem and hope it can recover.

first and second command gimme this...

smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/                        

=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Extended self-test routine immediately in off-line mode".                                                                       
Drive command "Execute SMART Extended self-test routine immediately in off-line mode" successful.                                                               
Testing has begun.                                                              
Please wait 154 minutes for test to complete.                                   
Test will complete after Tue Nov 18 17:17:31 2008                               

Use smartctl -X to abort test.

then

smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF READ SMART DATA SECTION ===
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       90%      7871         8284
# 2  Extended offline    Completed: read failure       90%      7871         8284

wuts it mean.. or if u dont wanna explain just wut do i do next? are the LBA the numbers i substitute in for NNNN?

[psusi]

It is pretty self explanatory. The test failed to read sector 8284, so that's what you use for NNNN.

[killaray]

ur such a beautiful person psusi... thank you that worked... lol

[psusi]

Now you might want to check the output of smartctl -a again and look at the relocated sector count. If the sector just got corrupted and the drive was able to rewrite it without a problem, the relocated count should still be 0. If the media is physically damaged and can not be written to, then the drive will have relocated it. If this is the case, you might want to think about getting a new drive because once media defects start, they tend to spread.

[killaray]

Once I get home ill give that a go... thanx again for all ur help

[killaray]

where do u find the number of relocated sectors?

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar Second Generation Serial ATA family
Device Model:     WDC WD5000AAJS-00YFA0                                     
Serial Number:    WD-WCAS82048017                                           
Firmware Version: 12.01C02                                                  
User Capacity:    500,107,862,016 bytes                                     
Device is:        In smartctl database [for details use: -P show]           
ATA Version is:   8                                                         
ATA Standard is:  Exact ATA specification draft version not indicated       
Local Time is:    Thu Nov 20 01:24:17 2008 EST                              
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:  (0x82) Offline data collection activity
                                        was completed without error.    
                                        Auto Offline Data Collection: Enabled.
Self-test execution status:      ( 121) The previous self-test completed having
                                        the read element of the test failed.   
Total time to complete Offline                                                 
data collection:                 (13200) 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:        ( 154) minutes.                                
Conveyance self-test routine                                                    
recommended polling time:        (   5) minutes.                                
SCT capabilities:              (0x303f) 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     0x000f   200   200   051    Pre-fail  Always       -       0                                                                        
  3 Spin_Up_Time            0x0003   176   166   021    Pre-fail  Always       -       6191                                                                     
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       290                                                                      
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0                                                                        
  7 Seek_Error_Rate         0x000e   200   200   051    Old_age   Always       -       0                                                                        
  9 Power_On_Hours          0x0032   090   090   000    Old_age   Always       -       7906                                                                     
 10 Spin_Retry_Count        0x0012   100   100   051    Old_age   Always       -       0                                                                        
 11 Calibration_Retry_Count 0x0012   100   100   051    Old_age   Always       -       0                                                                        
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       190                                                                      
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       554                                                                      
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       667                                                                      
194 Temperature_Celsius     0x0022   108   098   000    Old_age   Always       -       42                                                                       
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   0x0010   200   200   000    Old_age   Offline      -       0                                                                        
199 UDMA_CRC_Error_Count    0x003e   200   192   000    Old_age   Always       -       20                                                                       
200 Multi_Zone_Error_Rate   0x0008   200   200   051    Old_age   Offline      -       0                                                                        

SMART Error Log Version: 1
ATA Error Count: 630 (device log contains only the most recent five errors)
        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 630 occurred at disk power-on lifetime: 7892 hours (328 days + 20 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                              
  -- -- -- -- -- -- --                              
  40 51 00 5c 20 00 e0  Error: UNC at LBA = 0x0000205c = 8284

  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 01 5c 20 00 00 08      20:38:09.043  READ DMA            
  27 00 00 00 00 00 00 08      20:38:09.043  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 00 08      20:38:09.033  IDENTIFY DEVICE            
  ef 03 46 00 00 00 00 08      20:38:09.026  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 00 08      20:38:09.026  READ NATIVE MAX ADDRESS EXT     

Error 629 occurred at disk power-on lifetime: 7892 hours (328 days + 20 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                              
  -- -- -- -- -- -- --                              
  40 51 00 5c 20 00 e0  Error: UNC at LBA = 0x0000205c = 8284

  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 01 5c 20 00 00 08      20:38:05.757  READ DMA            
  27 00 00 00 00 00 00 08      20:38:05.757  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 00 08      20:38:05.748  IDENTIFY DEVICE            
  ef 03 46 00 00 00 00 08      20:38:05.741  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 00 08      20:38:05.741  READ NATIVE MAX ADDRESS EXT     

Error 628 occurred at disk power-on lifetime: 7892 hours (328 days + 20 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                              
  -- -- -- -- -- -- --                              
  40 51 00 5c 20 00 e0  Error: UNC at LBA = 0x0000205c = 8284

  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 01 5c 20 00 00 08      20:38:02.285  READ DMA            
  27 00 00 00 00 00 00 08      20:38:02.285  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 00 08      20:38:02.276  IDENTIFY DEVICE            
  ef 03 46 00 00 00 00 08      20:38:02.269  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 00 08      20:38:02.269  READ NATIVE MAX ADDRESS EXT     

Error 627 occurred at disk power-on lifetime: 7892 hours (328 days + 20 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                              
  -- -- -- -- -- -- --                              
  40 51 00 5c 20 00 e0  Error: UNC at LBA = 0x0000205c = 8284

  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 01 5c 20 00 00 08      20:37:58.820  READ DMA            
  27 00 00 00 00 00 00 08      20:37:58.820  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 00 08      20:37:58.811  IDENTIFY DEVICE            
  ef 03 46 00 00 00 00 08      20:37:58.804  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 00 08      20:37:58.804  READ NATIVE MAX ADDRESS EXT     

Error 626 occurred at disk power-on lifetime: 7892 hours (328 days + 20 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
  -- -- -- -- -- -- --
  40 51 00 5c 20 00 e0  Error: UNC at LBA = 0x0000205c = 8284

  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 01 5c 20 00 00 08      20:37:55.879  READ DMA
  27 00 00 00 00 00 00 08      20:37:55.879  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 00 08      20:37:55.870  IDENTIFY DEVICE
  ef 03 46 00 00 00 00 08      20:37:55.870  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 00 08      20:37:55.859  READ NATIVE MAX ADDRESS EXT

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       90%      7871         8284
# 2  Extended offline    Completed: read failure       90%      7871         8284

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.

is it this one?

5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0

[psusi]

Yep, looks like the sector just got corrupted somehow and the media is ok. But it looks like you never ran another test after fixing the first one to make sure there aren't any more.

[killaray]

Yep, looks like the sector just got corrupted somehow and the media is ok. But it looks like you never ran another test after fixing the first one to make sure there aren't any more.

it gave me this after running the test again

== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%      7922         -
# 2  Extended offline    Completed: read failure       90%      7871         8284
# 3  Extended offline    Completed: read failure       90%      7871         8284

it says read failure is that bad??