Date: Thu, 1 Mar 2012 11:53:40 +0100 (CET) From: egoitz@ramattack.net To: "Karl Pielorz" <kpielorz_lst@tdx.co.uk> Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD 9-R pxeboot fails with 'Mounting root filesystem rw failed'... Message-ID: <55469.194.30.18.3.1330599220.squirrel@www1.saremail.com> In-Reply-To: <0D52CADE287778C263E7EF6A@OctaHexa64-MkII> References: <0D52CADE287778C263E7EF6A@OctaHexa64-MkII>
next in thread | previous in thread | raw e-mail | index | archive | help
Take a look at freebsd-hackers mailing list... I have suggested some change in some Makefile and sh script in order to unless at this moment to be able to have an unattended system built with sysinstall (the idea I think it was to maintain sysinstall in 9.0 unless).... and using you're install.cfg.... At freebsd-hackers seems that people is pretty busy and can't look at this in order for committing or unless saying something about it... perhaps they're working on another thing or so, or don't know I assume they can't check this now... but like changes are not significant... I am going to do with the changes suggested and have tested and release builts fine and you can use Jumpstart without issues.. this way... So I recomend you reading last mails of mine in freebsd-hackers... Hope it helps, Bye! El Jue, 1 de Marzo de 2012, 11:24 am, Karl Pielorz escribió: > Hi, > > > I've got a 9.0-R amd64 system I'm trying to netboot / pxeboot from the > network, to install other machines (and do fixups etc.) > > I set this up as we setup previous versions here - but setting up a tftp > server, and nfs server - and 'dumping' the contents of the install CD to a > directory on the dhcp server, which is exported via nfs (it's exported > as read/write). > > The system kind of boots, but falls over with: > > > " > Interface em0 IP-Address 192.168.0.47 Broadcast 192.168.0.255 > Entropy harvesting: interrupts ethernet point_to_pick kickstart. > Starting file system checks: > mount_nfs: no <host>:<dirpath> nfs-name > Mounting root filesystem rw failed, startup aborted > ERROR: ABORTING BOOT (sending SIGTERM to parent)! > Mar 1 118:10 init: /bin/sh on /etc/rc terminated abnormally, going to > single user mode Enter full pathname of shell or RETURN for /bin/sh: > " > > > It looks like it's failing to 'remount' / promote the root file system as > read/write (It's definitely exported as read/write - I've tested it by > mounting it on another machine). If you start a shell at this point and > run mount, you get: > > " > 192.168.0.37:/usr2/netboot/os/9.0-amd64 on / (nfs, read-only) > devfs on /dev (devfs, local, multilabel) " > > > Is there something I have to set (e.g. in '/etc/rc.conf') in order to fix > this? > > Previous systems setup this way would always boot through to the > sysinstall menu. > > > Thanks, > > > -Karl > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55469.194.30.18.3.1330599220.squirrel>