HP9000 - /dev/dsk/c1t2d0: Device busy

[Karl Haynes]

I have an HP9000/D350. I have been unable to use the CDROM drive. I tried to mount the CDROM drive and associate with /cdrom but got the following error message:

# mount /dev/dsk/c1t2d0 /cdrom
/dev/dsk/c1t2d0: Device busy

I am pointing to the correct device. Did you test to make sure that the CD-ROM could mount ? Is there somethinh that I am missing ? I have tried checking patches (ONe 27225 - which is only for 64-bit systems....mine is a 32-bit system), user groups...but to no avail.

# ioscan -fn -C disk
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
disk 0 8/4.5.0 sdisk CLAIMED DEVICE SEAGATE ST34371W
/dev/dsk/c0t5d0 /dev/rdsk/c0t5d0
disk 1 8/4.8.0 sdisk CLAIMED DEVICE SEAGATE ST34572WC
/dev/dsk/c0t8d0 /dev/rdsk/c0t8d0
disk 2 8/16/5.2.0 sdisk CLAIMED DEVICE TOSHIBA CD-ROM XM-5401T
A
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0

[Bill Hassell · Accepted solution]

Start with the basics (put an HP-UX CD in the drive first):

diskinfo /dev/rdsk/c1t2d0

(Note the use of /dev/rdsk, not /dev/dsk) Should look something like this:

SCSI describe of /dev/rdsk/c1t2d0:
vendor: TOSHIBA
product id: CD-ROM XM-5401TA
type: CD-ROM
size: 302628 Kbytes
bytes per sector: 2048

That means that the drive is working at the hardware level (SCSI describe command works OK).

Check to see if the device files are truly busy with fuser:

fuser /dev/rdsk/c1t2d0
fuser /dev/dsk/c1t2d0

There should be no process ID's shown. If there are, then the listed process(es) caused the problem.

Now try to read some data:

dd if=/dev/rdsk/c1t2d0 of=/dev/null bs=2048

Then type CTRL-C after a few seconds and you'll see something like this:

523+0 records in
523+0 records out

which means that the drive is working OK. If either of the previous tests fail, then you likely have a drive problem.

Check that /cdrom is not busy:

fuser /cdrom

Any processes listed will cause the mountpoint to be busy. The most common problem: using cd to change to the /cdrom directory. It is good sysadmin technique to use full pathnames rather than cd as in:

ll /cdrom

and not: cd /cdrom ; ll

[Michael Steele_2]

Most common problem with this error is user currently within /cdrom.

pwd

cd /

umount /cdrom

[Karl Haynes]

Bill/Michael....Thanks for the responses. I have not only resolved my regualar mount problem due to the great answers but also my pfs_mount issues. Great answers

[Karl Haynes]

Bill/Michael....Thanks for the responses. I have not only resolved my regualar mount problem due to the great answers but also my pfs_mount issues. Great answers