[mythtv-users] Struggling with Diskless clients on Ubuntu (probably OT)

Nick Rout nick.rout at gmail.com
Tue Jun 1 20:15:07 UTC 2010


On Wed, Jun 2, 2010 at 12:38 AM, Mark Small <msmall at eastlink.ca> wrote:
> On May 31, 2010 21:15:15 Nick Rout wrote:
>> On Tue, Jun 1, 2010 at 11:16 AM, Emmanuel <eallaud at gmail.com> wrote:
>> > Ben Lancaster a écrit :
>> >> Hi list,
>> >>
>> >> I've been trying to get diskless clients up and running on Ubuntu Lucid
>> >> Lynx for the past couple of days, but have hit a bit of a brick wall.
>> >> Here's the situation:  Using the "mythbuntu-diskless-server-standalone",
>> >> I set up DHCP and created a mythbuntu image (ltsp-build-client
>> >> --mythbuntu). The DHCP server works correctly and machines are able to
>> >> load the kernel and start booting (vmlinuz and initrd.img), but hang as
>> >> soon as the mythbuntu boot screen appears, the boot output shows:
>> >>
>> >> udhcp[286]: Sending discover...
>> >> udhcp[286]: Seneding select for 192.168.1.24...
>> >> udhcp[286]: Lease of 192.168.1.25 obtained, lease time 43200
>> >> IP-Config: eth0 hardware address 00:0c:29:ca:04:4f mtu 1500 DHCP RARP
>> >>
>> >> ...and then just sits there.
>> >>
>> >> /var/log/daemon.log from the server shows the following output during
>> >> the boot process:
>> >>
>> >> dhcpd: DHCPDISCOVER from 00:0c:29:ca:04:4f via eth0
>> >> dhcpd: DHCPOFFER on 192.168.1.25 to 00:0c:29:ca:04:4f via eth0
>> >> dhcpd: DHCPREQUEST for 192.168.1.25 (192.168.1.98) from
>> >> 00:0c:29:ca:04:4f via eth0
>> >> dhcpd: DHCPACK on 192.168.1.25 to 00:0c:29:ca:04:4f via eth0
>> >> in.tftpd[1595]: RRQ from 192.168.1.25 filename /ltsp/i386/pxelinux.0
>> >> in.tftpd[1595]: tftp: client does not accept options
>> >> in.tftpd[1596]: RRQ from 192.168.1.25 filename /ltsp/i386/pxelinux.0
>> >> in.tftpd[1597]: RRQ from 192.168.1.25 filename
>> >> /ltsp/i386/pxelinux.cfg/564d3d34-8815-be6a-ec2d-e0d50aca044f
>> >> in.tftpd[1598]: RRQ from 192.168.1.25 filename
>> >> /ltsp/i386/pxelinux.cfg/01-00-0c-29-ca-04-4f
>> >> in.tftpd[1599]: RRQ from 192.168.1.25 filename
>> >> /ltsp/i386/pxelinux.cfg/C0A80119
>> >> in.tftpd[1600]: RRQ from 192.168.1.25 filename
>> >> /ltsp/i386/pxelinux.cfg/C0A8011
>> >> in.tftpd[1602]: RRQ from 192.168.1.25 filename
>> >> /ltsp/i386/pxelinux.cfg/C0A801
>> >> in.tftpd[1603]: RRQ from 192.168.1.25 filename
>> >> /ltsp/i386/pxelinux.cfg/C0A80
>> >> in.tftpd[1604]: RRQ from 192.168.1.25 filename
>> >> /ltsp/i386/pxelinux.cfg/C0A8
>> >> in.tftpd[1605]: RRQ from 192.168.1.25 filename
>> >> /ltsp/i386/pxelinux.cfg/C0A in.tftpd[1606]: RRQ from 192.168.1.25
>> >> filename /ltsp/i386/pxelinux.cfg/C0 in.tftpd[1607]: RRQ from
>> >> 192.168.1.25 filename /ltsp/i386/pxelinux.cfg/C in.tftpd[1608]: RRQ from
>> >> 192.168.1.25 filename
>> >> /ltsp/i386/pxelinux.cfg/default
>> >> in.tftpd[1609]: RRQ from 192.168.1.25 filename /ltsp/i386/vmlinuz
>> >> in.tftpd[1610]: RRQ from 192.168.1.25 filename /ltsp/i386/initrd.img
>> >> dhcpd: DHCPDISCOVER from 00:0c:29:ca:04:4f via eth0
>> >> dhcpd: DHCPOFFER on 192.168.1.25 to 00:0c:29:ca:04:4f via eth0
>> >> dhcpd: DHCPREQUEST for 192.168.1.25 (192.168.1.98) from
>> >> 00:0c:29:ca:04:4f via eth0
>> >> dhcpd: DHCPACK on 192.168.1.25 to 00:0c:29:ca:04:4f via eth0
>> >> dhcpd: DHCPDISCOVER from 00:0c:29:ca:04:4f via eth0
>> >> dhcpd: DHCPOFFER on 192.168.1.25 to 00:0c:29:ca:04:4f via eth0
>> >
>> > A very wild guess: is it normal that after dowloading the kernel the
>> > client sends another dhcp request.
>>
>> I think it is, the first request is from the pxe client, the other one
>> is from the linux system. The linux system doesn't inherit the pxe's
>> address.
>> _______________________________________________
>
> Try passing some arguments to the kernel command line within you pxelinux.cfg
> dir.  On my debian client, I pass the following.
>
> ip=dhcp root=/dev/nfs
>
> The full option for my  lubuntu boot from iso image looks like this
>
>        MENU LABEL LUBUNTU 10.04 Beta
>        kernel lubuntu/vmlinuz
>        append initrd=lubuntu/initrd.lz ip=dhcp boot=casper netboot=nfs
> nfsroot=192.168.4.1:/mnt/nfs/lubuntu nosplash
>

My understanding is that ubuntu doesn't use nfs, but some other system
for mounting root. (nbd I think it's called)


More information about the mythtv-users mailing list