I don't have RAID - do I ????
During boot, I have always got messages about RAID. Before, using the huge kernel, these did not worry me particularly, but now that I have switched to the generic kernel and initrd, the boot process really slows down when it comes to the RAID part.
I have a bog normal PC with two ide disks, two dvd drives, one of them a burner and USB1 and USB2 ports - the USB2 ports are on a card as my PC is a somewhat elderly P4. I'm sure I don't have RAID - or do I? If not I want to stop it searching for and configuring RAID. Here are the messages from dmesg: Code:
hda: Maxtor 6Y060L0, ATA DISK drive |
Well, imagine that your system have drivers for RAID, even you don't use. Simply, ignore this messages.
|
Quote:
|
Add raid=noautodetect to your kernel command line. It won't stop you seeing the md messages you get in the log when the driver loads, but it'll stop it attempting to scan for an array to build. I'm not convinced this is what's slowing your boot down however, as it whizzes by on mine, but if you think it is, it's worth a try.
|
You could try compiling your own kernel with the RAID drivers taken out. There are guides all over the place for compiling a custom kernel. Admittedly, it's not a "quick fix" if you have never done this before but might be something worth considering.
|
Quote:
Unfortunately those were console meassges that are not in dmesg and were too early in the startup to be captured by bootlogd. I can't find where or how mdadm is called. Quote:
But it seems to be the only solution. |
I'm just wondering whether you might have accidentally included RAID support in the initrd by using the '-R' option on mkinitrd or RAID=1 in mkinitrd.conf. If you do a "ls /boot/initrd-tree/sbin/mdadm" does it find anything? If you do, then try to rebuild your initrd without raid support and see if that helps.
|
Code:
$ ls /boot/initrd-tree/sbin/mdadm Here's my present mkinitrd.conf: Code:
# mkinitrd.conf . In anycase I shall run it again, "mkinitrd -F", with RAID=0 and LVM=0. I shall also add CLEAR_TREE="1". Thanks GazL |
Nothing changed:
Code:
using /lib/modules/2.6.29.6-smp/kernel/fs/ext2/ext2.ko Code:
# mkinitrd.conf Here is /boot/initrd-tree/sbin/: Code:
adjtimex |
Well, you could run...
Code:
chmod -x /sbin/mdadm Although if you remove /boot/initrd-tree manually prior to re-running mkinitrd, you should not even have a /boot/initrd-tree/sbin/mdadm present at all. What command line are you using to run mkinitrd? |
Ahh, if you look in the /sbin/mkinitrd script you find this.
Code:
if [ ! -z "$RAID" ]; then RAID="0" won't do the trick. I don't know if they've reworked it since 13.0 (I'm using current), but all it does is source in the mkinitrd.conf file, so yes, an unset RAID= should work. |
Quote:
Quote:
Code:
mkinitrd -F |
Clutching at straws now, but perhaps you've managed to get some non-printable characters in your mkinitrd.conf file that are upsetting the script.
I'd suggest renaming it out the way and building an initrd with just the command-line options. mkinitrd -c -k 2.6.29.6-smp -m ext2 -f ext2 -r /dev/hda2 Or, something very similar. |
GazL - THAT WORKED !!! :hattip:
As you said: Quote:
Code:
# mkinitrd.conf Now to see what else I can throw out of startup..... |
So, when you had them commented out, it didn't work, but setting them to "" worked? How strange.
All I can think of there is that those variables were somehow exported from your shell environment and were being inherited. The mkinitrd script probably ought to unset them at the beginning to avoid things like that. Anyway, whatever the reason. glad you got there in the end. :) |
All times are GMT -5. The time now is 02:09 AM. |