Hi,

I checked this out with 2 each 250GB drives using v9 builder.

It looked like everything was going well. It completed the build of hda correctly. It created the proper inodes for hdb until the end of the process it asked the following question which I had a 50/50 shot at getting it wrong. The following list shows what happened....

+ DRIVE12=hdb5
+ logshow_message("Making ")
'Making '
+ echo 'Making '
Making
+ echo 'POPUP 9999 Making '
+ /bin/mkfs.ext2 /dev/
mke2fs 1.14, 9-Jan-1999 for EXT2 FS 0.5b, 95/08/09
/dev/ is not a block special device.
Proceed anyway? (y,n) y
ext2fs_check_if_mount: No such file or directory while determining whether /dev/
is mounted.
/dev/: Invalid argument passed to ext2 library while setting up superblock
+ /bin/swapoff /dev/
swapoff: /dev/: Invalid argument
+ /bin/swapoff /dev/hda3
+ /bin/swapoff /dev/hda6
+ log 'Done!'
+ echo 'Done!'
Done!
+ echoshow_message("Done!")
'POPUP 9999 Done!'
+ exec /bin/bash --login
bash-2.03#

It looks like it got an unexpected response.

The partitions appear to be built identical (correctly?)....

bash-2.03# cat /proc/partitions
major minor #blocks name

3 0 244198584 hda
3 1 1 hda1
3 2 40162 hda2
3 3 40162 hda3
3 4 244027350 hda4
3 5 24034 hda5
3 6 64228 hda6
3 64 244198584 hdb
3 65 1 hdb1
3 66 40162 hdb2
3 67 40162 hdb3
3 68 244027350 hdb4
3 69 24034 hdb5
3 70 64228 hdb6
bash-2.03#


Did I just answer wrong or is there a problem?

Mark, what do you think?

Thanks,

Ross

I wonder what I was smoking when I did that to the script?

Fixed in builder_bigdisk_v10.upgrade at the usual place.

Thanks for testing things!

I'll check it out.

Thanks again,

Ross

Hi,

Ahhh much better!

Once again the IDE_GUY proves that he is the "Master" and not the "Slave" of code.

It might be good when we are all done (very close now), that you sync the versions (like v10 for the builder and player software).

BTW, who's RobV? Anyway, Happy Birthday RobV.

Good job,

Ross

That would be Rob Voisey, who first emailed me on August 14, 2000:

Hi,

In case anyone is interested, here is some information about available music database size with the larger disks.


120 GB drive = 117 GB each for 234 GB total with Emplode

Drives like the Toshiba MK1234GAX, & Hitachi



250 GB drive = 232 GB each for 465 GB total with Emplode

Currently the only 250GB ATA-6 (IDE) drive I know of is the Western Digital WD2500BEVE (I was able to purchase a few for $125.00 US this week). I have not seen the reported boot problem that I have read on the web with either of the first 2 drives. These drives are available but not widely available and stil are inexpensive.


I really appreciate Mark for helping us have this additional capacity.

Thanks,

Ross

Hi,

Okay, got Ethernet working thanks for the Ethernet FAQ default addresses. The FAQs for the Empeg are really great!

One problem encountered though, I have to disable my Kerio Firewall for access to the Empeg (of course it is turned on right now and any time I am not syncing a music database).

I went into the Kerio allowed network access fields in the advanced options and added the new Address/Masks and still no luck.

Is anyone using Kerio and can point me to the correct method to allow the Rio to be excluded from the filters list or allow the network address?

Thanks,

Ross

Hi,

Any one using Kerio Firewall with an Ethernet connection?

I could use a little assistance with this if you are able to help.

Thanks,

Ross

I don't use Kerio Firewall anymore it was about 4 years ago when I stopped. You need to allow the local network but I don't know how since I don't use it anymore.

Hi,

I think I will just have to work this with Kerio. probably something that I'm stupid about again.

Thanks for replying,

Ross

Hi,

I checked with Kerio. They no longer support the Kerio Firewall that I have and sold it off to sun-belt. Deleted Kerio.

Bought Norton Internet Security 2008, that solved the problem.

Thanks,

Ross

Please remove all Norton software from your computer. It's got to be in the running for the worst software ever made. I've been using NOD32 for more than 2 years now and they just released SmartSecurity that has a Firewall built in. I haven't tried it since I use NAT.

Edited to add: I feel the same as Bob the Angry Flower does about Norton.

Yup. Got NOD32 here as well. Works well and it isn't a huge memory hog like Norton.

Agreed. NOD32 is really the best. Norton probably one of the worst. It entangles itself so deeply into your system, IMO it should be regarded as spyware.

The enterprise versions of Norton et al are usually better because they don't have the fancy UI and all the other crap bolted on.

Still pretty poor though: badly written cludge-together

I started using NOD32 a year ago, migrating from Norton business, and I've been happy with the performance. I recently upgraded to their Smart Security package (w. firewall), as I had been using the old Sygate Office Network firewall, which hasn't been supported in years since Symantec purchased it, for the purpose of eradicating its competition - the best software firewall on the market. NOD32's firewall is very unobtrusive and has all the configuration options I would want.

I had a disk crash in my Rio Car & have installed a new 250GB WD2500BEVE drive. I have tried using both builder_bigdisk_v3 & builder_bigdisk_v4, but either way when I install one of your tweaked upgrade installs (car2_v2.01_hijack.upgrade or car2_v3a11_hijack.upgrade) I end up with the same result:

The Hijack Vital Signs show:
Mk2aL 32MB 244GB

However, Emplode 2.1 or Jemplode 70 both show (and only allow me to fill up to) 128GB of space.

Since I actually removed both a good and a bad 80GB drive that were close to full, I cannot load all of my music back onto the player.

Help! (please)

I'm surprised by the emplode and jemplode issues you describe. That's the first I've heard anyone mention that happening.

Emplode 2.10 ... Well that's got known issues and shouldn't be used anyway. (only 2.00 is known to be stable.) But Jemplode should do just fine, so I'm surprised. First I'd look to make sure that the shell thinks you've got 250gb there. Vital signs might be reading the IDE hardware directly. I don't know the command required at the shell to show the disk size of drive0, but I'm sure someone here can help with that.

Next, if the shell really reports 250gb, then I'm curious about exactly what goes wrong with jemplode, i.e., exactly what you're loading and how, and exactly what error jemplode is giving.

Hi,

I've loaded up a lot of 250GB WD drives on multiple Mk2a's without problems.I have used the V2.01 Player Hijack Software with the big builder software that Mark Lords crafted. Haven't tried the latest Big-Builder for any size drives yet.

It ought to work. The 244GB on the Vital Signs is correct. When using Emplode (I haven't use J-Emplode), you should see the player capacity as 232GB for one drive and 465GB for 2 drives at the bottom of the GUI window. You could try Emplode.

If you have a lot of info (tags), in your playlists, you may have to adjust the cache reserve to prevent memory errors (mem err).

Anyone been successful with SATA drives yet. They are getting bigger...

Ross

Yeah. So I think that somehow, despite having used the bigdisk builder, his drive0 is still formatted to only 128gb.

What's the shell command to show the disk size at the shell prompt?

df

Peter

Yeah. There's a difference as to disk size (and partition configuration) and filesystem size. I assumed he was looking for filesystem size, but maybe not.

Well, really we need both, because as Tony says, one of our candidate diagnoses at this point is that the filesystem was somehow not created the full size of the disk.

Peter

It's probably the same old issue, of the builder refusing to build a drive that's already partially built.

So he's gotta wipe what's there, before the bigdisk builder will actually rebuild it.

Okay, in case that's the problem, I've now released bigdisk builder v6, which will unconditionally wipe out any existing installation.

Give that one a whirl.

Thanks for the feedback, but it sounds like I was doing everything by the book... so now I'm going to try the alternative route.

I just finished a manual partitioning and formatting of the 250GB drive on the Empeg. I am installing the car2_v2.01_hijack.upgrade now. Crossing my fingers...

-Ed

So far so good.. Jemplode 70 showing 232.54GB capacity!

I'm new onto this forum so please bear with me as I've not read this entire thread but I thought I might share my experience with upgrading my empeg with you anyway. My upgrade process was using the Windows software versions.

Empeg / RIO rebuild with multi-drives

This is my experience during a rebuild with 2x 250GB WD2500BEVE drives on Empeg MkII (sn 080000452).

Using builder_bigdisk_v6.upgrade

both drives initally connected as master/slave

failed to find drives (bad pump) when both drives connected
unplugged drive on end of cable (slave) - then success

unplugged first drive - plugged in 2nd drive on the end of the cable - failed
plugged 2nd drive to first cable point - failed

changed jumpers to make 2nd drive master and plugged it back in on the end of ribbon - success

hence drive needs to be master to work, ribbon point not relevant
hence with 2 drives you must do them one at a time

Whilst each drive is plugged in individually and set to master then run the software installer.
hence for 2 drives you should repeat the process.
used car2_v2.01_hjack.upgrade

Note - even as Master the drive now needs to be on the first ribbon connection (not the end) or it fails

Once complete for both drives, connect both as master/slave and it works fine.
Capacity found as 360GB