Jon Nelson skrev:
On Sun, 21 Jan 2007, Bo Jacobsen wrote:
After having copied a OpenSuse 10.2 system with software-raid (
disk-mirror with 2 IDE harddisks) to a different set of harddisks,
Linux can no longer boot on the new disks, when I boot with the
standard Open SuSE 10.2 kernel.
The error message is from MD saying that it can not find any devices
for my three raid partions /dev/md0 (swap) , /dev/md1 (/) and /dev/md2
(/home)
md: No device found for /dev/md0...
and the boot sequence halts.
The strange thing is that if I boot the system with a standard Linux
2.6.19.1 kernel, also on the harddisk (no module support), or if I
connect the harddisk to a MS Virtual PC, it boots just fine. The
problem has apparently something to do with the OpenSuSE 10.2 std
kernel. If I boot the rescue system from the dvd, it also looks just
fine ! (cat /dev/mdstat).
On the harddisk where the system was originally copied from, it works
perfectly.
Boot the rescue CD and find and remove /etc/mdadm.conf
--
Carpe diem - Seize the day.
Carp in denim - There's a fish in my pants!
Jon Nelson <[EMAIL PROTECTED]>
I have tried this, but as MD can't create /dev/mdx I don't think the
kernel, as this point, has access to
the file system on mdx.
This is part of the boot messages seen while booting.
..
Loading liniar
md: Liniar personality registered for level1
Loading JBD
Loading mbcache
Loading ext3
md: MD1: No device found for /dev/md1
Waiting for device /dev/md1 to appear: OK
/dev/md1: Unknown volume type
Invalid boot file system - exiting to /bin/sh.
..
And then the boot stops.
The same harddisk mounted on a MS Virtual PC and booted with the same
Grub bootline,
boots as expected, and makes the following lines in boot.msg:
..
Loading liniar
Loading mbcache
Loading ext3
mdadm: /dev/md0 has been started with 1 drive (out of 2).
mdadm: /dev/md1 has been started with 1 drive (out of 2).
...
/Bo
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
