Buffer I/O errors when trying to clone xbox HDD?

Discussion in 'Modding and Hacking - Consoles and Electronics' started by Ashevent, May 22, 2016.

Watch Thread
  1. Ashevent

    Ashevent Site Supporter 2015

    Joined:
    Oct 1, 2015
    Messages:
    503
    Likes Received:
    137
    I've upgraded about 12 Original XBox's, mostly softmods and for the first time ever, having trouble upgrading to a larger IDE hard drive. When I try to clone with Chimp as usual i'm getting a "Buffer I/O error on device hda, logical block 568448" error message. I've tried searching the forums and elswhere for a solution. Any idea's what up? or what that means?
     
    Ashevent, May 22, 2016 Report
    #1 + Quote Reply
  2. ASSEMbler

    ASSEMbler Administrator Staff Member

    Joined:
    Mar 13, 2004
    Messages:
    19,394
    Likes Received:
    995
    Found this on another forum about Buffer i/o error

    "
    I used a laptop with Windows XP SP3, an IDE to USB attachment and XBoxhdm. I "hotswapped" using the error 12 method.

    QEmu 0.12.2 works well. I downloaded the -Lite windows binary from QEmu on Windows.

    And I ran QEmu with these parameters

    Code:
    qemu.exe -L . -m 512 -hda //./PhysicalDrive2 -cdrom linux.iso -boot d -localtime -M pc -parallel none
    The biggest difference is -parallel none and no sound. This is because I received IRQ errors. My laptop doesn't have a parallel port and I suppose the default is to attach one. I also removed the sound because of the IRQ errors.

    After the IRQ errors I changed the physical drive. ./PhysicalDrive2 is because I kept another USB drive attached to my computer. It was trial and error (either 1 or 2) to find the correct one. I knew 2 was correct because xbrowser worked and the intro for linux displayed the device with the correct size.

    Again, thanks for the great tip. You saved me a headache to find a computer with an IDE... Again.

    Will"
     
    ASSEMbler, May 22, 2016 Report
    #2 + Quote Reply
    Ashevent likes this.
  3. ASSEMbler

    ASSEMbler Administrator Staff Member

    Joined:
    Mar 13, 2004
    Messages:
    19,394
    Likes Received:
    995
    I would run a disk test first, make sure it's not bad. Could be a bad drive.
     
    ASSEMbler, May 22, 2016 Report
    #3 + Quote Reply
    Ashevent likes this.
  4. Jack.

    Jack. RISC Master Race

    Joined:
    Sep 3, 2014
    Messages:
    129
    Likes Received:
    9
    Very likely, I wouldn't bother checking. Try exploring the disk with a forensics tools that doesn't need sequential block access (WinHex does that). Try to dd it on a file through linux (or dd for windows), that usually works with every kind of media, as long as it can read the block. Thank *nix for treating media as files.
     
    Jack., May 23, 2016 Report
    #4 + Quote Reply
    Ashevent likes this.
  5. Rocky5

    Rocky5 Site Supporter 2015

    Joined:
    Jan 17, 2014
    Messages:
    524
    Likes Received:
    95
    Chimp will spew out this error when a drive is locked.
    (But that's usually on hdb the slave drive)

    Try Chimp 261812
     
    Rocky5, May 28, 2016 Report
    #5 + Quote Reply
  6. Ashevent

    Ashevent Site Supporter 2015

    Joined:
    Oct 1, 2015
    Messages:
    503
    Likes Received:
    137
    I had a few trips we're on so only had time to try and clone to a different new drive before we left and..same thing. Got to 5% clone and then exact same message. Once we get back (now in Vegas) i'll try some of the suggestions. Thanks so much guys!
     
    Ashevent, Jun 1, 2016 Report
    #6 + Quote Reply
  7. Ashevent

    Ashevent Site Supporter 2015

    Joined:
    Oct 1, 2015
    Messages:
    503
    Likes Received:
    137
    Well at first I thought I dodged a bullet. A freind only wanted coinops lite so I just threw that on the xbox I was having problems with and moved on. Downloaded the new chimp (thanks Rocky5!) and after my usual soft mod of a different xbox, I went to clone the problem hard drive. EVEYTHING WORKED PERFECTLY until I went to lock the hard drive. Nothing, nada. Could't lock from motherboard, tried backing up eprom and locking from there. Nope...nothing. Tried a different new hard dirve and...exact same thing. I've done this 10? times or more in the last year with no troubles and now suddenly these two things. Kind of wondering if the Mod Gods are pissed at me..lol. FYI, If I try loading the unlocked hard drive on it's own, I do of course get the "problem 9" screen.
     
    Ashevent, Jun 13, 2016 Report
    #7 + Quote Reply
sonicdude10
Draft saved Draft deleted
Insert every image as a...
  1.  0%

Share This Page