Sponsored Content
Operating Systems Solaris solaris 8 hangs and data access error on reboot Post 302224587 by rhfrommn on Wednesday 13th of August 2008 01:14:38 PM
Old 08-13-2008
This is 99% sure to be failed memory. The 2nd line of your log is pointing to a memory error on DIMM 3, and later the CPU causes a panic to crash the box due to this unrecoverable memory error.

Latest versions of Sol 8 kernel patches had better error correction routines, but if it truly is failing memory that's not going to help much. I'd say replace the bad DIMM, or if the box has enough you can just remove the bad memory and keep it running on less try that and see if it helps.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Data Access Error

Dear Reader, My Sun Machine comes to halt with a message 'Data Access Error'. What / Where could be wrong..?? Thanks in Advance.... (5 Replies)
Discussion started by: joseph_shibu
5 Replies

2. SCO

System hangs on data compression

Hi, We are having an automated system installed on SCO unixware, which runs a End Of Day routine during midnight. Since few days system is hanging at data backup, I have checked the log, system hangs exactly on data compression, any idea or help that why system is hanging only on compression....... (10 Replies)
Discussion started by: tayyabq8
10 Replies

3. Solaris

Boot hangs up on solaris

Hi all, I have a SUN server Sun-Fire-V890 running solaris 9, with a remote system console . Both the IP adresses of the server and the console are in a private network (address 10.67.xxx). For some reasons I need to give the access to the server from outside address 194.xxx, but I prefer that... (2 Replies)
Discussion started by: aribault
2 Replies

4. HP-UX

Can't access external disk after reboot

Hi, I have an HP RX4640 running HP-UX 11iv3 with two internal disks and its connected to a HP disk system 2400 with fibre cable. If the storage system is online before the server is on then the server can't find the disks. And I get the following error messages: vgchange: Warning: Couldn't... (3 Replies)
Discussion started by: hoff
3 Replies

5. Solaris

Unable to login Solaris 10 Sparc - Data Access Error

Hello everyone, This is the first time I am installing Solaris. I have SunBlade 1500 Wrkstn. I installed Solaris 10 Sparc. The installation went successfully but I don't get the login screen. I get the following error message: Boot device: disk:a File and agrs:- Data Access Error Ok ... (4 Replies)
Discussion started by: mfsaeed
4 Replies

6. Solaris

solaris hangs after booting

Hi, We've got a Sun Fire V245 that's failing to boot from either boot disk (mirrored using SVM). It simply hangs after loading a few modules: Sun Fire V245, No Keyboard Copyright 2006 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.22.22, 1024 MB memory installed, Serial... (5 Replies)
Discussion started by: badoshi
5 Replies

7. Solaris

Solaris ssh client hangs when connecting to another Solaris machine

Got a strange problem. I have 4 Solaris servers all configured the same, Solaris 10 x86 update 10. When I try to ssh from one Solaris 10 server to another server ssh hangs. I have an identical server and when I try this everything works fine. The weird thing is if I am root on the server... (1 Reply)
Discussion started by: ccj4467
1 Replies

8. Solaris

Solaris 10 - hangs during boot

Power server up runs through diagnostics. Goes to the boot section and then the bit where the cursor is spinning and thats it. Hangs completely. Any ideas? (10 Replies)
Discussion started by: psychocandy
10 Replies

9. Solaris

Solaris hangs (Firefox)

dear members, i am a newbie to solaris 11.3, and deeply impressed. On my test pc (Lenovo M90), however, using the internet hangs the system from time to time; initializing the connecting (WLAN) during installation (via the live cd) took two attempts as well. Maybe someone has a solution... (7 Replies)
Discussion started by: RichardLichten
7 Replies

10. Solaris

Solaris 10 boot problem - ERROR: Last Trap: Fast Data Access MMU Miss

Hello, We have a T5140 server with Solaris 10 and its suddenly throwing "segmentation core" when I login into the server and not showing any output for commands like df, mount etc. so I had to reboot the server to fix this issue. Please note that there's no boot disk mirroring. But... (2 Replies)
Discussion started by: prvnrk
2 Replies
dontdump(5)							File Formats Manual						       dontdump(5)

NAME
dontdump - defines which classes of kernel memory pages are not dumped when a kernel panic occurs VALUES
Failsafe Default (Allow the kernel to choose which classes to dump.) Allowed values Integer values from to The integer value should be the sum of the integer values for the excluded classes as follows: 2 : Unused pages 4 : User pages 8 : Buffer cache 16 : Kernel text pages 32 : Process stack 64 : File-system Metadata 128 : Kernel dynamic data 256 : Kernel static data 512 : Unused superpage pool Recommended values (Allow the kernel to choose which classes to dump.) The value the kernel usually chooses is = The kernel chooses these classes because they are not usually useful in debugging kernel prob- lems. DESCRIPTION
On large systems, the time required to dump system memory when a kernel panic occurs can be excessive or even prohibitive, depending on how much physical memory is installed in the system. Fast-dump capabilities controlled by the and parameters provide a means for restricting kernel dumps to specific types of information: . Unused Physical Memory . User Process . Buffer Cache . Kernel Code . Process Stack . File-System Metadata . Kernel Dynamic Data . Kernel Static Data . Unused Superpage Pool The command, and its associated configuration file control which of these memory classes are to be included in the memory dumps associated with a kernel panic. On rare occasions, the system may panic before crashconf(1M) is run during the boot process. On those occasions, the configuration can be set using the and tunables. The bit-map value stored in specifies which of these memory classes are not to be included in the memory dumps associated with a kernel panic. The default value for this parameter is The system determines whether or not to dump classes of memory based on the type of crash that occurs, in this case. Note that certain types of system crash, require a full crash dump. Also, the system operator may request a full crash dump at the time the dump is taken. In either of these cases, a full dump will be performed regardless of the classes selected using Who Is Expected to Change This Tunable? Only HP Field engineers should change the value of this tunable. Restrictions on Changing Changes to this tunable take effect at next reboot. Use to change the selection of pages to take effect immediately. When Should the Tunable Be Turned On? This tunable should be turned on to exclude certain classes of pages from being dumped when there is a system crash. This can be done to speedup the dump. What Are the Side Effects of Turning the Tunable On? If pages necessary for analyzing the dump are excluded, then the dump may not be useful for identifying the cause of the system crash. When Should the Tunable Be Turned Off? The tunable is turned off by default. What Are the Side Effects of Turning the Tunable Off? The system decides the page classes that must not be dumped based on the type of crash. The dump may take longer. What Other Tunables Should Be Changed at the Same Time? The tunable should not contain the same page classes as WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of HP-UX. Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation, some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun- able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was factory installed on your system, see at AUTHOR
was developed by HP. SEE ALSO
crashconf(1M), alwaysdump(5). Tunable Kernel Parameters dontdump(5)
All times are GMT -4. The time now is 08:24 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy