interactive stop on boot
Hi -- I'm running a Tombstone machine that's functioning as a server. The machine is located somewhere with a fast connection, and not somewhere that I have easy access to. As such, I want this machine to do its best to boot up and get onto the network, no matter what happens on boot, so that I have a chance to actually fix the problem. Lately when it boots it runs into an NFS mounting error, claiming that some of my NFS-mounted drives have unexpected inconsistencies. It says unexpected error - help! and then quits to a /bin/sh single-user-mode prompt. As I am 10 miles away, this is decidedly unhelpful. I don't care if it can't mount some irrelevant drive or not; I want it to boot up and ask me questions later. Is there a way that I can set the machine to do its best to boot no matter what it finds at boot time? Thanks in advance for any help you can provide, - Jason PS -- Boot messages not available, as the machine is down at the moment and I can't get over there to type enter exitenter until later this afternoon. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interactive stop on boot
On Friday 14 March 2008 11:24:57 am Jason Barnes wrote: Hi -- I'm running a Tombstone machine that's functioning as a server. The machine is located somewhere with a fast connection, and not somewhere that I have easy access to. As such, I want this machine to do its best to boot up and get onto the network, no matter what happens on boot, so that I have a chance to actually fix the problem. Lately when it boots it runs into an NFS mounting error, claiming that some of my NFS-mounted drives have unexpected inconsistencies. It says unexpected error - help! and then quits to a /bin/sh single-user-mode prompt. As I am 10 miles away, this is decidedly unhelpful. I don't care if it can't mount some irrelevant drive or not; I want it to boot up and ask me questions later. You probably want your NFS entries in fstab to have the noauto option, and you _definitely_ want the last two fields to be zeroes. Even if you _do_ want the NFS mounts to come up at boot I would still set them to be noauto and then write your own script to try to mount them later. Is there a way that I can set the machine to do its best to boot no matter what it finds at boot time? Thanks in advance for any help you can provide, The bootup rc script is just a sh script, you can hack it to do whatever you want. That said, it only bails out if there's a (potentially) significant problem. Given that this is a remote machine, you should be extra-careful when modifying anything to do with the startup process, especially fstab or any firewall rules. You could also look at options like a serial console, IP KVM, or something like a LightsOut card for your system. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interactive stop on boot
On Mar 14, 2008, at 11:24 AM, Jason Barnes wrote: Hi -- I'm running a Tombstone machine that's functioning as a server. The machine is located somewhere with a fast connection, and not somewhere that I have easy access to. As such, I want this machine to do its best to boot up and get onto the network, no matter what happens on boot, so that I have a chance to actually fix the problem. Lately when it boots it runs into an NFS mounting error, claiming that some of my NFS-mounted drives have unexpected inconsistencies. It says unexpected error - help! and then quits to a /bin/sh single-user-mode prompt. As I am 10 miles away, this is decidedly unhelpful. I don't care if it can't mount some irrelevant drive or not; I want it to boot up and ask me questions later. Is there a way that I can set the machine to do its best to boot no matter what it finds at boot time? Thanks in advance for any help you can provide, Depends on the whether or not the system needs something from the NFS mount at boot time. If it doesn't then you would do well to use amd (man 8 amd) to handle the mount. The short of is that amd automates the process of mounting a filesystem by presenting a directory. When a process requests a file within that directory amd performs the mount. Amd helps by deferring the mount until something actually needs something from the remote filesystem. Simpler still would be to change the mounts entry to noauto in /etc/ fstab. However then you or someone else will have to perform the mount when you need the filesystem. -- Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interactive stop on boot
Yeah, what CHris said. Also, there is an option you can put in fstab to allow the automount, and background the NFS mounts ... so that if the mount fails the boot will continue. Again, as mentioned, this will only work if the OS and your connection method (ssh daemon?) are not dependant on the NFS mounts. Here is what my fstab looks like. Note line 6 that specifies the -t=10,-b options (to timeout the mount after 10 seconds and to background the nfs mount). # DeviceMountpoint FStype Options Dump Pass# /dev/da0s1b noneswapsw 0 0 /dev/da0s1a / ufs rw 1 1 /dev/da0s1f /home ufs userquota,rw0 2 /dev/da0s1d /usrufs rw 2 2 /dev/da0s1e /varufs rw 2 2 nfsserver:/mnt /mntnfs -t=10,-b,rw 0 0 -Grant - Original Message - From: Christopher Sean Hilton [EMAIL PROTECTED] To: Jason Barnes [EMAIL PROTECTED] Sent: Friday, March 14, 2008 12:03 PM Subject: Re: interactive stop on boot On Mar 14, 2008, at 11:24 AM, Jason Barnes wrote: Hi -- I'm running a Tombstone machine that's functioning as a server. The machine is located somewhere with a fast connection, and not somewhere that I have easy access to. As such, I want this machine to do its best to boot up and get onto the network, no matter what happens on boot, so that I have a chance to actually fix the problem. Lately when it boots it runs into an NFS mounting error, claiming that some of my NFS-mounted drives have unexpected inconsistencies. It says unexpected error - help! and then quits to a /bin/sh single-user-mode prompt. As I am 10 miles away, this is decidedly unhelpful. I don't care if it can't mount some irrelevant drive or not; I want it to boot up and ask me questions later. Is there a way that I can set the machine to do its best to boot no matter what it finds at boot time? Thanks in advance for any help you can provide, Depends on the whether or not the system needs something from the NFS mount at boot time. If it doesn't then you would do well to use amd (man 8 amd) to handle the mount. The short of is that amd automates the process of mounting a filesystem by presenting a directory. When a process requests a file within that directory amd performs the mount. Amd helps by deferring the mount until something actually needs something from the remote filesystem. Simpler still would be to change the mounts entry to noauto in /etc/ fstab. However then you or someone else will have to perform the mount when you need the filesystem. -- Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interactive stop on boot
On Friday 14 March 2008 16:24:57 Jason Barnes wrote: Lately when it boots it runs into an NFS mounting error, claiming that some of my NFS-mounted drives have unexpected inconsistencies. It says unexpected error - help! and then quits to a /bin/sh single-user-mode prompt. As I am 10 miles away, this is decidedly unhelpful. I don't care if it can't mount some irrelevant drive or not; I want it to boot up and ask me questions later. man mount_nfs(8), specifically -R, -b, -i and -s. And indeed omit the fsck check as said earlier. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: interactive stop on boot
Jason, If there isn't anything needed from the NFS mounts, you can add intr,soft options to the /etc/fstab for each NFS share. Intr allows you to interrupt the NFS process with CTRL-C. You may not be available to do this, but you could call a user to do it. Soft allows the NFS client to fail, instead of hang. Or you could just delete the entries or have them noauto. Also, verify that the dump and pass# are set to zero. At least pass#, as if it is any other number, the background fschk will try to run and hang if not available (not ideal to run fschk on NFS mounts anyway) Hope this helps. David Wassman Message: 13 Date: Fri, 14 Mar 2008 08:24:57 -0700 From: Jason Barnes [EMAIL PROTECTED] Subject: interactive stop on boot To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1 Hi -- I'm running a Tombstone machine that's functioning as a server. The machine is located somewhere with a fast connection, and not somewhere that I have easy access to. As such, I want this machine to do its best to boot up and get onto the network, no matter what happens on boot, so that I have a chance to actually fix the problem. Lately when it boots it runs into an NFS mounting error, claiming that some of my NFS-mounted drives have unexpected inconsistencies. It says unexpected error - help! and then quits to a /bin/sh single-user-mode prompt. As I am 10 miles away, this is decidedly unhelpful. I don't care if it can't mount some irrelevant drive or not; I want it to boot up and ask me questions later. Is there a way that I can set the machine to do its best to boot no matter what it finds at boot time? Thanks in advance for any help you can provide, - Jason PS -- Boot messages not available, as the machine is down at the moment and I can't get over there to type enter exitenter until later this afternoon. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interactive stop on boot
These suggestions look really good -- thanks for your help everyone. I'll let you know how they work :) - Jason ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
