61: failed to open tags...

Posted by: Ladmo

61: failed to open tags... - 12/07/2005 18:41

anyone know what THAT means, and how to fix?
Thanks

Posted by: tman

Re: 61: failed to open tags... - 12/07/2005 18:42

At a guess it's probably the tags file which is part of the database kept on the empeg.

Posted by: philb

Re: 61: failed to open tags... - 12/07/2005 19:23

I upgraded my v2 empeg to alpha10 last night, now it rebuilds the database every time it boots, and I get the 61: failed to open tags message on the console. Neither emplode/jemplode will connect to it now :-(
Are there some files I need to delete to get the database to rebuild correctly?

Posted by: tfabris

Re: 61: failed to open tags... - 12/07/2005 20:47

Quote:
Are there some files I need to delete to get the database to rebuild correctly?

Yes. The procedure for doing this is in the FAQ, which is down at the moment (server trouble).

You could simply try synching once with emplode (2.0 final please), and see if that fixes it. If not, we need the FAQ procedure, which I do not have memorized.

Posted by: Ladmo

Re: 61: failed to open tags... - 12/07/2005 22:59

I have an old copy of the faq...hard copy. Cannot find anything about tags. Found someother stuff which has not worked yet...If I just reload the player software and hijack, will that wipe out the music on the player, and I have to start from scratch?
I cannot get emplode or jEmplode to see the player in this state, can only use hyperterm to get to it. Well I can try the usb connnection to try to get to the player, but doubtful. Just hangs on that rebuilding the music databases...should I post the serial log stuff from the hyperterm startup session?
Thanks

Posted by: SonicSnoop

Re: 61: failed to open tags... - 12/07/2005 23:05

The section I believe Tony is refering to in the faq is the part about connecting to the player with hyperterminal and issuing the ro command and then the various e2fsck commands on the differnt partitions *again the faq is down so I cant be more specific*

Posted by: Ladmo

Re: 61: failed to open tags... - 12/07/2005 23:09

Yeah, I got that part, but I only have two different sets of commands and neither of them worked, but I may not have done them correctly. Does it take an increadabley long time for the last part of those commands?

Posted by: SonicSnoop

Re: 61: failed to open tags... - 12/07/2005 23:18

I wouldnt try this until one of the experts on here comment on it but once I had an issue with database building and had to delete the 3 files in /drive0/var/ think they were database3 playlists and tags, but my problem may not have been the same issue your having so may not be needed...

Posted by: Ladmo

Re: 61: failed to open tags... - 13/07/2005 00:41

Here is my serial log, if anyone has any idea/suggesion...
*************
If there is anyone present who wants to upgrade the flash, let them speak now,JSA-210, 9590MB w/384kB Cache, CHS=19485/16/63
or forever hold their peace...it seems not. Let fly the Penguins of Linux!=38760/16/63

e000 v1.04h driver i
Copying kernel...
Calling linux kernel...on 0x3349
Uncompressing Linux..................................... done, booting the kerne

SMC9194: SMC91C94(r:9) at 0x4008000
l.Q:
Linux version 2.2.14-rmk5-np17-empeg52 (rob@aphex) (gcc version 2.95.3 20010315

(release)) #11 Tue Apr 1 18:49:59 BST 2003
Processor: Intel StrongARM-1100 revision 11
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel C
Dentry hash table entries: 2048 (order 2, 16k)
Buffer cache hash table entries: 16384 (order 4, 64k)
Page cache hash table entries: 4096 (order 2, 16k)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP0001106 (hugo@empeg.com)
TCP: Hash tables configured (ehash 16384 bhash 16384)re is anyone present who wants to upgrade the flash,
IrDA (tm) Protocols for Linux-2.2 (Dag Brattli)
Linux-IrDA: IrCOMM protocol ( revision:Tue May 18 03:11:39 1999 )s of Linux!
ircomm_tty: virtual tty driver for IrCOMM ( revision:Wed May 26 00:49:11 1999 )lling linux kernel...
Uncompressing Linux...............
Starting kswapd v 1.5 done, booting the ke
SA1100 serial driver version 4.27 with no serial options enabled
l.
Linux version 2.2.14-rmk5-np17-empeg52 (
ttyS00 at 0xf8010000 (irq = 15) is a SA1100 UART
ttyS01 at 0xf8050000 (irq = 17) is a SA1100 UART:49:59 BST 2003
ttyS02 at 0xf8030000 (irq = 16) is a SA1100 UARTn 11

empeg dsp audio initialisedrial number 10101787)
empeg dsp mixer initialised
empeg dsp initialisedm
empeg audio-in initialised, CS4231A revision a0
Memory: 15
empeg remote control/panel button initialised.2k data, 4k init)
empeg usb initialised, PDIUSBD12 id 1012
Dentry hash table entries: 2048 (or
empeg state support initialised 0089/88c1 (save to d0004f80).er cache hash table entries: 16384 (order 4, 64k)
empeg RDS driver initialised
Page cache hash
empeg power-pic driver initialised (first boot)
POSIX con
RAM disk driver initialized: 16 RAM disks of 4096K size
Linux NET4.0 for Linux 2.2
empeg single channel IDEersit
ircomm_tty: virtual tty driver for IrCOMM ( revision
empeg-flash driver initialized
smc chip id/revision 0x3349
Starting
smc9194.c:v0.12 03/06/96 by Erik Stahlman (erik@vt.edu)ersion 4.27 with no seria
b
Partition check:
hda: hda1 < hda5 hda6 > hda2 hda3 hda4
hdb: [PTBL] [2432/255/63] hdb1 < hdb5 hdb6 > hdb2 hdb3 hdb4
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 320 blocks [1 disk] into ram disk... done.
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
empeg-pump v0.03 (19980601)
Press Ctrl-A to enter pump...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 2003/04/01.
! tags.cpp : 61:Failed to open tags (0xc0041002).

Posted by: mlord

Re: 61: failed to open tags... - 13/07/2005 01:07

Delete /empeg/var/database*, /empeg/var/tags, and /empeg/var/playlists, and then do a sync from Emplode.

-ml

Posted by: Ladmo

Re: 61: failed to open tags... - 13/07/2005 02:36

I typed in rm /empeg/var/database*
and the others, and it said that file did not exist...
What am I doing wrong?
Thanks

Posted by: Mataglap

Re: 61: failed to open tags... - 13/07/2005 03:40

are you remounting the filesystem rw? see if you have a 'rwm' command. don't forget to remount it read-only when it's all done.

go to the shell
'rwm'
remove the files (DO NOT delete config.ini)
'exit' & watch player rebuild the db.
when it's done go back to the shell
'rom'
'exit'

--Nathan

Posted by: mlord

Re: 61: failed to open tags... - 13/07/2005 10:42

You are doing nothing wrong.

Just do those commands and then tell Emplode to "sync". Wait (and wait..) for it.

Then sync it again.

Posted by: Ladmo

Re: 61: failed to open tags... - 13/07/2005 11:15

Mark, it tells me that those files dont exist.
I'm ready to start over from scratch, if I can find that darn disk builder software...didn't notice it on the empeg.com site, unless they are just calling it something different...
Thanks

Posted by: pgrzelak

Re: 61: failed to open tags... - 13/07/2005 11:18

If they do not exist, that is not an issue. Continue following the steps. The commands merely deleted the probably defective database. If the files are not there, that is one less step you need to do. Just continue the exit and rebuild as before.

Posted by: Ladmo

Re: 61: failed to open tags... - 13/07/2005 11:35

Too late...I only had about 25 gig of music on the player. I have done so much crap it is trashed pretty well...now I need to just start over...

Posted by: tfabris

Re: 61: failed to open tags... - 13/07/2005 14:44

Quote:
The section I believe Tony is refering to in the faq is the part about connecting to the player with hyperterminal and issuing the ro command and then the various e2fsck commands

No. I was talking about the section that describes how to manually rebuild the database files.

Posted by: SonicSnoop

Re: 61: failed to open tags... - 14/07/2005 00:37

my bad..

Posted by: AndrewT

Re: 61: failed to open tags... - 14/07/2005 06:42

Quote:
Quote:
The section I believe Tony is refering to in the faq is the part about connecting to the player with hyperterminal and issuing the ro command and then the various e2fsck commands

No. I was talking about the section that describes how to manually rebuild the database files.

Perhaps it might be helpful to include a note in the FAQ on error number 0xc0041002? After loading v3 aplha 10, my player started giving this error in Emplode and searching the FAQ for this number didn't produce any hits.

Posted by: Roger

Re: 61: failed to open tags... - 14/07/2005 09:43

Quote:
error number 0xc0041002?

Well, the 0x means it's in hex. The c means it came from the player. The 004 is reserved (it's actually Win32's FACILITY_ITF). The 1 is the player component (in this case, the main player code -- the audio path has a different ID, some of the libraries use different IDs again). The 002 is ENOENT.

File not found, in other words.

Posted by: jbauer

Re: 61: failed to open tags... - 19/08/2005 21:49

I'm getting this error also... Failed to open tags (0xc0041002).

I think I may have caused the problem by copying more mp3 files than I could fit on the player. Now, when I boot the player, it has to rebuild the database, and when I try to load emplode, it does a disk check and then emplode fails without an error code. I get this message when it starts the integrity check:

Adding Swap: 16028k swap-space (priority -1)
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
ext2fs_check_if_mount: No such file or directory while determining whether /dev/
hda4 is mounted.

So 2 questions:

1) Do I need to delete my databases as outlined above in this thread?
2) Does this happen if I overfill my empeg every time? This isn't very graceful...

- Thanx
- Jon

P.S. I'm using 2.0 release version.

Posted by: pgrzelak

Re: 61: failed to open tags... - 20/08/2005 13:20

Delete and manually rebuild the databases, and then try to apply the max_fid patch that Mark wrote. This has done wonders for when I overfill my player...

Posted by: jbauer

Re: 61: failed to open tags... - 20/08/2005 23:09

Ok, I think I got the original problem fixed, but now I'm getting...

Prolux 4 empeg car - 2.1434 Mar 26 2003
Vcb: 0x408d7000
serial_notify_thread.cpp: 116:@@ N7
serial_notify_thread.cpp: 117:@@ F0x53da0
serial_notify_thread.cpp: 118:@@ TThere's No Home For You Here
serial_notify_thread.cpp: 119:@@ AWhite Stripes
serial_notify_thread.cpp: 120:@@ GRock
serial_notify_thread.cpp: 180:@@ #53da0 0:00:00
serial_notify_thread.cpp: 170:@@ S0

The weird thing is that I've deleted the album that contains the track that this is referencing. Could it be that I have a track that's dangling with no reference in the FID's or somethin'?

- Jon

Posted by: pgrzelak

Re: 61: failed to open tags... - 21/08/2005 10:48

It is happening all the time? I would recommend the following possible tests / fixes...

a) start the player with a -i and see if you can select another playlist
b) search for the deleted file with refs=0
c) look at the playlist you are currently running to see if it has the reference
d) fsck

Posted by: jbauer

Re: 61: failed to open tags... - 22/08/2005 21:45

Grrr. I'm back to the empeg re-building the database every time it boots up...

When I look in the /drive0/var directories, I only find one file, in the /drive0/var directory. Nothing else in any of these (from the faq)...

rm /drive0/var/database
rm /drive0/var/database3
rm /drive0/var/tags
rm /drive0/var/playlists
rm /drive1/var/database
rm /drive1/var/database3
rm /drive1/var/tags
rm /drive1/var/playlists

So does this mean that it's not able to successfully build the databases? Could I be completely out of space?

I also get:

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 2003/04/01.
! tags.cpp : 61:Failed to open tags (0xc0041002).

What's that "tried to mount" message???

- Jon

Posted by: mtempsch

Re: 61: failed to open tags... - 23/08/2005 03:20

Quote:

What's that "tried to mount" message???

Perfectly normal - the software first tries to mount the partition as a reiserfilessystem, but as it isn't a reiserfs (it's ext2) it fails and then goes on to mount it as an ext2 filesystem.

Have you tried clearing and rebuilding? A manual fsck might be an idea as well, just to be sure the filesystems are OK.

Posted by: pgrzelak

61: failed to open tags...