Mounting on boot up

9 More Discussions You Might Find Interesting

1. Solaris

Help mounting nfs on boot on Solaris 11

Hello, I am looking for some assistance in mounting an nfs drive on boot, on a Solaris 11 machine. On my Solaris 9/10 machines, I have an entry for my nfs mount in /etc/vfstab, however when I add the same entry to my vfstab on Solaris 11, the drive will not mount on boot. After booting up, I...

2. Solaris

Solaris x86 installation using jumpstart does not local boot ( boot from hdd)

I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD...

3. Boot Loaders

Reboot and Select Proper Boot device or insert Boot media in select Boot device and press a key

Hello, I have kubuntu on my laptop and now I decided to switch to Windows 7. I made the bios settings properly (first choice is boot from cd\vd) but I see the error " reboot and select proper Boot device or insert Boot media in select Boot device and press a key " I have tried CD and...

4. SCO

stage 1 boot failure: error loading hd (40)/boot

hi SCO Unix 5.0.6 doesn't boot due to this problem: not a directory boot not found cannot open stage 1 boot failure: error loading hd (40)/boot Knows someone howto solve it?

5. Ubuntu

mounting shared folder at boot

Hi All Everytime a reboot my machine "hostB" I have to mount a shared (with machine "hostA" ) NFS folder giving this command sudo mount hostA:/sharedFolder /sharedFolder How to use fstab in order to do this automatically? I should say hostA:/sharedFolder /sharedFolder ...

6. Solaris

Mounting disk at boot

Hi once more :p Yesterday I reinstalled Solaris OS and now I can not mount pcfs HDD SunOS unknown 5.10 Generic_142901-03 i86pc i386 i86pc and what has been added in /etc/vfstab is /dev/dsk/c1t0d0p1:c - /podaci - pcfs - yes rw But as I said , my disk is...

7. Solaris

cannot find boot device and won't boot off cdrom

I'm running solaris 2.5.1. My main development server is DEAD, i can't even boot off the cdrom, it powers up, acts like it is starting the boot process but then says cannot find boot device. I've done the search here on this site and saw the other posts, but at the ok prompt it won't even let me...

8. Solaris

solaris boot problem boot error loading interpreter(misc/krtld)

When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error. cannot find mis/krtld boot error loading...

9. UNIX for Advanced & Expert Users

Cannot boot - Boot : Panic : File size out of range (EWS-UX/V unix)

Hey ! I am running EWS-UX/V (Rel 4.2) on NEC EWS/4800/330 station and I am having problems rebooting my station : I am getting the following message on display : BOOT : PANIC : File size out of range. According to user guide, this error is occuring when a file exceeding the limit and/or...

LEARN ABOUT FREEBSD

reboot

REBOOT(8)						    BSD System Manager's Manual 						 REBOOT(8)

NAME

     reboot, halt, fastboot, fasthalt -- stopping and restarting the system

SYNOPSIS

     halt [-lnpq] [-k kernel]
     reboot [-dlnpq] [-k kernel]
     fasthalt [-lnpq] [-k kernel]
     fastboot [-dlnpq] [-k kernel]

DESCRIPTION

     The halt and reboot utilities flush the file system cache to disk, send all running processes a SIGTERM (and subsequently a SIGKILL) and,
     respectively, halt or restart the system.	The action is logged, including entering a shutdown record into the user accounting database.

     The options are as follows:

     -d      The system is requested to create a crash dump.  This option is supported only when rebooting, and it has no effect unless a dump
	     device has previously been specified with dumpon(8).

     -k kernel
	     Boot the specified kernel on the next system boot.  If the kernel boots successfully, the default kernel will be booted on successive
	     boots, this is a one-shot option.	If the boot fails, the system will continue attempting to boot kernel until the boot process is
	     interrupted and a valid kernel booted.  This may change in the future.

     -l      The halt or reboot is not logged to the system log.  This option is intended for applications such as shutdown(8), that call reboot
	     or halt and log this themselves.

     -n      The file system cache is not flushed.  This option should probably not be used.

     -p      The system will turn off the power if it can.  If the power down action fails, the system will halt or reboot normally, depending on
	     whether halt or reboot was called.

     -q      The system is halted or restarted quickly and ungracefully, and only the flushing of the file system cache is performed (if the -n
	     option is not specified).	This option should probably not be used.

     The fasthalt and fastboot utilities are nothing more than aliases for the halt and reboot utilities.

     Normally, the shutdown(8) utility is used when the system needs to be halted or restarted, giving users advance warning of their impending
     doom and cleanly terminating specific programs.

SEE ALSO

     getutxent(3), boot(8), dumpon(8), nextboot(8), savecore(8), shutdown(8), sync(8)

HISTORY

     A reboot utility appeared in Version 6 AT&T UNIX.

BSD
								 October 11, 2010							       BSD

UNIX for Dummies Questions & Answers