I see my problem. Since I am using pxe instead of PXELINUX, the kernel
argument root=/dev/ram0 was not being passed to the kernel. So, I started
with a fresh initrd from the ltsp distribution and set pxe to provide this
argument. First hiccup is again the usage message from init (there is, by
the way, no init in the initrd image, so the only init can be the one that
is mounted from /opt/ltsp/i386/sbin/init). I edited linuxrc and added an
argument to init and got much further. The failure is a call to busbox
(?!), which causes me to think that something is still using the utilities
in the initrd (oldroot). The Busybox Usage message succeeds:
VFS: Mounted root (ext2 filesystem) readonly
Freeing unused kernel memory: 76k freed
BusyBox v0.60.2 (2002.02.28-04:43+0000) multi-call binary
...
help?
-don
On Tue, 30 Sep 2003 [EMAIL PROTECTED] wrote:
> On Tue, 30 Sep 2003, Don Burns wrote:
>
> >
> >
> > Hi Jim,
> >
> > Thanks for the response...
> >
> > On Tue, 30 Sep 2003 [EMAIL PROTECTED] wrote:
> >
> > > On Mon, 29 Sep 2003, Don Burns wrote:
> > >
> > > >
> > > > Hi ltsp list.
> > > >
> > > > I'm back after a year or so, working on a new configuration of diskless
> > > > clients. I've noticed a few things have changed and I am also trying to
> > > > clean the cobwebs from my memory on how this stuff all works. Some help
> > > > would be appreciated.
> > > >
> > > > My diskless client is an ASUS A7N8X nforce2-based MOBO, Athlon XP 2200+,
> > > > and 128 MB of memory. I noticed some discussion on the list about
> > > > troubles with using the nVidia chipset, but this was not an issue. It
> > > > simply required building the nvnet.o driver from nVidia with the target
> > > > kernel, plopping it into the right directory, depmodding and voila. I did
> > > > have to do a couple of custom things to get the kernel to find the right
> > > > driver, but it loaded and used it just fine.
> > > >
> > > > My problems are three:
> > > >
> > > > 1) PXELINUX
> > > >
> > > > I am using PXE from the client machine, a simple flag to turn on in the
> > > > bios. PXELINUX loads on the client, but never gets past:
> > > >
> > > > My IP address seems to be 0A000065 10.0.0.101
> > > > ip=10.0.0.101:10.0.0.11:10.0.0.1:255.255.255.0
> > > > (happy blinking cursor)
> > > >
> > > > My /tftpboot directory has a pxelinux.cfg/0A000065 file and a
> > > > pxelinux.cfg/default, but there is never an attempt at downloading them.
> > > > The last message in my /var/log/messages file on the server is:
> > > >
> > > > Sep 30 06:01:08 blackbox in.tftpd[2742]: RRQ from 10.0.0.101 filename
> > > > pxelinux.0
> > > >
> > > > SO, I tried using the pxe server distributed with RedHat 9 and got much
> > > > further.
> > > >
> > > > 2) linuxrc script
> > > >
> > > > I'm sure it is my oversight, but there are two places in the linuxrc
> > > > script that don't seem right to me. One, is that the last line in the
> > > > script is:
> > > >
> > > > exec /sbin/init
> > > >
> > > > With no specified run level. This results in a usage message from init:
> > > >
> > > > Usage: init 0123456SsQqAaBbCcUu
> > >
> > >
> > > If you are getting an error, them I suspect the workstation is
> > > executing the wrong init. The /linuxrc script is supposed to mount
> > > a new root via NFS, and do a pivot root. If you are getting an error,
> > > i'm guessing that the pivot root failed, and you are still running
> > > the busybox init that is in the initrd, rather than running the
> > > normal /sbin/init that is on the server.
> > >
> >
> > I've entered some debugging into linuxrc, listing the '/' directory before
> > the pivot_root and after and get the expected results: they are different.
> > To be sure, I put this at the end of linuxrc:
> >
> > echo "This is a test" /tmp/dummy
> >
> > After the boot, the file /opt/ltsp/i386/tmp/dummy exists and contains the
> > contents "This is a test". So, it looks like pivot_root is succeeding,
> > but I am still getting the final failure:
>
>
> This still shows a problem,
>
> the /tmp directory of the workstation is supposed to be in ram on
> the workstation. There's no way you should be able to write
> something to /tmp/dummy on the workstation, and then view it from
> the server. It isn't supposed to exist on the server.
>
> So, something's wrong with either creating or mounting the ram
> filesystem on /tmp of the workstation.
>
>
> >
> > Kernel panic: VFS: Unable to mount root fs on 01:01
> >
> > Can you clarify what 01:01 is supposed to be? Is this a designation for
> > ram disk or something?
>
> No, it shouldn't be doing that at all. 01:01 doesn't mean anything to
> me.
>
> >
> > So, I'm also still left with the questions as to why init would fail with
> > a usage message now that I am reasonably sure that the right sbin/init is
> > being called (I just tested by running /opt/ltsp/i386/sbin/init on the
> > server and also got a usage message), and why the root file system is
> > mounted read-only.
>
> The root filesystem is SUPPOSED to be read-only. The last thing you
> want to have happen is for one workstation to be modifying things
> in the root fs, that other workstations are depending on.
>
>
> Jim.
>
>
>
> >
> > Thanks for your patience.
> >
> > -don
> >
> >
> > >
> > > >
> > > > I added an init level to get past this. The next failure comes when the
> > > > message "init: cannot create /tmp/initrunlvl". Upon investigation, this
> > > > file system is mounted by the script read-only. I chnaged this to rw and
> > > > tried again.
> > >
> > > Again, the wrong /sbin/init could cause this.
> > >
> > >
> > > One thing to check, is that you are mounting the correct directory
> > > via NFS. Is it '/opt/ltsp/i386' ?
> > >
> > > >
> > > > 3) Final message:
> > > >
> > > > Kernel panic: VFS: Unable to mount root fs on 01:01
> > > >
> > > > I'm stopped here, not sure how to proceed or trouble shoot. Any ideas
> > > > what 01:01 is? Any help would be much appreciated.
> > > >
> > > > For reference, I am using ltsp_core-3.0.9-0, ltsp_kernel-3.0.11-0, and
> > > > building the kernels and drivers with ltsp_initrd_kit-3.0.10.
> > >
> > > Why are you using an older initrd_kit ? Nevermind, my mistake. I
> > > put a new initrd_kit on the download page, but never updated the links
> > > on the instructions-3.0.html page. It's updated now.
> > >
> > > Jim McQuillan
> > > [EMAIL PROTECTED]
> > >
> > >
> > >
> > > >
> > > > Thanks!
> > > >
> > > > -don
> > > >
> > > >
> > > >
> > > > -------------------------------------------------------
> > > > This sf.net email is sponsored by:ThinkGeek
> > > > Welcome to geek heaven.
> > > > http://thinkgeek.com/sf
> > > > _____________________________________________________________________
> > > > Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
> > > > https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> > > > For additional LTSP help, try #ltsp channel on irc.freenode.net
> > > >
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This sf.net email is sponsored by:ThinkGeek
> > > Welcome to geek heaven.
> > > http://thinkgeek.com/sf
> > > _____________________________________________________________________
> > > Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
> > > https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> > > For additional LTSP help, try #ltsp channel on irc.freenode.net
> > >
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _____________________________________________________________________
> > Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
> > https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> > For additional LTSP help, try #ltsp channel on irc.freenode.net
> >
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _____________________________________________________________________
> Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
> https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help, try #ltsp channel on irc.freenode.net
>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
