What does this Mount Error Indicate ?
 

These days, whenever I try to burn a CD with some backup files and mount it, I am constatnly getting this error below. What does this indicate ?

I also burned ISO images and those discs are booting fine. Thanks.

Vijay :Pengy:

bash-2.05b$ mount /dev/cdrom
mount: wrong fs type, bad option, bad superblock on /dev/cdrom,
or too many mounted file systems
(could this be the IDE device where you in fact use
ide-scsi so that sr0 or sda or so is needed?)

Also how can this problem be solved ? Thanks.

It probably means you didn't add 'append hdX=ide-scsi' to /etc/lilo.conf or your symlink is still pointing to /dev/hdc rather than /dev/sr0 or whatever it needs to be. Probably editing the symlink will take care of it.

I am a newbie and am very confused by this. How can I do this ? Please explain in detail. Thanks.

Vijay

I put the line

append="hdc=ide-scsi hdd=ide-scsi"

in my /etc/lilo.conf - the first uncommented line in mine. That enables scsi emulation for cd/dvd drives. So if yours was hdc you'd need "hdc=ide-scsi".

Then, in the /dev directory, there's probably a file 'cdrom' which is a symlink to your cd device. Only it probably points to '/dev/hdc' and you need to 'rm /dev/cdrom' and 'ln -s /dev/sr0 /dev/cdrom' (I think I got that right this time) to replace it. (Probably sr0 - if that doesn't work try scd0 or maybe another possibility or two we'll try to figure out if necessary.)

Then make sure /etc/fstab has a line something like

/dev/cdrom /mnt/cdrom iso9660 noauto,user,ro 0 0

and lastly, make sure that the settings for k3b in one of the gui panels or menus or whatever points to /dev/cdrom. It's probably one of those elements in the chain that got messed up somewhere.

Last thing to note is that you have to run k3bsetup, of course. It should create a 'cdrecording' group and change the ownership of /dev/sr0 and generally take care of stuff so that you can burn CDs.

And, of course, make sure you in fact have a readable/writable cdrom in the drive and it's not scratched or whaever. :)

-- I'm not doing a very good job here. If you do need to add the append line, I think you have to reboot for it to take effect. Probably should do /sbin/lilo and reboot.

And to see where the symlink points to, do 'ls -l /dev/cdrom' and you'll see something like 'cdrom -> dev/hdc' or 'cdrom -> dev/sr0' or what have you.

To view the contents of all these files, do 'less filename'. To edit them, use the editor of your choice.

I think that covers it.

Here is my LILO Configuration file for reference. Where can I find symlink ?

Thanks.

Vijay

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hdc
append = "=ide-scsi"
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# DOS bootable partition config begins
other = /dev/hdc1
label = DOS
table = /dev/hdc
# DOS bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hdc6
label = Linux
read-only
# Linux bootable partition config ends

Oops. Simultaneous post/edit. I added some stuff above when I realized I might not have been too clear.

You have a problem with the append line as it's posted - is your cd drive on hdb or hdd? It looks like a hdc is a hard drive. Anyway, you need to change

append = "=ide-scsi"

to

append = "hd?=ide-scsi"

And, like I say, the symlink you're interested in is in the /dev directory. 'ls -l /dev/cdrom' to see stuff about it.

-- Screwed up my own thing there - no /dev on that one. /dev's all over the place, but not there. :)

WOW !!! This seems to be a big mess presently. It was OK just until two days ago.
What do you feel caused this mess that I am in currently ?

Vijay :Pengy:

Here is my symlink. How do I change this and to what ?

bash-2.05b$ ls -l /dev/cdrom
lrwxrwxrwx 1 root root 8 Sep 21 10:03 /dev/cdrom -> /dev/hdd

Also, another question. Ig mounting doesn't work correctly, how come xcdroast is burning the iso files correctly ?!!! I am confused about this. Also I use xcdroast and not k3b.

Thanks.

Vijay

Well, not all of that is probably wrong. I was just describing key factors. The first thing seems to be the missing device specification in the append line. If you change that, that may be all it takes so all that caused it was that line. :) And that was probably there all along and just doesn't cause any problem as long as you're not trying to burn a CD, so you wouldn't notice. (Though there might be a boot error message that scrolls by real fast, I think that'd be the only sign.)

Unless you're saying you *could* burn CDs before and it suddenly stopped working. Then it looks like your lilo.conf must have gotten corrupted in one way or another - stray typo when you were editing something else in the file or some weird RAM issue. But let's just hope it was a typo all along. :)

Okay. The floor just disappeared on me. xcdroast is burning correctly? But xcdroast and k3b are both just frontends for cdrecord and other tools and those require scsi-emulation, which you can't have without that append line, as far as I know. I'm lost now.

Unless you've got the newest versions of some the cdrtools. I hear they've finally gotten around to supporting plain ATAPI.

-- Sorry. So you're using xcdroast. I don't know where I got the idea you were using k3b. But, like I say, that's just a frontend. I don't know the gui so I don't know how to set up xcdroast or check it's settings, but cdrecord should be being screwed up with that append.

I tried this and it didn't work. Looks like I am in this for the long haul !!! Dang !!

Re: What does this Mount Error Indicate ?
 

I completely misread your post and misunderstood your problem. I'm sorry about that. Post again so that you have another zero-reply thread and somebody will be sure to actually help you out with your actual problem and no one should complain of a double post. Sorry again.

Yes, the recording worked good and the CD booted well. Can I trust that CD ?

Either it will work or not correct ? If the burning worked that means the CD Media was detected and mounted properly, correct ?

Please assist. Thanks.

Vijay