helm
25.04.05, 14:05
Hello,
I try since 2 weeks to establish a bootable Migration from a SuSE Linux 9.1 Installtion to Softwareraid 1. I investigated the web and found the following HOWTO:
http://unthought.net/Software-RAID.HOWTO/S....HOWTO-7.html#s
I tried Point 7.6, and it's all working fine but Step 11 resize the filesystem. At e2fsck -f /dev/md0 its stating a Bad magic number in Superblock while trying to open /dev/md0. And resize2fs states the same.
When I now try to boot from the Raid 1 get the following errors:
md: Autodedecting RAID Arrays
md: autorun...
md: considering hdc2...
md: adding hdc2
md: adding hda2
md: created md0
md: bind <hda2>
md: bind <hdc2>
md: running: <hdc2><hda2>
md: peronality3 is not loaded!
md: do_md_run() returned -22
md: md0 stopped
md: unbind <hdc2>
md: export-rdev (hdc2)
md: unbind <hda>
md: export-rdev (hda)
EXT2-fs: unable to read superblock
Minix-fs: unable to read superblock
iso-fill-super: bread failed, dev=md0, iso_blknum 15, block=32
Kernel Panic: VFS: unable to mount rootfilesystem on md0
I have somehow got to it that e2fsck and resize2fs works (perhaps it has something to do with the fs on md0, or because I downloaded all updates, I got no clue), but its doesn't boot nevertheless.
So I tried Point 7.5 Making the system boot on RAID from the HOWTO. So I could at least make a filesystem on md0 before I copied the system from the as failed-disk marked hda2 partition to the md0 Raiddevice. It works all fine, but at the boot I got the following:
fsck failed, please try manually to repair and reboot
then you can login to a (none) system to run e2fsck, but it states the same message with the corrupt superblock although it works fine in the rescue system.
But somehow it must work, because when I install Linux on a at the install defined RAID 1, it install Linux on the RAID 1 device and boot faultless.
Can somebody please help, I doesn't get anyfurther at this point.
I try since 2 weeks to establish a bootable Migration from a SuSE Linux 9.1 Installtion to Softwareraid 1. I investigated the web and found the following HOWTO:
http://unthought.net/Software-RAID.HOWTO/S....HOWTO-7.html#s
I tried Point 7.6, and it's all working fine but Step 11 resize the filesystem. At e2fsck -f /dev/md0 its stating a Bad magic number in Superblock while trying to open /dev/md0. And resize2fs states the same.
When I now try to boot from the Raid 1 get the following errors:
md: Autodedecting RAID Arrays
md: autorun...
md: considering hdc2...
md: adding hdc2
md: adding hda2
md: created md0
md: bind <hda2>
md: bind <hdc2>
md: running: <hdc2><hda2>
md: peronality3 is not loaded!
md: do_md_run() returned -22
md: md0 stopped
md: unbind <hdc2>
md: export-rdev (hdc2)
md: unbind <hda>
md: export-rdev (hda)
EXT2-fs: unable to read superblock
Minix-fs: unable to read superblock
iso-fill-super: bread failed, dev=md0, iso_blknum 15, block=32
Kernel Panic: VFS: unable to mount rootfilesystem on md0
I have somehow got to it that e2fsck and resize2fs works (perhaps it has something to do with the fs on md0, or because I downloaded all updates, I got no clue), but its doesn't boot nevertheless.
So I tried Point 7.5 Making the system boot on RAID from the HOWTO. So I could at least make a filesystem on md0 before I copied the system from the as failed-disk marked hda2 partition to the md0 Raiddevice. It works all fine, but at the boot I got the following:
fsck failed, please try manually to repair and reboot
then you can login to a (none) system to run e2fsck, but it states the same message with the corrupt superblock although it works fine in the rescue system.
But somehow it must work, because when I install Linux on a at the install defined RAID 1, it install Linux on the RAID 1 device and boot faultless.
Can somebody please help, I doesn't get anyfurther at this point.