This is the old XigmaNAS forum in read only mode,
it will taken offline by the end of march 2021!



I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!

[Résolu]Problème de disques et remplacement sur Raidz1

French community

Moderators: velivole18, ernie, mtiburs

Forum rules
Set-Up GuideFAQsForum Rules
User avatar
lulu80
PowerUser
PowerUser
Posts: 763
Joined: 15 Jun 2014 12:15
Location: France-(Picardie 80)
Contact:
Status: Offline

[Résolu]Problème de disques et remplacement sur Raidz1

Post by lulu80 »

bonjour
ce matin j'ai ceci sur le nas après un reboot , cela correspond a un disque de mon pool1 peut ont me dire ?
Jul 26 07:15:46 nas4free kernel: (ada4:ahcich4:0:0:0): Retrying command
Jul 26 07:15:46 nas4free kernel: (ada4:ahcich4:0:0:0): RES: 41 40 98 94 00 00 00 00 00 00 00
Jul 26 07:15:46 nas4free kernel: (ada4:ahcich4:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
Jul 26 07:15:46 nas4free kernel: (ada4:ahcich4:0:0:0): CAM status: ATA Status Error
Jul 26 07:15:46 nas4free kernel: (ada4:ahcich4:0:0:0): READ_FPDMA_QUEUED. ACB: 60 50 88 94 00 40 00 00 00 00 00 00
Jul 26 07:14:26 nas4free kernel: (ada4:ahcich4:0:0:0): Retrying command
Jul 26 07:14:26 nas4free kernel: (ada4:ahcich4:0:0:0): RES: 41 40 68 8d 00 00 00 00 00 00 00
Jul 26 07:14:26 nas4free kernel: (ada4:ahcich4:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC )
Jul 26 07:14:26 nas4free kernel: (ada4:ahcich4:0:0:0): CAM status: ATA Status Error
Jul 26 07:14:25 nas4free kernel: (ada4:ahcich4:0:0:0): READ_FPDMA_QUEUED. ACB: 60 50 50 8d 00 40 00 00 00 00 00 00
j'ai fait un zpool status mais il semble normal
zpool status.PNG
You do not have the required permissions to view the files attached to this post.
Last edited by lulu80 on 03 Jan 2016 19:01, edited 2 times in total.
Version 11.2.0.4 - Omnius (revision 6400)
https://lucinfordi.fr

User avatar
velivole18
Forum Moderator
Forum Moderator
Posts: 647
Joined: 14 Jul 2012 20:23
Location: France
Status: Offline

Re: Problème de disque

Post by velivole18 »

Bonjour,

Je pencherai tout d'abord pour un problème temporaire de connectique et je vérifierai mes câbles et connexions physiques.
Le matériel souffre actuellement par les fortes chaleurs.
Je ferai aussi un SMART complet pour voir ce qu'il en sort.
J'ai déjà eu ce type d'erreur et à chaque fois SMART sortait effectivement un problème, en général pas très bon ...

Cordialement.
11.2.0.4 - Omnius (revision 6026) x64-embedded
111909 RSDT1411 AMD Athlon(tm) 64 Processor 4000+ 4096MiB RAM - HDD 2 x 6 To in ZFS mirroring + 2 x (2 x 4To in ZFS mirroring) - SSD 32Go - UPS EATON Ellipse MAX 1100.

User avatar
lulu80
PowerUser
PowerUser
Posts: 763
Joined: 15 Jun 2014 12:15
Location: France-(Picardie 80)
Contact:
Status: Offline

Re: Problème de disque

Post by lulu80 »

bonjours
voici les rapport des disques qui présente des défaut

Code: Select all

Périphérique /dev/ada3 - Seagate Barracuda 7200.14 (AF)
=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.14 (AF)
Device Model:     ST1000DM003-1CH162
Serial Number:    Z1D5HXQV
LU WWN Device Id: 5 000c50 05d084d2a
Firmware Version: CC49
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Jul 26 11:59:03 2015 CEST
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:       (  575) 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   115   099   006    Pre-fail  Always       -       92059472
  3 Spin_Up_Time            0x0003   098   097   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       249
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       72
  7 Seek_Error_Rate         0x000f   080   060   030    Pre-fail  Always       -       100667672
  9 Power_On_Hours          0x0032   094   094   000    Old_age   Always       -       5736
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       244
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   019   019   000    Old_age   Always       -       81
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0 0 0
189 High_Fly_Writes         0x003a   099   099   000    Old_age   Always       -       1
190 Airflow_Temperature_Cel 0x0022   067   059   045    Old_age   Always       -       33 (Min/Max 31/33)
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       -       41
193 Load_Cycle_Count        0x0032   097   097   000    Old_age   Always       -       6801
194 Temperature_Celsius     0x0022   033   041   000    Old_age   Always       -       33 (0 13 0 0 0)
197 Current_Pending_Sector  0x0012   100   099   000    Old_age   Always       -       56
198 Offline_Uncorrectable   0x0010   100   099   000    Old_age   Offline      -       56
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       5561h+09m+09.663s
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       4071092662
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       11201531128

SMART Error Log Version: 1
ATA Error Count: 81 (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 81 occurred at disk power-on lifetime: 4511 hours (187 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 38 3f 93 0d  Error: UNC at LBA = 0x0d933f38 = 227753784

  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 58 6e 13 40 00   4d+15:16:07.738  READ FPDMA QUEUED
  60 00 08 98 f6 05 4f 00   4d+15:16:07.738  READ FPDMA QUEUED
  60 00 08 90 3e 0c 4d 00   4d+15:16:07.738  READ FPDMA QUEUED
  61 00 00 ff ff ff 4f 00   4d+15:16:07.738  WRITE FPDMA QUEUED
  60 00 08 40 45 b2 4b 00   4d+15:16:07.738  READ FPDMA QUEUED

Error 80 occurred at disk power-on lifetime: 4511 hours (187 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 38 3f 93 0d  Error: UNC at LBA = 0x0d933f38 = 227753784

  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 58 6e 13 40 00   4d+15:16:04.230  READ FPDMA QUEUED
  60 00 08 98 f6 05 4f 00   4d+15:16:04.183  READ FPDMA QUEUED
  60 00 08 90 3e 0c 4d 00   4d+15:16:04.155  READ FPDMA QUEUED
  61 00 00 ff ff ff 4f 00   4d+15:16:04.144  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00   4d+15:16:04.130  WRITE FPDMA QUEUED

Error 79 occurred at disk power-on lifetime: 4511 hours (187 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 38 3f 93 0d  Error: UNC at LBA = 0x0d933f38 = 227753784

  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 38 3e 0c 4d 00   4d+15:16:00.530  READ FPDMA QUEUED
  60 00 08 e8 6b 13 40 00   4d+15:16:00.529  READ FPDMA QUEUED
  61 00 00 ff ff ff 4f 00   4d+15:16:00.522  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00   4d+15:16:00.505  WRITE FPDMA QUEUED
  60 00 08 40 45 b2 4b 00   4d+15:16:00.501  READ FPDMA QUEUED

Error 78 occurred at disk power-on lifetime: 4511 hours (187 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 38 3f 93 0d  Error: UNC at LBA = 0x0d933f38 = 227753784

  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 40 45 b2 4b 00   4d+15:16:00.324  READ FPDMA QUEUED
  60 00 08 10 3e 0c 4d 00   4d+15:15:56.951  READ FPDMA QUEUED
  60 00 08 d8 6b 13 40 00   4d+15:15:56.927  READ FPDMA QUEUED
  61 00 00 ff ff ff 4f 00   4d+15:15:56.926  WRITE FPDMA QUEUED
  61 00 40 ff ff ff 4f 00   4d+15:15:56.924  WRITE FPDMA QUEUED

Error 77 occurred at disk power-on lifetime: 4511 hours (187 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 38 3f 93 0d  Error: WP at LBA = 0x0d933f38 = 227753784

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 08 e0 e6 93 4d 00   4d+15:15:55.723  WRITE FPDMA QUEUED
  60 00 58 08 93 93 4d 00   4d+15:15:54.298  READ FPDMA QUEUED
  60 00 08 50 6a 13 40 00   4d+15:15:53.107  READ FPDMA QUEUED
  60 00 08 80 3b 0c 4d 00   4d+15:15:53.093  READ FPDMA QUEUED
  60 00 08 30 3b 0c 4d 00   4d+15:15:53.092  READ FPDMA QUEUED

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.

Code: Select all

Périphérique /dev/ada5 - KingFast
=== START OF INFORMATION SECTION ===
Device Model:     KingFast
Serial Number:    SZHYPO14092804D0264
LU WWN Device Id: 5 dc663a c8200022f
Firmware Version: 1.092.37
User Capacity:    32,010,928,128 bytes [32.0 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2 T13/2015-D revision 3
SATA Version is:  SATA >3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Jul 26 11:59:03 2015 CEST
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:       (   32) 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:     (   1) minutes.
SCT capabilities:           (0x0039)   SCT Status supported.
               SCT Error Recovery Control supported.
               SCT Feature Control supported.
               SCT Data Table supported.

SMART Attributes Data Structure revision number: 0
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000a   100   100   000    Old_age   Always       -       0
  2 Throughput_Performance  0x0005   100   100   050    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0007   100   100   050    Pre-fail  Always       -       0
  5 Reallocated_Sector_Ct   0x0013   100   100   050    Pre-fail  Always       -       0
  7 Unknown_SSD_Attribute   0x000b   100   100   050    Pre-fail  Always       -       0
  8 Unknown_SSD_Attribute   0x0005   100   100   050    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       5386
 10 Unknown_SSD_Attribute   0x0013   100   100   050    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0012   100   100   000    Old_age   Always       -       190
167 Unknown_Attribute       0x0022   100   100   000    Old_age   Always       -       0
168 Unknown_Attribute       0x0012   100   100   000    Old_age   Always       -       0
169 Unknown_Attribute       0x0013   100   100   010    Pre-fail  Always       -       524290
170 Unknown_Attribute       0x0013   100   100   010    Pre-fail  Always       -       0
173 Unknown_Attribute       0x0012   197   197   000    Old_age   Always       -       4297588771
175 Program_Fail_Count_Chip 0x0013   100   100   010    Pre-fail  Always       -       0
180 Unused_Rsvd_Blk_Cnt_Tot 0x0033   100   100   020    Pre-fail  Always       -       34
192 Power-Off_Retract_Count 0x0012   100   100   000    Old_age   Always       -       32
194 Temperature_Celsius     0x0022   075   075   030    Old_age   Always       -       25 (0 60 0 30 0)
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
231 Temperature_Celsius     0x0033   099   099   005    Pre-fail  Always       -       1
240 Unknown_SSD_Attribute   0x0013   100   100   050    Pre-fail  Always       -       0
241 Total_LBAs_Written      0x0032   100   100   000    Old_age   Always       -       1023780387
242 Total_LBAs_Read         0x0032   100   100   000    Old_age   Always       -       455900282

SMART Error Log Version: 1
ATA Error Count: 552 (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 552 occurred at disk power-on lifetime: 461 hours (19 days + 5 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 41 00 00 00 00 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 00 00 00 00 00 00 08      00:08:18.805  NOP [Abort queued commands]
  ef 02 00 00 00 00 40 08      00:08:18.642  SET FEATURES [Enable write cache]
  ef aa 00 00 00 00 40 08      00:08:18.642  SET FEATURES [Enable read look-ahead]
  c6 00 01 00 00 00 40 08      00:08:18.642  SET MULTIPLE MODE
  ef 10 02 00 00 00 40 08      00:08:18.642  SET FEATURES [Enable SATA feature]

Error 551 occurred at disk power-on lifetime: 461 hours (19 days + 5 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 41 00 00 00 00 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 00 00 00 00 00 00 08      00:08:09.855  NOP [Abort queued commands]
  e3 00 00 00 00 00 40 08      00:08:06.872  IDLE
  ef 05 fe 00 00 00 40 08      00:08:06.872  SET FEATURES [Enable APM]
  ec 00 00 00 00 00 40 08      00:08:06.872  IDENTIFY DEVICE
  ea 00 00 00 00 00 40 08      00:07:53.820  FLUSH CACHE EXT

Error 550 occurred at disk power-on lifetime: 461 hours (19 days + 5 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 41 00 00 00 00 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 00 00 00 00 00 00 08      00:01:40.802  NOP [Abort queued commands]
  ef 02 00 00 00 00 40 08      00:01:40.655  SET FEATURES [Enable write cache]
  ef aa 00 00 00 00 40 08      00:01:40.655  SET FEATURES [Enable read look-ahead]
  c6 00 01 00 00 00 40 08      00:01:40.655  SET MULTIPLE MODE
  ef 10 02 00 00 00 40 08      00:01:40.655  SET FEATURES [Enable SATA feature]

Error 549 occurred at disk power-on lifetime: 461 hours (19 days + 5 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 41 00 00 00 00 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 00 00 00 00 00 00 08      00:01:40.575  NOP [Abort queued commands]
  ef 02 00 00 00 00 40 08      00:01:20.185  SET FEATURES [Enable write cache]
  ef aa 00 00 00 00 40 08      00:01:20.185  SET FEATURES [Enable read look-ahead]
  c6 00 01 00 00 00 40 08      00:01:20.185  SET MULTIPLE MODE
  ef 10 02 00 00 00 40 08      00:01:20.182  SET FEATURES [Enable SATA feature]

Error 548 occurred at disk power-on lifetime: 458 hours (19 days + 2 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 41 00 00 00 00 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 00 00 00 00 00 00 08      21:52:39.185  NOP [Abort queued commands]
  b0 d5 01 09 4f c2 40 08      20:16:37.295  SMART READ LOG
  b0 d5 01 06 4f c2 40 08      20:16:37.295  SMART READ LOG
  b0 d5 01 01 4f c2 40 08      20:16:37.295  SMART READ LOG
  b0 d5 01 00 4f c2 40 08      20:16:37.295  SMART READ LOG

Warning! SMART Self-Test Log Structure error: invalid SMART checksum.
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.
Version 11.2.0.4 - Omnius (revision 6400)
https://lucinfordi.fr

User avatar
b0ssman
Forum Moderator
Forum Moderator
Posts: 2438
Joined: 14 Feb 2013 08:34
Location: Munich, Germany
Status: Offline

Re: Problème de disque

Post by b0ssman »

replace ada3 immediately
remplacer immédiatement le lecteur

5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 72
Nas4Free 11.1.0.4.4517. Supermicro X10SLL-F, 16gb ECC, i3 4130, IBM M1015 with IT firmware. 4x 3tb WD Red, 4x 2TB Samsung F4, both GEOM AES 256 encrypted.

sleid
PowerUser
PowerUser
Posts: 774
Joined: 23 Jun 2012 07:36
Location: FRANCE LIMOUSIN CORREZE
Status: Offline

Re: Problème de disque

Post by sleid »

Il manque le smart d'ada4 s'il est en plus mauvais état qu'ada3 il faudra prioriser entre les deux
12.1.0.4 - Ingva (revision 7852)
FreeBSD 12.1-RELEASE-p12 #0 r368465M: Tue Dec 8 23:25:11 CET 2020
X64-embedded sur Intel(R) Atom(TM) CPU C2750 @ 2.40GHz Boot UEFI
ASRock C2750D4I 2 X 8GB DDR3 ECC
Pool of 2 vdev Raidz1: 3 WDC WD40EFRX + 3 WDC WD40EFRX

User avatar
lulu80
PowerUser
PowerUser
Posts: 763
Joined: 15 Jun 2014 12:15
Location: France-(Picardie 80)
Contact:
Status: Offline

Re: Problème de disque

Post by lulu80 »

Code: Select all

Périphérique /dev/ada4 - Western Digital Caviar Blue (SATA 6Gb/s)
=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar Blue (SATA 6Gb/s)
Device Model:     WDC WD10EZEX-08M2NA0
Serial Number:    WD-WCC3F5371374
LU WWN Device Id: 5 0014ee 20a3fb7bd
Firmware Version: 01.01A01
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Jul 26 13:18:59 2015 CEST
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: 		(11400) seconds.
Offline data collection
capabilities: 			 (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 routine
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 118) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x3035)	SCT Status 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          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       1676
  3 Spin_Up_Time            0x0027   174   172   021    Pre-fail  Always       -       2258
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       425
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   092   092   000    Old_age   Always       -       6285
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       390
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       53
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       526
194 Temperature_Celsius     0x0022   111   102   000    Old_age   Always       -       32
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       31
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       21
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       50

SMART Error Log Version: 1
No Errors Logged

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.
Version 11.2.0.4 - Omnius (revision 6400)
https://lucinfordi.fr

User avatar
lulu80
PowerUser
PowerUser
Posts: 763
Joined: 15 Jun 2014 12:15
Location: France-(Picardie 80)
Contact:
Status: Offline

Re: Problème de disque

Post by lulu80 »

faut il que je change que seulement ada03 ?
edit: que doit-je faire dans l'immédiat :?
Version 11.2.0.4 - Omnius (revision 6400)
https://lucinfordi.fr

sleid
PowerUser
PowerUser
Posts: 774
Joined: 23 Jun 2012 07:36
Location: FRANCE LIMOUSIN CORREZE
Status: Offline

Re: Problème de disque

Post by sleid »

D'abord ada03 (5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 72)

puis ada04 :
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 1676 doit être à 0 pour les WD (dégradation)
198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 21 début de dégradation mais peut revenir à 0
200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 50 idem ci-dessus confirme la ligne 1

A priori pas de problème de connectique (199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0).
12.1.0.4 - Ingva (revision 7852)
FreeBSD 12.1-RELEASE-p12 #0 r368465M: Tue Dec 8 23:25:11 CET 2020
X64-embedded sur Intel(R) Atom(TM) CPU C2750 @ 2.40GHz Boot UEFI
ASRock C2750D4I 2 X 8GB DDR3 ECC
Pool of 2 vdev Raidz1: 3 WDC WD40EFRX + 3 WDC WD40EFRX

User avatar
lulu80
PowerUser
PowerUser
Posts: 763
Joined: 15 Jun 2014 12:15
Location: France-(Picardie 80)
Contact:
Status: Offline

Re: Problème de disque

Post by lulu80 »

Merci , je vais changer le ada03 il et encore garanti (sa fera la deuxième fois pour se seagate) donc je le remplacer par WD
et ensuite je ferait le ada04 qui lui doit être aussi en garanti
en attendent puis je remplacer le ada03 par un plus gros (2To) et remettre un 1 To quand il me sera livré ?
ou bien le nas doit être arrêter pendant se temps ?
Version 11.2.0.4 - Omnius (revision 6400)
https://lucinfordi.fr

User avatar
velivole18
Forum Moderator
Forum Moderator
Posts: 647
Joined: 14 Jul 2012 20:23
Location: France
Status: Offline

Re: Problème de disque

Post by velivole18 »

Bonjour,

Pour ma part, dans cette situation, je n'utilise plus le Nas avant changement des disques.
De plus, à l'achat des disques et avant de les installer dans le NAS, je remets les disques à zéro par un formatage bas niveau.
Au moindre problème lors du formatage bas niveau, je les renvoie pour échange au fournisseur.
Je ne monte un disque dans mon NAS que si il y a zéro défaut.

Cordialement.
11.2.0.4 - Omnius (revision 6026) x64-embedded
111909 RSDT1411 AMD Athlon(tm) 64 Processor 4000+ 4096MiB RAM - HDD 2 x 6 To in ZFS mirroring + 2 x (2 x 4To in ZFS mirroring) - SSD 32Go - UPS EATON Ellipse MAX 1100.

sleid
PowerUser
PowerUser
Posts: 774
Joined: 23 Jun 2012 07:36
Location: FRANCE LIMOUSIN CORREZE
Status: Offline

Re: Problème de disque

Post by sleid »

oui, il restera limité à 1 to puisque c'est du mirroring

Pour le WD il est toujours préférable de demander la rma avec un résultat de Data Lifeguard Diagnostic (utilitaire wd)
12.1.0.4 - Ingva (revision 7852)
FreeBSD 12.1-RELEASE-p12 #0 r368465M: Tue Dec 8 23:25:11 CET 2020
X64-embedded sur Intel(R) Atom(TM) CPU C2750 @ 2.40GHz Boot UEFI
ASRock C2750D4I 2 X 8GB DDR3 ECC
Pool of 2 vdev Raidz1: 3 WDC WD40EFRX + 3 WDC WD40EFRX

User avatar
lulu80
PowerUser
PowerUser
Posts: 763
Joined: 15 Jun 2014 12:15
Location: France-(Picardie 80)
Contact:
Status: Offline

Re: Problème de disque

Post by lulu80 »

je vais donc démonter mon pool2 2x2 To qui lui et vide et placer l'un des disque sur le pool1 mais
Comment procédé pour faire l'échange entre le ada3 1 To et le ada8 2 To sans perdre mes données qui se trouve sur
le pool1 raidz1 ?
"mon pool1 qui se compose de 4x1 To raidz1 (3WD et 1 Segeate)"
Version 11.2.0.4 - Omnius (revision 6400)
https://lucinfordi.fr

User avatar
lulu80
PowerUser
PowerUser
Posts: 763
Joined: 15 Jun 2014 12:15
Location: France-(Picardie 80)
Contact:
Status: Offline

Re: Problème de disque

Post by lulu80 »

par ailleurs j'ai le ada4 qui me donne une error 5, retries exhausted qui me fait ramer le nas et le rend inaccessible
ne serait il pas mieux de le remplacer aussi ?
Version 11.2.0.4 - Omnius (revision 6400)
https://lucinfordi.fr

sleid
PowerUser
PowerUser
Posts: 774
Joined: 23 Jun 2012 07:36
Location: FRANCE LIMOUSIN CORREZE
Status: Offline

Re: Problème de disque

Post by sleid »

Après avoir démonté le pool2 Il faut mettre à "0"(voir post velivole18) l'ada8 autrement la sécurité de ZFS détectera un autre pool et refusera de s'en servir.

Mettre offline ada3 puis vérifier dans l'état du pool le nom donné à ada3 (exemple 12007307646702120630 was ada3)
arrêter le nas, changer physiquement ada3 par l'ex ada8
remettre en marche le nas
Exécuter zpool replace pool1 12007307646702120630 ada3
le resilvering va démarrer et le pool retrouvera son état initial

IMPORTANT
Si ada4 ralenti le nas changez celui-ci en premier autrement la reconstruction prendra des jours.
12.1.0.4 - Ingva (revision 7852)
FreeBSD 12.1-RELEASE-p12 #0 r368465M: Tue Dec 8 23:25:11 CET 2020
X64-embedded sur Intel(R) Atom(TM) CPU C2750 @ 2.40GHz Boot UEFI
ASRock C2750D4I 2 X 8GB DDR3 ECC
Pool of 2 vdev Raidz1: 3 WDC WD40EFRX + 3 WDC WD40EFRX

User avatar
lulu80
PowerUser
PowerUser
Posts: 763
Joined: 15 Jun 2014 12:15
Location: France-(Picardie 80)
Contact:
Status: Offline

Re: Problème de disque

Post by lulu80 »

Il faut mettre à "0" l'ada8
c'est le re formaté avec un formatage lent c'est sa ?
vérifier dans l'état du pool le nom donné à ada3
ou puis je vérifier cela ?
Exécuter zpool replace pool1 12007307646702120630 ada3
en ligne de commande ?
Version 11.2.0.4 - Omnius (revision 6400)
https://lucinfordi.fr

User avatar
mtiburs
Forum Moderator
Forum Moderator
Posts: 951
Joined: 09 Aug 2012 23:34
Location: France - Besançon
Status: Offline

Re: Problème de disque

Post by mtiburs »

velivole18 wrote:De plus, à l'achat des disques et avant de les installer dans le NAS, je remets les disques à zéro par un formatage bas niveau.
Tu utilises quoi ?
Serveur Intel bi-Xéon P5530 / 8 X Ubuntu Serveur 18.04 LTS - ZFS-BTRFS-bcache / ~30 x PI2b(ARM) sous Nas4Free / et ...(chhhut)... 1 seul Xigmanas :o ... et pas à jour en plus :oops: (çà craint)
Conception d'un "système bizarre" :mrgreen: de "super-devices-autonomes" en NFS gérés par des micro-serveurs SAN(+nas) sous N4F (11 super-devs en raidz3) taille actuelle: 16To / prévue: 64To / théorique: 320To (consommation < 15W en veille - 24/24h) en service depuis 2 ans.

User avatar
mtiburs
Forum Moderator
Forum Moderator
Posts: 951
Joined: 09 Aug 2012 23:34
Location: France - Besançon
Status: Offline

Re: Problème de disque

Post by mtiburs »

sleid wrote:Après avoir démonté le pool2 Il faut mettre à "0"(voir post velivole18) l'ada8 autrement la sécurité de ZFS détectera un autre pool et refusera de s'en servir.
@lulu80
Pour démonter ton pool2, fais
zpool destroy pool2
de cette façon, ZFS libérera le disque proprement

sinon, oui, il faut tout faire en ligne de commande ... c'est le top ! :mrgreen:
Serveur Intel bi-Xéon P5530 / 8 X Ubuntu Serveur 18.04 LTS - ZFS-BTRFS-bcache / ~30 x PI2b(ARM) sous Nas4Free / et ...(chhhut)... 1 seul Xigmanas :o ... et pas à jour en plus :oops: (çà craint)
Conception d'un "système bizarre" :mrgreen: de "super-devices-autonomes" en NFS gérés par des micro-serveurs SAN(+nas) sous N4F (11 super-devs en raidz3) taille actuelle: 16To / prévue: 64To / théorique: 320To (consommation < 15W en veille - 24/24h) en service depuis 2 ans.

sleid
PowerUser
PowerUser
Posts: 774
Joined: 23 Jun 2012 07:36
Location: FRANCE LIMOUSIN CORREZE
Status: Offline

Re: Problème de disque

Post by sleid »

ou puis je vérifier cela ? zpool status
12.1.0.4 - Ingva (revision 7852)
FreeBSD 12.1-RELEASE-p12 #0 r368465M: Tue Dec 8 23:25:11 CET 2020
X64-embedded sur Intel(R) Atom(TM) CPU C2750 @ 2.40GHz Boot UEFI
ASRock C2750D4I 2 X 8GB DDR3 ECC
Pool of 2 vdev Raidz1: 3 WDC WD40EFRX + 3 WDC WD40EFRX

User avatar
lulu80
PowerUser
PowerUser
Posts: 763
Joined: 15 Jun 2014 12:15
Location: France-(Picardie 80)
Contact:
Status: Offline

Re: Problème de disque

Post by lulu80 »

Ok je fait cela demain si le n'as me laisse assez de liberté car les échanges deviennent une galère dû à sa latence
Version 11.2.0.4 - Omnius (revision 6400)
https://lucinfordi.fr

sleid
PowerUser
PowerUser
Posts: 774
Joined: 23 Jun 2012 07:36
Location: FRANCE LIMOUSIN CORREZE
Status: Offline

Re: Problème de disque

Post by sleid »

La première chose à faire c'est de mettre offline ada04
12.1.0.4 - Ingva (revision 7852)
FreeBSD 12.1-RELEASE-p12 #0 r368465M: Tue Dec 8 23:25:11 CET 2020
X64-embedded sur Intel(R) Atom(TM) CPU C2750 @ 2.40GHz Boot UEFI
ASRock C2750D4I 2 X 8GB DDR3 ECC
Pool of 2 vdev Raidz1: 3 WDC WD40EFRX + 3 WDC WD40EFRX

User avatar
lulu80
PowerUser
PowerUser
Posts: 763
Joined: 15 Jun 2014 12:15
Location: France-(Picardie 80)
Contact:
Status: Offline

Re: Problème de disque

Post by lulu80 »

bonjour ,
j'ai mis ada4 offline et récupéré sont nom dans le zpool status >> " 11425908422794113397 OFFLINE 0 0 0 was /dev/ada4 "

je vais démonter mon pool2 et procédé a sont remplacement ,mais avant je voudrait être sur que je pourrait après réception des WD neuf
refaire l'échange et récupéré mes 2 To ?
Version 11.2.0.4 - Omnius (revision 6400)
https://lucinfordi.fr

sleid
PowerUser
PowerUser
Posts: 774
Joined: 23 Jun 2012 07:36
Location: FRANCE LIMOUSIN CORREZE
Status: Offline

Re: Problème de disque

Post by sleid »

sans problèmes
12.1.0.4 - Ingva (revision 7852)
FreeBSD 12.1-RELEASE-p12 #0 r368465M: Tue Dec 8 23:25:11 CET 2020
X64-embedded sur Intel(R) Atom(TM) CPU C2750 @ 2.40GHz Boot UEFI
ASRock C2750D4I 2 X 8GB DDR3 ECC
Pool of 2 vdev Raidz1: 3 WDC WD40EFRX + 3 WDC WD40EFRX

User avatar
lulu80
PowerUser
PowerUser
Posts: 763
Joined: 15 Jun 2014 12:15
Location: France-(Picardie 80)
Contact:
Status: Offline

Re: Problème de disque

Post by lulu80 »

bon je vide le pool2 et mes en sécurité les données dessus (il yen a très peut) et en suite
je le démonte en suivant la procédure de mtiburs > "zpool destroy pool2"

pour le formatage lent quel commande faut il appliqué ?
Version 11.2.0.4 - Omnius (revision 6400)
https://lucinfordi.fr

User avatar
lulu80
PowerUser
PowerUser
Posts: 763
Joined: 15 Jun 2014 12:15
Location: France-(Picardie 80)
Contact:
Status: Offline

Re: Problème de disque

Post by lulu80 »

je vient de faire un zpool status pour voir si mon pool2 avait disparut et cela n'est pas bon

Code: Select all

nas4free: ~ # zpool status
  pool: pool1
 state: DEGRADED
status: One or more devices has been taken offline by the administrator.
        Sufficient replicas exist for the pool to continue functioning in a
        degraded state.
action: Online the device using 'zpool online' or replace the device with
        'zpool replace'.
  scan: resilvered 1.84M in 0h15m with 0 errors on Sat Jul 11 12:27:16 2015
config:

        NAME                      STATE     READ WRITE CKSUM
        pool1                     DEGRADED     0     0     0
          raidz1-0                DEGRADED     0     0     0
            ada1                  ONLINE       0     0     0
            ada2                  ONLINE       0     0     0
            ada3                  ONLINE       0     0     0
            11425908422794113397  OFFLINE      0     0     0  was /dev/ada4

errors: No known data errors
nas4free: ~ #
Version 11.2.0.4 - Omnius (revision 6400)
https://lucinfordi.fr

User avatar
mtiburs
Forum Moderator
Forum Moderator
Posts: 951
Joined: 09 Aug 2012 23:34
Location: France - Besançon
Status: Offline

Re: Problème de disque

Post by mtiburs »

lulu80 wrote:je vient de faire un zpool status pour voir si mon pool2 avait disparut et cela n'est pas bon

Code: Select all

nas4free: ~ # zpool status
  pool: pool1
 state: DEGRADED
status: One or more devices has been taken offline by the administrator.
        Sufficient replicas exist for the pool to continue functioning in a
        degraded state.
action: Online the device using 'zpool online' or replace the device with
        'zpool replace'.
  scan: resilvered 1.84M in 0h15m with 0 errors on Sat Jul 11 12:27:16 2015
config:

        NAME                      STATE     READ WRITE CKSUM
        pool1                     DEGRADED     0     0     0
          raidz1-0                DEGRADED     0     0     0
            ada1                  ONLINE       0     0     0
            ada2                  ONLINE       0     0     0
            ada3                  ONLINE       0     0     0
            11425908422794113397  OFFLINE      0     0     0  was /dev/ada4

errors: No known data errors
nas4free: ~ #
Oui enfin moi ce que j'en dis, c'est que tu veux tester le pool2 et tu nous fais lire le status du pool1 :shock: :roll: :cry: :?
Faut pas abuser des bonnes choses :lol:
Serveur Intel bi-Xéon P5530 / 8 X Ubuntu Serveur 18.04 LTS - ZFS-BTRFS-bcache / ~30 x PI2b(ARM) sous Nas4Free / et ...(chhhut)... 1 seul Xigmanas :o ... et pas à jour en plus :oops: (çà craint)
Conception d'un "système bizarre" :mrgreen: de "super-devices-autonomes" en NFS gérés par des micro-serveurs SAN(+nas) sous N4F (11 super-devs en raidz3) taille actuelle: 16To / prévue: 64To / théorique: 320To (consommation < 15W en veille - 24/24h) en service depuis 2 ans.

User avatar
mtiburs
Forum Moderator
Forum Moderator
Posts: 951
Joined: 09 Aug 2012 23:34
Location: France - Besançon
Status: Offline

Re: Problème de disque

Post by mtiburs »

En fait ta commande "zpool status" est générale, donc, comme le pool2 n'y apparait pas/plus, c'est qu'il n'existe plus (c'est ce qu'on voulait)

Tu peux tester un pool directement, en tapant: zpool status pool2
Serveur Intel bi-Xéon P5530 / 8 X Ubuntu Serveur 18.04 LTS - ZFS-BTRFS-bcache / ~30 x PI2b(ARM) sous Nas4Free / et ...(chhhut)... 1 seul Xigmanas :o ... et pas à jour en plus :oops: (çà craint)
Conception d'un "système bizarre" :mrgreen: de "super-devices-autonomes" en NFS gérés par des micro-serveurs SAN(+nas) sous N4F (11 super-devs en raidz3) taille actuelle: 16To / prévue: 64To / théorique: 320To (consommation < 15W en veille - 24/24h) en service depuis 2 ans.

sleid
PowerUser
PowerUser
Posts: 774
Joined: 23 Jun 2012 07:36
Location: FRANCE LIMOUSIN CORREZE
Status: Offline

Re: Problème de disque

Post by sleid »

lol
12.1.0.4 - Ingva (revision 7852)
FreeBSD 12.1-RELEASE-p12 #0 r368465M: Tue Dec 8 23:25:11 CET 2020
X64-embedded sur Intel(R) Atom(TM) CPU C2750 @ 2.40GHz Boot UEFI
ASRock C2750D4I 2 X 8GB DDR3 ECC
Pool of 2 vdev Raidz1: 3 WDC WD40EFRX + 3 WDC WD40EFRX

User avatar
lulu80
PowerUser
PowerUser
Posts: 763
Joined: 15 Jun 2014 12:15
Location: France-(Picardie 80)
Contact:
Status: Offline

Re: Problème de disque

Post by lulu80 »

Combien de disque peut ont remplacer en même temps sur un pool qui comporte 4 disques ?
Version 11.2.0.4 - Omnius (revision 6400)
https://lucinfordi.fr

sleid
PowerUser
PowerUser
Posts: 774
Joined: 23 Jun 2012 07:36
Location: FRANCE LIMOUSIN CORREZE
Status: Offline

Re: Problème de disque

Post by sleid »

1 par 1 par sécurité car pour l'instant il en reste 2 qui sont sains à l'instant t mais pendant la reconstruction ils sont sollicités donc prudence.
12.1.0.4 - Ingva (revision 7852)
FreeBSD 12.1-RELEASE-p12 #0 r368465M: Tue Dec 8 23:25:11 CET 2020
X64-embedded sur Intel(R) Atom(TM) CPU C2750 @ 2.40GHz Boot UEFI
ASRock C2750D4I 2 X 8GB DDR3 ECC
Pool of 2 vdev Raidz1: 3 WDC WD40EFRX + 3 WDC WD40EFRX

User avatar
lulu80
PowerUser
PowerUser
Posts: 763
Joined: 15 Jun 2014 12:15
Location: France-(Picardie 80)
Contact:
Status: Offline

Re: Problème de disque

Post by lulu80 »

ok merci
Version 11.2.0.4 - Omnius (revision 6400)
https://lucinfordi.fr

Post Reply

Return to “Français”