I remember seeing something like this as well. Seems like a bug in partman.
The only way I got around it is to partition the disk using fdisk.
Getting fdisk on the machine was the tricky part, it was not on my installation
media. I put the executable on another server, and copied that over from
the install shell.
--
Martin
---------------------------------------------------------------------------
30 years from now GNU/Linux will be as redundant a term as MERT/UNIX is
today. - Martin Habets
---------------------------------------------------------------------------
On Sat, May 31, 2008 at 04:27:57PM -0700, Gary W. Smith wrote:
> Hello,
>
> I've been working to get Debian current installed on a Netra X1 from a
> netboot over LOM. I first encountered the problem with the tulip driver
> (requiring me to shell out, unload dmfe/tulip and then load tulip). As
> is well on the network front. The problem is after it downloads all of
> the install from ftp, it comes up and states that it cannot find any
> disks and asks me to load a driver.
>
> So I shell again and I can see /dev/hda in /proc/partitions (20gb). I
> run partman from the shell and it sees no drives. Thinking that it's
> because of the former Sun partition, I dd if=/dev/zero of=/dev/had bs=1M
> count=1 to clear any partitions. I then run partman and it now sees a
> 1MB disk drive.
>
> Any ideas on why this might be happening and how I can work around it.
> I have several of these machines that I'd like to build out in the next
> couple days for a project, but they just aren't cooperating.
>
> Gary
--
To UNSUBSCRIBE, email to debian-sparc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org