01-29-2014
The RAID controller only looks at raw storage. It doesn't know anything about format, partition types, or filesystems. In rebuilding the mirror it will simply copy sector 0 to sector0, sector 1 to sector 1, thru' sector n to sector n. It doesn't give a stuff what's on the new drive is sees.
Historically, there used to be less able RAID controllers which looked for empty drives ie, expecting no format or partition table. For this reason, if I had to test a recycled drive prior to using it, I'll blow any partition table away before disconnecting from my test rig (to make it look empty) but this is really no longer necessary. Your RAID controller is a LSI and they're extremely good. It will just take care of everything.
Since your problem drive is marked "failed" by the controller, it won't even be trying to talk to it any more so it won't be flashing when the system is I/O'ing. That should tell you which drive to pull.
Don't be surprised if pulling out the drive and reinserting it starts the rebuild. After months/years of operation a poor connection can develop which is cured by reseating. If that doesn't work insert a replacement with the same or greater LBA's.
10 More Discussions You Might Find Interesting
1. AIX
My root disk is failed and how to replace the root disk in AIX.
Can u give a detailed explanation in step wise.
Pls give the answer taking different scenarios.
Regards
Praveen (1 Reply)
Discussion started by: chinnu_mulakala
1 Replies
2. Solaris
Hi All,
I have new Netra 240 box which is not detecting its harddisk equiped with itse same har disk are detected when I swap with another machine.
Same time If I swap hardisk of other machine to this Netra 240 box, also do not work. I have checked chassis, cabling etc and all looks fine. ... (1 Reply)
Discussion started by: xpwistler
1 Replies
3. Shell Programming and Scripting
Hi,
I am trying to write a shell script designed to take input line by line by line from a file with a word on each line for editing with sed. Example file:
1.ejverything
2.bllown
3.maikling
4.manegement
5.existjing
6.systems
My design currently takes input from the user, and... (2 Replies)
Discussion started by: mkfitzwilliams
2 Replies
4. Solaris
Hello,
I wrote a script which monitor the keyswitch state repeatedly each 10 minutes.
I'm extracting the keyswitch status by using prtdiag.
The script works fine for Netra v440 , but I found that prtdiag under Netra 1290 don't give keyswitch status.
unlike Netra 440 server , I found that... (2 Replies)
Discussion started by: Alalush
2 Replies
5. Solaris
I got two 2.5" disk for a x4200 and put it in.
Just same these disk were, I remember doing this in the past, working..
Now when I put in the disk and run 'devfsadm' and also check with 'cfgadm -a', that disk doesn't seem to show up.
When I pull out the disk I see this in the logs:
Mar... (15 Replies)
Discussion started by: madvikas
15 Replies
6. UNIX for Advanced & Expert Users
Hello All
I have always had a question about find and replace in Vi. As this uses Vi, sed, and RegEx I never knew how or where to post the question but I thought I would give it a shot here. Say I have a text file filled with the following:
Sue, your IP address is 192.168.1.10 which is... (4 Replies)
Discussion started by: NoSalt
4 Replies
7. Solaris
Hi all
I wish to mirror for the root disk, but last time i do, make the server cannot boot up. :p So this time, hope you guys can assist me on it. =)
At the last code, is the step i wish to do. Please help to check and correct me if got any wrong.
root@leo # format </dev/null
Searching for... (17 Replies)
Discussion started by: SmartAntz
17 Replies
8. Solaris
Hi All
Hope it's okay to post on this sub-forum, couldn't find a better place
I've got a 480R running solaris 8 with veritas volume manager managing all filesystems, including an encapsulated root disk (I believe the root disk is encapsulated as one of the root mirror disks has an entry under... (1 Reply)
Discussion started by: sunnyd76
1 Replies
9. Hardware
Hello,
I have a spare SUN server X4200 with a DC PSU (oracle part number 300-2186)
The PSU is the one in the photo
I was looking in the net about what cable i can order but i couldn't find anything that fit there :)
Any idea?
Thanks! (2 Replies)
Discussion started by: @dagio
2 Replies
10. Solaris
Hi Guys,
Could someone please share the dvd/cd that came with server Netra x4200 M2 since it is not more available in Oracle site? Or do you know where I can get that?
Thanks! (4 Replies)
Discussion started by: CristianS
4 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)