I can't offer any solutions but have had a similar error in the past and am sure it has something to do a change to the disk structure. Did you install lilo into the mbr? Have you modify the mbr? Was the OS always on /dev/hda3? Dp. On 18 Jan 2006 at 16:04, Miguel González Castaños wrote: > Carl escribió: > > > At 12:36 18/01/2006, Miguel González Castaños wrote: > > > >> I have reviewed my configurations and I do not see why I getting > >> this error: > >> > >> - I have deactivated modules support, so EXT3 support is within the > >> kernel, not loaded as a module > > > > > > I always thought you REQUIRED ext3 support in the initrd image so > > the ext3 filesystem that holds the kernel can be mounted. > > I have read that filesystem modules should be compiled within the > kernel, not as modules, otherwise the system doesn´t boot. Initrd uses > the information in the /lib/modules/ directory to build the img file, > so I am not sure whether I have to use initrd, anyway I have tried to > use mkinitrd with a monolithic kernel and obviously didn´t work. Are > you sure of that point? > > Best Regards, > > Miguel > > > > > > - > : send the line "unsubscribe linux-admin" > in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo > info at http://vger.kernel.org/majordomo-info.html > - : send the line "unsubscribe linux-admin" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
