From: Andrew Walrond <andrew@walrond.org>
To: linux-kernel@vger.kernel.org
Subject: 2.5.bk no longer boots from NFS root after bk pull this morning
Date: Tue, 14 Jan 2003 10:03:51 +0000 [thread overview]
Message-ID: <3E23E087.9020302@walrond.org> (raw)
2.5 has been booting fine over NFS for ages, but after getting latest
stuff with a bk pull this morning, it no longer works
Do I need to do something new, or has something busted?
The relevant bits from dmesg are
Sending DHCP requests ., OK
IP-Config: Got DHCP answer from 10.0.0.1, my address is 10.0.0.103
IP-Config: Complete:
device=eth0, addr=10.0.0.103, mask=255.255.0.0, gw=10.0.0.1,
host=hal3.office, domain=office, nis-domain=(none),
bootserver=10.0.0.1, rootserver=10.0.0.1,
rootpath=/eboot/slash/hal.office
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 10.0.0.1
Looking up port of RPC 100005/1 on 10.0.0.1
net/sunrpc/rpc_pipe.c: rpc_lookup_path failed to find path
/mount/clntc398a880
RPC: Couldn't create pipefs entry /mount/clntc398a880
Root-NFS: Server returned error -13 while mounting /eboot/slash/hal.office
VFS: Unable to mount root fs via NFS, trying floppy.
Kernel panic: VFS: Unable to mount root fs on 02:00
Andrew Walrond
next reply other threads:[~2003-01-14 9:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 10:03 Andrew Walrond [this message]
2003-01-14 10:09 ` 2.5.bk no longer boots from NFS root after bk pull this morning William Lee Irwin III
2003-01-14 10:30 ` Andrew Walrond
2003-01-14 11:24 ` William Lee Irwin III
2003-01-14 11:25 ` William Lee Irwin III
2003-01-14 15:32 ` Trond Myklebust
2003-01-14 16:24 ` Andrew Walrond
2003-01-14 19:02 ` Trond Myklebust
2003-01-15 10:22 ` Andrew Walrond
2003-01-15 11:59 ` Andrew Walrond
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=3E23E087.9020302@walrond.org \
--to=andrew@walrond.org \
--cc=linux-kernel@vger.kernel.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).