Skip to main content
Welcome guest. | Register | Login | Post

Debian burns DVD's it can't read

11 replies [Last post]
libervisco's picture
Offline
Joined: 2006-05-04

I switched to Debian Lenny Beta 2 which is on its way to become the next stable Debian release and Debian Stable is known to be rock solid for stability. Yet somehow I'm not impressed..

Either I am asking too much or I'm just out of luck, but whatever I try I am running into issues which I don't, to be entirely honest, really want to tolerate anymore.

I burned a DVD using Nautilus CD/DVD burner, as I usually do and it burned it successfully. However, when I try to insert the DVD it wouldn't mount it complaining of such things as "cdrom: This disc doesn't have any tracks I recognize!" or "attempt to access beyond end of device". I did the same thing when I was still on Debian Sid and the same exact thing happened, but apparently the problem isn't isolated to the unstable branch. Apparently, like some other bugs in Debian it is one of those things which isn't fixed for weeks through out both the unstable and testing branch, and even when the testing branch is almost proclaimed as stable.

Sad really.

The thing is that these DVD's work elsewhere. I had a GoboLinux handy and tried loading the DVD burned in sid there and it was successful. So in other words, Debian burns DVDs it itself (and apparently only itself) can't read.

Meh.

Any ideas?

a thing's picture
Offline
Joined: 2005-12-20
mount it manually

Can you mount it manually, without GNOME?

libervisco's picture
Offline
Joined: 2006-05-04
Yes, I ran mount /dev/hdb

Yes, I ran mount /dev/hdb /media/cdrom0/ and got a "mount: you must specify the filesystem type" message.

Then I tried mount -t iso9660 /dev/hdb /media/cdrom0/ and also tried th "udf" as type, but I just get:

mount: block device /dev/hdb is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/hdb,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

Aside from what I mentioned above I also get in dmesg:

attempt to access beyond end of device
hdb: rw=0, want=68, limit=4
isofs_fill_super: bread failed, dev=hdb, iso_blknum=16, block=16

That said, I just burned a DVD in Pardus 2008 and looks like the same is happening there too. Now since it didn't happen in GoboLinux which I believe has an older kernel while Debian Sid and Pardus use 2.6.25 and Debian Lenny uses 2.6.24 it could be that this is some sort of a kernel regression that appeared in 2.6.24 and remains in 2.6.25.

Either that or some other kind of bug that applies to all of these systems or my DVD drive is faulty, which would be rather weird and unexpected and I wouldn't immediately take that as an answer.. I do plan on buying a SATA DVD burner at some point, but no need to rush it if this one works and this is merely an annoying software bug. :S

Well, kernel devs brag about rapid and accelerating progress on kernel developer citing specifically 2.6.25 as hectic which the greatest amount of changes ever. Perhaps a few nasty regressions slipped up? :S

Offline
Joined: 2006-03-28
Fedora 8 and 9 both are

Fedora 8 and 9 both are running kernels in the 2.6.25-versions and there are no problems like that.

mount comes from util-linux(-ng), which version is installed? Maybe there is something wrong.

Also, does cat /proc/filesystems list iso9660?

a thing's picture
Offline
Joined: 2005-12-20
alternative kernel

Try booting a kernel from another distro into the Debian /.

libervisco's picture
Offline
Joined: 2006-05-04
reptiler wrote: Fedora 8
reptiler wrote:

Fedora 8 and 9 both are running kernels in the 2.6.25-versions and there are no problems like that.

Wasn't 2.6.25 released after after Fedora 8?

Anyway, it might just be that the problem happens only on certain DVD drives, not all, so a lot of people wouldn't be aware of it if it was a bug.

reptiler wrote:

mount comes from util-linux(-ng), which version is installed?

On Debian Lenny it's 2.13.1.1-1, according to synaptic. I think the -1 thing is added by debian.

reptiler wrote:

Also, does cat /proc/filesystems list iso9660?

Actually not. Here is what it lists:

nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev cpuset
nodev debugfs
nodev securityfs
nodev sockfs
nodev usbfs
nodev pipefs
nodev anon_inodefs
nodev futexfs
nodev tmpfs
nodev inotifyfs
nodev devpts
nodev ramfs
nodev hugetlbfs
nodev mqueue
ext3
ext2
reiserfs
vfat

It should be there though, right?

I'm gonna check this on Pardus too in a bit.

libervisco's picture
Offline
Joined: 2006-05-04
On Pardus util-linux is

On Pardus util-linux is 2.14 and it does list iso9660 with cat /proc/filesystems.

I have some CD or DVD in the drive and when I try to remove it by pressing the button on the drive it seems to be spinning, but wont come out. Reading tail -f /var/log/messages gives me this:

Jun 29 04:33:46 localhost klogd: sr 0:0:1:0: [sr0] Add. Sense: No seek complete
Jun 29 04:33:52 localhost klogd: sr 0:0:1:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
Jun 29 04:33:52 localhost klogd: sr 0:0:1:0: [sr0] Sense Key : Medium Error [current]
Jun 29 04:33:52 localhost klogd: Info fld=0x230ffe

I'd have to boot back to Debian to see if I'm getting the same thing there.. But this is pretty weird. Either it's the driver for the jmicron PATA stuff acting up or I might have a dieing DVD burner after all. Sad

Offline
Joined: 2006-03-28
Yes, the 2.6.25-kernel was

Yes, the 2.6.25-kernel was released after F8, but it comes through the updates. Yes, Fedora is that advanced. ;-)

That ISO660 is not listed in filesystems makes you think.
Here's mine:

nodev   sysfs
nodev   rootfs
nodev   bdev
nodev   proc
nodev   cgroup
nodev   cpuset
nodev   binfmt_misc
nodev   debugfs
nodev   securityfs
nodev   sockfs
nodev   usbfs
nodev   pipefs
nodev   anon_inodefs
nodev   futexfs
nodev   tmpfs
nodev   inotifyfs
nodev   devpts
nodev   ramfs
nodev   hugetlbfs
        iso9660
nodev   mqueue
nodev   selinuxfs
        ext3
nodev   fuse
        fuseblk
nodev   fusectl
libervisco's picture
Offline
Joined: 2006-05-04
OK, looks like this is

OK, looks like this is happening only with Traxdata DVD-R (16x capable) media. I tried some others and it works, including Traxdata CD-R's, but whichever Traxdata DVD I try it does the same thing, in both Pardus and Debian.

Now, it didn't do this before. Such DVD's worked fine and I'm not sure I burned any Traxdata DVDs while on sid before the one I burned when this first happened on sid so it is still possible that there is a software bug of some sort. It's just weird that it would affect only Traxdata DVD reading (even burning them seems to work). Even if it was a hardware issue it is still weird why only Traxdata.

Especially considering that the same Traxdata media I tried now and had a problem with actually worked alright before. Also, Traxdata are media I generally consider to be of good quality.

So I'm just puzzled. :S

a thing's picture
Offline
Joined: 2005-12-20
individual disk quality
libervisco wrote:

Especially considering that the same Traxdata media I tried now and had a problem with actually worked alright before.

Do you mean DVDs from the same package? Some damage could have been done (either before or after you got them) to only a select few disks.

libervisco's picture
Offline
Joined: 2006-05-04
No actually. It wouldn't

No actually. It wouldn't read even older Traxdata DVDs which weren't from the same new package I got. They also don't look damaged.

I now even tried in Ubuntu 7.04 (feisty) which is fairly old now, and surprisingly the same thing happens. :S

So I guess my DVD burner is to blame, but.. I don't get it.

libervisco's picture
Offline
Joined: 2006-05-04
I've asked about this on

I've asked about this on CDFreaks and although we didn't make much progress there I think it's pretty evident that the drive is getting faulty. It may work most of the time, as it reads all CD's and probably most of non-traxdata DVDs and can also burn everything, the fact that it can't read burned traxdata DVDs yet another burner can is pretty telling by itself.

And it's not necessarily that it wont read only traxdata DVDs, I just don't have many other brands to test with. It's quite possible it might not be able to read some others too.

Considering that the warranty expired a couple of months ago and I planned on getting a SATA burner anyway, and burners aren't that expensive nowadays I'll probably be buying a new one.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.