Re: Diskless Boot Problem
kevin stovall wrote: I am trying to set up diskless boot with FreeBSD 6.0 BETA2. I am using PXE which is successful and the diskless box finds the kernel fine, but it hangs right before it would normally give the login prompt. It displays the date and then hangs. I am unable to SSH in from other machine. It boots fine into single user mode. Has anyone experienced this or have any ideas? I just followed my own guide (www.daemonsecurity.com/pxe) from the beginning again and ended up with a login prompt and could login and get a shell. I have learned that dhclient should not be used, the interface is correctly configured on boot and any further client specific configuration can be passed by other means, I am considering LDAP or some specially formatted config file. Cheers, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt Subject ID: 9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72 Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Diskless Boot Problem
kevin stovall wrote: Thanks for responding and sorry it took me so long to respond. I am still having the same problem that I was. / is mounted through nfs. Do you know if the dhclient does the same as you described in 6? Also, I think that they did away with mfs in version 6. you should (and have?) mount / read-only, then mount /var either as a mfs or nfs mounted read-write. If there is no writable /var, dhclient cannot store the lease - this is true both in 5.x and 6.x. If you look through /etc/rc.d/var (there is an equivalent one for tmp) you will see it has three modes: yes, no and auto. If set to yes, a mfs /var partition is created, if auto, the startup scripts will check if there is a writable /var, if not, then an mfs /var is created - this is default. There are good reasons for using mfs for /tmp and /var, as well as for not: by using mfs you have no cleanup, and no personal data is disclosed if logout causes a reboot every time. However, in particular for /var there are data that is usefull to keep: IIRC latex stores generated fonts there. If you have an mfs /var then the problem mentioned should not cause nfs-mounts to be lost because the lease is stored in the mfs. But if /var is an nfs mount then you may have a problem. I sent a problem report on this, it was closed because I didn't get back on it. Reason is that I haven't had time to set up diskless FBSD6 environment. So, I'm not sure, however, if you include output from the terminal (yes I know it's tideus to copy), I can see if I can interpret it. Cheers, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt Subject ID: 9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72 Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Diskless Boot Problem
Yes, / is read-only and /var is rw. Here is my fstab: 192.168.0.200:/home/diskless_ro / nfsro 0 0 192.168.0.200:/home/diskless_rw/var /var nfs rw 0 0 192.168.0.200:/home/diskless_rw/tmp /tmp nfs rw 0 0 192.168.0.200:/usr /usr nfsrw 0 0 proc/proc procfs rw 0 0 I will try to get more of the terminal input tomorrow. Here is the last few lines Trying to mount root from nfs:192.168.0.200:/home/diskless_ro NFS ROOT: 192.168.0.200:/home/diskless_ro Interface fxp0 IP-Address 192.168.0.196 Broadcast 192.168.0.255 Date Also, I will try setting varmfs and tmpmfs to YES tomorrow to see if that works. you should (and have?) mount / read-only, then mount /var either as a mfs or nfs mounted read-write. If there is no writable /var, dhclient cannot store the lease - this is true both in 5.x and 6.x. If you look through /etc/rc.d/var (there is an equivalent one for tmp) you will see it has three modes: yes, no and auto. If set to yes, a mfs /var partition is created, if auto, the startup scripts will check if there is a writable /var, if not, then an mfs /var is created - this is default. There are good reasons for using mfs for /tmp and /var, as well as for not: by using mfs you have no cleanup, and no personal data is disclosed if logout causes a reboot every time. However, in particular for /var there are data that is usefull to keep: IIRC latex stores generated fonts there. If you have an mfs /var then the problem mentioned should not cause nfs-mounts to be lost because the lease is stored in the mfs. But if /var is an nfs mount then you may have a problem. I sent a problem report on this, it was closed because I didn't get back on it. Reason is that I haven't had time to set up diskless FBSD6 environment. So, I'm not sure, however, if you include output from the terminal (yes I know it's tideus to copy), I can see if I can interpret it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Diskless Boot Problem
kevin stovall wrote: Yes, / is read-only and /var is rw. Here is my fstab: 192.168.0.200:/home/diskless_ro / nfsro 0 0 192.168.0.200:/home/diskless_rw/var /var nfs rw 0 0 192.168.0.200:/home/diskless_rw/tmp /tmp nfs rw 0 0 192.168.0.200:/usr /usr nfsrw 0 0 proc/proc procfs rw 0 0 Question: what is your /etc/exports? Did you export all rw or /home/diskless_ro ro? Thing is that it's tricky to have both rw and ro exports on the same partition. Cheers, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt Subject ID: 9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72 Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Diskless Boot Problem
I exported everything rw. / -alldirs -maproot=root -network 192.168.0 -mask 255.255.255.0 /home -alldirs -maproot=root -network 192.168.0.0 -mask 255.255.255.0 Question: what is your /etc/exports? Did you export all rw or /home/diskless_ro ro? Thing is that it's tricky to have both rw and ro exports on the same partition. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Diskless Boot Problem
kevin stovall wrote: I exported everything rw. / -alldirs -maproot=root -network 192.168.0 -mask 255.255.255.0 /home -alldirs -maproot=root -network 192.168.0.0 -mask 255.255.255.0 and what do you see if you run showmount(8) ? Cheers, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt Subject ID: 9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72 Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Diskless Boot Problem
kevin stovall wrote: I exported everything rw. / -alldirs -maproot=root -network 192.168.0 -mask 255.255.255.0 /home -alldirs -maproot=root -network 192.168.0.0 -mask 255.255.255.0 is /usr a separate disklabel? because, then it doesn't appear to be exported. Cheers, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt Subject ID: 9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72 Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Diskless Boot Problem
# showmount Hosts on localhost: 192.168.0.196 and what do you see if you run showmount(8) ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Diskless Boot Problem
kevin stovall wrote: # showmount Hosts on localhost: 192.168.0.196 It's ok if you read the manpage to see what interesting options there are to get some more info. If you want help, then you also need to provide the interesting stuff. Using -e you can see what mounts are actually exported, fx. I have: # showmount -e Exports list on localhost: /var/diskless/FreeBSD 192.168.0.0 /var/diskless/192.168.0.16 192.168.0.16 /home 192.168.0.0 I pointed you to a guide I wrote - although I haven't finished it because I haven't got to the true diskless system yet - most of the advice I have given here is actually explained. Cheers, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt Subject ID: 9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72 Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Diskless Boot Problem
No, I have two disks, / and /home. is /usr a separate disklabel? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Diskless Boot Problem
Thanks for responding and sorry it took me so long to respond. I am still having the same problem that I was. / is mounted through nfs. Do you know if the dhclient does the same as you described in 6? Also, I think that they did away with mfs in version 6. BLOCKQUOTE style='PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #A0C6E5 2px solid; MARGIN-RIGHT: 0px'font style='FONT-SIZE:11px;FONT-FAMILY:tahoma,sans-serif'hr color=#A0C6E5 size=1 From: iErik Norgaard lt;[EMAIL PROTECTED]gt;/ibrTo: ikevin stovall lt;[EMAIL PROTECTED]gt;/ibrCC: ifreebsd-questions@freebsd.org/ibrSubject: iRe: Diskless Boot Problem/ibrDate: iWed, 14 Sep 2005 11:10:37 +0200/ibrgt;kevin stovall wrote:brgt;gt;The root file system seems to mount correctly, but I am not sure brgt;gt;how to tell. The root file system is /home/diskless_ro which is set brgt;gt;up correctly for NFS. I don't have a memory file system set up, so brgt;gt;this is likely the problem.brgt;brgt;You will use either or, not both. A memory file system will ocupy brgt;ram so if you don't have much it's not a good idea. Also, var and brgt;tmp may be created as mfs if these are not mounted or toggled in brgt;rc.conf. (see /etc/rc.d/var and /etc/rc.d/tmp) so you may run out of brgt;ram.brgt;brgt;Check that you can mount the nfs root device. There are some brgt;permission stuff to be aware of if you have multiple exports on the brgt;same device.brgt;brgt;I tried once, a while ago to set up diskless systems, and wrote my brgt;own guide to keep track of what I was doing, you can read it here:brgt;brgt; www.daemonsecurity.com/pxebrgt;brgt;I didn't get it working, my problem was that the dhclient of 5.4 brgt;would unconfigure the NIC before obtaining a new lease meaning that brgt;any NFS mounted filesystems was lost and then it couldn't write the brgt;lease file. This problem could posibly be solved by using mfs for brgt;/var and / but I only have 112 MB ram, so I prefered to have it nfs brgt;mounted.brgt;brgt;Cheers, Erikbrgt;brgt;--brgt;Ph: +34.666334818 web: brgt;www.locolomo.orgbrgt;S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crtbrgt;Subject ID: brgt;9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72brgt;Fingerprint: brgt;5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9brgt;___brgt;freebsd-questions@freebsd.org mailing listbrgt;http://lists.freebsd.org/mailman/listinfo/freebsd-questionsbrgt;To unsubscribe, send any mail to brgt;quot;[EMAIL PROTECTED]quot;br/font/BLOCKQUOTE ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Diskless Boot Problem
kevin stovall wrote: I am trying to set up diskless boot with FreeBSD 6.0 BETA2. I am using PXE which is successful and the diskless box finds the kernel fine, but it hangs right before it would normally give the login prompt. It displays the date and then hangs. I am unable to SSH in from other machine. It boots fine into single user mode. Has anyone experienced this or have any ideas? Does it correctly mount the root file system? What is your root file system? a memory file system downloaded with tftp or nfs mount? I had the same problem (I recall it hanging just after displaying the date) recently on my disked laptop because /etc/ttys was corrupt after a crash. Also, I had no problems booting in single-user mode. Cheers, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt Subject ID: 9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72 Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Diskless Boot Problem
The root file system seems to mount correctly, but I am not sure how to tell. The root file system is /home/diskless_ro which is set up correctly for NFS. I don't have a memory file system set up, so this is likely the problem. BLOCKQUOTE style='PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #A0C6E5 2px solid; MARGIN-RIGHT: 0px'font style='FONT-SIZE:11px;FONT-FAMILY:tahoma,sans-serif'hr color=#A0C6E5 size=1 From: iErik Norgaard lt;[EMAIL PROTECTED]gt;/ibrTo: ikevin stovall lt;[EMAIL PROTECTED]gt;/ibrCC: ifreebsd-questions@freebsd.org/ibrSubject: iRe: Diskless Boot Problem/ibrDate: iWed, 14 Sep 2005 10:00:09 +0200/ibrgt;kevin stovall wrote:brgt;gt;I am trying to set up diskless boot with FreeBSD 6.0 BETA2. I am brgt;gt;using PXE which is successful and the diskless box finds the kernel brgt;gt;fine, but it hangs right before it would normally give the login brgt;gt;prompt. It displays the date and then hangs. I am unable to SSH in brgt;gt;from other machine. It boots fine into single user mode. Has anyone brgt;gt;experienced this or have any ideas?brgt;brgt;Does it correctly mount the root file system? What is your root file brgt;system? a memory file system downloaded with tftp or nfs mount?brgt;brgt;I had the same problem (I recall it hanging just after displaying brgt;the date) recently on my disked laptop because /etc/ttys was corrupt brgt;after a crash. Also, I had no problems booting in single-user mode.brgt;brgt;Cheers, Erikbrgt;brgt;--brgt;Ph: +34.666334818 web: brgt;www.locolomo.orgbrgt;S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crtbrgt;Subject ID: brgt;9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72brgt;Fingerprint: brgt;5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9brgt;___brgt;freebsd-questions@freebsd.org mailing listbrgt;http://lists.freebsd.org/mailman/listinfo/freebsd-questionsbrgt;To unsubscribe, send any mail to brgt;quot;[EMAIL PROTECTED]quot;br/font/BLOCKQUOTE ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Diskless Boot Problem
kevin stovall wrote: The root file system seems to mount correctly, but I am not sure how to tell. The root file system is /home/diskless_ro which is set up correctly for NFS. I don't have a memory file system set up, so this is likely the problem. You will use either or, not both. A memory file system will ocupy ram so if you don't have much it's not a good idea. Also, var and tmp may be created as mfs if these are not mounted or toggled in rc.conf. (see /etc/rc.d/var and /etc/rc.d/tmp) so you may run out of ram. Check that you can mount the nfs root device. There are some permission stuff to be aware of if you have multiple exports on the same device. I tried once, a while ago to set up diskless systems, and wrote my own guide to keep track of what I was doing, you can read it here: www.daemonsecurity.com/pxe I didn't get it working, my problem was that the dhclient of 5.4 would unconfigure the NIC before obtaining a new lease meaning that any NFS mounted filesystems was lost and then it couldn't write the lease file. This problem could posibly be solved by using mfs for /var and / but I only have 112 MB ram, so I prefered to have it nfs mounted. Cheers, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt Subject ID: 9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72 Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
