For some reason, I cannot mount either of my DVD drives. Under YAST2’s Hardware information, it finds both drives, but it says that they are SCSI instead of IDE like they really are. One is a DVD drive and the other is a DVD RW.
The funny thing is, the burning software found the burner and burned an ISO DVD fine. Why is it I cannot mount the drive for my own use? And is there a way to change it from SCSI to IDE and see if that really works. I have tried all the device names that YAST claims they are under, but I believe that the SCSI idea is throwing the whole thing off.
Thanks much.
In recent Linux kernels, PATA drives are handled like SCSI drives. This is because ATA drives have acquired many of the characteristics of SCSI drives in the way they handle commands.
It should make no difference to whether you can mount or burn media though, the problem would be elsewhere.
linevike wrote:
> For some reason, I cannot mount either of my DVD drives. Under YAST2’s
> Hardware information, it finds both drives, but it says that they are
> SCSI instead of IDE like they really are. One is a DVD drive and the
> other is a DVD RW.
>
> The funny thing is, the burning software found the burner and burned an
> ISO DVD fine. Why is it I cannot mount the drive for my own use? And is
> there a way to change it from SCSI to IDE and see if that really works.
> I have tried all the device names that YAST claims they are under, but I
> believe that the SCSI idea is throwing the whole thing off.
There is now a common library that handles disk devices. Almost all disk drives
are now called /dev/sd*, no matter whether they are SATA, PATA, or true SCSI.
Similarly, CD/DVD drives are /dev/sr*, no matter how they are connected. My DVD
drive is /dev/sr0.
If you look at the output of the command ‘dmesg’, you will find what the kernel
called your DVD when it found it. On my system, the message is
sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 4:0:0:0: Attached scsi CD-ROM sr0
Larry
I have done that. I only get the error message that /dev/** whatever I tried cannot be found in the fstab or the mtab.
Also, when I do the dmesg command, I get several errors regarding I/O errors in certain blocks of DVD drives.
When you load the media it should be automounted by the system and show up in /media/LABEL where LABEL is from the CD/DVD. You shouldn’t have to manually mount.
It doesn’t. That’s part of why I know I have a problem. That and I believe in previous versions, the device would have an icon on the desktop, but there is nothing there, nor in My Computer.
You’d have to look in /var/log/messages when you insert the media to see what the system thinks of it.
Also part of the problem. It’s like the system doesn’t recognize the drives, but the drives exist according to YaST.
Is it possible your drive has failed, or at least the reading portion? IIRC they are separate lasers.
Drive failed?
It’s recognized, and the system got installed on there just fine with the drives. Highly unlikely.
linevike wrote:
> Drive failed?
>
> It’s recognized, and the system got installed on there just fine with
> the drives. Highly unlikely.
You still have not posted the portion of dmesg output where your DVD is recognized!!
why would I? It shows the band and name of my drive and that it’s recognized as sr0 and the other as sr1. Sure is a lot of information to be had there.
linevike wrote:
> why would I? It shows the band and name of my drive and that it’s
> recognized as sr0 and the other as sr1. Sure is a lot of information to
> be had there.
That information tells me that you can mount your device with the command
sudo mount -t iso9660 /dev/sr0 /mnt
Is that what you wanted?
I tried that and this is the error I got:
linux-ehld:~ # sudo mount -t iso9660 /dev/sr0 /mnt
mount: block device /dev/sr0 is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/sr0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
and the error I get in dmesg is:
end_request: I/O error, dev sr0, sector 64
isofs_fill_super: bread failed, dev=sr0, iso_blknum=16, block=16
any ideas?
linevike wrote:
> I tried that and this is the error I got:
>
> linux-ehld:~ # sudo mount -t iso9660 /dev/sr0 /mnt
> mount: block device /dev/sr0 is write-protected, mounting read-only
> mount: wrong fs type, bad option, bad superblock on /dev/sr0,
> missing codepage or helper program, or other error
> In some cases useful info is found in syslog - try
> dmesg | tail or so
>
>
> and the error I get in dmesg is:
>
> end_request: I/O error, dev sr0, sector 64
> isofs_fill_super: bread failed, dev=sr0, iso_blknum=16, block=16
>
> any ideas?
How did you burn that DVD?
When I did the command I sent, this is what I get:
finger@larrylap:~/linux-2.6> sudo mount -t iso9660 /dev/sr0 /mnt
mount: block device /dev/sr0 is write-protected, mounting read-only
To show that it is OK,
finger@larrylap:~/linux-2.6> ls /mnt
ARCHIVES.gz control.xml gpg-pubkey-7e2e3b05-4816488f.asc
license.tar.gz README.DOS
autorun.inf directory.yast gpg-pubkey-9c800aca-481f343a.asc
ls-lR.gz suse
boot docu gpg-pubkey-a1912208-446a0899.asc
media.1 SuSEgo.ico
ChangeLog EULA.txt GPLv2.txt
openSUSE11_0_LOCAL.exe
content gpg-pubkey-0dfb3188-41ed929b.asc GPLv3.txt
openSUSE-release.prod
content.asc gpg-pubkey-307e3d54-481f30aa.asc images
pubring.gpg
content.key gpg-pubkey-3d25d3d9-36e12d04.asc INDEX.gz
README
Larry
I used the burning program that came with openSuse. It recognized it and burned it fine.
I think I’m just going to go back to 10.3 because this makes no sense. I can’t figure out why it can burn but it can’t be read. I know it’s not a drive failure just because I have used it recently and if I throw Windows on it, everything will be fine. I’m out of ideas on it.
I had this issue with 10.1. The DVD drive would simply fail to auto mount at times and trying to manually mount would result in the fstab/mtab error you mentioned. Sometimes a reboot would solve the problem. Never did figure it out. I’m running 10.2 and 10.3 now (tried 11 but went back to 10.3) on various machines and haven’t had that problem since.