Sponsored Content
Full Discussion: hdds physically
Operating Systems HP-UX hdds physically Post 302071568 by Perderabo on Friday 21st of April 2006 05:08:32 PM
Old 04-21-2006
Then use dd to read the whole thing and see if that works.
 

4 More Discussions You Might Find Interesting

1. Solaris

How to check if rsc is physically exist

I have a bunch of servers that cant connect via rsc, but supposingly they can connect... Any chance I can check if the rsc card is physically exist in the server by some command? Some of the machines are in overseas, and I won't go datacenter to check anyways... Many Thanks! (6 Replies)
Discussion started by: nicole0404
6 Replies

2. Solaris

Physically identify hard disk.

Hi, I have a failed hard disk in my Sun Fire V240. Unfortunately it does not show up in 'cfgadm -al' or in the format command so I cannot unconfigure it and illuminate the blue light on the front to identify it. Is there any way of iluminating the blue lights on the other disks so I can at... (3 Replies)
Discussion started by: sparcman
3 Replies

3. Solaris

SPARC T4-1/Solaris 11/Add 2 new HDDs in RAID 0 configuration

Hi, Couple of sentences for background: I'm a software developer, whose task was to create a server software for our customer. Software is ready for deployment and customer has a new T4-1 SPARC, but somehow it also became my task also to setup the server. I have managed to get the server is up... (13 Replies)
Discussion started by: julumme
13 Replies

4. AIX

IBM AIX 5.2 cloning Hdds

I have an old IBM Power 5 9111-520 that has data on it but the system is failing. I need to move it to a more reliable server. The current system has two drives and no raid. I would like to setup my "newer" system with raid and two partitions then clone my setup over. What is the best way to do... (2 Replies)
Discussion started by: BDC80
2 Replies
FD(4)							     Kernel Interfaces Manual							     FD(4)

NAME
fd - floppy disk DESCRIPTION
The fd* devices refer to the Floppy disk driver using the NEC PD765 floppy disk controller. These diskettes are arrays of 512 byte sec- tors, although Minix always works with two sectors at a time due to its 1024 byte block size. You can read or write any number of bytes however, Minix takes care of cutting and pasting incomplete blocks together. The driver is normally configured for two floppy disk devices fd0 and fd1. It can handle two more, but it is unlikely that the average PC can. On the first access to an fd device (by open(2) or mount(2)), the driver will execute a series of read tests to determine the floppy type. This works ok for all floppy types except the true 360k type, because it is indistinguishable from the 720k type. This only means that the size of the floppy is not estimated right. Bits 2-6 of the minor device number may be set to the floppy disk type to make it known to the driver what type of diskette it is reading or writing. The non-auto devices should be used for formatting, or when one wants to be absolutely sure that the device is accessed right. These devices exist for drive 0: type device minor media 0 fd0 0 autodetect 1 pc0 4 360k, 5.25" 2 at0 8 1.2M, 5.25" 3 qd0 12 360k in a 720k, 5.25" drive 4 ps0 16 720k, 3.5" 5 pat0 20 360k in a 1.2M, 5.25" drive 6 qh0 24 720k in a 1.2M, 5.25" drive 7 PS0 28 1.44M, 3.5" Type 4 may also be used for the rarely seen 720k, 5.25" floppies (type 2 made them obsolete fast.) Note that these "types" only describe the floppies from a software point of view, type 1 and 4 drives use the same parameters. If the format bit (bit 7) is set, then the driver interprets write commands as track formatting requests. This is used by the format(1) command. If the type bits are set to 28, 29, 30, or 31, then the driver uses a partition table found in sector 0 to partition the floppy. The par- titions of fd0 may be accessed as fd0a through fd0d. See hd(4) for a description of the partition table, and associated ioctl commands. FILES
/dev/fd[0-3], /dev/pc[0-3], /dev/at[0-3], /dev/qd[0-3], /dev/ps[0-3], /dev/pat[0-3], /dev/qh[0-3], /dev/PS[0-3], /dev/fd[0-3][a-d] SEE ALSO
format(1), hd(4), part(8). BUGS
The driver does not know the size of a 360k diskette in a 360k 5.25" drive, because it uses the 720k parameters for it. So it will happily try to read past the end making all kinds of interesting noises. It's a good thing these drives are practically obsolete. The partition table is only read when the drive motor is off and only for an auto or partition device. The driver assumes that a floppy in a drive with a running motor can't have been replaced all of a sudden. AUTHOR
Kees J. Bot (kjb@cs.vu.nl) FD(4)
All times are GMT -4. The time now is 07:30 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy