Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 28

Thread: Recover data from NAS HD

  1. #11
    Join Date
    Jun 2008
    Beans
    23

    Re: Recover data from NAS HD

    As I told you, I do not own a desktop. I will have to borrow that computer from someone to use it for a couple of hours. Having said that, what else I will need to run on the desktop? Thanks

  2. #12
    Join Date
    Feb 2007
    Location
    West Hills CA
    Beans
    10,046
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Recover data from NAS HD

    As long as you have a wired, ethernet connection to the computer, you should be able to boot the LiveUSB stick, install smartmontools run the command to get the SMART parameters. You need to determine what is causing both hard drives to fail before you can start a recovery process.

    Some reading: https://help.ubuntu.com/community/DataRecovery

    In theory, you should be able to find a near-matching 2TB drive, put it in your NAS, now with 2 matching disk drives, and let the NAS rebuild the RAID1 pool. If this is successful, then you have access to your data, and a short-term backup, until you move your data to another medium.
    -------------------------------------
    Oooh Shiny: PopularPages

    Unumquodque potest reparantur. Patientia sit virtus.

  3. #13
    Join Date
    Jun 2008
    Beans
    23

    Re: Recover data from NAS HD

    Hi - I borrow a desktop pc from good friend of mine (thanks Cassio!!!) and was finally able to run the smartctl command as requested. Please find below the output

    Code:
    smartctl 6.4 2014-10-07 r4002 [x86_64-linux-4.2.0-16-generic] (local build)
    Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
    
    === START OF INFORMATION SECTION ===
    Model Family:     Western Digital Caviar Green (AF)
    Device Model:     WDC WD20EARS-00MVWB0
    Serial Number:    WD-WCAZA6352649
    LU WWN Device Id: 5 0014ee 25b100d33
    Firmware Version: 51.0AB51
    User Capacity:    2,000,398,934,016 bytes [2.00 TB]
    Sector Size:      512 bytes logical/physical
    Device is:        In smartctl database [for details use: -P show]
    ATA Version is:   ATA8-ACS (minor revision not indicated)
    SATA Version is:  SATA 2.6, 1.5 Gb/s
    Local Time is:    Tue Dec  8 01:39:40 2015 UTC
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled
    
    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED
    
    General SMART Values:
    Offline data collection status:  (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: 		(35460) 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: 	 ( 342) minutes.
    Conveyance self-test routine
    recommended polling time: 	 (   5) minutes.
    SCT capabilities: 	       (0x3035)	SCT Status supported.
    					SCT Feature Control supported.
    					SCT Data Table supported.
    
    SMART Attributes Data Structure revision number: 16
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
      1 Raw_Read_Error_Rate     0x002f   194   194   051    Pre-fail  Always       -       3201
      3 Spin_Up_Time            0x0027   253   164   021    Pre-fail  Always       -       941
      4 Start_Stop_Count        0x0032   091   091   000    Old_age   Always       -       9385
      5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
      7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
      9 Power_On_Hours          0x0032   066   066   000    Old_age   Always       -       25107
     10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
     11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
     12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       332
    192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       175
    193 Load_Cycle_Count        0x0032   009   009   000    Old_age   Always       -       574030
    194 Temperature_Celsius     0x0022   113   075   000    Old_age   Always       -       37
    196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
    197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       19
    198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       1
    199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
    200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       4
    
    SMART Error Log Version: 1
    ATA Error Count: 483 (device log contains only the most recent five errors)
    	CR = Command Register [HEX]
    	FR = Features Register [HEX]
    	SC = Sector Count Register [HEX]
    	SN = Sector Number Register [HEX]
    	CL = Cylinder Low Register [HEX]
    	CH = Cylinder High Register [HEX]
    	DH = Device/Head Register [HEX]
    	DC = Device Command Register [HEX]
    	ER = Error register [HEX]
    	ST = Status register [HEX]
    Powered_Up_Time is measured from power on, and printed as
    DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
    SS=sec, and sss=millisec. It "wraps" after 49.710 days.
    
    Error 483 occurred at disk power-on lifetime: 25103 hours (1045 days + 23 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      40 51 08 c0 ca 3c e0  Error: UNC 8 sectors at LBA = 0x003ccac0 = 3984064
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      c8 00 08 c0 ca 3c e0 00      00:49:10.711  READ DMA
      ec 00 00 00 00 00 e0 00      00:49:08.043  IDENTIFY DEVICE
      ef 03 46 00 00 00 a0 00      00:49:08.033  SET FEATURES [Set transfer mode]
    
    Error 482 occurred at disk power-on lifetime: 25103 hours (1045 days + 23 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      40 51 08 c0 ca 3c e0  Error: UNC 8 sectors at LBA = 0x003ccac0 = 3984064
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      c8 00 08 c0 ca 3c e0 00      00:48:35.729  READ DMA
      ec 00 00 00 00 00 e0 00      00:48:32.975  IDENTIFY DEVICE
      ef 03 46 00 00 00 a0 00      00:48:32.962  SET FEATURES [Set transfer mode]
    
    Error 481 occurred at disk power-on lifetime: 25103 hours (1045 days + 23 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      40 51 08 c0 ca 3c e0  Error: UNC 8 sectors at LBA = 0x003ccac0 = 3984064
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      c8 00 08 c0 ca 3c e0 00      00:47:59.800  READ DMA
      ec 00 00 00 00 00 e0 00      00:47:57.122  IDENTIFY DEVICE
      ef 03 46 00 00 00 a0 00      00:47:57.122  SET FEATURES [Set transfer mode]
    
    Error 480 occurred at disk power-on lifetime: 25103 hours (1045 days + 23 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      40 51 08 c0 ca 3c e0  Error: UNC 8 sectors at LBA = 0x003ccac0 = 3984064
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      c8 00 08 c0 ca 3c e0 00      00:47:24.553  READ DMA
    
    Error 479 occurred at disk power-on lifetime: 25103 hours (1045 days + 23 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      40 51 08 40 7b 39 e0  Error: UNC 8 sectors at LBA = 0x00397b40 = 3767104
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      c8 00 08 40 7b 39 e0 00      00:46:19.839  READ DMA
      ec 00 00 00 00 00 e0 00      00:46:19.814  IDENTIFY DEVICE
      ef 03 46 00 00 00 a0 00      00:46:19.795  SET FEATURES [Set transfer mode]
    
    SMART Self-test log structure revision number 1
    No self-tests have been logged.  [To run self-tests, use: smartctl -t]
    
    SMART Selective self-test log data structure revision number 1
     SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
        1        0        0  Not_testing
        2        0        0  Not_testing
        3        0        0  Not_testing
        4        0        0  Not_testing
        5        0        0  Not_testing
    Selective self-test flags (0x0):
      After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute delay.
    I ran some additional commands too:
    Code:
    Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: gpt
    Disk identifier: 45A11E44-7BEE-40FA-AF61-C0D4CA0654D0
    
    Device       Start        End    Sectors   Size Type
    /dev/sda1    64320    3984191    3919872   1.9G Linux RAID
    /dev/sda2  3984192    4498175     513984   251M Linux RAID
    /dev/sda3  4498176    6474175    1976000 964.9M Linux RAID
    /dev/sda4  6474176 3907029134 3900554959   1.8T Linux RAID
    
    ubuntu@ubuntu:~$ sudo mount /dev/md0 /mnt
    mount: special device /dev/md0 does not exist
    ubuntu@ubuntu:~$ sudo mount /dev/sda /mnt
    mount: wrong fs type, bad option, bad superblock on /dev/sda,
           missing codepage or helper program, or other error
    
           In some cases useful info is found in syslog - try
           dmesg | tail or so.
    ubuntu@ubuntu:~$ dmesg | tail -n 100
    [   60.699395] ata1.00: status: { DRDY ERR }
    [   60.699397] ata1.00: error: { UNC }
    [   60.708547] ata1.00: configured for UDMA/133
    [   60.708563] sd 0:0:0:0: [sda] tag#25 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [   60.708568] sd 0:0:0:0: [sda] tag#25 Sense Key : Medium Error [current] [descriptor] 
    [   60.708571] sd 0:0:0:0: [sda] tag#25 Add. Sense: Unrecovered read error - auto reallocate failed
    [   60.708576] sd 0:0:0:0: [sda] tag#25 CDB: Read(10) 28 00 00 3c cb 40 00 01 00 00
    [   60.708578] blk_update_request: I/O error, dev sda, sector 3984200
    [   60.708597] ata1: EH complete
    [   63.496075] ata1.00: exception Emask 0x0 SAct 0x83 SErr 0x0 action 0x0
    [   63.496080] ata1.00: irq_stat 0x40000008
    [   63.496083] ata1.00: failed command: READ FPDMA QUEUED
    [   63.496089] ata1.00: cmd 60/08:38:40:cb:3c/00:00:00:00:00/40 tag 7 ncq 4096 in
                            res 41/40:00:40:cb:3c/00:00:00:00:00/40 Emask 0x409 (media error) <F>
    [   63.496092] ata1.00: status: { DRDY ERR }
    [   63.496094] ata1.00: error: { UNC }
    [   63.506084] ata1.00: configured for UDMA/133
    [   63.506101] sd 0:0:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [   63.506105] sd 0:0:0:0: [sda] tag#7 Sense Key : Medium Error [current] [descriptor] 
    [   63.506109] sd 0:0:0:0: [sda] tag#7 Add. Sense: Unrecovered read error - auto reallocate failed
    [   63.506113] sd 0:0:0:0: [sda] tag#7 CDB: Read(10) 28 00 00 3c cb 40 00 00 08 00
    [   63.506115] blk_update_request: I/O error, dev sda, sector 3984192
    [   63.506119] Buffer I/O error on dev sda2, logical block 0, async page read
    [   63.506130] ata1: EH complete
    [   63.746160] cgroup: new mount options do not match the existing superblock, will be ignored
    [   64.961224] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready
    [   65.160352] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready
    [   66.709432] e1000e: enp0s25 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
    [   66.709541] e1000e 0000:00:19.0 enp0s25: 10/100 speed: disabling TSO
    [   66.709576] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s25: link becomes ready
    [  181.370324] ata1.00: exception Emask 0x0 SAct 0x20 SErr 0x0 action 0x0
    [  181.370330] ata1.00: irq_stat 0x40000008
    [  181.370334] ata1.00: failed command: READ FPDMA QUEUED
    [  181.370340] ata1.00: cmd 60/08:28:40:cb:3c/00:00:00:00:00/40 tag 5 ncq 4096 in
                            res 41/40:00:40:cb:3c/00:00:00:00:00/40 Emask 0x409 (media error) <F>
    [  181.370343] ata1.00: status: { DRDY ERR }
    [  181.370346] ata1.00: error: { UNC }
    [  181.378726] ata1.00: configured for UDMA/133
    [  181.378740] sd 0:0:0:0: [sda] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [  181.378745] sd 0:0:0:0: [sda] tag#5 Sense Key : Medium Error [current] [descriptor] 
    [  181.378749] sd 0:0:0:0: [sda] tag#5 Add. Sense: Unrecovered read error - auto reallocate failed
    [  181.378753] sd 0:0:0:0: [sda] tag#5 CDB: Read(10) 28 00 00 3c cb 40 00 00 08 00
    [  181.378756] blk_update_request: I/O error, dev sda, sector 3984192
    [  181.378769] ata1: EH complete
    [  184.875317] ata1.00: exception Emask 0x0 SAct 0x2000000 SErr 0x0 action 0x0
    [  184.875321] ata1.00: irq_stat 0x40000008
    [  184.875325] ata1.00: failed command: READ FPDMA QUEUED
    [  184.875331] ata1.00: cmd 60/08:c8:30:cb:3c/00:00:00:00:00/40 tag 25 ncq 4096 in
                            res 41/40:00:30:cb:3c/00:00:00:00:00/40 Emask 0x409 (media error) <F>
    [  184.875334] ata1.00: status: { DRDY ERR }
    [  184.875337] ata1.00: error: { UNC }
    [  184.884796] ata1.00: configured for UDMA/133
    [  184.884808] sd 0:0:0:0: [sda] tag#25 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [  184.884812] sd 0:0:0:0: [sda] tag#25 Sense Key : Medium Error [current] [descriptor] 
    [  184.884816] sd 0:0:0:0: [sda] tag#25 Add. Sense: Unrecovered read error - auto reallocate failed
    [  184.884820] sd 0:0:0:0: [sda] tag#25 CDB: Read(10) 28 00 00 3c cb 30 00 00 08 00
    [  184.884822] blk_update_request: I/O error, dev sda, sector 3984176
    [  184.884834] ata1: EH complete
    [  187.660008] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
    [  187.660013] ata1.00: irq_stat 0x40000008
    [  187.660016] ata1.00: failed command: READ FPDMA QUEUED
    [  187.660022] ata1.00: cmd 60/01:00:3f:cb:3c/00:00:00:00:00/40 tag 0 ncq 512 in
                            res 41/40:00:3f:cb:3c/00:00:00:00:00/40 Emask 0x409 (media error) <F>
    [  187.660025] ata1.00: status: { DRDY ERR }
    [  187.660027] ata1.00: error: { UNC }
    [  187.669404] ata1.00: configured for UDMA/133
    [  187.669416] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [  187.669421] sd 0:0:0:0: [sda] tag#0 Sense Key : Medium Error [current] [descriptor] 
    [  187.669424] sd 0:0:0:0: [sda] tag#0 Add. Sense: Unrecovered read error - auto reallocate failed
    [  187.669428] sd 0:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 3c cb 3f 00 00 01 00
    [  187.669431] blk_update_request: I/O error, dev sda, sector 3984191
    [  187.669444] ata1: EH complete
    [  190.444774] ata1.00: exception Emask 0x0 SAct 0x40000 SErr 0x0 action 0x0
    [  190.444779] ata1.00: irq_stat 0x40000008
    [  190.444782] ata1.00: failed command: READ FPDMA QUEUED
    [  190.444789] ata1.00: cmd 60/01:90:3e:cb:3c/00:00:00:00:00/40 tag 18 ncq 512 in
                            res 41/40:00:3e:cb:3c/00:00:00:00:00/40 Emask 0x409 (media error) <F>
    [  190.444792] ata1.00: status: { DRDY ERR }
    [  190.444794] ata1.00: error: { UNC }
    [  190.454920] ata1.00: configured for UDMA/133
    [  190.454932] sd 0:0:0:0: [sda] tag#18 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [  190.454937] sd 0:0:0:0: [sda] tag#18 Sense Key : Medium Error [current] [descriptor] 
    [  190.454940] sd 0:0:0:0: [sda] tag#18 Add. Sense: Unrecovered read error - auto reallocate failed
    [  190.454944] sd 0:0:0:0: [sda] tag#18 CDB: Read(10) 28 00 00 3c cb 3e 00 00 01 00
    [  190.454947] blk_update_request: I/O error, dev sda, sector 3984190
    [  190.454959] ata1: EH complete
    [  193.217853] ata1.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x0
    [  193.217857] ata1.00: irq_stat 0x40000008
    [  193.217861] ata1.00: failed command: READ FPDMA QUEUED
    [  193.217867] ata1.00: cmd 60/08:08:c0:ca:3c/00:00:00:00:00/40 tag 1 ncq 4096 in
                            res 41/40:00:c0:ca:3c/00:00:00:00:00/40 Emask 0x409 (media error) <F>
    [  193.217870] ata1.00: status: { DRDY ERR }
    [  193.217872] ata1.00: error: { UNC }
    [  193.227425] ata1.00: configured for UDMA/133
    [  193.227437] sd 0:0:0:0: [sda] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [  193.227442] sd 0:0:0:0: [sda] tag#1 Sense Key : Medium Error [current] [descriptor] 
    [  193.227445] sd 0:0:0:0: [sda] tag#1 Add. Sense: Unrecovered read error - auto reallocate failed
    [  193.227449] sd 0:0:0:0: [sda] tag#1 CDB: Read(10) 28 00 00 3c ca c0 00 00 08 00
    [  193.227452] blk_update_request: I/O error, dev sda, sector 3984064
    [  193.227465] ata1: EH complete



    What shall I do next?
    Last edited by gilsonsjc; December 8th, 2015 at 11:49 AM.

  4. #14
    Join Date
    Apr 2012
    Beans
    7,256

    Re: Recover data from NAS HD

    Just FYI, the WD Greens are not recommended for RAID because the 'Idle 3' Intellipark feature can cause excessive load cycle counts. Just something to be aware of when you're shopping for the replacement drives.

  5. #15
    Join Date
    Feb 2007
    Location
    West Hills CA
    Beans
    10,046
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Recover data from NAS HD

    Yes, and I assume that you bought the NAS enclosure without disks and put your own disks in it. Green disks generally are not suitable for RAID service.

    So you have 25K hours on this drive. Most consumer drives are rated to 30k hours. You have 547K load cycles. Most consumer drives are rated to 600K. So your drive is nearing the end of its life from a design standpoint. You have 8 uncorrectable sectors. This is not bad for the drive's age, and if this number increases linearly with time, then it's time to replace the drive. You have had 19 relocation events, meaning the drive's firmware has attempted to move data from the bad sectors to reserve sectors 19 times. So your drive has passed, but it is starting to have issues.

    What are the SMART parameters for the second 2TB disk drive?

    The dmesg output is troubling. The kernel really wants to read those bad sectors.
    -------------------------------------
    Oooh Shiny: PopularPages

    Unumquodque potest reparantur. Patientia sit virtus.

  6. #16
    Join Date
    Jun 2008
    Beans
    23

    Re: Recover data from NAS HD

    Quote Originally Posted by steeldriver View Post
    Just FYI, the WD Greens are not recommended for RAID because the 'Idle 3' Intellipark feature can cause excessive load cycle counts. Just something to be aware of when you're shopping for the replacement drives.
    I wish I knew that sooner. I bought 2x5TB WD Green HDs which are currently running in the same NAS in RAID 1.

    Quote Originally Posted by tgalati4 View Post
    Yes, and I assume that you bought the NAS enclosure without disks and put your own disks in it. Green disks generally are not suitable for RAID service.

    So you have 25K hours on this drive. Most consumer drives are rated to 30k hours. You have 547K load cycles. Most consumer drives are rated to 600K. So your drive is nearing the end of its life from a design standpoint. You have 8 uncorrectable sectors. This is not bad for the drive's age, and if this number increases linearly with time, then it's time to replace the drive. You have had 19 relocation events, meaning the drive's firmware has attempted to move data from the bad sectors to reserve sectors 19 times. So your drive has passed, but it is starting to have issues.

    What are the SMART parameters for the second 2TB disk drive?

    The dmesg output is troubling. The kernel really wants to read those bad sectors.
    I actually bought the NAS with the disks on it already. Weeks ago I bought the replacement disk myself. Following WD's recommendation, I got 2x5tb green disks WD to run in raid 1 in the same NAS (MBWE II Whitelights). I wish I had known they were not good for RAID 1 before.

    I connected the other drive to the computer (the one that failed) as you recommended. Please find below the information about it:


    Code:
    Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    
    ubuntu@ubuntu:~$ sudo smartctl -a /dev/sdb
    smartctl 6.4 2014-10-07 r4002 [x86_64-linux-4.2.0-16-generic] (local build)
    Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
    
    === START OF INFORMATION SECTION ===
    Model Family:     Western Digital Caviar Green (AF)
    Device Model:     WDC WD20EARS-00MVWB0
    Serial Number:    WD-WCAZA6328687
    LU WWN Device Id: 5 0014ee 25b0ffdec
    Firmware Version: 51.0AB51
    User Capacity:    2,000,398,934,016 bytes [2.00 TB]
    Sector Size:      512 bytes logical/physical
    Device is:        In smartctl database [for details use: -P show]
    ATA Version is:   ATA8-ACS (minor revision not indicated)
    SATA Version is:  SATA 2.6, 1.5 Gb/s
    Local Time is:    Tue Dec  8 08:42:49 2015 UTC
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled
    
    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED
    
    General SMART Values:
    Offline data collection status:  (0x82)	Offline data collection activity
    					was completed without error.
    					Auto Offline Data Collection: Enabled.
    Self-test execution status:      (   0)	The previous self-test routine completed
    					without error or no self-test has ever 
    					been run.
    Total time to complete Offline 
    data collection: 		(35760) 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: 	 ( 345) minutes.
    Conveyance self-test routine
    recommended polling time: 	 (   5) minutes.
    SCT capabilities: 	       (0x3035)	SCT Status supported.
    					SCT Feature Control supported.
    					SCT Data Table supported.
    
    SMART Attributes Data Structure revision number: 16
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
      1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
      3 Spin_Up_Time            0x0027   239   166   021    Pre-fail  Always       -       3016
      4 Start_Stop_Count        0x0032   091   091   000    Old_age   Always       -       9331
      5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
      7 Seek_Error_Rate         0x002e   100   253   000    Old_age   Always       -       0
      9 Power_On_Hours          0x0032   066   066   000    Old_age   Always       -       25103
     10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
     11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
     12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       306
    192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       140
    193 Load_Cycle_Count        0x0032   001   001   000    Old_age   Always       -       625927
    194 Temperature_Celsius     0x0022   121   075   000    Old_age   Always       -       29
    196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
    197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
    198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       0
    199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
    200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0
    
    SMART Error Log Version: 1
    No Errors Logged
    
    SMART Self-test log structure revision number 1
    No self-tests have been logged.  [To run self-tests, use: smartctl -t]
    
    SMART Selective self-test log data structure revision number 1
     SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
        1        0        0  Not_testing
        2        0        0  Not_testing
        3        0        0  Not_testing
        4        0        0  Not_testing
        5        0        0  Not_testing
    Selective self-test flags (0x0):
      After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute delay.
    What should I do next?

    Thank you!
    Last edited by howefield; December 8th, 2015 at 04:33 PM.

  7. #17
    Join Date
    Apr 2012
    Beans
    7,256

    Re: Recover data from NAS HD

    Quote Originally Posted by gilsonsjc View Post
    I wish I knew that sooner. I bought 2x5TB WD Green HDs which are currently running in the same NAS in RAID 1.
    Well FWIW I run a RAID1 setup with a pair of WD20EARX Greens, however I used idle3-tools to disable the IntelliPark feature on them (there may be better ways now. I haven't checked recently)

    http://idle3-tools.sourceforge.net/

    They are currently showing LCCs of 22587 and 28833 respectively after a little over 30,000 power-on hrs (the asymmetry is due to having a small /var partition on one I think: the RAID arrays don't use the whole disk)

  8. #18
    Join Date
    Feb 2007
    Location
    West Hills CA
    Beans
    10,046
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Recover data from NAS HD

    The disk that failed, actually looks in better shape than the working disk. So take a Sharpie and mark the drives as Drive 0 and Drive 1 and assume that they are both mechanically working. Take another two 2 TB drives and use dd to copy the data from Drive 0 to a fresh disk and Drive 1 to a fresh disk. Mark them as Drive 0 New and Drive 1 New. Put those in your NAS and try to mount. After copying, put Drive 0 and Drive 1 in a safe place. Do no further operations with them. Do no further operations with them.

    You will now attempt to recover data from the copies that you have made, Drive 0 New and Drive 1 New.

    Since it is a Western Digital MyBook NAS, it makes sense that it would have WD drives. Green drives are consumer-grade drives. After going through the Agony Units of data recovery, your opinion of Green drives may change.

    Are you running the latest firmware on the NAS?

    Some reading: http://mybookworld.wikidot.com/forum...ion-nas-device

    The most important step is working on copies of your original drives. Any further operations on your original drives puts your data at risk.

    I don't have a MyBook, but my quick web search confirms that recovery is automatic as long as you one good RAID1 drive and one good, matching blank drive. I would assume that you should be able to mount the NAS to at least access your data with one good RAID1. So, now I have to assume that you have other problems, like both drives are scrambled, or the NAS power supply is weak, or the NAS hardware is failing.
    Last edited by tgalati4; December 8th, 2015 at 03:21 PM.
    -------------------------------------
    Oooh Shiny: PopularPages

    Unumquodque potest reparantur. Patientia sit virtus.

  9. #19
    Join Date
    Jun 2008
    Beans
    23

    RE: Recover data from NAS HD

    so it looks like I just need to run the following command in order to disable it?
    Code:
    idle3ctl -d /dev/sda
    Does it void the warranty?

    Quote Originally Posted by tgalati4 View Post
    The disk that failed, actually looks in better shape than the working disk. So take a Sharpie and mark the drives as Drive 0 and Drive 1 and assume that they are both mechanically working. Take another two 2 TB drives and use dd to copy the data from Drive 0 to a fresh disk and Drive 1 to a fresh disk. Mark them as Drive 0 New and Drive 1 New. Put those in your NAS and try to mount. After copying, put Drive 0 and Drive 1 in a safe place. Do no further operations with them. Do no further operations with them.

    You will now attempt to recover data from the copies that you have made, Drive 0 New and Drive 1 New.

    Since it is a Western Digital MyBook NAS, it makes sense that it would have WD drives. Green drives are consumer-grade drives. After going through the Agony Units of data recovery, your opinion of Green drives may change.

    Are you running the latest firmware on the NAS?

    Some reading: http://mybookworld.wikidot.com/forum...ion-nas-device

    The most important step is working on copies of your original drives. Any further operations on your original drives puts your data at risk.

    I don't have a MyBook, but my quick web search confirms that recovery is automatic as long as you one good RAID1 drive and one good, matching blank drive. I would assume that you should be able to mount the NAS to at least access your data with one good RAID1. So, now I have to assume that you have other problems, like both drives are scrambled, or the NAS power supply is weak, or the NAS hardware is failing.
    Hey tgalati4, here is what I have here:
    1) NAS with brand new 2x5TB disks running on RAID 1 - since it is brand new without any data on it I can remove them from the NAS and use it them if needed.
    2) 2x2TB disks (Drive 0 and/or Drive 1) that used to run on the same NAS in #1 on RAID 1. I tried to clean the disks that have failed (lets brand it as "Drive 0") using the clean disk option in the NAS Web GUI, I guess that option has formatted the disk. However it continued failing.
    3) 1 Sata to USB enclosure
    4) 1 PC with 2 SATA ports running Ubuntu from USB, temporarily borrowed from a good friend.

    I can't get another disks due to budget issues. Is there any way to work only what I have here do recovery the data from Drive 1 and/or Drive 0?

    I am running the latest firmware from WD and it is working just fine with the new 2x5tb disks.

    I also have a thread opened on that forum, let me read that link to see what if I can get anything.

    My NAS does not work with neither Disk 0 or Disk 1 mounted, either together or separately one at a time.
    Last edited by howefield; December 8th, 2015 at 04:33 PM.

  10. #20
    Join Date
    Feb 2007
    Location
    West Hills CA
    Beans
    10,046
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Recover data from NAS HD

    Some more tips: http://iknowsomething.com/how-to-fix...rand-new-disk/

    Sometimes disks with 30K hours get sticky spindles, run hotter, and take more power. So, purchase a new power supply, and see if the disks spin up properly. It's possible the new 5TB disks spin easier (they are new after all).

    One way to copy two disks:

    Code:
    sudo cp /dev/sda /dev/sdb
    So you could simply copy the 2 TB drive to the 5 TB drive and then use parted to fix the partitions. You could simply mark the remaining 3 TB space as a separate, blank partition. Mark the unit Drive 0 New. Put that in the NAS, by itself, and see if it mounts and if you can see your data. Don't put the second disk in it. Set the NAS to JBOD mode.

    I don't know what the "Clean Disk Option" mode does from the web panel. If you did wipe the disk, then data recovery is difficult. Use testdisk and photorec to attempt to recover data. You can use your second 5 TB drive to receive the recovered files.
    -------------------------------------
    Oooh Shiny: PopularPages

    Unumquodque potest reparantur. Patientia sit virtus.

Page 2 of 3 FirstFirst 123 LastLast

Bookmarks

Posting Permissions

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