Sponsored Content
Full Discussion: Cannot mount boot archive
Operating Systems Solaris Cannot mount boot archive Post 302381190 by incredible on Thursday 17th of December 2009 10:57:27 AM
Old 12-17-2009
you are not providing sufficient log/output. can you boot to single user mode first? capture and show whats the console message before it goes to single user/maintenance mode for login. And also for information, what model is this server?
 

10 More Discussions You Might Find Interesting

1. AIX

Unable to mount NFS share during boot

Hello Everyone, I have a pseries machine running AIX 4.3.3 that has an invalid IP in /etc/hosts. During a boot the system hangs because it's trying to mount an NFS share to this invalid IP. I've tried to boot the system from a mksysb (not sure if the device was defined as rmt0) and AIX CD... (0 Replies)
Discussion started by: jlslhills
0 Replies

2. Solaris

Boot problem: failed to mount /usr

My Solaris10 cannot boot after I made an error when apending the vfstab to: dev to mount======/dev/dsk/c0d0p1:1 device to fsck====== <blank> mount pt=========/Data FS Type==========pcfs fsck pass=========- mount at boot=====yes mount options===== <blank> My 'Data' partition is a... (3 Replies)
Discussion started by: maag
3 Replies

3. AIX

NFS does not mount on boot!

Hi, Can someone help me on this? I'm not able to enable a well working mounting process for NFS filesystems on boot time. On the server side (AIX 5.2) everything seems to be OK and correctly exported, seeing other clients (AIX 5.2) are able to mount normally on boot time. On a client in... (5 Replies)
Discussion started by: padawan75
5 Replies

4. Solaris

boot-archive issue

I had logged into Server via ALOM and was placed into runlevel 5 other than 3 which is default. I did a svcadm delete boot-archive, and was promptly placed in runlevel 3. Now, I am unable to do a telnet or login into the server through any other service. bash-3.00# svcs -a svcs -a STATE ... (3 Replies)
Discussion started by: praveenr
3 Replies

5. Solaris

Open Boot PROM - OK Prompt +dd +mount

Greetings friends, I would like to 'clone' the system/root hard disk with dd. (Solaris 10 on SPARC). If I understood correctly, 'OK Prompt' can use dd command? Can it mount drives? (to avoid any possibility of cloning the wrong drive, I'd like to output dd to file) thanks. (3 Replies)
Discussion started by: orange47
3 Replies

6. Solaris

archive logs mount point space check script

I have the below shell script which is checking /archlog mount point space on cappire(solaris 10) server. When the space usage is above 80% it should e-mail. When i tested this script it is working as expected. -------------------------------------------------------------------------... (0 Replies)
Discussion started by: dreams5617
0 Replies

7. Solaris

Need help to boot a server and mount all partitions

Hello, I am having an issue with a SUN FIRE V440. First of all, lots of mirrors and submirrors needed maintenance, so I applied #metasync to fix all of them, but I still couldn't mount all the partitions of the server . I tried to mount manually all the partitions that appear in the /etc/vfstab... (4 Replies)
Discussion started by: feg
4 Replies

8. Solaris

Boot-archive Problem

I disabled the boot-archive service by using #svcadm disable svc:/system/boot-archive:default then i rebooted my system but i am unable to boot. It throws the following errors CONSOLE LOGIN SERVICE(S) CANNOT RUN then it automatically asked me for the maintenance mode passwd. i logged... (3 Replies)
Discussion started by: dinu
3 Replies

9. Solaris

Cannot boot nor mount

After applying the latest patchset on a Sun v240 (SPARC, 64b Solaris 10), I got the below error: Boot device: disk File and args: | Evaluating: Out of memory Warning: Fcode sequence resulted in a net stack depth change of 1 Evaluating: Evaluating: The file just loaded does not... (2 Replies)
Discussion started by: LittleLebowski
2 Replies

10. Solaris

Boot archive file sizes are different on cluster units

Hi experts, I would have a question on boot archive files on solaris10 platform running on T5220 cluster servers. When we check the /platform/sun4v directory , and perform boot archive-list , we see that on both units same files exist. And when we mount the boot archive we see that all files... (0 Replies)
Discussion started by: dyavuzy1
0 Replies
bootadm(1M)															       bootadm(1M)

NAME
bootadm - manage bootability of GRUB-enabled operating system SYNOPSIS
/sbin/bootadm update-archive [-vn] [-R altroot] /sbin/bootadm list-archive [-vn] [-R altroot] only /sbin/bootadm set-menu [-R altroot] key=value /sbin/bootadm list-menu [-R altroot] The bootadm command manages the boot archive and GRUB (GRand Unified Bootloader) menu. The update-archive option provides a way for user to update the boot archive as a preventative measure or as part of the recovery procedure. The set-menu subcommand allows you to switch the auto-boot timeout and default boot entry in the GRUB menu. The list-menu subcommand displays the location of the GRUB menu and the current GRUB menu entries. While the typical location of the GRUB menu is /boot/grub/menu.lst, depending on the install method used the active GRUB menu might be located somewhere else. Use the list-menu subcommand to locate the active GRUB menu. For example, if a system was installed using Live Upgrade, the GRUB menu might not be located in the current boot environment. See the section for typical output from the list-menu option. Note that a SPARC system does not have the concept of a boot archive. The bootadm command on a SPARC system is intended for managing disk- less clients. SUBCOMMANDS
The bootadm command has the following subcommands: update-archive Updates current boot archive if required. Applies to both SPARC and platforms. list-archive Lists the files and directories to be included in the boot archive. Applies to both SPARC and platforms. set-menu Maintain the GRUB menu. The current GRUB menu is boot/grub/menu.lst, relative to root. Do not depend on this location, because it is subject to change. Applies to platforms only. list-menu Lists the location of the active GRUB menu, as well as the current GRUB menu entries. This includes the autoboot-timeout, the default entry number, and the title of each entry. Applies to platforms only. The bootadm command has the following options: -v In an update-archive operation, stale files are displayed on stderr. -n In an update-archive operation, archive content is checked but not updated. -R altroot Operation is applied to an alternate root path. Note - The root file system of any non-global zones must not be referenced with the -R option. Doing so might damage the global zone's file system, might compromise the security of the global zone, and might damage the non-global zone's file system. See zones(5). key=value Possible values are: default=entrynum The item number (for example, 0, 1, or 2) in the GRUB menu designating the operating system to boot when the timer expires. timeout=seconds The number of seconds before the operating system designated by the default item number is booted. If the value is -1, auto boot is disabled. Example 1: Updating the Current Boot Archive The following command updates the current boot archive: # bootadm update-archive Example 2: Updating the Boot Archive on an Alternate Root The following command updates the boot archive on an alternate root: # bootadm update-archive -R /a Example 3: Listing Installed OS Instances The following command lists the installed operating system instances in a GRUB menu: # bootadm list-menu default=0 timeout=10(0) Solaris10(1) Solaris10 Failsafe(2) Linux Example 4: Switching Default Boot Entry The following command refers to the menu displayed in the previous example. The user selects Linux (item 2). # bootadm set-menu default=2 Example 5: Listing GRUB Menu Entries and Location of GRUB Menu The following command lists the GRUB menu entries and the location of the GRUB menu: # bootadm list-menu The location for the active GRUB menu is: /stubboot/boot/grub/menu.lst default 0 timeout 10 0 Solaris10 1 Solaris10 failsafe 2 Linux Example 6: Displaying Location of GRUB Menu The following command displays the location of the GRUB menu: # bootadm list-menu The location for the active GRUB menu is: /dev/dsk/c0t1d0s0 (not mounted) The filesystem type of the menu device is <ufs> default 2 timeout 10 0 c0t1d0s3 1 c0t1d0s3 failsafe 2 Solaris10 3 Solaris10 failsafe In this example, the active GRUB menu is located on a device which is not mounted. To access the GRUB menu, mount the device and access the GRUB menu at <mountpoint>/boot/grub/menu.lst. The following exit values are returned: 0 The command completed successfully. 1 The command exited due to an error. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ boot(1M), installgrub(1M), attributes(5) The GRUB home page: http://www.gnu.org/software/grub/ 10 Oct 2005 bootadm(1M)
All times are GMT -4. The time now is 06:55 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy