Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

softraid and mount plus boot as root

1 view
Skip to first unread message

Oliver Sass

unread,
Dec 10, 2001, 11:04:19 AM12/10/01
to
Dear Linux-users,
I have installed a softraid level 1 on a system with 2.4.4 Kernel.
The funny thing is, that the system doesn't want to mount the root-dir from
the md-device... and even more funny is: it doesn't say so: it makes me
believe it had mounted the right md-dev...

Here is my data: there are two disks /dev/hde and /dev/hdg with four
software raids level 1 and a type 83 partition for /boot.
My old root is on /dev/hda3, and lilo is on the mbr of /dev/hda...

here are my config-files:
lilo.conf:

boot = /dev/hda
vga = normal
read-only
prompt
timeout = 30

image = /boot/raidImage
label = raidkernel
root = /dev/hda3

image = /boot/raidImage
label = raidonroot
root = /dev/md2

fstab on /dev/hda3:
# BASE
/dev/hde3 swap swap defaults 0 0
/dev/hdg3 swap swap defaults 0 0
/dev/hde1 /boot ext2 defaults 1 2
# RAID
/dev/md0 /usr/local/httpd ext2 defaults 1 1
/dev/hda3 / ext2 defaults 1 1
/dev/md1 /home ext2 defaults 1 1
/dev/md3 /var ext2 defaults 1 1
# PROC
none /proc proc defaults 0 0

fstab on /dev/md2:
# BASE
/dev/hde3 swap swap defaults 0 0
/dev/hdg3 swap swap defaults 0 0
/dev/hde1 /boot ext2 defaults 1 2
# RAID
/dev/md0 /usr/local/httpd ext2 defaults 1 1
/dev/md2 / ext2 defaults 1 1
/dev/md1 /home ext2 defaults 1 1
/dev/md3 /var ext2 defaults 1 1
# PROC
none /proc proc defaults 0 0

And my raidtab:
raiddev /dev/md0
raid-level 1
nr-raid-disks 2
persistent-superblock 1
chunk-size 4

device /dev/hde5
raid-disk 0
device /dev/hdg5
raid-disk 1


raiddev /dev/md1
raid-level 1
nr-raid-disks 2
persistent-superblock 1
chunk-size 4

device /dev/hde6
raid-disk 0
device /dev/hdg6
raid-disk 1

raiddev /dev/md2
raid-level 1
nr-raid-disks 2
persistent-superblock 1
chunk-size 4

device /dev/hde7
raid-disk 0
device /dev/hdg7
raid-disk 1

raiddev /dev/md3
raid-level 1
nr-raid-disks 2
persistent-superblock 1
chunk-size 4

device /dev/hde8
raid-disk 0
device /dev/hdg8
raid-disk 1

and the partition-table of /dev/hde

/dev/hde1 * 1 5 40131 83 Linux
/dev/hde2 6 7465 59922450 5 Extended
/dev/hde3 7466 7476 88357+ 82 Linux swap
/dev/hde5 6 4467 35840983+ fd Linux raid autodetect
/dev/hde6 4468 5742 10241406 fd Linux raid autodetect
/dev/hde7 5743 7017 10241406 fd Linux raid autodetect
/dev/hde8 7018 7465 3598528+ fd Linux raid autodetect

--------------------------------------------------------------------------------
The Raidsystem works quite well, except the fact that I am not able to boot
the root-fs from /dev/md2... In fact: even when I tell the system to boot
with /dev/md2 as root-dir, it does mount /dev/hda3. But when I type
"mount", it tells me, that /dev/md2 is mounted, but IN FACT, it is
/dev/hda3! This is quite a strange thing...

Does anybody know, how this can happen?
Does anybody know a reliable way to see what fs' are mounted indeed?
And does anybody know a way to force the system booting root-fs on a
raid-device?
Thank you very much in forward,
Oliver


--
## Oliver
## sa...@gw.sino.uni-heidelberg.de
## Heidelberg, Germany

0 new messages