insf -H ?

[Idham]

What is the proper command to install back hard drive using the "-H"...
#insf -H ...use to be registered /dev/rdsk/c3t0d0.

fyi,

Before this the disk system have 4 disk. Somehow one of the 1st disk failed & I'm replacing it with a new disk. If I run insf -e will change the raw device permission and will affect the other 3 devices which registered in oracle raw devices (ASM)

disk 8 0/1/1/1.2.0 sdisk CLAIMED DEVICE HP 146 GMAU3147NC
/dev/dsk/c3t2d0 /dev/rdsk/c3t2d0
disk 9 0/1/1/1.4.0 sdisk CLAIMED DEVICE HP 146 GMAU3147NC
/dev/dsk/c3t4d0 /dev/rdsk/c3t4d0
disk 10 0/1/1/1.6.0 sdisk CLAIMED DEVICE HP 146 GMAU3147NC
/dev/dsk/c3t6d0 /dev/rdsk/c3t6d0

[Jeeshan]

#insf -eH 0/1/1/1.2.0

[Idham]

I dont think so...
the path already registered for "disk 8"

[Jeeshan]

if you run insf -e, the system reinstall the disk driver. as well as the permission will also reset. this is obvious.

whenever you assign back the faulty disk with the new one , it will create separate disk.

[Duncan Edmonstone]

So can you see the new disk in:

ioscan -f

You should just see the hardware path there.

To get around the insf problem you describe, when using ASM I always create my own set of disk devices using mknod.

Use ll /dev/rdsk/*

to get the major and minor numbers the disks you're interested in then:

mkdir /asm
mknod /asm/asmdisk1 c
chown oracle:dba /asm/asmdisk1

replacinging and with what you got from the ll command. Repeating for all your oracle disks.

Now within your ASM instance set ASM_DISKSTRING to "/asm/asmdisk*" and you're good to go.

Now whenever someone runs insf -e, it won't touch these new disk devices you created. Of course you'll need to go through the same process every time you add a new disk.

HTH

Duncan

[sujit kumar singh]

hi


u can easily do the following in ur case.

yes the insf -e -C disk and the insf -e H shall reinstall the DSF with the original ownership which shalll be like bin:sys

instead whatu can do like is note the HW path of the disk and do an

#insf -e -H
and do change the ownerships of the Dev files accordingly both raw and blocks as might be reqd.

but the device files would be there in place if u might not have remove them by a previous rmsf of rm

Reggards
sujit