SunFire V120 with A1000

OK, we've got a SunFire V120 server with an X6541A PCI SCSI card installed. The card is connected to an A1000 RAID Array with a good quality HVD SCSI cable. The other port on the A1000 has a HVD terminator installed. There are eight 73GB drives in the array, and there are two internal drives running on the server's built-in SCSI. Running Solaris 8 on the server.
So far, I have not been able to get the server to recognize the array at all. If I run a "probe-scsi-all" I get this:

ok probe-scsi-all
/pci@1f,0/pci@1/scsi@5,1
/pci@1f,0/pci@1/scsi@5
Fatal SCSI error at script address 10 Unexpected disconnect
/pci@1f,0/pci@1/scsi@8,1
/pci@1f,0/pci@1/scsi@8
Target 0
Unit 0 Disk FUJITSU MAP3367N SUN36G 0301
Target 1
Unit 0 Disk SEAGATE ST336704LSUN36G 0326
As you can see, it recognizes the internal drives on SCSI address 8 and the X6541 card at SCSI address 5, but reports an error on the port attached to the A1000.
I also get the following email to root occasionally:
To: root
Subject: raid Event
Content-Length: 183
An array event has been detected on Controller Unknown
Device Unknown at Host <<our domain name here>> - Time 08/23/2005 21:14:27
And I get errors on boot up:
Sun Fire V120 (UltraSPARC-IIe 648MHz), No Keyboard
OpenBoot 4.0, 1536 MB memory installed, Serial #53835884.
Ethernet address 0:3:ba:35:78:6c, Host ID: 8335786c.
last command: boot
Boot device: disk File and args:
SunOS Release 5.8 Version Generic_108528-17 64-bit
Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
WARNING: /pci@1f,0/pci@1/scsi@5 (glm2):
unexpected SCSI interrupt while idle
configuring IPv4 interfaces: eri0.
Hostname: <<our domain name here>>
The system is coming up. Please wait.
checking ufs filesystems
/dev/rdsk/c0t1d0s6: is stable.
/dev/rdsk/c0t0d0s7: 52762 files, 11375733 used, 10986210 free
/dev/rdsk/c0t0d0s7: (39522 frags, 1368336 blocks, 0.1% fragmentation)
/dev/rdsk/c0t0d0s4: is stable.
8/24/2005 1:14:21 GMT LOM time reference
starting rpc services: rpcbind done.
Setting netmask of eri0 to 255.255.255.240
Setting default IPv4 interface for multicast: add net 224.0/4: gateway <<our domain name here>>
syslog service starting.
Print services started.
There are no devices (controllers) in the system; nvutil terminated.
There are no devices (controllers) in the system.
fwutil failed!
Array Monitor initiated
Aug 23 21:14:27 /usr/lib/osa/bin/arraymon: No RAID devices found to check.
RDAC daemons initiated
volume management starting.
Wnn6: Key License Server started....
Nihongo Multi Client Server (Wnn6 R2.34)
Finished Reading Files
httpd starting.
Starting nrpe: Starting mysqld daemon with databases from /usr/local/mysql/data started
The system is ready.
The first SCSI error you see in the boot sequence:
WARNING: /pci@1f,0/pci@1/scsi@5 (glm2):
unexpected SCSI interrupt while idle
is sometimes replaced with:
WARNING: invalid vector intr: number 0x7df, pil 0x0
Any ideas at all? Is it the A1000, it's RAID controller, the X6541A, PROM settings? Anything???
Thanks!
- Matt

If it doesn't pass at this level you have zero chance in Solaris.
You're probably right.
I have tried swapping the ports on both the A1000 and the SCSI card. But I can't recall the exact effects -- problem is, I am in New Hampshire and the Server is in New York. "Hands-on" debugging is a bit difficult.
I do have auto-boot set to false, so no problem running the SCSI probe. I will probably have to do one more trip down there it looks like. Your suggestion of trying the SCSI probe with the A1000 disconnected is a good one - at least that will isolate to the A1000 or the SCSI card.
I have a hunch there is a hardware problem on the RAID contoller card in the A1000, but no proof yet.
Installed 300 or so patches last night. 50 or so to go. This part needs to get done anyway, even if it doesn't fix the RAID array!

Similar Messages

Solaris 10 on 280R with A1000

We have loaded solaris 10 ( 3/05) on our server i.e. Sunfire 280R with A1000 storage connected to it thru SCSI cable. We have addon SCSI card installed in server. Our A1000 is having only one controller.
Afterthat we have loaded sun storage RAID Manager 6.22 software to configure A1000 , we have made slices using RAID 5 & using RM6 utility. While rebooting the server we are getting following two errors & keeps scrolling on screen for about 10 minutes , though we are able to access A1000;
1. Warning : mod_load : cannot load module 'rdriver'
2. /kernel/drv/spark9/rdriver:undefined symbol 'dev_get_dev_info'
Is any solution to above errors? Is any patch / upgrade / firmware etc for above errors ?
Will it recommended to upgrade to solaris 10 or continue with solaris 9. we are using this as a database server with oracle 10G.

FYI, I think Sun discontinued support for the A1000 h/w in Solaris 10... should be documented.
I only mention this in case you want to have Sun support help you... if it works fine, I generally wouldn't worry. But it is a production system, I might have second thoughts about using Solaris 10 with unsupported h/w.
My $.02, YMMV.
David Strom

Installing Solaris 10 on Sunfire V120 via network boot from Linux

I have been given a free SunFire V120 server loaded with and old copy of Solaris 9. The problem is that this server no longer has the internal DVD/CDRom drive any more. Google'd for finding a replacement CD-Rom drive show cost more than the SunFire V120 unit itself.
The plan: Install Solaris 10 for SPARC on Sunfire V120 Server
Available:
-- Sun Microsystems SunFire V120 Server (1GB of Ram and 2x 36GB 10K RPM SCSI3 drives)
-- CentOS 5.1 Linux Server
-- Solaris 10 SPARC DVD ISO Image
-- DB25 to RJ45 Serial Cable accessing V120 LOM via Minicom application on CentOS 5 server
Via the http://www.docbert.org/Solaris/Jumpstart/linux.html site, I have configured the following:
* NFS Server (nfs-utils under RedHat)
* bootparams server (bootparamd under RedHat)
* rarpd server (rarpd under RedHat)
* tftp server (tftp-server)
CentOS Server Settings:
[root@jsserv ~]# cat /etc/ethers
0:3:ba:36:34:48 jsclient
[root@jsserv ~]# cat /etc/bootparams
jsclient root=jsserv:/jumpstart/sol10/Solaris_10/Tools/Boot install=jsserv:/jumpstart/sol10 boottype=:in
[root@jsserv ~]# cat /etc/exports
/jumpstart *(ro,no_root_squash)
[root@jsserv ~]# cat /etc/hosts
192.168.0.20 jsserv
192.168.0.22 jsclient
[root@jsserv ~]# ls -l /tftpboot
lrwxrwxrwx 1 root root 20 Mar 7 13:35 C0A80016 -> inetboot.sol10.sun4u
lrwxrwxrwx 1 root root 20 Mar 7 13:35 C0A80016.SUN4U -> inetboot.sol10.sun4u
-rw-r--r-- 1 root root 217016 Mar 7 13:34 inetboot.sol10.sun4u
On CentOS Linux server -- under /var/log/messages, the rarpd shows this message:
Mar 7 14:24:41 jsserv rarpd[3516]: RARP request from 0 on eth0
Mar 7 14:24:41 jsserv rarpd[3516]: RARP response to 0 192.168.0.22 on eth0
On the SunFire V120 server, the console displays:
Sun Fire V120 (UltraSPARC-IIe 648MHz), No Keyboard
OpenBoot 4.0, 1024 MB memory installed, Serial #53883976.
Ethernet address 0:3:ba:36:34:48, Host ID: 83363448.
Executing last command: boot net -v - install
Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: -v - install
38e00 Using RARP/BOOTPARAMS...
Internet address is: 192.168.0.22
hostname: jsclient
domainname: (none)
Found 192.168.0.20 @ 0:13:d3:9a:9e:98
root server: jsserv (192.168.0.20)
root directory: /jumpstart/sol10/Solaris_10/Tools/Boot
boot: cannot open kernel/sparcv9/unix
Enter filename [kernel/sparcv9/unix]: /platform/sun4u/kernel/sparcv9/unix
boot: failed to allocate 8192 bytes from scratch memory
panic - boot: boot: scratch memory overflow.
Program terminated
So now what do I do?
-- Michael

Anyone know where I can get the firmware (OBP) update / upgrade version 4.22 for the SunFire V120 server?
There is an old thread (http://forum.java.sun.com/thread.jspa?threadID=5137796) that talks of having to update your firmware 4.22.x, but I have looked through the SunSolve site and I cannot find a reference to this firmware any place for the SunFire V120 servers.

Reinstalling Solaris 10 on SunFire V120

Hi,
I would like to get some step-by-step instruction on how to reinstall the Solaris 10 into a SunFire V120.
The situation is like this..
1. We have a ununse Sunfire V120. It was able to boot up from the HDD till the console prompt.
2. But no one know the username/password. And from the bootup message, it is running "SunOS Release 5.8 Version Generic_108528-18 64-bit".
3. I've tried going into "LOM>" prompt and do a "bootmod forth". After resetting it I was able to go into "OK" prompt.
4. When I do a "boot cdrom" it give this error message "Fast Data Access MMU Miss".
What error is this? The that I put in is the burn image of Disc1 of the Solaris 10 download from SUN.
I can use this Disc1 to reinstall my SunBlade 150.
Is there anything that I miss out for the V120 reinstallation??
Thanks a million in advance.

The error you observed was simply because you had halted the system
in a brute force fashion. There was still data cached in place.
"Fast data MMU Miss" is a classic console output
for "Ouch! That hurt! You hit the brakes too quickly!"
Get it to OBP once again.
Set your auto-boot variable to 'false' and reset the chassis.
It will go through a power cycle reset and automatically stop at the OK prompt.
Every data bus will be empty and you won't see that error
when you try to boot from the optical drive.
There are additional web resources for that system ...
The Sunfire V120 has a resource page in the Sun System Handbook
http://sunsolve.sun.com/handbook_pub/Systems/SunFireV120/SunFireV120.html
which included links to all its documentation.
If you need a bit of help with OBP commands,
then find the OBP4.x Command Reference Manual at Docs.Sun.Com
http://docs.sun.com/app/docs?q=816-1177
========
Then again, you could just Google for keywords "solaris root password"
and find guidance on clearing the current password to a null value.
Then you will be able to reboot the system to its current Solaris 8 environment.
( ... a woefully underpatched Solaris 8 environment, but it would still boot.)

Need help about boot SUNFIRE V120

Hi all....
I need help about how to change boot from boot net to boot disk....
after i installed sun solaris 10 at my sunfire v120, then reboot the machine ... this sunfire still boot from net not from disk...
can i change it?
please i really need help ....
thanks

If its booted, try "eeprom boot-device=disk"
If your at the OBP, "setenv boot-device disk".
If that doesnt work check the value of "diag-switch?".
It could be booting off the the diag-device instead

Help please. How do I set up a dray tek v120 with apple TC?

Could someone please help me, as this is driving me mad.
I have purchased a Dray Tek vigor v120 modem, and want to set it up to use with my TC (version 7 2TB) I have been using a BT home hub3 with the TC, and works fine, minimal setup. Now I want to use the Dray Tek in place of the HH3, so I can use my TC as my main router. Now problem I'm having is with the v6 airport utility. Following the steps from the Dray Tek website, it uses the V5 Airport utility to walk you through, but I cannot do any of this with the v6?
How do I reset the TC, how do I manually. Setup in this wretched v6 airport utility.?
The old version is straight forward, but in v6 I cannot find any way of doing this.
Can anybody help?
Here's the link to setting this up with the old, easier version of airport
http://www.draytek.co.uk/archive/kb/kb_vigor120_AirportExtreme_setup.html
Best regards
Paddy.
Ps I'm in the UK.

The only thing you have to do with the TC is setup PPPoE client. That is no problem. It may work automagically via the wizard but if not it is easy to fix up.
Do the first step from draytek instructions..
Set up the Vigor 120 modem so that it is turned on and plugged into the ADSL line, do not plug it into a PC or router yet.Wait until the DSL light stops flashing and goes solid, that indicates that it is ready to pass through the ADSL connection to your router. The modem is pre-configured for standard UK ADSL connections so will not need any further setup for an ADSL connection with the settings listed above.
Now plug the WAN of the TC into the 120.
In the airport utility click on the "Other wifi devices" in the top left corner.. it should have a (1) on the end to indicate a new device needs to be configured. If not reset the TC and start afresh.
Run through the setup wizard. I always recommend people change the apple names proposed for names that are short, no spaces and pure alphanumeric but up to you.
The wizard might well detect you are on adsl and will bring up the pppoe screen and you type in your username and password exactly as you would in the draytek instructions.
Finish the wizard without other changes.
Did it detect pppoe?? If not you can now edit it.
Click on the TC in the airport utility. Then click on the edit.. this is same as the manual setup in v5 utility.
Go to the Internet tab and click on the connect using there.
Select pppoe.
That will open a bunch of different options where you can type in username and password as supplied by your ISP.
If you run into issues.. please do screenshots of where you have problems.
Edit.. I always should add at the top but end up thinking of last.
Apple do not automatically setup the wireless in the computer correctly. Generally ipv6 will default to auto. For Time Capsule or any airport setup this might be ok.. but it is better to ensure it is correctly set to link-local.
Open your network preferences and fix the ipv6. It should look like this.

Installing Solaris 11 on SunFIre T1000 With Automated Installer Server Fail

h4. Hi
h4. A few days i am try to intall solaris 11 11/11 on our server Sunfire T1000
h4. we first upgrade the firmware of the server to
sc> showhost
Sun-Fire-T1000 System Firmware 6.7.12 2011/07/06 20:03
Host flash versions:
OBP 4.30.4.d 2011/07/06 14:27
Hypervisor 1.7.3.c 2010/07/09 15:14
POST 4.30.4.b 2010/07/09 14:25
h4. And after we install Solaris 11 x86 on a laptop, in that we configure an AIS (Automated installer Server)
installadm list
Service Name Alias Of Status Arch Image Path
default-sparc s11-sparc on Sparc /install/images/s11-sparc
s11-sparc - on Sparc /install/images/s11-sparc
h4. We are using the default installations with a DHCP server in the Laptop
installadm list -m -p
Service Name Manifest Status
default-sparc orig_default Default
s11-sparc orig_default Default
h4. By the other side, in the sparc server (T1000) we use OBP for a WAN Boot Installation
boot net:dhcp - installl
2012-08-08 20:33:44,911 InstallationLogger DEBUG Starting Automated Installation
2012-08-08 20:33:44,913 InstallationLogger INFO Using XML Manifest: /system/volatile/ai.xml
2012-08-08 20:33:44,965 InstallationLogger INFO Using profile specification: /system/volatile/profile
2012-08-08 20:33:45,018 InstallationLogger INFO Using service list file: /var/run/service_list
2012-08-08 20:33:45,070 InstallationLogger INFO Starting installation.
2012-08-08 20:33:45,122 InstallationLogger DEBUG Registering Manifest Parser Checkpoint
2012-08-08 20:33:45,124 InstallationLogger DEBUG Engine registering:
2012-08-08 20:33:45,126 InstallationLogger DEBUG name: manifest-parser
2012-08-08 20:33:45,128 InstallationLogger DEBUG module_path: solaris_install.manifest.parser
2012-08-08 20:33:45,129 InstallationLogger DEBUG checkpoint_class_name: ManifestParser
2012-08-08 20:33:45,131 InstallationLogger DEBUG args: None
2012-08-08 20:33:45,133 InstallationLogger DEBUG kwargs: {'call_xinclude': True, 'manifest': '/system/volatile/ai.xml', 'validate_from_docinfo': True}
2012-08-08 20:33:45,135 InstallationLogger DEBUG insert_before: None
2012-08-08 20:33:45,136 InstallationLogger DEBUG log_level: None
2012-08-08 20:33:45,138 InstallationLogger DEBUG =============================
2012-08-08 20:33:45,142 InstallationLogger DEBUG Current checkpoint list:
2012-08-08 20:33:45,144 InstallationLogger DEBUG manifest-parser
2012-08-08 20:33:45,146 InstallationLogger DEBUG Executing Manifest Parser Checkpoint
2012-08-08 20:33:45,148 InstallationLogger DEBUG Retrieving checkpoint list from manifest-parser to None+
2012-08-08 20:33:45,150 InstallationLogger DEBUG Executing Engine Checkpoints...+
2012-08-08 20:33:45,152 InstallationLogger DEBUG Retrieving checkpoint list from manifest-parser to None+
2012-08-08 20:33:45,154 InstallationLogger DEBUG Engine will be executing following checkpoints:+
2012-08-08 20:33:45,155 InstallationLogger DEBUG manifest-parser
2012-08-08 20:33:45,157 InstallationLogger DEBUG Spawning InstallEngine execution thread
2012-08-08 20:33:45,160 InstallationLogger DEBUG Loading manifest-parser checkpoint
2012-08-08 20:33:45,213 InstallationLogger.manifest-parser DEBUG Initializing ManifestParser (manifest=/system/volatile/ai.xml, Validate_from_docinfo=True, dtd_file=None, load_defaults=True, call_xinclude=True)
2012-08-08 20:33:45,273 InstallationLogger DEBUG manifest-parser: prog est-1, prog ratio-0.95, total_ratio-1.00
2012-08-08 20:33:45,275 InstallationLogger DEBUG Last checkpoint, manifest-parser: prog ratio 0.95
2012-08-08 20:33:45,279 InstallationLogger DEBUG Snapshotting DOC to /var/run/install_engine/engine.MYk67H/.data_cache.manifest-parser
2012-08-08 20:33:45,286 InstallationLogger DEBUG Executing manifest-parser checkpoint
2012-08-08 20:33:45,288 InstallationLogger.manifest-parser DEBUG ManifestParser.execute(dry_run=False) called
2012-08-08 20:33:45,290 InstallationLogger.manifest-parser DEBUG ManifestParser.parse(doc=-> [DataObjectCache] (<solaris_install.data_object.cache.DataObjectCache object at 0xee1b90>)
 -> [persistent] (DataObjectCacheChild: persistent)
 -> [auto-install] (<solaris_install.ApplicationData object at 0xee1030>)
 -> [volatile] (DataObjectCacheChild: volatile)
 -> [apply_sysconfig_dict] (<solaris_install.data_object.data_dict.DataObjectDict object at 0xee1050>)) called
2012-08-08 20:33:45,292 InstallationLogger.manifest-parser DEBUG loading manifest (dtd_validation=True)
2012-08-08 20:33:45,872 InstallationLogger.manifest-parser DEBUG Parsed XML document:
<!DOCTYPE auto_install SYSTEM "file:///usr/share/install/ai.dtd.1">
<auto_install>
<ai_instance name="orig_default" auto_reboot="false">
<target>
<logical noswap="false" nodump="false">
<zpool name="rpool" is_root="true" action="create">
<filesystem name="export" mountpoint="/export" action="create" in_be="false"/>
<filesystem name="export/home" action="create" in_be="false"/>
<be name="solaris"/>
</zpool>
</logical>
</target>
<software type="IPS">
<destination>
<image action="create" index="false">

<facet set="false">facet.locale.*</facet>
<facet set="true">facet.locale.en</facet>
<facet set="true">facet.locale.en_US</facet>
<facet set="true">facet.locale.es</facet>
<facet set="true">facet.locale.es_ES</facet>
</image>
</destination>
<source>
<publisher name="solaris">
<origin name="http://pkg.oracle.com/solaris/release"/>
</publisher>
</source>
h4. When the installation precess is in this part
13% target-selection completed.
17% ai-configuration completed.
19% target-instantiation completed.
19% Beginning IPS transfer
Creating IPS image
Installing packages from:
solaris
origin: http://pkg.example.com/solaris/
h4. in the install_log file show us this errors:
2012-08-08 20:51:39,653 InstallationLogger.generated-transfer-1184-1 DEBUG Download: text/doctools ...
2012-08-08 20:51:43,156 InstallationLogger.generated-transfer-1184-1 DEBUG Download: system/core-os ...
2012-08-08 20:52:03,704 InstallationLogger.generated-transfer-1184-1 DEBUG Download: text/less ...
2012-08-08 20:52:03,788 InstallationLogger.generated-transfer-1184-1 DEBUG Download: system/management/rad/module/rad-smf ...
2012-08-08 20:52:03,835 InstallationLogger.generated-transfer-1184-1 DEBUG Download: system/library ...
2012-08-08 20:52:30,609 InstallationLogger.generated-transfer-1184-1 DEBUG Cleaning up
2012-08-08 20:52:30,611 InstallationLogger ERROR Error occurred during execution of 'generated-transfer-1184-1' checkpoint.
Traceback (most recent call last):
File "/usr/lib/python2.6/vendor-packages/solaris_install/engine/__init__.py", line 811, in executecheckpoints
checkpoint.execute(dry_run)
File "/usr/lib/python2.6/vendor-packages/solaris_install/transfer/ips.py", line 359, in execute
self._transfer()
File "/usr/lib/python2.6/vendor-packages/solaris_install/transfer/ips.py", line 639, in _transfer
self.api_inst.prepare()
File "/usr/lib/python2.6/vendor-packages/pkg/client/api.py", line 2021, in prepare
self._img.imageplan.preexecute()
File "/usr/lib/python2.6/vendor-packages/pkg/client/imageplan.py", line 2827, in preexecute
p.download()
File "/usr/lib/python2.6/vendor-packages/pkg/client/pkgplan.py", line 406, in download
mfile.wait_files()
File "/usr/lib/python2.6/vendor-packages/pkg/client/transport/transport.py", line 2857, in wait_files
self._transport._get_files(self)
File "/usr/lib/python2.6/vendor-packages/pkg/client/transport/transport.py", line 432, in wrapper
return f(instance, fargs, *f_kwargs)
File "/usr/lib/python2.6/vendor-packages/pkg/client/transport/transport.py", line 1736, in getfiles
self._get_files_list(mfile, filelist)
File "/usr/lib/python2.6/vendor-packages/pkg/client/transport/transport.py", line 1685, in getfiles_list
raise tfailurex
TransportFailures: 1: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 7558caebcb4a599c08c6a1b1591672f2b3b3cb06.
2: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: c8edd4ff7e100c83ad74ba75a9baeda47348800c.
3: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 91350cb5e1dc88dbbcf2e94e0a05b075f03ba35b.
4: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 85bec186fd71c8a072cb3261aac5a2d26e0bed01.
5: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: feaf36a0752e78974e4cdbd757a2af9dd5f94236.
6: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 93adf874561a2c2e383fa55da1f23cc93f1b24b5.
7: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 5c261f9705a8c604bf3f473f1d76c7f646cedc60.
8: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 81fa4733fa459a553001f8fdf30f49e35067a5ea.
2012-08-08 20:52:30,731 InstallationLogger DEBUG Checkpoints Completed: DOC:+
-> [DataObjectCache] (<solaris_install.data_object.cache.DataObjectCache object at 0xee1b90>)+
 -> [persistent] (DataObjectCacheChild: persistent)+
 -> [auto-install] (<solaris_install.ApplicationData object at 0xee1030>)+
 -> [Engine-DOC-Root-Node] (<solaris_install.engine.EngineData object at 0xecc930>)+
 -> [manifest-parser] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee10d0>)+
 -> [target-discovery] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee1230>)+
 -> [target-selection] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee12f0>)+
 -> [ai-configuration] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee1410>)+
 -> [var-shared-dataset] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee1c30>)+
 -> [target-instantiation] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee1750>)+
 -> [discovered] (<solaris_install.target.Target object at 0xee1330>)+
 -> [disk] (Disk: ctd=c2t0d0; volid=None; devpath=/pci@7c0/pci@0/pci@8/scsi@2/sd@0,0; devid=id1,sd@n5000cca334c724bf; prop:dev_type=scsi; prop:dev_vendor=HITACHI; prop:dev_size=148.99gb; keyword: key=boot_disk; is_cdrom=False; label=VTOC; whole_disk=False; write_cache=False)+
 -> [0] (Slice: name=0; action=preserve, force=False, is_swap=False, tag=2, flag=0, in_use={'used_by': ['exported_zpool'], 'used_name': ['rpool']}; size=148.99gb; start_sector=4768)+
 -> [2] (Slice: name=2; action=preserve, force=False, is_swap=False, tag=5, flag=1; size=148.99gb; start_sector=0)+
 -> [logical] (Logical: noswap=True; nodump=True)+
 -> [desired] (<solaris_install.target.Target object at 0xede3f0>)+
 -> [logical] (Logical: noswap=False; nodump=False)+
 -> [rpool] (Zpool: name=rpool; action=create; is_root=True; vdev_list=['c2t0d0s0'])+
 -> [export] (Filesystem: name=export; action=create; mountpoint=/export)+
 -> [export/home] (Filesystem: name=export/home; action=create)+
 -> [solaris] (BE: name=solaris; mountpoint=/a)+
 -> [vdev] (Vdev: name=vdev; redundancy=none)+
 -> [swap] (Zvol: name=swap; action=create; use=swap; size=1024m)+
 -> [dump] (Zvol: name=dump; action=create; use=dump; size=512m)+
 -> [var] (Filesystem: name=var; action=create; mountpoint=/var)+
 -> [disk] (Disk: ctd=c2t0d0; volid=None; devpath=/pci@7c0/pci@0/pci@8/scsi@2/sd@0,0; devid=id1,sd@n5000cca334c724bf; prop:dev_type=scsi; prop:dev_vendor=HITACHI; prop:dev_size=148.99gb; keyword: key=boot_disk; is_cdrom=False; label=VTOC; whole_disk=False; write_cache=True)+
 -> [0] (Slice: name=0; action=create, force=True, is_swap=False, tag=2, flag=0; in_zpool=rpool; in_vdev=vdev; size=148.99gb; start_sector=4768)+
 -> [volatile] (DataObjectCacheChild: volatile)+
 -> [apply_sysconfig_dict] (<solaris_install.data_object.data_dict.DataObjectDict object at 0xee1050>)+
 -> [orig_default] (ai_instance: name='orig_default' auto_reboot=False; http_proxy='None')+
 -> [target] (<solaris_install.target.Target object at 0xee1d30>)+
 -> [logical] (Logical: noswap=False; nodump=False)+
 -> [rpool] (Zpool: name=rpool; action=create; is_root=True; vdev_list=[None])+
 -> [export] (Filesystem: name=export; action=create; mountpoint=/export)+
 -> [export/home] (Filesystem: name=export/home; action=create)+
 -> [solaris] (BE: name=solaris)+
 -> [generated-transfer-1184-1] (<solaris_install.transfer.info.Software object at 0xee1f30>)+
 -> [transfer] (<solaris_install.transfer.info.IPSSpec object at 0xecc050>)+
 -> [destination] (<solaris_install.transfer.info.Destination object at 0xecc0b0>)+
 -> [image] (<solaris_install.transfer.info.Image object at 0xecc130>)+
 -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc150>)+
 -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc1b0>)+
 -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc210>)+
 -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc270>)+
 -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc2d0>)+
 -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc330>)+
 -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc390>)+
 -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc3f0>)+
 -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc450>)+
 -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc4b0>)+
 -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc510>)+
 -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc570>)+
 -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc5d0>)+
 -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc630>)+
 -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc690>)+
 -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc6f0>)+
 -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc750>)+
 -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc7b0>)+
 -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc810>)+
 -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc870>)+
 -> [img_type] (<solaris_install.transfer.info.ImType object at 0xee1b70>)+
 -> [source] (<solaris_install.transfer.info.Source object at 0xecc8b0>)+
 -> [publisher] (<solaris_install.transfer.info.Publisher object at 0xecc8f0>)+
 -> [origin] (<solaris_install.transfer.info.Origin object at 0xecc910>)+
 -> [transfer-zpool-cache] (<solaris_install.data_object.data_dict.DataObjectDict object at 0xee18f0>)+
 -> [transfer-ai-files] (<solaris_install.data_object.data_dict.DataObjectDict object at 0xee15b0>)+
2012-08-08 20:52:30,747 InstallationLogger DEBUG Checkpoints Completed: DOC (xml_format):
<root>
<target name="discovered">
<disk whole_disk="false">
<disk_name name="c2t0d0" name_type="ctd"/>
<disk_prop dev_type="scsi" dev_vendor="HITACHI" dev_size="312461344secs"/>
<disk_keyword key="boot_disk"/>
<slice name="0" action="preserve" force="false" is_swap="false">
<size val="312456576secs" start_sector="4768"/>
</slice>
<slice name="2" action="preserve" force="false" is_swap="false">
<size val="312461344secs" start_sector="0"/>
</slice>
</disk>
<logical noswap="true" nodump="true"/>+
</target>+
<target name="desired">+
<logical noswap="false" nodump="false">+
<zpool name="rpool" action="create" is_root="true">+
<filesystem name="export" action="create" mountpoint="/export" in_be="false"/>+
<filesystem name="export/home" action="create" in_be="false"/>+
<be name="solaris"/>+
<vdev name="vdev" redundancy="none"/>+
<zvol name="swap" action="create" use="swap">+
<size val="1024m"/>+
</zvol>+
<zvol name="dump" action="create" use="dump">+
<size val="512m"/>+
</zvol>+
<filesystem name="var" action="create" mountpoint="/var" in_be="true"/>+
</zpool>+
</logical>+
<disk whole_disk="false">+
<disk_name name="c2t0d0" name_type="ctd"/>+
<disk_prop dev_type="scsi" dev_vendor="HITACHI" dev_size="312461344secs"/>+
<disk_keyword key="boot_disk"/>+
<slice name="0" action="create" force="true" is_swap="false" in_zpool="rpool" in_vdev="vdev">+
<size val="312456576secs" start_sector="4768"/>+
</slice>+
</disk>+
</target>+
<ai_instance auto_reboot="false" name="orig_default">+
<target>+
<logical noswap="false" nodump="false">+
<zpool name="rpool" action="create" is_root="true">+
<filesystem name="export" action="create" mountpoint="/export" in_be="false"/>+
<filesystem name="export/home" action="create" in_be="false"/>+
<be name="solaris"/>+
</zpool>+
</logical>+
</target>+
<software name="generated-transfer-1184-1" type="IPS">+
<software_data>+
<name>pkg:/entire@latest</name>+
<name>pkg:/group/system/solaris-large-server</name>+
</software_data>
<destination>
<image img_root="/a" action="create" index="False">
<facet set="false">facet.locale.*</facet>
<facet set="true">facet.locale.en</facet>
<facet set="true">facet.locale.en_US</facet>
<facet set="true">facet.locale.es</facet>
<facet set="true">facet.locale.es_ES</facet>
</image>
</destination>
<source>
<publisher name="solaris">
<origin name="http://pkg.oracle.com/solaris/release"/>
</publisher>
</source>
</software>
</ai_instance>
</root>
2012-08-08 20:52:30,749 InstallationLogger CRITICAL Failed Checkpoints:
2012-08-08 20:52:30,803 InstallationLogger ERROR
2012-08-08 20:52:30,855 InstallationLogger ERROR generated-transfer-1184-1
2012-08-08 20:52:30,907 InstallationLogger ERROR
2012-08-08 20:52:30,960 InstallationLogger ERROR Checkpoint execution error:
2012-08-08 20:52:31,012 InstallationLogger ERROR
2012-08-08 20:52:31,064 InstallationLogger ERROR 1: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 7558caebcb4a599c08c6a1b1591672f2b3b3cb06.
2012-08-08 20:52:31,117 InstallationLogger ERROR 2: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: c8edd4ff7e100c83ad74ba75a9baeda47348800c.
2012-08-08 20:52:31,169 InstallationLogger ERROR 3: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 91350cb5e1dc88dbbcf2e94e0a05b075f03ba35b.
2012-08-08 20:52:31,222 InstallationLogger ERROR 4: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 85bec186fd71c8a072cb3261aac5a2d26e0bed01.
2012-08-08 20:52:31,274 InstallationLogger ERROR 5: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: feaf36a0752e78974e4cdbd757a2af9dd5f94236.
2012-08-08 20:52:31,326 InstallationLogger ERROR 6: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 93adf874561a2c2e383fa55da1f23cc93f1b24b5.
2012-08-08 20:52:31,379 InstallationLogger ERROR 7: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 5c261f9705a8c604bf3f473f1d76c7f646cedc60.
2012-08-08 20:52:31,431 InstallationLogger ERROR 8: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 81fa4733fa459a553001f8fdf30f49e35067a5ea.
2012-08-08 20:52:31,484 InstallationLogger ERROR
2012-08-08 20:52:31,536 InstallationLogger INFO Automated Installation Failed. See install log at /system/volatile/install_log
2012-08-08 20:52:31,588 InstallationLogger DEBUG Shutting down Progress Handler
h4. Is something about:
2012-08-08 20:52:30,611 InstallationLogger ERROR Error occurred during execution of 'generated-transfer-1184-1' checkpoint.
Traceback (most recent call last):
File "/usr/lib/python2.6/vendor-packages/solaris_install/engine/__init__.py", line 811, in executecheckpoints
checkpoint.execute(dry_run)
2012-08-08 20:52:30,749 InstallationLogger CRITICAL Failed Checkpoints:
2012-08-08 20:52:30,803 InstallationLogger ERROR
2012-08-08 20:52:30,855 InstallationLogger ERROR generated-transfer-1184-1
2012-08-08 20:52:30,907 InstallationLogger ERROR
2012-08-08 20:52:30,960 InstallationLogger ERROR Checkpoint execution error:
h4. Somebody knows about this error?

The chash failures indicate that either the repository you're using has corrupt content for those files, or the files are being corrupted on download. The latter is more likely, usually a result of badly-behaved http proxies.

Enterprise 420R with A1000 problem

Dear all
I'm getting the following error and i am able to "see" the system only from console.
Sep 29 12:54:28 cohealths1 unix: WARNING: vxvm:vxio: Subdisk rootdisk-03 block 110672: Uncorrectable write error
Sep 29 12:54:28 cohealths1 unix: WARNING: vxvm:vxio: Subdisk rootdisk-02 block 1039519: Uncorrectable write error
I went to "ok" prompt and i gave the "boot" command, but i got the following errors
{2} ok boot
Resetting ...
screen not found.
Can't open input device.
Keyboard not present. Using ttya for input and output.
Sun Enterprise 420R (2 X UltraSPARC-II 450MHz), No Keyboard
OpenBoot 3.23, 4096 MB memory installed, Serial #15281095.
Ethernet address 8:0:20:e9:2b:c7, Host ID: 80e92bc7.
Rebooting with command: boot
Boot device: net File and args:
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
{1} ok boot disk0
Boot device: /pci@1f,4000/scsi@3/disk@0,0 File and args:
Can't open boot device
{1} ok boot disk1
Boot device: /pci@1f,4000/scsi@3/disk@1,0 File and args:
Can't open boot device
It seems that the problem is on the two internal disks (the leds are green!!) .....
Can anybody help me ?

Hello,
probe the disks from the ok-prompt (either after reset or power-up)
setenv auto-boot? false
reset
probe-scsi
(if you use probe-scsi-all the external disks and the A1000 will be probed as well, which doesn't make sense at the moment).
If the internal disk are visible, boot into single-user mode from CD-ROM (Software 1 of Solaris 8/9, CD1 of Solaris 10) and invoke format to check the disks (-> analyze, non-destructive test).
boot cdrom -sv
Otherwise try if reseating the disks solves the problem.
Is the (internal) SCSI controller visible with show-devs ?
Running diagnostics might be a good idea.
setenv diag-switch? true
reset-all
Michael

SunFire V120/SUNWatm

I have two Sun Fire V120's. They are used by NET as management platforms for their Scream 100 ATM switches. They happen to be the worst switches known to man and only their very expensive tech support can surpass how horrible these devices are. Both are running Solaris 8. I cannot upgrade because of their relationship to the Screams. The Sun communicates with the Scream via an ATM card. One of my Sun servers works fine and seems to have an older version of this card. It is a Magneto card with the assembly # 5013028-02. My other Sun is running the same OS with the same configuration but seems to have a new version of the card. It cannot access the card. I get a driver error for SUNWatm. I attempted to reload this package off of the Sun CD's I have to no avail. Is it possible that this card needs a different driver package? Thanks for the help.

Benjamin,
That V120 platform has only one PCI slot, so positioning cannot influence functionality.
Is each card seen at the OBP level? A "dead" card cannot use driver packages.
Are you using the same identical patch level of Solaris 8, and of the ATM software, in both systems?
Does functionalty (... or non-functionality) follow the cards, if you swap them between the two systems?
Perhaps you might install and run Sun's Explorer data gathering tool to both boxes.
Run it and open a support case with Sun. They'll guide you how to FTP the output file to them.
Let the Network Technical Support team analyze whatever Explorer gathers.
see Public Infodoc 82329, for Explorer:
http://sunsolve.sun.com/search/document.do?assetkey=1-9-82329-1

ST2540 cannot be detected by Sunfire x4440 with windows 200

we installed windows 2008 on x4440 and attached ST2540 to it.x4440 server cannot detect the storage.how do we go about on these situation?
Edited by: sajulga on Aug 26, 2010 6:34 AM

The GeForce 8800 GS in an iMac is equivalent to a GeForce 8800M GTS in a PC.
Forceware driver 178.15 offers support for GeForce 8800M GTS:
http://laptopvideo2go.com/forum/index.php?showtopic=20927
Run that exe in Vista 64x, and then select the INF file from the Device Manager manual driver update instructions instead of picking from the list (which doesn't contain GeForce 8800 GS).
GF 8800 GS does NOT equal GF 8800 GT. Very different cards.
http://en.wikipedia.org/wiki/GeForce8_series#8800GS
See http://discussions.apple.com/thread.jspa?messageID=8281574#8281574 for more info.
I didn't figure out how to get this to work on 32-bit Vista.

Solaris 10 x86 in Sunfire V20Z

Hi All,
Just a quick question, Can i access the Solaris NOS directly on the IPMI (SP) port of the V20z? Coz currently, im accessing the Solaris Installed via Serial Redirection.
Im thinking that the Sunfire V120 is same when you access it via LOM. When you are in LOM? type console and you will go to # prompt in Solaris OS.
Thanks

i was facing the same problem just hours ago.
i successfully installed broadcom driver into solaris 10 with Dell GX280
i copy broadcom driver into a CD and run it on solaris pc.
i copied out the file into a directory and use pkgadd -d BRCMbcme.pkg and voila. My pc detected the network card.
Then start configuring your network.
It works for me. Hope it works for u.
remember to read the readme file which come with the broadcom driver.

Sun V120 Blade: can't boot from disk. Is there anyway to recover?

I have a SunFire V120 Blade with 2 hard drives (one contains application data), and NO CDROM drive. It appears that the rack took a power hit, and now I cannot boot the V120 server. A 'boot disk' command returns: Executing last command: boot disk
Boot device: /pci@1f,0/pci@1/scsi@8/disk@0,0 File and args:
Can't read disk label.
Can't open disk label package
Evaluating: boot disk
Can't open boot device
ok
Since I have no CDROM, how can I reset/recover, because I wouldn't know how I could reinstall Solaris?
Any ideas? Thanks in advance for the assistance.
Jim

You have 2 choices, replace 2nd disk with a CDROM drive or perform a network install from a JumpStart server on the same subnet.

Netra 120 - Will a SunFire 120 Power Supply Work?

Thanks in advance for any help with this question.
Will a SunFire v120 AC power supply fit/work in a Netra 120?
I dont have a DC power source for my Netra, and would like to replace the DC power supply with an AC one. Will one from a SunFire v120 work?
Alternately, anyone know a cheap DC Power source that would work to power the server?
-allan

In answer to my own question, yes. I put the AC power supply from a SunFire v120 into the Netra 120 and it works just fine. This is probably the only difference between the two servers.

JVM termination with standalone oc4j

Hi,
We have several (around 15) standalone oc4j instances running on a Sun machine, the details are as follows:
Machine: SunFire V1280 with 8 processors (sun4u sparc) and 24 GB RAM
OS: SunOS 5.9 Generic_117171-02
oc4j version: 9.0.4.0.0
There is also a 10g installation on this machine.
We are finding that quite regularly one or more of the oc4j instances shuts down without warning. the only information in the log files (jms.log, rmi.log etc) is a "Stopped (JVM termination)" message. I cannot find any other logs on the machine which can help me with this error.
I am after one of two things:
1. Potential reasons for this happening (preferably with solutions!)
2. A possible for a log file created by the JVM detailing why it is terminating.
Can anyone help?
Thanks

http://blogs.oracle.com/shay/2005/10/24#a55

Can we run two instances of solaris in 1 hardware (SunFire Server)

Hi,
There is a need for us to run two instance of Solaris in SunFire Server.
Because we need to install Domino Servers in a Single Hardware.
The hardware consist of Eight Processors.
How to allocate the resource in such a way that the Domino Server should take 4 Processor and other application should take other four.
Please be in more detail.
Regards,
C.Kumanan

"Sunfire" is a product line that includes many different computer designs
and many different capabilities. You will need to be more specific as to what model you actually have.
The Sun Fire Midrange Systems are hardware designs that can be configured
to run discrete domains in the same overall chassis.
So, for those systems the answer to your question would be "Yes".
For any Sun Fire computer syustem that is smaller than the Midrange systems,
the answer to your question would be "No".
So ... A Sun Fire 3800 with eight processors ??? "Yes"
However, a Sunfire V880 with eight processors ??? "No"
Any other configuration questions of the actual Solaris instance,
such as Zones or processor thread affinity are outside the scope of this forum.
Those issues would be discussed better in an OS forum.

SunFire V120 with A1000

Similar Messages

Maybe you are looking for