When calling luxadm remove_device /dev/rdsk/c1t1d0s2, the system asks for confirmation and reports that the disk is spinning down and being taken offline. When the disk is removed, pressing Return causes the system to report that the device links are removed.
However, the device links are not removed. The disk can then be re-inserted and used without running the luxadm insert_device command. When the command is subsequently run, the system reports that no new devices were added and the following message is produced at the console:
bash-2.03# luxadm remove_device /dev/rdsk/c1t1d0s2
WARNING!!! Please ensure that no filesystems are mounted on these device(s). All data on these devices should have been backed up.
The list of devices which will be removed is: 1: Device name: /dev/rdsk/c1t1d0s2 Node WWN: 2000002037e367e4 Device Type:Disk device Device Paths: /dev/rdsk/c1t1d0s2
Please verify the above list of devices and then enter 'c' or <CR> to Continue or 'q' to Quit. [Default: c]: stopping: /dev/rdsk/c1t1d0s2....Done offlining: /dev/rdsk/c1t1d0s2....Done
Hit <Return> after removing the device(s)
Device: /dev/rdsk/c1t1d0s2 Logical Nodes being removed under /dev/dsk/ and /dev/rdsk: c1t1d0s0 c1t1d0s1 c1t1d0s2 c1t1d0s3 c1t1d0s4 c1t1d0s5 c1t1d0s6 c1t1d0s7
Device: /dev/rdsk/c1t1d0s2 Logical Nodes being removed under /dev/dsk/ and /dev/rdsk: c1t1d0s0 c1t1d0s1 c1t1d0s2 c1t1d0s3 c1t1d0s4 c1t1d0s5 c1t1d0s6 c1t1d0s7
bash-2.03# ls -l /dev/dsk/c1t1* lrwxrwxrwx 1 root root 70 May 4 19:07 /dev/dsk/c1t1d0s0 -> ../../devices/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w2100002037e367e4,0:a |
lrwxrwxrwx 1 root root 70 May 4 19:07 /dev/dsk/c1t1d0s1 -> ../../devices/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w2100002037e367e4,0:b
bash-2.03# ls -l /dev/rdsk/c1t1* lrwxrwxrwx 1 root root 74 May 4 19:07 /dev/rdsk/c1t1d0s0 -> ../../devices/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w2100002037e367e4,0:a,raw lrwxrwxrwx 1 root root 74 May 4 19:07 /dev/rdsk/c1t1d0s7 -> ../../devices/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w2100002037e367e4,0:h,raw . . /* the following errors are caused by SUNWvts reprobe looking for said disk */
bash-2.03# 8012 05/22/01 14:05:07 Failed on iotcl DKIOCGMEDIAINFO: 6: No such device or address
8012 05/22/01 14:05:41 Failed on iotcl DKIOCGMEDIAINFO: 6: No such device or address
8012 05/22/01 14:07:25 Failed on iotcl DKIOCGMEDIAINFO: 6: No such device or address
bash-2.03# luxadm insert_device Please hit <RETURN> when you have finished adding Fibre Channel Enclosure(s)/Device(s):
Waiting for Loop Initialization to complete... No new device(s) were added!!
|
To work around, enter the following when luxadm remove_device claims to have completed successfully:
# devfsadm -C -c disk |
If four USB Iomega zip drives are attached, prtconf indicates that no driver is loaded after the system has booted. drvconf starts a system probe that finds only two of the four USB zip drives.
Running cat on the /dev/usb/hub0 file causes the system to add the two zip drives.
Workaround: Do not use more than two zip drives in the current release.
The LOMlite2 reset-x command does not currently reset the CPUs. Look for this functionality in a later revision of the OpenBoot PROM.