Page 1 of 3 123 LastLast
Results 1 to 10 of 28

Thread: Recover data from NAS HD

  1. #1
    Join Date
    Jun 2008
    Beans
    23

    Recover data from NAS HD

    Hi everybody

    One of my NAS' 2TB HD failed. I have the NAS set up as raid 1. I removed both HDs (the bad one and the good one) and added new and bigger HDs. Now, I need to recover the data from the old-good HD so that I can upload to the NAS again.

    I have one external HD enclosure, one Macbok air and a Ubuntu VM on vmware fusion.

    One of the things I did in order to identify one of my old HDs was failing was to run the commands on the page http://mybookworld.wikidot.com/myboo...sx-and-windows against the good-old HD with the option to NOT to destroy the data

    Here I some information I could gather so far

    Code:
    $sudo fdisk -l
    
    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
    Code:
    $ sudo mdadm --examine /dev/sdb
    mdadm: No md superblock detected on /dev/sdb.
    What should I do in order to recover the data?

    Thanks
    Gilson

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

    Re: Recover data from NAS HD

    Welcome to the forums. What was the model of the NAS? If your NAS used a hardware RAID1 to control the disk drives, then you need to find an identical NAS enclosure, put in an identical-sized replacement drive, and rebuild the RAID1 pool on the NAS, then transfer the data. If your original NAS enclosure is working with the larger drives, then take them out and put in your original 2TB drive, and find an identical replacement drive. The NAS should automatically rebuild the pool. Let that happen, and it will take time.

    Once the pool has been recreated, start your backup process. Don't try to backup and recreate the pool at the same time--too much risk of a 2nd hard drive failure.
    -------------------------------------
    Oooh Shiny: PopularPages

    Unumquodque potest reparantur. Patientia sit virtus.

  3. #3
    Join Date
    Jun 2008
    Beans
    23

    Re: Recover data from NAS HD

    The NAS is one Western Digital My Book World Edition II Whitelights. It is currently running 2 new HDs of 5 TB each. Since I have only thing enclosure, I will try to remove the current drives and insert the old one whit the data as you recommended to test.

    I will let you know if that worked.

    Thanks.

    It turns out I was working on the drive that failed. Here is the drive I am trying to mount to recovery the data and what I have tried to far:

    $ sudo fdisk -l
    Code:
    Disk /dev/sdc: 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/sdc1    64320    3984191    3919872   1.9G Linux RAID
    /dev/sdc2  3984192    4498175     513984   251M Linux RAID
    /dev/sdc3  4498176    6474175    1976000 964.9M Linux RAID
    /dev/sdc4  6474176 3907029134 3900554959   1.8T Linux RAID
    $ sudo mount /dev/md0 /mnt
    Code:
    $ sudo mount /dev/md0 /mnt
    mount: wrong fs type, bad option, bad superblock on /dev/loop0,
           missing codepage or helper program, or other error
    
           In some cases useful info is found in syslog - try
           dmesg | tail or so.

    $ dmesg | tail -n 100
    Code:
    [   97.590495] sd 33:0:0:0: Attached scsi generic sg2 type 0
    [   97.602615] sd 33:0:0:0: [sdb] Spinning up disk...
    [  105.379014] .ready
    [  105.381670] sd 33:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
    [  105.385490] sd 33:0:0:0: [sdb] Write Protect is off
    [  105.385497] sd 33:0:0:0: [sdb] Mode Sense: 10 00 00 00
    [  105.387682] sd 33:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [  105.415475] sd 33:0:0:0: [sdb] Attached SCSI disk
    [  215.652022] EXT4-fs (loop0): mounting ext3 file system using the ext4 subsystem
    [  215.652298] EXT4-fs (loop0): bad geometry: block count 499952 exceeds size of device (120452 blocks)
    [  230.677236] usb 1-2: USB disconnect, device number 3
    [  230.682887] sd 33:0:0:0: [sdb] Synchronizing SCSI cache
    [  230.682906] sd 33:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
    [  535.816999] usb 1-2: new high-speed USB device number 4 using ehci-pci
    [  535.964892] usb 1-2: New USB device found, idVendor=0928, idProduct=000a
    [  535.964897] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [  535.964899] usb 1-2: Product: 1394A/USB2.0/eSATA combo drive
    [  535.964901] usb 1-2: Manufacturer: PI-208
    [  535.964903] usb 1-2: SerialNumber: 2009021200001475
    [  536.018373] usb-storage 1-2:1.0: USB Mass Storage device detected
    [  536.018559] scsi host34: usb-storage 1-2:1.0
    [  537.018644] scsi 34:0:0:0: Direct-Access     Ext Hard  Disk                 PQ: 0 ANSI: 4
    [  537.023146] sd 34:0:0:0: Attached scsi generic sg2 type 0
    [  537.035945] sd 34:0:0:0: [sdb] Spinning up disk...
    [  545.685119] .ready
    [  545.687908] sd 34:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
    [  545.690574] sd 34:0:0:0: [sdb] Write Protect is off
    [  545.690580] sd 34:0:0:0: [sdb] Mode Sense: 10 00 00 00
    [  545.692502] sd 34:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [  547.485277]  sdb: sdb1 sdb2 sdb3 sdb4
    [  549.330208] sd 34:0:0:0: [sdb] Attached SCSI disk
    [  587.500858] sd 34:0:0:0: [sdb] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [  587.500865] sd 34:0:0:0: [sdb] Sense Key : Medium Error [current] 
    [  587.500877] sd 34:0:0:0: [sdb] Add. Sense: Data phase error
    [  587.500881] sd 34:0:0:0: [sdb] CDB: Read(10) 28 00 00 3c ca c0 00 00 08 00
    [  587.500884] blk_update_request: I/O error, dev sdb, sector 3984064
    [  615.107154] sd 34:0:0:0: [sdb] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [  615.107160] sd 34:0:0:0: [sdb] Sense Key : Medium Error [current] 
    [  615.107164] sd 34:0:0:0: [sdb] Add. Sense: Data phase error
    [  615.107168] sd 34:0:0:0: [sdb] CDB: Read(10) 28 00 00 3c ca c0 00 00 08 00
    [  615.107171] blk_update_request: I/O error, dev sdb, sector 3984064
    [  615.107177] Buffer I/O error on dev sdb1, logical block 489968, async page read
    [  638.996500] sd 34:0:0:0: [sdb] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [  638.996508] sd 34:0:0:0: [sdb] Sense Key : Medium Error [current] 
    [  638.996513] sd 34:0:0:0: [sdb] Add. Sense: Data phase error
    [  638.996517] sd 34:0:0:0: [sdb] CDB: Read(10) 28 00 00 3c cb 40 00 00 08 00
    [  638.996521] blk_update_request: I/O error, dev sdb, sector 3984192
    [  671.403732] md: bind<sdb2>
    [  671.417697] md: bind<sdb3>
    [  671.429457] md: bind<sdb4>
    [  916.145549] EXT4-fs (loop0): mounting ext3 file system using the ext4 subsystem
    [  916.145572] EXT4-fs (loop0): bad geometry: block count 499952 exceeds size of device (120452 blocks)
    [  938.701220] EXT4-fs (loop0): mounting ext3 file system using the ext4 subsystem
    [  938.701254] EXT4-fs (loop0): bad geometry: block count 499952 exceeds size of device (120452 blocks)
    [ 1027.971605] EXT4-fs (loop0): mounting ext3 file system using the ext4 subsystem
    [ 1027.971617] EXT4-fs (loop0): bad geometry: block count 499952 exceeds size of device (120452 blocks)
    [ 1090.355904] usb 1-2: USB disconnect, device number 4
    [ 1090.363349] sd 34:0:0:0: [sdb] Synchronizing SCSI cache
    [ 1090.363371] sd 34:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
    [ 1463.518184] usb 1-2: new high-speed USB device number 5 using ehci-pci
    [ 1463.667570] usb 1-2: New USB device found, idVendor=0928, idProduct=000a
    [ 1463.667575] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [ 1463.667578] usb 1-2: Product: 1394A/USB2.0/eSATA combo drive
    [ 1463.667580] usb 1-2: Manufacturer: PI-208
    [ 1463.667581] usb 1-2: SerialNumber: 2009021200001475
    [ 1463.724790] usb-storage 1-2:1.0: USB Mass Storage device detected
    [ 1463.724980] scsi host35: usb-storage 1-2:1.0
    [ 1464.731309] scsi 35:0:0:0: Direct-Access     Ext Hard  Disk                 PQ: 0 ANSI: 4
    [ 1464.733876] sd 35:0:0:0: Attached scsi generic sg2 type 0
    [ 1464.745829] sd 35:0:0:0: [sdc] Spinning up disk...
    [ 1469.083624] .ready
    [ 1469.087834] sd 35:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
    [ 1469.089975] sd 35:0:0:0: [sdc] Write Protect is off
    [ 1469.089984] sd 35:0:0:0: [sdc] Mode Sense: 10 00 00 00
    [ 1469.093345] sd 35:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 1469.119977]  sdc: sdc1 sdc2 sdc3 sdc4
    [ 1469.131610] sd 35:0:0:0: [sdc] Attached SCSI disk
    [ 1492.984081] sd 35:0:0:0: [sdc] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [ 1492.984090] sd 35:0:0:0: [sdc] Sense Key : Medium Error [current] 
    [ 1492.984094] sd 35:0:0:0: [sdc] Add. Sense: Data phase error
    [ 1492.984097] sd 35:0:0:0: [sdc] CDB: Read(10) 28 00 00 3c ca c0 00 00 08 00
    [ 1492.984100] blk_update_request: I/O error, dev sdc, sector 3984064
    [ 1516.945163] sd 35:0:0:0: [sdc] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [ 1516.945167] sd 35:0:0:0: [sdc] Sense Key : Medium Error [current] 
    [ 1516.945169] sd 35:0:0:0: [sdc] Add. Sense: Data phase error
    [ 1516.945172] sd 35:0:0:0: [sdc] CDB: Read(10) 28 00 00 3c ca c0 00 00 08 00
    [ 1516.945173] blk_update_request: I/O error, dev sdc, sector 3984064
    [ 1516.945177] Buffer I/O error on dev sdc1, logical block 489968, async page read
    [ 1517.088615] md: export_rdev(sdc2)
    [ 1517.093427] md: export_rdev(sdc2)
    [ 1517.111599] md: export_rdev(sdc3)
    [ 1517.116648] md: export_rdev(sdc3)
    [ 1517.132338] md: export_rdev(sdc4)
    [ 1517.134496] md: export_rdev(sdc4)
    [ 1761.496542] EXT4-fs (loop0): mounting ext3 file system using the ext4 subsystem
    [ 1761.496557] EXT4-fs (loop0): bad geometry: block count 499952 exceeds size of device (120452 blocks)
    [ 4992.005590] EXT4-fs (loop0): mounting ext3 file system using the ext4 subsystem
    [ 4992.006389] EXT4-fs (loop0): bad geometry: block count 499952 exceeds size of device (120452 blocks)
    [ 5069.353129] EXT4-fs (loop0): mounting ext3 file system using the ext4 subsystem
    [ 5069.353173] EXT4-fs (loop0): bad geometry: block count 499952 exceeds size of device (120452 blocks)

    What else should I try?

    Please remember this HD has data I must not loose!

    Thanks
    Gilson
    Last edited by howefield; December 5th, 2015 at 10:31 AM.

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

    Re: Recover data from NAS HD

    A RAID1 will typically work in a degraded fashion when 1 drive fails. When the second drive fails, it will fail to mount. So if your dmesg output is on the "good" drive, then you now have 2 failed drives and data recovery is not trivial.
    -------------------------------------
    Oooh Shiny: PopularPages

    Unumquodque potest reparantur. Patientia sit virtus.

  5. #5
    Join Date
    Jun 2008
    Beans
    23

    Re: Recover data from NAS HD

    I forgot to mention that the above commands I got running it on a Ubuntu virtual machine and having the good drive connected to the laptop with a Sata to USB cable - not sure it that changes anything.

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

    Re: Recover data from NAS HD

    Check the SMART parameters of the disk drive:

    Code:
    sudo smartctl -a /dev/sdg
    Your drive number will be different from /dev/sdg.
    -------------------------------------
    Oooh Shiny: PopularPages

    Unumquodque potest reparantur. Patientia sit virtus.

  7. #7
    Join Date
    Jun 2008
    Beans
    23

    Re: Recover data from NAS HD

    Here it goes

    Code:
    gsantos@ubuntu:~$ smartctl -a /dev/sdb
    smartctl 6.4 2014-10-07 r4002 [x86_64-linux-4.2.0-19-generic] (local build)
    Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
    
    /dev/sdb: Unknown USB bridge [0x0928:0x000a (0x000)]
    Please specify device type with the -d option.
    
    Use smartctl -h to get a usage summary

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

    Re: Recover data from NAS HD

    You can't get SMART parameters through a USB enclosure. You need to connect it to a SATA port.
    -------------------------------------
    Oooh Shiny: PopularPages

    Unumquodque potest reparantur. Patientia sit virtus.

  9. #9
    Join Date
    Jun 2008
    Beans
    23

    Re: Recover data from NAS HD

    I am sorry. All I get is a Sata to USB and a laptop. Is there any way I can do it with what I have?

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

    Re: Recover data from NAS HD

    Put the hard drive in a desktop computer with a LiveUSB of Ubuntu 14.04. Connect the hard drive with a SATA cable and connect to the network with an ethernet cable. Boot, install smartmontools, it will be in RAM only with a Live session, check the SMART status of the drive.
    -------------------------------------
    Oooh Shiny: PopularPages

    Unumquodque potest reparantur. Patientia sit virtus.

Page 1 of 3 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
  •