aspose file tools*
The moose likes Linux / UNIX and the fly likes mount /unmount Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Engineering » Linux / UNIX
Bookmark "mount /unmount" Watch "mount /unmount" New topic
Author

mount /unmount

Raghav Mathur
Ranch Hand

Joined: Jan 12, 2001
Posts: 641
I have windows on one partition and linux on the other . Recently i installed a new CD ROM drive which was detected by windows and linux both . My CDROM drive works fine on windows but doesn't work at all on linux . Linux gives me an error " bad device block /dev/cdrom" .I've tried to mount the device but it seem to give the same errot every time . Any suggestions
thanks in advance
raghav


Raghav.
Michael Ernest
High Plains Drifter
Sheriff

Joined: Oct 25, 2000
Posts: 7292

It may be a question of the format style on the CD you have in the bay. Windows uses (I believe) Joliet extension format, while most Unixes standardize on High Sierra format.


Make visible what, without you, might perhaps never have been seen.
- Robert Bresson
Raghav Mathur
Ranch Hand

Joined: Jan 12, 2001
Posts: 641
i didn't get you .... please if you could explain it to me in detail .
thanks in advance
raghav mathur
Originally posted by Michael Ernest:
It may be a question of the format style on the CD you have in the bay. Windows uses (I believe) Joliet extension format, while most Unixes standardize on High Sierra format.

Guy Allard
Ranch Hand

Joined: Nov 24, 2000
Posts: 776
Have you tried to mount one of the Linux install CD's there? If that does not work, then you have a problem indeed!
Joliet under my RH 7.1 system is called 'Joliet' and is a kernel configuration parameter.
I'd think that most pre-configured kernels would have this set (but don't know for sure).
I'm not sure how to tell if it (Joliet) is there without looking at the .config file from the kernel build, but there must be a way to do that on the fly. Anybody know?
Regards, Guy
[This message has been edited by Guy Allard (edited November 30, 2001).]
[This message has been edited by Guy Allard (edited November 30, 2001).]
Raghav Mathur
Ranch Hand

Joined: Jan 12, 2001
Posts: 641
The LInux CD doesn't work too ..... I'll check the .config in the meanwhile.
thanks
raghav
Originally posted by Guy Allard:
Have you tried to mount one of the Linux install CD's there? If that does not work, then you have a problem indeed!
Joliet under my RH 7.1 system is called 'Joliet' and is a kernel configuration parameter.
I'd think that most pre-configured kernels would have this set (but don't know for sure).
I'm not sure how to tell if it (Joliet) is there without looking at the .config file from the kernel build, but there must be a way to do that on the fly. Anybody know?
Regards, Guy
[This message has been edited by Guy Allard (edited November 30, 2001).]
[This message has been edited by Guy Allard (edited November 30, 2001).]

Guy Allard
Ranch Hand

Joined: Nov 24, 2000
Posts: 776
What exact mount command are you issuing, and what is the exact message you get? Your first message said 'another CDROM' and also '/dev/cdrom'. I think a second one would show up as '/dev/cdrom1' or something to that effect.

Are there any other messages in syslog? (/var/log/messages ?)
What is the result of:
ls /dev/cdrom
ls -l /dev/cdrom
ls /dev/cdrom1
ls -l /dev/cdrom1
??
What are the contents of /etc/fstab?
Are you sure the boot routines do not have a problem with the device? Check syslog and 'dmesg | less'.
What is the output of 'cat /proc/filesystems' ?
Was the Linux system installed from the ROM? Is this a second CD on the system? It should probalbly show up as /dev/cdrom1, not /dev/cdrom.
Regards,Guy


[This message has been edited by Guy Allard (edited December 01, 2001).]
Guy Allard
Ranch Hand

Joined: Nov 24, 2000
Posts: 776
Also, take a look at a number of the files and subdirs of /proc. If the device is really recognized there should be a number of pieces of data there indicating that it is up and functioning.
Is this a burner or just a second CD?
G.

Raghav Mathur
Ranch Hand

Joined: Jan 12, 2001
Posts: 641
hi
(1) Var/log/messages gives me a long list of messages but my CDROM is being detected ( as one of the messages quote that ).
(2) I've tried all possible mount commands .... nothing deems to work . " /dev/cdrom is not a valid block device " .... this is the message which keeps popping up .
(3) /etc /fstab gives me the list of partitions . There is a partition for the cdrom :
/dev/cdrom /mnt/cdrom iso9660 noauto , owner ..........

(4) cat /proc/filesystem has iso9660 .
What next ?
thanks
raghav ...
Originally posted by Guy Allard:
What exact mount command are you issuing, and what is the exact message you get? Your first message said 'another CDROM' and also '/dev/cdrom'. I think a second one would show up as '/dev/cdrom1' or something to that effect.

Are there any other messages in syslog? (/var/log/messages ?)
What is the result of:
ls /dev/cdrom
ls -l /dev/cdrom
ls /dev/cdrom1
ls -l /dev/cdrom1
??
What are the contents of /etc/fstab?
Are you sure the boot routines do not have a problem with the device? Check syslog and 'dmesg | less'.
What is the output of 'cat /proc/filesystems' ?
Was the Linux system installed from the ROM? Is this a second CD on the system? It should probalbly show up as /dev/cdrom1, not /dev/cdrom.
Regards,Guy

[This message has been edited by Guy Allard (edited December 01, 2001).]

Guy Allard
Ranch Hand

Joined: Nov 24, 2000
Posts: 776
Let's look at the 'ls' commands.
ls /dev/cdrom -> should not show much. It is normally a symlink to another /dev device, usually one of the 'hard disk' devices.
ls -l /dev/cdrom -> should show you which device. On my system the output shows:
...... cdrom -> /dev/hdc
Using this as an example, then do a:
ls -l /dev/hdc
The 1st character of the 'perms' should be a 'b'. For example on my system "ls -l /dev/hdc" shows:
brw-------
I'm just trying to verify that /dev/cdrom does indeed point to a block device, not a character device (these have 'c' in the 1st character of the ls -l output) .......
G.

Guy Allard
Ranch Hand

Joined: Nov 24, 2000
Posts: 776
Does the phrase "driver not present" appear in syslog?
Does the physical device have a jumper for master/slave? This should be in your doc for the new ROM. If so, change it to the other setting and give it a try. (!!! Try this 1st !!!).
Another experiment you could try is to get into BIOS setup and flip the setting for 'plug-n-play OS'.
What Linux distribution are you running?
What is the output of "uname -r"?
What is (all) of the output of:
cat /proc/devices
ls -l /dev/cdrom
ls -l /dev/hdc (or whatever device cdrom points to)
G.
[This message has been edited by Guy Allard (edited December 02, 2001).]
[This message has been edited by Guy Allard (edited December 02, 2001).]
[This message has been edited by Guy Allard (edited December 02, 2001).]
[This message has been edited by Guy Allard (edited December 02, 2001).]
Guy Allard
Ranch Hand

Joined: Nov 24, 2000
Posts: 776
And also see:
http://www.redhat.com/support/resources/gotchas/7.2/
Raghav Mathur
Ranch Hand

Joined: Jan 12, 2001
Posts: 641
Thanks a Ton guy . Problem rectified !
Originally posted by Guy Allard:
And also see:
http://www.redhat.com/support/resources/gotchas/7.2/

 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: mount /unmount