[opensuse-es] Ayuda SMART log
Hola, alguien que sepa manejar smart... el short test me da el siguiente log: ?Alguien sabe qu� quiere decir y si tiene arreglo? smartctl 5.39 2008-10-24 22:33 [i686-suse-linux-gnu] (openSUSE RPM) Copyright (C) 2002-8 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.10 family Device Model: ST3500630A Serial Number: 9QG06MEN Firmware Version: 3.AAC User Capacity: 500,107,862,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sat Jan 24 21:45:43 2009 CET SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 430) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 163) minutes. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 110 092 006 Pre-fail Always - 29099634 3 Spin_Up_Time 0x0003 095 093 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 452 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 084 061 030 Pre-fail Always - 296688016 9 Power_On_Hours 0x0032 097 097 000 Old_age Always - 2930 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 456 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 060 048 045 Old_age Always - 40 (Lifetime Min/Max 28/40) 194 Temperature_Celsius 0x0022 040 052 000 Old_age Always - 40 (0 16 0 0) 195 Hardware_ECC_Recovered 0x001a 065 052 000 Old_age Always - 1844796 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0 202 TA_Increase_Count 0x0032 100 253 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 2 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 2 occurred at disk power-on lifetime: 0 hours (0 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 SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0 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 01 00 00 00 e0 00 00:04:39.592 READ DMA EXT b0 d9 00 00 4f c2 e0 00 00:04:39.559 SMART DISABLE OPERATIONS b0 d2 f1 00 4f c2 e0 00 00:04:39.559 SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE b0 d8 00 00 4f c2 e0 00 00:04:38.864 SMART ENABLE OPERATIONS 91 00 3f 00 00 00 ef 00 00:04:35.101 INITIALIZE DEVICE PARAMETERS [OBS-6] Error 1 occurred at disk power-on lifetime: 0 hours (0 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 SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0 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 01 00 00 00 e0 00 00:00:51.341 READ DMA EXT b0 d9 00 00 4f c2 e0 00 00:00:51.341 SMART DISABLE OPERATIONS b0 d2 f1 00 4f c2 e0 00 00:00:50.641 SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE b0 d8 00 00 4f c2 e0 00 00:00:46.867 SMART ENABLE OPERATIONS 91 00 3f 00 00 00 ef 00 00:00:39.156 INITIALIZE DEVICE PARAMETERS [OBS-6] SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 2930 - # 2 Short offline Completed without error 00% 2929 - # 3 Short offline Completed without error 00% 2929 - 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. -- Saludos. C�sar Enfr�ntate a los malos; enfr�ntate a los crueles; enfr�ntate a todos, menos a los tontos. Son demasiados y siempre ser�s derrotado. (Proverbio hind�) -- Para dar de baja la suscripción, mande un mensaje a: opensuse-es+unsubscribe@opensuse.org Para obtener el resto de direcciones-comando, mande un mensaje a: opensuse-es+help@opensuse.org
csalinux escribi�:
Hola, alguien que sepa manejar smart... el short test me da el siguiente log: ?Alguien sabe qu� quiere decir y si tiene arreglo?
smartctl 5.39 2008-10-24 22:33 [i686-suse-linux-gnu] (openSUSE RPM) Copyright (C) 2002-8 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.10 family Device Model: ST3500630A Serial Number: 9QG06MEN Firmware Version: 3.AAC User Capacity: 500,107,862,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sat Jan 24 21:45:43 2009 CET SMART support is: Available - device has SMART capability. SMART support is: Enabled
=== START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED
General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 430) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 163) minutes.
SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 110 092 006 Pre-fail Always - 29099634 3 Spin_Up_Time 0x0003 095 093 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 452 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 084 061 030 Pre-fail Always - 296688016 9 Power_On_Hours 0x0032 097 097 000 Old_age Always - 2930 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 456 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 060 048 045 Old_age Always - 40 (Lifetime Min/Max 28/40) 194 Temperature_Celsius 0x0022 040 052 000 Old_age Always - 40 (0 16 0 0) 195 Hardware_ECC_Recovered 0x001a 065 052 000 Old_age Always - 1844796 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0 202 TA_Increase_Count 0x0032 100 253 000 Old_age Always - 0
SMART Error Log Version: 1 ATA Error Count: 2 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 2 occurred at disk power-on lifetime: 0 hours (0 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 SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
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 01 00 00 00 e0 00 00:04:39.592 READ DMA EXT b0 d9 00 00 4f c2 e0 00 00:04:39.559 SMART DISABLE OPERATIONS b0 d2 f1 00 4f c2 e0 00 00:04:39.559 SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE b0 d8 00 00 4f c2 e0 00 00:04:38.864 SMART ENABLE OPERATIONS 91 00 3f 00 00 00 ef 00 00:04:35.101 INITIALIZE DEVICE PARAMETERS [OBS-6]
Error 1 occurred at disk power-on lifetime: 0 hours (0 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 SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
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 01 00 00 00 e0 00 00:00:51.341 READ DMA EXT b0 d9 00 00 4f c2 e0 00 00:00:51.341 SMART DISABLE OPERATIONS b0 d2 f1 00 4f c2 e0 00 00:00:50.641 SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE b0 d8 00 00 4f c2 e0 00 00:00:46.867 SMART ENABLE OPERATIONS 91 00 3f 00 00 00 ef 00 00:00:39.156 INITIALIZE DEVICE PARAMETERS [OBS-6]
SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 2930 - # 2 Short offline Completed without error 00% 2929 - # 3 Short offline Completed without error 00% 2929 -
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.
Y el output smartctl 5.39 2008-10-24 22:33 [i686-suse-linux-gnu] (openSUSE RPM) Copyright (C) 2002-8 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.10 family Device Model: ST3500630A Serial Number: 9QG06MEN Firmware Version: 3.AAC User Capacity: 500,107,862,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sat Jan 24 22:09:31 2009 CET SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 430) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 163) minutes. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 110 092 006 Pre-fail Always - 29099634 3 Spin_Up_Time 0x0003 095 093 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 452 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 084 061 030 Pre-fail Always - 296702691 9 Power_On_Hours 0x0032 097 097 000 Old_age Always - 2930 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 456 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 061 048 045 Old_age Always - 39 (Lifetime Min/Max 28/40) 194 Temperature_Celsius 0x0022 039 052 000 Old_age Always - 39 (0 16 0 0) 195 Hardware_ECC_Recovered 0x001a 068 052 000 Old_age Always - 5194485 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0 202 TA_Increase_Count 0x0032 100 253 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 2 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 2 occurred at disk power-on lifetime: 0 hours (0 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 SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0 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 01 00 00 00 e0 00 00:04:39.592 READ DMA EXT b0 d9 00 00 4f c2 e0 00 00:04:39.559 SMART DISABLE OPERATIONS b0 d2 f1 00 4f c2 e0 00 00:04:39.559 SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE b0 d8 00 00 4f c2 e0 00 00:04:38.864 SMART ENABLE OPERATIONS 91 00 3f 00 00 00 ef 00 00:04:35.101 INITIALIZE DEVICE PARAMETERS [OBS-6] Error 1 occurred at disk power-on lifetime: 0 hours (0 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 SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0 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 01 00 00 00 e0 00 00:00:51.341 READ DMA EXT b0 d9 00 00 4f c2 e0 00 00:00:51.341 SMART DISABLE OPERATIONS b0 d2 f1 00 4f c2 e0 00 00:00:50.641 SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE b0 d8 00 00 4f c2 e0 00 00:00:46.867 SMART ENABLE OPERATIONS 91 00 3f 00 00 00 ef 00 00:00:39.156 INITIALIZE DEVICE PARAMETERS [OBS-6] SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 2930 - # 2 Short offline Completed without error 00% 2929 - # 3 Short offline Completed without error 00% 2929 - 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. -- Saludos. C�sar Enfr�ntate a los malos; enfr�ntate a los crueles; enfr�ntate a todos, menos a los tontos. Son demasiados y siempre ser�s derrotado. (Proverbio hind�) -- Para dar de baja la suscripción, mande un mensaje a: opensuse-es+unsubscribe@opensuse.org Para obtener el resto de direcciones-comando, mande un mensaje a: opensuse-es+help@opensuse.org
2009/1/24, csalinux:
Hola, alguien que sepa manejar smart... el short test me da el siguiente log: ?Alguien sabe qué quiere decir y si tiene arreglo?
¿Qué es lo que ves extraño? :-? *** Raw_Read_Error_Rate 0x000f 110 092 006 Pre-fail Always - 29099634 Spin_Up_Time 0x0003 095 093 000 Pre-fail Always - 0 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 Seek_Error_Rate 0x000f 084 061 030 Pre-fail Always - 296688016 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 *** Si te refieres a los valores elevados de "Raw_Read_Error_Rate" y "Seek_Error_Rate" yo los tengo peor en un disco Seagate: linux:~ # smartctl -A /dev/sda Raw_Read_Error_Rate 0x000f 118 100 006 Pre-fail Always - 173065346 Seek_Error_Rate 0x000f 082 060 030 Pre-fail Always - 176248168 Pero en otro Western Digital los tengo a "0". Luego me da que los Seagate tienen algún problema con estos valores... ... ... Je, ahora me has dejado a mí con la duda :-} Saludos, -- Camaleón -- Para dar de baja la suscripción, mande un mensaje a: opensuse-es+unsubscribe@opensuse.org Para obtener el resto de direcciones-comando, mande un mensaje a: opensuse-es+help@opensuse.org
Camaleón escribió:
2009/1/24, csalinux:
Hola, alguien que sepa manejar smart... el short test me da el siguiente log: ?Alguien sabe qué quiere decir y si tiene arreglo?
¿Qué es lo que ves extraño? :-?
*** Raw_Read_Error_Rate 0x000f 110 092 006 Pre-fail Always - 29099634 Spin_Up_Time 0x0003 095 093 000 Pre-fail Always - 0 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 Seek_Error_Rate 0x000f 084 061 030 Pre-fail Always - 296688016 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 ***
Si te refieres a los valores elevados de "Raw_Read_Error_Rate" y "Seek_Error_Rate" yo los tengo peor en un disco Seagate:
linux:~ # smartctl -A /dev/sda
Raw_Read_Error_Rate 0x000f 118 100 006 Pre-fail Always - 173065346 Seek_Error_Rate 0x000f 082 060 030 Pre-fail Always - 176248168
Pero en otro Western Digital los tengo a "0". Luego me da que los Seagate tienen algún problema con estos valores...
...
...
Je, ahora me has dejado a mí con la duda :-}
Saludos,
Tengo dos pares de discos gemelos. sda da log de smart, sdb, su gemelo, no. Los otros dos no dan fallo ninguno. sda y sdb son ide 133 sdc y sdd son sata 150 todos de 500 gb y de la marca que compró seagate que antes competía con ella, ahora no me acuerdo como se llamaba. -- Saludos. César Enfréntate a los malos; enfréntate a los crueles; enfréntate a todos, menos a los tontos. Son demasiados y siempre serás derrotado. (Proverbio hindú) -- Para dar de baja la suscripción, mande un mensaje a: opensuse-es+unsubscribe@opensuse.org Para obtener el resto de direcciones-comando, mande un mensaje a: opensuse-es+help@opensuse.org
El 24/01/09, csalinux escribió:
Tengo dos pares de discos gemelos. sda da log de smart, sdb, su gemelo, no.
Los otros dos no dan fallo ninguno.
sda y sdb son ide 133 sdc y sdd son sata 150
todos de 500 gb y de la marca que compró seagate que antes competía con ella, ahora no me acuerdo como se llamaba.
La marca es Maxtor. Pero el disco del que has sacado el log pone que es: *** Model Family: Seagate Barracuda 7200.10 family Device Model: ST3500630A *** Saludos, -- Camaleón -- Para dar de baja la suscripción, mande un mensaje a: opensuse-es+unsubscribe@opensuse.org Para obtener el resto de direcciones-comando, mande un mensaje a: opensuse-es+help@opensuse.org
Camaleón escribió:
El 24/01/09, csalinux escribió:
Tengo dos pares de discos gemelos. sda da log de smart, sdb, su gemelo, no.
Los otros dos no dan fallo ninguno.
sda y sdb son ide 133 sdc y sdd son sata 150
todos de 500 gb y de la marca que compró seagate que antes competía con ella, ahora no me acuerdo como se llamaba.
La marca es Maxtor.
Pero el disco del que has sacado el log pone que es:
*** Model Family: Seagate Barracuda 7200.10 family Device Model: ST3500630A ***
Saludos,
Pues puedo jurar que son MAXTOR los cuatro :), aunque ya veo que por dentro no lo son. -- Saludos. César Enfréntate a los malos; enfréntate a los crueles; enfréntate a todos, menos a los tontos. Son demasiados y siempre serás derrotado. (Proverbio hindú) -- Para dar de baja la suscripción, mande un mensaje a: opensuse-es+unsubscribe@opensuse.org Para obtener el resto de direcciones-comando, mande un mensaje a: opensuse-es+help@opensuse.org
Camaleón escribió:
El 24/01/09, csalinux escribió:
Tengo dos pares de discos gemelos. sda da log de smart, sdb, su gemelo, no.
Los otros dos no dan fallo ninguno.
sda y sdb son ide 133 sdc y sdd son sata 150
todos de 500 gb y de la marca que compró seagate que antes competía con ella, ahora no me acuerdo como se llamaba.
La marca es Maxtor.
Pero el disco del que has sacado el log pone que es:
*** Model Family: Seagate Barracuda 7200.10 family Device Model: ST3500630A ***
Saludos,
Por otra parte, en boot.msg, aparece lo siguiente: Starting udevd: done Loading drivers, configuring devices: done Loading required kernel modules doneActivating swap-devices in /etc/fstab... done[mntent]: warning: no final newline at the end of /etc/fstab Setting up the hardware clockdone Activating device mapper... done Starting MD Raid mdadm: /dev/md/0 has been started with 2 drives. mdadm: /dev/md/1 has been started with 2 drives. mdadm: /dev/md/2 has been started with 2 drives. mdadm: /dev/md/3 has been started with 2 drives. mdadm: /dev/md/4 has been started with 2 drives. mdadm: /dev/md/5 has been started with 2 drives. mdadm: /dev/md/6 has been started with 2 drives. mdadm: /dev/md/7 has been started with 2 drives. mdadm: /dev/md/9 has been started with 2 drives. mdadm: /dev/md/10 has been started with 2 drives. mdadm: /dev/md/11 has been started with 2 drives. mdadm: /dev/md/12 has been started with 2 drives. failed ¿Cómo puedo saber si el raid está realmente trabajando bien? Otra cosa, ¿cuál es el módulo del kernel que maneja el raid? -- Saludos. César Enfréntate a los malos; enfréntate a los crueles; enfréntate a todos, menos a los tontos. Son demasiados y siempre serás derrotado. (Proverbio hindú) -- Para dar de baja la suscripción, mande un mensaje a: opensuse-es+unsubscribe@opensuse.org Para obtener el resto de direcciones-comando, mande un mensaje a: opensuse-es+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2009-01-24 a las 23:11 +0100, csalinux escribió:
Por otra parte, en boot.msg, aparece lo siguiente:
Starting udevd: done Loading drivers, configuring devices: done Loading required kernel modules doneActivating swap-devices in /etc/fstab... done[mntent]: warning: no final newline at the end of /etc/fstab
Te falta un final de linea al final del fstab - puede tener problemas para leer la ultima linea.
Setting up the hardware clockdone Activating device mapper... done Starting MD Raid mdadm: /dev/md/0 has been started with 2 drives. mdadm: /dev/md/1 has been started with 2 drives. mdadm: /dev/md/2 has been started with 2 drives. mdadm: /dev/md/3 has been started with 2 drives. mdadm: /dev/md/4 has been started with 2 drives. mdadm: /dev/md/5 has been started with 2 drives. mdadm: /dev/md/6 has been started with 2 drives. mdadm: /dev/md/7 has been started with 2 drives. mdadm: /dev/md/9 has been started with 2 drives. mdadm: /dev/md/10 has been started with 2 drives. mdadm: /dev/md/11 has been started with 2 drives. mdadm: /dev/md/12 has been started with 2 drives. failed
¿Cómo puedo saber si el raid está realmente trabajando bien?
En el /var/log/messages debiera sacar los problemas. Prueba: mdadm --detail /dev/md0
Otra cosa, ¿cuál es el módulo del kernel que maneja el raid?
Bueno, uno se llama 'raid1', el resto no lo recuerdo. - -- Saludos Carlos E.R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkl7pK8ACgkQtTMYHG2NR9WZqgCeKK5e6ppKMbBZ3Ii4HXIwy8MC 2fwAn3srFXEDG3CFkMNidVshCZVfbyJV =nAVR -----END PGP SIGNATURE-----
Carlos E. R. escribió:
Prueba:
mdadm --detail /dev/md0
Otra cosa, ¿cuál es el módulo del kernel que maneja el raid?
Bueno, uno se llama 'raid1', el resto no lo recuerdo.
Todo parece OK. Gracias.
-- Saludos Carlos E.R.
-- Saludos. César Enfréntate a los malos; enfréntate a los crueles; enfréntate a todos, menos a los tontos. Son demasiados y siempre serás derrotado. (Proverbio hindú) -- Para dar de baja la suscripción, mande un mensaje a: opensuse-es+unsubscribe@opensuse.org Para obtener el resto de direcciones-comando, mande un mensaje a: opensuse-es+help@opensuse.org
Carlos E. R. escribió:
Otra cosa, ¿cuál es el módulo del kernel que maneja el raid?
Bueno, uno se llama 'raid1', el resto no lo recuerdo.
-- Saludos Carlos E.R.
Estoy torpe ultimamente :) lsmod | grep raid* raid456 137232 0 async_xor 3232 1 raid456 async_memcpy 2168 1 raid456 async_tx 3352 3 raid456,async_xor,async_memcpy xor 16280 2 raid456,async_xor raid0 6608 0 raid1 19940 13 :) -- Saludos. César Enfréntate a los malos; enfréntate a los crueles; enfréntate a todos, menos a los tontos. Son demasiados y siempre serás derrotado. (Proverbio hindú) -- Para dar de baja la suscripción, mande un mensaje a: opensuse-es+unsubscribe@opensuse.org Para obtener el resto de direcciones-comando, mande un mensaje a: opensuse-es+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2009-01-25 a las 01:37 +0100, csalinux escribió:
Otra cosa, ¿cuál es el módulo del kernel que maneja el raid?
Bueno, uno se llama 'raid1', el resto no lo recuerdo.
Estoy torpe ultimamente :)
lsmod | grep raid*
raid456 137232 0 async_xor 3232 1 raid456 async_memcpy 2168 1 raid456 async_tx 3352 3 raid456,async_xor,async_memcpy xor 16280 2 raid456,async_xor raid0 6608 0 raid1 19940 13
:)
A mi sólo me sale raid1. Por lo que veo sólo se carga ese con un raid por software de tipo 1. - -- Saludos Carlos E.R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkl7wyYACgkQtTMYHG2NR9XnUQCfS9DRQq338bOINtoxPD7iJ/tC ASkAoJjz4tE2DifD4QUcP0uCQ1M8wtJi =n16Y -----END PGP SIGNATURE-----
Carlos E. R. escribió:
El 2009-01-25 a las 01:37 +0100, csalinux escribió:
Otra cosa, ¿cuál es el módulo del kernel que maneja el raid?
Bueno, uno se llama 'raid1', el resto no lo recuerdo.
Estoy torpe ultimamente :)
lsmod | grep raid*
raid456 137232 0 async_xor 3232 1 raid456 async_memcpy 2168 1 raid456 async_tx 3352 3 raid456,async_xor,async_memcpy xor 16280 2 raid456,async_xor raid0 6608 0 raid1 19940 13
:)
A mi sólo me sale raid1. Por lo que veo sólo se carga ese con un raid por software de tipo 1.
-- Saludos Carlos E.R.
Yo sólo tengo raid1 por software. En la Bios está desactivado el fake raid. -- Saludos. César Enfréntate a los malos; enfréntate a los crueles; enfréntate a todos, menos a los tontos. Son demasiados y siempre serás derrotado. (Proverbio hindú) -- Para dar de baja la suscripción, mande un mensaje a: opensuse-es+unsubscribe@opensuse.org Para obtener el resto de direcciones-comando, mande un mensaje a: opensuse-es+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2009-01-25 a las 02:43 +0100, csalinux escribió:
lsmod | grep raid*
raid456 137232 0 async_xor 3232 1 raid456 async_memcpy 2168 1 raid456 async_tx 3352 3 raid456,async_xor,async_memcpy xor 16280 2 raid456,async_xor raid0 6608 0 raid1 19940 13
:)
A mi sólo me sale raid1. Por lo que veo sólo se carga ese con un raid por software de tipo 1.
Yo sólo tengo raid1 por software. En la Bios está desactivado el fake raid.
Según la lista de módulos, también tienes un raid 0 y un raid 456. Al menos, los detecta por algún sitio aunque no se usen. Prueba "cat /proc/mdstat". - -- Saludos Carlos E.R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkl7zlAACgkQtTMYHG2NR9XcFwCfXoJU+Irdz0QSGETkzBU6w/l0 QTcAnjKr4JLDrC4ZAfkWoPfrJ0pc569I =/pxO -----END PGP SIGNATURE-----
Carlos E. R. escribió:
Según la lista de módulos, también tienes un raid 0 y un raid 456. Al menos, los detecta por algún sitio aunque no se usen.
Prueba "cat /proc/mdstat".
-- Saludos Carlos E.R.
linux-ax2:~> cat /proc/mdstat Personalities : [raid1] [raid0] [raid6] [raid5] [raid4] md12 : active raid1 sda12[0] sdb12[1] 262927652 blocks super 1.0 [2/2] [UU] bitmap: 8/502 pages [32KB], 256KB chunk md11 : active raid1 sda10[0] sdb10[1] 20972752 blocks super 1.0 [2/2] [UU] bitmap: 10/161 pages [40KB], 64KB chunk md10 : active raid1 sda9[0] sdb9[1] 20972752 blocks super 1.0 [2/2] [UU] bitmap: 0/161 pages [0KB], 64KB chunk md9 : active raid1 sda8[0] sdb8[1] 10482308 blocks super 1.0 [2/2] [UU] bitmap: 4/160 pages [16KB], 32KB chunk md7 : active raid1 sda6[0] sdb6[1] 1052212 blocks super 1.0 [2/2] [UU] bitmap: 0/9 pages [0KB], 64KB chunk md6 : active raid1 sdc10[0] sdd10[1] 262911588 blocks super 1.0 [2/2] [UU] bitmap: 0/502 pages [0KB], 256KB chunk md5 : active raid1 sdc8[0] sdd8[1] 20972752 blocks super 1.0 [2/2] [UU] bitmap: 0/161 pages [0KB], 64KB chunk md4 : active raid1 sdc7[0] sdd7[1] 20972752 blocks super 1.0 [2/2] [UU] bitmap: 0/161 pages [0KB], 64KB chunk md3 : active raid1 sdc6[0] sdd6[1] 10490340 blocks super 1.0 [2/2] [UU] bitmap: 0/161 pages [0KB], 32KB chunk md2 : active raid1 sdc5[0] sdd5[1] 41945608 blocks super 1.0 [2/2] [UU] bitmap: 0/161 pages [0KB], 128KB chunk md1 : active raid1 sdc2[0] sdd2[1] 1052212 blocks super 1.0 [2/2] [UU] bitmap: 0/9 pages [0KB], 64KB chunk md0 : active raid1 sdc1[0] sdd1[1] 125837040 blocks super 1.0 [2/2] [UU] bitmap: 0/241 pages [0KB], 256KB chunk md8 : active raid1 sda7[0] sdb7[1] 41945608 blocks super 1.0 [2/2] [UU] bitmap: 17/161 pages [68KB], 128KB chunk unused devices: <none> linux-ax2:~> -- Saludos. César Enfréntate a los malos; enfréntate a los crueles; enfréntate a todos, menos a los tontos. Son demasiados y siempre serás derrotado. (Proverbio hindú) -- Para dar de baja la suscripción, mande un mensaje a: opensuse-es+unsubscribe@opensuse.org Para obtener el resto de direcciones-comando, mande un mensaje a: opensuse-es+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2009-01-25 a las 03:35 +0100, csalinux escribió:
Carlos E. R. escribió:
Según la lista de módulos, también tienes un raid 0 y un raid 456. Al menos, los detecta por algún sitio aunque no se usen.
Prueba "cat /proc/mdstat".
linux-ax2:~> cat /proc/mdstat Personalities : [raid1] [raid0] [raid6] [raid5] [raid4]
Ahí lo tienes: ha considerado diferentes tipos de raid, los tienes listados. A mí sólo me sale raid1. El motivo por el que lo hace así, no lo se. Y dale a la tecla de borrar lineas de vez en cuando, anda. - -- Saludos Carlos E.R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkl70t0ACgkQtTMYHG2NR9WteACeLR6tw/B4WNgBoaD4mpyOfQRg 6xEAn2f6TV6QJOY+OB75kyZHc47305MQ =65MV -----END PGP SIGNATURE-----
Carlos E. R. escribió:
Y dale a la tecla de borrar lineas de vez en cuando, anda.
-- Saludos Carlos E.R.
Me parece que le he dado ;). Te veo gruñón. :P -- Saludos. César Enfréntate a los malos; enfréntate a los crueles; enfréntate a todos, menos a los tontos. Son demasiados y siempre serás derrotado. (Proverbio hindú) -- Para dar de baja la suscripción, mande un mensaje a: opensuse-es+unsubscribe@opensuse.org Para obtener el resto de direcciones-comando, mande un mensaje a: opensuse-es+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-ID:
Camaleón escribió:
Pero en otro Western Digital los tengo a "0". Luego me da que los Seagate tienen algún problema con estos valores...
Son tipicos, se corrigen.
Tengo dos pares de discos gemelos. sda da log de smart, sdb, su gemelo, no.
Pues el que no da log es el malo >:-)
Los otros dos no dan fallo ninguno.
¿Y que fallo te da este? Yo no veo ninguno. - -- Saludos Carlos E.R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkl7lIYACgkQtTMYHG2NR9UkgQCfade1MYtH3hIwewEJ+Alrrvby EqkAmwYO1gT98oDauGXhG2icBRkQPma1 =zglV -----END PGP SIGNATURE-----
participants (3)
-
Camaleón -
Carlos E. R. -
csalinux