RE: [SLUG] RAID1 system boot problem after new kernel compile
yeah I've done this and it still fails.. tested at 5PM today.. People say the RAID must be in the kernel and not a module but mkinitrd complains it need RAID1 which I assume it needs them as modules because it doesn't complain when I do... but also doesn't boot up.. from the LILO prompt is there anything I can type to make it load the root FS somehow?? -Original Message- From: Grant Parnell [mailto:[EMAIL PROTECTED]] Sent: Monday, 14 January 2002 10:05 PM To: George Vieira Subject: Re: [SLUG] RAID1 system boot problem after new kernel compile I'm sure somebody would have beaten me to an answer, but yes, you're going to have to make an initrd. It's easy-as though, man mkinitrd (assuming you did a make modules_install somewhere along the line. -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
RE: [SLUG] RAID1 system boot problem after new kernel compile
WhhoooO! That was the problem, I don't need to add the line for initrd in lilo.conf argh, for so long I've been trying to figure out what was going on.. thanks peeps. George Vieira Systems Manager Citadel Computer Systems P/L http://www.citadelcomputer.com.au -Original Message- From: Marty Richards [mailto:[EMAIL PROTECTED]] Sent: Monday, January 14 2002 11:41 PM To: George Vieira Subject: RE: [SLUG] RAID1 system boot problem after new kernel compile FYI image = /boot/vmlinux root = /dev/md0 label = Linux_new read-only is all thats in our lilo.conf... no mention of initrd at all. -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
Re: [SLUG] RAID1 system boot problem after new kernel compile
Have you got the RAID elements included as monolithic or as modules? If they are modules then you might need to build and use an initrd. Just a stab in the dark. On Mon, 14 Jan 2002, George Vieira wrote: Hi all, I'm still stuck with the machine with RAID1 and recompiling the kernel. I've upgraded kernels for years but never done one with the built in RAID of linux and everytime I try to boot with a new kernel config, it crashes with a problem mounting root fs. My guess is that it's not loading the RAID drivers/software or something as it's fine on the old kernel. It's frustrating me to hell coz' I need to compile some important stuff and patch my iptables etc,etc Has anybody recompiled a NEW kernel from scratch (with a new .config) and has RAID1 running on it. Any help on this? thanks, George Vieira Systems Manager Citadel Computer Systems P/L -- Howard. LANNet Computing Associates - Your Linux people Contact detail at http://www.lannetlinux.com We are either doing something, or we are not. 'Talking about' is a subset of 'not'. -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
RE: [SLUG] RAID1 system boot problem after new kernel compile
default=linux image=/boot/vmlinuz-2.4.2-2 label=linux initrd=/boot/initrd-2.4.2-2.img read-only root=/dev/md5 image=/boot/vmlinux-2.4.16 label=firewall initrd=/boot/initrd-2.4.2-2.img read-only root=/dev/md5 Could it be that I didn't update anything with the initrd 2.4.2-2 version? I've never had to touch it and yet have systems running quite fine..?? Should I be using mkinitrd, I've never created a new one (n00b he he) thanks, George Vieira Systems Manager Citadel Computer Systems P/L -Original Message- From: Howard Lowndes [mailto:[EMAIL PROTECTED]] Sent: Monday, 14 January 2002 8:12 AM To: George Vieira Cc: Sydney Linux Users Group (E-mail) Subject: Re: [SLUG] RAID1 system boot problem after new kernel compile Have you got the RAID elements included as monolithic or as modules? If they are modules then you might need to build and use an initrd. Just a stab in the dark. On Mon, 14 Jan 2002, George Vieira wrote: -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
RE: [SLUG] RAID1 system boot problem after new kernel compile
On Mon, 14 Jan 2002, George Vieira wrote: default=linux image=/boot/vmlinuz-2.4.2-2 label=linux initrd=/boot/initrd-2.4.2-2.img read-only root=/dev/md5 image=/boot/vmlinux-2.4.16 label=firewall initrd=/boot/initrd-2.4.2-2.img --- bz - wrong read-only root=/dev/md5 Could it be that I didn't update anything with the initrd 2.4.2-2 version? I've never had to touch it and yet have systems running quite fine..?? Should I be using mkinitrd, I've never created a new one (n00b he he) thanks, George Vieira Systems Manager Citadel Computer Systems P/L -Original Message- From: Howard Lowndes [mailto:[EMAIL PROTECTED]] Sent: Monday, 14 January 2002 8:12 AM To: George Vieira Cc: Sydney Linux Users Group (E-mail) Subject: Re: [SLUG] RAID1 system boot problem after new kernel compile Have you got the RAID elements included as monolithic or as modules? If they are modules then you might need to build and use an initrd. Just a stab in the dark. On Mon, 14 Jan 2002, George Vieira wrote: -- Howard. LANNet Computing Associates - Your Linux people Contact detail at http://www.lannetlinux.com We are either doing something, or we are not. 'Talking about' is a subset of 'not'. -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
