Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've burned a data DVD-R with K3B. K3B did verify it successfully.
I haven't used the entire capacity (4.3 GB), there were approx. 250 MB to spare.
The DVD can be mounted, but the files that have been written last, are not readable under Linux. (This is a dual boot machine, and the files in question are readable with Windows)
Apparently there is an upper limit, and any attempt to read beyond that fails.
Can the limit be changed? Or is it determined automatically? Why can K3B read these sectors but not the "normal" OS?
/var/log/messages
Code:
May 23 01:18:16 localhost kernel: [4298007.805000] hdc: rw=0, want=8475852, limit=8388604
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=8475856, limit=8388604
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=8475860, limit=8388604
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=8475800, limit=8388604
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
I had the same problem.
I thought I had heard something about a 2.6 kernel hack for this somewhere, but that was some time back.
Did you try a
# dd if=/dev/what-have-you of=dvd_image.iso
??
I tried this on my DVD-ROM and that didn't work, but from the DVDRW it did.
Jan 28 11:39:45 linux kernel: attempt to access beyond end of device
Jan 28 11:39:45 linux kernel: hda: rw=0, want=8388624, limit=8388604
Jan 28 11:39:45 linux kernel: Buffer I/O error on device hda, logical
block 2097155
The cause of this problem is brilliantly discussed in detail in: http://lkml.org/lkml/2006/11/23/182
To sum up, when something has previously tried to open the cdrom, it can cause the kernel to stay locked on the wrong assumptions about the device (i.e. its maximum size).
Usually, that something is the pktsetup instruction, as described in: http://lists.opensuse.org/archive/pa.../msg00022.html
In Debain, all one has to do is:
/etc/init.d/udftools stop
for everything to return to work fine.
Chances are this will repair also the message "inappropiate ioctl for device" if that happens to you when using the eject command.
I forgot to make clear that, whenever you want to use packet writing again, you will have to execute:
/etc/init.d/udftools start
(in Debian). Remember to stop it when you are finished, or the "beyond end of device" could happen again.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.