From: Brandon Evans <maillists@hosttuls.com>
To: Linux-raid maillist <linux-raid@vger.kernel.org>
Subject: Kernal Panic when booting redhat. Raid devices mount fine under Knoppix
Date: Wed, 10 Dec 2003 15:03:31 -0800 [thread overview]
Message-ID: <3FD7A643.7060602@hosttuls.com> (raw)
Using rsync, I mirrored one server to some raid 1 partitions on another
server running knoppix. The Raid devices mount fine
under knoppix 3.3, but when I try to boot Redhat 7.3, the servers can
not read the superblock on the root device (/dev/md1), so the system panics.
This has happened on 2 servers so far.
The error I am getting is this:
EXT3-fs: unable to read superblock
mount:error 22 mounting ext3 flags
There is also something like this: pivotroot: pivot_root
(/sysroot,/sysroot/initrd) failed 2. But I left my notes at home, so
I'm not sure
that is exactly what the error says. The same migration process
worked fine in the test environment, but on the live servers,
with more data (20 Gigs), the server produce the above errors.
Why is Knoppix able to mount the root partition, but Redhat not?
To rsync, I used these steps:
http://hosttuls.com/whitepapers/SyncServerMigration.txt
Raidtab:
raiddev /dev/md0
raid-level 1
nr-raid-disks 2
chunk-size 64k
persistent-superblock 1
nr-spare-disks 0
device /dev/hda1
raid-disk 0
device /dev/hdd1
raid-disk 1
raiddev /dev/md1
raid-level 1
nr-raid-disks 2
chunk-size 64k
persistent-superblock 1
nr-spare-disks 0
device /dev/hda3
raid-disk 0
device /dev/hdd2
raid-disk 1
Fstab:
/dev/md1 / ext3 defaults,usrquota,grpquota 1 1
/dev/md0 /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/hda2 swap swap defaults 0 0
/dev/cdrom /mnt/cdrom iso9660
noauto,owner,kudzu,ro 0 0
/dev/fd0 /mnt/floppy auto
noauto,owner,kudzu 0 0
Lilo Entry:
image=/boot/vmlinuz-2.4.20-20.7smp
label=rh-2.4.20-20r
initrd=/boot/initrd-2.4.20-20.7smp.raid.img
read-only
root=/dev/md1
df:
Filesystem Size Used Avail Use% Mounted on
/dev/md1 112G 26G 80G 24% /
none 112G 26G 80G 24% /proc
/dev/md0 99M 28M 65M 30% /boot
none 112G 26G 80G 24% /dev/pts
none 112G 26G 80G 24% /dev/shm
/proc 112G 26G 80G 24% /proc
--
Brandon E.
next reply other threads:[~2003-12-10 23:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 23:03 Brandon Evans [this message]
2003-12-11 1:03 ` Raid array not clean (its barely used and a few weeks old.. how can i find out what went wrong?) James R Bamford
2003-12-11 1:49 ` Guy
2003-12-12 0:07 ` James R Bamford
2003-12-12 2:27 ` Guy
[not found] ` <3FD822D4.2030501@ratnet.stw.uni-erlangen.de>
2003-12-11 22:16 ` Kernal Panic when booting redhat. Raid devices mount fine underKnoppix Brandon Evans
2003-12-11 23:26 ` Dan Egli
[not found] ` <3FD99121.9000702@ratnet.stw.uni-erlangen.de>
2003-12-12 17:46 ` Brandon Evans
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3FD7A643.7060602@hosttuls.com \
--to=maillists@hosttuls.com \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).