IIRC, HW raid should not be showing the individual drives to linux. They
should appear as a single device. I would check the raid card
configuration. Did the battery on it die or something?
Are you using a 'real' raid card, or raid on the MB? Raid on the MB is
fake-raid, and you should steer clear of that.
--
-Eric 'shubes'
On 05/15/2012 09:48 AM, David wrote:
Ok, I was doing some more comparison and experimentation on this machine
I want to work with HW raid.
here is what I get when I run this
[root@localhost ~]# blkid | sort
/dev/hda: LABEL="CentQMT5-1.2.1" TYPE="iso9660"
/dev/sda1: LABEL="/boot" UUID="16efa862-46f7-4d34-b2e0-a2a7c8df9a3f"
TYPE="ext3"
/dev/sda2: LABEL="/1" UUID="cb0fdf32-bcd5-4112-b6e8-9908ef872b8c"
SEC_TYPE="ext2" TYPE="ext3"
/dev/sda3: LABEL="SWAP-isw_ddfebj" TYPE="swap"
/dev/sdb1: LABEL="/boot" UUID="16efa862-46f7-4d34-b2e0-a2a7c8df9a3f"
SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb2: LABEL="/1" UUID="cb0fdf32-bcd5-4112-b6e8-9908ef872b8c"
TYPE="ext3"
/dev/sdb3: LABEL="SWAP-isw_ddfebj" TYPE="swap"
I can see both drives and the LABEL has the /1 in it which I do not
understand.
On 05/14/2012 11:37 AM, David wrote:
Here is what the default image installs before an update and it will
reboot with no issue.
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this
file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/mapper/isw_digeehiaa_Raid_0p2
# initrd /initrd-version.img
#boot=/dev/mapper/isw_digeehiaa_Raid_0
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.18-194.8.1.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-194.8.1.el5 ro root=LABEL=/
initrd /initrd-2.6.18-194.8.1.el5.img
The only thing different is the LABEL=/1 vs LABEL=/
I wonder if it tried to relabel but failed.
more to come
On 05/14/2012 10:15 AM, Eric Shubert wrote:
I presume that you cannot boot the previous kernel as well?
I would try modifying the root= parameter as it appears in the
comment. BL appears to be that the root filesystem no longer has a
label=\1, so grub cannot find it. Alternatively, you might try
putting a label on the root filesystem.
Sorry, but I'm not familiar off hand with how hardware raid appears
to grub (I prefer software raid myself).
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
