System details at the end of the email.
PROBLEM:
I understand the latest lilo should allow to boot off a raid device, however I'm
having trouble doing so. Booting with the complete mirror is ok, booting with
the first disk (hda) is ok, booting with just the 2nd (hdc) stops at LI.
When doing tests I power off, and disconnect the IDE cable and reboot.
BIOS is all to auto.
I see there are some weird things with CHS (I'm using old HDs on a test system,
before doing this on a "real" system), could they be the cause of my problems?
When doing "lilo" I see there's a * (star) near the "linux" image on hda, but
not for the one of hdc. I tried setting the bootable flag on hdc1, but it does
not change anything.
I'm sure the bios allows to boot with just HDC, as I tried this is the past with
not mirrored disks.
SYSTEM DETAILS:
RedHat6.x system with 2.2.19 kernel (from RH + some minor patches not related to
raid, so with 0.90 raid).
== /proc/mdstat
Personalities : [raid1]
read_ahead 1024 sectors
md0 : active raid1 hdc2[1] hda2[0] 819392 blocks [2/2] [UU]
md1 : active raid1 hdc3[1] hda3[0] 205568 blocks [2/2] [UU]
md2 : active raid1 hdc4[1] hda4[0] 177344 blocks [2/2] [UU]
unused devices: <none>
== lilo version
LILO version 21.4-4
== lilo.conf
boot = /dev/md0
message = /boot/message
lba32
timeout = 200
image = /boot/vmlinuz
label = linux
root = /dev/md0
read-only
== output of lilo -v (no * for the hdc "linux")
LILO version 21.4-4, Copyright (C) 1992-1998 Werner Almesberger
'lba32' extensions Copyright (C) 1999,2000 John Coffman
boot = /dev/hda, map = /boot/map.0302
Reading boot sector from /dev/hda
Merging with /boot/boot.b
Mapping message file /boot/message
Boot image: /boot/vmlinuz
Added linux *
/boot/boot.0300 exists - no backup copy made.
Writing boot sector.
boot = /dev/hdc, map = /boot/map.1602
Reading boot sector from /dev/hdc
Merging with /boot/boot.b
Mapping message file /boot/message
Boot image: /boot/vmlinuz
Added linux
/boot/boot.1600 exists - no backup copy made.
Writing boot sector.
== partition tables
Partition Table for /dev/hda
---Starting--- ----Ending---- Start Number of
# Flags Head Sect Cyl ID Head Sect Cyl Sector Sectors
-- ----- ---- ---- ---- ---- ---- ---- ---- -------- ---------
1 0x00 1 1 0 0x82 127 63 32 63 266049
2 0x00 0 1 33 0xFD 127 63 236 266112 1645056
3 0x00 0 1 237 0xFD 127 63 287 1911168 411264
4 0x00 0 1 288 0xFD 127 63 614 2322432 2636928
Partition Table for /dev/hdc
---Starting--- ----Ending---- Start Number of
# Flags Head Sect Cyl ID Head Sect Cyl Sector Sectors
-- ----- ---- ---- ---- ---- ---- ---- ---- -------- ---------
1 0x00 1 1 0 0x82 63 63 24 63 100737
2 0x80 0 1 25 0xFD 63 63 431 100800 1641024
3 0x00 0 1 432 0xFD 63 63 533 1741824 411264
4 0x00 0 1 534 0xFD 63 63 621 2153088 354816
== kernel boot messages regarding partition
hda: SAMSUNG WU32543A (2.54GB), ATA DISK drive
hdc: FUJITSU M1636TAU, ATA DISK drive
hdd: PCRW804, ATAPI CDROM drive
hda: SAMSUNG WU32543A (2.54GB), 2423MB w/109kB Cache, CHS=615/128/63
hdc: FUJITSU M1636TAU, 1226MB w/128kB Cache, CHS=2491/16/63
Partition check:
hda: hda1 hda2 hda3 hda4
hdc: [PTBL] [622/64/63] hdc1 hdc2 hdc3 hdc4
== /etc/raidtab
raiddev /dev/md0
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
chunk-size 4
persistent-superblock 1
device /dev/hda2
raid-disk 0
device /dev/hdc2
raid-disk 1
raiddev /dev/md1
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
chunk-size 4
persistent-superblock 1
device /dev/hda3
raid-disk 0
device /dev/hdc3
raid-disk 1
raiddev /dev/md2
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
chunk-size 4
persistent-superblock 1
device /dev/hda4
raid-disk 0
device /dev/hdc4
raid-disk 1
== df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/md0 792800 203145 548686 27% /
/dev/md1 199015 13 188724 0% /data1
/dev/md2 171711 13 162831 0% /data2
hda1 and hdc1 are used for swap, not on raid.
Thanks
--
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
