Re: LILO with root-raid nightmare - please help.
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
drives have msdos partition tables. The partition table type
is listed as e.g. "Disk label type: msdos".
Here is the output from parted:
:~# parted /dev/hde print
Disk geometry for /dev/hde: 0.000-39083.625 megabytes
Disk label type: msdos
Minor Start End Type Filesystem Flags
1 0.031 15.750 primary ext3 boot, raid
2 15.750 494.648 primary linux-swap raid
3 494.648 635.906 primary ext3 raid
4 635.906 39083.625 extended
5 635.937 730.406 logical ext3 raid
6 730.437 4636.898 logical ext3 raid
7 4636.929 8543.390 logical ext3 raid
8 8543.421 39083.625 logical ext3 raid
Information: Don't forget to update /etc/fstab, if necessary.
:~# parted /dev/hda print
Disk geometry for /dev/hda: 0.000-39205.687 megabytes
Disk label type: msdos
Minor Start End Type Filesystem Flags
1 0.031 23.532 primary ext3 boot, raid
2 23.533 509.875 primary linux-swap raid
3 509.875 658.916 primary ext3 raid
4 658.916 39205.502 extended
5 658.947 760.891 logical ext3 raid
6 760.922 4675.166 logical ext3 raid
7 4675.197 8589.440 logical ext3 raid
8 8589.472 39205.502 logical ext3 raid
Information: Don't forget to update /etc/fstab, if necessary.
I'm going to try taking hda out of the array again. I'll move hde to the
on board ide so I don't have to tell the bios to boot off the promise
card. If this boots ok I'll try and add the new drive again. After a
little reading I believe software Raid volumes are identified by their
superblock, right? So it shouldn't matter to the array if a disk that
was previously hde is booted as hda? I partitioned the drives using
cfdisk and they've only been used for linux (the 200gb hdg with a fat 32
partition isn't currently in use, though I did put it in at the same
time as I replaced the failed raid drive).
I haven't changed lilo.conf since I set the array up a year ago so I had
been hoping things would "just work" oh well :-)
I'll post here if the changes I suggest above have any effect.
regards,
drbob
Reply to: