11-14-2010
Check the errpt entries before and after the disk replacement, do they show the same disk detail, serial, Etc?
If they do then something odd is going on, like the VG thinks it is still missing the old disk.
If the new errors show the details of the new hdisk28 then it looks like the new disk has a problem.
10 More Discussions You Might Find Interesting
1. SuSE
Errpt- Generates an error report from entries in the log.
Errpt is a AIX command.
we want equivallent suse linux command.
If there is no exact replace ment pls give us alternative way.
we want to log each n evry system error and generate an error report (2 Replies)
Discussion started by: vrguha
2 Replies
2. AIX
Hi All,
Can anyone explain me the meanning of the following errors:
LABEL: SC_DISK_ERR2
IDENTIFIER: B6267342
Description
DISK OPERATION ERROR
Probable Causes
DASD DEVICE
Failure Causes
DISK DRIVE
DISK DRIVE ELECTRONICS
Recommended Actions
PERFORM PROBLEM DETERMINATION... (1 Reply)
Discussion started by: gianlu
1 Replies
3. AIX
Hi,
I'm getting the errors below in the errpt report for a IBM Blade server. I'm guessing there's a problem with one of the disks but don't know how I can confirm this. Can anyone offer any suggestions?
Regards
Gareth (4 Replies)
Discussion started by: m223464
4 Replies
4. Solaris
Hello,
Can someone advise the proper procedure for replacing a mirrored disk in SVM. I have checked the docs and various websites but the procedure seems to vary. This is what I would do...
1. Remove the db replicas from the bad disk.
2. Detach it from the mirror
3. Clear it with... (4 Replies)
Discussion started by: Actuator
4 Replies
5. UNIX and Linux Applications
We are getting below error when processing a transaction through ESB.
I work for SOA admin and checked the JCA connection is working fine also code also working fine in other envs.
An unhandled exception has been thrown in the ESB system. The exception reported is:... (1 Reply)
Discussion started by: KuldeepSinghTCS
1 Replies
6. AIX
Hello,
after upgrading the memory to 96GB & 6 Dual Processor for P 550 ( and still not applied the parameters which some experienced posters said in post https://www.unix.com/aix/141835-oracle-database-running-slow-aix-nmon-topas-6.html )
I am getting system dumps. How to understand and... (1 Reply)
Discussion started by: filosophizer
1 Replies
7. Shell Programming and Scripting
Hi folks,
I am trying to send an email in Perl script with the below code.
I have written the code in Padre IDE and installed all the required modules(Mail::Sendmail) and executed the code.
It is neither showing errors nor giving the output. I havnt received an mail after running the below... (1 Reply)
Discussion started by: giridhar276
1 Replies
8. Shell Programming and Scripting
Hey guys.
I have created a script that mounts an external folder via sshfd, counts the number of files then do some delete and then counts the files again to get how many files have been deleted.
Then it sends the resault by mail.
My question is, how can i send via mail the errors on this... (2 Replies)
Discussion started by: Pizza
2 Replies
9. Filesystems, Disks and Memory
Hello,
On 4/20/2018, we performed a disk replacement on our IBM 8202 P7 server. After the disk was rebuilt, the SAS Disk Array sissas0 showed a status of degraded. However, the pdisks in the array all show a status of active.
We did see a message in errpt. DISK ARRAY PROTECTION SUSPENDED.
... (1 Reply)
Discussion started by: terrya
1 Replies
10. AIX
Hello,
On 4/20/2018, we performed a disk replacement on our IBM 8202 P7 server. After the disk was rebuilt, the SAS Disk Array sissas0 showed a status of degraded. However, the pdisks in the array all show a status of active.
We did see a message in errpt. DISK ARRAY PROTECTION SUSPENDED.
... (3 Replies)
Discussion started by: terrya
3 Replies
BAD144(8) System Manager's Manual BAD144(8)
NAME
bad144 - read/write DEC standard 144 bad sector information
SYNOPSIS
bad144 disktype disk [ sno [ bad ... ] ]
DESCRIPTION
Bad144 can be used to inspect the information stored on a disk that is used by the disk drivers to implement bad sector forwarding. The
format of the information is specified by DEC standard 144, as follows.
The bad sector information is located in the first 5 even numbered sectors of the last track of the disk pack. There are five identical
copies of the information, described by the dkbad structure. Only the first of these copies is used.
Replacement sectors are allocated starting with the first sector before the bad sector information and working backwards towards the begin-
ning of the disk. A maximum of 126 bad sectors can be supported. The position of the bad sector in the bad sector table determines which
replacement sector it corresponds to.
The bad sector information and replacement sectors are conventionally only accessible through the ``h'' file system partition of the disk.
If that partition is used for a file system, the user is responsible for making sure that it does not overlap the bad sector information or
any replacement sectors.
The bad sector structure is as follows:
struct dkbad {
long bt_csn; /* cartridge serial number */
u_short bt_mbz; /* unused; should be 0 */
u_short bt_flag; /* -1 => alignment cartridge */
struct bt_bad {
u_short bt_cyl; /* cylinder number of bad sector */
u_short bt_trksec; /* track and sector number */
} bt_bad[MAXBAD];
};
Unused slots in the bt_bad array are filled with all bits set, a putatively illegal value. MAXBAD (in <sys/dkbad.h>) may be tuned locally
to reduce the space required to hold the bad-sector file in memory. It may not be greater than 126, which uses the whole disk sector. Bad
sectors past MAXBAD may be included by the formatter, but replacement sectors will not be used until MAXBAD is increased.
Bad144 is invoked by giving a device type (e.g. rk07, rm03, rm05, etc.), and a device name (e.g. hk0, hp1, etc.). It reads the first sec-
tor of the last track of the corresponding disk and prints out the bad sector information. It may also be invoked giving a serial number
for the pack and a list of bad sectors, and will then write the supplied information onto the same location. Note, however, that bad144
does not arrange for the specified sectors to be marked bad in this case. This option should only be used to restore known bad sector
information which was destroyed.
New bad sectors can be added by running the standard DEC formatter in section ``bad.''
SEE ALSO
badsect(8)
BUGS
Not all drivers support bad-sector forwarding on the PDP-11.
It should be possible to both format disks on-line under UNIX and to change the bad sector information, marking new bad sectors, without
running a standalone program.
The bootstrap drivers used to boot the system do not understand bad sectors or handle ECC errors. This means that none of these errors can
occur when reading the file /unix to boot. Sector 0 of the disk drive and the file /boot in the root file system of that drive must also
not have any of these errors in it.
The drivers that write a system core image on disk after a crash do not handle errors; thus the crash dump area must be free of errors and
bad sectors.
3rd Berkeley Distribution BAD144(8)