Cannot stat device "/dev/rdsk/c0t6d0s0" on solaris 8

Cannot stat device "/dev/rdsk/c0t6d0s0" on solaris 8

Post by TingCho » Sun, 05 Jan 2003 05:21:46



The error
'Cannot stat device "/dev/rdsk/c0t6d0s0" on solaris 8'
appear
when executing
xmcd &

How to fix it?

 
 
 

Cannot stat device "/dev/rdsk/c0t6d0s0" on solaris 8

Post by Lars Tunkran » Sun, 05 Jan 2003 20:05:36



> The error
> 'Cannot stat device "/dev/rdsk/c0t6d0s0" on solaris 8'
> appear
> when executing
> xmcd &

> How to fix it?

   The Motif CD Player makes a reasonable assumption that
you CD drive  is SCSI unit  6.  This is the normal
Adress for any Older SUN Workstation. And xmcd is an old
program ( I used it in 1993 )

You must change XMCD's  idea of what hardware adress
the CD-Drive has.

Dont know from the top of my head if this is Configurable
or requires a source code change.

--

Lars Tunkrans

 
 
 

Cannot stat device "/dev/rdsk/c0t6d0s0" on solaris 8

Post by Thomas Tornblo » Sun, 05 Jan 2003 23:31:38




> > The error
> > 'Cannot stat device "/dev/rdsk/c0t6d0s0" on solaris 8'
> > appear
> > when executing
> > xmcd &

> > How to fix it?

>    The Motif CD Player makes a reasonable assumption that
> you CD drive  is SCSI unit  6.  This is the normal
> Adress for any Older SUN Workstation. And xmcd is an old
> program ( I used it in 1993 )

> You must change XMCD's  idea of what hardware adress
> the CD-Drive has.

> Dont know from the top of my head if this is Configurable
> or requires a source code change.

> --

> Lars Tunkrans

The problem is more likely that vold is controlling the device.

Either stop vold (/etc/init.d/volmgt stop) or make xmcd use the vold
managed device in /vol/dev/aliases/

Thomas

 
 
 

Cannot stat device "/dev/rdsk/c0t6d0s0" on solaris 8

Post by TingCho » Tue, 07 Jan 2003 23:23:59


The error
'Cannot stat device "/dev/rdsk/c0t6d0s0" on solaris 8'
appear
when executing
xmcd &

How to fix it?

 
 
 

Cannot stat device "/dev/rdsk/c0t6d0s0" on solaris 8

Post by TingCho » Tue, 07 Jan 2003 23:36:53


I try both
wcars27e-145> xmcd -dev  /vol/dev/aliases/cdrom0 &
[7] 4591
wcars27e-146> USCSICMD ioctl failed: I/O error
USCSICMD ioctl failed: I/O error

and

wcars27e-146> xmcd -c /vol/dev/aliases/cdrom0 &
[7] 4672
wcars27e-147> USCSICMD ioctl failed: I/O error
USCSICMD ioctl failed: I/O error

Both result in
Warning:
Device is not SCSI-II compliant.

My computer is Sun Ultra 10.




> > > The error
> > > 'Cannot stat device "/dev/rdsk/c0t6d0s0" on solaris 8'
> > > appear
> > > when executing
> > > xmcd &

> > > How to fix it?

> >    The Motif CD Player makes a reasonable assumption that
> > you CD drive  is SCSI unit  6.  This is the normal
> > Adress for any Older SUN Workstation. And xmcd is an old
> > program ( I used it in 1993 )

> > You must change XMCD's  idea of what hardware adress
> > the CD-Drive has.

> > Dont know from the top of my head if this is Configurable
> > or requires a source code change.

> > --

> > Lars Tunkrans

> The problem is more likely that vold is controlling the device.

> Either stop vold (/etc/init.d/volmgt stop) or make xmcd use the vold
> managed device in /vol/dev/aliases/

> Thomas

 
 
 

Cannot stat device "/dev/rdsk/c0t6d0s0" on solaris 8

Post by Michael Tos » Wed, 08 Jan 2003 00:07:11



Quote:> The error
> 'Cannot stat device "/dev/rdsk/c0t6d0s0" on solaris 8'
> appear
> when executing
> xmcd &

> How to fix it?

I dunno what xmcd is - you certainly need a higher version.
The alternative is to turn vold off, or comment cdrom out in /etc/vold.conf.

--
Michael Tosch / Master IS/IT Support
Ericsson Eurolab Deutschland GmbH
Tel: +49 2407 575 313

 
 
 

Cannot stat device "/dev/rdsk/c0t6d0s0" on solaris 8

Post by Thomas Tornblo » Wed, 08 Jan 2003 03:54:25



> I try both
> wcars27e-145> xmcd -dev  /vol/dev/aliases/cdrom0 &
> [7] 4591
> wcars27e-146> USCSICMD ioctl failed: I/O error
> USCSICMD ioctl failed: I/O error

> and

> wcars27e-146> xmcd -c /vol/dev/aliases/cdrom0 &
> [7] 4672
> wcars27e-147> USCSICMD ioctl failed: I/O error
> USCSICMD ioctl failed: I/O error

> Both result in
> Warning:
> Device is not SCSI-II compliant.

> My computer is Sun Ultra 10.

An ultra 10 does not normally have a SCSI CDROM, it has an IDE CDROM
normally at /dev/rdsk/c0t2d0s0.

I have no idea if xmcd handles non-SCSI CDROM:s, but from the error
message it doesn't seem that way.

Thomas

 
 
 

Cannot stat device "/dev/rdsk/c0t6d0s0" on solaris 8

Post by Michael T Pin » Wed, 08 Jan 2003 09:37:28




>> I try both
>> wcars27e-145> xmcd -dev  /vol/dev/aliases/cdrom0 &
>> [7] 4591
>> wcars27e-146> USCSICMD ioctl failed: I/O error
>> USCSICMD ioctl failed: I/O error

>> and

>> wcars27e-146> xmcd -c /vol/dev/aliases/cdrom0 &
>> [7] 4672
>> wcars27e-147> USCSICMD ioctl failed: I/O error
>> USCSICMD ioctl failed: I/O error

>> Both result in
>> Warning:
>> Device is not SCSI-II compliant.

>> My computer is Sun Ultra 10.
>An ultra 10 does not normally have a SCSI CDROM, it has an IDE CDROM
>normally at /dev/rdsk/c0t2d0s0.
>I have no idea if xmcd handles non-SCSI CDROM:s, but from the error
>message it doesn't seem that way.

xmcd (at least as of v2.6, which is what I'm running) works fine on
non-SCSI CDROMs.  I'm using it as I type this on my Ultra5.  I suspect you
were correct the first time, it's a vold problem.  He needs to either tell
vold to ignore the CD player, or a better option, tell xmcd at install time
that the CD player is under the control of vold.

--
**************************************************************************


*     ftp://ftp.nndev.org/pub        |     #include <std.disclaimer>     *

 
 
 

Cannot stat device "/dev/rdsk/c0t6d0s0" on solaris 8

Post by Philip Bro » Wed, 08 Jan 2003 09:58:22



Quote:>I try both
>wcars27e-145> xmcd -dev  /vol/dev/aliases/cdrom0 &
>[7] 4591
>wcars27e-146> USCSICMD ioctl failed: I/O error
>USCSICMD ioctl failed: I/O error

>and

>wcars27e-146> xmcd -c /vol/dev/aliases/cdrom0 &
>[7] 4672
>wcars27e-147> USCSICMD ioctl failed: I/O error
>USCSICMD ioctl failed: I/O error

that sounds like the "security fix problem".

non-root users can no longer do USCSI ioctls.

You have to use a program that uses the ioctls specifically for CDROMs.

/usr/include/sys/cdio.h

--
http://www.blastwave.org/ for solaris pre-packaged binaries with pkg-get
  Sign up to maintain a package for your own favourite software!
[Trim the no-bots from my address to reply to me by email!]

http://www.spamlaws.com/state/ca1.html

 
 
 

Cannot stat device "/dev/rdsk/c0t6d0s0" on solaris 8

Post by Joerg Schilli » Wed, 08 Jan 2003 19:01:49





>>I try both
>>wcars27e-145> xmcd -dev  /vol/dev/aliases/cdrom0 &
>>[7] 4591
>>wcars27e-146> USCSICMD ioctl failed: I/O error
>>USCSICMD ioctl failed: I/O error

>>and

>>wcars27e-146> xmcd -c /vol/dev/aliases/cdrom0 &
>>[7] 4672
>>wcars27e-147> USCSICMD ioctl failed: I/O error
>>USCSICMD ioctl failed: I/O error

>that sounds like the "security fix problem".

>non-root users can no longer do USCSI ioctls.

It isn't. If it would, then errno would not be EIO.

Without more debugging the real reason is hart to tell.

--



URL:  http://www.fokus.fhd.de/usr/schilling    ftp://ftp.berlios.de/pub/schily

 
 
 

Cannot stat device "/dev/rdsk/c0t6d0s0" on solaris 8

Post by Juergen Kei » Wed, 08 Jan 2003 19:40:30



> I try both
> wcars27e-145> xmcd -dev  /vol/dev/aliases/cdrom0 &
> [7] 4591
> wcars27e-146> USCSICMD ioctl failed: I/O error
> USCSICMD ioctl failed: I/O error

Are there any error messages logged to /var/adm/messages when you try
this?

You probably should increase the verbosity of the "sd" driver to
diagnose the problem, with the command (you have to run this as
"root")

  echo 'sd_error_level/W1' | adb -wk

 
 
 

Cannot stat device "/dev/rdsk/c0t6d0s0" on solaris 8

Post by TingCho » Thu, 09 Jan 2003 05:07:15


I do not have root permission.


> > I try both
> > wcars27e-145> xmcd -dev  /vol/dev/aliases/cdrom0 &
> > [7] 4591
> > wcars27e-146> USCSICMD ioctl failed: I/O error
> > USCSICMD ioctl failed: I/O error

> Are there any error messages logged to /var/adm/messages when you try
> this?

> You probably should increase the verbosity of the "sd" driver to
> diagnose the problem, with the command (you have to run this as
> "root")

>   echo 'sd_error_level/W1' | adb -wk