Solaris 8 x86 system refuses to upgrade to Solaris 9

My x86 system successfully runs Solaris 8 (Feb. 2000 revision A) but refuses to upgrade to Solaris 9. When trying to boot one of the installation cds in anyone of the installation modes, the boot process proceeds till the message "booting kernel/unix, ... use is subject to license terms". Next I would expect setup messages for the network interface, but instead I get a blank screen with a cursor blinking top left, and that's the end of it.
Well, to be true, it's not really a problem of Solaris 9. The same thing happened when I tried to install a patch set on Solaris 8.
What ways of diagnosis do I have?
Is anything in Solaris 8 not upward compatible?
Thanks in advance for every hint!
Bernd.

OK after the DCA scans, it goes to a screen labeled "Boot Solaris" which indicates the boot drive. On that screen f4 is labeled Boot Tasks. Press f4 and go thru the settings to select the boot device and any of the other settings you might want to change. then f3 back to the boot screen and f2 continue. When the boot options screen appears, type in b -r. The DCA should not start up each time after that. To be honest, I had to do this a couple of times before something unknown to me made it finally work. Go figure!
Lee

Similar Messages

Tload for Solaris X86

I have a sun Storedge L9 hooked up to a Solaris X86 system and need to update the firmware and moving the loader to a sparc systems isn't feasible at the moment. Is there a Solaris X86 version of tload available
i.e. I want to apply the firmware updates in 112141-03, using Solaris X86
Thanks for any help.

Nevermind i found one in a newer patch for a different drive.

Solaris 10(x86) u4 8/07 Upgrade Install trashes disk label

In 4 attempts now to upgrade a working Solaris 10(x86) u2 6//06 system to Solaris 10 8/07 the upgrade fails. If the system reboots at the end of the upgrade, the system is stuck at the grub prompt. When options are set to NOT reboot at the end of the install, inspection of the system produces:
- I/O errors with df command for /a and /a/var (see next point for why)
- using format command to inspect partition table reveals that an "effectively empty" label with zero length slices for s0,s1,s3-s7 has been written to the disk effectively trashing the installation and the previously defined partition layout.
This upgrade failure occurs if using a non-upgraded 6/06 install or a fully updated install. The 6/06 install is partitioned with partitions for /, swap, /var, and /export/home. The system I am trying to upgrade is a test system (laptop with 768MB) and is basically a fresh install of 6/06. I am trying to define and validate the procedure to upgrade a 6/06 system to 8/07.
I have not explored using Live Upgrade yet as I suspect the same problem will occur to the target if the fault lies in the installer on the DVD.
Has anyone experienced this issue and can anyone point me in the right direction to remedy this failure?

In 4 attempts now to upgrade a working Solaris 10(x86) u2 6//06 system to Solaris 10 8/07 the upgrade fails. If the system reboots at the end of the upgrade, the system is stuck at the grub prompt. When options are set to NOT reboot at the end of the install, inspection of the system produces:
- I/O errors with df command for /a and /a/var (see next point for why)
- using format command to inspect partition table reveals that an "effectively empty" label with zero length slices for s0,s1,s3-s7 has been written to the disk effectively trashing the installation and the previously defined partition layout.
This upgrade failure occurs if using a non-upgraded 6/06 install or a fully updated install. The 6/06 install is partitioned with partitions for /, swap, /var, and /export/home. The system I am trying to upgrade is a test system (laptop with 768MB) and is basically a fresh install of 6/06. I am trying to define and validate the procedure to upgrade a 6/06 system to 8/07.
I have not explored using Live Upgrade yet as I suspect the same problem will occur to the target if the fault lies in the installer on the DVD.
Has anyone experienced this issue and can anyone point me in the right direction to remedy this failure?

How to upgrade oracle 32 to 64 bit on sun solaris x86 64 bit OS?

Hi,
I want to upgrade/convert 32 bit Oracle Database 10.2.0.2 to 64 bit database. Existing 32 bit database is RAC and it is running on Sun Solaris X86 64 bit OS.
First, I want to know is it possible?
If yes, then what are the exact steps?

Hi,
Such a migration can be done, just follow the steps in Metalink note 62290.1
It is important to remember that 64-bit database requires more shared pool memory so you should increase your shared pool size.
Liron Amitzi
Senior DBA consultant
[www.dbsnaps.com]
[www.orbiumsoftware.com]
Edited by: Liron Amitzi on Jul 1, 2009 3:08 PM

Installation problems (Solaris 10 3/05 release, on x86 system)

Late last year, i recieved a Solaris 10 installation DVD case, containing the intallation DVDs for SPARC and x86 systems.
after finally getting another hard drive (the other was too full), i tried booting the computer off the x86 disc, to install.
it went to the light grey screen where it asks for installation mode, i chose default interactive installation (option 1).
this is where the problem starts. It appears that before beginning the interactive installer, it gathers information about the computer (such as USB ports, 100mb/s connection, etc)
I have read this process should only take a few seconds.
BUT, after 2 hours, it appears to have locked up after displaying "Skipping RTSL 0"
(it may not be rtsl, but something similar, and it was after detecting the 100mb/s connection)
My question is: how do i get it to work so i can install Solaris, without having to wait those 2 hours that should only be a few seconds?
thx to those who answer, thanx
(ps: i have had no previous experience with solaris)

errm...
I do not know what TRS-80, VIC-20, or E10K mean, but i can try give you the hardware config (ps i'm installing solaris as a secondary OS in another
partition to XP, on the second HD (so there are 2 Hard drives in the computer).
WARNING: LIST VERY LONG AND POSSIBLY NOT WHAT YOU MEANT FOR ME TO POST (well.. i dont really know how to get HW configs, and what ones you require)
Omega technology ATX
Intel Celeron CPU 1.30 GHz, 512 MB RAM
From XP device manager:
Computer:
ACPI PC
Disk Drives:
ST340810A (partitioned into: C, F, G, and X which will be removed for C soon)
MDT MD400AB-00BVA0 (partitioned into D, and E)
the MDT is the new HD, and partition D will be used for solaris OS and extra space for stuff done in solaris).
Display adapters:
RADEON 9550
RADEON 9550 secondary
DVD/CD-ROM drives:
LG DVD-rom DRD8160B
Lite-on DVDRW SOHW-1673s
Standard floppy disk drive and controller
IDE ATA/ATAPI controllers:
Primary IDE Channel
Secondary IDE Channel
VIA bus master IDE controller
Easy internet keyboard
PS/2 mouse
soft V92 smart speakerphone modem
Monitors: LG 900B
Network adapters:
Surecom EP-320X-R 100/10/M PCI Adapter
Ports (COM & LPT):
COM 1 & COM2
printer port (LPT1)
Processors:
Intel Celeron CPU 1300MHz
Sound, video and game controllers:
Audio Codecs
Legacy Audio Drivers
Legacy Video Capture Devices
Media control Devices
Standard Game port
Unimodem Half-Duplex Audio Device
VIA AC'97 Audio Controller (WDM)
Video Codecs
System Devices:
ACPI fixed feature button
direct memory access controller
ISAPNP read data port
Microcode Update Device
Microsoft ACPI-compliant system
Microsoft system management BIOS driver
motherboard resources
Numeric data processor
PCI bus
Plug and play software device enumerator
programmable interrupt controller
system board
System CMOS/real time clock
System speaker
system timer
VIA CPU to AGP controller
VIA Tech CPU to PCI bridge
VIA Tech PCI to ISA bridge
VIA Tech power management controller
USB controllers:
NEC PCI to USB open host controller
NEC PCI to USB open host controller
standard enhanced PCI to USB host controller
USB root hub
USB root hub
USB root hub
USB root hub
USB root hub
VIA rev 5 or later USB universal host controller
VIA rev 5 or later USB universal host controller
well.. there we go. i hope thats what you wanted :)
thx for replying though.

Could not mount USB drive on Solaris 10 x86 system

Hi All,
I am having difficulty mounting a USB drive on Solaris 10 x86 system with the following different unsuccessful attempts:
# uname -a
SunOS venus 5.10 Generic_139556-08 i86pc i386 i86pc
# rmformat
Looking for devices...
 1. Volmgt Node: /vol/dev/aliases/cdrom0
 Logical Node: /dev/rdsk/c0t0d0s2
 Physical Node: /pci@0,0/pci-ide@4/ide@0/sd@0,0
 Connected Device: TEAC DV-28E-V 1.AC
 Device Type: DVD Reader
 2. Logical Node: /dev/rdsk/c4t0d0s2
 Physical Node: /pci@0,0/pci108e,534b@2,1/storage@9/disk@0,0
 Connected Device: WD My Book 1140 1007
 Device Type: Removable
 3. Volmgt Node: /vol/dev/aliases/rmdisk0
 Logical Node: /dev/rdsk/c4t0d0p0
 Physical Node: /pci@0,0/pci108e,534b@2,1/storage@9/disk@0,0
 Connected Device: WD My Book 1140 1007
 Device Type: Removable
# svcs volfs
STATE STIME FMRI
online Apr_13 svc:/system/filesystem/volfs:default# ls -lt /mnt
total 0
# mount -F pcfs /dev/dsk/c4t0d0p0:c /mnt
mount: I/O error
# mount -F pcfs /dev/rdsk/c4t0d0p0:c /mnt
mount: Block device required
# mount -F pcfs /dev/dsk/c4t0d0s2:c /mnt
mount: I/O error
# mount -F pcfs /dev/rdsk/c4t0d0s2:c /mnt
mount: Block device required
# fsck /dev/dsk/c4t0d0p0
Can't open /dev/rdsk/c4t0d0p0: I/O error
# fsck /dev/rdsk/c4t0d0p0
Can't open /dev/rdsk/c4t0d0p0: I/O error
# fsck /dev/dsk/c4t0d0s2
Can't open /dev/rdsk/c4t0d0s2: I/O error
# fsck /dev/rdsk/c4t0d0s2
Can't open /dev/rdsk/c4t0d0s2: I/O errorSecond try,
# svcadm disable volfs
# svcs volfs
STATE STIME FMRI
disabled 20:47:00 svc:/system/filesystem/volfs:default
# mount -F pcfs /dev/dsk/c4t0d0p0:c /mnt
mount: I/O errorLast try,
# mkdir /rmdisk
mkdir: Failed to make directory "/rmdisk"; File exists
# ls -lt /rmdisk
total 4
lrwxrwxrwx 1 root nobody 16 Oct 1 2009 rmdisk0 -> ./unnamed_rmdik
drwxr-xr-x 2 root nobody 512 Sep 30 2009 unnamed_rmdisk
# cd /rmdisk
# ls -lt
total 4
lrwxrwxrwx 1 root nobody 16 Oct 1 2009 rmdisk0 -> ./unnamed_rmdik
drwxr-xr-x 2 root nobody 512 Sep 30 2009 unnamed_rmdisk
# ls -lt unnamed_rmdisk
total 0
# ls -lt rmdisk0
lrwxrwxrwx 1 root nobody 16 Oct 1 2009 rmdisk0 -> ./unnamed_rmdik
# df -h
Filesystem size used avail capacity Mounted on
/dev/dsk/c1t0d0s0 5.1G 4.0G 1.1G 78% /
/devices 0K 0K 0K 0% /devices
ctfs 0K 0K 0K 0% /system/contract
proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
swap 5.9G 984K 5.9G 1% /etc/svc/volatile
objfs 0K 0K 0K 0% /system/object
sharefs 0K 0K 0K 0% /etc/dfs/sharetab
/usr/lib/libc/libc_hwcap2.so.1
 5.1G 4.0G 1.1G 78% /lib/libc.so.1
fd 0K 0K 0K 0% /dev/fd
swap 5.9G 148K 5.9G 1% /tmp
swap 5.9G 32K 5.9G 1% /var/run
/dev/dsk/c1t0d0s7 129G 1.7G 126G 2% /export/home
# /etc/init.d/volmgt stop
# svcs volfs
STATE STIME FMRI
disabled 21:02:31 svc:/system/filesystem/volfs:default
# pwd
/rmdisk
# cd /
# ls -lt /rmdisk
total 4
lrwxrwxrwx 1 root nobody 16 Oct 1 2009 rmdisk0 -> ./unnamed_rmdik
drwxr-xr-x 2 root nobody 512 Sep 30 2009 unnamed_rmdisk
# /etc/init.d/volmgt st
# svcs volfs
STATE STIME FMRI
disabled 21:02:31 svc:/system/filesystem/volfs:default
# /etc/init.d/volmgt start
volume management starting.
# svcs volfs
STATE STIME FMRI
online 21:04:44 svc:/system/filesystem/volfs:default
# svcs volfs
# mount | grep rmdisk
# pwd
# ls -lt /rmdisk
total 4
lrwxrwxrwx 1 root nobody 16 Oct 1 2009 rmdisk0 -> ./unnamed_rmdik
drwxr-xr-x 2 root nobody 512 Sep 30 2009 unnamed_rmdisk
# ls -lt /rmdisk/unnamed_rmdisk
total 0
# iostat -En
c0t0d0 Soft Errors: 3 Hard Errors: 0 Transport Errors: 0
Vendor: TEAC Product: DV-28E-V Revision: 1.AC Serial No:
Size: 0.00GB <0 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 3 Predictive Failure Analysis: 0
c1t0d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: HITACHI Product: HUS1514SBSUN146G Revision: SA04 Serial No: 0921B2Y3PC
Size: 146.81GB <146810535936 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
c1t1d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: HITACHI Product: HUS1514SBSUN146G Revision: SA04 Serial No: 0921B2Z5NC
Size: 146.81GB <146810535936 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
c4t0d0 Soft Errors: 21 Hard Errors: 0 Transport Errors: 0
Vendor: WD Product: My Book 1140 Revision: 1007 Serial No:
Size: 2000.37GB <2000365289472 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 21 Predictive Failure Analysis: 0
#This is a working production system with 2 146.81GB mirrored hard disks. There is no disk error for either local or external 2TB Western Digital USB disks that works on Windows 7 or XP.
Any idea on what else to look for?
Thanks in advance,
Jack
Edited by: 797805 on 6/06/2012 04:48

Hi All,
Looks like it was a driver / incompatibility / unsupported issue since 2 other much smaller USB keys (Lexar USB Flash Drive – 32GB, SanDisk Cruzer Colors – 4GB) were successfully mounted automatically by volfs service as follows:
# df -h
Filesystem size used avail capacity Mounted on
/dev/dsk/c1t0d0s0 5.1G 4.0G 1.1G 78% /
/dev/dsk/c1t0d0s7 129G 1.7G 126G 2% /export/home
/vol/dev/dsk/c3t0d0/unnamed_rmdisk#1:c 3.7G 2.4G 1.3G 65% /rmdisk/unnamed_rmdisk#1
/vol/dev/dsk/c2t0d0/unnamed_rmdisk:c 29G 96K 29G 1% /rmdisk/unnamed_rmdiskIt also appears that the Device status of Not Ready from “iostat –En” below may not be correct either since both smaller drives are working fine:
# iostat -En
c4t0d0 Soft Errors: 23 Hard Errors: 0 Transport Errors: 0
Vendor: WD Product: My Book 1140 Revision: 1007 Serial No:
Size: 2000.37GB <2000365289472 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 23 Predictive Failure Analysis: 0
c2t0d0 Soft Errors: 7 Hard Errors: 0 Transport Errors: 0
Vendor: Lexar Product: USB Flash Drive Revision: 1100 Serial No:
Size: 31.41GB <31406948352 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 7 Predictive Failure Analysis: 0
c3t0d0 Soft Errors: 60 Hard Errors: 8 Transport Errors: 0
Vendor: SanDisk Product: Cruzer Colors+ Revision: 8.02 Serial No:
Size: 4.02GB <4022337024 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 8 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0In other word, the same question remains on whether it is possible to install a driver to overcome this issue and where to such driver?
It is necessary to install additional driver that came with the disk on Windows XP platform. However,
Thanks again,
Jack

11 -- 11,1 Upgrade: pkg://solaris/system/library signature problems?

Hi all,
I have a vanilla 11 11/11 lab system (x64, in VirtualBox) that I've tried to upgrade to 11.1:
# uname -a
SunOS alpha 5.11 11.0 i86pc i386 i86pc
# pkg list entire
NAME (PUBLISHER) VERSION IFO
entire 0.5.11-0.175.0.0.0.2.0 i--
# pkg publisher
PUBLISHER TYPE STATUS URI
solaris origin online http://pkg.oracle.com/solaris/release/
It has full connectivity to the Internet, and I've tried pointing it to the public release repo, a local 11.1 repo that has had the update ISO injected into it, and with a single loopback repo pointing to only the upgrade ISO (sol-11_1-upgrade-repo.iso, md5 verified). In all 3 cases I get this at the first stage of the upgrade:
# pkg update
Creating Plan |
pkg update: A signature in pkg://solaris/system/[email protected],5.11-0.175.0.10.1.0.0:20120918T164707Z could not be verified for this reason:
The signature value did not match the expected value. Res: 0
The signature's hash is 235c7674d821032ae3eeda280c7837d1f1f4fdb5
I must be missing something simple, because I can't imagine a bad signature in the public or upgrade-ISO repos. Any ideas?
Thanks!

If possible, please file a support request for this issue through the My Oracle Support portal so that the details of the issue can be captured.
With that said, executing the following commands may provide a viable workaround:
pkg set-property signature-policy=ignore
pkg set-publisher --set-property signature-policy=ignore solaris
Once the above commands have been executed, attempt the pkg update again. If successful, then after rebooting to the new boot environment, reset the properties as follows:
pkg unset-property signature-policy
pkg set-publisher --unset-property signature-policy

Latest (November) EIS-Patching ISO for Solaris SPARC & X86 systems download.

Hi All,
I hope someone can assist as this has given me a headache for the last few days.
I require the latest (November) EIS-Patching ISO for Solaris SPARC & X86 systems.
I require the ISO and not just the Patch set.
Please advise.
Kind regards,
Paul

The current ISO (october) is available at the usual place : EIS for Partner
And for information, the next planned EIS will be available very soon but not this month.

From 7.3 on NT to 8 on Solaris x86?

Has Oracle ported Oracle8 for Solaris x86?

Hi,
usually I expect people to do a little research and I do not give everything chewed.
Point 4:
go to the
Oracle9i Database Migration Release 2 (9.2)
go to the chapter 3
Upgrading a Database to the New Oracle9i Release
go to the point:
Upgrade the Database Manually
Exactly from here:
http://download.oracle.com/docs/cd/B10501_01/server.920/a96530/upgrade.htm#1009200
Keep in mind
1) that the EXACT procedure you are following it is not indicated in this manual
2) you have to think a little ( do you have all the windows services created on the destination system? if not, you have to create them ... )
3) this procedure is not supported by SAP. It is a valid option but not supported by them. You have to practice until you get all the points correctly

Solaris 10 update 9 - live upgrade issues with ZFS

Hi
After doing a live upgrade from Solaris 10 update 8 to Solaris 10 update 9 the alternate boot environment I created is no longer bootable.
I have completed all the pre-upgrade steps like:
- Installing the latest version of live upgrade from the update 9 ISO.
- Create and test the new boot environment.
- Create a sysidcfg file used by the live upgrade that has auto_reg=disable in it.
There is also no errors while creating the boot environment or even when activating it.
Here is the error I get:
SunOS Release 5.10 Version Generic_14489-06 64-bit
Copyright (c) 1983, 2010, Oracle and/or its affiliates. All rights reserved.
NOTICE: zfs_parse_bootfs: error 22
Cannot mount root on altroot/37 fstype zfs
*panic[cpu0]/thread=fffffffffbc28040: vfs mountroot: cannot mount root*
ffffffffffbc4a8d0 genunix:main+107 ()
Skipping system dump - no dump device configured
Does anyone know how I can fix this?
Edited by: user12099270 on 02-Feb-2011 04:49

Found the culprit... *142910-17*... breaks it
System has findroot enabled GRUB
Updating GRUB menu default setting
GRUB menu default setting is unaffected
Saving existing file </boot/grub/menu.lst> in top level dataset for BE <s10x_u8wos_08a> as <mount-point>//boot/grub/menu.lst.prev.
File </etc/lu/GRUB_backup_menu> propagation successful
Successfully deleted entry from GRUB menu
Validating the contents of the media </admin/x86/Patches/10_x86_Recommended/patches>.
The media contains 204 software patches that can be added.
Mounting the BE <s10x_u8wos_08a_Jan2011>.
Adding patches to the BE <s10x_u8wos_08a_Jan2011>.
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Done!
The following requested patches have packages not installed on the system
Package SUNWio-tools from directory SUNWio-tools in patch 142910-17 is not installed on the system. Changes for package SUNWio-tools will not be applied to the system.
Package SUNWzoneu from directory SUNWzoneu in patch 142910-17 is not installed on the system. Changes for package SUNWzoneu will not be applied to the system.
Package SUNWpsm-ipp from directory SUNWpsm-ipp in patch 142910-17 is not installed on the system. Changes for package SUNWpsm-ipp will not be applied to the system.
Package SUNWsshdu from directory SUNWsshdu in patch 142910-17 is not installed on the system. Changes for package SUNWsshdu will not be applied to the system.
Package SUNWsacom from directory SUNWsacom in patch 142910-17 is not installed on the system. Changes for package SUNWsacom will not be applied to the system.
Package SUNWmdbr from directory SUNWmdbr in patch 142910-17 is not installed on the system. Changes for package SUNWmdbr will not be applied to the system.
Package SUNWopenssl-commands from directory SUNWopenssl-commands in patch 142910-17 is not installed on the system. Changes for package SUNWopenssl-commands will not be applied to the system.
Package SUNWsshdr from directory SUNWsshdr in patch 142910-17 is not installed on the system. Changes for package SUNWsshdr will not be applied to the system.
Package SUNWsshcu from directory SUNWsshcu in patch 142910-17 is not installed on the system. Changes for package SUNWsshcu will not be applied to the system.
Package SUNWsshu from directory SUNWsshu in patch 142910-17 is not installed on the system. Changes for package SUNWsshu will not be applied to the system.
Package SUNWgrubS from directory SUNWgrubS in patch 142910-17 is not installed on the system. Changes for package SUNWgrubS will not be applied to the system.
Package SUNWzoner from directory SUNWzoner in patch 142910-17 is not installed on the system. Changes for package SUNWzoner will not be applied to the system.
Package SUNWmdb from directory SUNWmdb in patch 142910-17 is not installed on the system. Changes for package SUNWmdb will not be applied to the system.
Package SUNWpool from directory SUNWpool in patch 142910-17 is not installed on the system. Changes for package SUNWpool will not be applied to the system.
Package SUNWudfr from directory SUNWudfr in patch 142910-17 is not installed on the system. Changes for package SUNWudfr will not be applied to the system.
Package SUNWxcu4 from directory SUNWxcu4 in patch 142910-17 is not installed on the system. Changes for package SUNWxcu4 will not be applied to the system.
Package SUNWarc from directory SUNWarc in patch 142910-17 is not installed on the system. Changes for package SUNWarc will not be applied to the system.
Package SUNWtftp from directory SUNWtftp in patch 142910-17 is not installed on the system. Changes for package SUNWtftp will not be applied to the system.
Package SUNWaccu from directory SUNWaccu in patch 142910-17 is not installed on the system. Changes for package SUNWaccu will not be applied to the system.
Package SUNWppm from directory SUNWppm in patch 142910-17 is not installed on the system. Changes for package SUNWppm will not be applied to the system.
Package SUNWtoo from directory SUNWtoo in patch 142910-17 is not installed on the system. Changes for package SUNWtoo will not be applied to the system.
Package SUNWcpc from directory SUNWcpc.i in patch 142910-17 is not installed on the system. Changes for package SUNWcpc will not be applied to the system.
Package SUNWftdur from directory SUNWftdur in patch 142910-17 is not installed on the system. Changes for package SUNWftdur will not be applied to the system.
Package SUNWypr from directory SUNWypr in patch 142910-17 is not installed on the system. Changes for package SUNWypr will not be applied to the system.
Package SUNWlxr from directory SUNWlxr in patch 142910-17 is not installed on the system. Changes for package SUNWlxr will not be applied to the system.
Package SUNWdcar from directory SUNWdcar in patch 142910-17 is not installed on the system. Changes for package SUNWdcar will not be applied to the system.
Package SUNWnfssu from directory SUNWnfssu in patch 142910-17 is not installed on the system. Changes for package SUNWnfssu will not be applied to the system.
Package SUNWpcmem from directory SUNWpcmem in patch 142910-17 is not installed on the system. Changes for package SUNWpcmem will not be applied to the system.
Package SUNWlxu from directory SUNWlxu in patch 142910-17 is not installed on the system. Changes for package SUNWlxu will not be applied to the system.
Package SUNWxcu6 from directory SUNWxcu6 in patch 142910-17 is not installed on the system. Changes for package SUNWxcu6 will not be applied to the system.
Package SUNWpcmci from directory SUNWpcmci in patch 142910-17 is not installed on the system. Changes for package SUNWpcmci will not be applied to the system.
Package SUNWarcr from directory SUNWarcr in patch 142910-17 is not installed on the system. Changes for package SUNWarcr will not be applied to the system.
Package SUNWscpu from directory SUNWscpu in patch 142910-17 is not installed on the system. Changes for package SUNWscpu will not be applied to the system.
Package SUNWcpcu from directory SUNWcpcu in patch 142910-17 is not installed on the system. Changes for package SUNWcpcu will not be applied to the system.
Package SUNWopenssl-include from directory SUNWopenssl-include in patch 142910-17 is not installed on the system. Changes for package SUNWopenssl-include will not be applied to the system.
Package SUNWdtrp from directory SUNWdtrp in patch 142910-17 is not installed on the system. Changes for package SUNWdtrp will not be applied to the system.
Package SUNWhermon from directory SUNWhermon in patch 142910-17 is not installed on the system. Changes for package SUNWhermon will not be applied to the system.
Package SUNWpsm-lpd from directory SUNWpsm-lpd in patch 142910-17 is not installed on the system. Changes for package SUNWpsm-lpd will not be applied to the system.
Package SUNWdtrc from directory SUNWdtrc in patch 142910-17 is not installed on the system. Changes for package SUNWdtrc will not be applied to the system.
Package SUNWhea from directory SUNWhea in patch 142910-17 is not installed on the system. Changes for package SUNWhea will not be applied to the system.
Package SUNW1394 from directory SUNW1394 in patch 142910-17 is not installed on the system. Changes for package SUNW1394 will not be applied to the system.
Package SUNWrds from directory SUNWrds in patch 142910-17 is not installed on the system. Changes for package SUNWrds will not be applied to the system.
Package SUNWnfsskr from directory SUNWnfsskr in patch 142910-17 is not installed on the system. Changes for package SUNWnfsskr will not be applied to the system.
Package SUNWudf from directory SUNWudf in patch 142910-17 is not installed on the system. Changes for package SUNWudf will not be applied to the system.
Package SUNWixgb from directory SUNWixgb in patch 142910-17 is not installed on the system. Changes for package SUNWixgb will not be applied to the system.
Checking patches that you specified for installation.
Done!
Approved patches will be installed in this order:
142910-17
Checking installed patches...
Executing prepatch script...
Installing patch packages...
Patch 142910-17 has been successfully installed.
See /a/var/sadm/patch/142910-17/log for details
Executing postpatch script...
Creating GRUB menu in /a
Installing grub on /dev/rdsk/c2t0d0s0
stage1 written to partition 0 sector 0 (abs 16065)
stage2 written to partition 0, 273 sectors starting at 50 (abs 16115)
Patch packages installed:
BRCMbnx
SUNWaac
SUNWahci
SUNWamd8111s
SUNWcakr
SUNWckr
SUNWcry
SUNWcryr
SUNWcsd
SUNWcsl
SUNWcslr
SUNWcsr
SUNWcsu
SUNWesu
SUNWfmd
SUNWfmdr
SUNWgrub
SUNWhxge
SUNWib
SUNWigb
SUNWintgige
SUNWipoib
SUNWixgbe
SUNWmdr
SUNWmegasas
SUNWmptsas
SUNWmrsas
SUNWmv88sx
SUNWnfsckr
SUNWnfscr
SUNWnfscu
SUNWnge
SUNWnisu
SUNWntxn
SUNWnv-sata
SUNWnxge
SUNWopenssl-libraries
SUNWos86r
SUNWpapi
SUNWpcu
SUNWpiclu
SUNWpsdcr
SUNWpsdir
SUNWpsu
SUNWrge
SUNWrpcib
SUNWrsgk
SUNWses
SUNWsmapi
SUNWsndmr
SUNWsndmu
SUNWtavor
SUNWudapltu
SUNWusb
SUNWxge
SUNWxvmpv
SUNWzfskr
SUNWzfsr
SUNWzfsu
PBE GRUB has no capability information.
PBE GRUB has no versioning information.
ABE GRUB is newer than PBE GRUB. Updating GRUB.
GRUB update was successfull.
Unmounting the BE <s10x_u8wos_08a_Jan2011>.
The patch add to the BE <s10x_u8wos_08a_Jan2011> completed.
Still need to know how to resolve it though...

Mounting a Solaris x86 CD/DVD from a remote Windows CD/DVD-ROM drive

Greetings, all.
Is it possible to mount a remote Windows CD/DVD-ROM drive? I have the Solaris 10x86 Companion Software DVD sitting in a CD/DVD-ROM drive that's installed on a Windows server on my network. It is shared-out (F:) and the two servers can ping each other. I've also confirmed the NFS services/daemons are running on the Solaris x86 machine. I've tried the following variations but, all have failed to produce successful results:
# mount -F nfs x.x.x.x:/f /mnt
nfs mount: x.x.x.x: : RPC: Program not registered
nfs mount: retrying: /mnt
# mount -F hsfs x.x.x.x:/f /mnt
mount: No such device
mount: cannot mount x.x.x.x:/f
# mount -F hsfs x.x.x.x:/F /mnt
mount: No such device
mount: cannot mount x.x.x.x:/F
[FYI: S10_106_SOFTWARE is the DVD's label as reported by Windows Explorer.]
# mount -F hsfs x.x.x.x:/S10_106_SOFTWARE /mnt
mount: No such device
mount: cannot mount x.x.x.x:/S10_106_SOFTWARE
# mount -F hsfs x.x.x.x:/s10_106_software /mnt
mount: No such device
mount: cannot mount x.x.x.x:/s10_106_software
# mount -F nfs x.x.x.x:/S10_106_SOFTWARE /mnt
nfs mount: x.x.x.x: : RPC: Program not registered
nfs mount: retrying: /mnt
# mount -F nfs x.x.x.x:/s10_106_software /mnt
nfs mount: x.x.x.x: : RPC: Program not registered
nfs mount: retrying: /mnt
# mount -F hsfs x.x.x.x:/f/s10_106_software /mnt
mount: No such device
mount: cannot mount x.x.x.x:/f/s10_106_software
# mount -F hsfs x.x.x.x:/F/s10_106_software /mnt
mount: No such device
mount: cannot mount x.x.x.x:/F/s10_106_software
# mount -F hsfs x.x.x.x:/f/S10_106_SOFTWARE /mnt
mount: No such device
mount: cannot mount x.x.x.x:/f/S10_106_SOFTWARE
# mount -F hsfs x.x.x.x:/F/S10_106_SOFTWARE /mnt
mount: No such device
mount: cannot mount x.x.x.x:/F/S10_106_SOFTWARE
I've also tried mounting it at bootup by adding the appropriate entry in the /etc/vfstab file but, this does not work as well. I've tried Google'ing for an answer to my issue but, I haven't been able to find anything that applies directly to what I'm reporting. It's usually chatter about mounting from one UNIX server to another. Any advice from the community would be greatly appreciated.

After three weeks, you deserve a reply. Windoze does
not natively support NFS.Also deserves a decent answer...
There are two ways to do this:
Install Microsoft's free "Windows Services for UNIX," which includes a Windows NFS server; or
Install the 'sharity' package (google for it); it provides Solaris systems the ability to mount Windows shares

After upgrading to Solaris 10 "Can't load the root filesystem" on V245

I have a Sunfire V245 that was running on Solaris 9 (very stable). I upgraded to Solaris 10 (6/06) this morning and everything seemed to go smoothly. After the upgrade the system rebooted, but will not boot. I get the following uptput;
Rebooting with command: boot
Boot device: disk File and args:
SunOS Release 5.10 Version Generic_118833-17 64-bit
Copyright 1983-2005 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
pxb_bcm: cannot load driver
Cannot load drivers for /pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/disk@0,0:a
Can't load the root filesystem
Type 'go' to resume
"go" attempts to reboot, but I end up back in the same place.
Please help.
Thanks in advanced,
Craig

It seems like the driver for that device does not exist. Since the system installed successfully it means that it S10 did find a disk. I wonder if that was a different disk than the default disk. Please boot to the miniroot and check the disk info.

Announcing availability of x86 hosted cross compiler for SPARC/Solaris

We are pleased to announce the release for GCC For Sun Systems 4.2.0 cross compilers!
This is a Solaris/x86 hosted compiler with target code generation for
SPARC/Solaris systems. If you develop on your OpenSolaris, or Solaris
x86 laptop or desktop, you can now start compiling your sources for
SPARC systems. Almost all features available in the
native SPARC GCC For Sun Systems 4.2.0 compiler are available
for use in the cross compiler. Please refer to the mini cross compiler howto
page for additional details on install and usage, and gotchas in cross
development environment.
Please continue to provide us your feedback and issues, which helps
us make the product better.
Thanks
GCCFSS team

Can GCCFSS also cross compile from in reverse - from SPARC to x86/x64?
Thank you

Oracle 8.1.5 Client/WLS/Solaris x86

has anyone been able to get Oracle's client 8.1.5 running on Solaris x86 in conjunction with WLS to talk to back-end Oracle? Any help would be greatly appreciated.thanks.

This will not work. We have not built the native libraries to work with
Solaris on Intel..
I suggest trying the platform independent type 4 JDBC driver available for
free from Oracle. It is supported (as is any JDBC driver) with WebLogic
Server. To download it:
Go to http://www.oracle.com and select the "Download" option.
From the resulting page, use the "Select Utility or Driver" dropdown to
select Oracle JDBC drivers
From the resulting page, scroll down a little (since SQLJ stuff appears at
the top).
Or, to go directly there:
http://technet.oracle.com/software/tech/java/sqlj_jdbc/software_index.htm
Thanks,
Michael
Michael Girdley
BEA Systems Inc
"Dean Davis" <[email protected]> wrote in message
news:3a267487$[email protected]..
has anyone been able to get Oracle's client 8.1.5 running on Solaris x86in conjunction with WLS to talk to back-end Oracle? Any help would be
greatly appreciated.thanks.

Oracle 10g RAC to 11g RAC Upgrade on Solaris

Hi,
We are planning to do a migration of a 4 Node Oracle 10g RAC on Solaris 9 to 11g with Solaris 10. We'd like know what would be the best path to take. We cannot afford any downtime!
Options: Are these feasible? Which option is best? Any documents links?
a) Do a rolling upgrade of Oracle from 10g to 11g. Then take down individual nodes and upgrade the Solaris OS from 9 to 10 and bring them up back into the cluster. Is there any known issues taking this path? Is a rolling upgrade like this possible?
b) Do an upgrade of the Solaris OS from 9 to 10 on each node and then bring them back up? Is this practical? Does Oracle allow different versions of OS running on different nodes?
c) Use Dataguard with 2 different RAC environments (2 nodes each). How would this work? Is it the only possible way? Any steps please?
Thanks

a) Do a rolling upgrade of Oracle from 10g to 11g. Then take down individual nodes and upgrade the Solaris OS from 9 to 10 and bring them up back into the cluster. Is there any known issues taking this path? Is a rolling upgrade like this possible?Hi,
first of all i would not change several components (OS, database version) at a time. My recommendation is to make small steps and start with the operating system first. Seconds recommendation is to test and test everything in your dev or test environment prior doing the upgrades in the productive environment. Trust me: You will face problems :-) So you better try it beforehand!
b) Do an upgrade of the Solaris OS from 9 to 10 on each node and then bring them back up? Is this practical? Does Oracle allow different versions of OS running on different nodes?As far i know you can run different operating system versions on different nodes if they are supported (Solaris 9 and 10 are).
Ronny Egner
My blog: http://ronnyegner.wordpress.com

Solaris 8 x86 system refuses to upgrade to Solaris 9

Similar Messages

Maybe you are looking for