No playlists, no shell prompt on my player

I am replacing my existing 18 GB drive with a 40 GB drive.

Before I started, I made sure I could get a shell prompt on my 18 GB drive with hyperterminal, and I could indeed do so.

I took the player apart, hooked the 40 GB drive to the IDE cable, and installed the disk builder upgrade on it.

I then installed the developer version of Beta 2.0 RC1 on the 40 GB drive because that is what was on the 18 GB drive and I figured it would be best to have them match. The intent was to get a shell prompt and copy the 18GB drive over to the 40 GB drive (using the command # cp -a /drive1 /drive0), then remove the 18 GB drive. (The drive is in the process of dying with bad sectors).

I then jumpered the 18 GB drive as slave and powered up the player. The player booted almost normally, except that it spent a long time at "building music database". This didn't concern me too much because the database is now on the slave drive and the player is probably looking at the primary drive. However, once it is all booted up, no playlists are found.

Hyperterminal works in that it displays the bootup information from the player; but apparently it will not accept any input from my keyboard. I cannot use the "q" command to get to the linux shell on the player in order to copy my 18 GB drive to the new 40 GB drive.

The bootup log looks pretty normal to me:

VFS: Mounted root (ext2 filesystem).
empeg-pump v0.03 (19980601)
Press Ctrl-A to enter pump...VFS: Mounted root (ext2 filesystem) readonly.
change_root: old root has d_count=1
Trying to unmount old root ... okay
Freeing unused kernel memory: 4k initempeg init 0.8
I see this is a developer image!
Mounting proc
Mounting first music partition
Tried to mount /dev/hda4 as reiserfs but got error 19
Mounting second music partition
Remounting first music partition read-only
Remounting second music partition read-only
Press 'q' now to go into development mode. You Have Zero Seconds To Comply...
Starting player
player.cpp : 385:empeg-car 2.00-rc1 2003/01/15.
! tunedb_disk.cpp :1274:Database size mismatch error.
Prolux 4 empeg car - 2.1434 Jan 15 2003
Vcb: 0x4054d000
Vcb: 0
Vcb: 65536
Vcb: 0
Vcb: 65536

I am confident that the IDE cable is good (I tried both my two-year-old Mark II cable that has never given me a moment's trouble, and a brand new cable destined for my Mark IIA spare) and I am confident that the connectors are installed properly, not misaligned.

If I try to boot up with just the 18 GB drive attached, it won't boot, I suspect because it is set as a slave drive. I didn't have a proper jumper for the drive, and since it was dying and never to be used again once this process was finished, I bent and soldered the two "slave" pins together, so I cannot very easily "unslave" the drive. However, before I did this bit of butchery, I did check and the drive would boot up solo and I could access the playlists and play music.

If I try to boot with just the 40 GB drive attached, it boots right up, but I still cannot get to a shell prompt.

I don't know where to go from here. Anybody got any ideas?

tanstaafl.

> tunedb_disk.cpp :1274:Database size mismatch error.

Delete the database files and do a fresh sync. Details somewhere in the FAQ.

-ml

Delete the database files and do a fresh sync. Details somewhere in the FAQ.

The obligatory link is here. Also, another possible problem might be related to this, but I don't know exactly.

I'm concerned that Doug used a soldering iron directly on his 18gb disk drive. Could that possibly have caused a problem?

Also, permanently turning a disk drive into a slave drive is a bad idea, because in the empeg, sometimes when you add a new drive, certain drives refuse to be a slave and will only work as a master. For instance, I had intended for my recent upgrade to be a certain master/slave order, and they refused to work that way. So I had to rethink my process and get the files ordered/copied differenty.

I'm concerned that Doug used a soldering iron directly on his 18gb disk drive. Could that possibly have caused a problem?

Although not the best of things to do, if it was done cleanly and quickly it shouldn't pose much more of a risk to the drive than changing the jumper.

The drive looks like it is working just fine, so it's not that.

Cheers

Mark said: Delete the database files and do a fresh sync. Details somewhere in the FAQ.

Tony said (in the FAQ):Reboot the player, and after the player software starts, press q (enter) to get to a shell prompt.

I said (in the original post that started this thread): Hyperterminal works in that it displays the bootup information from the player; but apparently it will not accept any input from my keyboard. I cannot use the "q" command to get to the linux shell on the player in order to copy my 18 GB drive to the new 40 GB drive.

And unfortunately, even if I could get to the shell prompt and delete the database, I cannot re-synch my 18 GB drive, because the dying sectors are in the database, and the last two times I tried to synch that drive (and I'll never try it again!) the synchronization process took over an hour while the heads seeked and re-seeked trying to read the bad sectors, and about 10% of my music disappeared.

I think my first priority has to be getting a shell prompt so I can at least attempt to copy the 18GB drive over to the 40 GB drive. At that point, the 18 GB drive gets retired forever, and I'll work on getting any corrupted data repaired on the 40 GB drive.

sometimes when you add a new drive, certain drives refuse to be a slave and will only work as a master
Both of my drives are IBM TravelStars, which are known to be non-problematic as far as compatibility problems and other weirdnesses.

Can anybody offer any suggestions on how to get my command prompt working? I have Beta 2.0RC1 developer on both drives, and because of the bad sectors on the 18GB drive I don't think I can install any other software version on it. I am using "Hyperterminal Private Edition v.6.3" by Hilgraeve as my terminal program. Before I started this disk swap process, I was able to get a shell prompt (on the 18 GB drive) using this program, but now I cannot.

I am puzzled...

tanstaafl.

Can anybody offer any suggestions on how to get my command prompt working? I have Beta 2.0RC1 developer on both drives, and because of the bad sectors on the 18GB drive I don't think I can install any other software version on it. I am using "Hyperterminal Private Edition v.6.3" by Hilgraeve as my terminal program. Before I started this disk swap process, I was able to get a shell prompt (on the 18 GB drive) using this program, but now I cannot.

The woes of your 18Gb drive won't be affecting Hyperterminal access. Can you try it with a different cable, or using a different serial port or PC?

Peter

Are you sure you installed a developer version of the software? If you didn't, you won't be able to `q'.

Edit: Oh. Duh. I see this is a developer image! Nevermind.

Greetings!

Let's leave the 18 out for a minute.

You say that when you boot the 40 solo, it boots fine, but you cannot break into a shell. Can you see anything through emplode in that case? Are any of your audio files on the drive? Can you show a boot log of that case?

You say that when you boot the 40 solo, it boots fine, but you cannot break into a shell. Can you see anything through emplode in that case? Are any of your audio files on the drive? Can you show a boot log of that case?

If you do this, bear in mind that synchronising with just the 40 in will write a blank fid 0x100, i.e. a blank root playlist. Subsequent synchronisations, or database rebuilds, will use this root playlist and not the populated one from the 18 (if the file exists on both /drive0 and /drive1, then the /drive0 one gets used).

Once you do solve your problem and get to a shell prompt, you should delete the contents of /drive0/fids (probably just 100 and 101) before the copy operation.

Peter

I thought that the copy from the 18 had already been completed, and that it might have been conflicting fids that were part of the problem. That still doesn't explain the inability to get shell, but an upgrade with the latest stock beta might help that.

I cannot use the "q" command to get to the linux shell on the player in order to copy my 18 GB drive to the new 40 GB drive.

Assuming that your serial connection is working properly (you can get Q to work on another drive or another player), does Ctrl+C work (as described here)?

The woes of your 18Gb drive won't be affecting Hyperterminal access. Can you try it with a different cable, or using a different serial port or PC?

I brought my disassembled player to work, hooked it up to my computer there, and had no difficulty getting the shell prompt.

I have no explanation of why I could get a shell prompt at home Saturday afternoon, but by Saturday night I could not.

The player is in the process of copying everything from my 18GB drive over to my new 40 GB drive (thanks to a little bit of ICQ help from Bitt!) and has been doing so for about two hours now. Uhhh... anybody have any idea how long it will take to transfer about 15.5 GB of data?

tanstaafl.

I think my 30GB took about 5 hours, disk-to-disk.

More like 15 hours when I used rsync to my desktop box, though!

I think my 30GB took about 5 hours, disk-to-disk.

That sounds about right. I had 13 GB of data, it took a bit under three hours.

However... I still have problems.

Even after 3 hours of copying files, my player tells me that there are no songs or playlists. Emplode tells me the same thing... except that at the bottom of the Emplode window it tells me Est. Free Space: 24.2 GB, Capacity: 37.1 GB. This would strongly suggest that there is indeed about 13 GB of data on my hard drive. Now the only question is, how do I get to it?

I tried the FAQ trick here of deleting /empeg/var/database, power cycling and doing a synch, but that caused no change in behavior.

Poking around at the command shell is not enlightening to me, because I don't remember enough about Linux (it's been ten years or more since I worked with any *nix system) to know what I'm looking for. But I sure can't seem to find any directories with any substantial amount of data.

Can anyone offer any helpful suggestions here?

tanstaafl.

If you do a ``ls /drive0/fids'', do you get a huge list of stuff? It's possible that you accidentally copied it to the wrong place, but with the stuff you said you executed when I was talking to you on ICQ, I don't think so. Regardless, it's worth it to check.

If you do a ``ls /drive0/fids'', do you get a huge list of stuff?

No. Just two files: "100" and "101".

It seems strange to me that emplode shows 13 GB of space being used, but I can find no trace of that usage in the command shell, the player software, or through emplode looking for playlists, songs, etc.

Should I try re-copying the songs over again? Should I run diskbuilder on the 40 GB drive and try again from the beginning?

tanstaafl.

Do a ``df -k /drive0''. Do you have both drives in right now, or just the one?

You could try running "find /" and hopefully you will see all of your fids fly past, then atleast you will know they are on the drive and where abouts they are, then it should just be a matter of moving them rather than copying them all again.

Well the files went somewhere. The fact that 13gb is being used seems to indicated that.

I'm guessing that a typo in the procedure put them somewhere else on the hard disk.

Or maybe concatenated them all into one huge file.... ick...

No find on the player, but "ls -R /" works..

That's what I get for not hooking up the Empeg and trying it before posting.

I will go and sit in the corner for 5 minutes and contemplate what I have done

Do a ``df -k /drive0''. Do you have both drives in right now, or just the one?

Just the one drive. I apologize fo being so slow in responding here, but my work computer just went Tango Uniform with apparently a corrupted display driver and I finally got it to reboot using a generic windows display driver in something that looks like about 160x240 and I am afaraid to mess with it right now because it is working after a fashion and it took me about eight reboot attempts to get it this far. (The chief engineer is going to work on it tomorrow...)Anyway

Anyway, the df -k /drive0 yielded the following:

empeg:/empeg/bin# df -k /drive0
df: Warning: cannot read table of mounted filesystems: No such file or directory

Filesystem 1k-blocks Used Available Use% Mounted on
- 38915386 13525622 25389764 35% /drive0
empeg:/empeg/bin#

Is that useful information?

tanstaafl.

Well, there's definitely 13GB of data on that drive. Somwhere. Do the "ls -R /" thing, and hit Ctrl-C after it spews out a few screenfuls of information. You should see a bunch of filenames that are just numbers. Post one, and we'll tell you what to do.

You could try running "find /"

empeg:/empeg/bin# find /
bash: find: command not found
empeg:/empeg/bin#

Well, that didn't work too well...

But a similar idea yielded something maybe useful:

empeg:/# ls -l -r
total 23
drwxr-xr-x 3 0 0 1024 Aug 28 1999 var
drwxr-xr-x 4 0 0 1024 Feb 6 2000 usr
drwxr-xr-x 2 0 0 1024 Apr 13 1999 tmp
lrwxrwxrwx 1 0 0 10 Jan 15 23:04 swapfile -> ./dev/hda6
lrwxrwxrwx 1 0 0 3 Jan 15 23:04 sbin -> bin
dr-xr-xr-x 16 0 0 0 Mar 17 19:56 proc
drwxr-xr-x 2 0 0 1024 Jun 2 1999 mnt
drwx------ 2 0 0 12288 Jan 15 23:04 lost+found
drwxr-xr-x 2 0 0 1024 Feb 9 2000 lib
drwxr-xr-x 3 0 0 1024 Sep 15 1999 etc
drwxr-xr-x 4 0 0 1024 Jan 15 23:04 empeg
drwxr-xr-x 2 0 0 1024 Jun 2 1999 drive1
drwxr-xr-x 6 0 0 1024 Mar 15 18:42 drive0
drwxr-xr-x 2 0 0 1024 Jul 4 2000 dev
drwxr-xr-x 2 0 0 1024 Jan 15 23:01 bin

I sure don't see where 13 GB of files could be hiding.

tanstaafl.
empeg:/#

Yeah, Yeah, The Lord already chastised me

what do you get if you do a ls -lR of / other than lots of text?

Do the "ls -R /" thing, and hit Ctrl-C after it spews out a few screenfuls of information.

Ha! The "-R" is case sensitive!

Here's what I got:

empeg:/# ls -R /
/:
bin drive0 empeg lib mnt sbin tmp var
dev drive1 etc lost+found proc swapfile usr

/bin:
badblocks dd fsck.ext2 init mkfifo nice ro sh sz
bash df grep insmod mknod od rom shutdown tar
cat diff gunzip ln mkswap ps rw stty tune2fs
chmod echo gzip ls more reboot rwm swapoff umount
cmp fdisk halt mkdir mount rm rz swapon userver
cp fsck hdstress mke2fs mv rmdir sed sync x

/dev:
audio empeg_state hda5 hdc1 hdc7 mixer ram2 tty1 usb
audioin hda hda6 hdc2 hdc8 null ram3 tty2 usb0
console hda1 hda7 hdc3 hdc9 radio random ttyS0 zero
display hda2 hda8 hdc4 ir radio0 rds0 ttyS1
dsp hda3 hda9 hdc5 kmem ram0 tty ttyS2
empeg_power hda4 hdc hdc6 mem ram1 tty0 urandom

/drive0:
drive1 fids lost+found var

/drive0/drive1:
fids lost+found var

/drive0/drive1/fids:
100 2020 3001 400 4fe0 5fc0 6ff1 7fe0 9050 a030 b010 c00 cfe0
1000 2021 301 4000 4fe1 5fc1 700 7fe1 9051 a031 b011 c000 cfe1
1001 2030 3010 4001 4ff0 5fd0 7000 7ff0 9060 a040 b020 c001 cff0
101 2031 3011 401 4ff1 5fd1 7001 7ff1 9061 a041 b021 c01 cff1
1010 2040 3020 4010 500 5fe0 701 800 9070 a050 b030 c010 d00
1011 2041 3021 4011 5000 5fe1 7010 8000 9071 a051 b031 c011 d000
1020 2050 3030 4020 5001 5ff0 7011 8001 9080 a060 b040 c020 d001
1021 2051 3031 4021 501 5ff1 7020 801 9081 a061 b041 c021 d01
1030 2060 3040 4030 5010 600 7021 8010 9090 a070 b050 c030 d010
1031 2061 3041 4031 5011 6000 7030 8011 9091 a071 b051 c031 d011
1040 2070 3050 4040 5020 6001 7031 8020 90a0 a080 b060 c040 d020
1041 2071 3051 4041 5021 601 7040 8021 90a1 a081 b061 c041 d021
1050 2080 3060 4050 5030 6010 7041 8030 90b0 a090 b070 c050 d030
1051 2081 3061 4051 5031 6011 7050 8031 90b1 a091 b071 c051 d031
1060 2090 3070 4060 5040 6020 7051 8040 90c0 a0a0 b080 c060 d040
1061 2091 3071 4061 5041 6021 7060 8041 90c1 a0a1 b081 c061 d041
1070 20a0 3080 4070 5050 6030 7061 8050 90d0 a0b0 b090 c070 d050
1071 20a1 3081 4071 5051 6031 7070 8051 90d1 a0b1 b091 c071 d051
1080 20b0 3090 4080 5060 6040 7071 8060 90e0 a0c0 b0a0 c080 d060
1081 20b1 3091 4081 5061 6041 7080 8061 90e1 a0c1 b0a1 c081 d061
1090 20c0 30a0 4090 5070 6050 7081 8070 90f0 a0d0 b0b0 c090 d070
1091 20c1 30a1 4091 5071 6051 7090 8071 90f1 a0d1 b0b1 c091 d071
10a0 20d0 30b0 40a0 5080 6060 7091 8080 910 a0e0 b0c0 c0a0 d080
10a1 20d1 30b1 40a1 5081 6061 70a0 8081 9100 a0e1 b0c1 c0a1 d081
10b0 20e0 30c0 40b0 5090 6070 70a1 8090 9101 a0f0 b0d0 c0b0 d090
10b1 20e1 30c1 40b1 5091 6071 70b0 8091 911 a0f1 b0d1 c0b1 d091
10c0 20f0 30d0 40c0 50a0 6080 70b1 80a0 9110 a10 b0e0 c0c0 d0a0
10c1 20f1 30d1 40c1 50a1 6081 70c0 80a1 9111 a100 b0e1 c0c1 d0a1
10d0 210 30e0 40d0 50b0 6090 70c1 80b0 9120 a101 b0f0 c0d0 d0b0
10d1 2100 30e1 40d1 50b1 6091 70d0 80b1 9121 a11 b0f1 c0d1 d0b1
10e0 2101 30f0 40e0 50c0 60a0 70d1 80c0 9130 a110 b10 c0e0 d0c0
10e1 211 30f1 40e1 50c1 60a1 70e0 80c1 9131 a111 b100 c0e1 d0c1
10f0 2110 310 40f0 50d0 60b0 70e1 80d0 9140 a120 b101 c0f0 d0d0
10f1 2111 3100 40f1 50d1 60b1 70f0 80d1 9141 a121 b11 c0f1 d0d1
110 2120 3101 410 50e0 60c0 70f1 80e0 9150 a130 b110 c10 d0e0
1100 2121 311 4100 50e1 60c1 710 80e1 9151 a131 b111 c100 d0e1
1101 2130 3110 4101 50f0 60d0 7100 80f0 9160 a140 b120 c101 d0f0
111 2131 3111 411 50f1 60d1 7101 80f1 9161 a141 b121 c11 d0f1
1110 2140 3120 4110 510 60e0 711 810 9170 a150 b130 c110 d10
1111 2141 3121 4111 5100 60e1 7110 8100 9171 a151 b131 c111 d100
1120 2150 3130 4120 5101 60f0 7111 8101 9180 a160 b140 c120 d101
1121 2151 3131 4121 511 60f1 7120 811 9181 a161 b141 c121 d11
1130 2160 3140 4130 5110 610 7121 8110 9190 a170 b150 c130 d110
1131 2161 3141 4131 5111 6100 7130 8111 9191 a171 b151 c131 d111
1140 2170 3150 4140 5120 6101 7131 8120 91a0 a180 b160 c140 d120
1141 2171 3151 4141 5121 611 7140 8121 91a1 a181 b161 c141 d121


and lots, lots more after that.

tanstaafl.

Hmmm... replying to my own post. How tacky...

/drive0/drive1/fids:
100 2020 3001 400 4fe0 5fc0 6ff1 7fe0 9050 a030 b010 c00 cfe0

Well, there's my files, in a subdirectory under /drive0. So, how do I move all the files in /drive0/drive1/fids to /drive0/fids?

tanstaafl.

someone check me on this:

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

Looks OK to me.

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/" ...