I finally got around to building the drive in the MKlla tonight and then I loaded the MKl software, seems to be fine. Now I want to copy a 5GB drive on to the 80GB. All this room, I better get busy on uploading some music to it and buying more CDs to rip.

I want to thank Tony again for the wonderful drive upgrade guide. I was able to copy the drive I wanted to very easily, ok, so it took me a few times to get the spaces exact on the command line, but when I did, away it started copying.

You're quite welcome!

I'm debating whether or not to add your "run builder on a Mk2" trick to the upgrade guide or not. I'm hoping there's some kind of another good work-around that doesn't require a Mk2 player to get the job done...

It would be nice to be able to upgrade without having to have a MKll to use. Some people don't have both models to play around with. Maybe someone will come up with a work around in the near future.

empeg could change the builder image to use the swap partition they've just created. That should solve the problem but I doubt it would be very fast.

- Trevor

Seeing as how the builder image is in need of an update anyway (to incorporate the greater-than-127-mb changes to the kernel), I'm hoping that they can release a new builder image as part of the 3.0 beta, and then I won't need to updated the D.U. Guide.

Damn. I just got an 80gb problem and I'm getting this same error, but on a Mk2. Is it possible that with an 80gb drive it needs the extra 4mb found in a Mk2a? I was hoping to do the drive upgrade using my Mk2 so I don't have to sacrifice my Mk2a until the last minute (when I copy over the dynamic data partition et. all.)

Or is there some other cause of this? I've tried using both builder images (the "outdated" one and the "test" one.)

Greetings!

It is right on the borderline. What you might want to do is just open the Mark2A, disconnect the drives that are in it, and hook the new 80GB drive up. Do the build there, and then reapply 2.0 and hijack on the 2A. Disconnect the new drive, reconnect your existing ones. This will leave your Mark2A with the newly loaded 2.0 and hijack, but with all of your old configuration and music data. It will also give you a pre-built disk that you can drop in the Mark2... Note - you will need to install 2.0 and hijack on that Mark2 as well.

It is right on the borderline.

Right past the borderline, it seems. Throwing my 80gb drive into my Mk2a did the trick. I suppose I could have switched it back to my Mk2 for the sync process (keeping my Mk2a active with the old disk drives in it) but I just bit the bullet and went without an empeg for a couple days. I synced about 2/3 of my collection last night and began the rest of it this morning, hopefully it'll be done by the time I get home tonight.

BTW I suggest to anyone who's starting over and syncing their entire collection definitely avoid having v3 alpha on their player when they do it. I had absolutely no success syncing using v3 alpha, but once I flashed back to 2.0b13 everything worked great. Seems to me one can be semi-confident in using v3 alpha for small syncs (5 or 10 albums) but anything beyond that seems beyond its abilities.

Heya, sorry to bring an old old thread to live...

I just got a nice 80gb Hitachi for my Mark 1 and I'm having trouble building the drive, as Laura had in this thread earlier. Now I'm wondering if there is another solution than building the drive in a MK2 or MK2a, since I don't really have one to build in.
I was wondering if it could be possible to build the disk in my PC (workstation with 3.5 -> 2.5 adapter or a laptop)? Then there should be enough RAM for the process

Any hints?
MLord suggested in this thread

In reply to:

---

mkswap /dev/hda6
swapon /dev/hda6
mke2fs /dev/hda4 <--- Peter can tell us the exact parameters to use here

---

Is this working? Didn't test it yet...
I wonder also that there's no mentioning of the problem anywhere handy, not in the Drive upgrade document and I really worked to find even this thread through the millions of posts in this forum d=/

Hopefully someone can give me some hints fast, my Empeg is opened on my table and I'd like to get it on the road a.s.a.p. d=)

- d3

Certainly doable - if you have a machine that runs Linux (if not, a boot floppy or boot CD is useful - like tomsrtbt and Knoppix)

You need to create the same partitioning scheme as the builder would. For sizes (except the music drive - use all that is left over) look at the existing partitions on your current drive.
I think the parameters to use for the mkfs command when creating the file system on the music partition (to get the proper space per inode ratio) have been stated previously here on the BBS...

/Michael

Ok so there is still some hope for the big drive d=I

Umm, I can't really create partitions from Linux, I would really need specified help/commands for the job. And I don't have Linux installed anywhere, but I do have Knoppix laying somewhere...
But could I do this all inside the empeg since I can get into the shell of the developer image?

Well, I need to do some more searching on the bbs... But hope you guys can help me some out more.

Well, I need to do some more searching on the bbs... But hope you guys can help me some out more.


I'll bet that if you asked, you'd have 10 volunteers inside of six hours who would be happy to build your drive for you if you were to mail it to them. With transit time it might take a week, but would be a painless, sure-fire method of getting the job done.

tanstaafl.

I'll bet that if you asked, you'd have 10 volunteers inside of six hours who would be happy to build your drive for you if you were to mail it to them. With transit time it might take a week, but would be a painless, sure-fire method of getting the job done.

But where's the fun and education in postal services?! Plus being a week (or more) in a silent car? *phew* Are you out of your mind?!
I'm living in Finland and with my experience from the postal service, I really wouldn't trust my harddisks for them to handle d=/

But could I do this all inside the empeg since I can get into the shell of the developer image?

Well, no. That's the problem: not enough memory in the empeg. You'll need to connect it to a PC (as you already suggested) and figure out the correct commands.

figure out the correct commands

Watch this space, coming right up...

Partitioning your empeg: http://www.differentpla.net/node/view/199
Formatting your empeg: http://www.differentpla.net/node/view/200

Alright! Go Roger!
Thanks dude!

I think this info should be added to the FAQ / Drive upgrade guide, agreed?

I'll post the results here, hopyfully I manage to do this d=)

Formatting your empeg: http://www.differentpla.net/node/view/200

I'm pretty sure the builder, at least these days, uses "-s 1" and no "-b" option -- in other words, just like the second command-line you give. Older builders might have done it differently, but "-s 1" is little short of essential on vast modern drives.

Peter

I'm pretty sure the builder, at least these days

Those commands build the disk in exactly the same way as the "Test Builder Image (2001/10/22)", that I just downloaded, does.

It seems that the builder file on www.empeg.com should be updated to use the better scheme. It uses an earlier version of mke2fs anyway -- possibly explaining the difference (maybe the defaults have changed).

I've updated my page to emphasise the preferred command.

I'm living in Finland

Woah! Finally another countryman here!

Woah! Finally another countryman here!

Heh, finally?-) I've been here for a quite time... I think I got my Empeg in 2001. Registered to bbs about that time, might been '02?

Ok,

Now I've been copying the fids from the old 10gb drive for 2 hours and it's finally done. Now starting to copy the 20gb drive there also d=/ Maybe it's then 2x the time, 4 hours?

I'm not sure if things were quite right, here's something from the bootup that I don't understand:


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
Tried to mount /dev/hdc4 but got error 15
Error mounting partitions (possibly already mounted)
Remounting first music partition read-only
Remounting second music partition read-only
No secondary hard disStarting player
player.cpp : 385:empeg-car 2.00-beta13 2002/07/24.
! tags.cpp : 61:Failed to open tags (0xc0041002).

Sorry about the hyperterminal scramble... What does the line 'Tried to mount /dev/hda4 as reinsefs but got error 19' mean?

I did get something odd as a result from Formatting the music partition -section. Everything else just as the guide tells, but after the Writing superblocks thingie there was something more. Stupid of me didn't capture it.... But I just shrugged, didn't look at all too serious

Also funny that I couldn't access the Empeg with Emplode when the new drive was plugged, crashed when building the database I believe. Lack of fids? Builder does more than the manual style?

What does the line 'Tried to mount /dev/hda4 as reinsefs but got error 19' mean?

Added a FAQ entry just for you, and the other thousand people who ask that question.

Damn. Then my unit must be ok!
(Don't tell anyone I didn't really search the FAQ for that one because I thought it was related to the manuallybuildingthedrive)

Well, I guess I'll have to get up early tomorrow, just to check on my Empeg that everythings copied ok and reassembly the unit so I can try it in the production environment!

Heh, finally?-) I've been here for a quite time...

But being quiet in the best Finnish tradition?

Heh, finally?-) I've been here for a quite time...

But being quiet in the best Finnish tradition?

shhh.. not that loud.
Talkative only when I have problems, or when I'm drunk. Often both.

Talkative only when I have problems, or when I'm drunk. Often both.

Now why does that remind me of Night On Earth

I'll post the results here, hopyfully I manage to do this d=)

Ok, partitioned and formatted the 80gb drive according to Roger's guide. Copied everything from the old drives to the new one. I have only the new drive plugged in now, the two old drives are on my desk. All the songs show correctly in the Empeg, plays in the car etc.

Problems:
- Can't access the Empeg via Emplode. Emplode crashes after Rubuilding the databases.
- Everything Empeg is rebooted it will Rebuild the databases. Even incar, takes ~2 minutes... I was wondering if there went something from in the mke2fs -part of the hda4 formatting After the format it said that partition is checked after 30 (or was it 60?) mounts or 180 days, whichever occurs first.

Hints for these issues? Empeg is Mark 1 with 2b13, no Hijack. Emplode is 2.0. Haven't yet tried with my desktop computer, this all was done with the laptop.

Can't access the Empeg via Emplode. Emplode crashes after Rubuilding the databases.

Can you get a serial log from the player, and a log from emplode (under Options/Troubleshooting)? Post them as an attachment here (ZIP 'em if you need to).

Everything Empeg is rebooted it will Rebuild the databases. Even incar, takes ~2 minutes...

This is because emplode's failing to rebuild the database. This is a FAQ.

...in the mke2fs -part of the hda4 formatting After the format it said that partition is checked after 30...

Unrelated.

I'll try putting some music on my newly-formatted player with emplode, and see what happens.

Aren't you glad I've got a spare player?