Panic on SUN server Post: 302219949

Sponsored Content

Operating Systems Solaris Panic on SUN server Post 302219949 by seun on Wednesday 30th of July 2008 01:02:39 PM

07-30-2008

Registered User

Panic on SUN server

Hi,
I have a SUN server running solaris 9 and crash with the following error message.
Have anybody come across the panic message on a sun server?

panic[cpu0]/thread=3005ce5f480: alloccgblk: can't find blk in cyl, pos:0, i:612, fs:/ bno: 0

000002a100b9ef00 ufs:ufs_fault_v+e0 (30032045ea0, 1527960, 2a100b9f0f0, 1, 1f0e030, 0)

%l0-3: 0000000000000000 0000000001527960 0000000000000000 0000000001512890

%l4-7: 00000300292bc5e0 00000300292bc690 000003005ce596b8 000003005cfebb60

000002a100b9efb0 ufs:ufs_fault+1c (30032045ea0, 1527960, 0, 264, 300327840d4, 0)

%l0-3: 0000000001339a18 0000000000000000 0000000001f0e030 0000011300000000

%l4-7: 000003005bf24a60 000003002e3e0b68 000003004f4b14c0 0000000000001000

000002a100b9f060 ufs:alloccgblk+4bc (0, 90000, 264, 264, 264, 30032784560)

%l0-3: 00000300292bc5e0 0000030032784000 000003006526c460 000003006526c000

%l4-7: 000003005bf24a60 00000300292bc5e0 0000000000000008 0000000000000000

000002a100b9f110 ufs:alloccg+158 (140, 1400, 3005bf24a60, 300292bc690, 2000, 0)

%l0-3: 000003006526c460 0000000000f87008 0000030032784000 000003006526c000

%l4-7: 0000000000002000 00000300292bc5e0 0000000000000140 000003005cfeba00

000002a100b9f1c0 ufs:hashalloc+2c (3005cfeba00, 140, f87008, 2000, 1198dac, 2a100b9f320)

%l0-3: 0000000000000140 0000000000023cec 0000030032784000 0000000000002000

%l4-7: 0000000000000000 0000000001198dac 000003005cfeba00 0000000000000000

000002a100b9f270 ufs:alloc+154 (10, 0, 30032784000, 2a100b9f630, 30029137f70, 23c00)

%l0-3: 0000000000002000 0000000000f87008 00000300292bc5e0 000003005cfeba00

%l4-7: 0000000000f87008 00000000000000ff 0000000000000000 0000000000000000

000002a100b9f330 ufs:bmap_write+8f0 (0, b, 0, f87008, 30029137f70, 0)

%l0-3: 0000000001474800 000003005cfeba00 0000000000002000 0000030032784000

%l4-7: 0000000000000000 00000300292bc5e0 0000000000000003 000000000000000c

000002a100b9f640 ufs:wrip+428 (0, 2a100b9f9f8, 0, 30029137f70, 105d400, 0)

%l0-3: 0000000000000200 000003005cfeba00 0000000000000200 000002a100b9f9f8

%l4-7: 00000300292bc5e0 00000300292bc698 00000300292bc628 0000000000000001

000002a100b9f870 ufs:ufs_write+480 (3005cfebb68, 3005cfebbb8, 1526c00, 1526c00, 0, 0)

%l0-3: 00000300292bc628 00000300292bc5e0 0000000000000000 000002a100b9f9f8

%l4-7: 0000000000000000 0000030029137f70 000003005cfeba00 000003005cfebb60

000002a100b9f940 genunix:write+26c (1, 1b, 200, 3005ce596b8, 61, 7fffffffffffffff)

%l0-3: 00000000011a8894 000003005cfebaa0 0000000000000200 0000000000000000

%l4-7: 0000000000000006 0000000000000200 000003004f4b14c0 0000000000002102

000002a100b9fa40 genunix:write32+38 (6, 26000, 200, 0, 0, 0)

%l0-3: 000003005ce69508 000003005ce596b8 0000000000000004 000002a100b9fba0

%l4-7: 0000000000000000 0000000000000001 0000000000000006 000003005ce5f480

seun

View Public Profile for seun

Find all posts by seun

3 More Discussions You Might Find Interesting

1. Solaris

Sun server

I'm working on a new Sun Solaris server.It was right and run with it's installed Solaris.I used Ifconfig command and check all the file in /etc folder, and now the system can not login as ROOT user in to the server? I'm young in Unix ! I don't know what did I do? How can I comeback ?

2. Red Hat

server panic

Hi, one of our linux server got panic with the following messages Jun 2 17:09:57 inchesfttu006 kernel: ------------------------ Jun 2 17:09:57 inchesfttu006 kernel: kernel BUG at kernel/exit.c:904! Jun 2 17:09:57 inchesfttu006 kernel: invalid operand: 0000 Jun 2 17:09:57 inchesfttu006...

3. Solaris

can any body tell me what is the difference between server panic and fatal error.

HI friends can any body tell me what is the difference between server panic and fatal error.

LEARN ABOUT DEBIAN

installboot

installboot(1M)                                                                                                                    installboot(1M)

NAME

       installboot - install bootblocks in a disk partition

SYNOPSIS

       installboot bootblk raw-disk-device

       The boot(1M) program, ufsboot, is loaded from disk by the bootblock program which resides in the boot area of a disk partition.

       The  ufs  boot objects are platform-dependent, and reside in the /usr/platform/platform-name/lib/fs/ufs directory. The platform name can be
       found using the -i option of uname(1).

       The installboot utility is a SPARC only program. It is not supported on the  architecture.  users should use installgrub(1M) instead.

       bootblk         The name of the bootblock code.

       raw-disk-device The name of the disk device onto which the bootblock code is to be installed; it must be a character device which is  read-
                       able and writable. Naming conventions for a SCSI or IPI drive are c?t?d?s? and c?d?s? for an IDE drive.

       Example 1: Installing UFS Boot Block

       To install a ufs boot block on slice 0 of target 0 on controller 1 of the platform where the command is being run, use:

              example# installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk 
                   /dev/rdsk/c1t0d0s0

       /usr/platform/platform-name/lib/fs/ufs

           directory where ufs boot objects reside.

       /platform/platform-name/ufsboot

           second level program to boot from a disk or CD

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE         |      ATTRIBUTE VALUE        |
       +-----------------------------+-----------------------------+
       |Availability                 |SUNWcsu                      |
       +-----------------------------+-----------------------------+

       od(1), uname(1), boot(1M), init(1M), kadb(1M), kernel(1M), monitor(1M), reboot(1M), rpc.bootparamd(1M), init.d(4), attributes(5)

WARNINGS

       The installboot utility fails if the bootblk or openfirmware files do not exist or if the raw disk device is not a character device.

                                                                    11 Apr 2005                                                    installboot(1M)