Hi,
Thanks for your reply. I believe your right, it's fine, detecting
everything. But in the below i'm seeing hda1 has different uuid than the
other raid elements. How do i correct this as this appears to be the heart
of the trouble?
Thanks.
Dave.
Loading raid1.ko module
md: raid1 personality registered for level 1
md: Autodetecting RAID arrays.
md: autorun ...
md: considering hdb5 ...
md: adding hdb5 ...
md: hdb3 has different UUID to hdb5
md: hdb2 has different UUID to hdb5
md: hdb1 has different UUID to hdb5
md: adding hda5 ...
md: hda3 has different UUID to hdb5
md: hda2 has different UUID to hdb5
md: hda1 has different UUID to hdb5
md: created md3
md: bind<hda5>
md: bind<hdb5>
md: running: <hdb5><hda5>
raid1: raid set md3 active with 2 out of 2 mirrors
md: considering hdb3 ...
md: adding hdb3 ...
md: hdb2 has different UUID to hdb3
md: hdb1 has different UUID to hdb3
md: adding hda3 ...
md: hda2 has different UUID to hdb3
md: hda1 has different UUID to hdb3
md: created md0
md: bind<hda3>
md: bind<hdb3>
md: running: <hdb3><hda3>
raid1: raid set md0 active with 2 out of 2 mirrors
md: considering hdb2 ...
md: adding hdb2 ...
md: hdb1 has different UUID to hdb2
md: adding hda2 ...
md: hda1 has different UUID to hdb2
md: created md2
md: bind<hda2>
md: bind<hdb2>
md: running: <hdb2><hda2>
raid1: raid set md2 active with 2 out of 2 mirrors
md: considering hdb1 ...
md: adding hdb1 ...
md: adding hda1 ...
md: created md1
md: bind<hda1>
md: bind<hdb1>
md: running: <hdb1><hda1>
raid1: raid set md1 active with 2 out of 2 mirrors
md: ... autorun DONE.
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
Trying to resume from /dev/md0
No suspend signature on swap, not resuming.
Creating root device.
Mounting root filesystem.
mount: could notKernel panic - not syncing: Attempted to kill init!
find filesystem '/dev/root'
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
----- Original Message -----
From: "Scott Silva" <ssilva@xxxxxxxxxxxx>
To: <centos@xxxxxxxxxx>
Sent: Wednesday, November 28, 2007 5:52 PM
Subject: Re: CentOS /boot kernel files removed after rpm upgrades
on 11/28/2007 2:46 PM Dave spake the following:
Hello,
The error is in my original posting, md the raid arrays are not
synchronized.
Checking /proc/mdstat output is below, doesn't look to me like
trouble.
Thanks.
Dave.
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4]
md1 : active raid1 hdb1[1] hda1[0]
102208 blocks [2/2] [UU]
md3 : active raid1 hdb5[1] hda5[0]
1036096 blocks [2/2] [UU]
md0 : active raid1 hdb3[1] hda3[0]
522048 blocks [2/2] [UU]
md2 : active raid1 hdb2[1] hda2[0]
8337664 blocks [2/2] [UU]
unused devices: <none>
That looks perfectly fine. Maybe on boot the arrays weren't sync'd, but
have since caught up.
--
MailScanner is like deodorant...
You hope everybody uses it, and
you notice quickly if they don't!!!!
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
