04-05-2018
T4-2 - Memory DIMM issue - ldom config resets to factory-default
Which basically means the ldoms that were on there are not starting (not even showing).
If I do ldm list-config it shows live config as next reboot. But, of course, next reboot it reverts back to factory default again.
I must admit I'm wondering if its doing this becasue (with the one faulty DIMM) there is now not enough memory to serve the LDOMS configured. Does this make sense?
Bit worrying if one DIMM failure can take out entire host :-(
5 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi, Im in need to get the mem config on a sun sparq
Can some one please helpe me?
(im not a unixperson) (1 Reply)
Discussion started by: skil
1 Replies
2. HP-UX
Hi,
How to check the memory dimm status from OS leavel!! My system model HP N4000.
Thanks,
ARumugam. (2 Replies)
Discussion started by: arumsun
2 Replies
3. Solaris
Hi. I have 2 SunFire V490 servers running Solaris 10. We may have to upgrade with more memory on one of them to make it compatible with the other. Here's the one with 12GB of RAM:
Memory size: 12288 Megabytes
========================= CPUs ===============================================
... (1 Reply)
Discussion started by: th1amigo
1 Replies
4. Solaris
Solaris for Sparc 11.1 with the latest patches. Created a Guest LDOM with two vnet's net0 and net1, installed a guest whole root, ip exclusive zone that I want to be able to utilize DHCP. I have been able to create the zone but unable to get it to boot because I am unable to assign an anet to it.... (4 Replies)
Discussion started by: os2mac
4 Replies
5. Solaris
T4-2 issues meant replacing motherboard.
I thought the ldom config was automatically saved? Got the oracle document here.
At the moment, unable to get ldoms back - here is the output from a few commands:-
ldm list
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME... (4 Replies)
Discussion started by: psychocandy
4 Replies
REBOOT(8) System Manager's Manual REBOOT(8)
NAME
reboot - reboot the system immediately
SYNOPSIS
reboot [-f]
DESCRIPTION
Reboot can be used to reboot the system after installing a new kernel. It does not inform the users, but does log it's actions in
/usr/adm/wtmp and /usr/adm/authlog. The system is then rebooted with the reboot(2) systemcall.
If the -f flag is not given then all processes are sent terminate signals to give them a chance to die peacefully before the reboot() call.
If the wtmp file exists, reboot logs itself as if it were a shutdown. This is done to prevent last(1) from talking about system-crashes.
Reboot is registered as is in the authlog file.
Reboot can only be executed by the super-user. Any other caller will be refused, either by reboot(8) or by reboot(2).
SEE ALSO
reboot(2), shutdown(8), halt(8), boot(8).
BUGS
The error message's given by reboot are not always useful. There are several routines that can fail, but which are not fatal for the pro-
gram.
AUTHOR
Edvard Tuinder (v892231@si.hhs.NL)
REBOOT(8)