Hi osf gurus,
Thanks to all those who replied. I think our problem is
a flakey cdrom as we have found one disk (DECcampus ULTRIX & PAKS FOR
DEC/OSF1 AXP) that mounts intermitantly and we can sometimes get the OS
disks to mount, sometimes not. The cdrom
is supported in the kernel and the disks
are clean. The prize for the right answer goes to:
tpb_at_zk3.dec.com
see below for all responses:
Here's hoping that we don't have a hard disk crash,
Cheers,
Tim
*******************Original Post************************************
---------- Forwarded message ----------
Date: Tue, 27 May 1997 12:41:32 +0100 (BST)
From: Tim Gibbon <tng_at_dib.chem.nott.ac.uk>
Subject: CD mounting problems.
Dear osf gurus,
We are trying to mount our cd-rom drive(TOSHIBA
CD-ROM XM-4101TA 0064) on our DEC 3000 - M300LX system.
after not having used it for over a year. However when I try the command
mount -r -t cdfs /dev/rz0c /cdrom
/dev/rz0c on /cdrom: I/O error
We are not sure why this happens, but have probed further.
This error also occurs at boot. When we put a cd into the drive,
the drive spins and the led lights but apart from that we have
nothing more to go on. I have tried many of the options for mount but
still no joy.
We tried:
>>>show dev
DKAO A/0/0 RODISK RM WP CD-ROM 0064
our /etc/fstab looks like this
/dev/rz3a / ufs rw 1 1
/proc /proc procfs rw 0 0
/dev/rz3g /usr ufs rw 1 2
/dev/rz0c /cdrom ufs ro 0 0
/dev/rz1g /usr/users ufs rw 1 2
/dev/rz1b swap1 ufs sw 0 2
/dev/rz3b swap2 ufs sw 0 2
/dev/rz1h /tmpast1 ufs rw 1 2
from /var/adm/messages:
DEC 3000 - M300LX system
May 22 09:34:58 dib vmunix: DEC OSF/1 V2.1 (Rev. 250); Tue Oct 4 10:09:02
BST 1994
May 22 09:35:02 dib vmunix: rz0 at asc0 bus 0 target 0 lun 0 (TOSHIBA
CD-ROM XM-4101TA 0064)
#scu show edt bus 0
CAM Equipment Device Table (EDT) Information:
Bus: 0, Target: 0, Lun: 0, Device Type: Read-Only Direct Access
Bus: 0, Target: 0, Lun: 1, Device Type: (not present)
Any advice would be most gratefully received as to any
hardware checks/testing we can try
I shall post a summary,
Thanks,
Tim
**************************************************************************8
>From henckens_at_luc.ac.be Fri Jun 6 09:34:15 1997
Apart that you may have left ISO9660 support out of the kernel, I think
that the drive is broken.
>From Keith_MCCABE_at_paribas.com Fri Jun 6 09:35:44 1997
Tim,
Perhaps the CD you are trying to mount is UFS style not cdfs.
I have a little script which I sometimes use to mount cds so that I
don't have to worry about which device the cd is or what type the cd
is.
Cheers
Keith McCabe
Banque Paribas Capital Markets
London W1
#!/bin/ksh
PATH=/bin:/sbin:/usr/sbin:/usr/local/bin
MOUNTPOINT=/cdrom
if ! test -w /etc/passwd 2> /dev/null; then
echo 'Error: you do not have permission to run this command'
exit 1
fi
echo
echo 'Determining your cdrom drive please wait...'
CD=`file /dev/rrz*c | grep RRD | cut -d: -f1 | sed 's/rrz/rz/'`
echo
echo "Your cdrom drive is at $CD"
if [ `ls /cdrom | wc -w` -gt 0 ]; then
echo 'Error: /cdrom is not empty'
exit 1
fi
if file /dev/rrz*c | grep RRD | grep -q offline; then
echo 'Error: there is no CDROM in the drive'
exit 1
fi
if mount -r $CD $MOUNTPOINT 2> /dev/null ; then
echo "cdrom is now mounted under $MOUNTPOINT"
elif mount -r -t cdfs -o noversion $CD $MOUNTPOINT 2> /dev/null ;
then
echo "cdrom is now mounted under $MOUNTPOINT"
else
echo 'Error: could not read this format cdrom'
exit 1
fi
exit
***********************************************************************8
>From rioux_at_ip6480nl.ce.utexas.edu Fri Jun 6 09:35:21 1997
>From Knut.Hellebo_at_nho.hydro.com Fri Jun 6 09:34:28 1997
>From R.K.Hillman_at_bton.ac.uk Fri Jun 6 09:34:42 1997
>From khd_at_mail.aeg-atlas.de Fri Jun 6 09:35:00 1997
>From star_at_uclan.ac.uk Fri Jun 6 09:35:08 1997
Check that you have:
options CDFS
in your /sys/conf/<MACHINE>
kernel config file.
>From alan_at_nabeth.cxo.dec.com Fri Jun 6 09:34:54 1997
Look at the error log and see what the I/O error is. Be sure to
use the option "-o full" since that is the ONLY way to get the
device Request Sense information that has the actual device
error.
********************************************************************
>From osf_at_python.corning.com Fri Jun 6 09:35:31 1997
try adding the "-o noversion"
or "-o rrip"
option to your mount command
--
( ( / J. Shane Kennedy \ ) )
/ ) ) / osf_at_python.corning.com \ ( ( \
/ ( ( / =============================================== \ ) ) \
/ ) ) my opinions do not reflect those of my employer ( ( \
*************************************************************************
>From tpb_at_zk3.dec.com Fri Jun 6 09:35:37 1997
Sounds like a broken drive.
I/O errors usually occur due to broken hardware.
If the drive won't boot, there's a good change the hardware is broken.
You can try "scu" and "diskx"; both can read data from the drive, provided
the drive is working. For instance, just put a distribution CDROM into the
drive and try to use diskx to do a read test. If you get I/O errors, then
the drive is almost certainly broken.
diskx is part of the optional system exercisers; if it's present on your
system it's in /usr/field/diskx and there should be a reference page. Of
course, if it's not present and your CDROM drive is broken, you'll have a
hard time loading it from the CDROM media :^)
Tom
Received on Fri Jun 06 1997 - 11:28:54 NZST