Restoring a raid0 for data rescue

Linux RAID subsystem development
 help / color / mirror / Atom feed

* Restoring a raid0 for data rescue
       [not found] <S1726630AbgHBR6v/20200802175851Z+2001@vger.kernel.org>
@ 2020-08-02 18:09 ` tyranastrasz
  2020-08-02 19:01   ` antlists
  0 siblings, 1 reply; 9+ messages in thread
From: tyranastrasz @ 2020-08-02 18:09 UTC (permalink / raw)
  To: linux-raid

[-- Attachment #1: Type: text/plain, Size: 1568 bytes --]

Hello

I've a problem with my raid0.
The probelmatic disks (2x 1TB wdred) were in usage in my server, now
they got replaced with 3x 4TB seagate in a raid5.

Before I turned them off, I made a backup on an external drive (normal
hdd via USB) via rsync -avx /source /mnt/external/

Whatever happens in the night, the backup isn't complete and I miss files.
So I put the old raid again into the server and wanted to start, but the
Intel Raid Controller said that one of the disks are no member of a raid.

My server mainboard is from Gigabyte a MX11-PC0.

Well I made some mdadm examines, smartctl, mdstat, lsdrv logfiles and
attached them to the mail.

At the moment I have both raid0 disks, the backup disk and my normal ssd
in my workstation.
My workstation has this OS:
nara@Nibler:~$ cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.4 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.4 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

nara@Nibler:~$ uname -a
Linux Nibler 4.15.0-96-lowlatency #97-Ubuntu SMP PREEMPT Wed Apr 1
04:10:58 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

I would be very glad when someone can help me with this issue.
All I want is to localy mount the raid0 for getting my files and do a
new fresh rsync via SATA and not USB.

Thank you
Nara


[-- Attachment #2: lsdrv --]
[-- Type: text/plain, Size: 1383 bytes --]

root@Nibler:~/lsdrv# python2.7 lsdrv
**Warning** The following utility(ies) failed to execute:
  pvs
  lvs
Some information may be missing.

PCI [ahci] 00:1f.2 SATA controller: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode]
├scsi 0:0:0:0 ATA      Samsung SSD 850  {S2RFNXAH116475T}
│└sda 931.51g [8:0] Partitioned (gpt)
│ ├sda1 512.00m [8:1] vfat {971F-1967}
│ │└Mounted as /dev/sda1 @ /boot/efi
│ └sda2 465.26g [8:2] ext4 {e88b3bf8-b65e-4281-9b2f-497c0794c4e7}
│  └Mounted as /dev/sda2 @ /
├scsi 1:0:0:0 HL-DT-ST BDDVDRW CH10LS28 {K82C5365753}
│└sr0 1.00g [11:0] Empty/Unknown
├scsi 2:0:0:0 ATA      WDC WD10JFCX-68N {WD-WXS1A57H1LVF}
│└sdb 931.51g [8:16] Partitioned (dos)
│ ├sdb1 3.00m [8:17] Empty/Unknown
│ └sdb2 931.51g [8:18] Empty/Unknown
├scsi 3:0:0:0 ATA      WDC WD20EFRX-68A {WD-WMC1T3006015}
│└sdc 1.82t [8:32] Partitioned (dos)
│ └sdc1 1.82t [8:33] ext4 {1908a16a-0a8c-4f1b-abe5-5060ac051afb}
└scsi 4:0:0:0 ATA      WDC WD10JFCX-68N {WD-WX71EB6D6JL5}
 └sdd 931.51g [8:48] isw_raid_member
Other Block Devices
├loop0 0.00k [7:0] Empty/Unknown
├loop1 0.00k [7:1] Empty/Unknown
├loop2 0.00k [7:2] Empty/Unknown
├loop3 0.00k [7:3] Empty/Unknown
├loop4 0.00k [7:4] Empty/Unknown
├loop5 0.00k [7:5] Empty/Unknown
├loop6 0.00k [7:6] Empty/Unknown
└loop7 0.00k [7:7] Empty/Unknown

[-- Attachment #3: mdstat --]
[-- Type: text/plain, Size: 72 bytes --]

root@Nibler:~# cat /proc/mdstat
Personalities : 
unused devices: <none>

[-- Attachment #4: smartctl_xall_sdd --]
[-- Type: text/plain, Size: 14845 bytes --]

root@Nibler:~# smartctl --xall /dev/sdd
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-96-lowlatency] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red
Device Model:     WDC WD10JFCX-68N6GN0
Serial Number:    WD-WX71EB6D6JL5
LU WWN Device Id: 5 0014ee 65d0ea068
Firmware Version: 82.00A82
User Capacity:    1'000'204'886'016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Aug  2 18:08:37 2020 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM level is:     254 (maximum performance)
Rd look-ahead is: Enabled
Write cache is:   Enabled
ATA Security is:  Disabled, frozen [SEC2]
Wt Cache Reorder: 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: 		(18720) 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: 	 ( 209) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x703d)	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          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   200   200   051    -    0
  3 Spin_Up_Time            POS--K   180   178   021    -    1958
  4 Start_Stop_Count        -O--CK   100   100   000    -    27
  5 Reallocated_Sector_Ct   PO--CK   200   200   140    -    0
  7 Seek_Error_Rate         -OSR-K   100   253   000    -    0
  9 Power_On_Hours          -O--CK   072   072   000    -    20562
 10 Spin_Retry_Count        -O--CK   100   253   000    -    0
 11 Calibration_Retry_Count -O--CK   100   253   000    -    0
 12 Power_Cycle_Count       -O--CK   100   100   000    -    26
192 Power-Off_Retract_Count -O--CK   200   200   000    -    9
193 Load_Cycle_Count        -O--CK   189   189   000    -    35431
194 Temperature_Celsius     -O---K   113   093   000    -    34
196 Reallocated_Event_Count -O--CK   200   200   000    -    0
197 Current_Pending_Sector  -O--CK   200   200   000    -    0
198 Offline_Uncorrectable   ----CK   100   253   000    -    0
199 UDMA_CRC_Error_Count    -O--CK   200   200   000    -    0
200 Multi_Zone_Error_Rate   ---R--   100   253   000    -    0
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O      5  Comprehensive SMART error log
0x03       GPL     R/O      6  Ext. Comprehensive SMART error log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O      1  Extended self-test log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  SATA NCQ Queued Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x21       GPL     R/O      1  Write stream error log
0x22       GPL     R/O      1  Read stream error log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xa0-0xa7  GPL,SL  VS      16  Device vendor specific log
0xa8-0xb6  GPL,SL  VS       1  Device vendor specific log
0xb7       GPL,SL  VS      38  Device vendor specific log
0xbd       GPL,SL  VS       1  Device vendor specific log
0xc0       GPL,SL  VS       1  Device vendor specific log
0xc1       GPL     VS      93  Device vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
No Errors Logged

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     16883         -

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.

SCT Status Version:                  3
SCT Version (vendor specific):       258 (0x0102)
SCT Support Level:                   1
Device State:                        Active (0)
Current Temperature:                    34 Celsius
Power Cycle Min/Max Temperature:     25/34 Celsius
Lifetime    Min/Max Temperature:     20/54 Celsius
Under/Over Temperature Limit Count:   0/0
Vendor specific:
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        1 minute
Min/Max recommended Temperature:      0/60 Celsius
Min/Max Temperature Limit:           -41/85 Celsius
Temperature History Size (Index):    478 (398)

Index    Estimated Time   Temperature Celsius
 399    2020-08-02 10:11    41  **********************
 ...    ..( 63 skipped).    ..  **********************
 463    2020-08-02 11:15    41  **********************
 464    2020-08-02 11:16     ?  -
 465    2020-08-02 11:17    27  ********
 466    2020-08-02 11:18    27  ********
 467    2020-08-02 11:19    27  ********
 468    2020-08-02 11:20    28  *********
 469    2020-08-02 11:21    28  *********
 470    2020-08-02 11:22    29  **********
 471    2020-08-02 11:23    30  ***********
 ...    ..(  2 skipped).    ..  ***********
 474    2020-08-02 11:26    30  ***********
 475    2020-08-02 11:27    31  ************
 476    2020-08-02 11:28    31  ************
 477    2020-08-02 11:29    31  ************
   0    2020-08-02 11:30     ?  -
   1    2020-08-02 11:31    31  ************
   2    2020-08-02 11:32    31  ************
   3    2020-08-02 11:33    31  ************
   4    2020-08-02 11:34    32  *************
   5    2020-08-02 11:35    32  *************
   6    2020-08-02 11:36    32  *************
   7    2020-08-02 11:37    33  **************
   8    2020-08-02 11:38    33  **************
   9    2020-08-02 11:39    34  ***************
  10    2020-08-02 11:40    34  ***************
  11    2020-08-02 11:41    34  ***************
  12    2020-08-02 11:42     ?  -
  13    2020-08-02 11:43    27  ********
 ...    ..(  2 skipped).    ..  ********
  16    2020-08-02 11:46    27  ********
  17    2020-08-02 11:47    28  *********
  18    2020-08-02 11:48     ?  -
  19    2020-08-02 11:49    28  *********
  20    2020-08-02 11:50    28  *********
  21    2020-08-02 11:51    28  *********
  22    2020-08-02 11:52    29  **********
  23    2020-08-02 11:53    29  **********
  24    2020-08-02 11:54     ?  -
  25    2020-08-02 11:55    25  ******
  26    2020-08-02 11:56    25  ******
  27    2020-08-02 11:57    26  *******
  28    2020-08-02 11:58    26  *******
  29    2020-08-02 11:59    27  ********
  30    2020-08-02 12:00    27  ********
  31    2020-08-02 12:01    28  *********
  32    2020-08-02 12:02    29  **********
  33    2020-08-02 12:03    29  **********
  34    2020-08-02 12:04    30  ***********
 ...    ..(  4 skipped).    ..  ***********
  39    2020-08-02 12:09    30  ***********
  40    2020-08-02 12:10    31  ************
 ...    ..(  5 skipped).    ..  ************
  46    2020-08-02 12:16    31  ************
  47    2020-08-02 12:17    32  *************
 ...    ..(  2 skipped).    ..  *************
  50    2020-08-02 12:20    32  *************
  51    2020-08-02 12:21    33  **************
  52    2020-08-02 12:22    33  **************
  53    2020-08-02 12:23    33  **************
  54    2020-08-02 12:24    34  ***************
 ...    ..(  9 skipped).    ..  ***************
  64    2020-08-02 12:34    34  ***************
  65    2020-08-02 12:35    48  *****************************
 ...    ..( 20 skipped).    ..  *****************************
  86    2020-08-02 12:56    48  *****************************
  87    2020-08-02 12:57    47  ****************************
  88    2020-08-02 12:58    47  ****************************
  89    2020-08-02 12:59    47  ****************************
  90    2020-08-02 13:00    46  ***************************
  91    2020-08-02 13:01    46  ***************************
  92    2020-08-02 13:02    46  ***************************
  93    2020-08-02 13:03    45  **************************
 ...    ..(  2 skipped).    ..  **************************
  96    2020-08-02 13:06    45  **************************
  97    2020-08-02 13:07    44  *************************
 ...    ..( 14 skipped).    ..  *************************
 112    2020-08-02 13:22    44  *************************
 113    2020-08-02 13:23    43  ************************
 ...    ..( 19 skipped).    ..  ************************
 133    2020-08-02 13:43    43  ************************
 134    2020-08-02 13:44    42  ***********************
 ...    ..(  9 skipped).    ..  ***********************
 144    2020-08-02 13:54    42  ***********************
 145    2020-08-02 13:55    41  **********************
 ...    ..(  3 skipped).    ..  **********************
 149    2020-08-02 13:59    41  **********************
 150    2020-08-02 14:00    42  ***********************
 151    2020-08-02 14:01    42  ***********************
 152    2020-08-02 14:02    41  **********************
 ...    ..( 13 skipped).    ..  **********************
 166    2020-08-02 14:16    41  **********************
 167    2020-08-02 14:17    42  ***********************
 ...    ..( 24 skipped).    ..  ***********************
 192    2020-08-02 14:42    42  ***********************
 193    2020-08-02 14:43    41  **********************
 ...    ..(  7 skipped).    ..  **********************
 201    2020-08-02 14:51    41  **********************
 202    2020-08-02 14:52    42  ***********************
 203    2020-08-02 14:53    41  **********************
 ...    ..(  5 skipped).    ..  **********************
 209    2020-08-02 14:59    41  **********************
 210    2020-08-02 15:00    42  ***********************
 211    2020-08-02 15:01    41  **********************
 ...    ..( 15 skipped).    ..  **********************
 227    2020-08-02 15:17    41  **********************
 228    2020-08-02 15:18    42  ***********************
 ...    ..( 20 skipped).    ..  ***********************
 249    2020-08-02 15:39    42  ***********************
 250    2020-08-02 15:40    43  ************************
 251    2020-08-02 15:41    42  ***********************
 ...    ..( 41 skipped).    ..  ***********************
 293    2020-08-02 16:23    42  ***********************
 294    2020-08-02 16:24    43  ************************
 295    2020-08-02 16:25    42  ***********************
 ...    ..(  3 skipped).    ..  ***********************
 299    2020-08-02 16:29    42  ***********************
 300    2020-08-02 16:30    43  ************************
 301    2020-08-02 16:31    43  ************************
 302    2020-08-02 16:32    42  ***********************
 ...    ..( 26 skipped).    ..  ***********************
 329    2020-08-02 16:59    42  ***********************
 330    2020-08-02 17:00    43  ************************
 331    2020-08-02 17:01    42  ***********************
 ...    ..( 30 skipped).    ..  ***********************
 362    2020-08-02 17:32    42  ***********************
 363    2020-08-02 17:33    41  **********************
 ...    ..(  5 skipped).    ..  **********************
 369    2020-08-02 17:39    41  **********************
 370    2020-08-02 17:40    42  ***********************
 371    2020-08-02 17:41    42  ***********************
 372    2020-08-02 17:42    41  **********************
 ...    ..( 25 skipped).    ..  **********************
 398    2020-08-02 18:08    41  **********************

SCT Error Recovery Control:
           Read:     70 (7.0 seconds)
          Write:     70 (7.0 seconds)

Device Statistics (GP/SMART Log 0x04) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x0008  2            0  Device-to-host non-data FIS retries
0x0009  2            2  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2            3  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x000f  2            0  R_ERR response for host-to-device data FIS, CRC
0x0012  2            0  R_ERR response for host-to-device non-data FIS, CRC
0x8000  4         2363  Vendor specific

[-- Attachment #5: smartctl_xall_sdb --]
[-- Type: text/plain, Size: 15503 bytes --]

root@Nibler:~# smartctl --xall /dev/sdb
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-96-lowlatency] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red
Device Model:     WDC WD10JFCX-68N6GN0
Serial Number:    WD-WXS1A57H1LVF
LU WWN Device Id: 5 0014ee 607b8fe96
Firmware Version: 82.00A82
User Capacity:    1'000'204'886'016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Aug  2 18:07:23 2020 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM level is:     254 (maximum performance)
Rd look-ahead is: Enabled
Write cache is:   Enabled
ATA Security is:  Disabled, frozen [SEC2]
Wt Cache Reorder: 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: 		(18480) 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: 	 ( 207) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x703d)	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          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   200   200   051    -    0
  3 Spin_Up_Time            POS--K   178   177   021    -    2058
  4 Start_Stop_Count        -O--CK   100   100   000    -    27
  5 Reallocated_Sector_Ct   PO--CK   200   200   140    -    0
  7 Seek_Error_Rate         -OSR-K   100   253   000    -    0
  9 Power_On_Hours          -O--CK   074   074   000    -    19369
 10 Spin_Retry_Count        -O--CK   100   253   000    -    0
 11 Calibration_Retry_Count -O--CK   100   253   000    -    0
 12 Power_Cycle_Count       -O--CK   100   100   000    -    26
192 Power-Off_Retract_Count -O--CK   200   200   000    -    10
193 Load_Cycle_Count        -O--CK   189   189   000    -    35105
194 Temperature_Celsius     -O---K   112   095   000    -    35
196 Reallocated_Event_Count -O--CK   200   200   000    -    0
197 Current_Pending_Sector  -O--CK   200   200   000    -    0
198 Offline_Uncorrectable   ----CK   100   253   000    -    0
199 UDMA_CRC_Error_Count    -O--CK   200   200   000    -    0
200 Multi_Zone_Error_Rate   ---R--   100   253   000    -    0
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O      5  Comprehensive SMART error log
0x03       GPL     R/O      6  Ext. Comprehensive SMART error log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O      1  Extended self-test log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  SATA NCQ Queued Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x21       GPL     R/O      1  Write stream error log
0x22       GPL     R/O      1  Read stream error log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xa0-0xa7  GPL,SL  VS      16  Device vendor specific log
0xa8-0xb6  GPL,SL  VS       1  Device vendor specific log
0xb7       GPL,SL  VS      38  Device vendor specific log
0xbd       GPL,SL  VS       1  Device vendor specific log
0xc0       GPL,SL  VS       1  Device vendor specific log
0xc1       GPL     VS      93  Device vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
No Errors Logged

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     15690         -

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.

SCT Status Version:                  3
SCT Version (vendor specific):       258 (0x0102)
SCT Support Level:                   1
Device State:                        Active (0)
Current Temperature:                    35 Celsius
Power Cycle Min/Max Temperature:     25/35 Celsius
Lifetime    Min/Max Temperature:     20/52 Celsius
Under/Over Temperature Limit Count:   0/0
Vendor specific:
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        1 minute
Min/Max recommended Temperature:      0/60 Celsius
Min/Max Temperature Limit:           -41/85 Celsius
Temperature History Size (Index):    478 (416)

Index    Estimated Time   Temperature Celsius
 417    2020-08-02 10:10    41  **********************
 ...    ..( 65 skipped).    ..  **********************
   5    2020-08-02 11:16    41  **********************
   6    2020-08-02 11:17     ?  -
   7    2020-08-02 11:18    27  ********
 ...    ..(  2 skipped).    ..  ********
  10    2020-08-02 11:21    27  ********
  11    2020-08-02 11:22    28  *********
  12    2020-08-02 11:23    29  **********
  13    2020-08-02 11:24    30  ***********
 ...    ..(  2 skipped).    ..  ***********
  16    2020-08-02 11:27    30  ***********
  17    2020-08-02 11:28    31  ************
  18    2020-08-02 11:29    31  ************
  19    2020-08-02 11:30    31  ************
  20    2020-08-02 11:31     ?  -
  21    2020-08-02 11:32    31  ************
 ...    ..(  2 skipped).    ..  ************
  24    2020-08-02 11:35    31  ************
  25    2020-08-02 11:36    32  *************
  26    2020-08-02 11:37    32  *************
  27    2020-08-02 11:38    32  *************
  28    2020-08-02 11:39    33  **************
  29    2020-08-02 11:40    33  **************
  30    2020-08-02 11:41    34  ***************
  31    2020-08-02 11:42    34  ***************
  32    2020-08-02 11:43     ?  -
  33    2020-08-02 11:44    27  ********
 ...    ..(  2 skipped).    ..  ********
  36    2020-08-02 11:47    27  ********
  37    2020-08-02 11:48    28  *********
  38    2020-08-02 11:49     ?  -
  39    2020-08-02 11:50    28  *********
  40    2020-08-02 11:51    28  *********
  41    2020-08-02 11:52    28  *********
  42    2020-08-02 11:53    29  **********
  43    2020-08-02 11:54    29  **********
  44    2020-08-02 11:55     ?  -
  45    2020-08-02 11:56    25  ******
  46    2020-08-02 11:57    25  ******
  47    2020-08-02 11:58    26  *******
  48    2020-08-02 11:59    26  *******
  49    2020-08-02 12:00    27  ********
  50    2020-08-02 12:01    27  ********
  51    2020-08-02 12:02    27  ********
  52    2020-08-02 12:03    28  *********
  53    2020-08-02 12:04    29  **********
  54    2020-08-02 12:05    30  ***********
 ...    ..(  3 skipped).    ..  ***********
  58    2020-08-02 12:09    30  ***********
  59    2020-08-02 12:10    31  ************
  60    2020-08-02 12:11    31  ************
  61    2020-08-02 12:12    31  ************
  62    2020-08-02 12:13    32  *************
 ...    ..(  3 skipped).    ..  *************
  66    2020-08-02 12:17    32  *************
  67    2020-08-02 12:18    33  **************
 ...    ..(  2 skipped).    ..  **************
  70    2020-08-02 12:21    33  **************
  71    2020-08-02 12:22    34  ***************
  72    2020-08-02 12:23    34  ***************
  73    2020-08-02 12:24    34  ***************
  74    2020-08-02 12:25    35  ****************
 ...    ..(  7 skipped).    ..  ****************
  82    2020-08-02 12:33    35  ****************
  83    2020-08-02 12:34    48  *****************************
 ...    ..( 21 skipped).    ..  *****************************
 105    2020-08-02 12:56    48  *****************************
 106    2020-08-02 12:57    47  ****************************
 ...    ..(  2 skipped).    ..  ****************************
 109    2020-08-02 13:00    47  ****************************
 110    2020-08-02 13:01    46  ***************************
 111    2020-08-02 13:02    46  ***************************
 112    2020-08-02 13:03    46  ***************************
 113    2020-08-02 13:04    45  **************************
 ...    ..(  5 skipped).    ..  **************************
 119    2020-08-02 13:10    45  **************************
 120    2020-08-02 13:11    44  *************************
 ...    ..( 11 skipped).    ..  *************************
 132    2020-08-02 13:23    44  *************************
 133    2020-08-02 13:24    43  ************************
 ...    ..( 19 skipped).    ..  ************************
 153    2020-08-02 13:44    43  ************************
 154    2020-08-02 13:45    42  ***********************
 ...    ..( 17 skipped).    ..  ***********************
 172    2020-08-02 14:03    42  ***********************
 173    2020-08-02 14:04    41  **********************
 ...    ..(  8 skipped).    ..  **********************
 182    2020-08-02 14:13    41  **********************
 183    2020-08-02 14:14    42  ***********************
 ...    ..( 18 skipped).    ..  ***********************
 202    2020-08-02 14:33    42  ***********************
 203    2020-08-02 14:34    41  **********************
 ...    ..(  5 skipped).    ..  **********************
 209    2020-08-02 14:40    41  **********************
 210    2020-08-02 14:41    42  ***********************
 211    2020-08-02 14:42    42  ***********************
 212    2020-08-02 14:43    41  **********************
 ...    ..( 16 skipped).    ..  **********************
 229    2020-08-02 15:00    41  **********************
 230    2020-08-02 15:01    42  ***********************
 231    2020-08-02 15:02    42  ***********************
 232    2020-08-02 15:03    41  **********************
 ...    ..( 14 skipped).    ..  **********************
 247    2020-08-02 15:18    41  **********************
 248    2020-08-02 15:19    42  ***********************
 ...    ..( 70 skipped).    ..  ***********************
 319    2020-08-02 16:30    42  ***********************
 320    2020-08-02 16:31    43  ************************
 321    2020-08-02 16:32    43  ************************
 322    2020-08-02 16:33    42  ***********************
 ...    ..( 10 skipped).    ..  ***********************
 333    2020-08-02 16:44    42  ***********************
 334    2020-08-02 16:45    41  **********************
 ...    ..(  6 skipped).    ..  **********************
 341    2020-08-02 16:52    41  **********************
 342    2020-08-02 16:53    42  ***********************
 343    2020-08-02 16:54    42  ***********************
 344    2020-08-02 16:55    41  **********************
 ...    ..(  4 skipped).    ..  **********************
 349    2020-08-02 17:00    41  **********************
 350    2020-08-02 17:01    42  ***********************
 351    2020-08-02 17:02    42  ***********************
 352    2020-08-02 17:03    42  ***********************
 353    2020-08-02 17:04    41  **********************
 ...    ..(  7 skipped).    ..  **********************
 361    2020-08-02 17:12    41  **********************
 362    2020-08-02 17:13    42  ***********************
 ...    ..( 11 skipped).    ..  ***********************
 374    2020-08-02 17:25    42  ***********************
 375    2020-08-02 17:26    41  **********************
 ...    ..(  2 skipped).    ..  **********************
 378    2020-08-02 17:29    41  **********************
 379    2020-08-02 17:30    42  ***********************
 380    2020-08-02 17:31    42  ***********************
 381    2020-08-02 17:32    42  ***********************
 382    2020-08-02 17:33    41  **********************
 ...    ..(  6 skipped).    ..  **********************
 389    2020-08-02 17:40    41  **********************
 390    2020-08-02 17:41    42  ***********************
 391    2020-08-02 17:42    41  **********************
 ...    ..(  8 skipped).    ..  **********************
 400    2020-08-02 17:51    41  **********************
 401    2020-08-02 17:52    42  ***********************
 402    2020-08-02 17:53    41  **********************
 ...    ..( 13 skipped).    ..  **********************
 416    2020-08-02 18:07    41  **********************

SCT Error Recovery Control:
           Read:     70 (7.0 seconds)
          Write:     70 (7.0 seconds)

Device Statistics (GP/SMART Log 0x04) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x0008  2            0  Device-to-host non-data FIS retries
0x0009  2            2  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2            3  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x000f  2            0  R_ERR response for host-to-device data FIS, CRC
0x0012  2            0  R_ERR response for host-to-device non-data FIS, CRC
0x8000  4         2289  Vendor specific

[-- Attachment #6: mdadm_examine_sdb --]
[-- Type: text/plain, Size: 255 bytes --]

root@Nibler:~# mdadm --examine /dev/sdb
/dev/sdb:
   MBR Magic : aa55
Partition[0] :         6144 sectors at         2048 (type 83)
Partition[1] :   3674613760 sectors at         8192 (type 83)
Partition[2] :     37117952 sectors at   3674621952 (type 82)

[-- Attachment #7: mdadm_examine_sdd --]
[-- Type: text/plain, Size: 1147 bytes --]

root@Nibler:~# mdadm --examine /dev/sdd
/dev/sdd:
          Magic : Intel Raid ISM Cfg Sig.
        Version : 1.0.00
    Orig Family : bc081a95
         Family : bc081a95
     Generation : 00000056
     Attributes : All supported
           UUID : 20abbab0:bfc65211:fae8306d:1bed033e
       Checksum : de77ee21 correct
    MPB Sectors : 1
          Disks : 2
   RAID Devices : 1

  Disk01 Serial : WD-WX71EB6D6JL5
          State : active
             Id : 00000000
    Usable Size : 1953514766 (931.51 GiB 1000.20 GB)

[Echinops]:
           UUID : db4d2351:36a2bf8b:3508e539:9becbd9b
     RAID Level : 0
        Members : 2
          Slots : [_U]
    Failed disk : none
      This Slot : 1
    Sector Size : 512
     Array Size : 3711741952 (1769.90 GiB 1900.41 GB)
   Per Dev Size : 1855871240 (884.95 GiB 950.21 GB)
  Sector Offset : 0
    Num Stripes : 7249496
     Chunk Size : 128 KiB
       Reserved : 0
  Migrate State : idle
      Map State : failed
    Dirty State : clean
     RWH Policy : off

  Disk00 Serial : D-WXS1A57H1LVF:0
          State : active
             Id : ffffffff
    Usable Size : 1953514766 (931.51 GiB 1000.20 GB)

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Restoring a raid0 for data rescue
  2020-08-02 18:09 ` Restoring a raid0 for data rescue tyranastrasz
@ 2020-08-02 19:01   ` antlists
  2020-08-02 19:24     ` tyranastrasz
  0 siblings, 1 reply; 9+ messages in thread
From: antlists @ 2020-08-02 19:01 UTC (permalink / raw)
  To: tyranastrasz, linux-raid

On 02/08/2020 19:09, tyranastrasz@gmx.de wrote:
> Hello
> 
> I've a problem with my raid0.
> The probelmatic disks (2x 1TB wdred) were in usage in my server, now
> they got replaced with 3x 4TB seagate in a raid5.
> 
> Before I turned them off, I made a backup on an external drive (normal
> hdd via USB) via rsync -avx /source /mnt/external/
> 
> Whatever happens in the night, the backup isn't complete and I miss files.
> So I put the old raid again into the server and wanted to start, but the
> Intel Raid Controller said that one of the disks are no member of a raid.
> 
> My server mainboard is from Gigabyte a MX11-PC0.
> 
> Well I made some mdadm examines, smartctl, mdstat, lsdrv logfiles and
> attached them to the mail.
> 
Ow...

This is still the same linux on the server? Because mdstat says no raid 
personalities are installed. Either linux has changed or you've got 
hardware raid. in which case you'll need to read up on the motherboard 
manual.

I'm not sure what they're called, but try "insmod raid1x" I think it is. 
Could be raid0x. If that loads the raid0 driver, cat /proc/mdstat should 
list raid0 as a personality. Once that's there, mdadm may be able to 
start the array.

Until you've got a working raid driver in the kernel, I certainly can't 
help any further. But hopefully reading the mobo manual might help. The 
other thing to try is an up-to-date rescue disk and see if that can read 
the array.

Cheers,
Wol

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Restoring a raid0 for data rescue
  2020-08-02 19:01   ` antlists
@ 2020-08-02 19:24     ` tyranastrasz
  2020-08-02 20:38       ` tyranastrasz
  0 siblings, 1 reply; 9+ messages in thread
From: tyranastrasz @ 2020-08-02 19:24 UTC (permalink / raw)
  To: antlists, linux-raid

On 02.08.20 21:01, antlists wrote:
> On 02/08/2020 19:09, tyranastrasz@gmx.de wrote:
>> Hello
>>
>> I've a problem with my raid0.
>> The probelmatic disks (2x 1TB wdred) were in usage in my server, now
>> they got replaced with 3x 4TB seagate in a raid5.
>>
>> Before I turned them off, I made a backup on an external drive (normal
>> hdd via USB) via rsync -avx /source /mnt/external/
>>
>> Whatever happens in the night, the backup isn't complete and I miss
>> files.
>> So I put the old raid again into the server and wanted to start, but the
>> Intel Raid Controller said that one of the disks are no member of a raid.
>>
>> My server mainboard is from Gigabyte a MX11-PC0.
>>
>> Well I made some mdadm examines, smartctl, mdstat, lsdrv logfiles and
>> attached them to the mail.
>>
> Ow...
>
> This is still the same linux on the server? Because mdstat says no raid
> personalities are installed. Either linux has changed or you've got
> hardware raid. in which case you'll need to read up on the motherboard
> manual.
>
> I'm not sure what they're called, but try "insmod raid1x" I think it is.
> Could be raid0x. If that loads the raid0 driver, cat /proc/mdstat should
> list raid0 as a personality. Once that's there, mdadm may be able to
> start the array.
>
> Until you've got a working raid driver in the kernel, I certainly can't
> help any further. But hopefully reading the mobo manual might help. The
> other thing to try is an up-to-date rescue disk and see if that can read
> the array.
>
> Cheers,
> Wol

No, I have the disks in my pc.
The server can't boot the disks because Intel Storage says the raid has
a failure, because one of the disks has no raid information. But as I
read them both yesterday they had, now (see the last attachment) one of
them has none.
It makes no sense... I need the files

Intel means "yeah make a new raid, with data loss" that's no option.

Nara

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Restoring a raid0 for data rescue
  2020-08-02 19:24     ` tyranastrasz
@ 2020-08-02 20:38       ` tyranastrasz
  2020-08-02 20:50         ` antlists
  2020-08-03  4:37         ` NeilBrown
  0 siblings, 2 replies; 9+ messages in thread
From: tyranastrasz @ 2020-08-02 20:38 UTC (permalink / raw)
  To: antlists, linux-raid

On 02.08.20 21:24, tyranastrasz@gmx.de wrote:
> On 02.08.20 21:01, antlists wrote:
>> On 02/08/2020 19:09, tyranastrasz@gmx.de wrote:
>>> Hello
>>>
>>> I've a problem with my raid0.
>>> The probelmatic disks (2x 1TB wdred) were in usage in my server, now
>>> they got replaced with 3x 4TB seagate in a raid5.
>>>
>>> Before I turned them off, I made a backup on an external drive (normal
>>> hdd via USB) via rsync -avx /source /mnt/external/
>>>
>>> Whatever happens in the night, the backup isn't complete and I miss
>>> files.
>>> So I put the old raid again into the server and wanted to start, but the
>>> Intel Raid Controller said that one of the disks are no member of a
>>> raid.
>>>
>>> My server mainboard is from Gigabyte a MX11-PC0.
>>>
>>> Well I made some mdadm examines, smartctl, mdstat, lsdrv logfiles and
>>> attached them to the mail.
>>>
>> Ow...
>>
>> This is still the same linux on the server? Because mdstat says no raid
>> personalities are installed. Either linux has changed or you've got
>> hardware raid. in which case you'll need to read up on the motherboard
>> manual.
>>
>> I'm not sure what they're called, but try "insmod raid1x" I think it is.
>> Could be raid0x. If that loads the raid0 driver, cat /proc/mdstat should
>> list raid0 as a personality. Once that's there, mdadm may be able to
>> start the array.
>>
>> Until you've got a working raid driver in the kernel, I certainly can't
>> help any further. But hopefully reading the mobo manual might help. The
>> other thing to try is an up-to-date rescue disk and see if that can read
>> the array.
>>
>> Cheers,
>> Wol
>
> No, I have the disks in my pc.
> The server can't boot the disks because Intel Storage says the raid has
> a failure, because one of the disks has no raid information. But as I
> read them both yesterday they had, now (see the last attachment) one of
> them has none.
> It makes no sense... I need the files
>
> Intel means "yeah make a new raid, with data loss" that's no option.
>
> Nara


I tried something what was told here
https://askubuntu.com/questions/69086/mdadm-superblock-recovery

root@Nibler:~# mdadm --create /dev/md0 -v -f -l 0 -c 128 -n 2 /dev/sdd
/dev/sdb
mdadm: /dev/sdd appears to be part of a raid array:
        level=container devices=0 ctime=Thu Jan  1 01:00:00 1970
mdadm: partition table exists on /dev/sdb
mdadm: partition table exists on /dev/sdb but will be lost or
        meaningless after creating array
Continue creating array? yes
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md0 started.


root@Nibler:~# mdadm --examine /dev/sdb
/dev/sdb:
           Magic : a92b4efc
         Version : 1.2
     Feature Map : 0x0
      Array UUID : db01d7d9:e46ce30a:792e1d3a:31618e71
            Name : Nibler:0  (local to host Nibler)
   Creation Time : Sun Aug  2 22:13:10 2020
      Raid Level : raid0
    Raid Devices : 2

  Avail Dev Size : 1953260976 (931.39 GiB 1000.07 GB)
     Data Offset : 264192 sectors
    Super Offset : 8 sectors
    Unused Space : before=264112 sectors, after=0 sectors
           State : clean
     Device UUID : 0ea95638:7e83e76b:848ff6d2:e264029b

     Update Time : Sun Aug  2 22:13:10 2020
   Bad Block Log : 512 entries available at offset 8 sectors
        Checksum : 1b2cf600 - correct
          Events : 0

      Chunk Size : 128K

    Device Role : Active device 1
    Array State : AA ('A' == active, '.' == missing, 'R' == replacing)
root@Nibler:~# mdadm --examine /dev/sdd
/dev/sdd:
           Magic : a92b4efc
         Version : 1.2
     Feature Map : 0x0
      Array UUID : db01d7d9:e46ce30a:792e1d3a:31618e71
            Name : Nibler:0  (local to host Nibler)
   Creation Time : Sun Aug  2 22:13:10 2020
      Raid Level : raid0
    Raid Devices : 2

  Avail Dev Size : 1953260976 (931.39 GiB 1000.07 GB)
     Data Offset : 264192 sectors
    Super Offset : 8 sectors
    Unused Space : before=264112 sectors, after=0 sectors
           State : clean
     Device UUID : cef9d210:a794ef1e:6e37ee0e:34e10c52

     Update Time : Sun Aug  2 22:13:10 2020
   Bad Block Log : 512 entries available at offset 8 sectors
        Checksum : 99b37c22 - correct
          Events : 0

      Chunk Size : 128K

    Device Role : Active device 0
    Array State : AA ('A' == active, '.' == missing, 'R' == replacing)


But I have no access to /dev/md0 or /dev/md0p1 or /dev/md0p2

root@Nibler:~# mount -o ro /dev/md0p1 /mnt/raid
NTFS signature is missing.
Failed to mount '/dev/md0p1': Invalid argument
The device '/dev/md0p1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?


What can I do now?
Even if it costs money...

Nara

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Restoring a raid0 for data rescue
  2020-08-02 20:38       ` tyranastrasz
@ 2020-08-02 20:50         ` antlists
  2020-08-03  0:46           ` tyranastrasz
  2020-08-03  4:37         ` NeilBrown
  1 sibling, 1 reply; 9+ messages in thread
From: antlists @ 2020-08-02 20:50 UTC (permalink / raw)
  To: tyranastrasz, linux-raid, Phil Turmel, NeilBrown

On 02/08/2020 21:38, tyranastrasz@gmx.de wrote:
> On 02.08.20 21:24, tyranastrasz@gmx.de wrote:
>> On 02.08.20 21:01, antlists wrote:
>>> On 02/08/2020 19:09, tyranastrasz@gmx.de wrote:
>>>> Hello
>>>>
>>>> I've a problem with my raid0.
>>>> The probelmatic disks (2x 1TB wdred) were in usage in my server, now
>>>> they got replaced with 3x 4TB seagate in a raid5.
>>>>
>>>> Before I turned them off, I made a backup on an external drive (normal
>>>> hdd via USB) via rsync -avx /source /mnt/external/
>>>>
>>>> Whatever happens in the night, the backup isn't complete and I miss
>>>> files.
>>>> So I put the old raid again into the server and wanted to start, but 
>>>> the
>>>> Intel Raid Controller said that one of the disks are no member of a
>>>> raid.
>>>>
>>>> My server mainboard is from Gigabyte a MX11-PC0.
>>>>
>>>> Well I made some mdadm examines, smartctl, mdstat, lsdrv logfiles and
>>>> attached them to the mail.
>>>>
>>> Ow...
>>>
>>> This is still the same linux on the server? Because mdstat says no raid
>>> personalities are installed. Either linux has changed or you've got
>>> hardware raid. in which case you'll need to read up on the motherboard
>>> manual.
>>>
>>> I'm not sure what they're called, but try "insmod raid1x" I think it is.
>>> Could be raid0x. If that loads the raid0 driver, cat /proc/mdstat should
>>> list raid0 as a personality. Once that's there, mdadm may be able to
>>> start the array.
>>>
>>> Until you've got a working raid driver in the kernel, I certainly can't
>>> help any further. But hopefully reading the mobo manual might help. The
>>> other thing to try is an up-to-date rescue disk and see if that can read
>>> the array.
>>>
>>> Cheers,
>>> Wol
>>
>> No, I have the disks in my pc.
>> The server can't boot the disks because Intel Storage says the raid has
>> a failure, because one of the disks has no raid information. But as I
>> read them both yesterday they had, now (see the last attachment) one of
>> them has none.
>> It makes no sense... I need the files
>>
>> Intel means "yeah make a new raid, with data loss" that's no option.
>>
>> Nara
> 
> 
> I tried something what was told here
> https://askubuntu.com/questions/69086/mdadm-superblock-recovery
> 
> root@Nibler:~# mdadm --create /dev/md0 -v -f -l 0 -c 128 -n 2 /dev/sdd
> /dev/sdb

OH SHIT !!!

You didn't try booting with a rescue disk? That mistake could well cost 
you the array :-( I'm out of my depth ...

https://raid.wiki.kernel.org/index.php/Linux_Raid
https://raid.wiki.kernel.org/index.php/Linux_Raid#When_Things_Go_Wrogn

I've called in the heavy cavalry, and fortunately with 1.2 the damage 
might not be too bad.

Here's hoping,
Wol

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Restoring a raid0 for data rescue
  2020-08-02 20:50         ` antlists
@ 2020-08-03  0:46           ` tyranastrasz
  2020-08-03  2:55             ` Phil Turmel
  0 siblings, 1 reply; 9+ messages in thread
From: tyranastrasz @ 2020-08-03  0:46 UTC (permalink / raw)
  To: antlists, linux-raid, Phil Turmel, NeilBrown

On 02.08.20 22:50, antlists wrote:
> On 02/08/2020 21:38, tyranastrasz@gmx.de wrote:
>> On 02.08.20 21:24, tyranastrasz@gmx.de wrote:
>>> On 02.08.20 21:01, antlists wrote:
>>>> On 02/08/2020 19:09, tyranastrasz@gmx.de wrote:
>>>>> Hello
>>>>>
>>>>> I've a problem with my raid0.
>>>>> The probelmatic disks (2x 1TB wdred) were in usage in my server, now
>>>>> they got replaced with 3x 4TB seagate in a raid5.
>>>>>
>>>>> Before I turned them off, I made a backup on an external drive (normal
>>>>> hdd via USB) via rsync -avx /source /mnt/external/
>>>>>
>>>>> Whatever happens in the night, the backup isn't complete and I miss
>>>>> files.
>>>>> So I put the old raid again into the server and wanted to start,
>>>>> but the
>>>>> Intel Raid Controller said that one of the disks are no member of a
>>>>> raid.
>>>>>
>>>>> My server mainboard is from Gigabyte a MX11-PC0.
>>>>>
>>>>> Well I made some mdadm examines, smartctl, mdstat, lsdrv logfiles and
>>>>> attached them to the mail.
>>>>>
>>>> Ow...
>>>>
>>>> This is still the same linux on the server? Because mdstat says no raid
>>>> personalities are installed. Either linux has changed or you've got
>>>> hardware raid. in which case you'll need to read up on the motherboard
>>>> manual.
>>>>
>>>> I'm not sure what they're called, but try "insmod raid1x" I think it
>>>> is.
>>>> Could be raid0x. If that loads the raid0 driver, cat /proc/mdstat
>>>> should
>>>> list raid0 as a personality. Once that's there, mdadm may be able to
>>>> start the array.
>>>>
>>>> Until you've got a working raid driver in the kernel, I certainly can't
>>>> help any further. But hopefully reading the mobo manual might help. The
>>>> other thing to try is an up-to-date rescue disk and see if that can
>>>> read
>>>> the array.
>>>>
>>>> Cheers,
>>>> Wol
>>>
>>> No, I have the disks in my pc.
>>> The server can't boot the disks because Intel Storage says the raid has
>>> a failure, because one of the disks has no raid information. But as I
>>> read them both yesterday they had, now (see the last attachment) one of
>>> them has none.
>>> It makes no sense... I need the files
>>>
>>> Intel means "yeah make a new raid, with data loss" that's no option.
>>>
>>> Nara
>>
>>
>> I tried something what was told here
>> https://askubuntu.com/questions/69086/mdadm-superblock-recovery
>>
>> root@Nibler:~# mdadm --create /dev/md0 -v -f -l 0 -c 128 -n 2 /dev/sdd
>> /dev/sdb
>
> OH SHIT !!!
>
> You didn't try booting with a rescue disk? That mistake could well cost
> you the array :-( I'm out of my depth ...
>
> https://raid.wiki.kernel.org/index.php/Linux_Raid
> https://raid.wiki.kernel.org/index.php/Linux_Raid#When_Things_Go_Wrogn
>
> I've called in the heavy cavalry, and fortunately with 1.2 the damage
> might not be too bad.
>
> Here's hoping,
> Wol

What do you mean with 1.2?

Should I do?
https://raid.wiki.kernel.org/index.php/Recovering_a_damaged_RAID

I wait for an answer so I do it not more complicated :/
But is it not possible to merge both disks together into a virtual one,
block by block?
Our put the old superblock back?

I dunno what's the best solution.

Thanks
Nara

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Restoring a raid0 for data rescue
  2020-08-03  0:46           ` tyranastrasz
@ 2020-08-03  2:55             ` Phil Turmel
  0 siblings, 0 replies; 9+ messages in thread
From: Phil Turmel @ 2020-08-03  2:55 UTC (permalink / raw)
  To: tyranastrasz, antlists, linux-raid, NeilBrown

On 8/2/20 8:46 PM, tyranastrasz@gmx.de wrote:
> On 02.08.20 22:50, antlists wrote:

>>>> No, I have the disks in my pc.
>>>> The server can't boot the disks because Intel Storage says the raid has
>>>> a failure, because one of the disks has no raid information. But as I
>>>> read them both yesterday they had, now (see the last attachment) one of
>>>> them has none.
>>>> It makes no sense... I need the files
>>>>
>>>> Intel means "yeah make a new raid, with data loss" that's no option.
>>>>
>>>> Nara
>>>
>>>
>>> I tried something what was told here
>>> https://askubuntu.com/questions/69086/mdadm-superblock-recovery
>>>
>>> root@Nibler:~# mdadm --create /dev/md0 -v -f -l 0 -c 128 -n 2 /dev/sdd
>>> /dev/sdb
>>
>> OH SHIT !!!
>>
>> You didn't try booting with a rescue disk? That mistake could well cost
>> you the array :-( I'm out of my depth ...
>>
>> https://raid.wiki.kernel.org/index.php/Linux_Raid
>> https://raid.wiki.kernel.org/index.php/Linux_Raid#When_Things_Go_Wrogn
>>
>> I've called in the heavy cavalry, and fortunately with 1.2 the damage
>> might not be too bad.
>>
>> Here's hoping,
>> Wol
> 
> What do you mean with 1.2?
> 
> Should I do?
> https://raid.wiki.kernel.org/index.php/Recovering_a_damaged_RAID
> 
> I wait for an answer so I do it not more complicated :/
> But is it not possible to merge both disks together into a virtual one,
> block by block?
> Our put the old superblock back?
> 
> I dunno what's the best solution.
> 
> Thanks
> Nara

Oy.  I don't mind being called a "big gun", but I've zero experience 
with IMSM / software raid combinations.  Not even a sparkler for you, sorry.

I avoid any form of "fakeraid" as too dangerous to play with.  I 
understand it is necessary if you wish to dual boot windows and linux on 
the same raid, but I don't do the former at all any more (no bare metal 
windows in my life for over a decade, now).

):

Phil

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Restoring a raid0 for data rescue
  2020-08-02 20:38       ` tyranastrasz
  2020-08-02 20:50         ` antlists
@ 2020-08-03  4:37         ` NeilBrown
  2020-08-04  0:51           ` tyranastrasz
  1 sibling, 1 reply; 9+ messages in thread
From: NeilBrown @ 2020-08-03  4:37 UTC (permalink / raw)
  To: tyranastrasz, antlists, linux-raid

[-- Attachment #1: Type: text/plain, Size: 1930 bytes --]

On Sun, Aug 02 2020, tyranastrasz@gmx.de wrote:
>
> I tried something what was told here
> https://askubuntu.com/questions/69086/mdadm-superblock-recovery
>
> root@Nibler:~# mdadm --create /dev/md0 -v -f -l 0 -c 128 -n 2 /dev/sdd
> /dev/sdb

That was a mistake.  I probably could have saved you before you did
that.  Maybe I still can...

You have an Intel IMSM RAID0 array over sdb and sdd.
This was 3711741952 sectors in size using the first 1855871240 sectors
of each device - data arranged in 7249496 256KiB stripes (128KiB on each
device).

This 1900GB array was partitioned into 3 partitions: 3MB, 1800MB,
and 18MB.

Presumably the data you want is on the 2nd partition: the 1800MB one?

When you ran the "mdadm --create" command it wrote some meta data at the
start of the device - probably only a 4K block at 8K from the start.
This is before the first partition, so it might not have affected any
data at all.  It may have corrupted the partition table.

You need to put the array together again without writing anything to
it.  Fortunately that is fairly easy with RAID0.

1/ If /dev/md0 still exists, stop it "mdadm --stop /dev/md0"
2/ put the two devices into a RAID0 with no metadata.
    mdadm --build /dev/md0 -n 2 -z 927935620 -c 128 -l 0 /dev/sdb /dev/sdd

3/ create a read-only loop device over the second partition
    losetup -r -o 4096K --sizelimit 7176980M /dev/loop0 /dev/md0

4/ Examine the filesystem at /dev/loop0 READ-ONLY.
  You didn't say what sort of filesystem you used.  If ext4, then
     fsck -n /dev/loop0

5/ If it looks good, try mounting /dev/loop0 READ-ONLY.

I recommend that you FIRST read the relevant parts of the mdadm and
losetup man pages, and check my arithmetic to make sure the numbers that
I have given are correct.  If unsure, ask.

If it doesn't work, I recommend reporting results, asking, and waiting
before doing anything that might change anything on the drives.

NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Restoring a raid0 for data rescue
  2020-08-03  4:37         ` NeilBrown
@ 2020-08-04  0:51           ` tyranastrasz
  0 siblings, 0 replies; 9+ messages in thread
From: tyranastrasz @ 2020-08-04  0:51 UTC (permalink / raw)
  To: NeilBrown, antlists, linux-raid

Your numbers were correct, everything is perfect from you.
Yes it is everything on the 1800GB partition, ext4. It's consistency is
by 100%.
It worked perfectly!

You saved over 6 month of hard work!
Thank you so much!

The heatwave killed my braincells :/

All who helped get included of my godnight prayer, thank you :)

Nara
- Can now sleep well

On 03.08.20 06:37, NeilBrown wrote:
> On Sun, Aug 02 2020, tyranastrasz@gmx.de wrote:
>>
>> I tried something what was told here
>> https://askubuntu.com/questions/69086/mdadm-superblock-recovery
>>
>> root@Nibler:~# mdadm --create /dev/md0 -v -f -l 0 -c 128 -n 2 /dev/sdd
>> /dev/sdb
>
> That was a mistake.  I probably could have saved you before you did
> that.  Maybe I still can...
>
> You have an Intel IMSM RAID0 array over sdb and sdd.
> This was 3711741952 sectors in size using the first 1855871240 sectors
> of each device - data arranged in 7249496 256KiB stripes (128KiB on each
> device).
>
> This 1900GB array was partitioned into 3 partitions: 3MB, 1800MB,
> and 18MB.
>
> Presumably the data you want is on the 2nd partition: the 1800MB one?
>
> When you ran the "mdadm --create" command it wrote some meta data at the
> start of the device - probably only a 4K block at 8K from the start.
> This is before the first partition, so it might not have affected any
> data at all.  It may have corrupted the partition table.
>
> You need to put the array together again without writing anything to
> it.  Fortunately that is fairly easy with RAID0.
>
> 1/ If /dev/md0 still exists, stop it "mdadm --stop /dev/md0"
> 2/ put the two devices into a RAID0 with no metadata.
>      mdadm --build /dev/md0 -n 2 -z 927935620 -c 128 -l 0 /dev/sdb /dev/sdd
>
> 3/ create a read-only loop device over the second partition
>      losetup -r -o 4096K --sizelimit 7176980M /dev/loop0 /dev/md0
>
> 4/ Examine the filesystem at /dev/loop0 READ-ONLY.
>    You didn't say what sort of filesystem you used.  If ext4, then
>       fsck -n /dev/loop0
>
> 5/ If it looks good, try mounting /dev/loop0 READ-ONLY.
>
> I recommend that you FIRST read the relevant parts of the mdadm and
> losetup man pages, and check my arithmetic to make sure the numbers that
> I have given are correct.  If unsure, ask.
>
> If it doesn't work, I recommend reporting results, asking, and waiting
> before doing anything that might change anything on the drives.
>
> NeilBrown
>

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2020-08-04  0:51 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <S1726630AbgHBR6v/20200802175851Z+2001@vger.kernel.org>
2020-08-02 18:09 ` Restoring a raid0 for data rescue tyranastrasz
2020-08-02 19:01   ` antlists
2020-08-02 19:24     ` tyranastrasz
2020-08-02 20:38       ` tyranastrasz
2020-08-02 20:50         ` antlists
2020-08-03  0:46           ` tyranastrasz
2020-08-03  2:55             ` Phil Turmel
2020-08-03  4:37         ` NeilBrown
2020-08-04  0:51           ` tyranastrasz

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox