Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 32

Thread: MD raid trouble.

  1. #11
    Join Date
    Mar 2009
    Beans
    19

    Re: MD raid trouble.

    Same error messages, first it complains about decice or resource busy, for two fo the disks, and then i get a message about 2 acitve and one spare device.

    I assume the my options are starting to become limited?

  2. #12
    Join Date
    Jul 2010
    Location
    Michigan, USA
    Beans
    2,134
    Distro
    Ubuntu 16.04 Xenial Xerus

    Re: MD raid trouble.

    Did you make sure that mdadm didn't have a partially assembled array by stopping it first? About the only option you'll have is to try to re-run mdadm create with the assume clean with the same values as you had before. The beginning portion of this will give you an idea.

    First, have you tried swapping the SATA cables on those drives or putting them on different SATA heads on your motherboard to try to rule out hardware. Also, can you please paste the whole output of smartctl on both of those drives. Passing a smart test without running at least short test on them first doesn't mean they're working as they should.

    Here's how to run a long SMART test.
    Code:
    smartctl -s on -t long /dev/sdd
    smartctl -s on -t long /dev/sde
    This might take a few hours to finish, but you can check the drive's test status like this. If the status of a disk reports not completed because of read errors, those disks need to be replaced.
    Code:
    smartctl -l selftest /dev/sdd
    smartctl -l selftest /dev/sde
    Finally, I'd like to see the whole SMART output for each of the drives.
    Code:
    smartctl -d ata -a /dev/sdd
    smartctl -d ata -a /dev/sde
    I'd be very interested to see some of the values like reallocated sectors and UDMA error count.
    Last edited by rubylaser; April 4th, 2012 at 01:04 AM.

  3. #13
    Join Date
    Mar 2009
    Beans
    19

    Re: MD raid trouble.

    I haven't swapped the cables yet. Will look into that this evening.
    I was looking at your website and came across the article of multiple disk failure and the command:
    Code:
    mdadm --create --assume-clean /dev/md0 /dev/sd[abcdefg]1
    Is there any point in trying this ? Or will it just overwrite any data the might have been there? And i assume that i will have to get the order right in the command above?

    Smartctl test:
    Code:
    smartctl -d ata -a /dev/sdd
    smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.0.0-16-server] (local build)
    Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
    
    === START OF INFORMATION SECTION ===
    Model Family:     Seagate Barracuda Green (Adv. Format)
    Device Model:     ST2000DL003-9VT166
    Serial Number:    5YD1W8E8
    LU WWN Device Id: 5 000c50 02fbeebc9
    Firmware Version: CC32
    User Capacity:    2,000,398,934,016 bytes [2.00 TB]
    Sector Size:      512 bytes logical/physical
    Device is:        In smartctl database [for details use: -P show]
    ATA Version is:   8
    ATA Standard is:  ATA-8-ACS revision 4
    Local Time is:    Wed Apr  4 17:18:16 2012 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:                (  623) 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:        (   1) minutes.
    Extended self-test routine
    recommended polling time:        ( 255) minutes.
    Conveyance self-test routine
    recommended polling time:        (   2) minutes.
    SCT capabilities:              (0x30b7) SCT Status supported.
                                            SCT Feature Control supported.
                                            SCT Data Table 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   119   099   006    Pre-fail  Always       -       229912144
      3 Spin_Up_Time            0x0003   093   092   000    Pre-fail  Always       -       0
      4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       26
      5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
      7 Seek_Error_Rate         0x000f   084   060   030    Pre-fail  Always       -       262889320
      9 Power_On_Hours          0x0032   093   093   000    Old_age   Always       -       6332
     10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
     12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       27
    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   100   100   000    Old_age   Always       -       0
    188 Command_Timeout         0x0032   100   098   000    Old_age   Always       -       6
    189 High_Fly_Writes         0x003a   094   094   000    Old_age   Always       -       6
    190 Airflow_Temperature_Cel 0x0022   067   060   045    Old_age   Always       -       33 (Min/Max 31/38)
    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       -       18
    193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       26
    194 Temperature_Celsius     0x0022   033   040   000    Old_age   Always       -       33 (0 21 0 0)
    195 Hardware_ECC_Recovered  0x001a   024   009   000    Old_age   Always       -       229912144
    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
    240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       278489974446231
    241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       310312786
    242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       2466526807
    
    SMART Error Log Version: 1
    No Errors Logged
    
    SMART Self-test log structure revision number 1
    Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
    # 1  Extended offline    Completed without error       00%      6331         -
    
    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.
    
    root@Asgard:/home/renec/R-Studio# smartctl -d ata -a /dev/sde
    smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.0.0-16-server] (local build)
    Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
    
    === START OF INFORMATION SECTION ===
    Model Family:     Seagate Barracuda Green (Adv. Format)
    Device Model:     ST2000DL003-9VT166
    Serial Number:    6YD1JP7R
    LU WWN Device Id: 5 000c50 046199c58
    Firmware Version: CC3C
    User Capacity:    2,000,398,934,016 bytes [2.00 TB]
    Sector Sizes:     512 bytes logical, 4096 bytes physical
    Device is:        In smartctl database [for details use: -P show]
    ATA Version is:   8
    ATA Standard is:  ATA-8-ACS revision 4
    Local Time is:    Wed Apr  4 17:18:18 2012 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:                (  602) 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:        (   1) minutes.
    Extended self-test routine
    recommended polling time:        ( 255) minutes.
    Conveyance self-test routine
    recommended polling time:        (   2) minutes.
    SCT capabilities:              (0x30b7) SCT Status supported.
                                            SCT Feature Control supported.
                                            SCT Data Table 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   120   099   006    Pre-fail  Always       -       243225248
      3 Spin_Up_Time            0x0003   093   093   000    Pre-fail  Always       -       0
      4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       9
      5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
      7 Seek_Error_Rate         0x000f   078   060   030    Pre-fail  Always       -       61510937
      9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       946
     10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
     12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       9
    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   100   100   000    Old_age   Always       -       0
    188 Command_Timeout         0x0032   100   097   000    Old_age   Always       -       3
    189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
    190 Airflow_Temperature_Cel 0x0022   066   062   045    Old_age   Always       -       34 (Min/Max 32/38)
    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       -       8
    193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       9
    194 Temperature_Celsius     0x0022   034   040   000    Old_age   Always       -       34 (0 22 0 0)
    195 Hardware_ECC_Recovered  0x001a   024   013   000    Old_age   Always       -       243225248
    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
    240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       198131136332722
    241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       3081786388
    242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       3311031373
    
    SMART Error Log Version: 1
    No Errors Logged
    
    SMART Self-test log structure revision number 1
    Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
    # 1  Extended offline    Completed without error       00%       944         -
    
    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.

  4. #14
    Join Date
    Jul 2010
    Location
    Michigan, USA
    Beans
    2,134
    Distro
    Ubuntu 16.04 Xenial Xerus

    Re: MD raid trouble.

    Both of those disks are very healthly looking. If you look at that link that I sent the post before, it basically details recreating the mdadm array with the assume clean option. For it to work, you have to use the same creation options that you used to create the array and your disks need to be in the same order. It won't overwrite your data if you use assume clean, because it won't cause a resync. You'll only be recreating the superblock info.

  5. #15
    Join Date
    Mar 2009
    Beans
    19

    Re: MD raid trouble.

    Right this looks like it is getting some where.
    I am able to start mdadm with 4 of the 5 disks, when the 5th disk is added there are problems, i am running smartctl on it right now.

    It seems that this disk had problems ealier:
    Code:
    [1468403.073910] sd 5:0:0:0: [sdc]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
    Not sure what the error message means, but it will be interesting to see what happens with smartctl tool.

    btrfs won't mount yet, but i am able to get hold of some files using a recovery tool.

    rubylaser thanks a lot for all your advice. It is very much appreciated.

    I will post an update when i am done/give up.

  6. #16
    Join Date
    Jul 2010
    Location
    Michigan, USA
    Beans
    2,134
    Distro
    Ubuntu 16.04 Xenial Xerus

    Re: MD raid trouble.

    So, your array is assembled and working now, in a degraded state? That's great! Did you recreate the array with the assume clean option?
    What's the output of
    Code:
    cat /proc/mdstat
    This thread seems to cover the same error. Do you have any USB devices that you could unhook to see if it's an IRQ problem? Also, did you try a different SATA cable?
    Last edited by rubylaser; April 5th, 2012 at 01:26 AM.

  7. #17
    Join Date
    Mar 2009
    Beans
    19

    Re: MD raid trouble.

    My goal is now to copy as much off the disk to an external disk. When the data is safe i will try to see if i can get some life into sdd. (I have many usb disks which i could unplug)

    And then i will try again... Starting with zeroing out the first part of each drive to get rid of zfs and mdadm.

    Self test on disk /dev/sdd completed without errors.

    For others who might run into similar problems with btrfs, i was unable to use the btrfsck check succesfully and am now using btrfs-restore. This utility is able to use the file structure (unlike restore programs which only fine files without names) and copy the files to another drive.

    Code:
     cat /proc/mdstat
    Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] 
    md0 : active raid6 sdc[4] sda[2] sde[1] sdf[0]
          5860538880 blocks super 1.2 level 6, 512k chunk, algorithm 2 [5/4] [UUU_U]
          
    md127 : inactive sdd[3](S)
          1953513560 blocks super 1.2
           
    unused devices: <none>

    I noticed that the labels of the disks are moving around sda and sdb are swapping names every now and then but i assume mdadm is smart enough to firgure this out when the pc boots.

  8. #18
    Join Date
    Jul 2010
    Location
    Michigan, USA
    Beans
    2,134
    Distro
    Ubuntu 16.04 Xenial Xerus

    Re: MD raid trouble.

    Quote Originally Posted by rcastberg View Post
    I noticed that the labels of the disks are moving around sda and sdb are swapping names every now and then but i assume mdadm is smart enough to firgure this out when the pc boots.
    Yes it is, mdadm assembles the array based on the UUIDs in the superblock on each disk. So, the disk order really doesn't matter. Glad to hear you where able to recover your data.

  9. #19
    Join Date
    Nov 2009
    Location
    Mataro, Spain
    Beans
    13,988
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: MD raid trouble.

    But wouldn't a disk name moving around point to a faulty cable or connection? If you are not touching anything, they would only move if the order of discovery of disks is different, in other words if one is disconnected.

    Could this be in the wider picture of your problems?

    Yes, mdadm can work with the UUID but you can't ignore if one of the disks has good or bad connection.
    Darko.
    -----------------------------------------------------------------------
    Ubuntu 14.04 LTS 64bit & Windows 10 Pro 64bit

  10. #20
    Join Date
    Jul 2010
    Location
    Michigan, USA
    Beans
    2,134
    Distro
    Ubuntu 16.04 Xenial Xerus

    Re: MD raid trouble.

    It could, but the SMART data would show a bad SATA cable by looking at this line
    Code:
    199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
    Since the count is at zero, it's very unlikely that it's that.

Page 2 of 4 FirstFirst 1234 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •