Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a problem with an HP ProLiant Microserver that won't boot with a Slackware 12 system using Linux

If I boot a recent version of System Rescue CD, the disk is recognized.

So my question is: how can I find which module is the System Rescue CD kernel using to access the hard disk?


When trying to boot with Slackware, I get the dreadful message

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

The filesystem module (ext3) is loaded, so it can only be a controller driver issue, as far as I know.

share|improve this question
up vote 4 down vote accepted

In 2.6.21, the module for HP SmartArrays is 'cciss'. In more recent kernel versions they've been moving things over to a newer 'hpsa' driver. To find out what modules are driving which hardware, the '

lspci -k

command will display which modules are associated with which devices.

03:00.0 RAID bus controller: Hewlett-Packard Company Smart Array G6 controllers (rev 01)
Subsystem: Hewlett-Packard Company Smart Array P410i
Kernel driver in use: cciss
share|improve this answer
Hi, this might solve the non-booting server but it's not the answer to the original question. I know that I mixed 2 questions in 1 and it's a bit messy. Should I ask another question for the non-booting server? – Andrea Spadaccini Feb 2 '11 at 19:26
Hi, the driver was not cciss but ahci, as the ProLiant MicroServer does not have the HP Smart Array Controller. Thanks however for the help! – Andrea Spadaccini Feb 2 '11 at 19:43

After some more research, I found that the kernel module used by a given subsystem is obtained by lspci -k.

In this way I found that the module required by the controller is ahci, and I'm going to try and see if this works with my kernel.

share|improve this answer
It worked, the server booted flawlessly once I compiled statically ahci and set to AHCI the disk setting in the BIOS. – Andrea Spadaccini Feb 2 '11 at 19:44

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.