Maxoptix Tahiti-3 and IRIX 5.3
Frank Morgan
drive(SCSI) that was working under IRIX 5.2 on an Iris 4D-340(VGX).
When we recently upgraded to Irix 5.3 the Tahiti-3 no longer worked.
The system boots up normally under IRIX 5.3 and the drive still
appears as a floppy device on the desktop (note: the floppy device
icon is not and never has been usable but does seem to indicate
that the system recognizes the drive on the scsi bus) but when we
try to use the drive (which worked under IRIX 5.2 and nothing else
has changed) the following always happens:
I boot system normally and login as root.
I see the floppy icon for optical disk
hinv command reports optical disk(cntrllr 0 drive 4) removable media
I look in /dev/rdsk directory and device /dev/rdsk/dks0d4s7 exists
(/dev/rdsk/dks0d4s7 dev file for scsi contrlr 0 device 4 partition 7)
I put formatted optical disk in drive.
I give command "fsck -n /dev/rdsk/dks0d4s7"
System immediately reboots with message:
Kernel PANIC
read address error
(various hex numbers and codes)
There are 2 other scsi disks on the same scsi controller (cntrllr 0)
(system disk and a data disk) which both work normally.
It seems the kernel was reconfigured wrong in the upgrade.
Can anyone tell me how to reconfigure the kernel to use the
optical disk.
Thank You,
Frank Morgan
f...@panda.uchc.edu
University of CT Health Center
Dave Olson
| We have a Maxoptix Tahiti-3 1.3 Gb optical read/write disk
| drive(SCSI) that was working under IRIX 5.2 on an Iris 4D-340(VGX).
| When we recently upgraded to Irix 5.3 the Tahiti-3 no longer worked.
| The system boots up normally under IRIX 5.3 and the drive still
| appears as a floppy device on the desktop (note: the floppy device
| icon is not and never has been usable but does seem to indicate
| that the system recognizes the drive on the scsi bus) but when we
| try to use the drive (which worked under IRIX 5.2 and nothing else
| has changed) the following always happens:
You have to disable mediad on that device. See the mediad man page.
Use mediad -f to see what device to turn off.
| I put formatted optical disk in drive.
| I give command "fsck -n /dev/rdsk/dks0d4s7"
| System immediately reboots with message:
| Kernel PANIC
| read address error
| (various hex numbers and codes)
Now *that's* a bug. A backtrace with odbx -k on the files in
/usr/adm/crash would help tell us why (or work through your
support folks).
--
The most beautiful things in the world are | Dave Olson
those from which all excess weight has been | Silicon Graphics
removed. -Henry Ford | ol...@sgi.com
Alexis Cousein
>some support for them into IRIX ;-) ?
Get IRIX 5.3 and get support for MOD.
Use the ones that do not identify themselves as Optical, Removable Media
but Magneto Optical, e.g.
Maxoptix Tahiti 2 and 3
Pinnacle Micro PMO-650
Sony SMO-S521
In 5.3 you have the choice of using efs filesystems as before, or using
MAC/hfs filesystems for interoperability. You have to format the latter on
a MAC, though.
--
Alexis Cousein
Systems Support Engineer
Silicon Graphics Belgium
in .be domain: a...@sgi.be
elsewhere: a...@brussels.sgi.com
Alexis Cousein
MODs:
As superuser, create a directory where the disk will be
mounted. You may use any directory name. This example uses
the name "/MO".
# mkdir /MO
Mount the disk. Use the whole-volume raw device.
# /etc/mount -t hfs -o rw /dev/rdsk/dks0d7vol /MO
(assuming M-O is at SCSI controller 0, ID 7)
Ignore the message on the console:
dks0d7vol: volume header not valid
Dave Olson
| >We have these posts about mo-drive problems every week. Time SGI put
| >some support for them into IRIX ;-) ?
|
| Get IRIX 5.3 and get support for MOD.
|
| Use the ones that do not identify themselves as Optical, Removable Media
| but Magneto Optical, e.g.
These work on *all* IRIX releases. Nothing new in 5.3 for them at all.
(yes, yes, I know about my stupid 5.2 bug combined with somebody elses
bug that would crash with PMO on 5.2 unless you disable mediad).
| In 5.3 you have the choice of using efs filesystems as before, or using
| MAC/hfs filesystems for interoperability. You have to format the latter on
| a MAC, though.
This part *is* new in 5.3, and is the only M-O stuff new in 5.3.
Alexis Cousein
*always* have to disable mediad for MODs, only if it appears as floptical
or floppy on your desktop.
Even then, that means it identifies itself as removable media or
optical&removable media. On most MODs, (and I think that's the case with
Tahities), with the notable exception of some Ricohs, you have a DIP switch
that allows them to identify themselves correctly as Magneto-optical.
Dave Olson
| I'm sorry to have to contradict the Great Dave Olson here, but you don't
| *always* have to disable mediad for MODs, only if it appears as floptical
| or floppy on your desktop.
|
| Even then, that means it identifies itself as removable media or
| optical&removable media. On most MODs, (and I think that's the case with
| Tahities), with the notable exception of some Ricohs, you have a DIP switch
| that allows them to identify themselves correctly as Magneto-optical.
Yes, if you force them to look like a hard disk, then mediad will ignore
them. But I think that's a bad idea, perrsonally. And not all M-O
drives have firmware/jumpers that support that. Not even all of the
Tahiti's.
Alexis Cousein
Read closely. You can make them identify as M-O, *not* hard disk, and even
in 5.2 you get a nice `optical' icon on your desktop (doesn't do anything
useful, though, just sits there). Mediad *will* ignore the drive (well it
*does* do some things right, you know ;-) ).
But I agree, some drives don't have the jumpers (Pinnacle). But all recent
Ricoh's and Tahities I've seen have them (but I agree I haven't seen *that*
many ;-) )