Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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 an ageing but much loved Fedora Core 6 box for which I am attempting to compile a kernel more recent than 2.6.22, in order that I might employ its support for an eSATA card.

My Fedora box has a pair of 500G disks & uses LVM2 to pool most of their content into a large root file system. Together they form /dev/mapper/VolGroup00-LogVol00. All kernels reside in /boot which is on a more traditional /dev/sda1.

Once the newer kernel boots it very quickly cannot find /dev/mapper/VolGroup00-LogVol00 and panics, complaining that it cannot find /dev/root.

I have built my kernel using the config file '/boot/config-' as inspiration, hoping that whichever arcane switch I needed would be set, but so far - in vain.

I am resisting the urge to upgrade something more recent, as that's quite a hammer to break a very small egg.

Your clues & boos are all most welcome,


share|improve this question

Sounds like you don't hae device-mapper built into the kernel, as a module or possibly built into your new kernel's initrd file for use on boot. Check your config for the _DM options:


If it's built as a module, switch it to built in or 'mkinitrd --with=dm_mod' (sic) to get it in there.

share|improve this answer

The answer in the end was to set this in the .config

share|improve this answer

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.