Operating System - HP-UX
1833475 Members
3046 Online
110052 Solutions
New Discussion

No such device or address

 
Jonathan Caplette
Regular Advisor

No such device or address

Hi all,

I got a little problem here, I have a magneto optical disk drive on an HP J5000 Vizualise workstation with HP-UX 10.20 and when I'm trying to mount the drive the system report thi to me:

/dev/dsk/c0t2d0: No such device or address

I looked to the /dev/dsk and /dev/rdsk directories and the device is in... I've powered off the drive and powered it on without success...

Can somebody help me... Thanx...
6 REPLIES 6
Stephan Böhm
New Member

Re: No such device or address

Hi,

check at first the corresponding device files and the SW/HW state with
ioscan -fn

Issue an "insf -e" and try again mounting the drive.

Regards,
Martin
Jonathan Caplette
Regular Advisor

Re: No such device or address

Martin, I've tried the ioscan -fn command, but I can't see my device... have any clue?
Ajitkumar Rane
Trusted Contributor

Re: No such device or address

Hello,

well if ioscan does not show the device than either it is blown up or disconnected from the system. You need to do a physical check first.
BTW if its not shown up in ioscan, where did you get the device file. Also check for id clash.

Goodluck
Amidsts difficulties lie opportunities
Stephan Böhm
New Member

Re: No such device or address

Jonathan,
I agree with Ajitkumar, looks a bit like a hardware or connection problem. You could use another set of SCSI cables and connectors and check for correct termination.
Does any other device show up in the ioscan output on the hardware path of the drive?
Another thing you can try is to assign the drive a different SCSI id. If any, you could connect the drive to another SCSI controller.
Check the device files of the drive with the lssf command.
Hope this helps,
Martin
Vincenzo Restuccia
Honored Contributor

Re: No such device or address

Insert the driver in the kernel.
Jonathan Caplette
Regular Advisor

Re: No such device or address

Thanx all... It seems that it's an hardware problem... so I'm gonna get it fixed...