Please help RAID1 complete fail no superblock
Hello good people of the linux-raid group,
I really need your help with my RAID1 that has completely failed, on which I have photos of my beloved deceased grandparents.
I had the RAID1 array for about 3 years, and I had replaced one of the drives when it failed about one year ago. All worked fine.
A few weeks ago, I bought a new computer and wanted to move the array to the new computer.
I read several guides, and thought that all I had to do was turn both computers off, move the drives, and in the new computer execute: mdadm --assemble --scan which I did.
The output was: mdadm: /dev/sdb has no superblock - assembly aborted
I panicked, moved the drives back, but the old RAID wouldn't start! The old computer too says that one of the drives has no superblock and, even worse, that the other is UNALLOCATED SPACE!!!
I don't understand why the partition on the second drive disappeared, and I'm so worried.
PLEASE, PLEASE help me...
I read the wiki pages (raid wiki kernel), but I'm afraid to run any commands that might make things worse.
I would be very happy if I could restore the data from either one of the drives, and copy it to the new drives in my new computer (as I should have done before moving the drives).
I attached the output of smartctl --xall for both drives to this email.
Please see the output of the following commands:
uname -a
Linux 3.8.0-35-generic #50-Ubuntu SMP Tue Dec 3 01:24:59 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
mdadm -V
mdadm - v3.2.5 - 18th May 2012
/proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] unused devices: <none>
mdadm --detail /dev/md1
mdadm: cannot open /dev/md1: No such file or directory
mdadm --assemble /dev/md1 /dev/sd[bc]
mdadm: Cannot assemble mbr metadata on /dev/sdb
mdadm: /dev/sdb has no superblock - assembly aborted
(same out put for --force --assemble)
mdadm --examine /dev/sdb/dev/sdb:
MBR Magic : aa55
Partition[0] : 4294967295 sectors at 1 (type ee)
mdadm --examine /dev/sdb1
mdadm: No md superblock detected on /dev/sdb1
mdadm --examine /dev/sdc/dev/sdc:
MBR Magic : aa55
Partition[0] : 4294967295 sectors at 1 (type ee)
mdadm --examine /dev/sdc1
mdadm: cannot open /dev/sdc1: No such file or directory
I also have the UUID of the array from before the move in a copy of the mdadm.conf file, although I don't know how it could assist.
Any help and guidance would be very much appreciated.
Thank you!
Yaniv
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Caviar Green (Adv. Format) Device Model: WDC WD30EZRX-00DC0B0 Serial Number: WD-WMC1T1439000 LU WWN Device Id: 5 0014ee 0ae24394c Firmware Version: 80.00A80 User Capacity: 3,000,592,982,016 bytes [3.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: ACS-2 (revision not indicated) Local Time is: Mon Nov 14 00:19:07 2016 IST SMART support is: Available - device has SMART capability. SMART support is: Disabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled ATA Security is: Disabled, NOT FROZEN [SEC1]
=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART 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: (40080) 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: ( 402) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x70b5) SCT Status supported.
SCT Feature Control supported. SCT Data Table supported.
SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-K 200 200 051 - 3
3 Spin_Up_Time POS--K 190 173 021 - 5475
4 Start_Stop_Count -O--CK 100 100 000 - 168
5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0
7 Seek_Error_Rate -OSR-K 200 200 000 - 0
9 Power_On_Hours -O--CK 066 066 000 - 25069
10 Spin_Retry_Count -O--CK 100 100 000 - 0
11 Calibration_Retry_Count -O--CK 100 100 000 - 0
12 Power_Cycle_Count -O--CK 100 100 000 - 168
192 Power-Off_Retract_Count -O--CK 200 200 000 - 140
193 Load_Cycle_Count -O--CK 153 153 000 - 141868
194 Temperature_Celsius -O---K 120 106 000 - 30
196 Reallocated_Event_Count -O--CK 200 200 000 - 0
197 Current_Pending_Sector -O--CK 200 200 000 - 0
198 Offline_Uncorrectable ----CK 200 200 000 - 0
199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0
200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 0
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warningGeneral Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
GP/S Log at address 0x00 has 1 sectors [Log Directory] SMART Log at address 0x01 has 1 sectors [Summary SMART error log] SMART Log at address 0x02 has 5 sectors [Comprehensive SMART error log] GP Log at address 0x03 has 6 sectors [Ext. Comprehensive SMART error log] SMART Log at address 0x06 has 1 sectors [SMART self-test log] GP Log at address 0x07 has 1 sectors [Extended self-test log] SMART Log at address 0x09 has 1 sectors [Selective self-test log] GP Log at address 0x10 has 1 sectors [NCQ Command Error log] GP Log at address 0x11 has 1 sectors [SATA Phy Event Counters] GP/S Log at address 0x80 has 16 sectors [Host vendor specific log] GP/S Log at address 0x81 has 16 sectors [Host vendor specific log] GP/S Log at address 0x82 has 16 sectors [Host vendor specific log] GP/S Log at address 0x83 has 16 sectors [Host vendor specific log] GP/S Log at address 0x84 has 16 sectors [Host vendor specific log] GP/S Log at address 0x85 has 16 sectors [Host vendor specific log] GP/S Log at address 0x86 has 16 sectors [Host vendor specific log] GP/S Log at address 0x87 has 16 sectors [Host vendor specific log] GP/S Log at address 0x88 has 16 sectors [Host vendor specific log] GP/S Log at address 0x89 has 16 sectors [Host vendor specific log] GP/S Log at address 0x8a has 16 sectors [Host vendor specific log] GP/S Log at address 0x8b has 16 sectors [Host vendor specific log] GP/S Log at address 0x8c has 16 sectors [Host vendor specific log] GP/S Log at address 0x8d has 16 sectors [Host vendor specific log] GP/S Log at address 0x8e has 16 sectors [Host vendor specific log] GP/S Log at address 0x8f has 16 sectors [Host vendor specific log] GP/S Log at address 0x90 has 16 sectors [Host vendor specific log] GP/S Log at address 0x91 has 16 sectors [Host vendor specific log] GP/S Log at address 0x92 has 16 sectors [Host vendor specific log] GP/S Log at address 0x93 has 16 sectors [Host vendor specific log] GP/S Log at address 0x94 has 16 sectors [Host vendor specific log] GP/S Log at address 0x95 has 16 sectors [Host vendor specific log] GP/S Log at address 0x96 has 16 sectors [Host vendor specific log] GP/S Log at address 0x97 has 16 sectors [Host vendor specific log] GP/S Log at address 0x98 has 16 sectors [Host vendor specific log] GP/S Log at address 0x99 has 16 sectors [Host vendor specific log] GP/S Log at address 0x9a has 16 sectors [Host vendor specific log] GP/S Log at address 0x9b has 16 sectors [Host vendor specific log] GP/S Log at address 0x9c has 16 sectors [Host vendor specific log] GP/S Log at address 0x9d has 16 sectors [Host vendor specific log] GP/S Log at address 0x9e has 16 sectors [Host vendor specific log] GP/S Log at address 0x9f has 16 sectors [Host vendor specific log] GP/S Log at address 0xa0 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa1 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa2 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa3 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa4 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa5 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa6 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa7 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa8 has 1 sectors [Device vendor specific log] GP/S Log at address 0xa9 has 1 sectors [Device vendor specific log] GP/S Log at address 0xaa has 1 sectors [Device vendor specific log] GP/S Log at address 0xab has 1 sectors [Device vendor specific log] GP/S Log at address 0xac has 1 sectors [Device vendor specific log] GP/S Log at address 0xad has 1 sectors [Device vendor specific log] GP/S Log at address 0xae has 1 sectors [Device vendor specific log] GP/S Log at address 0xaf has 1 sectors [Device vendor specific log] GP/S Log at address 0xb0 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb1 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb2 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb3 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb4 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb5 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb6 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb7 has 1 sectors [Device vendor specific log] GP/S Log at address 0xbd has 1 sectors [Device vendor specific log] GP/S Log at address 0xc0 has 1 sectors [Device vendor specific log] GP Log at address 0xc1 has 93 sectors [Device vendor specific log] GP/S Log at address 0xe0 has 1 sectors [SCT Command/Status] GP/S Log at address 0xe1 has 1 sectors [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% 17488 - # 2 Short offline Completed without error 00% 8774 - # 3 Extended offline Completed without error 00% 7531 - # 4 Short offline Completed without error 00% 2 -
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_testingSelective 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: 30 Celsius Power Cycle Min/Max Temperature: 30/30 Celsius Lifetime Min/Max Temperature: 15/44 Celsius Under/Over Temperature Limit Count: 0/0 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 (373)
Index Estimated Time Temperature Celsius
374 2016-11-13 16:22 31 ************ ... ..(116 skipped). .. ************ 13 2016-11-13 18:19 31 ************ 14 2016-11-13 18:20 32 ************* ... ..( 3 skipped). .. ************* 18 2016-11-13 18:24 32 ************* 19 2016-11-13 18:25 31 ************ ... ..( 6 skipped). .. ************ 26 2016-11-13 18:32 31 ************ 27 2016-11-13 18:33 30 *********** 28 2016-11-13 18:34 ? - 29 2016-11-13 18:35 24 ***** 30 2016-11-13 18:36 24 ***** 31 2016-11-13 18:37 25 ****** 32 2016-11-13 18:38 ? - 33 2016-11-13 18:39 30 *********** ... ..( 5 skipped). .. *********** 39 2016-11-13 18:45 30 *********** 40 2016-11-13 18:46 27 ******** ... ..( 14 skipped). .. ******** 55 2016-11-13 19:01 27 ******** 56 2016-11-13 19:02 26 ******* ... ..( 23 skipped). .. ******* 80 2016-11-13 19:26 26 ******* 81 2016-11-13 19:27 27 ******** ... ..( 13 skipped). .. ******** 95 2016-11-13 19:41 27 ******** 96 2016-11-13 19:42 28 ********* ... ..( 14 skipped). .. ********* 111 2016-11-13 19:57 28 ********* 112 2016-11-13 19:58 29 ********** ... ..( 13 skipped). .. ********** 126 2016-11-13 20:12 29 ********** 127 2016-11-13 20:13 30 *********** ... ..( 6 skipped). .. *********** 134 2016-11-13 20:20 30 *********** 135 2016-11-13 20:21 31 ************ ... ..( 28 skipped). .. ************ 164 2016-11-13 20:50 31 ************ 165 2016-11-13 20:51 32 ************* ... ..( 42 skipped). .. ************* 208 2016-11-13 21:34 32 ************* 209 2016-11-13 21:35 31 ************ ... ..( 3 skipped). .. ************ 213 2016-11-13 21:39 31 ************ 214 2016-11-13 21:40 30 *********** ... ..( 3 skipped). .. *********** 218 2016-11-13 21:44 30 *********** 219 2016-11-13 21:45 29 ********** ... ..( 22 skipped). .. ********** 242 2016-11-13 22:08 29 ********** 243 2016-11-13 22:09 30 *********** ... ..( 7 skipped). .. *********** 251 2016-11-13 22:17 30 *********** 252 2016-11-13 22:18 31 ************ ... ..( 2 skipped). .. ************ 255 2016-11-13 22:21 31 ************ 256 2016-11-13 22:22 ? - 257 2016-11-13 22:23 25 ****** 258 2016-11-13 22:24 ? - 259 2016-11-13 22:25 27 ******** ... ..( 4 skipped). .. ******** 264 2016-11-13 22:30 27 ******** 265 2016-11-13 22:31 ? - 266 2016-11-13 22:32 27 ******** ... ..( 5 skipped). .. ******** 272 2016-11-13 22:38 27 ******** 273 2016-11-13 22:39 28 ********* ... ..( 14 skipped). .. ********* 288 2016-11-13 22:54 28 ********* 289 2016-11-13 22:55 ? - 290 2016-11-13 22:56 28 ********* ... ..( 15 skipped). .. ********* 306 2016-11-13 23:12 28 ********* 307 2016-11-13 23:13 29 ********** ... ..( 8 skipped). .. ********** 316 2016-11-13 23:22 29 ********** 317 2016-11-13 23:23 30 *********** ... ..( 12 skipped). .. *********** 330 2016-11-13 23:36 30 *********** 331 2016-11-13 23:37 31 ************ ... ..( 21 skipped). .. ************ 353 2016-11-13 23:59 31 ************ 354 2016-11-14 00:00 ? - 355 2016-11-14 00:01 32 ************* 356 2016-11-14 00:02 31 ************ ... ..( 16 skipped). .. ************ 373 2016-11-14 00:19 31 ************
Warning: device does not support SCT Error Recovery Control command 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 2 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 419 Vendor specific
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Caviar Green (Adv. Format) Device Model: WDC WD30EZRX-00DC0B0 Serial Number: WD-WMC1T3646865 LU WWN Device Id: 5 0014ee 6ae054c3d Firmware Version: 80.00A80 User Capacity: 3,000,592,982,016 bytes [3.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: ACS-2 (revision not indicated) Local Time is: Mon Nov 14 00:17:37 2016 IST SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled ATA Security is: Disabled, NOT FROZEN [SEC1]
=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x84) Offline data collection activity
was suspended by an interrupting command from host. 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: (39540) 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: ( 397) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x70b5) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME 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 177 021 - 5958
4 Start_Stop_Count -O--CK 100 100 000 - 230
5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0
7 Seek_Error_Rate -OSR-K 200 200 000 - 0
9 Power_On_Hours -O--CK 068 068 000 - 23971
10 Spin_Retry_Count -O--CK 100 100 000 - 0
11 Calibration_Retry_Count -O--CK 100 100 000 - 0
12 Power_Cycle_Count -O--CK 100 100 000 - 230
192 Power-Off_Retract_Count -O--CK 200 200 000 - 196
193 Load_Cycle_Count -O--CK 001 001 000 - 670114
194 Temperature_Celsius -O---K 118 102 000 - 32
196 Reallocated_Event_Count -O--CK 200 200 000 - 0
197 Current_Pending_Sector -O--CK 200 200 000 - 0
198 Offline_Uncorrectable ----CK 200 200 000 - 0
199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0
200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 0
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warningGeneral Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
GP/S Log at address 0x00 has 1 sectors [Log Directory] SMART Log at address 0x01 has 1 sectors [Summary SMART error log] SMART Log at address 0x02 has 5 sectors [Comprehensive SMART error log] GP Log at address 0x03 has 6 sectors [Ext. Comprehensive SMART error log] SMART Log at address 0x06 has 1 sectors [SMART self-test log] GP Log at address 0x07 has 1 sectors [Extended self-test log] SMART Log at address 0x09 has 1 sectors [Selective self-test log] GP Log at address 0x10 has 1 sectors [NCQ Command Error log] GP Log at address 0x11 has 1 sectors [SATA Phy Event Counters] GP/S Log at address 0x80 has 16 sectors [Host vendor specific log] GP/S Log at address 0x81 has 16 sectors [Host vendor specific log] GP/S Log at address 0x82 has 16 sectors [Host vendor specific log] GP/S Log at address 0x83 has 16 sectors [Host vendor specific log] GP/S Log at address 0x84 has 16 sectors [Host vendor specific log] GP/S Log at address 0x85 has 16 sectors [Host vendor specific log] GP/S Log at address 0x86 has 16 sectors [Host vendor specific log] GP/S Log at address 0x87 has 16 sectors [Host vendor specific log] GP/S Log at address 0x88 has 16 sectors [Host vendor specific log] GP/S Log at address 0x89 has 16 sectors [Host vendor specific log] GP/S Log at address 0x8a has 16 sectors [Host vendor specific log] GP/S Log at address 0x8b has 16 sectors [Host vendor specific log] GP/S Log at address 0x8c has 16 sectors [Host vendor specific log] GP/S Log at address 0x8d has 16 sectors [Host vendor specific log] GP/S Log at address 0x8e has 16 sectors [Host vendor specific log] GP/S Log at address 0x8f has 16 sectors [Host vendor specific log] GP/S Log at address 0x90 has 16 sectors [Host vendor specific log] GP/S Log at address 0x91 has 16 sectors [Host vendor specific log] GP/S Log at address 0x92 has 16 sectors [Host vendor specific log] GP/S Log at address 0x93 has 16 sectors [Host vendor specific log] GP/S Log at address 0x94 has 16 sectors [Host vendor specific log] GP/S Log at address 0x95 has 16 sectors [Host vendor specific log] GP/S Log at address 0x96 has 16 sectors [Host vendor specific log] GP/S Log at address 0x97 has 16 sectors [Host vendor specific log] GP/S Log at address 0x98 has 16 sectors [Host vendor specific log] GP/S Log at address 0x99 has 16 sectors [Host vendor specific log] GP/S Log at address 0x9a has 16 sectors [Host vendor specific log] GP/S Log at address 0x9b has 16 sectors [Host vendor specific log] GP/S Log at address 0x9c has 16 sectors [Host vendor specific log] GP/S Log at address 0x9d has 16 sectors [Host vendor specific log] GP/S Log at address 0x9e has 16 sectors [Host vendor specific log] GP/S Log at address 0x9f has 16 sectors [Host vendor specific log] GP/S Log at address 0xa0 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa1 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa2 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa3 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa4 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa5 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa6 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa7 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa8 has 1 sectors [Device vendor specific log] GP/S Log at address 0xa9 has 1 sectors [Device vendor specific log] GP/S Log at address 0xaa has 1 sectors [Device vendor specific log] GP/S Log at address 0xab has 1 sectors [Device vendor specific log] GP/S Log at address 0xac has 1 sectors [Device vendor specific log] GP/S Log at address 0xad has 1 sectors [Device vendor specific log] GP/S Log at address 0xae has 1 sectors [Device vendor specific log] GP/S Log at address 0xaf has 1 sectors [Device vendor specific log] GP/S Log at address 0xb0 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb1 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb2 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb3 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb4 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb5 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb6 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb7 has 1 sectors [Device vendor specific log] GP/S Log at address 0xbd has 1 sectors [Device vendor specific log] GP/S Log at address 0xc0 has 1 sectors [Device vendor specific log] GP Log at address 0xc1 has 93 sectors [Device vendor specific log] GP/S Log at address 0xe0 has 1 sectors [SCT Command/Status] GP/S Log at address 0xe1 has 1 sectors [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% 16456 - # 2 Short offline Completed without error 00% 7672 - # 3 Short offline Aborted by host 90% 5719 - # 4 Short offline Completed without error 00% 2 -
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_testingSelective 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: 33 Celsius Power Cycle Min/Max Temperature: 32/33 Celsius Lifetime Min/Max Temperature: 16/49 Celsius Under/Over Temperature Limit Count: 0/0 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 (111)
Index Estimated Time Temperature Celsius
112 2016-11-13 16:20 30 *********** ... ..( 80 skipped). .. *********** 193 2016-11-13 17:41 30 *********** 194 2016-11-13 17:42 31 ************ ... ..( 3 skipped). .. ************ 198 2016-11-13 17:46 31 ************ 199 2016-11-13 17:47 ? - 200 2016-11-13 17:48 32 ************* ... ..( 3 skipped). .. ************* 204 2016-11-13 17:52 32 ************* 205 2016-11-13 17:53 33 ************** 206 2016-11-13 17:54 29 ********** ... ..( 26 skipped). .. ********** 233 2016-11-13 18:21 29 ********** 234 2016-11-13 18:22 30 *********** ... ..( 5 skipped). .. *********** 240 2016-11-13 18:28 30 *********** 241 2016-11-13 18:29 31 ************ ... ..( 2 skipped). .. ************ 244 2016-11-13 18:32 31 ************ 245 2016-11-13 18:33 ? - 246 2016-11-13 18:34 26 ******* 247 2016-11-13 18:35 ? - 248 2016-11-13 18:36 27 ******** ... ..( 4 skipped). .. ******** 253 2016-11-13 18:41 27 ******** 254 2016-11-13 18:42 ? - 255 2016-11-13 18:43 27 ******** ... ..( 8 skipped). .. ******** 264 2016-11-13 18:52 27 ******** 265 2016-11-13 18:53 28 ********* ... ..( 5 skipped). .. ********* 271 2016-11-13 18:59 28 ********* 272 2016-11-13 19:00 29 ********** ... ..( 4 skipped). .. ********** 277 2016-11-13 19:05 29 ********** 278 2016-11-13 19:06 ? - 279 2016-11-13 19:07 29 ********** ... ..( 13 skipped). .. ********** 293 2016-11-13 19:21 29 ********** 294 2016-11-13 19:22 30 *********** ... ..( 6 skipped). .. *********** 301 2016-11-13 19:29 30 *********** 302 2016-11-13 19:30 31 ************ ... ..( 23 skipped). .. ************ 326 2016-11-13 19:54 31 ************ 327 2016-11-13 19:55 32 ************* ... ..( 14 skipped). .. ************* 342 2016-11-13 20:10 32 ************* 343 2016-11-13 20:11 ? - 344 2016-11-13 20:12 33 ************** 345 2016-11-13 20:13 32 ************* ... ..( 6 skipped). .. ************* 352 2016-11-13 20:20 32 ************* 353 2016-11-13 20:21 33 ************** ... ..( 28 skipped). .. ************** 382 2016-11-13 20:50 33 ************** 383 2016-11-13 20:51 34 *************** ... ..(102 skipped). .. *************** 8 2016-11-13 22:34 34 *************** 9 2016-11-13 22:35 33 ************** ... ..( 6 skipped). .. ************** 16 2016-11-13 22:42 33 ************** 17 2016-11-13 22:43 ? - 18 2016-11-13 22:44 25 ****** ... ..( 4 skipped). .. ****** 23 2016-11-13 22:49 25 ****** 24 2016-11-13 22:50 26 ******* 25 2016-11-13 22:51 26 ******* 26 2016-11-13 22:52 27 ******** ... ..( 5 skipped). .. ******** 32 2016-11-13 22:58 27 ******** 33 2016-11-13 22:59 28 ********* ... ..( 11 skipped). .. ********* 45 2016-11-13 23:11 28 ********* 46 2016-11-13 23:12 29 ********** ... ..( 13 skipped). .. ********** 60 2016-11-13 23:26 29 ********** 61 2016-11-13 23:27 30 *********** ... ..( 49 skipped). .. *********** 111 2016-11-14 00:17 30 ***********
Warning: device does not support SCT Error Recovery Control command 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 2 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 328 Vendor specific
Quoted 16 lines · On Tue, Nov 22, 2016 at 9:31 AM, [email protected]…
Hello good people of the linux-raid group,
I really need your help with my RAID1 that has completely failed, on which I have photos of my beloved deceased grandparents.
I had the RAID1 array for about 3 years, and I had replaced one of the drives when it failed about one year ago. All worked fine.
A few weeks ago, I bought a new computer and wanted to move the array to the new computer.
I read several guides, and thought that all I had to do was turn both computers off, move the drives, and in the new computer execute: mdadm --assemble --scan which I did.The output was: mdadm:
/dev/sdbhas no superblock - assembly abortedI panicked, moved the drives back, but the old RAID wouldn't start! The old computer too says that one of the drives has no superblock and, even worse, that the other is UNALLOCATED SPACE!!!
Quoted 9 lines
I don't understand why the partition on the second drive disappeared, and I'm so worried.
PLEASE, PLEASE help me...
I read the wiki pages (raid wiki kernel), but I'm afraid to run any commands that might make things worse.
I would be very happy if I could restore the data from either one of the drives, and copy it to the new drives in my new computer (as I should have done before moving the drives).
Yadiv -
One more piece of information that would be helpful is the partition tables for each drive:
# fdisk -l /dev/sdb /dev/sdc
Signature · 3 lines
George Rapp (Pataskala, OH) Home: george.rapp -- at -- gmail.com LinkedIn profile: https://www.linkedin.com/in/georgerapp Phone: +1 740 936 RAPP (740 936 7277)
Quoted 28 lines · George Rapp
Quoted 16 lines · On Tue, Nov 22, 2016 at 9:31 AM, [email protected]…
Hello good people of the linux-raid group,
I really need your help with my RAID1 that has completely failed, on which I have photos of my beloved deceased grandparents.
I had the RAID1 array for about 3 years, and I had replaced one of the drives when it failed about one year ago. All worked fine.
A few weeks ago, I bought a new computer and wanted to move the array to the new computer.
I read several guides, and thought that all I had to do was turn both computers off, move the drives, and in the new computer execute: mdadm --assemble --scan which I did.The output was: mdadm:
/dev/sdbhas no superblock - assembly abortedI panicked, moved the drives back, but the old RAID wouldn't start! The old computer too says that one of the drives has no superblock and, even worse, that the other is UNALLOCATED SPACE!!!
Quoted 9 lines
I don't understand why the partition on the second drive disappeared, and I'm so worried.
PLEASE, PLEASE help me...
I read the wiki pages (raid wiki kernel), but I'm afraid to run any commands that might make things worse.
I would be very happy if I could restore the data from either one of the drives, and copy it to the new drives in my new computer (as I should have done before moving the drives).
Quoted 7 lines
Yadiv -
One more piece of information that would be helpful is the partition tables for each drive:
# fdisk -l /dev/sdb /dev/sdc
And search the archive for the following thread - "RAID10 with 2 drives auto-assembled as RAID1". It's pretty recent.
You've got a mirror, which means both of your drives should have a valid filesystem on them, so things look optimistic. It's just a case of finding it - that thread should help you look. The experts will chime in, but if you can find the string sequences they're looking for, it'll help you recover the partition(s). What filesystem were you using?
Cheers,
Wol
Quoted 4 lines · y k
Thank you for the quick response,
Attached are the outputs of fdisk -l for both drives.
Quoted 8 lines
I read all the correspondence in the archived email thread "RAID10 with 2 drives
auto-assembled as RAID1",
but I don't understand what I should do.Could you please guide me?
I'm afraid to execute any unfamiliar commands that might lower my chances of saving my data.
Basically, you need to run hexdump, and look for evidence of a damaged superblock, and/or a filesystem superblock.
Hexdump will only read a disk, not do anything to it. That thread should tell you what strings to look for to locate any superblocks, which are probably on a 4K boundary.
If you find them, the other experts will be able, hopefully, to tell you how to get the array back. What should happen is mdadm looks at the disk for the partition table, then looks at the partitions for an array superblock, then passes the array to linux to be mounted. Obviously, something in that chain has been broken, and unfortunately you now have to do that manually. Hexdump is your tool to examine the disk and look for the information that linux should have found for you automatically.
In the next few days, I'm planning to add a page to the wiki explaining how to use hexdump and find this information.
Quoted 59 lines
Thank you so much!
Yaniv
On Tue, Nov 22, 2016 at 5:05 PM, Wols Lists <[email protected] <mailto:[email protected]>> wrote:
On 22/11/16 14:49, George Rapp wrote:
> On Tue, Nov 22, 2016 at 9:31 AM, [email protected] <mailto:[email protected]>
> <[email protected]
<mailto:[email protected]>> wrote:
>> Hello good people of the linux-raid group,
>>
>> I really need your help with my RAID1 that has completely failed, on which I have photos of my beloved deceased grandparents.
>>
>> I had the RAID1 array for about 3 years, and I had replaced one of the drives when it failed about one year ago. All worked fine. >>
>> A few weeks ago, I bought a new computer and wanted to move the array to the new computer.
>> I read several guides, and thought that all I had to do was turn both computers off, move the drives, and in the new computer execute: mdadm --assemble --scan >> which I did.
>>
>> The output was: mdadm:/dev/sdbhas no superblock - assembly aborted
>>
>> I panicked, moved the drives back, but the old RAID wouldn't start!
>> The old computer too says that one of the drives has no superblock
>> and, even worse, that the other is UNALLOCATED SPACE!!!
>>
>> I don't understand why the partition on the second drive disappeared, and I'm so worried.
>>
>> PLEASE, PLEASE help me...
>>
>> I read the wiki pages (raid wiki kernel), but I'm afraid to run any commands that might make things worse.
>>
>> I would be very happy if I could restore the data from either one of the drives,
>> and copy it to the new drives in my new computer (as I should have done before moving the drives).
>>
>
> Yadiv -
>
> One more piece of information that would be helpful is the partition
> tables for each drive:
>
> # fdisk -l/dev/sdb/dev/sdc
>And search the archive for the following thread - "RAID10 with 2 drives auto-assembled as RAID1". It's pretty recent.
You've got a mirror, which means both of your drives should have a valid filesystem on them, so things look optimistic. It's just a case of finding it - that thread should help you look. The experts will chime in, but if you can find the string sequences they're looking for, it'll help you recover the partition(s). What filesystem were you using?
Cheers,
Wol
Quoted 5 lines · Wols Lists
Basically, you need to run hexdump, and look for evidence of a damaged superblock, and/or a filesystem superblock.
That thread should tell you what strings to look for to locate any superblocks, which are probably on a 4K boundary.
Thank you for the explanation.
How do I tell the difference between a filesystem superblock and a damanged one in the hexdump output?
I found in stackexchange instructions to look for "magic number 0x53EF", which I then realized was searched by the egrep command in the other thread you mentioned.
Quoted 2 lines
If you find them, the other experts will be able, hopefully, to tell you how to get the array back
I do see "53 ef" in the fifth line of the output for my sdb1 hexdump !
I'll greatly appreciate it if someone could instruct me in how to mount my sdb1 partition.
I see in some guide online, that one could mount a lost partition with a command like:
mount /dev/sdd -o ro,offset=2097152 /mnt/test/
How did they calculate that offset number?
And is there anything else I should do to recover the partition before or after mount?
I have a new HDD to which I could copy all the data, if I manage to mount the partition. So, I could create a new array on the old drives, and then copy the data back.