03-31-2009
Command to List Hard Disk Information
I have a SparcStation5 that is making sounds that make me think the disk drive(s) may be on the verge of quiting. What is the command to list the disk types and sizes? I'm thinking I can possibly pick up another drive or two and compy the exisiting drives while they are still working.
10 More Discussions You Might Find Interesting
1. AIX
Hi,
Other than df -k, is there any command that will tell me all physical hard drives installed on the system as well as the size of each one?
I'm using AIX 5.1
Thanks, (3 Replies)
Discussion started by: quickfirststep
3 Replies
2. UNIX for Dummies Questions & Answers
Hi,
I work in a production support environment. All our PROD machines SPARC machines and Solaris O/S. I want to know how to find out what the hard disk size, RAM size etc. of our PROD machines. Please let me know if there is any way to find out this (other than from system administrator).
... (2 Replies)
Discussion started by: ramaraju
2 Replies
3. UNIX Desktop Questions & Answers
I have a cuestion. How Can I to add other hard disk to my computer? I need to configurate anyone? (4 Replies)
Discussion started by: hmaraver
4 Replies
4. AIX
hi,
AIX 5.3
For any command(say tar command) I am getting 100% busy for my hdisk.
But my CPU and Memory is not busy and have more idle also.
Please advice for any performance analysing.
Thanks in Advance, (3 Replies)
Discussion started by: npcrao
3 Replies
5. UNIX for Dummies Questions & Answers
:eek: I use this Solaris to run CMS a call acounting software package for my job. No one could run reports today because it said the this when you logged on
"The following file systems are low, and could adversely affect server performance:
File system /: 99%full"
Can some one please explain... (9 Replies)
Discussion started by: mannyisme
9 Replies
6. SCO
hi
I've a fresh installation of SCO 5.0.7 on the IDE hard disk.
For SCSI hard disk I can declare, for example blc disk driver using:
# mkdev hd 0 SCSI-0 0 blc 0but it works for IDE hard disk? (3 Replies)
Discussion started by: ccc
3 Replies
7. Red Hat
When we write a programme,we declare variables and compiler allocates memory to them.I want to get access to the physical block number of hard-disk where actually the data is stored by the programme "
Some one help me out... (1 Reply)
Discussion started by: nagraz007
1 Replies
8. Linux
Hi all,
I'm kind of new to programming in Linux & c/c++. I'm currently writing a FileManager using Ubuntu Linux(10.10) for Learning Purposes. I've got started on this project by creating a loopback device to be used as my virtual hard disk. After creating the loop back hard disk and mounting it... (23 Replies)
Discussion started by: shen747
23 Replies
9. Solaris
While getting the total disk space in solaris machine using df -k command, i am getting the same disk info for every user available in that system.
Is there any way to remove it.
Filesystem 1024-blocks Used Available Capacity Mounted on
rpool/ROOT/solaris 573898752... (3 Replies)
Discussion started by: prasankn
3 Replies
10. AIX
Please help with command to check the busy % for a hard disk device like hdisk5
Best regards,
Vishal (7 Replies)
Discussion started by: Vishal_dba
7 Replies
HP(4) Kernel Interfaces Manual HP(4)
NAME
hp - RH-11/RP04, RP05, RP06 moving-head disk
DESCRIPTION
The octal representation of the minor device number is encoded idp, where i is an interleave flag, d is a physical drive number, and p is a
pseudodrive (subsection) within a physical unit. If i is 0, the origins and sizes of the pseudodisks on each drive, counted in cylinders
of 418 512-byte blocks, are:
disk start length
0 0 23
1 23 21
2 0 0
3 0 0
4 44 386
5 430 385
6 44 367
7 44 771
If i is 1, the minor device consists of the specified pseudodisk on drives numbered 0 through the designated drive number. Successively
numbered blocks are distributed across the drives in rotation.
Systems distributed for these devices use disk 0 for the root, disk 1 for swapping, and disk 4 (RP04/5) or disk 7 (RP06) for a mounted user
file system.
The block files access the disk via the system's normal buffering mechanism and may be read and written without regard to physical disk
records.
A `raw' interface provides for direct transmission between the disk and the user's read or write buffer. A single read or write call
results in exactly one I/O operation and therefore raw I/O is considerably more efficient when many words are transmitted. The names of
the raw files conventionally begin with an extra `r.' In raw I/O the buffer must begin on a word boundary, and raw I/O to an interleaved
device is likely to have disappointing results.
FILES
/dev/rp?, /dev/rrp?
SEE ALSO
rp(4)
BUGS
In raw I/O read and write(2) truncate file offsets to 512-byte block boundaries, and write scribbles on the tail of incomplete blocks.
Thus, in programs that are likely to access raw devices, read, write and lseek(2) should always deal in 512-byte multiples.
Raw device drivers don't work on interleaved devices.
HP(4)