Somewhere along the line, LinuxMint has lost the ability to mount my CD/DVD drive. I've burned ISOs on this machine in recent memory, but I went to burn one today and it could detect but not mount my drive.

After doing a lot of searches on this subject, I tried this:

zaivala@zaivala-Inspiron-518:~ > sudo mount -t iso9660 /dev/scd0 /media/cdrom
[sudo] password for zaivala:
mount: mount point /media/cdrom does not exist
zaivala@zaivala-Inspiron-518:~ >

When I put a blank disk in my drive, the computer detects this fact and tells me to click to mount the drive, but the drive does not mount.

Any ideas what now?

I'm running a Dell Inspiron 518 00, 4 GB RAM, and am running LinuxMint 17.1 Rebecca 32-bit with KDE.

In order to mount a CD/DVD it must have a file system on the CD/DVD. Therefore a blank CD/DVD is not mountable. The way that you burn a CD/DVD is to start the burn program and then insert a blank CD/DVD when the burn program asks you to.

-----------------------
Steve Stites

Um, no. If this were the case, you'd never burn an ISO again. And I've burned several ISO disks on this computer, as stated previously.

post edited a bunch because I'm dumb:
please post your /etc/fstab. here's the line for my cd:
If you want to keep trying to manually mount it, make sure /dev/scd0 is the correct device, then maybe try

If LinuxMint uses /media, or directories under that, as a mount point for it's auto mounts, I would use another mount point for manual mounting. You can make your own by creating as root something like:
/mounts/cdrom
and then mount your cdrom to that point. Nothing else will use it or know about it. The "does not exist" output may mean that the directory is not there. Mount points under /media may be tmpfs filesystems which means they don't persist over boots and only get created when needed. This contrasts with making your own mount point whose persistence and location in the filesystem you can pretty much fully control.

Also,
check:
you may find the user name after it.
so the mount point might be:
Does it play music/video cd's/dvd's ok? If yes, put one in and see where it mounts it with:
Fred.

not sure if this applies to your situation but i know on debian (which linuxmint is based on) theres an automount feature which is a default app thats called disks that will allow you to automount.

Because I'm stupid, I'm not thinking what command to use to run fstab to get this. I definitely have fstab, and it's definitely in my /etc directory, but the stupid things I'm trying are not resulting in a listing.

Some gaps in that, but yes, it plays CDs and DVDs fine. Where it mounts it with? Not precise enough English for my morning parser.

I started this with the idea that the problem was with K3b, and it still may be. The computer reports the blank DVD's existence, but K3b doesn't register it. The stupidest thing would be that I only had a CD/DVD-R, but no, the computer reports it as a DVD +/-.

I have new information. What may be happening is that D3B detects that the file is too large for the medium. How sad. "Capacity exceeded by 178.4 MiB." I don't know why, as the download was supposedly created for the express purpose of being a multiple live CD.

So the problem is not with my computer, drive, or OS, but with the downloaded file being too large.

Just FYI, the file is the latest linuxaio-ubuntu14043-mix.iso

Edit: ah, yes, I've had that happen. CDs come in different sizes, I believe. There may be a netinst option available, assuming you'll have an ethernet connection available when you're doing the install.

To get your fstab run:
To get your currently mounted drives just run
If you can play music then the drive is definitely mounted, it's just a matter of making sure k3b can find it, and that the blank disk doesn't have any scratches, etc. I haven't used k3b but from googling there is a setting that looks like this:

Readonly Devices: none
Writer Devices: none

Do you see that settings? If so, tell us what they are set to, and the results of:

to make sure cdrom is in there?

zaivala@zaivala-Inspiron-518:~ > sudo ls -l /media
total 4
drwxr-x---+ 5 root root 4096 Nov 29 00:09 zaivala
zaivala@zaivala-Inspiron-518:~ >


zaivala@zaivala-Inspiron-518:~ > sudo cat /etc/fstab
[sudo] password for zaivala:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=d1bec1bd-7a15-4f9b-886b-ded74e2bc71e / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=152c2903-d386-4b62-a05a-564ba26a867d none swap sw 0 0
zaivala@zaivala-Inspiron-518:~ >

the third one is quite long...

zaivala@zaivala-Inspiron-518:~ > ls -1 /dev | grep ^[^t]
autofs
block
bsg
btrfs-control
bus
cdrom
char
console
core
cpu
cpu_dma_latency
cuse
disk
dri
ecryptfs
fb0
fd
full
fuse
fw0
hidraw0
hidraw1
hidraw2
hidraw3
hidraw4
hidraw5
hidraw6
hpet
input
kmsg
kvm
log
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
loop-control
mapper
mcelog
mem
net
network_latency
network_throughput
null
port
ppp
psaux
ptmx
pts
ram0
ram1
ram10
ram11
ram12
ram13
ram14
ram15
ram2
ram3
ram4
ram5
ram6
ram7
ram8
ram9
random
rfkill
rtc
rtc0
sda
sda1
sda2
sda5
sdb
sdb1
sdc
sdc1
sg0
sg1
sg2
sg3
shm
snapshot
snd
sr0
stderr
stdin
stdout
uhid
uinput
urandom
usb
v4l
vcs
vcs1
vcs2
vcs3
vcs4
vcs5
vcs6
vcs63
vcs7
vcs8
vcsa
vcsa1
vcsa2
vcsa3
vcsa4
vcsa5
vcsa6
vcsa63
vcsa7
vcsa8
vga_arbiter
vhci
vhost-net
video0
zero
zaivala@zaivala-Inspiron-518:~ >

Ah, sorry, I had posted that before I saw your other post. I left it there just in case you were still curious, since the device does seem to be mounting. There's nothing you can do other than use a smaller file or a bigger storage medium.

The interesting bits, if you were still having problems mounting, is that your cd drive is named /dev/sr0, that your fstab isn't set up to mount it the usual way (or at least the way I'm used to), and that it's not mounted to the usual spot.

wrong post