jasne 0 Zgłoś post Napisano Luty 1, 2013 Witam Od jakiegoś czasu system wrzuca w logi: Feb 1 08:34:30 n smartd[5402]: Device: /dev/sdb, 178 Currently unreadable (pending) sectorsFeb 1 08:34:30 n smartd[5402]: Device: /dev/sdb, 178 Offline uncorrectable sectors Rozumiem że pojawiły się bad blocki na dysku sdb. Czy wartość 178 oznacza łączną ilość bad block czy numer pojedyńczego bad blocka. Dodam że ta wartość wzrosła przez kilka godzin z 31 do 178 Udostępnij ten post Link to postu Udostępnij na innych stronach
Inferno 41 Zgłoś post Napisano Luty 1, 2013 Sectors czyli liczba mnoga Lepiej zacznij kopiować dane. Udostępnij ten post Link to postu Udostępnij na innych stronach
Gość patrys Zgłoś post Napisano Luty 1, 2013 W skrócie - 178 sektorów w plecy. Jak najszybciej ten dysk wymieniać. Udostępnij ten post Link to postu Udostępnij na innych stronach
jasne 0 Zgłoś post Napisano Luty 1, 2013 ok. mam zastosowany RAID 1 , sychnronizacja 100%. Czy te bad sektory nie zostaja zapisane jakimis danymi , rozumiem ze zostaja pomijane przy probie zapisu ? Chodzi o to ze teraz bede robil backup to czy system nie zrobi kopii danych z odczytem ich z bad sektorow ? Udostępnij ten post Link to postu Udostępnij na innych stronach
przemon 35 Zgłoś post Napisano Luty 1, 2013 Sypnie błędem o niemożliwości odczytania danych z dysku uszkodzonego, dane powinien odczytać z dysku zdrowego. Wklej wynik smarta, odpal mu testy. Udostępnij ten post Link to postu Udostępnij na innych stronach
jasne 0 Zgłoś post Napisano Luty 1, 2013 ok === START OF INFORMATION SECTION ===Device Model: ST3750528ASSerial Number: 6VP9PPW5Firmware Version: CC44User Capacity: 750,156,374,016 bytesDevice is: Not in smartctl database [for details use: -P showall]ATA Version is: 8ATA Standard is: ATA-8-ACS revision 4Local Time is: Fri Feb 1 17:42:19 2013 CETSMART support is: Available - device has SMART capability.SMART support is: Enabled=== START OF READ SMART DATA SECTION ===SMART overall-health self-assessment test result: PASSEDGeneral SMART Values:Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled.Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run.Total time to complete Offlinedata collection: ( 617) seconds.Offline data collectioncapabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported.SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer.Error logging capability: (0x01) Error logging supported. General Purpose Logging supported.Short self-test routinerecommended polling time: ( 1) minutes.Extended self-test routinerecommended polling time: ( 152) minutes.Conveyance self-test routinerecommended polling time: ( 2) minutes.SCT capabilities: (0x103b) SCT Status supported. SCT Feature Control supported. SCT Data Table supported.SMART Attributes Data Structure revision number: 10Vendor Specific SMART Attributes with Thresholds:ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 111 099 006 Pre-fail Always - 33354619 3 Spin_Up_Time 0x0003 095 095 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 36 5 Reallocated_Sector_Ct 0x0033 096 096 036 Pre-fail Always - 181 7 Seek_Error_Rate 0x000f 087 060 030 Pre-fail Always - 533419204 9 Power_On_Hours 0x0032 079 079 000 Old_age Always - 19160 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 36183 Unknown_Attribute 0x0000 100 100 000 Old_age Offline - 0184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0187 Reported_Uncorrect 0x0032 073 073 000 Old_age Always - 27188 Unknown_Attribute 0x0032 100 096 000 Old_age Always - 1125298667783189 High_Fly_Writes 0x003a 098 098 000 Old_age Always - 2190 Airflow_Temperature_Cel 0x0022 059 046 045 Old_age Always - 41 (Lifetime Min/Max 41/44)194 Temperature_Celsius 0x0022 041 054 000 Old_age Always - 41 (0 23 0 0)195 Hardware_ECC_Recovered 0x001a 042 015 000 Old_age Always - 33354619197 Current_Pending_Sector 0x0012 096 096 000 Old_age Always - 178198 Offline_Uncorrectable 0x0010 096 096 000 Old_age Offline - 178199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 184241212115753241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 3521132359242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 3166240442SMART Error Log Version: 1ATA Error Count: 24 (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 asDDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,SS=sec, and sss=millisec. It "wraps" after 49.710 days.Error 24 occurred at disk power-on lifetime: 19140 hours (797 days + 12 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 ff ff ff ef 00 8d+10:02:49.182 READ DMA EXT ec 00 00 00 00 00 a0 00 8d+10:02:49.133 IDENTIFY DEVICE ef 03 42 00 00 00 a0 00 8d+10:02:45.965 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 00 8d+10:02:45.822 IDENTIFY DEVICE 25 00 40 ff ff ff ef 00 8d+10:02:42.937 READ DMA EXTError 23 occurred at disk power-on lifetime: 19140 hours (797 days + 12 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 ff ff ff ef 00 8d+10:02:42.937 READ DMA EXT ec 00 00 00 00 00 a0 00 8d+10:02:42.889 IDENTIFY DEVICE ef 03 42 00 00 00 a0 00 8d+10:02:42.817 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 00 8d+10:02:42.650 IDENTIFY DEVICE 25 00 40 ff ff ff ef 00 8d+10:02:39.777 READ DMA EXTError 22 occurred at disk power-on lifetime: 19140 hours (797 days + 12 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 ff ff ff ef 00 8d+10:02:39.777 READ DMA EXT ec 00 00 00 00 00 a0 00 8d+10:02:39.768 IDENTIFY DEVICE ef 03 42 00 00 00 a0 00 8d+10:02:39.713 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 00 8d+10:02:39.595 IDENTIFY DEVICE 25 00 40 ff ff ff ef 00 8d+10:02:36.710 READ DMA EXTError 21 occurred at disk power-on lifetime: 19140 hours (797 days + 12 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 ff ff ff ef 00 8d+10:02:36.710 READ DMA EXT 25 00 40 ff ff ff ef 00 8d+10:02:36.705 READ DMA EXT 25 00 40 ff ff ff ef 00 8d+10:02:36.138 READ DMA EXT 25 00 40 ff ff ff ef 00 8d+10:02:36.128 READ DMA EXT ea 00 00 ff ff ff af 00 8d+10:02:36.096 FLUSH CACHE EXITError 20 occurred at disk power-on lifetime: 19140 hours (797 days + 12 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 ff ff ff ef 00 8d+10:02:32.637 READ DMA EXT ec 00 00 00 00 00 a0 00 8d+10:02:32.580 IDENTIFY DEVICE ef 03 42 00 00 00 a0 00 8d+10:02:32.460 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 00 8d+10:02:32.318 IDENTIFY DEVICE 25 00 40 ff ff ff ef 00 8d+10:02:29.421 READ DMA EXTSMART Self-test log structure revision number 1Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error# 1 Short offline Completed without error 00% 8 -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_testingSelective 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. Udostępnij ten post Link to postu Udostępnij na innych stronach
przemon 35 Zgłoś post Napisano Luty 1, 2013 Wygląda to na uwalony dysk jak koledzy pisali. Kup nowy taki sam lub większy, odtwrórz tablicę partycji ze zdrowego dysku i odbuduj raid1. Udostępnij ten post Link to postu Udostępnij na innych stronach
d.v 1409 Zgłoś post Napisano Luty 2, 2013 Już sam pięciokrotny status "Pre-fail" świadczy o tym, że dysk należy natychmiast zutylizować. W przypadku RAID1 nie masz problemu, wywal ten uwalony, wstaw kolejny, odbuduj RAID. Innej opcji po prostu nie ma. Udostępnij ten post Link to postu Udostępnij na innych stronach