Hi All,

I had changed the /etc/system file . The file is listed below . ( The
last part is the part to the system file after the line "*----- Added
by Gaurav on 06th June 2006 for the installation of Control-SA agent of
Solaris
" which i had appended. )




*ident "@(#)system 1.18 97/06/27 SMI" /* SVR4 1.5 */
*
* SYSTEM SPECIFICATION FILE
*

* moddir:
*
* Set the search path for modules. This has a format similar to the
* csh path variable. If the module isn't found in the first directory
* it tries the second and so on. The default is /kernel /usr/kernel
*
* Example:
* moddir: /kernel /usr/kernel /other/modules



* root device and root filesystem configuration:
*
* The following may be used to override the defaults provided by
* the boot program:
*
* rootfs: Set the filesystem type of the root.
*
* rootdev: Set the root device. This should be a fully
* expanded physical pathname. The default is the
* physical pathname of the device where the boot
* program resides. The physical pathname is
* highly platform and configuration dependent.
*
* Example:
* rootfs:ufs
* rootdev:/sbus@1,f8000000/esp@0,800000/sd@3,0:a
*
* (Swap device configuration should be specified in /etc/vfstab.)



* exclude:
*
* Modules appearing in the moddir path which are NOT to be loaded,
* even if referenced. Note that `exclude' accepts either a module name,
* or a filename which includes the directory.
*
* Examples:
* exclude: win
* exclude: sys/shmsys



* forceload:
*
* Cause these modules to be loaded at boot time, (just before mounting
* the root filesystem) rather than at first reference. Note that
* forceload expects a filename which includes the directory. Also
* note that loading a module does not necessarily imply that it will
* be installed.
*
* Example:
* forceload: drv/foo



* set:
*
* Set an integer variable in the kernel or a module to a new value.
* This facility should be used with caution. See system(4).
*
* Examples:
*
* To set variables in 'unix':
*
* set nautopush=32
* set maxusers=40
*
* To set a variable named 'debug' in the module named 'test_module'
*
* set test_module:debug = 0x13

set shmsys:shminfo_shmseg=10
set shmsys:shminfo_shmmax=4294967295
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_semmns=1024
set shmsys:shminfo_semmni=100
set shmsys:shminfo_semmsl=260
set shmsys:shminfo_semopm=100
set shmsys:shminfo_semvmx=32767


*----- Added by Gaurav on 06th June 2006 for the installation of
Control-SA agent of Solaris
set msgsys:msginfo_msgmax=2048
set msgsys:msginfo_msgmnb=6144
set msgsys:msginfo_msgtql=50
set msgsys:msginfo_msgmni=5
set msgsys:msginfo_msgseg=12288
set msgsys:msginfo_msgssz=12288

forceload:sys/msgsys




Then after this I rebooted the machine , and then I ran "FSCK", as the
system wanted me to run it .

after completion of it, I again rebooted it , and since then the system
is in "OK" prompt.

when I try to type "boot -s " the system says " Timeout waiting for
ARP/RARP packet "

I have the backup of old system file as /etc/system.SAVE

Kindly help ,

Regards,

Gaurav

Gaurav wrote:

> Hi All,

[...]

> after completion of it, I again rebooted it , and since then the system
> is in "OK" prompt.
>
> when I try to type "boot -s " the system says " Timeout waiting for
> ARP/RARP packet "

Does it say anything else before that? What is "boot-device" set to
in the OBP?

The "ARP/RARP" message indicates that the system tries to boot over
the network.


/Roger

--
Roger Gustavsson
roger.gustavsson@teliasonera.com.INVALID

Hi Roger,

It also says

boot device /pci@1f,0/pci@1,1/network@c,1 file and args -a
using obboard transciever link up

and then the ARP thing.

the boot-device entry for me is "disk" . I have even tried to change
the entry to "net" and then tried it .

but still no help

regards,
gaurav

Hi ,

when i type in command :

"boot disk"



i get following error

cannot open : /etc/path_to_inst

Gaurav wrote:

> Hi Roger,
>
> It also says
>
> boot device /pci@1f,0/pci@1,1/network@c,1 file and args -a
> using obboard transciever link up
>
> and then the ARP thing.

I'm not sure, but I think the machine boots on diag-device if the
machine is in diag mode, i.e. the key is in the diag position or
"diag-switch?" is set to true. And in your case diag-device is
probably set to net.

> the boot-device entry for me is "disk" . I have even tried to change
> the entry to "net" and then tried it .


/Roger

--
Roger Gustavsson
roger.gustavsson@teliasonera.com.INVALID

Gaurav wrote:

> Hi ,
>
> when i type in command :
>
> "boot disk"
>
> i get following error
>
> cannot open : /etc/path_to_inst

I guess the machine at least booted on the disk this time.

Perhaps you could try to boot from an installation cdrom
and undo your changes to the /etc/system file and see if
that helps?

ok> boot cdrom -s

# mount /dev/dsk/<your-root-slice> /a


/Roger

--
Roger Gustavsson
roger.gustavsson@teliasonera.com.INVALID

Hi all,

I got the workaround to my problem..

the first thing that my "diag-switch" was true , thus the ARP error

then i ran "boot -ar" since my /etc/path_to_inst was deleted.

and then everything was fine.

thnx for everybody who replied to my post

cheers,
gaurav