Dear Members,
I have connected a MO drive (olympus MOS363) to a PC with Linux 2.4.9-34custom OS through SCSI port.

The MO drive have been recognized by BIOS and it has also been listed in proc/scsi/scsi file. But when I try to mount the drive I get the following error:
# mount /mnt/mo (ENTER)
mount: /dev/mo is not a valid block device

The contents of /etc/fstab for MO drive is as bellow:
/dev/mo /mnt/mo auto noauto,owner 0 0

I have tested the MO drive by connecting it to another computer via SCSI interface and it operated normally.

1- What could be the cause of the problem that mount can not mount the drive?
2- Is something is missing, maybe some modules?

3- As the device exists in /proc/scsi/scsi file, does it shows that it's driver is loaded?

Thank you

To find out the error you are getting do:

Hi,
I have entered the command. There are 21 lines of reports. I can not copy and paste them because they are on another platform and not connected to internet or Ethernet.
The followings are some of the messages that seems to be related:

Line 12: hdc: ATAPI 24X CD-ROM drive, 90kB cache, UDMA33
Line 13: Uniform CD-ROM driver Revision: 3.12
Line 14: SCSI host adapter emulation for IDE ATAPI devices
Line 15: serial driver version 5.05c (2001-07-08) with MANY_PORTS, MULTIPORT, SHARE_IRQ, SER
Line 16: IAL_PCI ISAPNP enabled

Please note this PC also has an internal CDRom drive and one 3.5" floppy.

Thank you

Typically /dev/mo is a link to the actual device ID i.e. /dev/sda. Your system may not of created the link vs the other PC where you tested the drive. I assume that recognized by BIOS is the SCSI controller vs the computer BIOS. The posted messages are unrelated to the MO drive.

Is the SCSI controller module being loaded?. You also need the scsi_mod module loaded. Once these modules are loaded a drive device ID should be created. You can look at the output of the lsmod command to see what modules are being loaded.

You are right /dev/mo in link to a some actual device but dev/sda in the hard disk in my computer. When I enter "mount" command the followings reported:
/dev/sda1 on / type ext3 (rw)
none on /proc/ type proc (rw)
none on /dev/pts type devpts (rw,gid-5,mode=620)
/dev/sda1 is the hard disk. The MO is attached but it is not appeared on the output list so i don't know /dev/mo links to which actual device. Because of this I think the related module has not been loaded.

the loaded modules related to SCSI listed by "lsmod" are as bellow:
ide-scsi
ide-cd
cdrom
There is a long list of available SCSI drivers when listed by modprobe -l
3w-xxxx.o
53c7,8xx.o
AM53C974.o
BusLogic.o
NCR53C406a.o
a100u2w.o
aacraid/aacraid.o
advansys.o
aha152x.o
ahaa542.o
aha1740.o
aic7xxx/aic7xxx.o
aic7xxx_old.o
atp870u.o
cpqfc.o
dmx3191d.o
dpt_i2o.o
dtc.o
eata.o
eata_dma.o
eata_pio.o
fdomain.o
g_NCR5380.o
gdth.o
ide-scsi.o
imm.o
in2000.o
initio.o
ips.o
iscsi.o
isp/sip_mod.o
megaraid.o
ncr53c8xx.o
osst.o
pas16.o
pci2000.o
pci2220i.o
pcmcia/aha152x_cs.o
pcmcia/fdomain_cs.o
pcmcia/nsp_cs.o
pcmcia/qlogic_cs.o
ppa.o
psi240i.o
qla1280.o
qla2x00.o
qlogicfas.o
qlogicfc.o
qlogicisp.o
scsi_debug.o
seagate.o
sg.o
sim710.o
sr_mod.o
st.o
sym53c416.o
t128.o
tmscsim.o
u14-34f.o
ultrastor.o
wd7000.o

The problem is that I don't know which module is related to MO drives. I have tried sg.o as a generic scsi controller but it didn't helped to recognize the drive.

I assume that /dev/sda is a SCSI drive and since no controller modules are listed I also assume that they are compiled into the kernel. Is there a /dev/sdb?

Please post your proc/scsi/scsi file

Also post your SCSI hardware configuration.

Dear Michaelk

There is no /dev/sdb on the computer. However the name exists (like many other /dev/xxx) but nothing is connected to them.

The /proc/scsi/scsi contents are as bellow:
========================================================
Attached devices:
Host: scsi0 Channel:00 Id:01 Lun:00
Vendor FUJITSU Model:MAW3073NC Rev:8601
Type: Direct-Access ANSI SCSI revision: 03

Host: scsi1 Channel: 00 Id:05 Lun:00
Vendor: OLYMPUS Model: MOS363 Rev: 3.01
Type: Optical Device ANSI SCSI revision: 02
=========================================================

Regarding SCSI hardware configuration I am not sure what is required. Visually there are two SCSI ports at the extension slots of the PC.


Thank you

I would expect the SCSI system to automatically assign /dev/sdb to your MO drive.

Does the following command output any information:
dmesg | grep sdb

What is /dev/mo actually linked to?
ls -l /dev/mo

# dmesg | grep sdb
has the following output:
=============================================
Attached scsi removable disk sdb at scsi1, channel 0, id 5, lun 0
SCSI device sdb: 310352 2048-byte hdwr sectors (636 MB)
sdb: Write protect is on
sdb: sdb1 sdb2 sdb3 sdb4
=============================================


#ls -l /dev/mo
has the following output:
=============================================
brw-rw-rw- 1 root disk 8, 240 Oct 27 23:27 /dev/mo
=============================================

So the drive appears to be working correctly. Try mounting /dev/sdb1.

Do you know what how the drive is formatted? i.e. filesystem types (ext2 etc)

I have tried to mount /dev/sdb1 but it returned the following result:

# mount /dev/sdb1 /mnt/mo
================================
mount: special device /dev/sdb1 does not exist
================================

I have also tried the followings but all of them had the same result.
# mount -t ext2 /dev/sdb1 /mnt/mo
# mount /dev/sdb2 /mnt/mo
# mount /dev/sdb3 /mnt/mo
# mount /dev/sdb4 /mnt/mo

regarding the file system, as I have seen the same disk under Windows, it was FAT (which is ext2?)

The command (dmesg | gerp sdb) gives MO disk information correctly e.g. whether the disk is write protected or not (provided that the disk has not been changed after boot) and says it is on /sdb. But system does not recognize /dev/sdb as a device. I am confused.

Dear Michaelk,
Thank you for support.

As a feedback to the forum I am posting this reply.
The problem has been solved. The MO drive ID was recommended incorrectly by supplier. By correcting the MO drive ID, it has been mounted by mount command as normal.

Best regards

Thanks for posting back that you got it working.