Page 1 of 2 12 LastLast
Results 1 to 10 of 17

Thread: recovering data from old HDD

  1. #1
    Join Date
    Jun 2008
    Location
    London
    Posts
    174

    Default recovering data from old HDD

    I've just got a STA/IDE to USB 2.0 gadgetas a quick and dirty way to get data off a HDD

    Plugged everything in hoping with no particualr reason that it would work like a USB stick.

    Device notifier spotted drive but wouldn't mount it

    Code:
    dmesg | tail
    [20197.639369] sd 8:0:0:0: [sdb]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [20197.639373] sd 8:0:0:0: [sdb]  Sense Key : Medium Error [current] 
    [20197.639378] sd 8:0:0:0: [sdb]  Add. Sense: Peripheral device write fault
    [20197.639383] sd 8:0:0:0: [sdb] CDB: Write(10): 2a 00 00 60 7c cf 00 00 08 00
    [20197.639391] end_request: I/O error, dev sdb, sector 6323407
    [20197.639397] Buffer I/O error on device sdb6, logical block 8210
    [20197.639399] lost page write due to I/O error on sdb6
    [20197.639429] REISERFS warning (device sdb6): journal-837 _update_journal_header_block: IO error during journal replay
    [20197.639434] REISERFS warning (device sdb6): reiserfs-2006 journal_init: Replay Failure, unable to mount
    [20197.639603] REISERFS warning (device sdb6): sh-2022 reiserfs_fill_super: unable to initialize journal space
    I don't think the drive is bad.
    I can't find much on what to do next
    May I ask for help and suggestions please?

  2. #2
    Join Date
    Jun 2008
    Location
    London
    Posts
    174

    Default Re: recovering data from old HDD

    Further info

    Code:
    fdisk -l
    
    Disk /dev/sda: 122.9 GB, 122942324736 bytes
    255 heads, 63 sectors/track, 14946 cylinders, total 240121728 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
    Disk identifier: 0x000e14af
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sda1              63     4192964     2096451   82  Linux swap / Solaris
    /dev/sda2   *     4192965    46122614    20964825   83  Linux
    /dev/sda3        46122615   240107489    96992437+  83  Linux
    
    Disk /dev/sdb: 82.0 GB, 81964302336 bytes
    16 heads, 63 sectors/track, 158816 cylinders, total 160086528 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
    Disk identifier: 0x00000000
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sdb1   *     4193280   160086527    77946624    f  W95 Ext'd (LBA)
    /dev/sdb5         4193343     6257663     1032160+  82  Linux swap / Solaris
    /dev/sdb6         6257727   160086527    76914400+  83  Linux

  3. #3

    Default Re: recovering data from old HDD

    Well it looks to me as though the ReiserFS file system is corrupted on the sdb6 partition. There are three basic tests you could perform in a root console:

    1) Check the file system logic with:

    fsck /dev/sdb6

    This may find that you have to rebuild the filesystem tree and that may result in loss of data.

    2) Check the disk hardware itself with a simple read test:

    badblocks -sv /dev/sdb

    3) Check the disk hardware with a much longer but more rigorous non destructive read write test:

    badblocks -svnt random /dev/sdb

    Good luck.

  4. #4
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: recovering data from old HDD

    On 2011-03-28 00:36, gerrygavigan wrote:

    > Code:
    > --------------------
    >
    > dmesg | tail
    > [20197.639369] sd 8:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    > [20197.639373] sd 8:0:0:0: [sdb] Sense Key : Medium Error [current]
    > [20197.639378] sd 8:0:0:0: [sdb] Add. Sense: Peripheral device write fault
    > [20197.639383] sd 8:0:0:0: [sdb] CDB: Write(10): 2a 00 00 60 7c cf 00 00 08 00
    > [20197.639391] end_request: I/O error, dev sdb, sector 6323407
    > [20197.639397] Buffer I/O error on device sdb6, logical block 8210
    > [20197.639399] lost page write due to I/O error on sdb6


    You can not continue with that type of error. I don't know if the problem
    is the disk or the gadget. Try to connect to real hardware port, run smart
    tests.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 11.2 x86_64 "Emerald" at Telcontar)

  5. #5
    Join Date
    Jun 2008
    Location
    London
    Posts
    174

    Default Re: recovering data from old HDD

    Thank you both for replying.

    I didn't really understand what a smart test was so I went with the first set of advice, which seems to indicate the drive is at least accessible

    Code:
    fsck /dev/sdb6
    
    Will read-only check consistency of the filesystem on /dev/sdb6
    Will put log info to 'stdout'
    
    Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
    ###########
    reiserfsck --check started at Mon Mar 28 15:55:16 2011
    ###########
    Replaying journal: Done.
    Reiserfs journal '/dev/sdb6' in blocks [18..8211]: 0 transactions replayed
    Checking internal tree.. \/  1 (of   4|/ 42 (of 122\bad_internal: vpf-10320: block 7372921, items 142 and 143: The wrong order of items: [3475 337075 0x0 SD (0)], [3475 336913 0x401 DRCT (2)]
     the problem in the internal node occured (7372921), whole subtree is skipped
    /  2 (of   4|/ 67 (of 152|/ 28 (of 148|block 16154825: The number of items (18) is incorrect, should be (9)
     the problem in the internal node occured (16154825), whole subtree is skipped
    /112 (of 152//110 (of 116\
    The problem has occurred looks like a hardware problem. If you have
    bad blocks, we advise you to get a new hard drive, because once you
    get one bad block  that the disk  drive internals  cannot hide from
    your sight,the chances of getting more are generally said to become
    much higher  (precise statistics are unknown to us), and  this disk
    drive is probably not expensive enough  for you to you to risk your
    time and  data on it.  If you don't want to follow that follow that
    advice then  if you have just a few bad blocks,  try writing to the
    bad blocks  and see if the drive remaps  the bad blocks (that means
    it takes a block  it has  in reserve  and allocates  it for use for
    of that block number).  If it cannot remap the block,  use badblock
    option (-B) with  reiserfs utils to handle this block correctly.
    
    bread: Cannot read the block (18514580): (Input/output error).
    
    Warning... fsck.reiserfs for device /dev/sdb6 exited with signal 6.
    badblocks -sv /dev/sdb chunters on to over 30,000,000 blocks (well past the data content of the drive) until I cntl-c'ed it

    more research suggests I need reiserfsprogs but the only source I could find

    reiserfsprogs Downloads - Linux Packages Search

    doesn't have openSUSE packages

    May I ask if anyone knows where to find them?

  6. #6
    Join Date
    Jun 2008
    Location
    London
    Posts
    174

    Default Re: recovering data from old HDD


  7. #7
    Join Date
    Jun 2008
    Location
    London
    Posts
    174

    Default Re: recovering data from old HDD

    I've compiled reiserfsprogs and based on

    http://www.cyberciti.biz/tips/repair...eiserfsck.html

    this is where I got to

    Code:
    reiserfsck --scan-whole-partition --rebuild-tree /dev/sdb6
    reiserfsck 3.6.21 (2009 www.namesys.com)
    
    Will rebuild the filesystem (/dev/sdb6) tree
    Will put log info to 'stdout'
    
    Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
    Replaying journal: Done.
    Reiserfs journal '/dev/sdb6' in blocks [18..8211]: 0 transactions replayed
    ###########
    reiserfsck --rebuild-tree started at Mon Mar 28 16:43:18 2011
    ###########
    
    Pass 0:
    ####### Pass 0 #######
    The whole partition (19228592 blocks) is to be scanned
    Skipping 8797 blocks (super block, journal, bitmaps) 19219795 blocks will be read
    0%block 369320: The number of items (1) is incorrect, should be (0) - corrected
    block 369320: The free space (0) is incorrect, should be (4072) - corrected
                                                         left 18716292, 5244 /sec
    The problem has occurred looks like a hardware problem. If you have
    bad blocks, we advise you to get a new hard drive, because once you
    get one bad block  that the disk  drive internals  cannot hide from
    your sight,the chances of getting more are generally said to become
    much higher  (precise statistics are unknown to us), and  this disk
    drive is probably not expensive enough  for you to you to risk your
    time and  data on it.  If you don't want to follow that follow that
    advice then  if you have just a few bad blocks,  try writing to the
    bad blocks  and see if the drive remaps  the bad blocks (that means
    it takes a block  it has  in reserve  and allocates  it for use for
    of that block number).  If it cannot remap the block,  use badblock
    option (-B) with  reiserfs utils to handle this block correctly.
    
    bread: Cannot read the block (512047): (Input/output error).
    
    Aborted
    I would be grateful for a few more words of advice

  8. #8
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: recovering data from old HDD

    On 2011-03-28 17:36, gerrygavigan wrote:
    >
    > Thank you both for replying.
    >
    > I didn't really understand what a smart test was so I went with the
    > first set of advice, which seems to indicate the drive is at least
    > accessible
    >


    No, it is not.

    Insist on running smart tests, or manufacturer HD tests.

    smart --> S.M.A.R.T. --> wikipedia.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 11.2 x86_64 "Emerald" at Telcontar)

  9. #9
    Join Date
    Jun 2008
    Location
    London
    Posts
    174

    Default Re: recovering data from old HDD

    Quote Originally Posted by robin_listas View Post
    On 2011-03-28 17:36, gerrygavigan wrote:[color=blue]

    No, it is not.

    Insist on running smart tests, or manufacturer HD tests.

    smart --> S.M.A.R.T. --> wikipedia.
    OK, I've read Wikpedia, thank you, but I still cannot work out the next stage.

    Ultimately

    I'd like to do a one-time read of what used to be a /home directory
    then extract such files as might still be there

    I'm not sure I understand how the SMART test takes me closer to that.
    I don't really want or need to integrate the disc into my file system.

  10. #10
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: recovering data from old HDD

    On 2011-03-28 18:06, gerrygavigan wrote:
    >
    > I've compiled reiserfsprogs and based on



    > reiserfsck --scan-whole-partition --rebuild-tree /dev/sdb6


    reiserfsck is part of the distro.


    > The problem has occurred looks like a hardware problem. If you have


    > Aborted
    >
    > I would be grateful for a few more words of advice


    You should give thanks that the process aborted, it would have destroyed
    your data. You have hardware problems, perhaps in the gadget or in the HD.

    You must connect that disk to a real [s|p]ATA port and do a hardware check,
    either with smartctl or with the HD manufacturer test disk.

    This is unavoidable, want it or not.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 11.2 x86_64 "Emerald" at Telcontar)

Page 1 of 2 12 LastLast

Posting Permissions

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