Thanks for the advice, I managed to get the system booting off either
disc without further swapping of the drives around though. I set
"raid-extra-boot=mbr-only" in lilo.conf. This forces lilo to rewrite the
mbr of each disc in the raid1 array and not to the first sector of the
raid1 partition.
hi ya drbob
On Mon, 16 Jan 2006, drbob wrote:
> I use mdadm to manage my array. The command was
>
> mdadm --set-faulty /dev/md1 /dev/hda1 --remove /dev/md1 /dev/hda1
i'd think there might be a short cut version, but i'm being
lazy to go look it up
- i'd set it faulty first, if the sys
drbob wrote:
I'll post here if the changes I suggest above have any effect.
regards,
drbob
Before I did this I tried a few different settings in lilo.conf and had
some success :-).
Setting raid-extra-boot=mbr-only avoided the error I was seeing previously:
:/etc# lilo -v
LILO version 2
Alvin Oga wrote:
what exaactly did you type BEFORE you removed the bad disk ??
raidhotadd, raidhotremove, etc, etc.. is required ( aka good idea )
I use mdadm to manage my array. The command was
mdadm --set-faulty /dev/md1 /dev/hda1 --remove /dev/md1 /dev/hda1
(repeated for the other par
hi ya drbob
On Sun, 15 Jan 2006, drbob wrote:
> I've replaced a failed disk in my raid 1 setup. I replaced the disk (hda
> on-board ide),
what exaactly did you type BEFORE you removed the bad disk ??
raidhotadd, raidhotremove, etc, etc.. is required ( aka good idea )
> So I went into the b
Mike Bird wrote:
They look good. I'm beginning to think that either your partition
table is corrupt or it's a non-DOS type that's too large to leave
room for LILO.
I can't find an fdisk option to ask for the partition table type.
You could try "parted /dev/hde print" (etc) to verify that both
On Sun, 2006-01-15 at 10:40, drbob wrote:
> I'm pretty sure it did. Attached are the outputs from fdisk and
> mdstat.
They look good. I'm beginning to think that either your partition
table is corrupt or it's a non-DOS type that's too large to leave
room for LILO.
I can't find an fdisk option to
Mike Bird wrote:
On Sun, 2006-01-15 at 09:59, drbob wrote:
I've replaced a failed disk in my raid 1 setup. I replaced the disk (hda
on-board ide), however the system then hung on reboot, this was because
hda, being blank, had no MBR. The second disk (hde) is plugged into a
promi
On Sun, 2006-01-15 at 09:59, drbob wrote:
> I've replaced a failed disk in my raid 1 setup. I replaced the disk (hda
> on-board ide), however the system then hung on reboot, this was because
> hda, being blank, had no MBR. The second disk (hde) is plugged into a
> promise ide card. So I went int
Hello,
I've replaced a failed disk in my raid 1 setup. I replaced the disk (hda
on-board ide), however the system then hung on reboot, this was because
hda, being blank, had no MBR. The second disk (hde) is plugged into a
promise ide card. So I went into the bios and set it to boot off the
pr
10 matches
Mail list logo
