Sponsored Content
Operating Systems Solaris M5000 showhardconf is showing everything is Deconfigured Post 302964862 by DukeNuke2 on Wednesday 20th of January 2016 08:19:26 AM
Old 01-20-2016
As it looks, CPUM#0-CHIP#0 and MEM#1A are faulted and might need replacement.
 

10 More Discussions You Might Find Interesting

1. Solaris

M5000 Question

Hi, I 've a fully loaded M5000 which i would like to partition in 4 domains but i have a concern that since we have only 4 internal disks how can we partition the box in for domains with 2 disks ( mirrored ) in each domain. Should i go ahead with 1 Lun from SAN and 1 internal disk for each of 4... (3 Replies)
Discussion started by: fugitive
3 Replies

2. Solaris

M5000 servers - XSCF functions

Hi all A couple of new M5000 servers will be arriving soon and I need to work out how to configure the underlying domains. It will come with 4 x CPUS, 32 Gb of memory, 4 x HD, 2 x IOtrays. Reading the XSCF manual, I can configure the item into 2 domains, something about uni / quad xsb.... (9 Replies)
Discussion started by: sbk1972
9 Replies

3. Solaris

M5000 Question

Hi i 've a M5000 running 2 domains in my Lab with following hardconf SPARC Enterprise M5000; Memory_Size:128 GB; +-----------------------------------+------------+ | FRU | Quantity | +-----------------------------------+------------+ | MBU_B... (3 Replies)
Discussion started by: fugitive
3 Replies

4. Solaris

Unable to start SunVTS on M5000

Please advise. Thank you bash-3.00# cd /usr/sunvts/bin/ bash-3.00# ls bios.bin iobushangscript.sh stopsunvts vtsprobe cmos.bin javabridge.jar sunlink vtsreportgenerate dispatcher loadVtsServer svmVolDiskList vtstalk env6test... (6 Replies)
Discussion started by: incredible
6 Replies

5. HP-UX

Deconfigured memories on RX7640

Hello, I am installing RX7640 and i have some issue with the memory modules. My system shows them as deconfigured. Do you think I use the right memories? (2 Replies)
Discussion started by: stapley
2 Replies

6. Solaris

Mounting USB in XSCF on M5000

Trying to update my M5000 firmware. trying to mount my USB to upload firmware and getting the following message. XSCF> getflashimage -v file:///media/usb_msd/FFXCP1115.tar.gz Free space: 97MB Making sure mount point is clear umount: /media/usb_msd is not mounted (according to mtab) Trying... (2 Replies)
Discussion started by: soupbone38
2 Replies

7. Solaris

How to solve M5000 CPU "Deconfigured" state?

Hi Community, i have one M5000 spare machine which was handled by support team. they told me that it is gone completely . i have checked the status. before it was showing MBU_B degraded. i updated to latest firmware and , resetted the xscf and now this is showing as normal. MBU_B... (5 Replies)
Discussion started by: bentech4u
5 Replies

8. IP Networking

M5000 Xscf

I took over an M5000 and have a jumper server with a nic to connect to the console IP of an M5000. access via ssh user@ip. it was working fine, another person can connect remotely on the subnet, but when I ssh,it just hangs and then times out. so my question is, any ideas of what I might... (4 Replies)
Discussion started by: rrodgers
4 Replies

9. Solaris

M5000 fails to boot

I have an m5000 that Is down. I have access to XSCF> and was able to get to the ok prompt. However, on >ok boot it failed to boot. erred with : svc.startd: svc:/system/device/fc-fabric:default: Method "/lib/svc/method/fc-fabric" failed due to signal KILL. Nov 29... (3 Replies)
Discussion started by: goya
3 Replies

10. Hardware

M5000 won't power up

on an m5000 , I can not power it up, system failure. XSCF> poweron -a DomainIDs to power on:00,01 Continue? :y 00 :Not powering on :Poweron canceled due to missing component. 01 :Not powering on :Poweron canceled due to missing component. the only fault that I can see is: ... (4 Replies)
Discussion started by: goya
4 Replies
MEM(4)                                                       Linux Programmer's Manual                                                      MEM(4)

NAME
mem, kmem, port - system memory, kernel memory and system ports DESCRIPTION
/dev/mem is a character device file that is an image of the main memory of the computer. It may be used, for example, to examine (and even patch) the system. Byte addresses in /dev/mem are interpreted as physical memory addresses. References to nonexistent locations cause errors to be returned. Examining and patching is likely to lead to unexpected results when read-only or write-only bits are present. Since Linux 2.6.26, and depending on the architecture, the CONFIG_STRICT_DEVMEM kernel configuration option limits the areas which can be accessed through this file. For example: on x86, RAM access is not allowed but accessing memory-mapped PCI regions is. It is typically created by: mknod -m 660 /dev/mem c 1 1 chown root:kmem /dev/mem The file /dev/kmem is the same as /dev/mem, except that the kernel virtual memory rather than physical memory is accessed. Since Linux 2.6.26, this file is available only if the CONFIG_DEVKMEM kernel configuration option is enabled. It is typically created by: mknod -m 640 /dev/kmem c 1 2 chown root:kmem /dev/kmem /dev/port is similar to /dev/mem, but the I/O ports are accessed. It is typically created by: mknod -m 660 /dev/port c 1 4 chown root:kmem /dev/port FILES
/dev/mem /dev/kmem /dev/port SEE ALSO
chown(1), mknod(1), ioperm(2) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. Linux 2015-01-02 MEM(4)
All times are GMT -4. The time now is 08:45 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy