attempt to access beyond end of device on DVD

I also connected the dvd recorder over a firewire adapter to my system and I got similar writing and reading errors from the scsi driver.

I have what seems to be a related problem with DVD-R

K3B burns and verifies (!) a DVD-R without errors, but when I try to read it with other applications, I get error messages (see below).

In my case, this seems only to occur, if the sum of the file lengths on the DVD-R exceeds 4 GB. (Nominal capacity: 4.3 GB, space used in my example: 4.1 GB)

Messages in /var/log/messages seem to indicate that there is a hardcoded (?) limit (which equals to 4 * 2 * 1024 * 1024):

/var/log/messages:
May 23 01:18:16 localhost kernel: [4298007.805000] attempt to access beyond end of device
May 23 01:18:16 localhost kernel: [4298007.805000] hdc: rw=0, want=8475804, limit=8388604

The strange thing is, K3B did not complain, only the "normal" OS does.

Remaining info:

Same kernel version.

hdparm -v -i /dev/dvd:

IO_support = 1 (32-bit)
 unmaskirq = 1 (on)
 using_dma = 1 (on)
 keepsettings = 0 (off)
 readonly = 0 (off)
 readahead = 256 (on)
 HDIO_GETGEO failed: Invalid argument

 Model=HL-DT-ST DVDRAM GSA-4160B, FwRev=A300, SerialNo=XXXXXXXXX
 Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
 RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
 BuffType=unknown, BuffSize=0kB, MaxMultSect=0
 (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes: pio0 pio3 pio4
 DMA modes: mdma0 mdma1 mdma2
 UDMA modes: udma0 udma1 *udma2 udma3 udma4
 AdvancedPM=no
 Drive conforms to: Unspecified: ATA/ATAPI-2 ATA/ATAPI-3 ATA/ATAPI-4 ATA/ATAPI-5

 * signifies the current active mode

Does the burned DVD work on another system?

Yes.

In fact, it also works on the same machine under W98SE (it's a dual boot machine), where I do an additional file by file comparison at the moment.

It is most likely not a coincident that this problems occurs with images > 4 GB, and limit mentioned in the log file is.... 4 GB

I presume that K3B uses a more direct API without this limitation.

If you write a > 4G DVD on someting else, does it work on the setup where you experience problems with K3B written DVD's?

I'm trying to narrow this down. The thing is that the "limit" mentioned in your dmesg is information obtained from the drive itself, which is obtained from reading the DVD. It sets the size limit (this isn't an OS limit, is what I'm trying to say).

I strongly suspect that K3B is writing something wrong, and that Linux is just being anal about it, more so than Windows. This might not be ideal, but if the disk is written incorrectly (with incorrect size values for the session), then that's not Linux's fault, it's K3B's fault.

That was my thought as well, but there two facts to consider:

On the DVD-R empty media (Verbatim) is says 4.7 GB. I know, this is the propaganda value. K3B itself reports (Disk Info):

DVD-R sequential
510:46:46 4.4 GB

Is there another tool that displays the media info?

As mentioned above, I did a (successful) file by file comparison, i.e. the data is actually on the media.

On Mon, 2006-06-05 at 22:32 +0000, mistr wrote:
> That was my thought as well, but there two facts to consider:
>
> On the DVD-R empty media (Verbatim) is says 4.7 GB. I know, this is the
> propaganda value. K3B itself reports (Disk Info):
>
> DVD-R sequential
> 510:46:46 4.4 GB
>
> Is there another tool that displays the media info?

I don't mean the media type data, I mean the data itself on the disk
reports the size of say the partition (just like a hardisk partition
would). If this data on the disk is incorrect, the it would report a
truncated length for the session/partition.

As for the 4.4/4.7 GB discrepancy, that's a marketing/technical issue.
4.7GB is the 10-base measurement, and 4.4GB is the 2-based one (e.g.
1000 bytes == 1k as opposed to 1024 bytes == 1k).

> I mean the data itself on the disk reports the size of say the partition

Any tool that could check this? This hypothetical fault should also be present in an image stored on the hard drive, which could be checked by a third party tool (like fsck - What filesystem is usually used on a data dvd? udf?)

On Tue, 2006-06-06 at 16:24 +0000, mistr wrote:
> > I mean the data itself on the disk reports the size of say the
> partition
>
> Any tool that could check this? This hypothetical fault should also be
> present in an image stored on the hard drive, which could be checked by
> a third party tool (like fsck - What filesystem is usually used on a
> data dvd? udf?)

It's likely iso9660 (check cat /proc/mounts to see). There's probably a
lot of iso checkers out there.

With readcd I can read in a complete DVD-ROM where before dvdread says can't seek to block. If I mount this iso image then as a loop device I can play this dvd without problem. Is this a problem in libdvdread?

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Since it has been a long time, I'd like to know if this is still a problem with a more recent version?
Like 7.04, or ideally Gutsy.

I just installed Gutsy, and I think I may have a similar problem. Upon inserting a burnt DVD (burnt using Nero in WinXP), I received the following errors:

[13150.597572] UDF-fs: No VRS found
[13150.601139] ISO 9660 Extensions: Microsoft Joliet Level 3
[13150.601392] ISOFS: changing to secondary root
[13166.226491] attempt to access beyond end of device
[13166.226499] hda: rw=0, want=8350544, limit=7650048
[13166.226502] Buffer I/O error on device hda, logical block 2087635
[13166.226837] attempt to access beyond end of device
[13166.226839] hda: rw=0, want=8350548, limit=7650048
[13166.226841] Buffer I/O error on device hda, logical block 2087636
[13166.227160] attempt to access beyond end of device
[13166.227163] hda: rw=0, want=8350552, limit=7650048
[13166.227165] Buffer I/O error on device hda, logical block 2087637
[13166.227477] attempt to access beyond end of device
[13166.227479] hda: rw=0, want=8350556, limit=7650048

I had to eject and remount about 5 times to get it to read properly. When it finally did mount, I copied the files to my hard disk. From the point of mounting to the end of copying, I recorded the following messages from dmesg:

[17539.028998] UDF-fs: No VRS found
[17540.097365] ISO 9660 Extensions: Microsoft Joliet Level 3
[17540.098002] ISOFS: changing to secondary root
[18037.675982] hda: media error (bad sector): status=0x51 { DriveReady SeekComplete Error }
[18037.675989] hda: media error (bad sector): error=0x34 { AbortedCommand LastFailedSense=0x03 }
[18037.675992] ide: failed opcode was: unknown
[18037.676465] hda: error code: 0x70 sense_key: 0x03 asc: 0x02 ascq: 0x00
[18037.676473] end_request: I/O error, dev hda, sector 404
[18605.133169] hda: media error (bad sector): status=0x51 { DriveReady SeekComplete Error }
[18605.133176] hda: media error (bad sector): error=0x34 { AbortedCommand LastFailedSense=0x03 }
[18605.133179] ide: failed opcode was: unknown
[18605.133753] hda: error code: 0x70 sense_key: 0x03 asc: 0x02 ascq: 0x00
[18605.133762] end_request: I/O error, dev hda, sector 280

While the disc would not mount properly in Ubuntu, it mounted fine in Windows XP through VMWare and I was able to read files off of it.

I am not sure tlutz is the same thing.
First, I am a bit surprised hda is your DVD writer, but I guess it is me that is ignorant here.
Your values are a bit different:
  want=8350556, limit=7650048
and others where having something like:
  want=8475804, limit=8388604.
Oh well, maybe not that much, I think I will consider it affecting Gutsy too.

I don't have a DVD reader or writer yet.
But I sure know that by default Nero (suppose K3B too) on CD, have overburning (not sure of the name of the option) set on by default, that allowed to write more than the media would normally allow.
Hum, I will mark it as affecting k3b, that way, the k3b maintainer(s) could comment on this.

And I suspect you guys have 'overburned' your DVD.
Now, I suppose Linux kernel is checking size reported by the media, and limit it to it.
It should probably allow a reading the overburn area while reading.
But it is unclear how to.

This sure looks something that would not be specific to Ubuntu, I should try to find information upstream or on other distros about overburning.

Oops, added to bad project by mistake. Invalidating.

The general question now is this: Are you able to write an image that cause this problem on reading, if overburning option is off with k3b when writing it?

http://www.ussg.indiana.edu/hypermail/linux/kernel/0403.3/0388.html COULD be related. (suggest a patch)

I experienced a similar issue with Feisty. My problem went away after a reboot but it seems like this is a fairly common issue.

Here are some possible duplicates:
Bug #118330
Bug #58018
Bug #152547

Bug #118330 is especially interesting as it has lots of logs.

On Thu, 15 Nov 2007 15:42:36 -0000
Paul Dufresne wrote:

> - attempt to access beyond end of device on DVD
> + attempt to access beyond end of device on DVD (overburning issue?)

No not overburning, because like I described in the initial comment
I have problems with dvd-ram and dvd-roms.

Ok Martin, not an overburning issue.

Let's come back to Ben comments.
One said to check filesystems type once mounted with 'cat /proc/mounts' to confirm that the image filesystem is iso9660 and not UDF type.

Also Ben said that there must be tons of iso9660 checkers out there.
Well when I do apropos iso9660 I get:
paul@paul-desktop:~$ apropos iso9660
devdump (1) - Utility programs for dumping and verifying iso9660 images.
fs (5) - Linux filesystem types: minix, ext, ext2, ext3, xia, msdos, umsdos, vfat, proc, nfs, iso...
genisoimage (1) - create ISO9660/Joliet/HFS filesystem with optional Rock Ridge attributes
isodump (1) - Utility programs for dumping and verifying iso9660 images.
isoinfo (1) - Utility programs for dumping and verifying iso9660 images.
isosize (8) - outputs the length of a iso9660 file system
isovfy (1) - Utility programs for dumping and verifying iso9660 images.

The two most interesting seems to be:
isovfy from genisoimage package
and isosize from util-linux package

I also note that I can't find dvdread in ubuntu that you mentioned in:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/42023/comments/12
My search was:
http://packages.ubuntu.com/cgi-bin/search_contents.pl?word=dvdread&searchmode=searchfiles&case=insensitive&version=gutsy&arch=amd64

Probably good to keep in head that iso9660 DON'T EASILY support that A SINGLE file be > 4GB.
See http://en.wikipedia.org/wiki/ISO_9660 , more precisely the "The 2 GiB (or 4 GiB depending on implementation) file size limit" paragraph.

Hi Paul,

On Wed, 21 Nov 2007 16:16:56 -0000
Paul Dufresne wrote:

> I also note that I can't find dvdread in ubuntu that you mentioned in:

The package is named libdvdread3. Try this link
http://packages.ubuntu.com/cgi-bin//search_contents.pl?version=gutsy&arch=amd64&case=insensitive&word=libdvdread3&searchmode=searchfiles

Does this happens only on commercial DVD (read movie DVD)?

Even if the movie been downloaded, it could have been read from DVD without being decrypted by some decss decoder program.

This could indeed fit bug #140044 (Commercial DVDs fail to mount. System simply hangs spinning disks. Both libdvdread3 and libdvdcss2 are installed. [Bug appeared with Gutsy according to bug poster]).

It is still unclear to me which programs cause the:
Apr 29 11:28:34 localhost kernel: [10458.017362] attempt to access beyond end of device
Apr 29 11:28:34 localhost kernel: [10458.017441] hdc: rw=0, want=8946808, limit=8388604
to appears. By opening a console and issuing 'sudo dmesg -c' you show AND CLEAR the kernel messages.
Then by using programs and issuing dmesg commands, you should find which programs cause it (or avoid causing it [like cdread I suppose]).

On Fri, 23 Nov 2007 14:53:33 -0000 Paul Dufresne wrote:

> Does this happens only on commercial DVD (read movie DVD)?

I see this on commercial movie dvds but not with every. And I have
this with DVD-RAMs.

> It is still unclear to me which programs cause the: Apr 29 11:28:34
> localhost kernel: [10458.017362] attempt to access beyond end of
> device Apr 29 11:28:34 localhost kernel: [10458.017441] hdc: rw=0,
> want=8946808, limit=8388604

This messages comes with mplayer/totem trying to play a movie dvd. And
I get this messages when trying to read/write from/to a DVD-RAM.

Well, probably time to ask the normally requested info for kernel bugs.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

I had the same problem when trying to read from DVD-ROM (so no recordable), also at the 4GB border:

[10513.644000] attempt to access beyond end of device
[10513.644000] hdb: rw=0, want=16328340, limit=8388604
[10513.644000] Buffer I/O error on device hdb, logical block 4082084
(see complete log in attachment)

The problem vanished after stopping the packet writing tools
sudo /etc/init.d/udftools stop

So I suspect it has something to do with udftools. I also noticed that when writing DVD-RAMs with packet writing this silently fails (i.e. I do not get an I/O error at the prompt, but md5sum of written file reveals that it wasn't written correctly, there are also errors in dmesg in this case. Sorry, I don't have a log currently).

Get a similar problem on (uname:Linux cixci 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux) :
the DVD is mounted, but i'm unable to play it.

lspci :
jack@cixci:~$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03)
00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
05:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100
06:00.0 FireWire (IEEE 1394): JMicron Technologies, Inc. IEEE 1394 Host Controller
06:00.1 System peripheral: JMicron Technologies, Inc. SD/MMC Host Controller
06:00.2 SD Host controller: JMicron Technologies, Inc. Standard SD Host Controller
06:00.3 System peripheral: JMicron Technologies, Inc. MS Host Controller
06:00.4 System peripheral: JMicron Technologies, Inc. xD Host Controller
07:00.0 VGA compatible controller: nVidia Corporation GeForce 9600M GT (rev a1)

here is a part of dmesg :(rest in attachement)

 5543.148112] attempt to access beyond end of device
[ 5543.148127] sr0: rw=0, want=7918424, limit=7918420
[ 5543.151099] attempt to access beyond end of device
[ 5543.151112] sr0: rw=0, want=7918424, limit=7918420
[ 5545.130160] attempt to access beyond end of device
[ 5545.130185] sr0: rw=0, want=7918424, limit=7918420
[ 5545.130192] __ratelimit: 14 callbacks suppressed
[ 5545.130199] Buffer I/O error on device sr0, logical block 1979605
[ 5545.136934] attempt to access beyond end of device
[ 5545.136948] sr0: rw=0, want=7918424, limit=7918420
[ 5545.136954] Buffer I/O error on devi...

I also see this problem on two computers (A Thinkpad X200 with external LG USB drive, and a desktop system with an LG recorder). When copying data from DVDs, I sometimes get "input/output errors" with cp, and copying with nautilus fails, too, for files that seem to be beyond the first 1GiB of the disc. in dmes, I see lots of these:

[12122.860542] sr0: rw=0, want=2097556, limit=2097151
[12122.860543] attempt to access beyond end of device
[12122.860551] sr0: rw=0, want=2097560, limit=2097151
[12122.862244] attempt to access beyond end of device
[12122.862247] sr0: rw=0, want=2097152, limit=2097151
[12122.862409] attempt to access beyond end of device
[12122.862412] sr0: rw=0, want=2097152, limit=2097151

I am running current karmic amd64 on both systems with linux 2.6.31-11.

On the laptop, unplugging the DVD drive helps sometimes. On the desktop, I have to reboot the system. After some attempts, I can read the DVD+R to the end, so it is no media fault.

This just started happening to me with a recent upgrade in Karmic.

justinjstark@melmac:/dev$ lsdvd /dev/sg0
libdvdread: Using libdvdcss version 1.2.10 for DVD access
libdvdread: Can't seek to block 3492320
libdvdread: Can't seek to block 3492320
libdvdread: Invalid IFO for title 2 (VTS_02_0.IFO).
Can't open ifo 2!

dmesg is full of:

[ 709.022985] attempt to access beyond end of device
[ 709.022988] sr0: rw=0, want=13969332, limit=2097151
[ 709.057683] attempt to access beyond end of device
[ 709.057694] sr0: rw=0, want=13969328, limit=2097151
[ 709.057703] attempt to access beyond end of device
[ 709.057706] sr0: rw=0, want=13969332, limit=2097151

Hi Martin,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/lucid.

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 42023

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

I have the same issue as #30, trying to read files beyond the 1 GB position from a LG DVD ROM.

[24168.595674] sr0: rw=0, want=7875976, limit=2097151
[24168.595676] attempt to access beyond end of device
[24168.595679] sr0: rw=0, want=7875980, limit=2097151
[24168.595681] attempt to access beyond end of device
[24168.595683] sr0: rw=0, want=7875984, limit=2097151

Ubuntu 10.04 Lucid amd64 updated with EXT4 file system.

I can read without problems the DVD:
- creating an ISO Image from the DVD using GnomeBaker (maybe other softwares works as well)
- through a virtual machine (VMWare) running Windows XP or Ubuntu 10.10 Maverick

[Expired for udftools (Ubuntu) because there has been no activity for 60 days.]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]