I'm running Debian Sarge with a 2.6.8 kernel on my fairly new (about 2 month old) AMD Duron system. I'm using Grub to boot rather than lilo & I have RAID support built into my kernel, not as a module. Today I just added a second drive and configured it for RAID 1, using the Software-RAID.HOWTO instructions for converting an existing system to RAID. The RAID device starts properly using the new drive (with my existing drive as a missing drive):
root@blackbox:/etc/mdadm# mdadm --query /dev/md0
/dev/md0: 111.67GiB raid1 2 devices, 0 spares. Use mdadm --detail for more detail.
/dev/md0: No md super block found, not an md component.
root@blackbox:/etc/mdadm# mdadm --detail /dev/md0
Version : 00.90.01
Creation Time : Fri Oct 1 16:37:58 2004
Raid Level : raid1
Array Size : 117089600 (111.67 GiB 119.90 GB)
Device Size : 117089600 (111.67 GiB 119.90 GB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Fri Oct 1 21:15:23 2004
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
Number Major Minor RaidDevice State
0 0 0 -1 removed
1 3 1 1 active sync /dev/hda1
UUID : 11585c9e:315397b1:e3ce7295:c1fa7ef3
Events : 0.14345
If I have the partition type set to FD, it's automatically detected at startup:
md: autorun ...
md: considering hda1 ...
md: adding hda1 ...
md: created md0
md: running: <hda1>
raid1: raid set md0 active with 1 out of 2 mirrors
md: ... autorun DONE.
ReiserFS: hde1: found reiserfs format "3.6" with standard journal
However, if I boot from /dev/hda1, it's unable to mount the root file system & I get a kernel panic right after that point if the partition type is FD. If I change the partition type back to 83, that drive is able to boot normally but it isn't auto-detected and the RAID device can't be started.
How can I get it to boot a partition of type FD?