On Thu, 2004-10-07 at 07:06, John Andersen wrote:
On Wednesday 06 October 2004 12:03 am, Nicholas Moir wrote:
I am trying to build kernel 2.4.24 on Suse 9.0. The box has Highpoint software RAID (hptraid.o) and / should be mounted on /dev/ataraid/d0p2.
I have used the stock 2.4.21-243 kernel as a starting point (because it boots!) and have included support for reiserfs, Software RAID, and NVIDIA IDE interfaces.
The exact error messages I receive on boot are:
reiserfs:checking transaction log (device ataraid(114,2)) node level 0 does not match to the expected one ataraid(114,2):vs_5150:search_by_key:invalid format found in block.Fsck? ataraid(114,2):vs_13070:reiserfs_read_inode:i/o failure occurred trying to find stat data of [1 2 0x0 50] ataraid(114,2):Using r5 hash to sort names VFS:Cannot open root device "ataraid /d0p2" Please append a correct "root=" boot option kernel panic:VFS:Unable to mount root fs
The reiserfs filesystem isn't corrupt as it boots perfectly well using kernel 2.4.21-243, which seems strange as I have used this kernel's .config as a base for the new one.
Any ideas? I can't think of anything else that needs to be included in the kernel .config to make this work.
Thanks. -- Nicholas Moir
Why do you have hptraid.o if you are using software raid? that raid module is for using the the on-board raid controller.
If you want software raid, jumper the card (usually un-jumper is needed) to make it look like a regular controller. Then you can build software raid on top of those disks.
Or fix the raid using the raid tools built into your bios and use hardware raid. But I don't think you should mix them. Or am I missing something?
Thanks for the reply. It is hardware raid I require, using HighPoint raid controller. I have also tried to get kernel 2.4.21 working on this system. It progresses slightly further: in that the / file-system is mounted read-only. ------- showconsole: Warning:the ioctl TIOCGDEV is not known by the kernel fsck.reiserfs /dev/ataraid/d0p2 failed (status 0x8). Run manually ------- Occasionally the following error also appears on the screen: -------- spurious 8259A interrupt:IRQ7 --------- So why does the stock SUSE kernel recognise and the mount the root partition while these new kernels don't? what am I missing?? Thanks. -- Nicholas Moir