Bug#438631: setting package to cdck, tagging 438631
# Automatically generated email from bts, devscripts version 2.10.18.1 # # cdck (0.7.0-1) unstable; urgency=low # # * New upstream release: adds a warning about misleading error output #(closes: #438631). # package cdck tags 438631 + pending -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#438631:
On Sat, 18 Aug 2007 17:45:06 +0200, gregor herrmann wrote: I'll check with the upstream author. Good idea. Maybe I'm just misunderstanding the output of cdck, or maybe my test CDs where burnt incorrectly. Yup, I've contacted him already, hopefully he can shed some light on our questions. Just a short note for those watching along at home: I've contacted Alexey again, and he has promised to look into the issue (probably by improving the documentation). Cheers, gregor -- .''`. http://info.comodo.priv.at/ | gpg key ID: 0x00F3CFE4 : :' : debian: the universal operating system - http://www.debian.org/ `. `' member of https://www.vibe.at/ | how to reply: http://got.to/quote/ `-NP: Juilliard Ensemble, Berberian,: Due pezzi für Violine und Klav signature.asc Description: Digital signature
Bug#438631: =?ISO-8859-1?Q?Spurious(?) I/O error?= s at end of CD-R
Package: cdck Version: 0.6.0-1 If I use cdck to verify a CD-R or CD-RW, it reports unreadable sectors at the end of the disc for several discs which are perfectly readable (I even verified MD5 sums for one disc). Log: iota:~$ cdck Reading sectors 1-27280 ! unable to read sector 27259, reason: Input/output error [...all sectors in between with same message...] ! unable to read sector 27280, reason: Input/output error CD overall: Sectors total: 27280: Good sectors: 27258: Bad sectors (incl. with poor timing): 22 CD timings: Minimal = 5 usec (0.05s) Maximal = 99340 usec (0.099340s) Average = 1161 usec (0.001161s) Conclusion: Disc contains BAD or even readable sectors, put it into trash can! This occured for several discs. The number of bad sectors reported varies from 14 to 24, but it is always the last sectors. Maybe cdck incorrectly detects the end of a CD? I also tried a real, pressed CD from retail: The problem did not occur. additional info- Here are excerpted logs for some CDs I tested. They were burnt on different drives. I also included the volume size as reported by isoinfo -d (the line Volume size is:). Strangely, it does not agree with what cdck reports. CD-R, burnt on Windows: Reading sectors 1-197640 ! unable to read sector 197627, reason: Input/output error ! unable to read sector 197640, reason: Input/output error Volume size is: 197488 CD-RW, burnt with mkisofs/cdrecord: Reading sectors 1-68879 ! unable to read sector 68859, reason: Input/output error ... ! unable to read sector 68879, reason: Input/output error Volume size is: 68877 CD-RW, burnt with mkisofs/cdrecord: Reading sectors 1-245488 ! unable to read sector 245435, reason: Input/output error ... ! unable to read sector 245488, reason: Input/output error Volume size is: 245486 CD-R, burnt on Windows: Reading sectors 1-27280 ! unable to read sector 27259, reason: Input/output error ! unable to read sector 27280, reason: Input/output error Volume size is: 27128 Tests done on CD drive: DVD/CD-RW, Compaq Armada M700 builtin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#438631: =?ISO-8859-1?Q?Spurious(?) I/O error?= s at end of CD-R
On Sat, 18 Aug 2007 14:53:28 +0200, [EMAIL PROTECTED] wrote: Hi Sebastian, thanks for taking the time to report this issue! If I use cdck to verify a CD-R or CD-RW, it reports unreadable sectors at the end of the disc for several discs which are perfectly readable (I even verified MD5 sums for one disc). I'm not sure if this is a bug -- or actually a feature. cdcd's purpose is not to check for un/readable files but for bad sectors. From the README: The known fact is that even if all files on the disc are readable, some sectors having bad timing can easily turn into unreadable ones in the future. In my understanding cdck tries to find problematic factors that _might_ make sectors unreadable in the _future_, and it warns about these sectors. [quoting resorted] This occured for several discs. The number of bad sectors reported varies from 14 to 24, but it is always the last sectors. I also tried a real, pressed CD from retail: The problem did not occur. I did some tests now with some of my CDs. Results: * Burnt ISO (bootable, 1 track): bad sectors at the end. * A random hardware driver CD: no errors. * Burnt data disc (mutlisession, 5 tracks): bad sectors all around. Ok, bad example. * Another burnt iso (bootable, 1 track, rather small): no errors. * A third burnt iso (bootable, 1 track): bad sectors at the end. * Another burnt data CD (1 track, rather small): no errors. * Another random software CD from some vendor (1 track, long but not full): tons of errors, ok. * Some random data CD burnt by a vendor (1 track, rather small): no errors Hm, I'm not sure what these results actually tell me ... Maybe cdck incorrectly detects the end of a CD? I'll check with the upstream author. Here are excerpted logs for some CDs I tested. They were burnt on different drives. I also included the volume size as reported by isoinfo -d (the line Volume size is:). Strangely, it does not agree with what cdck reports. That doesn't seem strange to me -- isoinfo checks the size of an iso file, on the CD there might be more sectors because of the lead in and lead out. cdck -v shows some info on the structure of the CD. Cheers, gregor -- .''`. http://info.comodo.priv.at/ | gpg key ID: 0x00F3CFE4 : :' : debian: the universal operating system - http://www.debian.org/ `. `' member of https://www.vibe.at/ | how to reply: http://got.to/quote/ `-NP: Arlo Guthrie: Coming into LA signature.asc Description: Digital signature
Bug#438631:
Hi, thanks for the super-fast reply. I'm not sure if this is a bug -- or actually a feature. cdcd's purpose is not to check for un/readable files but for bad sectors. From the README: The known fact is that even if all files on the disc are readable, some sectors having bad timing can easily turn into unreadable ones in the future. In my understanding cdck tries to find problematic factors that _might_ make sectors unreadable in the _future_, and it warns about these sectors. Yes, that is true. However, the message unable to read sector XXX, reason: Input/output error looks to me like cdck found a hard error, not just bad timing. That would mean that that sector is already unreadable, and the file which uses it should in consequence also be unreadable. Still, all files on the disc are OK, that is what I do not understand. Maybe cdck incorrectly detects the end of a CD? I'll check with the upstream author. Good idea. Maybe I'm just misunderstanding the output of cdck, or maybe my test CDs where burnt incorrectly. In that case, it might be enough to add a note to the docs about possible reasons for read errors and when these are harmless - or not. Greetings, Sebastian Leske -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#438631:
On Sat, 18 Aug 2007 17:14:43 +0200, Sebastian Leske wrote: thanks for the super-fast reply. You're welcome. In my understanding cdck tries to find problematic factors that _might_ make sectors unreadable in the _future_, and it warns about these sectors. Yes, that is true. However, the message unable to read sector XXX, reason: Input/output error looks to me like cdck found a hard error, not just bad timing. That would mean that that sector is already unreadable, and the file which uses it should in consequence also be unreadable. Right, if a file is actually using this sector ... (which might not be the case for the very last sectors of the CD) I'll check with the upstream author. Good idea. Maybe I'm just misunderstanding the output of cdck, or maybe my test CDs where burnt incorrectly. Yup, I've contacted him already, hopefully he can shed some light on our questions. In that case, it might be enough to add a note to the docs about possible reasons for read errors and when these are harmless - or not. Right. Cheers, gregor -- .''`. http://info.comodo.priv.at/ | gpg key ID: 0x00F3CFE4 : :' : debian: the universal operating system - http://www.debian.org/ `. `' member of https://www.vibe.at/ | how to reply: http://got.to/quote/ `- signature.asc Description: Digital signature
