Sponsored Content
Full Discussion: "PANIC CPU" ERROR MESSAGE
Operating Systems Solaris "PANIC CPU" ERROR MESSAGE Post 302522311 by feg on Saturday 14th of May 2011 10:10:47 AM
Old 05-14-2011
Error "PANIC CPU" ERROR MESSAGE

A server that I am working on (SUN FIRE V240 , SOLARIS 10) doesn't boot because of a corrupted files system.

I tried to repair de file system, I also tried to to restore all the files systems with a backup of the server that I have but the message bellow appear
Code:
 
 panic[cpu0]/thread=30002fc2060: alloccgblk: can't find blk in cyl, pos:0, i:381, fs:/opt bno: 1680 

Does anyone know what it is and how can I fix this issue??

Last edited by feg; 05-14-2011 at 11:30 AM..
 

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

"syntax error at line 21 :'done' unexpected." error message"

I am trying to run the script bellow but its given me "syntax error at line 20 :'done' unexpected." error message" can someone check to see if the script is ok? and correct me pls. Today is my first day with scripting. Gurus should pls help out #!/bin/ksh # Purpose: Check to see if file... (3 Replies)
Discussion started by: ibroxy
3 Replies

2. Debian

Debian: doubt in "top" %CPU and "sar" output

Hi All, I am running my application on a dual cpu debian linux 3.0 (2.4.19 kernel). For my application: <sar -U ALL> CPU %user %nice %system %idle ... 10:58:04 0 153.10 0.00 38.76 0.00 10:58:04 1 3.88 0.00 4.26 ... (0 Replies)
Discussion started by: jaduks
0 Replies

3. UNIX for Dummies Questions & Answers

suppressing an error message using the "ls" command

hi I'm new here so my question maybe be retarded or out of place: Is there a way to suppress the "No such file or directory" error message when using the "ls" command ? thanks (5 Replies)
Discussion started by: basher400
5 Replies

4. UNIX for Advanced & Expert Users

mailx error message -- "me": not a group

Hi all, When I tried to use mailx like mailx -s "test" someone@somedomain.com < myfile , mailx replies with "me": not a group. Mail did get sent though. So how to deal with this "me": not a group response. I guess it is because some property was not set properly. Because mailx worked well... (0 Replies)
Discussion started by: qiulang
0 Replies

5. Forum Support Area for Unregistered Users & Account Problems

Cannot register due to "spam" error message

Hi all, I am trying to register but it seems my IP address is being seen or black listed as a spam address. I get the following message: "Registration denied. Sorry, The UNIX and Linux Forums runs an active policy of not allowing spammers. Please contact us via by posting in this forum if... (0 Replies)
Discussion started by: codenjanod
0 Replies

6. SCO

"PANIC: k_trap" error

hi I've virtualized physical SCO 5.0.6 on ESX 4 according to: Blog du DS45: HOWTO SCO P2V in the real life SCO starts with the network, but during shutdown I'm getting this message: PANIC: k_trap. My /etc/default/boot: # cat /etc/default/boot #ScoAdminInit BOOTMNT {RO RW NO} RO... (4 Replies)
Discussion started by: ccc
4 Replies

7. UNIX for Dummies Questions & Answers

ls command gives "Not a directory" error message

The operating system is Solaris. There is a perl interpreter that is located at /opt/perl5.10.0/perl. when i give ls -ltr /opt/perl5.10.0/perl I get an error message saying that "/opt/perl5.10.0/perl Not a directory" At the next instant when i give the same command it lists the properties of... (5 Replies)
Discussion started by: sreeharshasn
5 Replies

8. UNIX for Dummies Questions & Answers

Unix "look" Command "File too large" Error Message

I am trying to find lines in a text file larger than 3 Gb that start with a given string. My command looks like this: $ look "string" "/home/patrick/filename.txt" However, this gives me the following message: "look: /home/patrick/filename.txt: File too large" So, I have two... (14 Replies)
Discussion started by: shishong
14 Replies
root_archive(1M)														  root_archive(1M)

NAME
root_archive - manage bootable miniroot archives SYNOPSIS
/boot/solaris/bin/root_archive pack archive root /boot/solaris/bin/root_archive unpack archive root /boot/solaris/bin/root_archive packmedia solaris_image root /boot/solaris/bin/root_archive unpackmedia solaris_image root The root_archive utility is used to manage bootable miniroot archives and is currently only available on platforms. The utility can pack and unpack boot/root archives in both ufs and hsfs (iso9660) format. It will always generate ufs archives. root_archive also uses the lofi file driver to export a file as a block device (see lofi(7D)) and mount to mount or unmount file systems and remote resources (see mount(1M)). root_archive requires the same privileges that are needed to run these commands. SUBCOMMANDS
The root_archive command has the following subcommands: pack archive root Pack from the image found under the root directory to the archive. unpack archive root Unpack from the archive to an unpacked image under the root directory. packmedia solaris_image root Pack the solaris image to the root directory. unpackmedia solaris_image root Unpack the solaris image from the root directory. For packmedia and unpackmedia, other items that do not go into the ramdisk image are copied or uncopied (see cpio(1)) as well. Specifi- cally, this includes all the packaging databases needed for pkgadd and the other packaging utilities to succeed which are not used in the running and hence pruned to conserve memory. EXAMPLES
Example 1: Unpacking the Solaris x86 install image The following command unpacks the current Solaris image from the root directory: # root_archive unpackmedia /export/nv/solarisdvd.nvx_dvd/latest /export/Boot Where /export/nv/solarisdvd.nvx_dvd/latest represents a path to a Solaris x86 install image and /export/Boot is a directory that will be purged or created, as necessary. Example 2: Packing the Solaris x86 install image The following command packs the current Solaris image to the root directory: # root_archive packmedia /export/nv/solarisdvd.nvx_dvd/latest /export/Boot The following exit values are returned: 0 The command completed successfully. 1 The command exited due to an error. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ cpio(1), bootadm(1M), mount(1M), attributes(5), lofi(7D) 26 Sep 2005 root_archive(1M)
All times are GMT -4. The time now is 03:24 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy