LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 12-09-2012, 11:05 AM   #1
satimis
Senior Member
 
Registered: Apr 2003
Posts: 3,569

Rep: Reputation: 54
Hard Disk:S.M.A.R.T. Statis BAD


Hi all,

Ubuntu 12.04 desktop 64bit

Booting problem

During booting
Code:
SATA 2: ST31000528AS CC38
Ultra DMA Mode-6, S.M.A.R.T. Capable and Status BAD
3rd slave Hard Disk:S.M.A.R.T. Status BAD, Backup and Replace
Press F1 to Resume
Pressing F1 starts Ubuntu

Then I ran Fedora live USB with;
Code:
# dd if=/dev/zero of=/dev/sda bs=1M
to wipe out the complete hd (1TB in capacity)

on reboot, following warning popup
Code:
.....
SATA 1: ST31000528AS CC38
Ultra DMA Mode-6, S.M.A.R.T. Capable and Status BAD
....
....
3rd Master  Hard Disk:S.M.A.R.T. Statis BAD. Backup and Replace
Press F1 to Resume
Pressing F1 started Fedora17
-> install Fedora 17 using the complete HD. But complained
Code:
Automatic Prtitioning Errors
The following errors occurred with your partitioning.

Your / partition is less than 4096.0 MB which is lower than recommended for normal Fedora Live install.

This can hapen if there is not enough space on your hard drive(s) for the installation

Press OK to chose a different partioning option
[OK]
Please help. TIA

B.R.
satimis

Background story:-
I connected 2 HDs on this PC, the captioned HD, say HD1 and another HD, say HD2. HD2 is also installed with Ubuntu 12.04 deskop as host and Oracle VirtualBox as virtualizer. I started booting HD1 trying to copy the VMs from HD2 to it. HD1 also has Oracle VirtualBox installed. On HOME of HD1 I saw VMs being copied to it. But later the PC hanged for unknown reason. I pressed hard reboot then the mishap started.

All the VMs copied on HD1 were automatically removed for unknown reason.
 
Old 12-09-2012, 11:26 AM   #2
H_TeXMeX_H
LQ Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279
Well, you should:

Quote:
Backup and Replace
the dying HDD.

Run 'smartctl -a' on each drive to find out which one is dying.
 
Old 12-09-2012, 11:33 AM   #3
satimis
Senior Member
 
Registered: Apr 2003
Posts: 3,569

Original Poster
Rep: Reputation: 54
Quote:
Originally Posted by H_TeXMeX_H View Post
Well, you should:



the dying HDD.
Before copying VMs both HDs were working without problem. Now HD2 is working without problem. Only HD1 has problem

Quote:
Run 'smartctl -a' on each drive to find out which one is dying.
How can I run above command to check HD1? Whether run Live Fedora17 USB to check it?


Edit:
Ran Fedora 17 live USB to test HD1

# smartctl -a /dev/sda
Code:
smartctl 5.43 2012-06-30 r3573 [x86_64-linux-3.3.4-5.fc17.x86_64] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.12
Device Model:     ST31000528AS
Serial Number:    5VP2N4R8
LU WWN Device Id: 5 000c50 01e43c03d
Firmware Version: CC38
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:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Sun Dec  9 21:01:05 2012 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: 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:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(  600) 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: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 ( 181) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) 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   119   099   006    Pre-fail  Always       -       205542173
  3 Spin_Up_Time            0x0003   095   094   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   097   097   020    Old_age   Always       -       3785
  5 Reallocated_Sector_Ct   0x0033   002   002   036    Pre-fail  Always   FAILING_NOW 4027
  7 Seek_Error_Rate         0x000f   075   060   030    Pre-fail  Always       -       35510604
  9 Power_On_Hours          0x0032   098   098   000    Old_age   Always       -       2353
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   099   099   020    Old_age   Always       -       1886
183 Runtime_Bad_Block       0x0032   099   099   000    Old_age   Always       -       1
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   099   099   000    Old_age   Always       -       1
188 Command_Timeout         0x0032   100   096   000    Old_age   Always       -       8590067093
189 High_Fly_Writes         0x003a   099   099   000    Old_age   Always       -       1
190 Airflow_Temperature_Cel 0x0022   068   059   045    Old_age   Always       -       32 (Min/Max 32/32)
194 Temperature_Celsius     0x0022   032   041   000    Old_age   Always       -       32 (0 14 0 0 0)
195 Hardware_ECC_Recovered  0x001a   038   032   000    Old_age   Always       -       205542173
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       -       1
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       237400022324607
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       866102008
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       2554858803

SMART Error Log Version: 1
ATA Error Count: 27 (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 27 occurred at disk power-on lifetime: 2353 hours (98 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  04 71 04 9d 00 32 e0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  a1 00 04 9d 00 32 a0 00      01:34:40.167  IDENTIFY PACKET DEVICE
  ec 00 01 01 00 00 a0 00      01:34:39.063  IDENTIFY DEVICE
  00 00 00 00 00 00 00 04      01:34:39.024  NOP [Abort queued commands]
  ec 00 00 00 00 00 a0 00      01:34:30.504  IDENTIFY DEVICE
  00 00 00 00 00 00 00 04      01:34:30.356  NOP [Abort queued commands]

Error 26 occurred at disk power-on lifetime: 2353 hours (98 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  04 71 04 9d 00 32 e0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ec 00 01 01 00 00 a0 00      01:34:39.063  IDENTIFY DEVICE
  00 00 00 00 00 00 00 04      01:34:39.024  NOP [Abort queued commands]
  ec 00 00 00 00 00 a0 00      01:34:30.504  IDENTIFY DEVICE
  00 00 00 00 00 00 00 04      01:34:30.356  NOP [Abort queued commands]
  00 00 00 00 00 00 00 ff      01:34:29.747  NOP [Abort queued commands]

Error 25 occurred at disk power-on lifetime: 2353 hours (98 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  04 71 04 9d 00 32 e0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ec 00 00 00 00 00 a0 00      01:34:30.504  IDENTIFY DEVICE
  00 00 00 00 00 00 00 04      01:34:30.356  NOP [Abort queued commands]
  00 00 00 00 00 00 00 ff      01:34:29.747  NOP [Abort queued commands]
  00 00 00 00 00 00 00 ff      01:34:23.042  NOP [Abort queued commands]
  a1 00 00 00 00 00 a0 00      01:33:41.671  IDENTIFY PACKET DEVICE

Error 24 occurred at disk power-on lifetime: 2353 hours (98 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  04 71 04 9d 00 32 e0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  a1 00 00 00 00 00 a0 00      01:33:41.671  IDENTIFY PACKET DEVICE
  ec 00 00 00 00 00 a0 00      01:33:41.671  IDENTIFY DEVICE
  00 00 00 00 00 00 00 04      01:33:41.520  NOP [Abort queued commands]
  00 00 00 00 00 00 00 04      01:33:41.365  NOP [Abort queued commands]
  00 00 00 00 00 00 00 ff      01:33:41.056  NOP [Abort queued commands]

Error 23 occurred at disk power-on lifetime: 2353 hours (98 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  04 71 04 9d 00 32 e0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ec 00 00 00 00 00 a0 00      01:33:41.671  IDENTIFY DEVICE
  00 00 00 00 00 00 00 04      01:33:41.520  NOP [Abort queued commands]
  00 00 00 00 00 00 00 04      01:33:41.365  NOP [Abort queued commands]
  00 00 00 00 00 00 00 ff      01:33:41.056  NOP [Abort queued commands]
  a1 00 04 9d 00 32 a0 00      01:33:23.939  IDENTIFY PACKET DEVICE

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


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.

B.R.
satimis

Last edited by satimis; 12-09-2012 at 12:07 PM.
 
Old 12-10-2012, 02:04 AM   #4
H_TeXMeX_H
LQ Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279
Code:
  5 Reallocated_Sector_Ct   0x0033   002   002   036    Pre-fail  Always   FAILING_NOW 4027
Yes, the drive is failing, backup all data from that drive if you have any on there and replace the drive.
 
Old 12-10-2012, 05:52 AM   #5
satimis
Senior Member
 
Registered: Apr 2003
Posts: 3,569

Original Poster
Rep: Reputation: 54
Quote:
Originally Posted by H_TeXMeX_H View Post
Code:
  5 Reallocated_Sector_Ct   0x0033   002   002   036    Pre-fail  Always   FAILING_NOW 4027
Yes, the drive is failing, backup all data from that drive if you have any on there and replace the drive.
This HD has been purchased for sometimes but not being used, only resting on the shelves.

I don't know whether copying VMs between HDs direct on the same PC is the cause of the HD failure. I have purchased a new WD 2TB Black Label HD. But I would copy VMs to an external HD first and then recopy them to the new HD.

Thanks

B.R.
satimis
 
Old 12-10-2012, 07:42 AM   #6
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Germany
Distribution: Whatever fits the task best
Posts: 16,566
Blog Entries: 2

Rep: Reputation: 4558Reputation: 4558Reputation: 4558Reputation: 4558Reputation: 4558Reputation: 4558Reputation: 4558Reputation: 4558Reputation: 4558Reputation: 4558Reputation: 4558
That the error ocured while copying large data files (the VM hard disks) onto it is a symptom, not the cause. If you copy large amounts of data onto a drive that has already failing sectors the drive's electronic will become aware of those sectors that it weren't recognizing as failing before. The disk has to use the sector to be able to determine its status. Copying the data onto it has not caused the failure.
By the way, the drive is not aware from where the data comes that is written on it. So copying the VM's to an external disk just to copy them back to the internal disk is nothing than a waste of time, except I have misunderstood that and you were talking about taking a backup.
 
Old 12-10-2012, 10:39 AM   #7
satimis
Senior Member
 
Registered: Apr 2003
Posts: 3,569

Original Poster
Rep: Reputation: 54
Quote:
Originally Posted by TobiSGD View Post
That the error ocured while copying large data files (the VM hard disks) onto it is a symptom, not the cause. If you copy large amounts of data onto a drive that has already failing sectors the drive's electronic will become aware of those sectors that it weren't recognizing as failing before. The disk has to use the sector to be able to determine its status. Copying the data onto it has not caused the failure.
Thanks for your advice.

Quote:
By the way, the drive is not aware from where the data comes that is written on it. So copying the VM's to an external disk just to copy them back to the internal disk is nothing than a waste of time, except I have misunderstood that and you were talking about taking a backup.
I do agree that this arrangement will waste lot of time because copying large data files. I'll copy them direct PC to PC via ssh.

B.R.
satimis
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Bad sectors on Hard Disk dsenic2000@yahoo.com Debian 5 03-17-2011 02:07 AM
HARD DISK BAD SECTOrS zoetrope87 Linux - Hardware 7 03-02-2007 05:16 PM
Bad hard disk? Anything I can try? jnsg Slackware 10 08-21-2006 01:28 AM
HARD DISK BAD SECTOrS zoetrope87 Linux - Software 2 01-12-2006 03:54 AM
Hard Disk not spinning down (is that bad?) l00zer Linux - Laptop and Netbook 2 11-05-2004 11:15 PM


All times are GMT -5. The time now is 06:10 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration