I have searched the faq and here and cant really find anything on this but any way I was prepairing a used drive for my empeg and got this error: Writing inode tables: done
Writing superblocks and filesystem accounting information: done

real 0m42.752s
user 0m0.300s
sys 0m2.230s
set_blocksize: b_count 1, dev ide0(3,4), block 1!
EXT2-fs error (device ide0(3,4)): ext2_check_descriptors: Block bitmap for group
64 not in group (block 2)!
EXT2-fs: group descriptors corrupted !
mount: wrong fs type, bad option, bad superblock on /dev/hda4,
or too many mounted file systems
hdstress.cpp 189 ( 19): Poll result=0 on fd=5
hdstress.cpp 189 ( 19): Poll result=0 on fd=5
Stressing /dev/hda: Spinning down.

What is that EXT2-fs error? and how do i fix it. I went ahead and installed b13 anyway to see what happens and it boots up but it has that same EXT2-fs error in the boot log: Tried to mount /dev/hda4 as reiserfs but got error 19
EXT2-fs error (device ide0(3,4)): ext2_check_descriptors: Block bitmap for group
64 not in group (block 2)!
Remounting filesystem read-only
EXT2-fs: group descriptors corrupted !
Tried to mount /dev/hda4 as ext2 but got error 22
Error mounting partitions (possibly already mounted)

everything else in the bootlog seems to look ok


UPDATE
Hmm.. now I m really confused, I did the whole thing over again starting with the developer image, and got the same error at first but them after installing beta13 the error went away, any ideas ? should I trust the drive?

It means your filesystem had become corrupted beyond the ability of the automatic check to noninteractively fix it. It looks like it did finally manage to fix itself by running the noninteractive check many times. This can happen, but I'd be more concerned about why it got corrupted in the first place? Did you have a failed sync recently? Sounds like you're not into hacking the empeg, so I doubt you manually mounted them read-write and then forgot to change it back to read-only, which would have otherwise been my first guess.

I am not shure what happend to this drive before I got it, I do know that the config file was so long on it that I am surprised that it booted at all, it had the old favorite visual bug it looked like to me, I would post it but it would take 3or 4 web pages to fit it all in, would that cause that kind of error? This is just a used second drive I got from the "for sale" section I figured I would pop it in and format it but I just wanted to see what was on it first, and then I found that. The funny thing is is that the error popped up after I formated it and the went away the second time I installed beta13.

the error popped up after I formated it and the went away the second time I installed beta13.

That was a mount-time error, not a fsck error. Running fsck (e.g. doing a sync) would probably have cleared it. Could it have been doing a sync that made it go away?

Peter

Well I never actually got to sync it before it went away so im not shure what happend. I went ahead and put it in my empeg with the other drive and all seems to be well, so I have no idea. The only wierd thing that I noticed is that since I put the second drive in when the player boots the hijack logo comes up and very very quickly goes to the rio loading screen and then back to hijack and the goes to rio and then plays, Its wierd you almost cant see it unless you watch for it.

The only wierd thing that I noticed is that since I put the second drive in when the player boots the hijack logo comes up and very very quickly goes to the rio loading screen and then back to hijack and the goes to rio and then plays

This is usually a symptom of a too-long hijack animation. The disk drives boot quickly enough so that Hijack isn't done playing the animation by the time the player software begins loading. Make a shorter animation.

Its just the standard hijack animation (like the one next to my name), I didnt change that. Thats why I thought it was wierd. Oh... it only seems to do it in the car also.

I've noticed that the car bootup is quicker than the home bootup. And the default Hijack animation may be a couple frames longer than the original 2.0 animation I made, not sure. But really I think the issue is that your drives are booting up faster than most other people's drives and that's the reason. So if you wanted, you could make a custom animation that was shorter than the default animation and the blinking problem would go away.

I have noticed the same symptoms with the same setup - I think it comes from a setting change I made in HiJack which allows for single disk only detect (faster boot). After I set to single disk, this "jitter" between the animation and the load screen occurred. If you return to Dual disk detect (slower boot), it goes away again.

The only problem with that is that I have two drives now

I guess I could make a custom animation, but can you take out the hijack animation and put it your own ? I didnt know you could change that one... hey I havent done much hacking of my empeg untill now, I just got up the nerve to add that new...err... um... used drive two days ago.

The only problem with that is that I have two drives now

You're misunderstanding how it works.

While the animation is playing, it's waiting for the drives to spin up and respond to the "init" command. If you have only one drive, it usually waits for quite a long time, to make sure there's not a second drive there that's just slow-to-start-up.

If you have two fast-booting drives, it doesn't have to wait as long as it would if there were only a single drive or two slow-booting drives.

For those who own a single drive, and they know what they're doing, and they don't want it to wait and look for a second drive, they can set the Hijack option to skip the wait-for-the-second-drive feature. This also results in a fast boot, similar to if you'd owned two fast-booting drives.


I guess I could make a custom animation, but can you take out the hijack animation and put it your own ? I didnt know you could change that one...

Yes, that animation will be completely replaced when you use Jemplode to put in a custom animation.

Oh, ok I did misunderstand what schofiel was saying, I will have too try jemplode for the animation. Any reson why it would only flick like that in the car though?

Any reson why it would only flick like that in the car though?

Yes, car booting is faster. Not exactly sure why, but I've noticed that.

Hmm ok that maks sense. I should probably ask this in a different post but since this post kinda went away from the origanal question anyway Ill ask it here, I have noticed that before I installed hijack the volume seemed to have a better response from the knob and the remote (faster), after hijack install it slowed down alot has anyone else noticed this? Dont get me wrong though I think hijack is great.

I don't think there is supposed to be a difference between the volume response between Hijack and the default software. Not with fairly recent versions of each, anyway. Unless, of course, you did some kind of IR translation tricks in Hijack.

hmm... wierd, its ver 300 of hijack with no mods and beta13 , there is definatly a difference before and after loading hijack, before hijack the vol steps very quickly moving by 5s after hijack it steps slowly counting by .05s

In the car, I don't think we bother waiting for the upgrader to make an appearance. This might account for it.

Ah, yes, that would explain it.

I finally got around to changing the boot up animation, I just put on the old empeg with tux one and no more flicking... you were right Tony. I guess the hijack one is just too long if your empeg boots up really fast, its funny how two drives boot up faster that one... because it doesnt have to wait for the second one when there isnt one.