Sponsored Content
Operating Systems Solaris Restoring a Root File System that was on a metadevice Post 302528588 by bartus11 on Tuesday 7th of June 2011 12:25:37 PM
Old 06-07-2011
You have to rebuild the boot archive first. After logging into single user mode, run this:
Code:
bootadm update-archive -f

Then clear the service state and reboot the system.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

URGENT, root file system is 99%

help, urgently root file is 99% hi, this iptrace causes my root file system to be 99%. iptrace writes to a file but i didn not specify any file so how? and how to reduce my root file system since i suspect that it is iptrace which causes this.? thanks (8 Replies)
Discussion started by: yls177
8 Replies

2. Filesystems, Disks and Memory

root file system full

Hi I have a Solaris 2.5.1 system. Recently my file system is full and i couldn't find what flood my root file system. Anyone can suggext any directories i should look out for. I am using Samba and Patrol agent. I am just usng this server as a file server, users cannot login into the system,... (1 Reply)
Discussion started by: owls
1 Replies

3. HP-UX

Root File system Space

Hi I'm using HP-UX 11.00, the root file system is as shown below. Several time it reach 100% used, to free some space I use to reboot the system. What can I do to free some space without rebooting the machine? Filesystem kbytes used avail %used Mounted on /dev/vg00/lvol3 ... (2 Replies)
Discussion started by: cgege
2 Replies

4. Solaris

Root file system is 82% full

Hi I want to find out the reason that why root partition is 82% full? when i did fu -k / then most of files were created on /var . can you please help me to find out what I need to do in order to find the reason. Regards Ajwat (2 Replies)
Discussion started by: Ajwat
2 Replies

5. Solaris

Why Veritas is not used for root file system.

Dear All, In our environment we use SDS (Solaris Vlume Manager) for root file system.So, I am wondering why Veritas is not use for the same. root@abc # df -kh Filesystem size used avail capacity Mounted on /dev/md/dsk/d10 30G 22G 6.9G 77% / /devices ... (3 Replies)
Discussion started by: Reboot
3 Replies

6. UNIX for Advanced & Expert Users

how to make a full system backup excluding data and restoring it to a new system

Hi, In order to have a sand box machine that I could use to test some system changes before going to production state, I'd like to duplicate a working system to a virtual one. Ideally, I'd like to manage to do it this way : - Make a full system backup excluding the user file system (this... (7 Replies)
Discussion started by: pagaille
7 Replies

7. Solaris

unable to boot afer restoring root partion manages by veritas

Hi all, After restoring the / FS on a netra 240. It is unable to boot the system. The message displayed is the following: "The file just loaded does not appear to be executable" Bellow, the content of /etc/vfstab before restoring: #more /etc/vfstab... (0 Replies)
Discussion started by: faberarnold
0 Replies

8. UNIX for Dummies Questions & Answers

Root File System

Hi, Please someone tell me, what are the contents of root file sysytem? and significance of it, what are all possible ways to mount root file system? (5 Replies)
Discussion started by: laxmi Sharma
5 Replies

9. Solaris

Migration of system having UFS root FS with zones root to ZFS root FS

Hi All After downloading ZFS documentation from oracle site, I am able to successfully migrate UFS root FS without zones to ZFS root FS. But in case of UFS root file system with zones , I am successfully able to migrate global zone to zfs root file system but zone are still in UFS root file... (2 Replies)
Discussion started by: sb200
2 Replies

10. Solaris

Restoring a system from a backup

I have backed up the contents of my Solaris 10 machine in its entirety, and I'm trying to figure out if I can somehow use this archive to restore my old system just as it was on a new machine. Assuming I have all files from my old machine backed up, is this possible? What I've been trying to do... (6 Replies)
Discussion started by: unblockable
6 Replies
bootadm(1M)						  System Administration Commands					       bootadm(1M)

NAME
bootadm - manage bootability of GRUB-enabled operating system SYNOPSIS
/sbin/bootadm update-archive [-vn] [-R altroot [-p platform]] /sbin/bootadm list-archive [-vn] [-R altroot [-p platform]] x86 only /sbin/bootadm set-menu [-R altroot [-p platform]] key=value /sbin/bootadm list-menu [-R altroot [-p platform]] DESCRIPTION
The bootadm command manages the boot archive and, with x86 boot environments, the 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 a recovery procedure. The set-menu sub- command 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 EXAMPLES section for typical output from the list-menu option. Note that OpenBoot PROM (OBP)-based machines, such as SPARC systems, do not use GRUB and have no boot menu manageable by bootadm. The bootadm command determines dynamically the options supported by the image to be managed, so that bootadm invoked on one platform can be used to manage diskless clients of a different platform type. SUBCOMMANDS
The bootadm command has the following subcommands: update-archive Updates current boot archive if required. Applies to both SPARC and x86 platforms. list-archive Lists the files and directories to be included in the boot archive. Applies to both SPARC and x86 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 x86 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 x86 platforms only. OPTIONS
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. -p platform The platform, or machine hardware class, of the client. The platform type can only be specified together with -R, and is generally use- ful only for managing a diskless client where the client is of a different platform class than the server. Platform must be one of i86pc, sun4u, or sun4v. -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. EXAMPLES
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. EXIT STATUS
The following exit values are returned: 0 The command completed successfully. 1 The command exited due to an error. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ SEE ALSO
boot(1M), installgrub(1M), attributes(5) Consult the GRUB home page, under: http://www.gnu.org/ SunOS 5.11 25 Apr 2008 bootadm(1M)
All times are GMT -4. The time now is 05:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy