From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Configure grub for pxe boot and nfs-mounted root
Date: Tue, 26 Nov 2013 12:57:25 +0100 [thread overview]
Message-ID: <52948CA5.2070700@gmail.com> (raw)
In-Reply-To: <CAPSTsktzr66kC_bq2GKv3uowpnVu78kazj_4xxUeNgDKyh_S=A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1833 bytes --]
On 26.11.2013 12:26, Beeblebrox wrote:
>>> This doesn't seem to be a GRUB problem at all. I use tftpd which serves
> from /var/tftpd
> You are right, it is not a GRUB problem; it's a folder structure error
> in the way I approached the problem.
>
>>> boot/grub ($prefix) is where grub.cfg goes. Judging from your first
>>> question, is it possible you serve from a different folder than you think you do?
> No, the dhcp-tftp chain is correct. Because /data/amd64 is a jail
> (like a chroot) and the chroot is where dhcp and tftpd are running, I
> thought maybe the correct sytax should be "grub-mknetdir
> --net-directory=/ --subdir=boot/grub", then copy the files to
> boot/grub under the chroot folder. No difference, however and client
> drops to "grub rescue". /var/log/xferlog shows:
> in.tftpd[41762]: RRQ from 192.168.2.34 filename i386-pc/core.0
> in.tftpd[41762]: tftp: client does not accept options
> in.tftpd[41763]: RRQ from 192.168.2.34 filename i386-pc/core.0
> in.tftpd[41764]: RRQ from 192.168.2.34 filename /boot/grub/i386-pc/normal.mod
> in.tftpd[41764]: sending NAK (1, File not found) to 192.168.2.34
>
You misconfigured your server --net-directory is where root of tftp is.
--subdir is subdirectory of it. Yet your server has root in /boot/grub
and not subdirectory
> grub rescue> set
> cmdpath=(tftp,192.168.2.1)i386-pc
> prefix=(tftp,192.168.2.1)/boot/grub
> root=tftp,192.168.2.1
> net_pxe_boot_file=i386-pc/core.0
>
> I changed the dhcp-tftpd configuration from prefix /boot/grub/i386-pc,
> to test whether the problem lay in tftpd's inability to rad giles from
> folders one level up (cd ..). Same result.
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]
next prev parent reply other threads:[~2013-11-26 11:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 10:01 Configure grub for pxe boot and nfs-mounted root Beeblebrox
2013-11-26 10:10 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-26 11:26 ` Beeblebrox
2013-11-26 11:57 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-11-25 15:29 Beeblebrox
2013-11-25 15:32 ` Vladimir 'phcoder' Serbinenko
2013-11-24 8:14 Beeblebrox
2013-11-24 8:32 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-25 16:25 ` Beeblebrox
2013-11-25 18:18 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-26 7:22 ` Beeblebrox
2013-11-26 7:56 ` Vladimir 'φ-coder/phcoder' Serbinenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52948CA5.2070700@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).