03-12-2013
Hi,
Thanks for your help.
Mistakenly we unassingned the disks, that's why we got those errors.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
Can we modify the GDB source code so as to analyze core dumps from different targets? From my analysis, I think we need to build our section table statically for each target. i.e., including the various address boundaries in build_section_table() function. If this is the case, then the GDB... (2 Replies)
Discussion started by: nsdeeps
2 Replies
2. UNIX for Advanced & Expert Users
hi you all!
I can write a network program to send and receive some messages. I use
read() and write() functions for extracting of sending messages via a given socket. By doing so, i know only the actions performed at the application layer of the TCP/IP suite. But i want to control the actual... (2 Replies)
Discussion started by: solomonml
2 Replies
3. Solaris
Hi,
Recently I faced with need of analyze root disk. I figured out two possible ways to do it:
1. Practical. Boot from CD and run format
2. Theoretical. Create live upgrade boot environment on another disk, activate it, reboot, unmont all root disk partitions and run format.
I've already... (3 Replies)
Discussion started by: Sapfeer
3 Replies
4. Shell Programming and Scripting
Hello there,
i am trying to write a shell script to analyse some of my log files.
I want the script to check if there is a logfile from yesterday or today (some times the script that creates the logfile takes a bit longer and its after 00:00) and search the logfile itself if the script was... (0 Replies)
Discussion started by: Linien
0 Replies
5. UNIX for Advanced & Expert Users
Dear All,
I am new to this forum. This is my first.
I am facing customer issue. Customer has got core file while running the server.
He had sent core file and details from pstack, pmap and pldd commands.
I have to debug this application, please help me to fix this issue.
I am using sparc... (1 Reply)
Discussion started by: KiranBangalore
1 Replies
6. Solaris
Dear All,
I am new to this forum. This is my first.
I am facing customer issue. Customer has got core file while running the server.
He had sent core file and details from pstack, pmap and pldd commands.
I have to debug this application, please help me to fix this issue.
I am using sparc 10... (4 Replies)
Discussion started by: KiranBangalore
4 Replies
7. Solaris
I need to analyse some vmcore files, do you guys know how can i get a free version of the "Solaris Crash Analysis Tool " (2 Replies)
Discussion started by: feg
2 Replies
8. Shell Programming and Scripting
Hi all,
I'm working with a peice of software that runs on Linux that allows planning trips in cars through maps. This software has different variations depending on the type of car, e.g. BMW, Audi, Hyundai, etc... Each variation has a dependency on common external components that are not... (1 Reply)
Discussion started by: emoshaya
1 Replies
9. UNIX for Dummies Questions & Answers
Hi,
Someone please analyse the following o/p of fdisk -l and tell me what it means for /dev/sda, /dev/sdb, /dev/sdc ....
Disk /dev/sda: 53.6 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start ... (5 Replies)
Discussion started by: stunn3r
5 Replies
10. AIX
Hi everyone,
I am trying to configure AIX 6.1 using syslogd to send syslog event to syslog server configured on RHEL. However, RHEL never receives the events.
I have tried to redirect the syslog event on AIX to a local file and successful. Only forwarding to remote server fails.
Firewall... (10 Replies)
Discussion started by: michael_hoang
10 Replies
LEARN ABOUT MOJAVE
diskscan
diskscan(1M) System Administration Commands diskscan(1M)
NAME
diskscan - perform surface analysis
SYNOPSIS
diskscan [-W] [-n] [-y] raw_device
DESCRIPTION
diskscan is used by the system administrator to perform surface analysis on a portion of a hard disk. The disk portion may be a raw parti-
tion or slice; it is identified using its raw device name. By default, the specified portion of the disk is read (non-destructive) and
errors reported on standard error. In addition, a progress report is printed on standard out. The list of bad blocks should be saved in a
file and later fed into addbadsec(1M), which will remap them.
OPTIONS
The following options are supported:
-n Causes diskscan to suppress linefeeds when printing progress information on standard out.
-W Causes diskscan to perform write and read surface analysis. This type of surface analysis is destructive and should be invoked
with caution.
-y Causes diskscan to suppress the warning regarding destruction of existing data that is issued when -W is used.
OPERANDS
The following operands are supported:
raw_device The address of the disk drive (see FILES).
FILES
The raw device should be /dev/rdsk/c?[t?]d?[ps]?. See disks(1M) for an explanation of SCSI and IDE device naming conventions.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Architecture |x86 |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
addbadsec(1M), disks(1M), fdisk(1M), fmthard(1M), format(1M), attributes(5)
NOTES
The format(1M) utility is available to format, label, analyze, and repair SCSI disks. This utility is included with the diskscan, addbad-
sec(1M), fdisk(1M), and fmthard(1M) commands available for x86. To format an IDE disk, use the DOS format utility; however, to label, ana-
lyze, or repair IDE disks on x86 systems, use the Solaris format(1M) utility.
SunOS 5.10 24 Feb 1998 diskscan(1M)