Yea - I have a new 160 drive and it's crippled to 137.

Anyone know of a workaround (ext3 maybe?) and a dynamic partitioning app available that can bump the discbuilder partition up to the full 160?

Are you running hijack and did you build the drive manually?

Yeah, the trick is to do the disk-install steps manually, under a Hijack kernel, rather than using the limited builder image.

Someday.. someday..

To be honest, I like the manual way as opposed to the builder. I like being able to set up either extra partitions or larger swap areas. Plus the instructions from Roger are more optimized than the original builder's method.

Yea - I tried the discbuilder, it failed as expected and I built the disc via roger's steps. I'm guessing I missed something?

Is there any way to resize the partitions?

Hi All,

Got my 2 new drives today. Got the WD1200VEs. Installed and am using http://www.differentpla.net/node/199 and have completed it.

What about the 2nd drive? This procedure and this one: http://www.differentpla.net/node/200 seem to set up one drive. I have two...

How do I setup the 2nd new drive?

- Thanx
- Jon

Actually, I'm getting lots of errors when doing this http://www.differentpla.net/node/200

After issuing the "mount -n /dev/hdc4 /drive1" command, I'm getting lots of these errors:

end_request: I/O error, dev 03:44 (hdb), sector 62128128
EXT2-fs error (device ide0(3,68)): read_block_bitmap: Cannot read block bitmap -
block_group = 237, block_bitmap = 7766016
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x40 { UncorrectableError }, LBAsect=63385549, sector=6317
6704
end_request: I/O error, dev 03:44 (hdb), sector 63176704
EXT2-fs error (device ide0(3,68)): read_block_bitmap: Cannot read block bitmap -
block_group = 241, block_bitmap = 7897088

Are those just bad sectors?

- Thanx
- Jon

They are not just bad sectors. Those would be invisibly remapped by the drive, as I understand it. Those are errors that are getting back to the empeg. I'd check your cables and header. If it's not one of those, it's almost definitely the drive. You could check to see if you get similar errors with the other drive you said you have to set up.

On one of the drives, I am getting this at the end of the partition procedure:

Command (m for help): p

Disk /dev/hdc: 255 heads, 63 sectors, 14593 cylinders
Units = cylinders of 16065 * 512 bytes

Device Boot Start End Blocks Id System
/dev/hdc1 1 5 40131 5 Extended
/dev/hdc2 6 10 40162+ 83 Linux
/dev/hdc3 11 13 24097+ 10 OPUS
/dev/hdc4 14 14593 117113850 83 Linux
/dev/hdc5 1 3 24034+ 83 Linux
/dev/hdc6 4 5 16033+ 82 Linux swap

Command (m for help): w
hdb: read_intr: status=0x59
hdb: read_intr: error=0x01
hdb: read_intr: status=0x59
hdb: read_intr: error=0x01
hdb: read_intr: status=0x59
hdb: read_intr: error=0x01
hdb: read_intr: status=0x59
hdb: read_intr: error=0x01
ide0: reset: success
hdb: read_intr: status=0x59
hdb: read_intr: error=0x01
hdb: read_intr: status=0x59
hdb: read_intr: error=0x01
hdb: read_intr: status=0x59
hdb: read_intr: error=0x01
hdb: read_intr: status=0x59
hdb: read_intr: error=0x01
ide0: reset: success
hdb: read_intr: status=0x59
hdb: read_intr: error=0x01
end_request: I/O error, dev 03:40 (hdb), sector 48194

Unable to write /dev/hdc
empeg:/empeg/bin#

The other drive worked fine. Does this smell like a defective drive? Is there a way to be sure and wipe out the drive before starting the procedure so that I can be sure it's clean?

- Thanx
- Jon

It sounds defective to me, but I'll let people more expert at IDE stuff confirm.

Okay, I am putting together an updated builder image now. So far, I've replaced the kernel with Hijack, and turned on swap during the upgrade. What else needs to be different?

I suppose I can read through Roger's detailed guide and try to find out, but..

Once the final (tested?) version is complete, I'll likely provide the binary on (email) request, and otherwise publish a script to patch an original (copyrighted) builder image.

Cheers

I'm sure he could make it really really difficult to select accidentally.

Anyway, it'd be nice if there were a way to make an updated builder image as easily available as the current builder image: No emailing, no scripts to merge builders, etc.

Is there anything in the current builder that's so copyrighted that it can't be redistributed by Mark? What if you just took Mark's builder and put it on the Empeg.com site?

Disk partitioning would be a near-trivial add-on for Hijack. But the "formatting" part is much much bigger -- I'd have to include the mkfs.ext3 binary (executable) inside the kernel, and it wouldn't fit in the available flash memory space (unfortunately).

Best left as a separate image (heartily agreeing with Roger).

Anyway, I have an image with Hijack+swap, just wonder what else needed tweaking. How about the mkfs.ext3 options?

Cheers

think I'll hold out for the 1.46 TB 2.5 inch drive.

http://www.computerworld.com/action/arti...urce=rss_news50

240GB installed. Thanks to Tony for the upgrade coaching, Roger for the guides, and Matt for buying my old drives...

- Jon