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

Bug#691346: kfreebsd-amd64 fails to install on LSI MegaRAID SAS 2208

Package: installation-reports
Severity: critical
Tags: d-i

-- Package-specific info:

Boot method: CD
Image version: debian-wheezy-DI-b3-kfreebsd-amd64-netinst.iso
Date: 201210241200

Machine: IBM System x3650 M4
Partitions: no partitions

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:           [E]
Detect network card:    [ ]
Configure network:      [ ]
Detect CD:              [ ]
Load installer modules: [ ]
Clock/timezone setup:   [ ]
User/password setup:    [ ]
Detect hard drives:     [ ]
Partition hard drives:  [ ]
Install base system:    [ ]
Install tasks:          [ ]
Install boot loader:    [ ]
Overall install:        [ ]


On this server the LSI RAID controller LSI MegaRAID SAS 2208/ServeRAID M5110e
is installed. I tried installing kfreebsd-amd64 on it from CD. The
installer GRUB menu works (see attachment boot.png), but right after
that the FreeBSD kernel hangs during boot with an error (see
attachment error.png). After 10/20 seconds another error line gets
printed -- something about hard resetting something -- but it was
too fast for me to take a screenshot, and the system reboots. 
On the very same machine I was able to install the standard 
debian-wheezy-DI-b3-amd64-netinst.iso without any problem. 

On LSI website I found this:
which seems to indicate that FreeBSD 9.0 ships an obsolete kernel
module for this controller, and they suggest a procedure how to create
a FreeBSD 9.0 installer with an updated module. My knowledge of
FreeBSD are a bit too limited for me to seriously think about
recompile the kernel and injecting some additional modules, but
maybe someone in the kfreebsd debian team knows how to do it?

I now have the machine up and running with linux debian amd64, so I
can make any needed additional hardware info -- as linux sees it --
available. I can also make the remote control console accessible to
more knowledgeable people for debugging.


PS: I did not know what severity to set, I thought that complete
install failures qualifies for "critical", but please downgrade it
if needed.

Attachment: boot.png
Description: PNG image

Attachment: error.png
Description: PNG image

Reply to: