Sponsored Content
Operating Systems Solaris Solaris10 sparc T5120 PANIC during iscsi command Post 302613559 by vmcore on Tuesday 27th of March 2012 12:20:46 PM
Old 03-27-2012
Looks like you will need to do some patching on that server.

No, you need active support contract with Oracle do download patches. Did you call them and try to open service request with Oracle?
 

9 More Discussions You Might Find Interesting

1. Solaris

How do I run OpenWindows on a Solaris10 Sparc system?

How do I run OpenWindows on a Solaris10 Sparc system? I know it has been discontinued, but I have some applications that only run on OpenWin. And I would like to run Solaris10 instead of Solaris8, hence the problem. Can I download, install and run it with Solaris10? Thanks, Mike (5 Replies)
Discussion started by: mndavies
5 Replies

2. Solaris

Solaris 10 10/08 sparc + iSCSI

hi, I have installed Solaris 10 10/08 on sparc machine. I would like to configure iSCSI on that to mount SAN Volumes. Is there any need to install any additional patches for iSCSI to work. Thanks, Prashant. (4 Replies)
Discussion started by: prashantbhushan
4 Replies

3. Solaris

how can t recover a crashed Solaris10 on Sparc

Hi all, currently i'm running solaris 10 on Sun Fire v880 i crashed the system by mistake and now the system cannot boot It gets keep showing error messages on the eprom prompt is there any steps or procedures can i follow to recover the system to it's previous state thanks in advance (8 Replies)
Discussion started by: h@foorsa.biz
8 Replies

4. Solaris

Small issue with Sun Sparc Enterprise T5120

Good Day, We have bought Sun Sparc Enterprise T5120 with pre-installed Solaris 10 Sparc But i need on this server Solaris 9. I have inserted in to DVD-rom (USB DVD-rom) with Solaris 9 for Sparc. Then log into shell and type: reboot -- cdrom. System rebooted and i have this message: ... (3 Replies)
Discussion started by: A.Shalin
3 Replies

5. Solaris

Solaris10 -> iscsi -> equiliogic lun

We "lose" the iscsi device after a reboot - i.e., it appears in /dev/rdsk and /dev/dsk but format cannot find it. Obviously, it won't mount either. This happens for two separately defined luns. We must be missing a step in iscsiadm. The luns are defined as targets, we can see them in... (2 Replies)
Discussion started by: jim mcnamara
2 Replies

6. Web Development

not able to build mod_auth_mysql.c on solaris10 sparc with apache 1.3.34 and mysql 5.1.50

Hello , I have s Solaris 10 10/09 s10x_u8wos_08a X86 OS. I installed Apache 1.3.34 and MYSQL 5.1.50. while executing the following command to compile the mod_auth_mysql.c module sudo ./apxs -c -L/d00/tbls/mysql/lib -I/d00/tbls/mysql/include -lmysqlclient -lm -lz mod_auth_mysql.c. result of it... (2 Replies)
Discussion started by: cnighojkar
2 Replies

7. Solaris

Can You Mount FAT32 iSCSI Target in Solaris 10 (sparc)?

I get "mount: I/O error" when trying to mount an existing FAT32 iSCSI target. I also tried formatting the iSCSI target with fdisk and got fdisk: "Error in ioctl DKIOCSMBOOT" Details -- According to the format command, the whole disk is allocated to slice 6 and /dev/rdsk shows this as:... (0 Replies)
Discussion started by: ctafret
0 Replies

8. UNIX for Advanced & Expert Users

Can You Mount FAT32 iSCSI Target in Solaris 10 (sparc)?

I get "mount: I/O error" when trying to mount an existing FAT32 iSCSI target. I also tried formatting the iSCSI target with fdisk and got fdisk: "Error in ioctl DKIOCSMBOOT" Details -- According to the format command, the whole disk is allocated to slice 6 and /dev/rdsk shows this as:... (1 Reply)
Discussion started by: ctafret
1 Replies

9. Solaris

Solaris10 sparc nslookup error

Hi Experts, While trying to query nameserver using nslookup it is giving following error. root@prod # nslookup 10.1.61.21 ** server can't find 26.61.1.10.in-addr.arpa.: NXDOMAIN root@prod # (1) /etc/hosts 10.1.61.2 prod (2)I also added domain and namservers accordingly in... (6 Replies)
Discussion started by: sai_2507
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 08:39 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy