Although, didn't he say he already had some files in /drive0/fids, it may be worth deleting those first, or doing mv -f rather than just an mv

cd /drive0/drive1/fids
mv * /drive0/fids
cd /drive0
rm -rf drive1

This works better if I mount the disk read/write

It is moving the files now. Is this just rearranging directory structure, or is it actually copying/deleting all the files? I hope this doesn't take another three hours...

Well, obviously it won't, because it is done now.

At this point, all I should have to do is change back to read-only, exit the command shell, fire up emplode and force a re-synch to rebuild the database. Right?

tanstaafl.

cd /drive0/drive1/fids
mv * /drive0/fids
cd /drive0
rm -rf drive1

mv /drive0/fids /drive0/fids.not (or just rm -rf /drive0/fids)
mv /drive0/drive1/fids /drive0

would have been slightly quicker... oh well, too late.

Peter

At this point, all I should have to do is change back to read-only, exit the command shell, fire up emplode and force a re-synch to rebuild the database. Right?

Yup.

Peter

Yup.

And indeed, empeg lives!

Thank you for all the help. The depth of knowledge and willingness to assist that prevails on this bbs never ceases to amaze me.

The re-synch generated some errors:

The length of playlist Comedy did not match the actual number of children detected

and repeated for Bach, Car Talk, and Steve Morse. I suspect this is the result of the damaged sectors in the database region of the original 18 GB drive, and that I have now lost a few more songs. Or, maybe not -- the player still shows the same total number of songs as I had on the 18 GB drive, so probably the errors were for songs present on the player and not in the database. A second synch fixed it and now everything is good.

Thanks again, people... now I can install the software upgrades and the Car Talk episodes I was sitting on because I couldn't synch my old drive.

tanstaafl.

So here's a question...

The problem was that the files ended up in a different directory than /drive0/fids. I'm assuming it was because of some kind of a mistake at the shell prompt during the copy operation. Does that mean there's a typo somewhere in the copy instructions in the Drive Upgrade Guide? Doug, were you going from those instructions?

Greetings!

I started with these instructions for the new drive installs, and I got the same thing - a drive1 directory under /drive0. Perhaps what might be better might be:

# cp -a /drive1/* /drive0

That is what I intend to try next.

I've used the command in the Guide line for line and never had a problem. I've done about 5 upgrades over the last few months for myself and other owners I know. I'm guessing a typo too.

Edit: Looks like he entered "cp -a /drive1 /drive0" and the Guide has "cp -auvfx /drive1/fids /drive0/" ...