--- Aleksandar Milivojevic amilivojevic@pbl.ca wrote:
Lee Parmeter wrote:
I did not mark the parition type to FD so apparently
the
kernel or mdadm just executes and looks in the
ndadm.conf
file.
When trying to start the raid manually, I found that
the
raid would fail unless I passed the partion assignments
on
the commandline to mdadm. However, when the DEVICE and
ARRAY are defined in the mdadm.conf, the partion info
was
not required, just the device name, "/dev/md0". So, I
think
the raid failed to start at boot due to not enough
information being available for it to startup, thus the
mdadm.conf file being required.
Anyway, that's what my experince told me!
OK, but have you attempted to mark the partition as type
fd (linux raid
autodetect)?
No. Since /dev/md0 is loading OK in fstab, I have not
messed with it further.
My guess is, if you did, the kernel would
bring it up as
soon as raid* device drivers are loaded. The information
in superblocks
at the end of each partition should be more than enough.
I will be creating another raid1 in the next week or two
and will try you suggestion then.
--
Aleksandar Milivojevic amilivojevic@pbl.ca Pollard
Banknote Limited
Systems Administrator 1499
Buffalo Place
Tel: (204) 474-2323 ext 276 Winnipeg,
MB R3T 1L7
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
--
Lee Parmeter Emperor, linXos - The Flying Penguin
http://www.linXos.com
Linux Registered User #337161
'It's free. It works. Duh.'" - Eric Harrison
The United States is NOT a democracy, it was founded as a Republic!
God is not a republican or a democrat nor is His government a democracy! - Lee Parmeter
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com