Not able to remove device file for internal removed disk.

[Kavita Poonia]

Hello All,

I am not able to remove device file of an already re-claimed internal disk on 11iv3.

#rmsf -H 64000/0xfa00/0x19e
Device at 64000/0xfa00/0x19e is busy. Cannot remove.

#rmsf /dev/disk/disk9552
Device /dev/disk/disk9552 is busy. Cannot remove.

Thanks & regards,
Kavita

[Turgay Cavdar]

Hi,
Are you sure this device is not used? If the device is in open state then you can't delete it.

Regards.

[Kavita Poonia]

Yes, its not in use.

[sarfaraj ahmad]

hi,

please put ioscan and ioscan -fnC disk output.

[Manix]

>>an already re-claimed internal disk on 11iv3

was there any disk replacement ? if so in 11iv3 was it done on the same HW path or there was any change.

If this is not in use at all than try

Unbind a driver associated with a node corresponding to the hardware

rmsf -u -H 64000/0xfa00/0x6

Then remove with Critical Resource Analysis (CRA) report.

rmsf -c -H 64000/0xfa00/0x6

[Kavita Poonia]

Manix,

Yes there was a replacement for the faulted disk on this device path, after replacement new device path generated for replaced disk & this old path remained so we tried to remove it but not ablt to.


cmihx002:/root# rmsf -u -H 64000/0xfa00/0x19e
rmsf: The given device doesn't support driver unbinding feature


Also rmsf -c -H 64000/0xfa00/0x19e, is not coming up with anything as it just hangs.

Thanks & regards,
Kavita

[Torsten.]

Is this is SAS disk?


Did you follow the procedure for SAS disk replacements?

Maybe not.


Did you do the "pvchange -a n ..." command?

[Kavita Poonia]

Yes, we did....can you give us the procedure you have for SAS disk replacement ?

[Turgay Cavdar]

Can you post ?
# scsimgr get_info -D /dev/rdisk/disk9552
# vgdisplay -v vg_name

[Torsten. · Accepted solution]

Such a sas disk always get a new device file, because it is another disk with another identifier.

After doing "pvchange -a n ..." and swap the disk, do

# sasmgr replace_tgt -D /dev/sasd0 -q old_dev=/dev/dsk/c1t4d0 -q new_tgt_hwpath=0/4/1/0.0.0.11.0


(with your own values!) to redirect the old device file to the new disk.


Then do the procedures as usual...