PC-HELP.CZ

Dnes se mi stala taková věc, zapl jsem normálně PC, jako každý jiný den... Potřeboval jsem zkopírovat nějaká data z disku. Tak jsem začal kopírovat, ale začalo mi to tam házet nějaký I/O error, tak jsem restartoval PC a windows se nechtěl načíst. Chvíli jsem zkoušel restartovat, ale pak jsem sáhl po přeinstalování windowsu. Mám 2 disky - SSD, který funguje normálně a HDD se kterým jsou teď problémy.
Windowsy jsem normálně přeinstaloval a už jedou normálně...aspoň že tak, ale ten disk furt nic. Windows disk furt ignoruje, přitom v BIOSu se mi normálně zobrazuje, dokonce ho můžu i do jisté míry procházet (ASUS Ez Flash Utility).
Vůbec nevím kde může být problém, s diskem dřív vůbec problémy nebyly, problém je v tom, že tam mám data, bez kterých se veskrze neobejdu...děkuji za pomoc

Disk: Seagate Barracuda 7200.14 1TB s Advanced Format

Windows jsou na SSD disku? Pokud ano, jejich preinstalace nemela smysl.

Jaky stav disku hlasi Crystal Disk Info? Je treba udelat sken celeho povrchu disku napr. pres HD Tune.

I/O error = hardwarova chyba disku, necitelne sektory.

Nojo, problem je ale v tom, ze se mi disk ve windowsech nezobrazi

Dodatečně přidáno po 6 minutách 38 vteřinách:
smartctl 5.43 2012-06-30 r3573 [i686-linux-3.10.4-pmagic] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda (SATA 3Gb/s, 4K Sectors)
Device Model: ST1000DM003-1CH162
Serial Number: S1D6PB10
LU WWN Device Id: 5 000c50 05b6045be
Firmware Version: CC44
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Sun Feb 28 09:21:23 2016 AKST
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: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 584) 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: ( 113) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x3085) SCT Status 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 087 086 006 Pre-fail Always - 243086542
3 Spin_Up_Time 0x0003 097 097 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 097 097 020 Old_age Always - 3518
5 Reallocated_Sector_Ct 0x0033 094 094 010 Pre-fail Always - 8040
7 Seek_Error_Rate 0x000f 070 060 030 Pre-fail Always - 17226929083
9 Power_On_Hours 0x0032 085 085 000 Old_age Always - 13142
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 099 099 020 Old_age Always - 1777
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 1962
188 Command_Timeout 0x0032 100 096 000 Old_age Always - 8590065677
189 High_Fly_Writes 0x003a 084 084 000 Old_age Always - 16
190 Airflow_Temperature_Cel 0x0022 069 058 045 Old_age Always - 31 (0 42 31 28 0)
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 - 300
193 Load_Cycle_Count 0x0032 018 018 000 Old_age Always - 164448
194 Temperature_Celsius 0x0022 031 042 000 Old_age Always - 31 (128 0 0 0 0)
197 Current_Pending_Sector 0x0012 084 084 000 Old_age Always - 2680
198 Offline_Uncorrectable 0x0010 084 084 000 Old_age Offline - 2680
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 72121090841946
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 10749365482
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 21713176080

SMART Error Log Version: 1
ATA Error Count: 1966 (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 1966 occurred at disk power-on lifetime: 13142 hours (547 days + 14 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 20 88 bb 00 Error: UNC at LBA = 0x00bb8820 = 12290080

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 20 88 bb 40 00 00:35:40.540 READ FPDMA QUEUED
b0 d5 01 00 4f c2 00 00 00:35:40.518 SMART READ LOG
60 00 08 18 88 bb 40 00 00:35:40.457 READ FPDMA QUEUED
b0 da 00 00 4f c2 00 00 00:35:36.577 SMART RETURN STATUS
60 00 08 10 88 bb 40 00 00:35:29.896 READ FPDMA QUEUED

Error 1965 occurred at disk power-on lifetime: 13142 hours (547 days + 14 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 00 88 bb 00 Error: UNC at LBA = 0x00bb8800 = 12290048

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 00 88 bb 40 00 00:35:06.084 READ FPDMA QUEUED
ec 00 01 00 00 00 00 00 00:35:06.084 IDENTIFY DEVICE
ef 10 02 00 00 00 a0 00 00:35:06.084 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 00 00:35:06.084 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 00:35:06.083 IDENTIFY DEVICE

Error 1964 occurred at disk power-on lifetime: 13142 hours (547 days + 14 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 28 88 bb 00 Error: UNC at LBA = 0x00bb8828 = 12290088

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 80 00 88 bb 40 00 00:34:43.201 READ FPDMA QUEUED
60 00 08 f8 87 bb 40 00 00:34:35.724 READ FPDMA QUEUED
60 00 08 f0 87 bb 40 00 00:34:29.413 READ FPDMA QUEUED
60 00 08 e8 87 bb 40 00 00:34:24.822 READ FPDMA QUEUED
60 00 08 d0 87 bb 40 00 00:34:18.295 READ FPDMA QUEUED

Error 1963 occurred at disk power-on lifetime: 13142 hours (547 days + 14 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 f0 87 bb 00 Error: UNC at LBA = 0x00bb87f0 = 12290032

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 80 80 87 bb 40 00 00:33:42.911 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 00:33:42.911 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 00 00:33:42.910 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 00:33:42.910 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 00:33:42.910 SET FEATURES [Set transfer mode]

Error 1962 occurred at disk power-on lifetime: 13141 hours (547 days + 13 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 70 87 bb 00 Error: UNC at LBA = 0x00bb8770 = 12289904

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 70 87 bb 40 00 00:33:09.393 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 00:33:09.393 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 00 00:33:09.393 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 00:33:09.392 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 00:33:09.392 SET FEATURES [Set transfer mode]

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


SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Ve Windows se nezobrazi jako pismeno nebo neni videt ani ve spravci disku a ve spravci zarizeni?

Pokud je ve spravci zarizeni videt, musi ho videt i Crystal Disk Info.

Podle SMARTu je tam hromada chybnych sektoru.

Nejlepsi by bylo udelat image disku - je to nejrychlejsi, jenze je potreba jiny disk kde je dost volneho mista - coz znamena disk vetsi nez 1 TB. Pak se pouzije linuxove DDRescue, ktere nejdriv kopiruje citelne sektory a ty necitelne si necha na konec a zkousi je cist postupne.

Druha nejlepsi vec co jde udelat je pouzit R-Studio nebo Get Data Back (je potrbe aplna verze tehle programu) a zacit kopirovat vsecko co jde.

Windows disk vůbec nezobrazuje. Disk se zobrazuje jenom v BIOSu a v linuxu, v tom linuxu nejde disk mountnout. Mám 1TB USB hardisk...jestli by to teda stačilo. Přes co bych měl kdyžtak v tom linuxu ten obraz udělat?

Obavam se ze nestacilo, protoze obraz 1 TB disku se na 1 TB disk nevejde.

Do linuxu staci doinstalovat nebo stahout DDRESCUE, ale ten image musi byt mozne nekam nahrat.

Co znamena disk se ve Windows nezobrazuje? Neni videt ani ve spravci zarizeni, ani ve spravci disku? To, ze neni videt jako dalsi pismeno znamena jen to, ze ho Windows nedokazi pripojit jako to nedokaze Linux, protoze minimalne zacatek disku je necitelny.

Mám pak ještě 2TB USB disk, pokud by nahrávání toho image bylo 100% bez rizika, tak by to nebyl problém...o další soubory už bych fakt hodně nerad přišel.

Není vidět ani ve správci zařízení, ani ve správci disku. Když jsem nabootoval Acronis Disk Director, tak se disk zobrazil, ale vyžadovalo to kontrolu systému souborů, protože byl disk nečitelný.

Pokud je na tom 2 TB disku vice nez 1 TB volneho mista a je naformatovan na NTFS nebo EXT tak nebude problem.

Pouziti DDRESCUE je pak jednoduche:

ddrescue -d -r3 /dev/sdc disk.img disk.logfile

-d znamena ze je pouzit primy pristup na disk
-r3 znamena ze kazdy vadny sektor se pokusi precist 3x nez ho preskoci
/dev/sd je ten vadny disk, samozrejmne je potreba vedet jake zarizeni to je konkretnim pripade
disk.img je soubor, kam se budou ikladat data - ten pak lze pripojit jako dalsi disk a data zachranovat z nej jako by to byl disk
disk.logfile je log, kde bude zapsano co se kde nepovedlo precist

Funguje to tak, ze sektory disku se ctou od zacatku disku, kdyz se narazi na chybu, tak se preskoci velky blok dat dokud se nenarazi zase na misto kde to jde precist - coz znamena, ze jako prvni to z celeho disku precte citelna data. Nakonec si ty necitelne useky zacne rozdelovat na mensi casti a cte je postupne - to uz pak jde i ptreskocit, protoze to muze trvat take 14 dnu.

S místem není problém, disk je NTFS.

Takže pokud mám adresu k disku /dev/sda2, tak bude příkaz vypadat: ddrescue -d -r3 /dev/sda2 disk.img disk.logfile?

Jak ale specifikuju, kam se bude ten disk.img ukládat (adresu).

/dev/sda2 udela jen oddil, /dev/sda udela cely disk. Je lepsi delat cely disk. Tedy pokud sda je ten vadny disk.

Ukladat se to bude tam, odkud se to spusti - jde zadat i cesta jako /home/uzivatel/disk.img a /home/uzivatel/disk.logfile

V tomhle pripade bude potreba ten 2 TB disk namountovat a cesta musi smerovat tam, takze treba /MNT/DISK/disk.img

Aha, rozumím. Udělám si na disku místo a jdu to vyzkoušet. Děkuju moc

Ted uz jen zalezi na tom, co vsechno je na tom disku necitelne.

Jestli zacatek, tak ten image pujde vytvorit.

Jeste tam pridej -v aby bylo videt co to dela, mam pocit ze -v4 bude vypisovat uplne vsechno.