[syslinux] PXELINUX: initrd loading failed

Muhammad Ammar mammar at gmail.com
Thu Sep 30 23:20:25 PDT 2010


Actually OS boots successfully but after a long time(approx 18 min). It
seems that the culprit is NIC, due to which it takes too much time to
download the image.

I will try boot with new NIC.

Very very thanks to all of you for kind and great help

Regards,

On Thu, Sep 30, 2010 at 8:33 PM, Gene Cumm <gene.cumm at gmail.com> wrote:

> On Thu, Sep 30, 2010 at 11:21, Muhammad Ammar <mammar at gmail.com> wrote:
> > no effect with
> >
> > boot: linux0
> >
> > still hanged
> >
> > The frustrating thing is that, there is not single message which can
> atleast
> > tell whats going on.
>
> Also, remove the word "quiet" from your APPEND statement.
>
> > Regards,
> >
> > On Thu, Sep 30, 2010 at 5:32 PM, Gene Cumm <gene.cumm at gmail.com> wrote:
> >
> >> On Thu, Sep 30, 2010 at 07:16, Muhammad Ammar <mammar at gmail.com> wrote:
> >> > I build a minimal FC13 using kickstart and livecd-creator.
> >> >
> >> > Then i created vmlinuz0 and initrd0.img using livecd-iso-to-pxeboot
> shell
> >> > script.
> >> >
> >> > The  'root=' and 'rootfstype=' parameters were added
> >> > by livecd-iso-to-pxeboot shell script.
> >> >
> >> > Now i have installed 1GB RAM, the following message has gone now
> >> >
> >> >  initrd too large to handle, disabling initrd
> >> >  Kernel panic - not syncing: VFS: Unable to mount root fs
> >> > on unknown-block(0,0)
> >> >
> >> > but it still not loading the OS and hanged(show the syslinux menu and
> >> upon
> >> > menu entry selection nothing happens)
> >>
> >> Are you using menu.c32/vesamenu.c32?  If so, exit from the menu system
> >> to the "boot: " prompt and type "linux0" (the LABEL in question;
> >> without quotes, of course) and watch its output.  This should help you
> >> in seeing if there's a hidden error.
> >>
> >> > Regards,
> >> >
> >> > On Thu, Sep 30, 2010 at 4:00 PM, Geert Stappers <stappers at stappers.nl
> >> >wrote:
> >> >
> >> >> Op 20100930 om 15:11 schreef Muhammad Ammar:
> >> >> > On Thu, Sep 30, 2010 at 2:39 PM, Ferenc Wagner <wferi at niif.hu>
> wrote:
> >> >> > > Muhammad Ammar <mammar at gmail.com> writes:
> >> >> > >
> >> >> > > > initrd too large to handle, disabling initrd
> >> >> > > > Kernel panic - not syncing: VFS: Unable to mount root fs on
> >> >> > > > unknown-block(0,0)
> >> >> > > >
> >> >> > > > Size of initrd0.img is approx. 317 MB
> >> >> > > > Size of vmlinuz is approx. 4 MB
> >> >> > > >
> >> >> > > > Note: The problem is on just one system, all other systems boot
> >> >> > > > without any problem.
> >> >> > >
> >> >> > > Maybe this system hasn't got enough memory for this initrd?
> >> >> >
> >> >> > I have a 512MB RAM in it. Is this not enough?
> >> >> > How can i calculate amount of memory needed for network boot?
> >> >>
> >> >> I'm not sure there is an "out of memory error".
> >> >>
> >> >> What I see is :
> >> >> > > > Kernel panic - not syncing: VFS: Unable to mount root fs on
> >> >> > > > unknown-block(0,0)
> >> >>
> >> >> So we have 'Unable to mount root fs'  and "unknown-block"
> >> >>
> >> >> Please explain what the idea is behind
> >> >>
> >> >> | label linux0
> >> >> | menu label MyFedora13 (default)
> >> >> |   kernel vmlinuz0
> >> >> | APPEND rootflags=loop initrd=initrd0.img root=live:/FC13.iso
> >> >> | rootfstype=iso9660 rw liveimg quiet selinux=0 rhgb rd_NO_LUKS
> rd_NO_MD
> >> >> | noiswmd blacklist nouveau
> >> >>
> >> >> especial the idea about 'root=' and 'rootfstype='
> >> >>
> >> >>
> >> >> Cheers
> >> >> Geert Stappers
> >>
> >> --
> >> -Gene
> >>
> >> _______________________________________________
> >> Syslinux mailing list
> >> Submissions to Syslinux at zytor.com
> >> Unsubscribe or set options at:
> >> http://www.zytor.com/mailman/listinfo/syslinux
> >> Please do not send private replies to mailing list traffic.
> >>
> >>
> > _______________________________________________
> > Syslinux mailing list
> > Submissions to Syslinux at zytor.com
> > Unsubscribe or set options at:
> > http://www.zytor.com/mailman/listinfo/syslinux
> > Please do not send private replies to mailing list traffic.
> >
> >
>
>
>
> --
> -Gene
>
> "No one ever says, 'I can't read that ASCII(plain text) e-mail you sent
> me.'"
>
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.
>
>



More information about the Syslinux mailing list