Login or Register to Ask a Question and Join Our Community


Solaris

Lun remove, stuck in /dev/dsk and /dev/rdsk

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems Solaris Lun remove, stuck in /dev/dsk and /dev/rdsk
# 1  
Old 04-30-2013
Lun remove, stuck in /dev/dsk and /dev/rdsk
So, we removed a LUN from the SAN and the system is refusing to remove the references to it in the /dev folder. I've done the following:

devfsadm -Cv
powermt -q
luxadm -e offline <drive path>
luxadm probe

All those commands failed to remove the path. The drive stills shows up as <drive type unknown> using the format command. Any ideas?

---------- Post updated at 07:47 AM ---------- Previous update was at 07:21 AM ----------

Oh, I forgot to add I've reboot --r too. Here's some ouput that show more info on the error and steps I've taken.

Code:
bash-3.2# cfgadm -a -o show_SCSI_LUN
Ap_Id                          Type         Receptacle   Occupant     Condition
c1                             fc           connected    unconfigured unknown
c2                             fc-fabric    connected    configured   unknown
c2::500601623ce01998,0         disk         connected    configured   unknown
c2::500601623ce01998,1         disk         connected    configured   unknown
c2::500601623ce01998,2         disk         connected    configured   unknown
c2::5006016a3ce01998,0         disk         connected    configured   unknown
c2::5006016a3ce01998,1         disk         connected    configured   unknown
c2::5006016a3ce01998,2         disk         connected    configured   unknown
bash-3.2# echo|format
Searching for disks...done


AVAILABLE DISK SELECTIONS:
       0. c0t0d0 <SUN80G cyl 65533 alt 2 hd 16 sec 149>
          /pci@7c0/pci@0/pci@8/scsi@2/sd@0,0
       1. c2t5006016A3CE01998d0 <drive type unknown>
          /pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w5006016a3ce01998,0
       2. c2t5006016A3CE01998d1 <DGC-RAID5-0429 cyl 40958 alt 2 hd 256 sec 10>
          /pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w5006016a3ce01998,1
       3. c2t5006016A3CE01998d2 <DGC-RAID5-0429 cyl 51198 alt 2 hd 256 sec 16>  new_lun
          /pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w5006016a3ce01998,2
       4. c2t500601623CE01998d0 <drive type unknown>
          /pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w500601623ce01998,0
       5. c2t500601623CE01998d1 <DGC-RAID5-0429 cyl 40958 alt 2 hd 256 sec 10>
          /pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w500601623ce01998,1
       6. c2t500601623CE01998d2 <DGC-RAID5-0429 cyl 51198 alt 2 hd 256 sec 16>  new_lun
          /pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w500601623ce01998,2
       7. emcpower0e <DGC-RAID5-0429 cyl 40958 alt 2 hd 256 sec 10>
          /pseudo/emcp@0
       8. emcpower2d <DGC-RAID5-0429 cyl 51198 alt 2 hd 256 sec 16>  new_lun
          /pseudo/emcp@2
Specify disk (enter its number): Specify disk (enter its number):
bash-3.2# cfgadm -c unconfigure -o unusable_SCSI_LUN c2::5006016A3CE01998d0
bash-3.2# cfgadm -c unconfigure -o unusable_SCSI_LUN c2::500601623CE01998d0
bash-3.2# luxadm probe
No Network Array enclosures found in /dev/es

Found Fibre Channel device(s):
  Node WWN:50060160bce01998  Device Type:Disk device
    Logical Path:/dev/rdsk/c2t5006016A3CE01998d0s2
    Logical Path:/dev/rdsk/c2t500601623CE01998d0s2
  Node WWN:50060160bce01998  Device Type:Disk device
    Logical Path:/dev/rdsk/c2t5006016A3CE01998d1s2
    Logical Path:/dev/rdsk/c2t500601623CE01998d1s2
  Node WWN:50060160bce01998  Device Type:Disk device
    Logical Path:/dev/rdsk/c2t5006016A3CE01998d2s2
    Logical Path:/dev/rdsk/c2t500601623CE01998d2s2
bash-3.2# devfsadm -Cv

# 2  
Old 04-30-2013
This may be a silly question but since you know which 'device' it is, why don't you manually remove the device node yourself from /dev/rdsk, /dev/dsk and /dev/cfg?

If it won't let you do that with the system up, take it down, boot from CD, mount the HD root filesystem under /a, and get in there and do it.

Or am I missing something here?

Why do you necessarily need to get rid of it anyway?
Last edited by hicksd8; 04-30-2013 at 09:01 AM..
This User Gave Thanks to hicksd8 For This Post:
DustinT
# 3  
Old 04-30-2013
No, it's probably not a silly question. But, mucking about inside /dev isn't something I'm willing to do with my current skills. It needs to be removed because we had to make some changes on our storage and that LUN is no longer available. Now I just need to convince the server to just let it go. Smilie

---------- Post updated at 08:08 AM ---------- Previous update was at 07:58 AM ----------

Quote:
Originally Posted by hicksd8
This may be a silly question but since you know which 'device' it is, why don't you manually remove the device node yourself from /dev/rdsk, /dev/dsk and /dev/cfg?

If it won't let you do that with the system up, take it down, boot from CD, mount the HD root filesystem under /a, and get in there and do it.

Or am I missing something here?

Why do you necessarily need to get rid of it anyway?
Well.... I decided to delete the /dev/dsk and /dev/rdsk references. While booted into single user mode, it worked with no problem. But, when I ran a devfsadm -Cv it recreated all the references. Smilie

Code:
bash-3.2# devfsadm -Cv
devfsadm[1365]: verbose: symlink /dev/dsk/c2t500601623CE01998d0s0 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w500601623ce01998,0:                      a
devfsadm[1365]: verbose: symlink /dev/dsk/c2t500601623CE01998d0s1 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w500601623ce01998,0:                      b
devfsadm[1365]: verbose: symlink /dev/dsk/c2t500601623CE01998d0s2 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w500601623ce01998,0:                      c
devfsadm[1365]: verbose: symlink /dev/dsk/c2t500601623CE01998d0s3 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w500601623ce01998,0:                      d
devfsadm[1365]: verbose: symlink /dev/dsk/c2t500601623CE01998d0s4 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w500601623ce01998,0:                      e
devfsadm[1365]: verbose: symlink /dev/dsk/c2t500601623CE01998d0s5 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w500601623ce01998,0:                      f
devfsadm[1365]: verbose: symlink /dev/dsk/c2t500601623CE01998d0s6 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w500601623ce01998,0:                      g
devfsadm[1365]: verbose: symlink /dev/dsk/c2t500601623CE01998d0s7 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w500601623ce01998,0:                      h
devfsadm[1365]: verbose: symlink /dev/rdsk/c2t500601623CE01998d0s0 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w500601623ce01998,0                      :a,raw
devfsadm[1365]: verbose: symlink /dev/rdsk/c2t500601623CE01998d0s1 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w500601623ce01998,0                      :b,raw
devfsadm[1365]: verbose: symlink /dev/rdsk/c2t500601623CE01998d0s2 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w500601623ce01998,0                      :c,raw
devfsadm[1365]: verbose: symlink /dev/rdsk/c2t500601623CE01998d0s3 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w500601623ce01998,0                      :d,raw
devfsadm[1365]: verbose: symlink /dev/rdsk/c2t500601623CE01998d0s4 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w500601623ce01998,0                      :e,raw
devfsadm[1365]: verbose: symlink /dev/rdsk/c2t500601623CE01998d0s5 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w500601623ce01998,0                      :f,raw
devfsadm[1365]: verbose: symlink /dev/rdsk/c2t500601623CE01998d0s6 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w500601623ce01998,0                      :g,raw
devfsadm[1365]: verbose: symlink /dev/rdsk/c2t500601623CE01998d0s7 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w500601623ce01998,0                      :h,raw
devfsadm[1365]: verbose: symlink /dev/dsk/c2t5006016A3CE01998d0s0 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w5006016a3ce01998,0:                      a
devfsadm[1365]: verbose: symlink /dev/dsk/c2t5006016A3CE01998d0s1 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w5006016a3ce01998,0:                      b
devfsadm[1365]: verbose: symlink /dev/dsk/c2t5006016A3CE01998d0s2 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w5006016a3ce01998,0:                      c
devfsadm[1365]: verbose: symlink /dev/dsk/c2t5006016A3CE01998d0s3 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w5006016a3ce01998,0:                      d
devfsadm[1365]: verbose: symlink /dev/dsk/c2t5006016A3CE01998d0s4 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w5006016a3ce01998,0:                      e
devfsadm[1365]: verbose: symlink /dev/dsk/c2t5006016A3CE01998d0s5 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w5006016a3ce01998,0:                      f
devfsadm[1365]: verbose: symlink /dev/dsk/c2t5006016A3CE01998d0s6 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w5006016a3ce01998,0:                      g
devfsadm[1365]: verbose: symlink /dev/dsk/c2t5006016A3CE01998d0s7 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w5006016a3ce01998,0:                      h
devfsadm[1365]: verbose: symlink /dev/rdsk/c2t5006016A3CE01998d0s0 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w5006016a3ce01998,0                      :a,raw
devfsadm[1365]: verbose: symlink /dev/rdsk/c2t5006016A3CE01998d0s1 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w5006016a3ce01998,0                      :b,raw
devfsadm[1365]: verbose: symlink /dev/rdsk/c2t5006016A3CE01998d0s2 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w5006016a3ce01998,0                      :c,raw
devfsadm[1365]: verbose: symlink /dev/rdsk/c2t5006016A3CE01998d0s3 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w5006016a3ce01998,0                      :d,raw
devfsadm[1365]: verbose: symlink /dev/rdsk/c2t5006016A3CE01998d0s4 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w5006016a3ce01998,0                      :e,raw
devfsadm[1365]: verbose: symlink /dev/rdsk/c2t5006016A3CE01998d0s5 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w5006016a3ce01998,0                      :f,raw
devfsadm[1365]: verbose: symlink /dev/rdsk/c2t5006016A3CE01998d0s6 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w5006016a3ce01998,0                      :g,raw
devfsadm[1365]: verbose: symlink /dev/rdsk/c2t5006016A3CE01998d0s7 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0/ssd@w5006016a3ce01998,0                      :h,raw

---------- Post updated at 08:09 AM ---------- Previous update was at 08:08 AM ----------

So, the driver that providing the 'ssd' support appears to be stuck in a loop where it's refusing to let go of the old references??
# 4  
Old 04-30-2013
As per my post, you need to remove from /dev/cfg too.

You need to remove the device node from all three directories.

You may need to use 'rm -f' if it won't go.
This User Gave Thanks to hicksd8 For This Post:
DustinT
# 5  
Old 04-30-2013
under /dev/cfg I have the following

Code:
bash-3.2# ls
c0  c1  c2
bash-3.2# cat c2
cat: input error on c2: No such device or address
bash-3.2# cd c2
bash: cd: c2: Not a directory

I have other LUNS off of c2 that I don't want to lose. How do I go about removing that reference since c2 isn't a file I can edit??

---------- Post updated at 08:13 AM ---------- Previous update was at 08:12 AM ----------

Code:
bash-3.2# ls -l /dev/cfg
total 3
lrwxrwxrwx   1 root     root          45 Nov 30  2010 c0 -> ../../devices/pci@7c0/pci@0/pci@8/scsi@2:scsi
lrwxrwxrwx   1 root     root          42 Apr  5  2011 c1 -> ../../devices/pci@780/SUNW,qlc@0/fp@0,0:fc
lrwxrwxrwx   1 root     root          44 Apr  5  2011 c2 -> ../../devices/pci@780/SUNW,qlc@0,1/fp@0,0:fc

# 6  
Old 04-30-2013
If you have other LUN's on c2 then you'll need to (in single user)

Code:
rm -r /a/dev/cfg/c2

then

Code:
devfsadm -r /a -p /a/etc/path_to_inst

to write the devices you still need back.

Remember to check that /a/etc/vfstab is correct and not trying to mount something which isn't there any more.
This User Gave Thanks to hicksd8 For This Post:
DustinT
# 7  
Old 04-30-2013
I'm trying a modified version of this.

rm /dev/dsk/<path>
rm /dev/rdsk/<path>
rm /dev/cfg/c2
devfsadm -r /a -p /etc/path_to_inst
reboot -- -r
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Canīt open /dev/dsk/c1t0d0s0 Clone/mirror

Hello friends, I Working with Solaris 8 on a SunFireV890, 150 GB SCSI HD's in Raid 1 (mirroring), my problem is that the master disk failed and going to put the slave (mirror) as a Master in the slot 0 (SCSI) will not start. The original mounting this, mirror in Raid 0: c1t0d0s0 (master)... (10 Replies)
Discussion started by: grymorum
10 Replies

2. Solaris

Size missing on /dev/dsk/c0t0d0s3

Our used size is 83 gb. Total of the folders and documents size is46,2 gb. 83-46=37 gb. Where is my space. Where was lost? Could you please I need your opinions? {root}/space>du -s -h * 308K alaerrm-jprof 1K argerela 20G baerckup_in 1.8G cererm 28M ecerlipselink ... (8 Replies)
Discussion started by: getrue
8 Replies

3. Solaris

how to make less capacity /dev/dsk/c1t0d0s5

how to make less capacity on /dev/dsk/c1t0d0s5 Filesystem size used avail capacity Mounted on /dev/dsk/c1t0d0s0 9.6G 2.3G 7.2G 25% / /dev/dsk/c1t0d0s1 9.6G 4.1G 5.4G 44% /usr /dev/dsk/c1t0d0s4 9.6G 81M 9.4G 1% /var... (1 Reply)
Discussion started by: Cah.Lanang
1 Replies

4. UNIX for Dummies Questions & Answers

Meaning of mount /dev/dsk/c... /mnt

Hi May I know the meaning of the following command mount /dev/dsk/c1t0d0s3 /mnt Will I be able to use my tape drive after that? Thanks (3 Replies)
Discussion started by: rahmantanko
3 Replies

5. Solaris

jumpstart Can't stat /dev/rdsk/c1t0d0s0 eror

I installed solaris 9u8 and flar image and put on my jumpstart server which is running 10u3. Then I do jumpstart with new image with same hardware. Jumpstart acts like it installs, configures, and looks generally good. However, During the boot process, it reports the following errors. The / file... (4 Replies)
Discussion started by: rushingfish
4 Replies

6. Solaris

How do I determine the hard drives in /dev/dsk in OpenSolaris?

I have a Solaris machine running OpenSolaris v5.11. It came with a hard drive. It's called /dev/dsk/c4d0s0. I added two new hard drives into the box. I can't figure out what it's called in /dev/dsk. There are 210 filenames in /dev/dsk. How do I find out which filename corresponds to the... (2 Replies)
Discussion started by: sqa777
2 Replies

7. Solaris

anyone can tell me what is /dev/dsk/c3t600A0B80002FA5F50000000000000000d0s0?

Hi all, I just find some strange device (at least to me) on my Sun Blade server, CP3060, like below: bash-3.00# cd /dev/dsk bash-3.00# ls c3* c3t600A0B80002FA5F50000000000000000d0s0 c3t600A0B80002FA60C0000000000000000d0s4 c3t600A0B80002FA5F50000000000000000d0s1 ... (6 Replies)
Discussion started by: sleepy_11
6 Replies

8. Solaris

pls help - /dev/dsk 100% full

I use the following command dk -k and get the following output: Filesystem kbytes used avail capacity Mounted on /dev/dsk/c0t0d0s0 1587078 56546 1482920 4% / /dev/dsk/c0t0d0s6 1984230 926199 998505 49% /usr /proc 0 0 0 ... (1 Reply)
Discussion started by: indianboy08
1 Replies

9. Solaris

mount: /dev/dsk/c0t6d0s0 no such device

I've searched through unix.com and google for this issue I am having on one particular Sun E280R with installing netbackup software from CD. I know the cd is good because i installed the software on 4 other servers right before this one. This is the issue I am seeing. vold does not mount the CD... (2 Replies)
Discussion started by: dangral
2 Replies

10. UNIX for Dummies Questions & Answers

sar + sdXY,Z + /dev/dsk

Hello! When I use "sar -d" I get information about disk activities like: sd0 ... sd0,a ... sd0,b ... ..... sd22 ... sd22,a ... ..... How I can find by , for example sd22,a , what physical disk is it. For example /dev/dsk/c1t3d0s1 easy to read and I can find by it physical disk.... (4 Replies)
Discussion started by: Colf
4 Replies
Login or Register to Ask a Question