Bugs item #1027160, was opened at 2004-09-13 12:56 Message generated for change (Comment added) made by tepahe You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100259&aid=1027160&group_id=259
Category: systemimager-client Group: v3.2.0 Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Kernel Panic: No init found. Try passing init= option to ker Initial Comment: We've tried many ways to pinpoint what could be wrong. One thing I've noticed is that you need to have a /boot partition if you plan to have a very large root partition. But this last problem seem to be related to the software raid partitions. When you use the Red Hat Enterprise Linux 3.0 raid software to mirror your /boot and / paritions the client allways fails to boot on the newly taken image. The error message is as follows: Loading raid0.0 module md: raid0 personality registered as nr 2 Loading raid1.0 module md: raid 1 personality registered as nr 3 Mounting /proc filesystem md: Autodetecting RAID arrays md: autorun ... md: ... autorun DONE md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE Creating block devices Creating root device Mounting root filesystem EXT2-fs: unable to read superblock mount: error 22 mounting ext2 pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2 unmount /initrd/proc failed: 2 Freeing unused kernel memory: 164k freed Kernel Panic: No init found. Try passing init= option to kernel Similar descriptions of the problem has been annonnced with no official solution to it We would be tremendously grateful for any help recieved. [EMAIL PROTECTED] ---------------------------------------------------------------------- Comment By: *Patrick* (tepahe) Date: 2004-09-13 16:28 Message: Logged In: YES user_id=1120881 It seems as there i something wrong when the partitioning is taking place. After booting on the CD running linux rescue and running fsck on the / partition I get the information that the parition is corrupt. And it seems to boil down to that the parition table and the superblock contains different information regarding the size of the / partition. Strangely it doesn't complain about the /boot partition... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100259&aid=1027160&group_id=259 ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php _______________________________________________ Sisuite-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-devel
