(SOLVED) hard drive check

I seem to be experiencing a failing drive. I can copy and write to it but keep getting disk utility errors. It does not give any more details. But I get the following from the terminal. Does that mean I have to chuck this drive?

I have two internal drives. Happily this not the one with any OS or personal data

============================================================================================================================
siawacsh@siawacsh-sager:~$ sudo smartctl -a /dev/sdb
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-51-generic] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Seagate Momentus 7200.4
Device Model: ST9320423AS
Serial Number: 5VH0HCSN
LU WWN Device Id: 5 000c50 01bd515d0
Firmware Version: 0002SDM1
User Capacity: 320,072,933,376 bytes [320 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Sat Aug 3 00:19:09 2013 IST
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: FAILED!
Drive failure expected in less than 24 hours. SAVE ALL DATA.
See vendor-specific Attribute list for failed Attributes.

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: ( 73) The previous self-test completed having
a test element that failed and the test
element that failed is not known.
Total time to complete Offline
data collection: ( 0) 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: ( 73) minutes.
Conveyance self-test routine
recommended polling time: ( 3) minutes.
SCT capabilities: (0x103f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

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 116 090 006 Pre-fail Always - 113316935
3 Spin_Up_Time 0x0003 098 097 085 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 097 097 020 Old_age Always - 3391
5 Reallocated_Sector_Ct 0x0033 032 032 036 Pre-fail Always FAILING_NOW 1402
7 Seek_Error_Rate 0x000f 076 060 030 Pre-fail Always - 8678394351
9 Power_On_Hours 0x0032 086 086 000 Old_age Always - 13048
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 097 037 020 Old_age Always - 3075
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 567
188 Command_Timeout 0x0032 098 095 000 Old_age Always - 171811603086
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 068 056 045 Old_age Always - 32 (Min/Max 29/32)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 2
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 260
193 Load_Cycle_Count 0x0032 062 062 000 Old_age Always - 77105
194 Temperature_Celsius 0x0022 032 044 000 Old_age Always - 32 (0 5 0 0)
195 Hardware_ECC_Recovered 0x001a 051 045 000 Old_age Always - 113316935
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
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 185692911055224
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 3124763032
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 3147572942
254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0

SMART Error Log Version: 1
ATA Error Count: 445 (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 445 occurred at disk power-on lifetime: 12986 hours (541 days + 2 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 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 00 ff ff ff 4f 00 00:44:12.103 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:44:12.101 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:44:11.739 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:44:11.737 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:44:11.324 READ FPDMA QUEUED

Error 444 occurred at disk power-on lifetime: 12986 hours (541 days + 2 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 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 ff ff ff 4f 00 00:41:09.681 READ FPDMA QUEUED
27 00 00 00 00 00 e0 00 00:41:09.681 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 00:41:09.679 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 00:41:09.679 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 00:41:09.678 READ NATIVE MAX ADDRESS EXT

Error 443 occurred at disk power-on lifetime: 12986 hours (541 days + 2 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 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 ff ff ff 4f 00 00:41:06.943 READ FPDMA QUEUED
27 00 00 00 00 00 e0 00 00:41:06.942 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 00:41:06.941 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 00:41:06.940 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 00:41:06.940 READ NATIVE MAX ADDRESS EXT

Error 442 occurred at disk power-on lifetime: 12986 hours (541 days + 2 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 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 ff ff ff 4f 00 00:41:04.119 READ FPDMA QUEUED
27 00 00 00 00 00 e0 00 00:41:04.119 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 00:41:04.117 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 00:41:04.117 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 00:41:04.116 READ NATIVE MAX ADDRESS EXT

Error 441 occurred at disk power-on lifetime: 12986 hours (541 days + 2 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 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 ff ff ff 4f 00 00:41:01.358 READ FPDMA QUEUED
27 00 00 00 00 00 e0 00 00:41:01.357 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 00:41:01.355 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 00:41:01.355 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 00:41:01.354 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: unknown failure 90% 13047 0
# 2 Extended offline Completed: unknown failure 90% 13047 0
# 3 Extended offline Completed: unknown failure 90% 13044 0

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.

siawacsh@siawacsh-sager:~$

Hi,

have you tried running "FSCK" from the reovery menu??.

Did/do you switch off your PC by pressing the power button without holding it down for 4 - 5 seconds?, this will kill a hard drive very quickly!.

Regards Wolfman

Seatools is not available on the ubuntu repositories. Nor is it available for Linux on the Seagate site.

Hi,

did you try running "FSCK"?.

Have you looked at "PartedMagic"?:

http://partedmagic.com/doku.php#.UgCh0eFiz7Q

Regards Wolfman

Thanks. Here is fsck result. Note it is referring to ext2 file system while I am using ext3.

======================================================================

siawacsh@siawacsh-sager:~$ sudo fsck /dev/sdb
fsck from util-linux 2.20.1
e2fsck 1.42.5 (29-Jul-2012)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>


=======================================================================

I tried the DOS utility. It detected both drives but I was not able to save the log files. I just remebers seeing the message "SMART is tripped" in relation to the Seagate drive.

siawacsh wrote:I tried the DOS utility. It detected both drives but I was not able to save the log files. I just remebers seeing the message "SMART is tripped" in relation to the Seagate drive.

Hi,

have you solved this now?.

In the future, as Swarf suggests, always use Ext4 as it is supossed to be the best!!.

Regards Wolfman

Yes, I tested the drive with the seagate utility resulting in over 20 errors. So I guess I need a new drive. My rig came with three hard drive bays. Till now, I have been using two internal drives. Initially I used one drive for windows and another for Linux. I abandoned windows a few weeks before the Seagate(dedicated to Linux) went belly up.

In the future I want to use the second drive as extra storage capacity. Last time I tried this I had the drive with OS with / and /home partition. I tried to dedicate the second drive to /home, but the installer did not like it. It did allow me to rename the partition as /home_two. But it did not allow me to access it post install. How do I get the OS to see this second drive as extra space.?


I am currently left with a Western Digital which used be dedicated to windows. Perhaps you can help me with a replacement strategy. Another words, how to balance durability versus sheer capacity.

Also, how I might marry a solid state drive with my existing drive.

If asked, durability and data safety has a higher priority than sheer data capacity. Then again, cost is also up there.

Data capacity should not be less than 200 GB.

Any advice regarding my next purchase decision would be much appreciated.

siawacsh

Hi,

have marked as solved.

Here is a vid about SSD:

http://www.youtube.com/watch?v=V3dAa_1LtmA

WD drives are very good but don't ask me which one, look maybe on eBay??.

You do have SATA connections on your motherboard don't you??.

Regards Wolfman

Yes, I do. But what about my question on how to use the second drive as a second /home partitian....? Is it possible to have a / and a /home on the same drive and another /home on the second? or is it an "either or" situation. Another words dedicate the drive with the OS (SSD) to / and the second drive to /home?

Hi,

if you only have one Linux OS on your PC you only need one root and one home, you can still use the 2nd drive for storage and you don't really need a mount point for it, format your root (about 20GB) and your home to EXT4 and the 2nd drive to either FAT32 or NTFS, you can manually mount it when you need it!!.

Regards Wolfman

That youtube link you provided suggests a solid state drive should used for the OS and the regular drive for storage. I suppose he was talking about a windows system. To reiterate, speed has rarely been an issue for me while using Linux. Durability and loss of data has. So would I be right to place the OS on a regular drive and personal data on the solid state?

Hi,

it doesn't really matter which way round you do it, I would use the SSD for Linux and the older drive for your data as there would be more advantages using the SSD for Linux even if you aren't interested in speed!.

What is important is that you set the master and slave settings correctly in BIOS and it is also important that the drive jumpers be set accordingly to slave or master should they be available to you, I don't think that SSD's have a master/slave setting so it would be easier to set the older drive (if it is an IDE drive) to slave!.

See also:

http://www.youtube.com/watch?v=KDPOpBi2gtE

http://www.youtube.com/watch?v=7ZUX9X8t23Y

http://www.easeus.com/disk-copy/single- ... pering.htm

Regards Wolfman

My old/existing drive is SATA2 drive. I have not noticed any jumpers on it. So, when I see drives referred to as SATA-300 or 600 I should aim for the 300 since I wont benefit from the capabilities of a 600, right?

Hi,

I don't know to be honest, I don't know what the differences between the two are, if you have an old SATA drive then there are no jumpers to worry about, just make sure you set the master and slave correctly in BIOS!.

Regards Wolfman