• 04-11-2014, 23:55:42
    #1
    Merhaba,

    Son bir haftadır sunucuma şu şekilde 2 mail geliyor. Bu iki mailde aynı anda geliyor, yeni farkettim. Hizmet aldığım ovh.com a yazdım ama belki buradan cevap daha hızlı gelir.. Mail aynen aşağıdaki gibi
    ---------------------------------------------
    This is an automatically generated mail message from mdadm
    running on "server adı"

    A DegradedArray event had been detected on md device /dev/md2.

    Faithfully yours, etc.

    P.S. The /proc/mdstat file currently contains the following:

    Personalities : [raid1] [raid10]
    md2 : active raid1 sdd2[3] sdf2[5] sdb2[1] sda2[0] sde2[4]
    204798912 blocks [6/5] [UU_UUU]

    md4 : active raid10 sdf4[5] sdb4[1] sdd4[3] sda4[0] sde4[4]
    11103103488 blocks super 1.2 512K chunks 2 near-copies [6/5] [UU_UUU]

    unused devices: <none>
    -------------------------------
    This is an automatically generated mail message from mdadm
    running on "sunucu adı"

    A DegradedArray event had been detected on md device /dev/md/4.

    Faithfully yours, etc.

    P.S. The /proc/mdstat file currently contains the following:

    Personalities : [raid1] [raid10]
    md2 : active raid1 sdd2[3] sdf2[5] sdb2[1] sda2[0] sde2[4]
    204798912 blocks [6/5] [UU_UUU]

    md4 : active raid10 sdf4[5] sdb4[1] sdd4[3] sda4[0] sde4[4]
    11103103488 blocks super 1.2 512K chunks 2 near-copies [6/5] [UU_UUU]

    unused devices: <none>

    ---------------------------------------

    Nedir Çözümü nasıldır? Sunucu üzerindeki siteler şimdilik düzgün çalışıyor gibi gözüküyor...

    Teşekkürler
  • 05-11-2014, 00:07:50
    #2
    Üyeliği durduruldu
    RAID ile alakalı bir sorun var gibi yinede bilgili arkadaşlar gelip bir baksın. @Elazığlı168 bilgilidir.
  • 05-11-2014, 00:47:08
    #3
    RAID yapısı donanımsal mı yazılımsal mı?

    Disklerinizden birisi arızalanmış gibi gözüküyor.
  • 05-11-2014, 01:42:21
    #4
    iptables adlı üyeden alıntı: mesajı görüntüle
    RAID yapısı donanımsal mı yazılımsal mı?

    Disklerinizden birisi arızalanmış gibi gözüküyor.
    yazılımsal hocam.

    mdadm --detail /dev/md2

    sonucunda şöyle bir şey döküyor;

    /dev/md2:
            Version : 0.90
      Creation Time : Sat Nov 30 03:48:04 2013
         Raid Level : raid1
         Array Size : 204798912 (195.31 GiB 209.71 GB)
      Used Dev Size : 204798912 (195.31 GiB 209.71 GB)
       Raid Devices : 6
      Total Devices : 5
    Preferred Minor : 2
        Persistence : Superblock is persistent
    
        Update Time : Wed Nov  5 01:41:40 2014
              State : clean, degraded
     Active Devices : 5
    Working Devices : 5
     Failed Devices : 0
      Spare Devices : 0
    
               UUID : f9f61139:c87569ee:a4a1adc2:26fd5442
             Events : 0.1860598
    
        Number   Major   Minor   RaidDevice State
           0       8        2        0      active sync   /dev/sda2
           1       8       18        1      active sync   /dev/sdb2
           2       0        0        2      removed
           3       8       50        3      active sync   /dev/sdd2
           4       8       66        4      active sync   /dev/sde2
           5       8       82        5      active sync   /dev/sdf2
  • 05-11-2014, 02:18:04
    #5
    Hatada bozuk bir dizk görünmüyor. Total kullanım alanın azalmış olabilir mi acaba? Bu hatada sadece rapor sunduğunu görüyorum. Belki boyut azaldığı için uyarıyor olabilir. Onun dışında yazılanlara göre tüm diskler faal durumda.
  • 05-11-2014, 07:29:51
    #6
    Kimlik doğrulama veya yönetimden onay bekliyor.
    6 disk Raid 10 yapınız mevcut sanırım. /dev/sdc Array üzerinde gözükmüyor. Kuvvetle muhtemel /dev/sdc diskiniz arızalı ve işletim sisteminde dahi gözükmüyor.

    Her şeyden önce 'smartctl -a /dev/sdc' komutunu uygulamanızı ve /dev/sdc'nin akıbetini görmenizi öneririm.

    Disk değiştirildikten sonra partition tablosunu başka bir diskten yeni /dev/sdc'ye kopyalabilir akabinde bu partitionları /dev/mdX altına ekleyebilirsiniz.
  • 05-11-2014, 12:56:24
    #7
    Tüm arkadaşlara tek tek ilgilendikleri için teşekkür ederim.

    conquer adlı üyeden alıntı: mesajı görüntüle
    Hatada bozuk bir dizk görünmüyor. Total kullanım alanın azalmış olabilir mi acaba? Bu hatada sadece rapor sunduğunu görüyorum. Belki boyut azaldığı için uyarıyor olabilir. Onun dışında yazılanlara göre tüm diskler faal durumda.
    Total kullanım alanı daha 8 TB civarında var hocam. Alanla ilgili bir sıkıntı yok şimdilik.

    Bilrom adlı üyeden alıntı: mesajı görüntüle
    6 disk Raid 10 yapınız mevcut sanırım. /dev/sdc Array üzerinde gözükmüyor. Kuvvetle muhtemel /dev/sdc diskiniz arızalı ve işletim sisteminde dahi gözükmüyor.

    Her şeyden önce 'smartctl -a /dev/sdc' komutunu uygulamanızı ve /dev/sdc'nin akıbetini görmenizi öneririm.

    Disk değiştirildikten sonra partition tablosunu başka bir diskten yeni /dev/sdc'ye kopyalabilir akabinde bu partitionları /dev/mdX altına ekleyebilirsiniz.
    [root@ns3378249 ~]# smartctl -a /dev/sdc
    smartctl 5.43 2012-06-30 r3573 [x86_64-linux-2.6.32-358.23.2.el6.x86_64] (local build)
    Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
    
    === START OF INFORMATION SECTION ===
    Device Model:     Hitachi HUS724040ALE640
    Serial Number:    PK1331PAG3XJSS
    LU WWN Device Id: 5 000cca 22bc1c840
    Firmware Version: MJAOA3B0
    User Capacity:    4,000,787,030,016 bytes [4.00 TB]
    Sector Sizes:     512 bytes logical, 4096 bytes physical
    Device is:        Not in smartctl database [for details use: -P showall]
    ATA Version is:   8
    ATA Standard is:  ATA-8-ACS revision 4
    Local Time is:    Wed Nov  5 12:53:32 2014 EET
    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: FAILED!
    Drive failure expected in less than 24 hours. SAVE ALL DATA.
    See vendor-specific Attribute list for failed Attributes.
    
    General SMART Values:
    Offline data collection status:  (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:                (   24) 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:        ( 569) minutes.
    SCT capabilities:              (0x003d) SCT Status supported.
                                            SCT Error Recovery Control supported.
                                            SCT Feature Control supported.
                                            SCT Data Table supported.
    
    SMART Attributes Data Structure revision number: 16
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
      1 Raw_Read_Error_Rate     0x000b   059   059   016    Pre-fail  Always       -       10788
      2 Throughput_Performance  0x0005   138   138   054    Pre-fail  Offline      -       76
      3 Spin_Up_Time            0x0007   134   134   024    Pre-fail  Always       -       560 (Average 591)
      4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       45
      5 Reallocated_Sector_Ct   0x0033   001   001   005    Pre-fail  Always   FAILING_NOW 1995
      7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
      8 Seek_Time_Performance   0x0005   112   112   020    Pre-fail  Offline      -       38
      9 Power_On_Hours          0x0012   099   099   000    Old_age   Always       -       11932
     10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
     12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       45
    192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       359
    193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       359
    194 Temperature_Celsius     0x0002   162   162   000    Old_age   Always       -       37 (Min/Max 22/52)
    196 Reallocated_Event_Count 0x0032   001   001   000    Old_age   Always       -       3819
    197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
    198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
    199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0
    
    SMART Error Log Version: 1
    ATA Error Count: 1699 (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 1699 occurred at disk power-on lifetime: 9859 hours (410 days + 19 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 08 00 9a 44 0d  Error: UNC 8 sectors at LBA = 0x0d449a00 = 222599680
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      c8 00 08 00 9a 44 ed 00      19:28:45.364  READ DMA
      ef 10 02 00 00 00 a0 00      19:28:45.363  SET FEATURES [Reserved for Serial ATA]
      27 00 00 00 00 00 e0 00      19:28:45.363  READ NATIVE MAX ADDRESS EXT
      ec 00 00 00 00 00 a0 00      19:28:45.360  IDENTIFY DEVICE
      ef 03 42 00 00 00 a0 00      19:28:45.360  SET FEATURES [Set transfer mode]
    
    Error 1698 occurred at disk power-on lifetime: 9859 hours (410 days + 19 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 08 00 9a 44 0d  Error: UNC 8 sectors at LBA = 0x0d449a00 = 222599680
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      c8 00 08 00 9a 44 ed 00      19:28:42.634  READ DMA
      ef 10 02 00 00 00 a0 00      19:28:42.633  SET FEATURES [Reserved for Serial ATA]
      27 00 00 00 00 00 e0 00      19:28:42.632  READ NATIVE MAX ADDRESS EXT
      ec 00 00 00 00 00 a0 00      19:28:42.629  IDENTIFY DEVICE
      ef 03 42 00 00 00 a0 00      19:28:42.629  SET FEATURES [Set transfer mode]
    
    Error 1697 occurred at disk power-on lifetime: 9859 hours (410 days + 19 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 08 00 9a 44 0d  Error: UNC 8 sectors at LBA = 0x0d449a00 = 222599680
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      c8 00 08 00 9a 44 ed 00      19:28:39.729  READ DMA
      ef 10 02 00 00 00 a0 00      19:28:39.728  SET FEATURES [Reserved for Serial ATA]
      27 00 00 00 00 00 e0 00      19:28:39.727  READ NATIVE MAX ADDRESS EXT
      ec 00 00 00 00 00 a0 00      19:28:39.724  IDENTIFY DEVICE
      ef 03 42 00 00 00 a0 00      19:28:39.724  SET FEATURES [Set transfer mode]
    
    Error 1696 occurred at disk power-on lifetime: 9859 hours (410 days + 19 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 08 00 9a 44 0d  Error: UNC 8 sectors at LBA = 0x0d449a00 = 222599680
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      c8 00 08 00 9a 44 ed 00      19:28:36.899  READ DMA
      ef 10 02 00 00 00 a0 00      19:28:36.897  SET FEATURES [Reserved for Serial ATA]
      27 00 00 00 00 00 e0 00      19:28:36.897  READ NATIVE MAX ADDRESS EXT
      ec 00 00 00 00 00 a0 00      19:28:36.894  IDENTIFY DEVICE
      ef 03 42 00 00 00 a0 00      19:28:36.894  SET FEATURES [Set transfer mode]
    
    Error 1695 occurred at disk power-on lifetime: 9859 hours (410 days + 19 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 08 00 9a 44 0d  Error: UNC 8 sectors at LBA = 0x0d449a00 = 222599680
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      c8 00 08 00 9a 44 ed 00      19:28:34.102  READ DMA
      ef 10 02 00 00 00 a0 00      19:28:34.100  SET FEATURES [Reserved for Serial ATA]
      27 00 00 00 00 00 e0 00      19:28:34.100  READ NATIVE MAX ADDRESS EXT
      ec 00 00 00 00 00 a0 00      19:28:34.097  IDENTIFY DEVICE
      ef 03 42 00 00 00 a0 00      19:28:34.097  SET FEATURES [Set transfer mode]
    
    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%      3760         -
    # 2  Short offline       Completed without error       00%      3759         -
    # 3  Short offline       Completed without error       00%      3759         -
    # 4  Short offline       Completed without error       00%      3759         -
    # 5  Short offline       Completed without error       00%      3757         -
    # 6  Short offline       Completed without error       00%      3757         -
    # 7  Short offline       Completed without error       00%      3682         -
    # 8  Short offline       Completed without error       00%      3682         -
    # 9  Short offline       Completed without error       00%      3661         -
    #10  Short offline       Completed without error       00%      3659         -
    #11  Short offline       Completed without error       00%      3659         -
    #12  Short offline       Completed without error       00%      3615         -
    #13  Short offline       Completed without error       00%      3520         -
    #14  Short offline       Completed without error       00%      3423         -
    #15  Short offline       Completed without error       00%      3327         -
    #16  Short offline       Completed without error       00%      3039         -
    #17  Short offline       Completed without error       00%      2943         -
    #18  Short offline       Completed without error       00%      2847         -
    #19  Short offline       Completed without error       00%      2752         -
    #20  Short offline       Completed without error       00%      2655         -
    #21  Short offline       Completed without error       00%      2559         -
    
    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.
    dediğiniz sorguyu yapınca bu cevabı alıyorum hocam. OVH çalışanlarına yazdım. Bakalım ne diyecekler...

    Ayrıca bu işten çok kıllandım gittim bir tane daha sunucu kiraladım. Ne olur ne olmaz, en azından ona yedekleme filan yaparım...

    Teşekkürler ilginize
  • 05-11-2014, 16:02:45
    #8
    dev/sdc Henuz olmemis ama olmek uzere.
    mdadm --detail /dev/md4 ciktiniza bakabilir miyim? Oda Raid10 ise endisenlmenize gerek yok. Ama OVH sdc diskini degistirmesi lazim. Eskiden bize sormadan dahi kendileri direk degisitiriyorlarda bu tarz diskleri. Siz ticket acip
    mdadm --detail /dev/md2
    mdadm --detail /dev/md4
    smartctl -a /dev/sdc
    Cikitilarinida ekleyin. sdc degisimini talep edin.
  • 05-11-2014, 17:08:41
    #9
    Ufkabakan adlı üyeden alıntı: mesajı görüntüle
    dev/sdc Henuz olmemis ama olmek uzere.
    mdadm --detail /dev/md4 ciktiniza bakabilir miyim? Oda Raid10 ise endisenlmenize gerek yok. Ama OVH sdc diskini degistirmesi lazim. Eskiden bize sormadan dahi kendileri direk degisitiriyorlarda bu tarz diskleri. Siz ticket acip
    mdadm --detail /dev/md2
    mdadm --detail /dev/md4
    smartctl -a /dev/sdc
    Cikitilarinida ekleyin. sdc degisimini talep edin.
    Merhaba hocam. Benim tek endişem veri kaybetmek. Sonucunda sektörümü biliyorsunuz. Disk değişmiş, değişmemiş çok da mühim değil. Sırf bu yüzden bir sunucu daha kiraladım bugün

    diğer çıktıyıda gönderiyorum size

    [root@ns3378249 ~]# mdadm --detail /dev/md4
    /dev/md4:
            Version : 1.2
      Creation Time : Sat Nov 30 03:48:20 2013
         Raid Level : raid10
         Array Size : 11103103488 (10588.74 GiB 11369.58 GB)
      Used Dev Size : 3701034496 (3529.58 GiB 3789.86 GB)
       Raid Devices : 6
      Total Devices : 5
        Persistence : Superblock is persistent
    
        Update Time : Wed Nov  5 17:08:13 2014
              State : clean, degraded
     Active Devices : 5
    Working Devices : 5
     Failed Devices : 0
      Spare Devices : 0
    
             Layout : near=2
         Chunk Size : 512K
    
               Name : rescue.ovh.net:4
               UUID : b4ee116e:5731cba7:e336b4f9:bbcb4be5
             Events : 25512218
    
        Number   Major   Minor   RaidDevice State
           0       8        4        0      active sync   /dev/sda4
           1       8       20        1      active sync   /dev/sdb4
           2       0        0        2      removed
           3       8       52        3      active sync   /dev/sdd4
           4       8       68        4      active sync   /dev/sde4
           5       8       84        5      active sync   /dev/sdf4