[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Installation reporting on HP Proliant ML350 with Smartarray



I apologise for the delay in responding to your installation report. As
far as I can see nobody else did, so here goes..

Francesco P. Lovergine wrote:
> Some problems in installation:
> 
> * d-i does not recognize ethernet (tg3) and controller (cciss for 641 series)
> 	I loaded by hand modules and proceeded. I could send pci ids
> 	in a couple of days.

It'd be good if you'd send those pci ids, this should be easy to fix.

> * kernel installation failed
> 	The problem is that the root /dev/cciss/disc/disc0/part1 path is not
> 	correctly managed by mkinitrd and it creates a 0byte file.
> 	The installation succeded by hand using a traditional
> 	device name -r /dev/cciss/c0d0p1, customizing in chroot /target
> 	the /etc/mkinitrd/modules to add cciss support, creating
> 	lilo.conf by hand (with non devfs device names) and running 
> 	lilo. 

Sounds like you have a good handle on what was broken and why, so why
don't you file a bug report on the kernel-image-2.4.22-i386 package (or
whatever kernel package it installed) with the full details of what
mkinitrd does wrong.

> 	Also, manual disk partition failed and presented a
> 	strange list of choices:
> 
> 	.
> 	.
> 	0
> 	0
> 	1
> 	1
> 	/
> 	/
> 	Finished
> 
> 	or so.

I think it's having a hard time converting the smartarray's nonstandard
devices into the easily readable format it tries to use. Can you file a
bug against the "partitioner" package?

-- 
see shy jo

Attachment: signature.asc
Description: Digital signature


Reply to: