Help! :-)

I'm trying to upgrade my player to a 128gb SSD (the KingSpec unit that MLord recommended). I'm trying to copy the FIDs from drive1 (the old drive) to drive0 (the new drive), and it ran for hours just fine, but now it's displaying error messages in the copy operation.

Here's what I did, and below that, the output:

- Installed the new SSD drive by itself, with the jumpers set to Master.
- Installed builder_bigdisk_v6.upgrade, freshly downloaded from http://rtr.ca/bigdisk on that drive, seemed to go OK, but I didn't get to the terminal prompt quickly enough to see if it was prompting me with a "disk was already built" message after the installation. I'm not clear on whether we need to press enter or not at that point any more.
- Installed car2_v2b13_hijack.upgrade, freshly downloaded from http://rtr.ca/bigdisk on that drive, it was successful and the empeg booted into the player software as expected.
- Installed the old drive back on the hard disk cable with its jumper in the slave position.
- At the serial terminal prompt:

Q
cd /
df drive0
df drive1

(confirmed that drive0 looked like the new 128gb SSD drive and drive1 looked like the original 40gb Fujitsu drive)

rw
rwm
cp -auvfx /drive1/fids /drive0/

It copied FIDs for several hours succesfully, and was still copying when I got back from going out to dinner. This is the current screen output (I have removed hundreds of lines of successful FID copying from the scrollback history):

(...)
/drive1/fids/b571 -> /drive0/fids/b571
/drive1/fids/b580 -> /drive0/fids/b580
/drive1/fids/b581 -> /drive0/fids/b581
/drive1/fids/b590 -> /drive0/fids/b590
/drive1/fids/b591 -> /drive0/fids/b591
/drive1/fids/b5a0 -> /drive0/fids/b5a0
/drive1/fids/b5a1 -> /drive0/fids/b5a1
/drive1/fids/b5b0 -> /drive0/fids/b5b0
/drive1/fids/b5b1 -> /drive0/fids/b5b1
/drive1/fids/b5c0 -> /drive0/fids/b5c0
/drive1/fids/b5c1 -> /drive0/fids/b5c1
/drive1/fids/b5d0 -> /drive0/fids/b5d0
/drive1/fids/b5d1 -> /drive0/fids/b5d1
/drive1/fids/b5e0 -> /drive0/fids/b5e0
hda: status timeout: status=0xd0
hda: no DRQ after issuing WRITE
ide0: reset timed-out, status=0xd0
hda: status timeout: status=0xd0
hda: drive not ready for command
ide0: reset timed-out, status=0xd0
hda: status timeout: status=0xd0
end_request: I/O error, dev 03:04 (hda), sector 0
hda: drive not ready for command
hda: status timeout: status=0xd0
hda: drive not ready for command
ide0: reset timed-out, status=0xd0
hda: status timeout: status=0xd0
hda: drive not ready for command
ide0: reset timed-out, status=0xd0
hda: status timeout: status=0xd0
end_request: I/O error, dev 03:04 (hda), sector 8
hda: drive not ready for command
hda: status timeout: status=0xd0
hda: drive not ready for command
ide0: reset timed-out, status=0xd0
hda: status timeout: status=0xd0
hda: drive not ready for command
ide0: reset timed-out, status=0xd0
hda: status timeout: status=0xd0
end_request: I/O error, dev 03:04 (hda), sector 1048672
hda: drive not ready for command
hda: status timeout: status=0xd0
hda: drive not ready for command
EXT2-fs error (device ide0(3,4)): ext2_write_inode: unable to read inode block - inode=2108, block=131084
ide0: reset timed-out, status=0xd0
hda: status timeout: status=0xd0
hda: drive not ready for command
ide0: reset timed-out, status=0xd0
hda: status timeout: status=0xd0
end_request: I/O error, dev 03:04 (hda), sector 27000832
hda: drive not ready for command
hda: status timeout: status=0xd0
hda: drive not ready for command
ide0: reset timed-out, status=0xd0
hda: status timeout: status=0xd0
hda: drive not ready for command
ide0: reset timed-out, status=0xd0
hda: status timeout: status=0xd0
end_request: I/O error, dev 03:04 (hda), sector 27014384
hda: drive not ready for command
hda: status timeout: status=0xd0
hda: drive not ready for command
ide0: reset timed-out, status=0xd0
hda: status timeout: status=0xd0


Unfortunately I don't have scrollback of the beginning of the terminal session which would show the boot sequence, seems Putty doesn't keep everything in the scrollback. Ah well.

I'm expecting that I should terminate the copy operation, and do a "ro" and "rom", to protect the contents of the original drive before I try to start over again. But before I start over again, does anyone have any other advice?

Thanks!
_________________________
Tony Fabris