Fedora 11 + HDD Fail

Red Hat, Fedora, CentOS

Sziasztok!

Most telepitettem egy clean installal az uj Fedorat, elso inditas utan ezt vagta a kepembe:

Tudtommal hibatlan a lemez, de ellenorzeskeppen lefuttattam par tesztet (HDD Regenerator, Seagate Tools), amik szinten nem talaltak hibat.

Letezik Fedora ala BadSector kergeto alkalmazas, es a vegerejarhatnak a dolgoknak?

Koszonom!

  • 1472 megtekintés

( fonya | 2009. 06. 12., p – 01:07 )

Kapcsold be a bios smart-jat, es az is ezt fogja mondani indulaskor, ui smart-on keresztul jutott erre a megallapitasra, nem teszttel a program. Egy smartctl -d sat -a /dev/sda elalrulja (az sda ertelemszeru, ha a fenti kepet jol ertelemezem, akkor Neked azzal van gond, a -d sat szinten igy adodott).

A badsector kergeto programot badblocks -nak hivjak.

Lefuttattam a smartctl tesztet, bar en sokmindent nemtudok kivenni belole, remelem te igen.


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

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.10 family
Device Model: ST3200820A
Serial Number: 5QF1BSTQ
Firmware Version: 3.AAC
User Capacity: 200,049,647,616 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Mon Jun 15 20:21:33 2009 CEST
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: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 430) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No 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: ( 74) minutes.

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 092 070 006 Pre-fail Always - 69140789
3 Spin_Up_Time 0x0003 095 095 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 099 099 020 Old_age Always - 1274
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 066 060 030 Pre-fail Always - 335333847632
9 Power_On_Hours 0x0032 092 092 000 Old_age Always - 7200
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 099 099 020 Old_age Always - 1492
187 Reported_Uncorrect 0x0032 080 080 000 Old_age Always - 20
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 060 052 045 Old_age Always - 40 (Lifetime Min/Max 24/40)
194 Temperature_Celsius 0x0022 040 048 000 Old_age Always - 40 (0 11 0 0)
195 Hardware_ECC_Recovered 0x001a 067 052 000 Old_age Always - 37279880
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 1
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 1
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 2
200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0
202 TA_Increase_Count 0x0032 100 253 000 Old_age Always - 0

SMART Error Log Version: 1
ATA Error Count: 23 (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 23 occurred at disk power-on lifetime: 3684 hours (153 days + 12 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 01 95 7c 61 e0 Error: UNC at LBA = 0x00617c95 = 6388885

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
42 d8 01 95 7c 61 e0 00 07:28:35.915 READ VERIFY SECTOR(S) EXT
25 d8 01 00 00 00 e0 00 07:28:35.915 READ DMA EXT
42 d8 02 95 7c 61 e0 00 07:28:35.901 READ VERIFY SECTOR(S) EXT
25 d8 01 00 00 00 e0 00 07:28:35.877 READ DMA EXT
42 d8 02 93 7c 61 e0 00 07:28:34.318 READ VERIFY SECTOR(S) EXT

Error 22 occurred at disk power-on lifetime: 3684 hours (153 days + 12 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 02 95 7c 61 e0 Error: UNC at LBA = 0x00617c95 = 6388885

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
42 d8 02 95 7c 61 e0 00 07:28:35.915 READ VERIFY SECTOR(S) EXT
25 d8 01 00 00 00 e0 00 07:28:35.915 READ DMA EXT
42 d8 02 93 7c 61 e0 00 07:28:35.901 READ VERIFY SECTOR(S) EXT
25 d8 01 00 00 00 e0 00 07:28:35.877 READ DMA EXT
42 d8 04 93 7c 61 e0 00 07:28:34.318 READ VERIFY SECTOR(S) EXT

Error 21 occurred at disk power-on lifetime: 3684 hours (153 days + 12 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 02 95 7c 61 e0 Error: UNC at LBA = 0x00617c95 = 6388885

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
42 d8 04 93 7c 61 e0 00 07:28:31.051 READ VERIFY SECTOR(S) EXT
25 d8 01 80 cf a4 e0 00 07:28:31.028 READ DMA EXT
42 d8 04 8f 7c 61 e0 00 07:28:31.004 READ VERIFY SECTOR(S) EXT
25 d8 01 00 00 00 e0 00 07:28:29.443 READ DMA EXT
42 d8 08 97 7c 61 e0 00 07:28:34.318 READ VERIFY SECTOR(S) EXT

Error 20 occurred at disk power-on lifetime: 3684 hours (153 days + 12 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 02 95 7c 61 e0 Error: UNC at LBA = 0x00617c95 = 6388885

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
42 d8 08 8f 7c 61 e0 00 07:28:31.051 READ VERIFY SECTOR(S) EXT
25 d8 01 00 00 00 e0 00 07:28:31.028 READ DMA EXT
42 d8 10 8f 7c 61 e0 00 07:28:31.004 READ VERIFY SECTOR(S) EXT
25 d8 01 80 cf a4 e0 00 07:28:29.443 READ DMA EXT
42 d8 10 7f 7c 61 e0 00 07:28:29.419 READ VERIFY SECTOR(S) EXT

Error 19 occurred at disk power-on lifetime: 3684 hours (153 days + 12 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 0a 95 7c 61 e0 Error: UNC at LBA = 0x00617c95 = 6388885

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
42 d8 10 8f 7c 61 e0 00 07:28:31.051 READ VERIFY SECTOR(S) EXT
25 d8 01 80 cf a4 e0 00 07:28:31.028 READ DMA EXT
42 d8 10 7f 7c 61 e0 00 07:28:31.004 READ VERIFY SECTOR(S) EXT
25 d8 01 00 00 00 e0 00 07:28:29.443 READ DMA EXT
42 d8 20 9f 7c 61 e0 00 07:28:29.419 READ VERIFY SECTOR(S) EXT

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 7178 -
# 2 Short offline Completed without error 00% 7173 -
# 3 Extended offline Aborted by host 90% 7172 -
# 4 Short offline Completed without error 00% 7172 -
# 5 Short offline Completed without error 00% 7171 -
# 6 Short offline Aborted by host 60% 7170 -
# 7 Short offline Completed without error 00% 7084 -

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.

Sookkal tobbet en sem, de ha utana akarsz jarni, akkor most mar tudod, hogy merre indulj el.
Egyebkent nalam a 197-es mellett 0 szerepel /196-tol 200-ig/:
197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 0
Gondolom jo nagy a winchester, igy a badblock nem igazan jatszik, es az is lehet, hogy at-map-eli, es nem is veszed eszre, reg nem merultem el a vinyok, es a smart rejtelmeiben. Ha lenne ra keret, akarmi, en cserelnem.

( tomsolo | 2009. 06. 15., h – 20:33 )

Nekem ugyanezt dobta fel hétvégén, pontosan 1 badsectorral, valahol boot partició környékén ráadásul.
Először én is mindenféle F11 összesküvést láttam a dologban, ezért átgyalultam NTFS-re és megnéztem win alatt sajna ott is megtaláltam. Utána a merevlemez diganosztikai toolja is megtalálta és - khmmm - javította. Azóta persze sehol sem látszik csak logból hogy volt ilyen.

Felhívtam a szervízt, hogy wtf akkor most mi van azt mondták hozzam be, adnak helyette egy másikat, ha fontosak az adataim.

No rainbow, no sugar

( segabor | 2009. 06. 15., h – 22:27 )

Ha már a SMART monitor elkezd jelezni, akkor készülj fel a terjedő kórra, egyre több bad sectorod lesz. Én így jártam másfél hónapja egy Seagate 80 GB-os vinyóval. Nem figyeltem a smartd károgására, meg is lett a böjtje. A be nem bootoló szervernél nincs siralmasabb látvány.

--
Kinek nem inge, ne vegye gatyára

( akkos v | 2009. 06. 15., h – 23:02 )

nekem szinten bad sector-t dobott a fedora. + állandóan csontrafagyott, és nemigen tudtam kideríteni miért.
ez má' gyanús :)
(más rendszeren nem futattam smart-ot, lusta vagyok)