Have you checked to see how big NetBSD thinks the sd0a partition
is?  Since there probably isn't a BSD disklabel on the drive, NetBSD will
construct a fake label from the partition table.  I'm not sure how HP-UX
works with respect to partition tables etc, so there might not be an i386
style partition table on the drive either.

Do a "disklabel sd0" and see what it says for the size of 'a'.  You might
want to use sd0d instead to save the whole drive (as opposed to just the
first partition) to a file.  If HP-UX does write an i386 style
partition table (i.e. the disklabel output looks like your partition 
setup in HP-UX) then you could probably save the individual
partitions to seperate files (i.e. sd0a might be a boot partition,
while sd0e holds the main big partition).

Hope this helps,
	Rick

On Wed, 16 May 2001, John Maier wrote:

> Date: Wed, 16 May 2001 14:02:44 -0500
> From: John Maier <jmaier@midamerica.net>
> To: Rob Quinn <rquinn@sprint.net>
> Cc: netbsd-users@netbsd.org
> Subject: Re: 'dd' ing a hard drive to a file
> 
> Background: I'm using i386 1.5 (release) I have a SCSI drive that is from a HP
> 735/99 running HP/UX 10.10 and the drive is whining something fierce.
> 
> I hooked the drive to the SCSI port, the netbsd kernel sees the physical drive,
> of course the partitions can't been seen.  Since I'm booting from a IDE drive,
> it is the only SCSI device (yes I have a SCSI card with nothing on it, don't
> ask) so it at sd0.
> 
> At the prompt I type:
> > dd if=/dev/rsd0a of=hpux1010.dsk
> 
> Say it read 2xxxxxx bytes to the file and exits.
> 
> What do you think?
> 
> jam
> 
> ----- Original Message -----
> From: "Rob Quinn" <rquinn@sprint.net>
> To: "John Maier" <jmaier@midamerica.net>
> Sent: Wednesday, May 16, 2001 11:46 AM
> Subject: Re: 'dd' ing a hard drive to a file
> 
> 
> > > I was trying to 'dd' a hard drive to a file and it sort of worked but died
> > > after 2 Megs.  Is this a limitation or is there a tric
> >
> >  I've dd'd several gig without a problem. What command line are you using, and
> > what's the error?
> >
>