Nie jesteś zalogowany.
Jeśli nie posiadasz konta, zarejestruj je już teraz! Pozwoli Ci ono w pełni korzystać z naszego serwisu. Spamerom dziękujemy!

Ogłoszenie

Prosimy o pomoc dla małej Julki — przekaż 1% podatku na Fundacji Dzieciom zdazyć z Pomocą.
Więcej informacji na dug.net.pl/pomagamy/.

Strony: 1

 

#1  2018-01-12 19:22:54

  Semerchet - Amator

Semerchet
Amator
Skąd: Koszalin
Zarejestrowany: 2007-04-14

Naprawy bad sektorów

Mamy na linuxa program w rodzaju mhdd?

Offline

 

#2  2018-01-12 20:09:59

  arecki - Użytkownik

arecki
Użytkownik
Skąd: 44 Bronson Lane Hensonville
Zarejestrowany: 2016-03-03

Re: Naprawy bad sektorów

whdd

Offline

 

#3  2018-02-07 20:14:21

  Novi-cjusz - Użytkownik

Novi-cjusz
Użytkownik
Zarejestrowany: 2013-03-05

Re: Naprawy bad sektorów

Jak zainstalowac WHDD na Ubuntu 17.10 ?
Komenda:

Kod:

 ./build.sh && sudo make install

nie dziala.
Mam dysk USB 2 TB z rozwalonym systemem plikow i przypuszczalnie partycji i ten program bardzo by mi sie przydal.

------------------------------------------------------------------------------------
"Inveniam viam aut faciam" : I will either find a way, or I shall make one
"Złoto to pieniądz królów, srebro to pieniądz dżentelmenów, barter to pieniądz chłopów ale dług to pieniądz niewolników."

Offline

 

#4  2018-02-07 20:21:02

  KerneLpaniC - Użytkownik

KerneLpaniC
Użytkownik
Skąd: 127.0.0.1
Zarejestrowany: 2016-08-09

Re: Naprawy bad sektorów

Nie lepiej skopiować gdzieś dane i załączyć gparted plus format ?

Offline

 

#5  2018-02-07 20:30:39

  lis6502 - Łowca lamerów

lis6502
Łowca lamerów
Skąd: Stalinogród
Zarejestrowany: 2008-12-04

Re: Naprawy bad sektorów

./build.sh && sudo make install
[b]nie dziala.[/b]
[color=red]nie dziala.[/color][/quote]
uwielbiam takich artystów.

jak nie działa to szukaj w google pod 'problem' ;]

Offline

 

#6  2018-02-07 20:34:18

  morfik - Cenzor wirtualnego świata

morfik
Cenzor wirtualnego świata
Skąd: ze WSI
Zarejestrowany: 2011-09-15
Serwis

Re: Naprawy bad sektorów

1. whdd chyba już nie jest rozwijany.
2. Jak masz "dysk USB 2 TB z rozwalonym systemem plikow i przypuszczalnie partycji", to whdd ci i tak w niczym nie pomoże. Lepiej sobie SMART zobacz. A jeśli tam w raporcie masz bad sektory, to ci tego już nic nie naprawi i dysk jest do wymiany, bo tych sektorów będzie przybywać i przechowywanie danych na tego typu nośniku nie jest rozważne.
3. Tak czy inaczej ja sobie kiedyś zbudował paczkę deb i wygląda, że działa u mnie na debian sid. Jak coś możesz ją zainstalować u siebie i zobaczyć czy działa:
https://app.box.com/s/g343qu6vx2iy49eq5aaougvo9kgpnlmk

Offline

 

#7  2018-02-07 21:23:39

  ciastek1981 - Użytkownik

ciastek1981
Użytkownik
Zarejestrowany: 2016-06-19

Re: Naprawy bad sektorów

To chyba o tego Seagate'a chodzi co kiedyś o nim pisał z NTFS. Wtedy pod Windą (pod warunkiem, że jest tam NTFS) można zrobić [b]chkdsk /r[/b] (z wiersza poleceń jako administrator), ale to przynajmniej kilkanaście godzin czekania przy 2 TB na USB 2.0 ;)

Ostatnio edytowany przez ciastek1981 (2018-02-07 21:26:34)

Burble, Burble, Burble ... hahaaaaaaa :D

Forum Linux Mint Polska http://forum.linuxmint.pl/

Offline

 

#8  2018-02-08 10:38:16

  Novi-cjusz - Użytkownik

Novi-cjusz
Użytkownik
Zarejestrowany: 2013-03-05

Re: Naprawy bad sektorów

@Morfik
Paczke sciagnolem, dziala, dziekuje..
O ten dysk chodzi:

Kod:

sudo fdisk -l
Disk /dev/sdc: 1.8 TiB, 1999664930816 bytes, 488199446 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x0001b9cc

Device     Boot Start       End   Sectors  Size Id Type
/dev/sdc1         256 488199423 488199168  1.8T  7 HPFS/NTFS/exFAT

Tak wyglada SMART:
[url=https://postimg.org/image/8q15wq7r9/][img]https://s18.postimg.org/8q15wq7r9/SMART.png[/img][/url]
@ciastek1981
Masz racje, wlasnie o ten dysk chodzi. Potrzebuje dysku, ktory bedzie uzywany rownoczesnie na Windows i Lnux.
Niestety pokazuje rozne pojemnosci i czas odczytu zwalnia w miare wielkosci uzywanych danych.
Gdybym wiedzial jak zresetowac dysk do ustawien fabrycznych ?????
Szkoda dysku - tylko 2600 godz pracy (;-(

------------------------------------------------------------------------------------
"Inveniam viam aut faciam" : I will either find a way, or I shall make one
"Złoto to pieniądz królów, srebro to pieniądz dżentelmenów, barter to pieniądz chłopów ale dług to pieniądz niewolników."

Offline

 

#9  2018-02-08 11:02:18

  morfik - Cenzor wirtualnego świata

morfik
Cenzor wirtualnego świata
Skąd: ze WSI
Zarejestrowany: 2011-09-15
Serwis

Re: Naprawy bad sektorów

Ten raport smart nie jest pełny. Weź tam wydaj:

Kod:

# smartctl -x /dev/sdc

Niestety pokazuje rozne pojemnosci i czas odczytu zwalnia w miare wielkosci uzywanych danych.[/quote]
Co to znaczy, bo w ogóle nie rozumiem tego zdania. xD

Przeskanowałeś dysk tym narzędziem whdd w stanie spoczynku? Wrzuć fotkę po zakończeniu.

Ostatnio edytowany przez morfik (2018-02-08 11:03:24)

Offline

 

#10  2018-02-08 13:33:34

  Novi-cjusz - Użytkownik

Novi-cjusz
Użytkownik
Zarejestrowany: 2013-03-05

Re: Naprawy bad sektorów

Kod:

smartctl -x /dev/sdc
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.13.0-32-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     SAMSUNG SpinPoint F4 EG (AF)
Device Model:     SAMSUNG HD204UI
Serial Number:    S2H7J1AB114610
LU WWN Device Id: 5 0024e9 004919e57
Firmware Version: 1AQ10001
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    5400 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Thu Feb  8 12:28:01 2018 GMT

==> WARNING: Using smartmontools or hdparm with this
drive may result in data loss due to a firmware bug.
****** THIS DRIVE MAY OR MAY NOT BE AFFECTED! ******
Buggy and fixed firmware report same version number!
See the following web pages for details:
http://knowledge.seagate.com/articles/en_US/FAQ/223571en
http://www.smartmontools.org/wiki/SamsungF4EGBadBlocks

SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Disabled
APM feature is:   Disabled
Rd look-ahead is: Enabled
Write cache is:   Enabled
ATA Security is:  Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: 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:      ( 121)    The previous self-test completed having
                    the read element of the test failed.
Total time to complete Offline 
data collection:         (21180) 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:      (   2) minutes.
Extended self-test routine
recommended polling time:      ( 353) minutes.
SCT capabilities:            (0x003f)    SCT Status supported.
                    SCT Error Recovery Control 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          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   100   100   051    -    27101
  2 Throughput_Performance  -OS--K   252   252   000    -    0
  3 Spin_Up_Time            PO---K   066   060   025    -    10311
  4 Start_Stop_Count        -O--CK   099   099   000    -    1491
  5 Reallocated_Sector_Ct   PO--CK   252   252   010    -    0
  7 Seek_Error_Rate         -OSR-K   252   252   051    -    0
  8 Seek_Time_Performance   --S--K   252   252   015    -    0
  9 Power_On_Hours          -O--CK   100   100   000    -    2400
 10 Spin_Retry_Count        -O--CK   252   252   051    -    0
 11 Calibration_Retry_Count -O--CK   252   252   000    -    0
 12 Power_Cycle_Count       -O--CK   099   099   000    -    1311
181 Program_Fail_Cnt_Total  -O---K   100   100   000    -    2
191 G-Sense_Error_Rate      -O---K   094   094   000    -    69484
192 Power-Off_Retract_Count -O---K   252   252   000    -    0
194 Temperature_Celsius     -O----   064   056   000    -    17 (Min/Max 10/44)
195 Hardware_ECC_Recovered  -O-RCK   100   100   000    -    0
196 Reallocated_Event_Count -O--CK   252   252   000    -    0
197 Current_Pending_Sector  -O--CK   099   097   000    -    132
198 Offline_Uncorrectable   ----CK   252   252   000    -    0
199 UDMA_CRC_Error_Count    -OS-CK   200   200   000    -    0
200 Multi_Zone_Error_Rate   -O-R-K   100   100   000    -    1
223 Load_Retry_Count        -O--CK   252   252   000    -    0
225 Load_Cycle_Count        -O--CK   100   100   000    -    1528
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O      2  Comprehensive SMART error log
0x03       GPL     R/O      2  Ext. Comprehensive SMART error log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O      2  Extended self-test log
0x08       GPL     R/O      2  Power Conditions log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  SATA NCQ Queued Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (2 sectors)
Device Error Count: 25458 (device log contains only the most recent 8 errors)
    CR     = Command Register
    FEATR  = Features Register
    COUNT  = Count (was: Sector Count) Register
    LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
    LH     = LBA High (was: Cylinder High) Register    ]   LBA
    LM     = LBA Mid (was: Cylinder Low) Register      ] Register
    LL     = LBA Low (was: Sector Number) Register     ]
    DV     = Device (was: Device/Head) Register
    DC     = Device Control Register
    ER     = Error register
    ST     = Status register
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 25458 [1] occurred at disk power-on lifetime: 2400 hours (100 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 e8 ca a7 f8 40 00  Error: UNC at LBA = 0xe8caa7f8 = 3905595384

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 08 00 00 e8 ca a7 f8 40 00     00:00:00.345  READ FPDMA QUEUED
  60 00 da 00 08 00 00 e8 ca a7 f8 40 00     00:00:00.405  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 00 00     00:00:00.405  READ LOG EXT
  60 00 00 00 08 00 00 e8 ca a7 f8 40 00     00:00:00.345  READ FPDMA QUEUED
  60 00 da 00 08 00 00 e8 ca a7 f8 40 00     00:00:00.399  READ FPDMA QUEUED

Error 25457 [0] occurred at disk power-on lifetime: 2400 hours (100 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 e8 ca a7 f8 40 00  Error: UNC at LBA = 0xe8caa7f8 = 3905595384

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 08 00 00 e8 ca a7 f8 40 00     00:00:00.345  READ FPDMA QUEUED
  60 00 da 00 08 00 00 e8 ca a7 f8 40 00     00:00:00.399  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 00 00     00:00:00.399  READ LOG EXT
  60 00 00 00 08 00 00 e8 ca a7 f8 40 00     00:00:00.345  READ FPDMA QUEUED
  60 00 da 00 08 00 00 e8 ca a7 f8 40 00     00:00:00.394  READ FPDMA QUEUED

Error 25456 [7] occurred at disk power-on lifetime: 2400 hours (100 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 e8 ca a7 f8 40 00  Error: UNC at LBA = 0xe8caa7f8 = 3905595384

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 08 00 00 e8 ca a7 f8 40 00     00:00:00.345  READ FPDMA QUEUED
  60 00 da 00 08 00 00 e8 ca a7 f8 40 00     00:00:00.394  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 00 00     00:00:00.394  READ LOG EXT
  60 00 00 00 08 00 00 e8 ca a7 f8 40 00     00:00:00.345  READ FPDMA QUEUED
  60 00 da 00 08 00 00 e8 ca a7 f8 40 00     00:00:00.389  READ FPDMA QUEUED

Error 25455 [6] occurred at disk power-on lifetime: 2400 hours (100 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 e8 ca a7 f8 40 00  Error: UNC at LBA = 0xe8caa7f8 = 3905595384

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 08 00 00 e8 ca a7 f8 40 00     00:00:00.345  READ FPDMA QUEUED
  60 00 da 00 08 00 00 e8 ca a7 f8 40 00     00:00:00.389  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 00 00     00:00:00.389  READ LOG EXT
  60 00 00 00 08 00 00 e8 ca a7 f8 40 00     00:00:00.345  READ FPDMA QUEUED
  60 00 da 00 08 00 00 e8 ca a7 f8 40 00     00:00:00.383  READ FPDMA QUEUED

Error 25454 [5] occurred at disk power-on lifetime: 2400 hours (100 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 e8 ca a7 f8 40 00  Error: UNC at LBA = 0xe8caa7f8 = 3905595384

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 08 00 00 e8 ca a7 f8 40 00     00:00:00.345  READ FPDMA QUEUED
  60 00 da 00 08 00 00 e8 ca a7 f8 40 00     00:00:00.383  READ FPDMA QUEUED
  b0 00 da 00 00 00 00 00 c2 4f 00 00 00     00:00:00.383  SMART RETURN STATUS
  b0 00 d0 00 00 00 00 00 c2 4f 00 00 00     00:00:00.382  SMART READ DATA
  e5 00 00 00 00 00 00 00 00 00 00 00 00     00:00:00.382  CHECK POWER MODE

Error 25453 [4] occurred at disk power-on lifetime: 2400 hours (100 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 e8 ca a7 f8 40 00  Error: UNC at LBA = 0xe8caa7f8 = 3905595384

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 08 00 00 e8 ca a7 f8 40 00     00:00:00.345  READ FPDMA QUEUED
  60 00 00 00 08 00 00 e8 ca a7 f8 40 00     00:00:00.377  READ FPDMA QUEUED
  60 00 00 00 08 00 00 00 00 08 08 40 00     00:00:00.377  READ FPDMA QUEUED
  60 00 00 00 08 00 00 00 00 08 00 40 00     00:00:00.377  READ FPDMA QUEUED
  60 00 00 00 08 00 00 e8 ca a7 f0 40 00     00:00:00.377  READ FPDMA QUEUED

Error 25452 [3] occurred at disk power-on lifetime: 2400 hours (100 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 e8 ca a5 b0 40 00  Error: UNC at LBA = 0xe8caa5b0 = 3905594800

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 08 00 00 e8 ca a5 b0 40 00     00:00:00.345  READ FPDMA QUEUED
  60 00 00 00 08 00 00 e8 ca a5 b0 40 00     00:00:00.372  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 00 00     00:00:00.372  READ LOG EXT
  60 00 00 00 08 00 00 e8 ca a5 b0 40 00     00:00:00.345  READ FPDMA QUEUED
  60 00 00 00 08 00 00 e8 ca a5 b0 40 00     00:00:00.367  READ FPDMA QUEUED

Error 25451 [2] occurred at disk power-on lifetime: 2399 hours (99 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 e8 ca a5 b0 40 00  Error: UNC at LBA = 0xe8caa5b0 = 3905594800

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 08 00 00 e8 ca a5 b0 40 00     00:00:00.345  READ FPDMA QUEUED
  60 00 00 00 08 00 00 e8 ca a5 b0 40 00     00:00:00.367  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 00 00     00:00:00.366  READ LOG EXT
  60 00 00 00 08 00 00 e8 ca a5 b0 40 00     00:00:00.345  READ FPDMA QUEUED
  60 00 00 00 08 00 00 e8 ca a5 b0 40 00     00:00:00.361  READ FPDMA QUEUED

SMART Extended Self-test Log Version: 1 (2 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%      2318         360712192
# 2  Short offline       Completed: read failure       90%      2318         171968512
# 3  Short offline       Completed: read failure       90%      2318         360712192
# 4  Extended offline    Completed: read failure       90%      2312         360712192
# 5  Extended offline    Aborted by host               90%      2312         -
# 6  Extended offline    Interrupted (host reset)      90%      2300         -
# 7  Short offline       Completed: read failure       70%      2300         360712192

SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Completed_read_failure [90% left] (0-65535)
    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.

SCT Status Version:                  2
SCT Version (vendor specific):       256 (0x0100)
SCT Support Level:                   1
Device State:                        Active (0)
Current Temperature:                    17 Celsius
Power Cycle Min/Max Temperature:     14/17 Celsius
Lifetime    Min/Max Temperature:     10/59 Celsius
Under/Over Temperature Limit Count:   0/0

SCT Temperature History Version:     2
Temperature Sampling Period:         5 minutes
Temperature Logging Interval:        5 minutes
Min/Max recommended Temperature:     -5/80 Celsius
Min/Max Temperature Limit:           -10/85 Celsius
Temperature History Size (Index):    128 (121)

Index    Estimated Time   Temperature Celsius
 122    2018-02-08 01:50    17  -
 123    2018-02-08 01:55    25  ******
 124    2018-02-08 02:00    26  *******
 125    2018-02-08 02:05    27  ********
 126    2018-02-08 02:10    28  *********
 127    2018-02-08 02:15    28  *********
   0    2018-02-08 02:20    26  *******
   1    2018-02-08 02:25    26  *******
   2    2018-02-08 02:30    27  ********
   3    2018-02-08 02:35    27  ********
   4    2018-02-08 02:40    28  *********
   5    2018-02-08 02:45    29  **********
   6    2018-02-08 02:50    29  **********
   7    2018-02-08 02:55    30  ***********
   8    2018-02-08 03:00    30  ***********
   9    2018-02-08 03:05    30  ***********
  10    2018-02-08 03:10    31  ************
 ...    ..(  3 skipped).    ..  ************
  14    2018-02-08 03:30    31  ************
  15    2018-02-08 03:35    32  *************
 ...    ..( 17 skipped).    ..  *************
  33    2018-02-08 05:05    32  *************
  34    2018-02-08 05:10    33  **************
  35    2018-02-08 05:15    33  **************
  36    2018-02-08 05:20    34  ***************
  37    2018-02-08 05:25    33  **************
 ...    ..(  7 skipped).    ..  **************
  45    2018-02-08 06:05    33  **************
  46    2018-02-08 06:10    32  *************
 ...    ..(  5 skipped).    ..  *************
  52    2018-02-08 06:40    32  *************
  53    2018-02-08 06:45    17  -
  54    2018-02-08 06:50    19  -
  55    2018-02-08 06:55    21  **
  56    2018-02-08 07:00    22  ***
  57    2018-02-08 07:05    23  ****
  58    2018-02-08 07:10    24  *****
  59    2018-02-08 07:15    25  ******
  60    2018-02-08 07:20    26  *******
  61    2018-02-08 07:25    26  *******
  62    2018-02-08 07:30    27  ********
  63    2018-02-08 07:35    27  ********
  64    2018-02-08 07:40    28  *********
  65    2018-02-08 07:45    28  *********
  66    2018-02-08 07:50    28  *********
  67    2018-02-08 07:55    29  **********
  68    2018-02-08 08:00    29  **********
  69    2018-02-08 08:05    30  ***********
 ...    ..(  2 skipped).    ..  ***********
  72    2018-02-08 08:20    30  ***********
  73    2018-02-08 08:25    31  ************
 ...    ..(  7 skipped).    ..  ************
  81    2018-02-08 09:05    31  ************
  82    2018-02-08 09:10    17  -
  83    2018-02-08 09:15    19  -
  84    2018-02-08 09:20    20  *
  85    2018-02-08 09:25    21  **
  86    2018-02-08 09:30    22  ***
  87    2018-02-08 09:35    22  ***
  88    2018-02-08 09:40    23  ****
  89    2018-02-08 09:45    23  ****
  90    2018-02-08 09:50    24  *****
  91    2018-02-08 09:55    24  *****
  92    2018-02-08 10:00    24  *****
  93    2018-02-08 10:05    25  ******
  94    2018-02-08 10:10    26  *******
  95    2018-02-08 10:15    27  ********
 ...    ..( 19 skipped).    ..  ********
 115    2018-02-08 11:55    27  ********
 116    2018-02-08 12:00    14  -
 117    2018-02-08 12:05    15  -
 118    2018-02-08 12:10    17  -
 119    2018-02-08 12:15    18  -
 120    2018-02-08 12:20    20  *
 121    2018-02-08 12:25    16  -

SCT Error Recovery Control:
           Read: Disabled
          Write: Disabled

Device Statistics (GP/SMART Log 0x04) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  4            0  Command failed due to ICRC error
0x0002  4            0  R_ERR response for data FIS
0x0003  4            0  R_ERR response for device-to-host data FIS
0x0004  4            0  R_ERR response for host-to-device data FIS
0x0005  4            0  R_ERR response for non-data FIS
0x0006  4            0  R_ERR response for device-to-host non-data FIS
0x0007  4            0  R_ERR response for host-to-device non-data FIS
0x0008  4            0  Device-to-host non-data FIS retries
0x0009  4            1  Transition from drive PhyRdy to drive PhyNRdy
0x000a  4            0  Device-to-host register FISes sent due to a COMRESET
0x000b  4            0  CRC errors within host-to-device FIS
0x000d  4            0  Non-CRC errors within host-to-device FIS
0x000f  4            0  R_ERR response for host-to-device data FIS, CRC
0x0010  4            0  R_ERR response for host-to-device data FIS, non-CRC
0x0012  4            0  R_ERR response for host-to-device non-data FIS, CRC
0x0013  4            0  R_ERR response for host-to-device non-data FIS, non-CRC
0x8e00  4            0  Vendor specific
0x8e01  4            0  Vendor specific
0x8e02  4            0  Vendor specific
0x8e03  4            0  Vendor specific
0x8e04  4            0  Vendor specific
0x8e05  4            0  Vendor specific
0x8e06  4            0  Vendor specific
0x8e07  4            0  Vendor specific
0x8e08  4            0  Vendor specific
0x8e09  4            0  Vendor specific
0x8e0a  4            0  Vendor specific
0x8e0b  4            0  Vendor specific
0x8e0c  4            0  Vendor specific
0x8e0d  4            0  Vendor specific
0x8e0e  4            0  Vendor specific
0x8e0f  4            0  Vendor specific
0x8e10  4            0  Vendor specific
0x8e11  4            0  Vendor specific

Niestety pokazuje rozne pojemnosci i czas odczytu zwalnia w miare wielkosci uzywanych danych.[/quote]
Wyjasnienie, przyklad:
- dla pliku wielkosci 1MB - szybkosc odczytu i zapisu - normalna.
- dla folderu wielkosci 1 TB - szybkosc oczytu i zapisu malejaca az do zatrzymania.

Przeskanowałeś dysk tym narzędziem whdd w stanie spoczynku? Wrzuć fotkę po zakończeniu.[/quote]
Skan na tym dysku nie dziala.

------------------------------------------------------------------------------------
"Inveniam viam aut faciam" : I will either find a way, or I shall make one
"Złoto to pieniądz królów, srebro to pieniądz dżentelmenów, barter to pieniądz chłopów ale dług to pieniądz niewolników."

Offline

 

#11  2018-02-08 13:45:59

  yossarian - Szczawiożerca

yossarian
Szczawiożerca
Skąd: Shangri-La
Zarejestrowany: 2011-04-25

Re: Naprawy bad sektorów

Kod:

197 Current_Pending_Sector  -O--CK   099   097   000    -    132

[/quote]
Jeśli te „tymczasowe problemy” nie znikną, to oznacza, że dysk zdycha.

To znów chodzi o ten totalnie zapełniony, ogromny dysk z tylko jedną partycją NTFS?
Już wtedy wiedziałeś, że nie ma to żadnego sensu i o sensownym działaniu pod Linuksem możesz zapomnieć.

Offline

 

#12  2018-02-08 13:59:17

  Novi-cjusz - Użytkownik

Novi-cjusz
Użytkownik
Zarejestrowany: 2013-03-05

Re: Naprawy bad sektorów

No to co robic?
Dostalem takiego automatycznego emaila:

Kod:

From root@robin-desktop  Thu Feb  8 09:19:26 2018
Return-Path: <root@robin-desktop>
X-Original-To: root@robin-desktop
Delivered-To: root@robin-desktop
Received: by robin-desktop.local (Postfix, from userid 0)
    id C338A2E0FC3; Thu,  8 Feb 2018 09:19:26 +0000 (GMT)
Subject: SMART error (CurrentPendingSector) detected on host: robin-desktop
To: <root@robin-desktop>
X-Mailer: mail (GNU Mailutils 3.1.1)
Message-Id: <20180208091926.C338A2E0FC3@robin-desktop.local>
Date: Thu,  8 Feb 2018 09:19:26 +0000 (GMT)
From: root@robin-desktop (root)

This message was generated by the smartd daemon running on:

   host name:  robin-desktop
   DNS domain: [Empty]

The following warning/error was logged by the smartd daemon:

Device: /dev/sdc [SAT], 132 Currently unreadable (pending) sectors

Device info:
SAMSUNG HD204UI, S/N:S2H7J1AB114610, WWN:5-0024e9-004919e57, FW:1AQ10001, 2.00 TB

For details see host's SYSLOG.

You can also use the smartctl utility for further investigation.
Another message will be sent in 24 hours if the problem persists.

From root@robin-desktop  Thu Feb  8 12:20:00 2018
Return-Path: <root@robin-desktop>
X-Original-To: root@robin-desktop
Delivered-To: root@robin-desktop
Received: by robin-desktop.local (Postfix, from userid 0)
    id 32F6B2E284D; Thu,  8 Feb 2018 12:20:00 +0000 (GMT)
Subject: SMART error (FailedOpenDevice) detected on host: robin-desktop
To: <root@robin-desktop>
X-Mailer: mail (GNU Mailutils 3.1.1)
Message-Id: <20180208122000.32F6B2E284D@robin-desktop.local>
Date: Thu,  8 Feb 2018 12:20:00 +0000 (GMT)
From: root@robin-desktop (root)

This message was generated by the smartd daemon running on:

   host name:  robin-desktop
   DNS domain: [Empty]

The following warning/error was logged by the smartd daemon:

Device: /dev/sdc [SAT], unable to open device

Device info:
SAMSUNG HD204UI, S/N:S2H7J1AB114610, WWN:5-0024e9-004919e57, FW:1AQ10001, 2.00 TB

For details see host's SYSLOG.

You can also use the smartctl utility for further investigation.
Another message will be sent in 24 hours if the problem persists.

From root@robin-desktop  Thu Feb  8 12:50:00 2018
Return-Path: <root@robin-desktop>
X-Original-To: root@robin-desktop
Delivered-To: root@robin-desktop
Received: by robin-desktop.local (Postfix, from userid 0)
    id 909A42E2977; Thu,  8 Feb 2018 12:50:00 +0000 (GMT)
Subject: SMART error (SelfTest) detected on host: robin-desktop
To: <root@robin-desktop>
X-Mailer: mail (GNU Mailutils 3.1.1)
Message-Id: <20180208125000.909A42E2977@robin-desktop.local>
Date: Thu,  8 Feb 2018 12:50:00 +0000 (GMT)
From: root@robin-desktop (root)

This message was generated by the smartd daemon running on:

   host name:  robin-desktop
   DNS domain: [Empty]

The following warning/error was logged by the smartd daemon:

Device: /dev/sdc [SAT], Self-Test Log error count increased from 0 to 5

Device info:
SAMSUNG HD204UI, S/N:S2H7J1AB114610, WWN:5-0024e9-004919e57, FW:1AQ10001, 2.00 TB

For details see host's SYSLOG.

You can also use the smartctl utility for further investigation.
Another message will be sent in 24 hours if the problem persists.

kern.log mowi ze:

Kod:

Feb  8 12:21:22 robin-desktop kernel: [15829.132288] sd 8:0:0:0: [sdc] 488199446 4096-byte logical blocks: (2.00 TB/1.82 TiB)
Feb  8 12:21:22 robin-desktop kernel: [15829.186514] sd 8:0:0:0: [sdc] Write Protect is off
Feb  8 12:21:22 robin-desktop kernel: [15829.186519] sd 8:0:0:0: [sdc] Mode Sense: 10 00 00 00
Feb  8 12:21:22 robin-desktop kernel: [15829.217885] sr 8:0:0:1: [sr1] scsi-1 drive
Feb  8 12:21:22 robin-desktop kernel: [15829.218226] sr 8:0:0:1: Attached scsi CD-ROM sr1
Feb  8 12:21:22 robin-desktop kernel: [15829.218365] sr 8:0:0:1: Attached scsi generic sg4 type 5
Feb  8 12:21:22 robin-desktop kernel: [15829.240388] sd 8:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb  8 12:21:22 robin-desktop kernel: [15829.479798]  sdc: sdc1
Feb  8 12:21:23 robin-desktop kernel: [15829.682445] sd 8:0:0:0: [sdc] Attached SCSI disk
Feb  8 12:21:57 robin-desktop kernel: [15864.031397] sd 8:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb  8 12:21:57 robin-desktop kernel: [15864.031404] sd 8:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current] 
Feb  8 12:21:57 robin-desktop kernel: [15864.031407] sd 8:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
Feb  8 12:21:57 robin-desktop kernel: [15864.031412] sd 8:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 1d 19 54 a5 00 00 15 00
Feb  8 12:21:57 robin-desktop kernel: [15864.031415] print_req_error: I/O error, dev sdc, sector 3905594664
Feb  8 12:22:31 robin-desktop kernel: [15898.462896] sd 8:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb  8 12:22:31 robin-desktop kernel: [15898.462902] sd 8:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current] 
Feb  8 12:22:31 robin-desktop kernel: [15898.462905] sd 8:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
Feb  8 12:22:31 robin-desktop kernel: [15898.462910] sd 8:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 1d 19 54 b6 00 00 01 00
Feb  8 12:22:31 robin-desktop kernel: [15898.462913] print_req_error: I/O error, dev sdc, sector 3905594800
Feb  8 12:22:31 robin-desktop kernel: [15898.462921] Buffer I/O error on dev sdc, logical block 488199350, async page read
Feb  8 12:23:04 robin-desktop kernel: [15931.050872] sd 8:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb  8 12:23:04 robin-desktop kernel: [15931.050879] sd 8:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current] 
Feb  8 12:23:04 robin-desktop kernel: [15931.050882] sd 8:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
Feb  8 12:23:04 robin-desktop kernel: [15931.050887] sd 8:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 1d 19 54 ff 00 00 01 00
Feb  8 12:23:04 robin-desktop kernel: [15931.050890] print_req_error: I/O error, dev sdc, sector 3905595384
Feb  8 12:23:36 robin-desktop kernel: [15963.440495] sd 8:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb  8 12:23:36 robin-desktop kernel: [15963.440501] sd 8:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current] 
Feb  8 12:23:36 robin-desktop kernel: [15963.440505] sd 8:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
Feb  8 12:23:36 robin-desktop kernel: [15963.440509] sd 8:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 1d 19 54 ff 00 00 01 00
Feb  8 12:23:36 robin-desktop kernel: [15963.440513] print_req_error: I/O error, dev sdc, sector 3905595384
Feb  8 12:23:36 robin-desktop kernel: [15963.440520] Buffer I/O error on dev sdc1, logical block 488199167, async page read
Feb  8 12:24:07 robin-desktop kernel: [15994.307648] usb 3-4: reset high-speed USB device number 4 using ehci-pci
Feb  8 12:24:08 robin-desktop kernel: [15994.520688]  sdc: sdc1
Feb  8 12:24:08 robin-desktop kernel: [15994.667019]  sdc: sdc1
Feb  8 12:24:08 robin-desktop kernel: [15994.737635]  sdc: sdc1
Feb  8 12:24:43 robin-desktop kernel: [16029.905921] sd 8:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb  8 12:24:43 robin-desktop kernel: [16029.905927] sd 8:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current] 
Feb  8 12:24:43 robin-desktop kernel: [16029.905930] sd 8:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
Feb  8 12:24:43 robin-desktop kernel: [16029.905935] sd 8:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 1d 19 54 a5 00 00 15 00
Feb  8 12:24:43 robin-desktop kernel: [16029.905938] print_req_error: I/O error, dev sdc, sector 3905594664
Feb  8 12:25:15 robin-desktop kernel: [16062.250927] sd 8:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb  8 12:25:15 robin-desktop kernel: [16062.250933] sd 8:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current] 
Feb  8 12:25:15 robin-desktop kernel: [16062.250936] sd 8:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
Feb  8 12:25:15 robin-desktop kernel: [16062.250941] sd 8:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 1d 19 54 b6 00 00 01 00
Feb  8 12:25:15 robin-desktop kernel: [16062.250944] print_req_error: I/O error, dev sdc, sector 3905594800
Feb  8 12:25:15 robin-desktop kernel: [16062.250951] Buffer I/O error on dev sdc, logical block 488199350, async page read
Feb  8 12:25:48 robin-desktop kernel: [16094.948767] sd 8:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb  8 12:25:48 robin-desktop kernel: [16094.948773] sd 8:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current] 
Feb  8 12:25:48 robin-desktop kernel: [16094.948776] sd 8:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
Feb  8 12:25:48 robin-desktop kernel: [16094.948780] sd 8:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 1d 19 54 ff 00 00 01 00
Feb  8 12:25:48 robin-desktop kernel: [16094.948784] print_req_error: I/O error, dev sdc, sector 3905595384
Feb  8 12:25:48 robin-desktop kernel: [16094.948791] Buffer I/O error on dev sdc1, logical block 488199167, async page read
Feb  8 12:26:22 robin-desktop kernel: [16128.839217] sd 8:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb  8 12:26:22 robin-desktop kernel: [16128.839223] sd 8:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current] 
Feb  8 12:26:22 robin-desktop kernel: [16128.839226] sd 8:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
Feb  8 12:26:22 robin-desktop kernel: [16128.839230] sd 8:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 1d 19 54 b6 00 00 01 00
Feb  8 12:26:22 robin-desktop kernel: [16128.839234] print_req_error: I/O error, dev sdc, sector 3905594800
Feb  8 12:26:22 robin-desktop kernel: [16128.839241] Buffer I/O error on dev sdc, logical block 488199350, async page read
Feb  8 12:26:54 robin-desktop kernel: [16161.459569] sd 8:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb  8 12:26:54 robin-desktop kernel: [16161.459575] sd 8:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current] 
Feb  8 12:26:54 robin-desktop kernel: [16161.459578] sd 8:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
Feb  8 12:26:54 robin-desktop kernel: [16161.459583] sd 8:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 1d 19 54 ff 00 00 01 00
Feb  8 12:26:54 robin-desktop kernel: [16161.459586] print_req_error: I/O error, dev sdc, sector 3905595384
Feb  8 12:26:54 robin-desktop kernel: [16161.459606] Buffer I/O error on dev sdc1, logical block 488199167, async page read
Feb  8 12:27:28 robin-desktop kernel: [16194.577742] sd 8:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb  8 12:27:28 robin-desktop kernel: [16194.577748] sd 8:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current] 
Feb  8 12:27:28 robin-desktop kernel: [16194.577751] sd 8:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
Feb  8 12:27:28 robin-desktop kernel: [16194.577756] sd 8:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 1d 19 54 b6 00 00 01 00
Feb  8 12:27:28 robin-desktop kernel: [16194.577760] print_req_error: I/O error, dev sdc, sector 3905594800
Feb  8 12:27:28 robin-desktop kernel: [16194.577767] Buffer I/O error on dev sdc, logical block 488199350, async page read
Feb  8 12:28:00 robin-desktop kernel: [16227.440933] sd 8:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb  8 12:28:00 robin-desktop kernel: [16227.440939] sd 8:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current] 
Feb  8 12:28:00 robin-desktop kernel: [16227.440943] sd 8:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
Feb  8 12:28:00 robin-desktop kernel: [16227.440947] sd 8:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 1d 19 54 ff 00 00 01 00
Feb  8 12:28:00 robin-desktop kernel: [16227.440950] print_req_error: I/O error, dev sdc, sector 3905595384
Feb  8 12:28:00 robin-desktop kernel: [16227.440958] Buffer I/O error on dev sdc1, logical block 488199167, async page read
Feb  8 12:28:36 robin-desktop kernel: [16262.634728] sd 8:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb  8 12:28:36 robin-desktop kernel: [16262.634734] sd 8:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current] 
Feb  8 12:28:36 robin-desktop kernel: [16262.634738] sd 8:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
Feb  8 12:28:36 robin-desktop kernel: [16262.634742] sd 8:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 1d 19 54 b6 00 00 01 00
Feb  8 12:28:36 robin-desktop kernel: [16262.634745] print_req_error: I/O error, dev sdc, sector 3905594800
Feb  8 12:28:36 robin-desktop kernel: [16262.634753] Buffer I/O error on dev sdc, logical block 488199350, async page read
Feb  8 12:29:08 robin-desktop kernel: [16294.558164] sd 8:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb  8 12:29:08 robin-desktop kernel: [16294.558170] sd 8:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current] 
Feb  8 12:29:08 robin-desktop kernel: [16294.558173] sd 8:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
Feb  8 12:29:08 robin-desktop kernel: [16294.558177] sd 8:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 1d 19 54 ff 00 00 01 00
Feb  8 12:29:08 robin-desktop kernel: [16294.558181] print_req_error: I/O error, dev sdc, sector 3905595384
Feb  8 12:29:08 robin-desktop kernel: [16294.558188] Buffer I/O error on dev sdc1, logical block 488199167, async page read
Feb  8 12:38:27 robin-desktop kernel: [16854.483382] usb 3-4: reset high-speed USB device number 4 using ehci-pci
Feb  8 12:38:28 robin-desktop kernel: [16854.696643]  sdc: sdc1
Feb  8 12:38:28 robin-desktop kernel: [16854.814377]  sdc: sdc1
Feb  8 12:38:28 robin-desktop kernel: [16854.911861]  sdc: sdc1
Feb  8 12:39:01 robin-desktop kernel: [16888.442455] sd 8:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb  8 12:39:01 robin-desktop kernel: [16888.442461] sd 8:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current] 
Feb  8 12:39:01 robin-desktop kernel: [16888.442464] sd 8:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
Feb  8 12:39:01 robin-desktop kernel: [16888.442469] sd 8:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 1d 19 54 b6 00 00 01 00
Feb  8 12:39:01 robin-desktop kernel: [16888.442472] print_req_error: I/O error, dev sdc, sector 3905594800
Feb  8 12:39:01 robin-desktop kernel: [16888.442479] Buffer I/O error on dev sdc, logical block 488199350, async page read
Feb  8 12:39:16 robin-desktop kernel: [16903.444517] traps: whdd[16245] general protection ip:7ffd5fbe6380 sp:7f1caca28f08 error:0
Feb  8 12:39:33 robin-desktop kernel: [16920.323780] sd 8:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb  8 12:39:33 robin-desktop kernel: [16920.323786] sd 8:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current] 
Feb  8 12:39:33 robin-desktop kernel: [16920.323790] sd 8:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
Feb  8 12:39:33 robin-desktop kernel: [16920.323794] sd 8:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 1d 19 54 ff 00 00 01 00
Feb  8 12:39:33 robin-desktop kernel: [16920.323797] print_req_error: I/O error, dev sdc, sector 3905595384
Feb  8 12:39:33 robin-desktop kernel: [16920.323804] Buffer I/O error on dev sdc1, logical block 488199167, async page read
Feb  8 12:40:07 robin-desktop kernel: [16954.059488] sd 8:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb  8 12:40:07 robin-desktop kernel: [16954.059494] sd 8:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current] 
Feb  8 12:40:07 robin-desktop kernel: [16954.059497] sd 8:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
Feb  8 12:40:07 robin-desktop kernel: [16954.059502] sd 8:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 1d 19 54 b6 00 00 01 00
Feb  8 12:40:07 robin-desktop kernel: [16954.059506] print_req_error: I/O error, dev sdc, sector 3905594800
Feb  8 12:40:07 robin-desktop kernel: [16954.059512] Buffer I/O error on dev sdc, logical block 488199350, async page read
Feb  8 12:40:39 robin-desktop kernel: [16986.029271] sd 8:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb  8 12:40:39 robin-desktop kernel: [16986.029278] sd 8:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current] 
Feb  8 12:40:39 robin-desktop kernel: [16986.029281] sd 8:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
Feb  8 12:40:39 robin-desktop kernel: [16986.029286] sd 8:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 1d 19 54 ff 00 00 01 00
Feb  8 12:40:39 robin-desktop kernel: [16986.029289] print_req_error: I/O error, dev sdc, sector 3905595384
Feb  8 12:40:39 robin-desktop kernel: [16986.029297] Buffer I/O error on dev sdc1, logical block 488199167, async page read
Feb  8 12:41:13 robin-desktop kernel: [17019.819606] sd 8:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb  8 12:41:13 robin-desktop kernel: [17019.819612] sd 8:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current] 
Feb  8 12:41:13 robin-desktop kernel: [17019.819616] sd 8:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
Feb  8 12:41:13 robin-desktop kernel: [17019.819621] sd 8:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 1d 19 54 b6 00 00 01 00
Feb  8 12:41:13 robin-desktop kernel: [17019.819624] print_req_error: I/O error, dev sdc, sector 3905594800
Feb  8 12:41:13 robin-desktop kernel: [17019.819631] Buffer I/O error on dev sdc, logical block 488199350, async page read
Feb  8 12:41:28 robin-desktop kernel: [17035.014019] Web Content[16273]: segfault at fffe8 ip 00007fb65ccf7c81 sp 00007fffd0007b80 error 4 in libxul.so[7fb659113000+4e18000]
Feb  8 12:41:45 robin-desktop kernel: [17051.634554] sd 8:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb  8 12:41:45 robin-desktop kernel: [17051.634559] sd 8:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current] 
Feb  8 12:41:45 robin-desktop kernel: [17051.634562] sd 8:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
Feb  8 12:41:45 robin-desktop kernel: [17051.634566] sd 8:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 1d 19 54 ff 00 00 01 00
Feb  8 12:41:45 robin-desktop kernel: [17051.634569] print_req_error: I/O error, dev sdc, sector 3905595384
Feb  8 12:41:45 robin-desktop kernel: [17051.634575] Buffer I/O error on dev sdc1, logical block 488199167, async page read
Feb  8 12:45:49 robin-desktop kernel: [17296.171733] SGI XFS with ACLs, security attributes, realtime, no debug enabled
Feb  8 12:45:49 robin-desktop kernel: [17296.235048] JFS: nTxBlock = 8192, nTxLock = 65536
Feb  8 12:45:49 robin-desktop kernel: [17296.344364] ntfs: driver 2.1.32 [Flags: R/O MODULE].
Feb  8 12:45:49 robin-desktop kernel: [17296.417120] QNX4 filesystem 0.2.3 registered.
Feb  8 12:45:50 robin-desktop kernel: [17296.535593] raid6: sse2x1   gen()  2430 MB/s
Feb  8 12:45:50 robin-desktop kernel: [17296.583588] raid6: sse2x1   xor()  1595 MB/s
Feb  8 12:45:50 robin-desktop kernel: [17296.631579] raid6: sse2x2   gen()  3593 MB/s
Feb  8 12:45:50 robin-desktop kernel: [17296.679586] raid6: sse2x2   xor()  2566 MB/s
Feb  8 12:45:50 robin-desktop kernel: [17296.727591] raid6: sse2x4   gen()  4373 MB/s
Feb  8 12:45:50 robin-desktop kernel: [17296.775590] raid6: sse2x4   xor()  2744 MB/s
Feb  8 12:45:50 robin-desktop kernel: [17296.775593] raid6: using algorithm sse2x4 gen() 4373 MB/s
Feb  8 12:45:50 robin-desktop kernel: [17296.775595] raid6: .... xor() 2744 MB/s, rmw enabled
Feb  8 12:45:50 robin-desktop kernel: [17296.775597] raid6: using ssse3x2 recovery algorithm
Feb  8 12:45:50 robin-desktop kernel: [17296.786539] xor: automatically using best checksumming function   avx       
Feb  8 12:45:50 robin-desktop kernel: [17296.865849] Btrfs loaded, crc32c=crc32c-intel
Feb  8 12:46:32 robin-desktop kernel: [17339.072545] sd 8:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb  8 12:46:32 robin-desktop kernel: [17339.072551] sd 8:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current] 
Feb  8 12:46:32 robin-desktop kernel: [17339.072554] sd 8:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
Feb  8 12:46:32 robin-desktop kernel: [17339.072559] sd 8:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 1d 19 54 ff 00 00 01 00
Feb  8 12:46:32 robin-desktop kernel: [17339.072562] print_req_error: I/O error, dev sdc, sector 3905595384
Feb  8 12:46:32 robin-desktop kernel: [17339.072569] Buffer I/O error on dev sdc1, logical block 488199167, async page read
Feb  8 12:47:59 robin-desktop kernel: [17426.303482] sd 8:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb  8 12:47:59 robin-desktop kernel: [17426.303488] sd 8:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current] 
Feb  8 12:47:59 robin-desktop kernel: [17426.303492] sd 8:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
Feb  8 12:47:59 robin-desktop kernel: [17426.303496] sd 8:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 1d 19 54 ff 00 00 01 00
Feb  8 12:47:59 robin-desktop kernel: [17426.303499] print_req_error: I/O error, dev sdc, sector 3905595384
Feb  8 12:47:59 robin-desktop kernel: [17426.303506] Buffer I/O error on dev sdc1, logical block 488199167, async page read
Feb  8 12:49:39 robin-desktop kernel: [17525.855201] sd 8:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb  8 12:49:39 robin-desktop kernel: [17525.855207] sd 8:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current] 
Feb  8 12:49:39 robin-desktop kernel: [17525.855211] sd 8:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
Feb  8 12:49:39 robin-desktop kernel: [17525.855215] sd 8:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 1d 19 54 ff 00 00 01 00
Feb  8 12:49:39 robin-desktop kernel: [17525.855218] print_req_error: I/O error, dev sdc, sector 3905595384
Feb  8 12:49:39 robin-desktop kernel: [17525.855226] Buffer I/O error on dev sdc1, logical block 488199167, async page read
Feb  8 12:51:05 robin-desktop kernel: [17612.501838] sd 8:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb  8 12:51:05 robin-desktop kernel: [17612.501845] sd 8:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current] 
Feb  8 12:51:05 robin-desktop kernel: [17612.501848] sd 8:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
Feb  8 12:51:05 robin-desktop kernel: [17612.501852] sd 8:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 1d 19 54 ff 00 00 01 00
Feb  8 12:51:05 robin-desktop kernel: [17612.501856] print_req_error: I/O error, dev sdc, sector 3905595384
Feb  8 12:51:05 robin-desktop kernel: [17612.501898] Buffer I/O error on dev sdc1, logical block 488199167, async page read

Chcialem wyselekcjonowac ze wszystkich logow tylko te dotyczace dysku "sdc"
ale ta komenda:

Kod:

dmesg | grep sdc

jest chyba niekompletna.

Ostatnio edytowany przez Novi-cjusz (2018-02-08 14:13:16)

------------------------------------------------------------------------------------
"Inveniam viam aut faciam" : I will either find a way, or I shall make one
"Złoto to pieniądz królów, srebro to pieniądz dżentelmenów, barter to pieniądz chłopów ale dług to pieniądz niewolników."

Offline

 

#13  2018-02-08 14:11:13

  morfik - Cenzor wirtualnego świata

morfik
Cenzor wirtualnego świata
Skąd: ze WSI
Zarejestrowany: 2011-09-15
Serwis

Re: Naprawy bad sektorów

No masz pliki rezydujące na uszkodzonych sektorach, z których system nie jest w stanie odczytać danych, dlatego pojawiają się błędy i to wiesza system i sprawia, że doświadczasz tych problemów które masz. Rada jest prosta, wywal pliki, rezydujące na tych uszkodzonych sektorach i może będzie lepiej ale sądząc po tym, że tych sektorów jest prawie 200, to ten dysk się nadaje już na złom, chyba że masz gwarancje na niego, to go zwróć. Ja bym go zaorał i przepisał zerami, by uwolnić uszkodzone bloki i sprawdzić czy pojawią się nowe bady.

Offline

 

#14  2018-02-08 23:46:36

  Novi-cjusz - Użytkownik

Novi-cjusz
Użytkownik
Zarejestrowany: 2013-03-05

Re: Naprawy bad sektorów

Podzielilem dysk na 2 rowne partycje.

Kod:

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1             256 244100351 244100096 931.2G 83 Linux
/dev/sda2       244100352 488199445 244099094 931.2G  6 FAT16

https://pastebin.com/p5phBCmg
W pierwszej mam klopot bo podczas tworzenia systemu plikow wywala error:
[url=https://postimg.org/image/4nxkddq8l/][img]https://s18.postimg.org/4nxkddq8l/Error_formating_partition.png[/img][/url]
Najprawdopodobniej uszkodzony jest "magic number" w superblocku.
Zastosowanie innego superblocku z backupu - nie pomaga.

Kod:

e2fsck -b 8193 /dev/sdc1

Nie majac systemu plikow - nie moge zamontowac.
Jak naprawic ten "magic number"?
Gdyby udalo sie naprawic ten blad to bym odzyskal dysk poniewaz druga partycja smiga, na 100%.

Ostatnio edytowany przez Novi-cjusz (2018-02-09 15:40:32)

------------------------------------------------------------------------------------
"Inveniam viam aut faciam" : I will either find a way, or I shall make one
"Złoto to pieniądz królów, srebro to pieniądz dżentelmenów, barter to pieniądz chłopów ale dług to pieniądz niewolników."

Offline

 

#15  2018-02-09 11:23:05

  andreq - Członek DUG

andreq
Członek DUG
Skąd: Nisko
Zarejestrowany: 2005-01-11

Re: Naprawy bad sektorów

Jesteś pewien co robisz? Bo na początku piszesz o partycji /dev/sda1 a mkfs.ext4 i e2fsck uruchamiasz na /dev/sdc1?????

Zrobiłeś to co proponował morfik? Jeśli nie to to zrób.

Po drugie. Jak chcesz naprawić system plików /dev/sdc1 lub go zamontować jak nie został on poprawnie utworzony, gdyż mkfs nie może zapisać superbloku, z dużą pewnością z powodu uszkodzenia sektorów dysku?

Zawsze możesz podać mkfs listę uszkodzonych sektorów zrobionych przy pomocy badblocks, tylko uprzedzając nie zapisuj tej listy na jakiejkolwiek partycji tego potencjalne uszkodzonego dysku!

Kod:

# badblocks -o lista_uszkodzonych_bloków /dev/sdc1
# mkfs.ext4 -v -l lista_uszkodzonych_bloków  /dev/sdc1

Pamiętaj trzymanie danych na potencjalnie uszkodzonym dysku to ryzyko, że możesz je stracić.

Ostatnio edytowany przez andreq (2018-02-09 12:22:06)

Offline

 

#16  2018-02-09 15:57:38

  Novi-cjusz - Użytkownik

Novi-cjusz
Użytkownik
Zarejestrowany: 2013-03-05

Re: Naprawy bad sektorów

Jesteś pewien co robisz? Bo na początku piszesz o partycji /dev/sda1 a mkfs.ext4 i e2fsck uruchamiasz na /dev/sdc1?????[/quote]
Rozne narzedzia dawaly rozne odczyty, mysle ze ze wzgledu na bledny system plikow.
Korzystalem z:
- GParted
- natywnego "disks" z dashbord.
Teraz korzystam wylacznie z wiersza poleceni:

Kod:

sudo fdisk -l
Disk /dev/loop0: 179.3 MiB, 187953152 bytes, 367096 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 184.1 MiB, 193036288 bytes, 377024 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 81.3 MiB, 85291008 bytes, 166584 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0006d088

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1            2048 123074313 123072266  58.7G 83 Linux
/dev/sda2  *    123074560 245926122 122851563  58.6G 83 Linux
/dev/sda3       245927936 368834185 122906250  58.6G 83 Linux
/dev/sda4       368836606 617381887 248545282 118.5G  5 Extended
/dev/sda5       368836608 379078655  10242048   4.9G 82 Linux swap / Solaris
/dev/sda6       432064512 494161919  62097408  29.6G 83 Linux
/dev/sda7       494163968 617381887 123217920  58.8G 83 Linux
/dev/sda8       379080704 432062463  52981760  25.3G 83 Linux

Partition table entries are not in disk order.




Disk /dev/sdb: 1.8 TiB, 1999664930816 bytes, 488199446 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x0000daf8

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sdb1             256 244100351 244100096 931.2G 83 Linux
/dev/sdb2       244100352 488199445 244099094 931.2G  6 FAT16

Dot /dev/sdb

Zrobiłeś to co proponował morfik? Jeśli nie to to zrób.[/quote]
Zerowanie dysku zamierzam zrobic w weekend, nastepujacym poleceniem:

Kod:

dd if=/dev/zero of=/dev/sdb bs=1M

Na tej stronie: https://forum.hddguru.com/viewtopic.php?t=12415&start=
znalazlem plik:  ext2-superblock.c
Odpalilem i miele, tylko nie bardzo rozumiem jaki jest wynik tego mielenia.
https://pastebin.com/u78FkUcT
Domyslam sie, ze listuje superbloki ???

Kod:

mkfs.ext4 -v -l lista_uszkodzonych_bloków  /dev/sdb
mke2fs 1.43.5 (04-Aug-2017)
Found a dos partition table in /dev/sdb
Proceed anyway? (y,N) y
fs_types for mke2fs.conf resolution: 'ext4'
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
122052608 inodes, 488199446 blocks
24409972 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=2636120064
14899 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Filesystem UUID: 5acf50ff-3f7d-41a1-b1ba-5f50a668d152
Superblock backups stored on blocks: 
    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
    4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 
    102400000, 214990848

read_bad_blocks_file: No such file or directory while trying to open lista_uszkodzonych_bloków

Koment: Zeby wykorzystac inny superblok z backupu, trzeba najpierw naprawic "magic number" Nie znalazlem dzialajacej porady w Internecie.

Ostatnio edytowany przez Novi-cjusz (2018-02-09 16:08:48)

------------------------------------------------------------------------------------
"Inveniam viam aut faciam" : I will either find a way, or I shall make one
"Złoto to pieniądz królów, srebro to pieniądz dżentelmenów, barter to pieniądz chłopów ale dług to pieniądz niewolników."

Offline

 

#17  2018-02-09 17:02:06

  andreq - Członek DUG

andreq
Członek DUG
Skąd: Nisko
Zarejestrowany: 2005-01-11

Re: Naprawy bad sektorów

Nie

Czemu tworzysz system plików na dysku /dev/sdb a nie na partycji /dev/sdb1?

badblocks, w przykładzie, który podałem tworzy plik  o nawie "lista_uszkodzonych_bloków"  z listą uszkodzonych bloków na dysku,

mkfs.ext4 z parametrem "-l lista_uszkodzonych_bloków"  - uwzględnia listę uszkodzonych bloków podaną w pliku o nazwie "lista_uszkodzonych_bloków"

Inna metoda to uruchomienie mkfs.ext4 z opcją -c, wtedy sprawdza bloki w czasie tworzenia systemu plików, szczegóły w pomocy do polecenia mkfs.ext4

Zrób po prostu (jak sdb1 jest partycją na której chcesz utworzyć ext4):

Kod:

mkfs.ext4 -v -c /dev/sdb1

Nie wiem, po co kombinujesz niepotrzebnie z listowaniem, odtwarzaniem superbloków, jak samo mkfs napisało, że nie może ich zapisać.

Ostatnio edytowany przez andreq (2018-02-09 17:11:27)

Offline

 

#18  2018-02-09 17:14:27

  Novi-cjusz - Użytkownik

Novi-cjusz
Użytkownik
Zarejestrowany: 2013-03-05

Re: Naprawy bad sektorów

Chcialem naprawic caly dysk a nie tylko partycje.

Kod:

mkfs.ext4 -v -c /dev/sdb1
mke2fs 1.43.5 (04-Aug-2017)
The file /dev/sdb1 does not exist and no size was specified.

Fdisk pokazuje teraz tak:

Kod:

sudo fdisk -l
Disk /dev/loop0: 179.3 MiB, 187953152 bytes, 367096 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 184.1 MiB, 193036288 bytes, 377024 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 81.3 MiB, 85291008 bytes, 166584 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0006d088

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1            2048 123074313 123072266  58.7G 83 Linux
/dev/sda2  *    123074560 245926122 122851563  58.6G 83 Linux
/dev/sda3       245927936 368834185 122906250  58.6G 83 Linux
/dev/sda4       368836606 617381887 248545282 118.5G  5 Extended
/dev/sda5       368836608 379078655  10242048   4.9G 82 Linux swap / Solaris
/dev/sda6       432064512 494161919  62097408  29.6G 83 Linux
/dev/sda7       494163968 617381887 123217920  58.8G 83 Linux
/dev/sda8       379080704 432062463  52981760  25.3G 83 Linux

Partition table entries are not in disk order.




Disk /dev/sdb: 1.8 TiB, 1999664930816 bytes, 488199446 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Zapodalem:

Kod:

mkfs.ext4 -v -c /dev/sdb
mke2fs 1.43.5 (04-Aug-2017)
fs_types for mke2fs.conf resolution: 'ext4'
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
122052608 inodes, 488199446 blocks
24409972 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=2636120064
14899 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Filesystem UUID: 3a78f98b-8190-4944-aa38-12e678e73fb0
Superblock backups stored on blocks: 
    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
    4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 
    102400000, 214990848

Running command: badblocks -b 4096 -X -s /dev/sdb 488199445
Checking for bad blocks (read-only test):   0.00% done, 0:00 elapsed. (0/0/0 er  0.80% done, 1:02:21 elapsed. (0/0/0 errors)

Poniewaz te polecenia zabieraja wiele czasu przydal by sie pasek postepu.
Moze ktos zna funkcjonalny pasek postepu na Linuxa ?

Ostatnio edytowany przez Novi-cjusz (2018-02-09 18:29:02)

------------------------------------------------------------------------------------
"Inveniam viam aut faciam" : I will either find a way, or I shall make one
"Złoto to pieniądz królów, srebro to pieniądz dżentelmenów, barter to pieniądz chłopów ale dług to pieniądz niewolników."

Offline

 

#19  2018-02-09 22:30:13

  andreq - Członek DUG

andreq
Członek DUG
Skąd: Nisko
Zarejestrowany: 2005-01-11

Re: Naprawy bad sektorów

Przykłady pasków postępu: https://www.cyberciti.biz/faq/linux-unix-dd-command-show-progress-while-coping/

Musisz się zdecydować co chcesz robić, bo na razie Twoje działania są chaotyczne.

Proponuję:

Kod:

# dd if=/dev/zero of=/dev/sdb bs=1M
# smartctl -t offline /dev/sdb
# smartctl -t long /dev/sdb
# smartctl -l selftest /dev/sdb
# badblocks -svw -o lista /dev/sdb

Potem zrób raport SMART i wklej wynik oraz zawartość pliku lista

Ostatnio edytowany przez andreq (2018-02-09 22:32:17)

Offline

 

#20  2018-02-10 10:38:50

  Novi-cjusz - Użytkownik

Novi-cjusz
Użytkownik
Zarejestrowany: 2013-03-05

Re: Naprawy bad sektorów

Dziekuje za paski. (;-)
Z tymi haotycznymi dzialaniami to prawda, bo nie mialem jeszcze takiej sytuacji, i teraz w przyspieszonym trybie z Wasza pomoca poznaje zagadnienie  pt " diagnostyka i naprawa HDD "
Ta komende - zerowania dysku:

Kod:

dd if=/dev/zero of=/dev/sdb bs=1M

wykonalem 17 godzin temu i moze w sobote wieczorem bedzie gotowa, bo jest bardzo czasochlonna.
Wlasnie do nie potrzebowalem paska postepu.
Nie mam jak sprawdzic stopnia zaawansowania.

Wykonalem rownoczesnie nastepna komende - tworzenie systemu plikow ext4 na calym dysku:

Kod:

mkfs.ext4 -v -c /dev/sdb
mke2fs 1.43.5 (04-Aug-2017)
fs_types for mke2fs.conf resolution: 'ext4'
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
122052608 inodes, 488199446 blocks
24409972 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=2636120064
14899 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Filesystem UUID: 3a78f98b-8190-4944-aa38-12e678e73fb0
Superblock backups stored on blocks: 
    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
    4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 
    102400000, 214990848

Running command: badblocks -b 4096 -X -s /dev/sdb 488199445
Checking for bad blocks (read-only test):   0.00% done, 0:00 elapsed. (0/0/0 er  3.93% done, 17:11:22 elapsed. (1224/0/0 errors)

Moze jeszcze bardziej czasochlonna ( 3.93% done, 17:11:22)
Utworzylem pasek:

Kod:

(pv -n /dev/sda | dd of=/dev/sdb bs=128M conv=notrunc,noerror) 2>&1 | dialog --gauge "Running dd command (cloning), please wait..." 10 70 0

Na razie odczytuje, zobaczymy jak dlugo?
Zamierzam:
zaczekac do konca wyzerowania calego dysku ( w optymistycznym wariancie - dzis wieczor) a nastepnie komendy:

Kod:

# smartctl -t offline /dev/sdb
# smartctl -t long /dev/sdb
# smartctl -l selftest /dev/sdb
# badblocks -svw -o lista /dev/sdb

Bede bardzo wdzieczny w tej nielatwej sytuacji za kazda dobra rade!

Ps. Szkoda tylko, ze w Internecie brak skutecznej rady, jak naprawic "magic number" bo od tego wszystko sie zaczyna, czyli nastepnie superblock a nastepnie filesystem.
      Aktualnie czytam: http://vanpupi.stepi.net/2018/01/05/compute-node-disk-expansion/ w aspekcie lokalizacji sektora i partycji + bad magic number.
                                   http://tltech.com/info/recovering-broken-partition/   Mysle, ze tu jest rozwiazanie problemu ?
                                   https://ext4.wiki.kernel.org/index.php/Ext4_Disk_Layout
                                   https://www.slashroot.in/understanding-file-system-superblock-linux
Wylaczylem tworzenie filesystem ext4 bo idzie za wolno (4% w ciagu 24 godz)

Kod:

Running command: badblocks -b 4096 -X -s /dev/sdb 488199445
Checking for bad blocks (read-only test):   0.00% done, 0:00 elapsed. (0/0/0 er  4.05% done, 23:58:05 elapsed. (1814/0/0 errors)

Znalazlem informacje ,ze 15 min na 2GB.. czyli 48 godzin na 650 => to w moim przypadku 2 TB oznacza 10 dob pracy komputera zeby wszystko wyzerowac.
Masakra, na prad nie zarobie.

Wyniki Twoich polecen:

Kod:

 smartctl -l selftest /dev/sdb
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.13.0-32-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== 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: handling damage??  90%      2445         0
# 2  Short offline       Completed: read failure       90%      2318         360712192
# 3  Short offline       Completed: read failure       90%      2318         171968512
# 4  Short offline       Completed: read failure       90%      2318         360712192
# 5  Extended offline    Completed: read failure       90%      2312         360712192
# 6  Extended offline    Aborted by host               90%      2312         -
# 7  Extended offline    Interrupted (host reset)      90%      2300         -
# 8  Short offline       Completed: read failure       70%      2300         360712192

Lista uszkodzonych blokow zawiera 73 linie jak ponizej:

Kod:

71078192
71078193
71078194
71078195
71078200
71078201
71078202
71078203
71078464
71078465
71078466
71078467
71078488
71078489
71078490
71078491
71079924
71079925
71079926
71079927
71086852
71086853
71086854
71086855
71088584
71088585
71088586
71088587
71095512
71095513
71095514
71095515
71097244
71097245
71097246
71097247
71098976
71098977
71098978
71098979
71101440
71101441
71101442
71101443
71106432
71106433
71106434
71106435
71107636
71107637
71107638
71107639
71118028
71118029
71118030
71118031
71118400
71118401
71118402
71118403
71118404
71118405
71118406
71118407
71122112
71122113
71122114
71122115
71124956
71125504
71125505
71125506

Natomiast plik "lista" zawiera 581532 linie, i zaden darmowy hosting plikow textowych nie oferuje tak wiele miejsca.

Kod:

smartctl -x /dev/sdb
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.13.0-32-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     SAMSUNG SpinPoint F4 EG (AF)
Device Model:     SAMSUNG HD204UI
Serial Number:    S2H7J1AB114610
LU WWN Device Id: 5 0024e9 004919e57
Firmware Version: 1AQ10001
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    5400 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Sun Feb 11 17:23:29 2018 GMT

==> WARNING: Using smartmontools or hdparm with this
drive may result in data loss due to a firmware bug.
****** THIS DRIVE MAY OR MAY NOT BE AFFECTED! ******
Buggy and fixed firmware report same version number!
See the following web pages for details:
http://knowledge.seagate.com/articles/en_US/FAQ/223571en
http://www.smartmontools.org/wiki/SamsungF4EGBadBlocks

SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Disabled
APM feature is:   Disabled
Rd look-ahead is: Enabled
Write cache is:   Enabled
ATA Security is:  Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: 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:  (0x00)    Offline data collection activity
                    was never started.
                    Auto Offline Data Collection: Disabled.
Self-test execution status:      ( 137)    The previous self-test completed having
                    a test element that failed and the
                    device is suspected of having handling
                    damage.
Total time to complete Offline 
data collection:         (21180) 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:      (   2) minutes.
Extended self-test routine
recommended polling time:      ( 353) minutes.
SCT capabilities:            (0x003f)    SCT Status supported.
                    SCT Error Recovery Control 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          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   001   001   051    NOW  46687
  2 Throughput_Performance  -OS--K   252   252   000    -    0
  3 Spin_Up_Time            PO---K   067   060   025    -    10134
  4 Start_Stop_Count        -O--CK   099   099   000    -    1506
  5 Reallocated_Sector_Ct   PO--CK   252   252   010    -    0
  7 Seek_Error_Rate         -OSR-K   252   252   051    -    0
  8 Seek_Time_Performance   --S--K   252   252   015    -    0
  9 Power_On_Hours          -O--CK   100   100   000    -    2452
 10 Spin_Retry_Count        -O--CK   252   252   051    -    0
 11 Calibration_Retry_Count -O--CK   252   252   000    -    0
 12 Power_Cycle_Count       -O--CK   099   099   000    -    1319
181 Program_Fail_Cnt_Total  -O---K   100   100   000    -    2
191 G-Sense_Error_Rate      -O---K   092   092   000    -    84145
192 Power-Off_Retract_Count -O---K   252   252   000    -    0
194 Temperature_Celsius     -O----   064   056   000    -    27 (Min/Max 10/44)
195 Hardware_ECC_Recovered  -O-RCK   100   100   000    -    0
196 Reallocated_Event_Count -O--CK   252   252   000    -    0
197 Current_Pending_Sector  -O--CK   059   057   000    -    5120
198 Offline_Uncorrectable   ----CK   100   100   000    -    41
199 UDMA_CRC_Error_Count    -OS-CK   200   200   000    -    0
200 Multi_Zone_Error_Rate   -O-R-K   100   100   000    -    1
223 Load_Retry_Count        -O--CK   252   252   000    -    0
225 Load_Cycle_Count        -O--CK   100   100   000    -    1544
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O      2  Comprehensive SMART error log
0x03       GPL     R/O      2  Ext. Comprehensive SMART error log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O      2  Extended self-test log
0x08       GPL     R/O      2  Power Conditions log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  SATA NCQ Queued Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (2 sectors)
Device Error Count: 40249 (device log contains only the most recent 8 errors)
    CR     = Command Register
    FEATR  = Features Register
    COUNT  = Count (was: Sector Count) Register
    LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
    LH     = LBA High (was: Cylinder High) Register    ]   LBA
    LM     = LBA Mid (was: Cylinder Low) Register      ] Register
    LL     = LBA Low (was: Sector Number) Register     ]
    DV     = Device (was: Device/Head) Register
    DC     = Device Control Register
    ER     = Error register
    ST     = Status register
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 40249 [0] occurred at disk power-on lifetime: 2445 hours (101 days + 21 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 e8 ca a5 b0 40 00  Error: UNC at LBA = 0xe8caa5b0 = 3905594800

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 08 00 00 e8 ca a5 b0 40 00     00:00:00.012  READ FPDMA QUEUED
  60 00 da 00 08 00 00 e8 ca a5 b0 40 00     00:00:00.074  READ FPDMA QUEUED
  b0 00 da 00 00 00 00 00 c2 4f 00 00 00     00:00:00.073  SMART RETURN STATUS
  b0 00 d0 00 00 00 00 00 c2 4f 00 00 00     00:00:00.073  SMART READ DATA
  e5 00 00 00 00 00 00 00 00 00 00 00 00     00:00:00.073  CHECK POWER MODE

Error 40248 [7] occurred at disk power-on lifetime: 2445 hours (101 days + 21 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 e8 ca a5 b0 40 00  Error: UNC at LBA = 0xe8caa5b0 = 3905594800

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 08 00 00 e8 ca a5 b0 40 00     00:00:00.012  READ FPDMA QUEUED
  60 00 00 00 08 00 00 e8 ca a5 b0 40 00     00:00:00.068  READ FPDMA QUEUED
  60 00 00 00 10 00 00 e8 ca ab a0 40 00     00:00:00.068  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 00 00     00:00:00.068  READ LOG EXT
  60 00 00 00 08 00 00 e8 ca a5 b0 40 00     00:00:00.012  READ FPDMA QUEUED

Error 40247 [6] occurred at disk power-on lifetime: 2445 hours (101 days + 21 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 e8 ca a5 b0 40 00  Error: UNC at LBA = 0xe8caa5b0 = 3905594800

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 08 00 00 e8 ca a5 b0 40 00     00:00:00.012  READ FPDMA QUEUED
  60 00 00 00 08 00 00 e8 ca a5 b0 40 00     00:00:00.063  READ FPDMA QUEUED
  60 00 00 00 f0 00 00 e8 ca aa b0 40 00     00:00:00.063  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 00 00     00:00:00.062  READ LOG EXT
  60 00 00 00 08 00 00 e8 ca a5 b0 40 00     00:00:00.010  READ FPDMA QUEUED

Error 40246 [5] occurred at disk power-on lifetime: 2445 hours (101 days + 21 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 e8 ca a5 b0 40 00  Error: UNC at LBA = 0xe8caa5b0 = 3905594800

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 08 00 00 e8 ca a5 b0 40 00     00:00:00.010  READ FPDMA QUEUED
  60 00 00 00 08 00 00 e8 ca a5 b0 40 00     00:00:00.057  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 00 00     00:00:00.057  READ LOG EXT
  60 00 00 00 08 00 00 e8 ca a5 b0 40 00     00:00:00.010  READ FPDMA QUEUED
  60 00 00 00 08 00 00 e8 ca a5 b0 40 00     00:00:00.052  READ FPDMA QUEUED

Error 40245 [4] occurred at disk power-on lifetime: 2445 hours (101 days + 21 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 e8 ca a5 b0 40 00  Error: UNC at LBA = 0xe8caa5b0 = 3905594800

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 08 00 00 e8 ca a5 b0 40 00     00:00:00.010  READ FPDMA QUEUED
  60 00 00 00 08 00 00 e8 ca a5 b0 40 00     00:00:00.052  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 00 00     00:00:00.052  READ LOG EXT
  60 00 00 00 08 00 00 e8 ca a5 b0 40 00     00:00:00.000  READ FPDMA QUEUED
  60 00 00 00 08 00 00 e8 ca a5 b0 40 00     00:00:00.047  READ FPDMA QUEUED

Error 40244 [3] occurred at disk power-on lifetime: 2445 hours (101 days + 21 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 01 00 08 00 00 e8 ca a5 b0 40 00  Error: UNC at LBA = 0xe8caa5b0 = 3905594800

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 08 00 00 e8 ca a5 b0 40 00     00:00:00.000  READ FPDMA QUEUED
  60 00 00 00 08 00 00 e8 ca a5 b0 40 00     00:00:00.047  READ FPDMA QUEUED
  60 00 00 00 08 00 00 e8 ca a5 a8 40 00     00:00:00.047  READ FPDMA QUEUED
  60 00 00 00 c0 00 00 e8 ca a9 f0 40 00     00:00:00.047  READ FPDMA QUEUED
  60 00 00 00 08 00 00 e8 ca a5 a0 40 00     00:00:00.047  READ FPDMA QUEUED

Error 40243 [2] occurred at disk power-on lifetime: 2445 hours (101 days + 21 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 01 00 20 00 00 e8 ca a5 b0 40 00  Error: UNC at LBA = 0xe8caa5b0 = 3905594800

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 a8 00 00 e8 ca a5 28 40 00     00:00:00.000  READ FPDMA QUEUED
  60 00 00 00 a8 00 00 e8 ca a5 28 40 00     00:00:00.041  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 00 00     00:00:00.041  READ LOG EXT
  60 00 00 00 a8 00 00 e8 ca a5 28 40 00     00:00:00.000  READ FPDMA QUEUED
  60 00 00 00 a8 00 00 e8 ca a5 28 40 00     00:00:00.035  READ FPDMA QUEUED

Error 40242 [1] occurred at disk power-on lifetime: 2445 hours (101 days + 21 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 01 00 20 00 00 e8 ca a5 b0 40 00  Error: UNC at LBA = 0xe8caa5b0 = 3905594800

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 a8 00 00 e8 ca a5 28 40 00     00:00:00.000  READ FPDMA QUEUED
  60 00 00 00 a8 00 00 e8 ca a5 28 40 00     00:00:00.035  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 00 00     00:00:00.035  READ LOG EXT
  60 00 00 00 a8 00 00 e8 ca a5 28 40 00     00:00:00.000  READ FPDMA QUEUED
  60 00 00 00 a8 00 00 e8 ca a5 28 40 00     00:00:00.030  READ FPDMA QUEUED

SMART Extended Self-test Log Version: 1 (2 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: handling damage??  90%      2451         0
# 2  Extended offline    Completed: handling damage??  90%      2445         0
# 3  Short offline       Completed: read failure       90%      2318         360712192
# 4  Short offline       Completed: read failure       90%      2318         171968512
# 5  Short offline       Completed: read failure       90%      2318         360712192
# 6  Extended offline    Completed: read failure       90%      2312         360712192
# 7  Extended offline    Aborted by host               90%      2312         -
# 8  Extended offline    Interrupted (host reset)      90%      2300         -
# 9  Short offline       Completed: read failure       70%      2300         360712192

SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Completed_handling_damage?? [90% left] (0-65535)
    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.

SCT Status Version:                  2
SCT Version (vendor specific):       256 (0x0100)
SCT Support Level:                   1
Device State:                        Active (0)
Current Temperature:                    27 Celsius
Power Cycle Min/Max Temperature:     26/29 Celsius
Lifetime    Min/Max Temperature:     10/59 Celsius
Under/Over Temperature Limit Count:   0/0

SCT Temperature History Version:     2
Temperature Sampling Period:         5 minutes
Temperature Logging Interval:        5 minutes
Min/Max recommended Temperature:     -5/80 Celsius
Min/Max Temperature Limit:           -10/85 Celsius
Temperature History Size (Index):    128 (23)

Index    Estimated Time   Temperature Celsius
  24    2018-02-11 06:45    27  ********
  25    2018-02-11 06:50    31  ************
  26    2018-02-11 06:55    31  ************
  27    2018-02-11 07:00    32  *************
  28    2018-02-11 07:05    31  ************
 ...    ..(  4 skipped).    ..  ************
  33    2018-02-11 07:30    31  ************
  34    2018-02-11 07:35    30  ***********
 ...    ..(  6 skipped).    ..  ***********
  41    2018-02-11 08:10    30  ***********
  42    2018-02-11 08:15    31  ************
  43    2018-02-11 08:20    30  ***********
 ...    ..(  7 skipped).    ..  ***********
  51    2018-02-11 09:00    30  ***********
  52    2018-02-11 09:05    31  ************
  53    2018-02-11 09:10    31  ************
  54    2018-02-11 09:15    30  ***********
  55    2018-02-11 09:20    30  ***********
  56    2018-02-11 09:25    31  ************
  57    2018-02-11 09:30    31  ************
  58    2018-02-11 09:35    31  ************
  59    2018-02-11 09:40    30  ***********
  60    2018-02-11 09:45    32  *************
  61    2018-02-11 09:50    31  ************
 ...    ..(  2 skipped).    ..  ************
  64    2018-02-11 10:05    31  ************
  65    2018-02-11 10:10    32  *************
  66    2018-02-11 10:15    28  *********
 ...    ..(  8 skipped).    ..  *********
  75    2018-02-11 11:00    28  *********
  76    2018-02-11 11:05    29  **********
  77    2018-02-11 11:10    28  *********
  78    2018-02-11 11:15    28  *********
  79    2018-02-11 11:20    27  ********
 ...    ..(  8 skipped).    ..  ********
  88    2018-02-11 12:05    27  ********
  89    2018-02-11 12:10    26  *******
  90    2018-02-11 12:15    27  ********
  91    2018-02-11 12:20    26  *******
  92    2018-02-11 12:25    27  ********
 ...    ..( 15 skipped).    ..  ********
 108    2018-02-11 13:45    27  ********
 109    2018-02-11 13:50    28  *********
 110    2018-02-11 13:55    27  ********
 ...    ..( 40 skipped).    ..  ********
  23    2018-02-11 17:20    27  ********

SCT Error Recovery Control:
           Read: Disabled
          Write: Disabled

Device Statistics (GP/SMART Log 0x04) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  4            0  Command failed due to ICRC error
0x0002  4            0  R_ERR response for data FIS
0x0003  4            0  R_ERR response for device-to-host data FIS
0x0004  4            0  R_ERR response for host-to-device data FIS
0x0005  4            0  R_ERR response for non-data FIS
0x0006  4            0  R_ERR response for device-to-host non-data FIS
0x0007  4            0  R_ERR response for host-to-device non-data FIS
0x0008  4            0  Device-to-host non-data FIS retries
0x0009  4            4  Transition from drive PhyRdy to drive PhyNRdy
0x000a  4            2  Device-to-host register FISes sent due to a COMRESET
0x000b  4            0  CRC errors within host-to-device FIS
0x000d  4            0  Non-CRC errors within host-to-device FIS
0x000f  4            0  R_ERR response for host-to-device data FIS, CRC
0x0010  4            0  R_ERR response for host-to-device data FIS, non-CRC
0x0012  4            0  R_ERR response for host-to-device non-data FIS, CRC
0x0013  4            0  R_ERR response for host-to-device non-data FIS, non-CRC
0x8e00  4            0  Vendor specific
0x8e01  4            0  Vendor specific
0x8e02  4            0  Vendor specific
0x8e03  4            0  Vendor specific
0x8e04  4            0  Vendor specific
0x8e05  4            0  Vendor specific
0x8e06  4            0  Vendor specific
0x8e07  4            0  Vendor specific
0x8e08  4            0  Vendor specific
0x8e09  4            0  Vendor specific
0x8e0a  4            0  Vendor specific
0x8e0b  4            0  Vendor specific
0x8e0c  4            0  Vendor specific
0x8e0d  4            0  Vendor specific
0x8e0e  4            0  Vendor specific
0x8e0f  4            0  Vendor specific
0x8e10  4            0  Vendor specific
0x8e11  4            0  Vendor specific

Ostatnio edytowany przez Novi-cjusz (2018-02-11 18:24:36)

------------------------------------------------------------------------------------
"Inveniam viam aut faciam" : I will either find a way, or I shall make one
"Złoto to pieniądz królów, srebro to pieniądz dżentelmenów, barter to pieniądz chłopów ale dług to pieniądz niewolników."

Offline

 

 

Strony: 1

Stopka forum

Powered by PunBB
© Copyright 2002–2005 Rickard Andersson
Nas ludzie lubią po prostu, a nie klikając w przyciski ;-)

[ Generated in 0.013 seconds, 11 queries executed ]

Informacje debugowania

Time (s) Query
0.00009 SET CHARSET latin2
0.00009 SET NAMES latin2
0.00143 SELECT u.*, g.*, o.logged FROM punbb_users AS u INNER JOIN punbb_groups AS g ON u.group_id=g.g_id LEFT JOIN punbb_online AS o ON o.ident='3.147.75.46' WHERE u.id=1
0.00117 REPLACE INTO punbb_online (user_id, ident, logged) VALUES(1, '3.147.75.46', 1732437792)
0.00050 SELECT * FROM punbb_online WHERE logged<1732437492
0.00099 SELECT topic_id FROM punbb_posts WHERE id=317405
0.00008 SELECT id FROM punbb_posts WHERE topic_id=30194 ORDER BY posted
0.00077 SELECT t.subject, t.closed, t.num_replies, t.sticky, f.id AS forum_id, f.forum_name, f.moderators, fp.post_replies, 0 FROM punbb_topics AS t INNER JOIN punbb_forums AS f ON f.id=t.forum_id LEFT JOIN punbb_forum_perms AS fp ON (fp.forum_id=f.id AND fp.group_id=3) WHERE (fp.read_forum IS NULL OR fp.read_forum=1) AND t.id=30194 AND t.moved_to IS NULL
0.00005 SELECT search_for, replace_with FROM punbb_censoring
0.00325 SELECT u.email, u.title, u.url, u.location, u.use_avatar, u.signature, u.email_setting, u.num_posts, u.registered, u.admin_note, p.id, p.poster AS username, p.poster_id, p.poster_ip, p.poster_email, p.message, p.hide_smilies, p.posted, p.edited, p.edited_by, g.g_id, g.g_user_title, o.user_id AS is_online FROM punbb_posts AS p INNER JOIN punbb_users AS u ON u.id=p.poster_id INNER JOIN punbb_groups AS g ON g.g_id=u.group_id LEFT JOIN punbb_online AS o ON (o.user_id=u.id AND o.user_id!=1 AND o.idle=0) WHERE p.topic_id=30194 ORDER BY p.id LIMIT 0,25
0.00095 UPDATE punbb_topics SET num_views=num_views+1 WHERE id=30194
Total query time: 0.00937 s