Sponsored Content
Full Discussion: Short Disk Read
Operating Systems Solaris Short Disk Read Post 303019033 by MadeInGermany on Thursday 21st of June 2018 02:17:05 PM
Old 06-21-2018
The message looks like memory error.
Set diag-level to min again; you might still see the error but sooner.

You should power-off the box, open the box, and swap the DIMMs.
1. Re-seating might wipe off some dust or oxide
and
2. During boot the DIMM0 or the first memory bank is used; moving a good DIMM to this position will enable boot (ok, it depends on the hardware/model if this trick works).
You might need to also set the diag-switch? to false again.
Of course, when booted, it might fail/crash later...
This User Gave Thanks to MadeInGermany For This Post:
 

10 More Discussions You Might Find Interesting

1. Linux

read removable disk

Hello I am trying to read from a small disk , 256 MB , removable sandisk.I am not able to access the device. The system does not recognise my disk to copy file s from the disk. Please post your solution in this issue. Thanks (2 Replies)
Discussion started by: singh85
2 Replies

2. Filesystems, Disks and Memory

I need read data from Disk,please help

Hallo, can You help me with this problem: I have Hard Disk with "SCO Server Release 5.0" and I need read the data from the disk. Know You how can I do it? I only know that the file system is ISC UNIX . I test FreeBSD, but I can not mount the disk (with error message "incorrect super block").... (7 Replies)
Discussion started by: Fik
7 Replies

3. SCO

Read a SCO floppy disk under another OS...

I have formatted a floppy disk under SCO unix. Is there a way I could read this disk under another operating system e.g. Windows or Linux? (1 Reply)
Discussion started by: sgertsos
1 Replies

4. SCO

i can't read hard disk scsi

i was installing i my computer windows xp and sco when i use knoppix5.0 live to read scsi partition wish sco was installing show me message that i have not permission to acces in scsi hard drive help me please (1 Reply)
Discussion started by: walidfinder
1 Replies

5. Solaris

How to read EMC disk space

Hi I am using Solaris8.I want to find the total disk space of my server.Can anyone please tell that which field in below mentioned code signifies the disk space and whether this space is in Mb or GB. c11t0d52 <EMC-SYMMETRIX-5264 cyl 4 alt 2 hd 15 sec 64> ... (4 Replies)
Discussion started by: sharmaankur85
4 Replies

6. Filesystems, Disks and Memory

Disk read and write speed.

Being a novice user to linux i m little unaware of how would i check disk read write speed. One of my mate is suggesting to create a file using dd command and check how much time it takes to create a 30 gb file . I think this has a little sense however i would also like to take your reviews... (5 Replies)
Discussion started by: pinga123
5 Replies

7. UNIX for Dummies Questions & Answers

How to read a disk label?

Hi there, I'm wondering how to display a disk label (why not edit it but I don't need that yet). I found several commands on forums like disklabel and diskinfo but I can't find them on my system and don't know the package they belong to. Can you help me? Cheers Santiago (2 Replies)
Discussion started by: chebarbudo
2 Replies

8. Solaris

Read/Write Data on CD/RW Disk

Would simply like to write data (no audio) to a CD/RW disk. The disk drive states CD/RW on the front but don't know for sure if the software is configured to recognize it as a writable disk. I can read/move data from the disk to the hard drive with no issue from the disk. Any help in this... (4 Replies)
Discussion started by: jes1trish
4 Replies

9. UNIX for Advanced & Expert Users

read sectors from disk failed with timeout

i'm writing some code to simulate the boot progress after power on but when i try to read the 2nd sector from a floppy disk, this operation always fail with ah=0x80h which means timeout, how can i get over this problem? my code would be like this: $ cat boot.S .code16 #define SETUPLEN 4... (0 Replies)
Discussion started by: wljackhero
0 Replies

10. AIX

read lv mountpoint information directly from disk

Hello, I need to get the lv mountpoint from the hdisk directly (from vgda i guess) and not from odm or /etc/filesystems I knew the command, but unfortunately I forgot it ;) cheers funksen (5 Replies)
Discussion started by: funksen
5 Replies
cfgadm_ac(1M)						  System Administration Commands					     cfgadm_ac(1M)

NAME
cfgadm_ac - EXX00 memory system administration SYNOPSIS
/usr/sbin/cfgadm [-c configure] [-f] [-o disable-at-boot | enable-at-boot ] ac#:bank# ... /usr/sbin/cfgadm [-c unconfigure] [-o disable-at-bootp | enable-at-boot ] ac#:bank# ... /usr/sbin/cfgadm [-v] [-o quick | normal | extended, [max_errors=#] ] -t ac#:bank#... /usr/sbin/cfgadm -x relocate-test ac#:bank# ... /usr/sbin/cfgadm [-l] -o disable-at-boot | enable-at-boot ac#:bank# ... DESCRIPTION
The ac hardware specific library /usr/platform/sun4u/lib/cfgadm/cfgadm_ac.so.1 provides the functionality for configuring and unconfiguring memory banks on E6X00, E5X00, E4X00 and E3X00 systems as part of the Dynamic Reconfiguration of CPU/Memory boards using cfgadm_sysctrl(1M). Memory banks appear as attachment points in the device tree. For each CPU/Memory board, two attachment points are published, one for each bank on the board: bank0 and bank1. If the bank is unpopulated, the receptacle state is empty. If the bank is populated, the receptacle state is connected. The receptacle state of a memory bank can never be disconnected. The occupant state of a connected memory bank can be configured or unconfigured. If the occupant state is configured, the memory is in use by Solaris, if unconfigured it is not. OPTIONS
Refer to cfgadm(1M) for complete descriptions of the command options. The following options are supported: -c configure | unconfigure Change the occupant state. The configure argument ensures that the memory is initialized and adds the memory to the Solaris memory pool. The unconfigure argument removes the memory from use by Solaris. When a CPU/Memory board is to be removed from a system, both banks of memory must be unconfigured. cfgadm refuses the configure operation if the memory on the board is marked disabled-at-boot (see info field), unless either the -f (force) option or the enable at boot flag, (-o enable-at-boot), is given. The configure operation takes a short time proportional to the size of memory that must be initialized. cfgadm refuses the unconfigure operation if there is not enough uncommitted memory in the system (VM viability error) or if the bank to be unconfigured has memory that can't be removed (non-relocatable pages error). The presence of non-relocatable pages is indicated by the word permanent in the info listing field. Removing memory from use by Solaris may take a significant time due to factors such as system load and how much paging to secondary storage is required. The unconfigure operation can be cancelled at any time and the memory returned to the fully configured state by interrupting the command invocation with a signal. The unconfigure operation self-cancels if no memory can be removed within a timeout period. The default timeout period of 60 seconds can be changed using the -o timeout=# option, with a value of 0 disabling the timeout. -f Force option. Use this option to override the block on configuring a memory bank marked as disabled at boot in the non-volatile dis- abled-memory-list variable. See Platform Notes:Sun Enterprise 6x00/5x00/4x00/3x00 Systems -l List option. This option is supported as described in cfgadm(1M). The type field is always memory. The info field has the following information for empty banks: slot# empty The slot# indicates the system slot into which the CPU/Memory board is inserted. For example, if this were slot11 the attachment point for use with cfgadm to manipulate the associated board would be sysctrl0:slot11. The info field has the following information for connected banks: slot# sizeMb|sizeGb [(sizeMb|sizeGb used)] base 0x### [interleaved #-way] [disabled at boot] [permanent] The size of the bank is given in Mb or Gb as appropriate. If the memory is less than completely used, the used size is reported. The physical base address is given in hexadecimal. If the memory bank is interleaved with some other bank, the interleave factor is reported. If the memory on the board is disabled at boot using the non-volatile disabled-memory-list variable, this is reported. If the bank has memory that cannot be removed this is reported as permanent. -o disable-at-boot | enable-at-boot These options allow the state of the non-volatile disabled-memory-list variable to be modified. These options can be used in conjunc- tion with the issuing of a -c option or with the explicit or implied listing command, -l, if no command is required. Use of -o enable- at-boot with the configure command to override the block on configuring memory on a board in the disabled memory list. -o extended | normal | quick Use with the -t option to specify test level. The normal test level ensures that each memory cell stores both a 0 and a 1, and checks that all cells are separately addressable. The quick test level only does the 0s and 1s test, and typically misses address line problems. The extended test uses patterns to test for adjacent cell interference problems. The default test level is normal. See -t option. -o max_errors=# Use with the -t option to specify the maximum number of allowed errors. If not specified, a default of 32 is assumed. -o timeout=# Use with the unconfigure command to set the self-cancelling timeout. The default value is 60 and the unit is seconds. A value of 0 means no timeout. -t Test an unconfigured bank of memory. Specify the test level using the -o quick | normal | extended option. cfgadm exits with a 0 (success) if the test was able to run on the memory bank. The result of the test is available in the condition for the attachment point. -v Verbose option. Use this option in combination with the -t option to display detailed progress and results of tests. -x relocate-test For all pages of memory in use on the specified memory bank, a relocation operation as used in the unconfigure command is attempted. The success of this operation does not guarantee that the bank can be unconfigured. Failure indicates that it probably cannot be uncon- figured. This option is for test purposes only. OPERANDS
The following operand is supported: ac#:bank# The attachment points for memory banks are published by instances of the address controller (ac) driver (ac#). One instance of the ac driver is created for each system board, but only those instances associated with CPU/Memory boards publish the two bank attachment points, bank0 and bank1. This form conforms to the logical ap_id specification given in cfgadm(1M). The corresponding physical ap_ids are listed in the FILES section. The ac driver instance numbering has no relation to the slot number for the corresponding board. The full phys- ical attachment point identifier has the slot number incorporated into it as twice the slot number in hexadecimal directly following the fhc@ part. FILES
/devices/fhc@*,f8800000/ac@0,1000000:bank? attachment points /usr/platform/sun4u/lib/cfgadm/cfgadm_ac.so.1 hardware specific library file ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWkvm.u | +-----------------------------+-----------------------------+ SEE ALSO
cfgadm(1M), cfgadm_sysctrl(1M), config_admin(3CFGADM), attributes(5) Sun Enterprise 6x00, 5x00, 4x00 and 3x00 Systems Dynamic Reconfiguration User's Guide Platform Notes:Sun Enterprise 6x00/5x00/4x00/3x00 Systems NOTES
Refer to the Sun Enterprise 6x00, 5x00, 4x00 and 3x00 Systems Dynamic Reconfiguration User's Guide for additional details regarding dynamic reconfiguration of EXX00 system CPU/Memory boards. SunOS 5.10 29 Sep 1999 cfgadm_ac(1M)
All times are GMT -4. The time now is 07:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy