Sponsored Content
Full Discussion: Help with mirroring rpool
Operating Systems Solaris Help with mirroring rpool Post 302995763 by os2mac on Wednesday 12th of April 2017 12:24:57 AM
Old 04-12-2017
well as man bootadm specifically said NOT to use s2. I would try again with the other installer but not s2.
 

10 More Discussions You Might Find Interesting

1. Solaris

rpool issue

My system is showing following .. how can i remove this rpool .. ? zpool status -v rpool pool: rpool state: UNAVAIL status: One or more devices could not be opened. There are insufficient replicas for the pool to continue functioning. action: Attach the missing device and... (0 Replies)
Discussion started by: fugitive
0 Replies

2. Solaris

How to change hostid saved in rpool?

Hi, We have a Sun M5000. I am now trying to boot the second system domain by using the boot disk (a mirrored boot disk actually) of the first domain (if succeed then no OS installation is needed for the second domain). I got the following errors: SPARC Enterprise M5000 Server, using Domain... (21 Replies)
Discussion started by: aixlover
21 Replies

3. Solaris

ZFS rpool physical disk move

I'd like to finish setting up this system and then move the secondary or primary disk to another system that is the exact same hardware. I've done things like this in the past with ufs and disk suite mirroring just fine. But I have yet to do it with a zfs root pool mirror. Are there any... (1 Reply)
Discussion started by: Metasin
1 Replies

4. Solaris

Create rpool manually

Hi All; My server's root partition was encapsulated with VxVM, I try to convert it to ZFS. I successfully de-encapsulated root. Now I try to mirror 2 root disks using ZFS. But I receive following error: # zpool create rpool mirror c0t0d0s0 c0t1d0s0 invalid vdev specification use '-f' to... (6 Replies)
Discussion started by: reseki
6 Replies

5. Solaris

How to access content of problematic rpool ?

Hi guys, I have a Solaris 10 x86 server with 2 physical disks. It had a ZFS rpool on the first disk c0t0d0s0. The server stopped booting with some error like "Cannot find bootfile". I booted with Solaris DVD and re-installed the operating system on the second disk with a different pool... (0 Replies)
Discussion started by: ARPcPro
0 Replies

6. Solaris

Resize rpool

Hi, I have rpool about 500G. So i want to use 210G from rpool and assign mount point as /database. I seek in google and couldn't found it. Does anyone know how to achieve it? Thanks. (2 Replies)
Discussion started by: mzainal
2 Replies

7. Solaris

Zfs rpool size

Hi everyone, I am doing housekeeping of my Solaris 11 for zfs snapshot to reduce the snapshot size. I have already cleared the / file system, however the rpool size still not reduced. Filesystem Size Used Available Capacity Mounted on rpool/ROOT/solaris-2 98G 6.9G ... (2 Replies)
Discussion started by: freshmeat
2 Replies

8. Solaris

Need help to understand zfs rpool space allocation

Hi, I am unable to understand that, in one of my servers while df -kh Filesystem Size Used Available Capacity Mounted on rpool/ROOT/solaris-2 98G 11G 29G 29% / Even the Root FS filled on 40gb and system becomes unstable. it is showing... (4 Replies)
Discussion started by: anuragr
4 Replies

9. Solaris

Trying to create ZFS slice on rpool

I have a 240GB disk as rpool. I have installed Solaris 11.3 to a partition which is 110GB. Now I have another 130GB which is unallocated. I want to use that additional space as a temporary folder to be shared between Solaris and Linux. The additional space had no /dev/dsk/c2t4... entry so I used... (8 Replies)
Discussion started by: kebabbert
8 Replies

10. Solaris

How to increase the size of rpool in Solaris 11?

Hi Please let me know how to increase the size of rpool in solaris 11 in ldom. I know how to map the new LUN to LDOM after that please let me know the procedure to increase the rpool and how to identify new disk in OBP level of ldom as I need to set the new/lun to be my new boot device. (5 Replies)
Discussion started by: hb00
5 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 03:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy