Skip to contentSkip to conversation

One partition degraded after every reboot

DISCUSSION Philipp Gortan 2 participants 4 messages Apr 1, 2004 – Apr 9, 2004 MD RAID

lore
Share & tools
lore
#0 lore raw
Quoted 3 lines · Thomas Andrews

I've set up RAID-1 on a pair of disks recently. When I reboot I get this in syslog, even though the partition was perfect & not degraded before:

...

Quoted 10 lines

kernel: md1: former device ide/host2/bus0/target0/lun0/part5 is unavailable, removing from array!

More specifically, of the 4 RAID-1 partitions, md1 (my root partition) is in degraded mode. Here's a snippet of /proc/mdstat:

md1 : active raid1 ide/host2/bus1/target0/lun0/part5[0]

      38957440 blocks [2/1] [U_]

All the RAID partitions are of type FD on both disks, and the disks are brand new

...

Quoted 1 line

This is a stock Debian/testing pc running a stock 2.4.24-1-686 kernel.

Hi Andrew,
I had the same problem today, with debian/testing and both 2.4 and 2.6 kernels.
My root filesystem, a raid 1 device would come up degraded at every reboot, even if it was clean on shutdown.

I solved the problem by creating a new initrd and fiddling with the lilo configuration:
for me,
after re-adding the always-failing drive to the raid

# mdadm -a /dev/md0 /dev/hda1
i updated my lilo.conf to:

...
boot=/dev/md0
raid-extra-boot=/dev/hda,/dev/hdc
root=/dev/md0
...

and created a new initrd

# mkinitrd -k -r /dev/md0 -o /boot/initrd.img-2.6.3-1-k7

and ran lilo again

# lilo

since that reboot, the raid comes up complete.

hope that helps,

cu, philipp

Signature · 3 lines
When in doubt, use brute force.

                               -- Ken Thompson
#1 lore raw
Quoted 2 lines · Philipp Gortan

and created a new initrd

# mkinitrd -k -r /dev/md0 -o /boot/initrd.img-2.6.3-1-k7

Yes I found I had to do that from the start because the initrd image from before the raid conversion was set up for a different root device, so in my case that isn't the solution.

Quoted 1 line

and ran lilo again

I'm using grub. I wonder if that's a problem ?

-Thomas

#2 lore raw
Quoted 9 lines · Thomas Andrews
Quoted 3 lines
# mkinitrd -k -r /dev/md0 -o /boot/initrd.img-2.6.3-1-k7

Yes I found I had to do that from the start because the initrd image from before the raid conversion was set up for a different root device, so in my case that isn't the solution.

Hi Thomas,
well, I'd definitely give it another try now...

Quoted 3 lines

I'm using grub. I wonder if that's a problem ?

I'm no grub expert, but I didn't get it to work under grub either, so I switched to lilo. Simply say

# apt-get install lilo
# liloconfig
accept the defaults and change the values in /etc/lilo.conf for boot and root to your root md device.
then run lilo and you should be set...

cu,
philipp

#3 lore raw
In reply to Philipp Gortan
Quoted 7 lines · Philipp Gortan
Quoted 7 lines

I've set up RAID-1 on a pair of disks recently. When I reboot I get this in syslog, even though the partition was perfect & not degraded before:

kernel: md1: former device ide/host2/bus0/target0/lun0/part5 is unavailable, removing from array!

More specifically, of the 4 RAID-1 partitions, md1 (my root partition) is in degraded mode.

[snip]

Quoted 13 lines

I solved the problem by creating a new initrd and fiddling with the lilo configuration:
for me,
after re-adding the always-failing drive to the raid

# mdadm -a /dev/md0 /dev/hda1
i updated my lilo.conf to:

...
boot=/dev/md0
raid-extra-boot=/dev/hda,/dev/hdc
root=/dev/md0
...

Quoted 5 lines

and created a new initrd

# mkinitrd -k -r /dev/md0 -o /boot/initrd.img-2.6.3-1-k7

and ran lilo again

# lilo

[snip]

Unfortunately, installing lilo in place of grub hasn't solved the problem, so I'm still without a solution.

-Thomas