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 removed a software RAID setup on a server I took over several years ago and everything worked fine until I upgraded the kernel the other day. It seems when debian updated the grub menu.lst file it not only added the new kernel with md0 but also the old kernel as md0.

What is causing debian to think there is still a software RAID setup? Is there a default file I need to change, do I need to remove the mdadm package?

share|improve this question
that's in /proc/mounts? – David Pashley Jun 12 '09 at 12:29
"what's in /proc/mounts?" even – David Pashley Jun 12 '09 at 12:30
up vote 3 down vote accepted

Some slightly non-specific Debian information..

  • Make sure that /etc/fstab contains no mention of the MD devices.
    I would presume that it doesn't, as you are able to otherwise boot.

  • Debian appears to perform some magic with /boot/grub/menu.lst.
    Check whether it contains an entry akin to this and re-run update-grub.


  • If you are definitely no longer using SW RAID at all then you can remove mdadm.
    Debian may use it's presence as a hook when updating GRUB.

share|improve this answer
+1 This looks mostly useful, but a pint for lunch is clouding my judgement slightly. All sensible things to check. – David Pashley Jun 12 '09 at 12:50
It was the kopt that was causing problems. Cheers – Chris Jun 12 '09 at 14:16

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.