automount [failed]

[Marine06]

After installing some bugfixes and patches from red hat's site i noticed that on my next reboot it said "automount [failed]." When i tried to mount my cdrom or floppy it gave me errors stating its not a valid block device or fs on vfat is not known. What can i do to repair my mounting abilities?

[armando86]

Originally posted by Marine06:
<STRONG>After installing some bugfixes and patches from red hat's site i noticed that on my next reboot it said "automount [failed]." When i tried to mount my cdrom or floppy it gave me errors stating its not a valid block device or fs on vfat is not known. What can i do to repair my mounting abilities?</STRONG>

What does your /etc/fstab file say?

[Marine06]

/etc/fstab reads:

Label ....
Label=/boot....
/dev/fd0 /mnt/floppy auto noauto,owner 0 0

none
none
/dev/cdrom /mnt/cdrom iso9660 noauto,owner,kudzu,ro 0 0

[Keyser Soze]

I know this probably isn't anything related, but you aren't trying to mount a music CD are you?

[Marine06]

Nope. Just trying to mount my cdrom and floppy but it gives me errors. Any way to reinstall the process that mounts my peripherals?

[bdg1983]

What were the patches and bugfixes you applied?

And what is the mount command you are using for both?

mount /mnt/cdrom

mount /mnt/floppy

[Keyser Soze]

try it as root, is it possible that you have deleted the mount points(are they still there) or that the permissions are changed?

[Marine06]

mdwatts the 3rd,
those are the commands i am using to mount my cdrom and floppy.

I am in root when mounting. I noticed when i boot up that when it loads automount it gives me a failed/error.

I applied:(in order starting from top)

I applied all these at once with the: rpm -Uhv *.rpm

losetup-2.11b-3.i386.rpm
xinetd-2.3.0-1.71.i386.rpm
gftp-2.0.8-1.i386.rpm
mgetty-1.1.25-5.i386.rpm
krb5-workstation-1.2.2-5.i386.rpm
gnupg-1.0.6-1.i386.rpm


I applied all these at once with the: rpm -Uhv *.rpm

mouseconfig-4.22-1.i386.rpm
up2date-2.5.4-1.i386.rpm
up2date-gnome-2.5.4-1.i386.rpm
SysVinit-2.78-17.i386.rpm
xloadimage-4.1-20.i386.rpm


I was going to apply the other larger updates via cdrom, but after the last set of updates and a ctrl alt delete to restart i received an error when trying to mount my cdrom/floppy.

[bdg1983]

Seems you have a problem with the automount daemon. Could you see if there are any more errors? /var/log/messages or other log files in /var/log.

[Marine06]

after searching through var/log/messages i found under root login:

localhost kernal: cdrom: open failed.
localhost kernal: last message repeated 4 times


Under boot.log

localhost depmod: depmod: Can't open /lib/modules/2.4.2-2/modules.dep for writing
localhost rc.sysinit: Finding module dependencies: failed


Also, when i run rpm -Uvh *.rpm and it updates the files with the progress bar is that all i have to do?

[ 18 July 2001: Message edited by: Marine06 ]

[bdg1983]

Can't open /lib/modules/2.4.2-2/modules.dep for writing

Doesn't look good. Hopefully it's fixable.

Does /lib/modules/2.4.2-2/modules.dep exist and if so, is it writable? I'm not sure what permissions this file should have.

[Marine06]

It does exist and i can access it and write to it using " vi. "

I scrolled through this lloooonngg file and found this pertaining to cdrom:

[all of this is one block of code]
/lib/modules/2.4.3-12/kernel/drivers/block/paride/pcd.o: &lt;spaces&gt; /lib/modules/2.4.3-12/kernel/drivers/block/paride/paride.o \
/lib/2.4.3-12/kernel/drivers/cdrom/cdrom.o

[each of these are on seperate lines]

/lib/modules/2.4.3-12/kernel/drivers/cdrom/aztcd.o:

/lib/modules/2.4.3-12/kernel/drivers/cdrom/cdrom.o:

and i found probably around 12 more lines of code referring to cdrom.

aztcd.o and others are drivers under /lib/modules/2.4.3-12/kernel/drivers/cdrom/

[bdg1983]

Somethings gotten messed up from those updates.

Try this.

cd /lib/modules/2.4.2-2
depmod -a

Hopefully that will fix it.

[Marine06]

for its actually 2.4.3-12 and depmod -a returns this:

cant' open /lib/modules/2.4.2-2/modules.dep for writing


It seems that when i try to mount its referring to a different module then exists?

[bdg1983]

You've got a versioning problem. Could have been xinetd or SysVinit update that caused it, but not sure.

I originally did a search at Google (http://www.google.com/linux) for 'modules.dep for writing' or 'can't open modules.dep for writing'. I cannot remember which one, so I would suggest you try both.

Whatever part of the boot process is pointing to 2.4.2-2 needs to be changed to 2.4.2-12 but how to do that. ?????

Check some of your init files to see if you can find the error. Use a file find with grep to search the files in /etc

Hopefully it can be fixed without reinstalling.