Unoffical empeg BBS

Quick Links: Empeg FAQ | Software | RioCar.Org | Hijack | jEmplode | emphatic
Repairs: Repairs | Addons: Eutronix | Cases

Topic Options
#362359 - 10/08/2014 21:07 Superblock issue. Stuck on building music databases
Empeg User
new poster

Registered: 10/06/2011
Posts: 13
I have a mkIIa unit that I haven't had any issues with until recently, when I upgraded from a 100gb Fujitsu drive to a white label 320GB pata drive with a model # HM321HC.

The unit is currently running 2.01 Developer version and has Hijack 5.18 installed. I was able to use the big disk builder v6 to get the drive set up
so that Emplode would see the correct capacity.

After doing over 10 or so syncs, I had an error while doing a final sync with Emplode. I'm unable to use Emplode or Jemplode with the player, as they reboot the player and times out while the "Building music databases..." step is processing. (Takes 25 min or so)

I checked rio car dot org and tried all of the different suggestions for using fsck and e2fsck to try and fix the partition. I'm getting this error:

"The filesystem size (according to the superblock) is 78116062 blocks
The physical size of the device is 33527655 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort? yes

Any ideas?

Top
#362361 - 11/08/2014 04:29 Re: Superblock issue. Stuck on building music databases [Re: Empeg User]
tfabris
carpal tunnel

Registered: 20/12/1999
Posts: 30696
Loc: Seattle, WA
Not sure if this is the issue or not, but there is mention of superblock errors in the FAQ but it's spelled with a hyphen:

http://www.riocar.org/modules.php?op=mod...;faqent=162#162

FAQ was mostly based on Mark's help in this thread:

http://empegbbs.com/ubbthreads.php/ubb/showflat/Number/328414

See if the info in there is helpful?
_________________________
Tony Fabris

Top
#362363 - 11/08/2014 09:08 Re: Superblock issue. Stuck on building music databases [Re: Empeg User]
Empeg User
new poster

Registered: 10/06/2011
Posts: 13
I did read up on those FAQ's already. I had gotten the magic number error on occasion with fsck, and the filesystem physical size mismatch error with fsck.ext2

These are the following values that I've tried for the superblock:

24576
24577
32769
98304
98305
163841
229377
294913

None of these produce a different result.
I used the big disk builder v6 when creating this drive.

Top
#362364 - 11/08/2014 10:00 Re: Superblock issue. Stuck on building music databases [Re: Empeg User]
peter
carpal tunnel

Registered: 13/07/2000
Posts: 4141
Loc: Cambridge, England
The filesystem size (according to the superblock) is 78116062 blocks
The physical size of the device is 33527655 blocks


It's only seeing 128GB of the 320GB drive. Are you dead sure Hijack is running? You might see that problem if you booted the stock kernel (which doesn't understand LBA48).

Peter


Edited by peter (11/08/2014 10:00)

Top
#362365 - 11/08/2014 10:29 Re: Superblock issue. Stuck on building music databases [Re: Empeg User]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13564
Loc: Canada
Yeah, really sounds like it doesn't have a Hijack kernel installed, or didn't have one at some point earlier (such as during the disk build).

Top
#362367 - 11/08/2014 10:52 Re: Superblock issue. Stuck on building music databases [Re: Empeg User]
Empeg User
new poster

Registered: 10/06/2011
Posts: 13
It's possible it didn't have it during the disk build. Does this mean I'm possibly screwed and should start all over? Or is there something that can be done at this point.

This is the sequence of what I did successfully in the beginning:

1. Car2 Builder V3
2. Builder Bigdisk V6 - (Hijack installed???)
3. Car2 2.01 w/hijack preinstalled

I went through many combinations of different images to get the Empeg up and running with the full 320GB. Originally I started with a the bigdisk v6 and the player only ended up being able to see 128GB. Only when I did the sequence shown above did it work and show the full amount.

I'm assuming Bigdisk V6 has hijack integrated since Mark released it.

Top
#362368 - 11/08/2014 10:53 Re: Superblock issue. Stuck on building music databases [Re: Empeg User]
Empeg User
new poster

Registered: 10/06/2011
Posts: 13
Just to clarify, Hijack 5.18 is currently installed at the moment.

Top
#362369 - 11/08/2014 11:15 Re: Superblock issue. Stuck on building music databases [Re: Empeg User]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13564
Loc: Canada
Quote:
The filesystem size (according to the superblock) is 78116062 blocks
The physical size of the device is 33527655 blocks


So at present, Hijack is installed, and all 320GB (33527655 blocks, where each block is 1024-bytes) is visible at the lowest layers. But the upper filesystem layer says the filesystem was formatted as if the drive was some completely different size, indicating that perhaps Hijack was not present while the formatting was done.

Time to start over. First wipe the drive: serial port, hit control^C, and do this to "unformat" everthing:

dd if=/dev/zero of=/dev/hda bs=512 count=3000

Then do the bigdisk builder procedure (yes, Hijack is included), and then reinstall the car2-developer image with Hijack included.

Top
#362370 - 11/08/2014 11:23 Re: Superblock issue. Stuck on building music databases [Re: Empeg User]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13564
Loc: Canada
The reason for all of the fuss about Hijack here, is that the stock empeg kernel was produced back when hard drives were all much, MUCH smaller than the LBA28 limit of 128GB. So the stock empeg kernel predates large drives, and is unable to correctly deal with them. Whereas Hijack has been continuously maintained since its inception, and includes LBA48 (big disk) support.

I think maybe the v3alpha kernel also has LBA48 support, but possibly still buggy.

Top
#362371 - 11/08/2014 11:41 Re: Superblock issue. Stuck on building music databases [Re: Empeg User]
peter
carpal tunnel

Registered: 13/07/2000
Posts: 4141
Loc: Cambridge, England
The blocks in question are 4K I think: 33527655*4096 is just short of 128GB, whereas 78116062*4096 is just short of 320GB (decimal).

Peter

Top
#362372 - 11/08/2014 12:16 Re: Superblock issue. Stuck on building music databases [Re: Empeg User]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13564
Loc: Canada
Yeah, you might be correct there. I do get confused about the various ambiguous uses of "block". smile

But it does normally mean 1024 bytes for most purposes, and given there's a Hijack kernel installed right now that is reporting 33527655 blocks as the size, I think it does mean 1024-bytes (320GB total) for that line at least. Which approximates the physical drive size.
Naw.. You're probably right!

The other number could just be the modulo-128GB value that was created when building the filesystem without LBA48 support.

Cheers



Edited by mlord (11/08/2014 12:21)

Top
#362373 - 11/08/2014 14:45 Re: Superblock issue. Stuck on building music databases [Re: Empeg User]
tfabris
carpal tunnel

Registered: 20/12/1999
Posts: 30696
Loc: Seattle, WA

Originally Posted By: Empeg User
It's possible it didn't have it during the disk build.


But you said you used Mark's Big Disk Builder?

Just trying to make sure that my disk upgrade instructions aren't wrong or something. Mark, shouldn't running the Big Disk Builder be enough in this case? If he thought he ran the Big Disk Builder, then what other step might have gone wrong? Is there something I should clarify in the disk upgrade guide?
_________________________
Tony Fabris

Top
#362374 - 11/08/2014 15:49 Re: Superblock issue. Stuck on building music databases [Re: peter]
Empeg User
new poster

Registered: 10/06/2011
Posts: 13
Thanks for all of the advice. This time around I ran the command provided by mark to wipe the drive. Then I used the Bigdisk 6 and the 2.01 w/hijack. Emplode shows 298GB free and I'm now testing a sync. Everything looks good so far.

I did use Marks big disk builder previously and for some reason I was having some sort of an issue with the full drive space not showing up. This is why I ran the regular builder and then the big disk builder. I think wiping the drive completely might have helped this time around.


Edited by Empeg User (11/08/2014 15:49)

Top
#362375 - 11/08/2014 16:24 Re: Superblock issue. Stuck on building music databases [Re: Empeg User]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13564
Loc: Canada
Yeah, hopefully that was the issue.

The builder images, including my big disk ones, try to be careful not to wipe an existing music collection. So one does need to pay very close attention to the messages from them to see if they really did what one expected. smile

Running the big disk builder after the regular builder probably doesn't work without an interim disk wipe. Or does it? I did try and address that once, but..

Cheers

Top
#362380 - 17/08/2014 10:30 Re: Superblock issue. Stuck on building music databases [Re: mlord]
Empeg User
new poster

Registered: 10/06/2011
Posts: 13
Running the big disk builder after the regular builder does in fact work. However, it may not work very well.

I thought everything was well after doing the wipe > big disk builder 6 > mkIIA 2.01 software w/hijack. Unfortunately, my first sync had an error at the very end. (after 3 days of syncing)

"Synchronize failed while writing player configuration. An operation was attempted on something that is no a socket. (error 0x80072736)"

The player is displaying this: 0000.0 segfault err

I only uploaded 180GB of music to the player, and there is 110GB free still. What could be the issue?

I used ethernet, and also a direct connection with the computer rather than going through a switch.


Edited by Empeg User (17/08/2014 10:32)

Top
#362381 - 17/08/2014 11:15 Re: Superblock issue. Stuck on building music databases [Re: Empeg User]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13564
Loc: Canada
Depending how many tracks you are uploading, you could well be hitting one of the other software limits of the device.

How many unique tracks?

Top
#362385 - 17/08/2014 13:05 Re: Superblock issue. Stuck on building music databases [Re: Empeg User]
Empeg User
new poster

Registered: 10/06/2011
Posts: 13
About 85,000 unique tracks. Is this too many? What is the upper limit? Can this limit be circumvented?


Edited by Empeg User (17/08/2014 15:50)

Top
#362388 - 17/08/2014 15:50 Re: Superblock issue. Stuck on building music databases [Re: Empeg User]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13564
Loc: Canada
Yeah, that passes a few soft limits. Most likely it just ran out of memory trying to keep track of them all. The stock 16MB (RioCar Mk2a) tends to have troubles with large collections.

I think the Empeg FAQ has suggestions on dealing with that, including manually enabling swap space before doing the sync. That way makes extra virtual memory available to supplement the physical RAM.

Cheers

Top
#362422 - 24/08/2014 13:21 Re: Superblock issue. Stuck on building music databases [Re: mlord]
Empeg User
new poster

Registered: 10/06/2011
Posts: 13
I found all of the threads regarding fidsift and set_empeg_max_fid, and will be trying both of those methods. However, I could not find anything on changing the swap size on this board or riocar.org.

How does one do this, and do it safely?

Top
#362423 - 24/08/2014 16:41 Re: Superblock issue. Stuck on building music databases [Re: Empeg User]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13564
Loc: Canada
I don't think there's any need to change the swap size. Just need to ensure it is enabled during the sync.

Top