AbcLinuxu:/ Poradna / Linuxová poradna / Chyba s diskem v raidu - vadný disk, kabel.. ?

Štítky: copyright, data, disk, error, ext4, firmware, For, GParted, chyba, kabely, napájení, net, pole, POWER, problém, RAID, recovery, rozdělení disků, rychlost, řadič, řadiče, SATA, smart, souborové systémy, standard, status, Super, Suspend, tag, test, virtualizace, VMware, změna

Dotaz: Chyba s diskem v raidu - vadný disk, kabel.. ?

22.1.2014 19:05 krtek
Chyba s diskem v raidu - vadný disk, kabel.. ?

Přečteno: 459×

Odpovědět | Admin

Hezký podvečer,

jsem v koncích, jelikož už po několikáté řeším jeden a ten samý stroj. Mám na debianu raid, kde jsou dva systémové disky, raid1, ty by měli být v pohodě. Donedávna tam byl třetí disk, 3TB jen jako datový, bohužel po tvrdým vypnutí se něco po.... Data se mi podařilo vytáhnout, disk naformátovat, projet pár utilitkama, které tvrdili, že disk ok. Tak jsem tedy disk vrátil, plus dovybavil stroj o čtvrtý disk, také 3TB a chtěl jsem opět je zrcadlit. Nakonec jsem si je v gparted hezky zarovnal, nechal jsem od konce cca 1GB místa pro jistotu (ani nevím proč tolik, asi mi to z těch 3TB přišlo akorát), vytvořil oddíly s ext4, vytvořil raidové pole, přidal disky, scanem vepsané v /etc/mdadm/mdadm.conf, kde to tedy funguje normálně i po restartu. Jakmile jsem ale /dev/md2 namountil někam (což šlo) se začali syncit a vše vypadalo v pohodě. Ale 68% je kritických, kde se to zastaví, rychlost spadne na 1K/sec

Personalities : [raid1]
md2 : active raid1 sdc[0] sdd[1]
      2930264367 blocks super 1.2 [2/2] [UU]
      [=============>.......]  resync = 68.5% (2008156992/2930264367) finish=14977129.5min speed=1K/sec

md1 : active (auto-read-only) raid1 sda2[0] sdb2[1]
      7914484 blocks super 1.2 [2/2] [UU]

md0 : active raid1 sda1[0] sdb1[1]
      480466808 blocks super 1.2 [2/2] [UU]

unused devices: none

a konec, už zo semnou nemluví. O to horší je, co najdu v logu. Přikládám výpis.

Jan 22 18:42:00 vmware kernel: [67204.407885] ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 22 18:42:00 vmware kernel: [67204.407898] ata7.00: BMDMA stat 0x25
Jan 22 18:42:00 vmware kernel: [67204.407907] ata7.00: failed command: READ DMA EXT
Jan 22 18:42:00 vmware kernel: [67204.407920] ata7.00: cmd 25/00:08:80:1a:64/00:00:ef:00:00/e0 tag 0 dma 4096 in
Jan 22 18:42:00 vmware kernel: [67204.407921]          res 51/40:00:80:1a:64/40:00:ef:00:00/00 Emask 0x9 (media error)
Jan 22 18:42:00 vmware kernel: [67204.407946] ata7.00: status: { DRDY ERR }
Jan 22 18:42:00 vmware kernel: [67204.407954] ata7.00: error: { UNC }
Jan 22 18:42:00 vmware kernel: [67204.452954] ata7.00: configured for UDMA/33
Jan 22 18:42:00 vmware kernel: [67204.452973] ata7: EH complete
Jan 22 18:42:03 vmware kernel: [67207.040700] ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 22 18:42:03 vmware kernel: [67207.040715] ata7.00: BMDMA stat 0x25
Jan 22 18:42:03 vmware kernel: [67207.040726] ata7.00: failed command: READ DMA EXT
Jan 22 18:42:03 vmware kernel: [67207.040740] ata7.00: cmd 25/00:08:80:1a:64/00:00:ef:00:00/e0 tag 0 dma 4096 in
Jan 22 18:42:03 vmware kernel: [67207.040742]          res 51/40:00:80:1a:64/40:00:ef:00:00/00 Emask 0x9 (media error)
Jan 22 18:42:03 vmware kernel: [67207.040770] ata7.00: status: { DRDY ERR }
Jan 22 18:42:03 vmware kernel: [67207.040779] ata7.00: error: { UNC }
Jan 22 18:42:03 vmware kernel: [67207.080951] ata7.00: configured for UDMA/33
Jan 22 18:42:03 vmware kernel: [67207.080969] ata7: EH complete
Jan 22 18:42:05 vmware kernel: [67209.713151] ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 22 18:42:05 vmware kernel: [67209.713166] ata7.00: BMDMA stat 0x25
Jan 22 18:42:05 vmware kernel: [67209.713176] ata7.00: failed command: READ DMA EXT
Jan 22 18:42:05 vmware kernel: [67209.713191] ata7.00: cmd 25/00:08:80:1a:64/00:00:ef:00:00/e0 tag 0 dma 4096 in
Jan 22 18:42:05 vmware kernel: [67209.713193]          res 51/40:00:80:1a:64/40:00:ef:00:00/00 Emask 0x9 (media error)
Jan 22 18:42:05 vmware kernel: [67209.713221] ata7.00: status: { DRDY ERR }
Jan 22 18:42:05 vmware kernel: [67209.713230] ata7.00: error: { UNC }
Jan 22 18:42:05 vmware kernel: [67209.760888] ata7.00: configured for UDMA/33
Jan 22 18:42:05 vmware kernel: [67209.760906] ata7: EH complete
Jan 22 18:42:08 vmware kernel: [67212.347898] ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 22 18:42:08 vmware kernel: [67212.347913] ata7.00: BMDMA stat 0x25
Jan 22 18:42:08 vmware kernel: [67212.347923] ata7.00: failed command: READ DMA EXT
Jan 22 18:42:08 vmware kernel: [67212.347938] ata7.00: cmd 25/00:08:80:1a:64/00:00:ef:00:00/e0 tag 0 dma 4096 in
Jan 22 18:42:08 vmware kernel: [67212.347940]          res 51/40:00:80:1a:64/40:00:ef:00:00/00 Emask 0x9 (media error)
Jan 22 18:42:08 vmware kernel: [67212.349816] ata7.00: status: { DRDY ERR }
Jan 22 18:42:08 vmware kernel: [67212.349826] ata7.00: error: { UNC }
Jan 22 18:42:08 vmware kernel: [67212.396932] ata7.00: configured for UDMA/33
Jan 22 18:42:08 vmware kernel: [67212.396951] ata7: EH complete
Jan 22 18:42:13 vmware kernel: [67217.662884] ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 22 18:42:13 vmware kernel: [67217.662899] ata7.00: BMDMA stat 0x25
Jan 22 18:42:13 vmware kernel: [67217.662910] ata7.00: failed command: READ DMA EXT
Jan 22 18:42:13 vmware kernel: [67217.662924] ata7.00: cmd 25/00:80:80:29:64/00:00:ef:00:00/e0 tag 0 dma 65536 in
Jan 22 18:42:13 vmware kernel: [67217.662926]          res 51/40:00:88:29:64/40:00:ef:00:00/00 Emask 0x9 (media error)
Jan 22 18:42:13 vmware kernel: [67217.662954] ata7.00: status: { DRDY ERR }
Jan 22 18:42:13 vmware kernel: [67217.662964] ata7.00: error: { UNC }
Jan 22 18:42:13 vmware kernel: [67217.708896] ata7.00: configured for UDMA/33
Jan 22 18:42:13 vmware kernel: [67217.708911] ata7: EH complete
Jan 22 18:42:17 vmware kernel: [67221.415179] ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 22 18:42:17 vmware kernel: [67221.415194] ata7.00: BMDMA stat 0x24
Jan 22 18:42:17 vmware kernel: [67221.415204] ata7.00: failed command: READ DMA EXT
Jan 22 18:42:17 vmware kernel: [67221.415219] ata7.00: cmd 25/00:80:80:29:64/00:00:ef:00:00/e0 tag 0 dma 65536 in
Jan 22 18:42:17 vmware kernel: [67221.415221]          res 51/40:00:90:29:64/40:00:ef:00:00/00 Emask 0x9 (media error)
Jan 22 18:42:17 vmware kernel: [67221.415249] ata7.00: status: { DRDY ERR }
Jan 22 18:42:17 vmware kernel: [67221.415258] ata7.00: error: { UNC }
Jan 22 18:42:17 vmware kernel: [67221.460411] ata7.00: configured for UDMA/33
Jan 22 18:42:17 vmware kernel: [67221.460427] ata7: EH complete
Jan 22 18:42:20 vmware kernel: [67224.032836] ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 22 18:42:20 vmware kernel: [67224.032850] ata7.00: BMDMA stat 0x25
Jan 22 18:42:20 vmware kernel: [67224.032861] ata7.00: failed command: READ DMA EXT
Jan 22 18:42:20 vmware kernel: [67224.032875] ata7.00: cmd 25/00:80:80:29:64/00:00:ef:00:00/e0 tag 0 dma 65536 in
Jan 22 18:42:20 vmware kernel: [67224.032877]          res 51/40:00:80:29:64/40:00:ef:00:00/00 Emask 0x9 (media error)
Jan 22 18:42:20 vmware kernel: [67224.032905] ata7.00: status: { DRDY ERR }
Jan 22 18:42:20 vmware kernel: [67224.032915] ata7.00: error: { UNC }
Jan 22 18:42:20 vmware kernel: [67224.072927] ata7.00: configured for UDMA/33
Jan 22 18:42:20 vmware kernel: [67224.072942] ata7: EH complete
Jan 22 18:42:22 vmware kernel: [67226.659199] ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 22 18:42:22 vmware kernel: [67226.659214] ata7.00: BMDMA stat 0x25
Jan 22 18:42:22 vmware kernel: [67226.659225] ata7.00: failed command: READ DMA EXT
Jan 22 18:42:22 vmware kernel: [67226.659239] ata7.00: cmd 25/00:80:80:29:64/00:00:ef:00:00/e0 tag 0 dma 65536 in
Jan 22 18:42:22 vmware kernel: [67226.659241]          res 51/40:00:80:29:64/40:00:ef:00:00/00 Emask 0x9 (media error)
Jan 22 18:42:22 vmware kernel: [67226.659269] ata7.00: status: { DRDY ERR }
Jan 22 18:42:22 vmware kernel: [67226.659278] ata7.00: error: { UNC }
Jan 22 18:42:22 vmware kernel: [67226.704725] ata7.00: configured for UDMA/33
Jan 22 18:42:22 vmware kernel: [67226.704742] ata7: EH complete
Jan 22 18:42:25 vmware kernel: [67229.235705] ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 22 18:42:25 vmware kernel: [67229.235719] ata7.00: BMDMA stat 0x25
Jan 22 18:42:25 vmware kernel: [67229.235728] ata7.00: failed command: READ DMA EXT
Jan 22 18:42:25 vmware kernel: [67229.235740] ata7.00: cmd 25/00:80:80:29:64/00:00:ef:00:00/e0 tag 0 dma 65536 in
Jan 22 18:42:25 vmware kernel: [67229.235741]          res 51/40:00:80:29:64/40:00:ef:00:00/00 Emask 0x9 (media error)
Jan 22 18:42:25 vmware kernel: [67229.235766] ata7.00: status: { DRDY ERR }
Jan 22 18:42:25 vmware kernel: [67229.235775] ata7.00: error: { UNC }
Jan 22 18:42:25 vmware kernel: [67229.280909] ata7.00: configured for UDMA/33
Jan 22 18:42:25 vmware kernel: [67229.280925] ata7: EH complete
Jan 22 18:42:27 vmware kernel: [67231.811962] ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 22 18:42:27 vmware kernel: [67231.811976] ata7.00: BMDMA stat 0x25
Jan 22 18:42:27 vmware kernel: [67231.811986] ata7.00: failed command: READ DMA EXT
Jan 22 18:42:27 vmware kernel: [67231.811999] ata7.00: cmd 25/00:80:80:29:64/00:00:ef:00:00/e0 tag 0 dma 65536 in
Jan 22 18:42:27 vmware kernel: [67231.812000]          res 51/40:00:80:29:64/40:00:ef:00:00/00 Emask 0x9 (media error)
Jan 22 18:42:27 vmware kernel: [67231.812028] ata7.00: status: { DRDY ERR }
Jan 22 18:42:27 vmware kernel: [67231.812037] ata7.00: error: { UNC }
Jan 22 18:42:27 vmware kernel: [67231.852876] ata7.00: configured for UDMA/33
Jan 22 18:42:27 vmware kernel: [67231.852893] sd 6:0:0:0: [sdc] Unhandled sense code
Jan 22 18:42:27 vmware kernel: [67231.852895] sd 6:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 22 18:42:27 vmware kernel: [67231.852898] sd 6:0:0:0: [sdc] Sense Key : Medium Error [current] [descriptor]
Jan 22 18:42:27 vmware kernel: [67231.852902] Descriptor sense data with sense descriptors (in hex):
Jan 22 18:42:27 vmware kernel: [67231.852904]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Jan 22 18:42:27 vmware kernel: [67231.852912]         ef 64 29 80
Jan 22 18:42:27 vmware kernel: [67231.852915] sd 6:0:0:0: [sdc] Add. Sense: Unrecovered read error - auto reallocate failed
Jan 22 18:42:27 vmware kernel: [67231.852920] sd 6:0:0:0: [sdc] CDB: Read(10): 28 00 ef 64 29 80 00 00 80 00
Jan 22 18:42:27 vmware kernel: [67231.852928] end_request: I/O error, dev sdc, sector 4016318848
Jan 22 18:42:27 vmware kernel: [67231.852961] ata7: EH complete
Jan 22 18:42:31 vmware kernel: [67235.010126] ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 22 18:42:31 vmware kernel: [67235.010139] ata7.00: BMDMA stat 0x25
Jan 22 18:42:31 vmware kernel: [67235.010148] ata7.00: failed command: READ DMA EXT
Jan 22 18:42:31 vmware kernel: [67235.010160] ata7.00: cmd 25/00:08:90:1a:64/00:00:ef:00:00/e0 tag 0 dma 4096 in
Jan 22 18:42:31 vmware kernel: [67235.010162]          res 51/40:00:90:1a:64/40:00:ef:00:00/00 Emask 0x9 (media error)
Jan 22 18:42:31 vmware kernel: [67235.010188] ata7.00: status: { DRDY ERR }
Jan 22 18:42:31 vmware kernel: [67235.010196] ata7.00: error: { UNC }
Jan 22 18:42:31 vmware kernel: [67235.092913] ata7.00: configured for UDMA/33
Jan 22 18:42:31 vmware kernel: [67235.092933] ata7: EH complete
Jan 22 18:42:38 vmware kernel: [67242.730860] ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 22 18:42:38 vmware kernel: [67242.730875] ata7.00: BMDMA stat 0x25
Jan 22 18:42:38 vmware kernel: [67242.730886] ata7.00: failed command: READ DMA EXT
Jan 22 18:42:38 vmware kernel: [67242.730900] ata7.00: cmd 25/00:08:b0:1a:64/00:00:ef:00:00/e0 tag 0 dma 4096 in
Jan 22 18:42:38 vmware kernel: [67242.730902]          res 51/40:00:b0:1a:64/40:00:ef:00:00/00 Emask 0x9 (media error)
Jan 22 18:42:38 vmware kernel: [67242.730930] ata7.00: status: { DRDY ERR }
Jan 22 18:42:38 vmware kernel: [67242.730940] ata7.00: error: { UNC }
Jan 22 18:42:38 vmware kernel: [67242.776908] ata7.00: configured for UDMA/33
Jan 22 18:42:38 vmware kernel: [67242.776926] ata7: EH complete

Kde tedy sdc je ten disk, který předtím zkolaboval, o to mě to děsí víc. Podle logu ale co jsem dobu googlil, tak se většinou dle chyb jedná o problém s napájením disku, se sata kabelem, či řadič, ale prostě nevím co dál. Ten stroj převezu zítra domů abych na tom mohl pracovat a testovat, takže mám v plánu dát nový kabely a proházet napájení dísků i disky na řadiči, jestli bude nějaká změna. Nesetkal se někdo s něčím podobným ? Díky za každou radu a tip ! Přikládám i nějaké výpisy ze smartctl, já z toho nějak moc moudrý nejsem

/smartctl -a /dev/sdc


smartctl 5.40 2010-07-12 r3124 [x86_64-unknown-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     ST3000VX000-9YW166
Serial Number:    Z1F1RM77
Firmware Version: CV13
User Capacity:    3 000 591 900 160 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Wed Jan 22 18:56:51 2014 CET
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:      (  33) The self-test routine was interrupted
                                        by the host with a hard or soft reset.
Total time to complete Offline
data collection:                 ( 600) seconds.
Offline data collection
capabilities:                    (0x73) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        No 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:        ( 255) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x10b9) 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   069   069   006    Pre-fail  Always       -       82731819
  3 Spin_Up_Time            0x0003   094   093   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       33
  5 Reallocated_Sector_Ct   0x0033   051   051   036    Pre-fail  Always       -       64736
  7 Seek_Error_Rate         0x000f   100   253   030    Pre-fail  Always       -       777764
  9 Power_On_Hours          0x0032   090   090   000    Old_age   Always       -       9543
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       33
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       11643
188 Command_Timeout         0x0032   090   090   000    Old_age   Always       -       51540393996
189 High_Fly_Writes         0x003a   081   081   000    Old_age   Always       -       19
190 Airflow_Temperature_Cel 0x0022   062   055   045    Old_age   Always       -       38 (Lifetime Min/Max 32/40)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       23
193 Load_Cycle_Count        0x0032   096   096   000    Old_age   Always       -       8361
194 Temperature_Celsius     0x0022   038   045   000    Old_age   Always       -       38 (0 15 0 0)
197 Current_Pending_Sector  0x0012   100   099   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   099   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       2

SMART Error Log Version: 1
ATA Error Count: 11509 (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 11509 occurred at disk power-on lifetime: 9543 hours (397 days + 15 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 ff ff ff ef 00   1d+00:43:12.519  READ DMA EXT
  25 00 08 ff ff ff ef 00   1d+00:43:11.919  READ DMA EXT
  25 00 08 ff ff ff ef 00   1d+00:43:11.322  READ DMA EXT
  25 00 80 ff ff ff ef 00   1d+00:43:03.575  READ DMA EXT
  25 00 08 ff ff ff ef 00   1d+00:43:02.972  READ DMA EXT

Error 11508 occurred at disk power-on lifetime: 9543 hours (397 days + 15 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 ff ff ff ef 00   1d+00:43:00.283  READ DMA EXT
  25 00 08 ff ff ff ef 00   1d+00:42:59.685  READ DMA EXT
  27 00 00 00 00 00 e0 00   1d+00:42:59.685  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00   1d+00:42:59.677  IDENTIFY DEVICE
  ef 03 42 00 00 00 a0 00   1d+00:42:59.668  SET FEATURES [Set transfer mode]

Error 11507 occurred at disk power-on lifetime: 9543 hours (397 days + 15 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 ff ff ff ef 00   1d+00:42:57.058  READ DMA EXT
  25 00 08 ff ff ff ef 00   1d+00:42:56.457  READ DMA EXT
  25 00 08 ff ff ff ef 00   1d+00:42:55.857  READ DMA EXT
  25 00 08 ff ff ff ef 00   1d+00:42:55.257  READ DMA EXT
  25 00 08 ff ff ff ef 00   1d+00:42:54.657  READ DMA EXT

Error 11506 occurred at disk power-on lifetime: 9543 hours (397 days + 15 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 ff ff ff ef 00   1d+00:42:51.381  READ DMA EXT
  25 00 08 ff ff ff ef 00   1d+00:42:50.795  READ DMA EXT
  25 00 08 ff ff ff ef 00   1d+00:42:49.273  READ DMA EXT
  25 00 08 ff ff ff ef 00   1d+00:42:48.672  READ DMA EXT
  25 00 08 ff ff ff ef 00   1d+00:42:48.086  READ DMA EXT

Error 11505 occurred at disk power-on lifetime: 9543 hours (397 days + 15 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 ff ff ff ef 00   1d+00:42:42.555  READ DMA EXT
  25 00 08 ff ff ff ef 00   1d+00:42:41.954  READ DMA EXT
  25 00 08 ff ff ff ef 00   1d+00:42:41.354  READ DMA EXT
  25 00 08 ff ff ff ef 00   1d+00:42:40.752  READ DMA EXT
  27 00 00 00 00 00 e0 00   1d+00:42:40.751  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  Short offline       Interrupted (host reset)      10%      9523         -
# 2  Short offline       Completed without error       00%      9476         -
# 3  Extended offline    Completed without error       00%        11         -
# 4  Extended offline    Completed without error       00%         5         -

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.

Řešení dotazu:

Nástroje: Začni sledovat (0) ?

Odpovědi

22.1.2014 19:20 krtek
Rozbalit Rozbalit vše Re: Chyba s diskem v raidu - vadný disk, kabel.. ?

Co po několikáté projíždím ten výpis ze smartctl, je vidět, že disk asi nebude zdráv. Pro jistotu jsem udělal ještě jeden test znovu a to samé. Nechci si odpovědět sám - "disk je mrtvý..." ale tak nějak to vidím.

22.1.2014 19:40 Michal2
Rozbalit Rozbalit vše Re: Chyba s diskem v raidu - vadný disk, kabel.. ?

Podle smart ID 5 a 188 (BB) -> disk na ceste do vecnych lovist

22.1.2014 20:14 Michal Makovec | skóre: 22 | Prostějov
Rozbalit Rozbalit vše Re: Chyba s diskem v raidu - vadný disk, kabel.. ?

pokud je disk v záruce tak reklamovat, v opačném případě přemístit do sběrného dvora

  5 Reallocated_Sector_Ct   0x0033   051   051   036    Pre-fail  Always       -       64736
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       11643

Založit nové vlákno • Nahoru

Tiskni Sdílej: