1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Linux I/O error

Discussion in 'Tech Support' started by Burnout21, 16 Dec 2009.

  1. Burnout21

    Burnout21 Mmmm biscuits

    Joined:
    9 Sep 2005
    Posts:
    8,616
    Likes Received:
    197
    joys of joys today.

    One success in one place, a failure else where!

    basically one of my HDD's in my ubuntu based NAS has gone awful funny.

    This seems to be effecting large files only at the moment, how big i cant say but it failed on a file of about 800mb.

    I can copy data of 6GB of more if anything there isn't a limit on that, onto the drive, however trying to copy it from there to anywhere else it simple fails with an I/O error, fail to read file.

    I am stumpt!

    So err in typical forum thread, as the saying goes HELP!!!
     
  2. gnutonian

    gnutonian What's a Dremel?

    Joined:
    6 Jan 2009
    Posts:
    340
    Likes Received:
    13
  3. Burnout21

    Burnout21 Mmmm biscuits

    Joined:
    9 Sep 2005
    Posts:
    8,616
    Likes Received:
    197
  4. Burnout21

    Burnout21 Mmmm biscuits

    Joined:
    9 Sep 2005
    Posts:
    8,616
    Likes Received:
    197
    right after several hours of googling trying to find a solution to recovery i found ddrescue, this is where it gets odd.

    i required the names of my drives for ddrescue, so i opened up Gparted.

    Gparted has a repair feature!

    Right now i can copy stuff off, too which i am doing, however the used space went from 115Gb to 89Gb, so something has been lost.

    oh well, at least its progress!
     
  5. Baz

    Baz I work for Corsair

    Joined:
    13 Jan 2005
    Posts:
    1,810
    Likes Received:
    92
    Wouldn't happen to be a Samsung F3 1TB this HDD would it? I've had one go on me in one of my systems after it chucked out read, write and CRC errors for weeks causing all kinds of havoc.
     
  6. Burnout21

    Burnout21 Mmmm biscuits

    Joined:
    9 Sep 2005
    Posts:
    8,616
    Likes Received:
    197
    na it was an old 250Gb hitachi, solid drive, but the ext4 filesystem on it has a bug, pointed out above.

    That bug is exactly my problem. Managed to fix the filesystem enough to copy my stuff off it, and revert it to ext3 for safety reasons.


    Oddly at the time i went ext4 because the wiki explained its better at organising large files. Sod that!
     

Share This Page