Very Computer

Newsgroups: comp.os.linux.setup,comp.os.linux.misc
Subject: Need help with "mount: fs iso9660 not defined in kernel" error
Summary:
Followup-To:
Distribution:
Organization: Florida State University Computer Science Department
Keywords:
Cc:

  Err, what the heck does this error message mean?!?  Just compiled 1.3.35
on my system, with the intention of mounting my Atapi CDRom using "mount -r
-t iso9660 /dev/cdrom /cdrom", where /dev/cdrom is linked to /dev/hdc.  Also
tried "mount -r -t iso9660 /dev/hdc /cdrom" for kicks.  Both times gave the
"fs iso9660 not defined etc etc" error.
  Not sure I understand the meaning of this error message.  I was sure that
I had specified to use fs iso9660 when I compiled the kernel.  I recompiled the
kernel again, making absolutely sure that I said yes to using iso9660 as a
file server.  Even dl'ed and installed an earlier kernel version (1.3.30) in
case it was a problem with 1.3.35.  Nothing helped.
  My hardware configuration currently is an EIDE2300 controller card with
the secondary controller disabled.  On this card I have my primary HD.  Then
I have a secondary ATAPI card controlling my CDROM.

Any clues?  Read several faqs, none seemed to help.
Steve

->   Subject: Need help with "mount: fs iso9660 not defined in kernel" error
->
->     Err, what the heck does this error message mean?!?  Just compiled 1.3.35
->   on my system, with the intention of mounting my Atapi CDRom using "mount -r
->   -t iso9660 /dev/cdrom /cdrom", where /dev/cdrom is linked to /dev/hdc.  Also
->   tried "mount -r -t iso9660 /dev/hdc /cdrom" for kicks.  Both times gave the
->   "fs iso9660 not defined etc etc" error.
->     Not sure I understand the meaning of this error message.  I was sure that
->   I had specified to use fs iso9660 when I compiled the kernel.  I recompiled the
->   kernel again, making absolutely sure that I said yes to using iso9660 as a
->   file server.  Even dl'ed and installed an earlier kernel version (1.3.30) in
->   case it was a problem with 1.3.35.  Nothing helped.

- Check /proc to see which fs are supported by the current kernel
- Ensure that you are using your NEW! kernel (the compilation time and
  date will be displayed on bootstrap.

--
--

snail-mail: TU Berlin; Sekr. FR 5-13; Franklinstr. 28-29; 10587 Berlin
=-=-=-=-= "I'm sorry Dave, but I can't do that"  HAL 2000  =-=-=-=-=-=

: : Subject: Need help with "mount: fs iso9660 not defined in kernel" error

: :   Err, what the heck does this error message mean?!?

: Well, that is easy to check.
: Say "cat /proc/filesystems".
: If iso9660 does not occur, then it means "fs iso9660 not defined in kernel".
: If iso9660 does occur, then it means "please upgrade, your mount is rotten".

: [A new mount will also fail, but also tell you what is wrong.
: Anticipating - since you have a distribution with rotten mount,
: you may easily have a rotten /dev/hdc as well. Check its major and
: minor numbers.]

Ok, found the problem.  Dont understand it, but found it.  After rerunning
makedev.ide and checking a variety of other things, I tried a mount on
/dev/hdd.  #$^ thing worked.  I can't figure out why my system is declaring
the cdrom to be hdd.  The way the cards and cables are hooked up it should
be hdc.

The thing that was throwing me off was the 'not defined by kernel' message.
To me this reads that there is a problem with my compiled kernel, not with
the mount I'm trying to make.  Error message should have read something like
'Unable to mount /dev/whatever as fs ...'.  This way there would have been
little to confuse the source of my problem with the kernel.

Many thanks to those who responded.
Steve