Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #236397
| From | "Thomas Schmitt" <scdbackup@gmx.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Fatal error while burning CD |
| Date | 2021-06-24 09:20 +0200 |
| Message-ID | <CtrOx-5M-1@gated-at.bofh.it> (permalink) |
| References | <CtiLf-2VY-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hi, i wrote: > > What were your exact cdrskin arguments ? Michael Lange wrote: > cdrskin -v -dummy -eject dev=/dev/sr0 -sao speed=10 '04 Pujeva.wav' \ > sao_pregap=75 '05 New Pulse.wav' sao_pregap=225 '07 Rocket \ > Keronian.wav' '10 Dodo.wav' Looks quite unsuspicious. The sao_pregap= options might be rarely used. Option -dummy might bring the drive into a state where it pretends that the medium is written and has a non-empty table-of-content. But this illusion should end after ejection of the medium. > I repeated the exact same command immediately afterwards with the same > disc, and the second time it finished without errors. I am quite sure that cdrskin acts deterministically. So if the same preconditions yield a different outcome then i would blame it on the drive. Given that -dummy was used, i expect not much influence by the actual quality of the medium. (The error key 5 "Illegal Request" indicates a problem between firmware and burn program, anyway.) The fact that it accepted 34 WRITE(10) commands before it complains about the 35th makes me think that the error occurs when the drive actually begins to write. But error key 5 does not really match this occasion. It stays a riddle. > $ cdrskin dev=/dev/sr0 -minfo 2>&1 | tee -i /tmp/cdrskin_minfo > ... > Vendor_info : 'PLEXTOR' > Identifikation : 'DVDR PX-810SA' > Revision : '1.01' According to Google this drive iseems to have appeared around 2006. How old is yours ? > Maybe I should add that this or similar errors (I at least > clearly remember the "Sense key 5") occured with cdrdao with > blanks of different manufacturers. I'd expect cdrdao to act deterministically, too. > Once I tried to let cdrdao just finish > without interrupting it and to my utter surprise it produced a CD that > when inserted into the CD-player was recognized and reported with the > expected track count and duration. Looks like the table-of-content was sucessfully written. With SAO this happens before data writing begins. So yes, you should consider to get a new drive. DVD drives are cheap nowadays. Last time i got one, i had to send it back because of being unreliable with reading what it wrote. The replacement works well. (I suspect that the bad one was sent to the next customer. Nobody was interested in my problem report.) Personally, i'd rather get a BD drive for about 5 times the price. But if you are mainly into audio CD burning, this would be overdone. In any case, test it with all your intended use cases, as soon as it arrives. Have a nice day :) Thomas
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Fatal error while burning CD Michael Lange <klappnase@freenet.de> - 2021-06-23 19:40 +0200
Re: Fatal error while burning CD "Thomas Schmitt" <scdbackup@gmx.net> - 2021-06-23 21:00 +0200
Re: Fatal error while burning CD Michael Lange <klappnase@freenet.de> - 2021-06-23 23:40 +0200
Re: Fatal error while burning CD "Thomas Schmitt" <scdbackup@gmx.net> - 2021-06-24 09:20 +0200
Re: Fatal error while burning CD Michael Lange <klappnase@freenet.de> - 2021-06-24 11:30 +0200
Re: Fatal error while burning CD "Thomas Schmitt" <scdbackup@gmx.net> - 2021-06-24 12:20 +0200
Re: Fatal error while burning CD "Thomas Schmitt" <scdbackup@gmx.net> - 2021-06-24 14:20 +0200
Re: Fatal error while burning CD Michael Lange <klappnase@freenet.de> - 2021-06-25 00:50 +0200
Re: Fatal error while burning CD "Thomas Schmitt" <scdbackup@gmx.net> - 2021-06-25 08:50 +0200
Re: Fatal error while burning CD Michael Lange <klappnase@freenet.de> - 2021-06-25 10:30 +0200
Re: Fatal error while burning CD "Thomas Schmitt" <scdbackup@gmx.net> - 2021-06-25 11:50 +0200
Re: Fatal error while burning CD mcgarrett <dmcgarrett@optonline.net> - 2021-06-26 04:00 +0200
How to verify newly burned disc [Was: Fatal error while burning CD] Michael Lange <klappnase@freenet.de> - 2021-06-29 10:30 +0200
Re: How to verify newly burned disc [Was: Fatal error while burning CD] Linux-Fan <Ma_Sys.ma@web.de> - 2021-06-29 10:40 +0200
Re: How to verify newly burned disc [Was: Fatal error while burning CD] Michael Lange <klappnase@freenet.de> - 2021-06-29 11:10 +0200
Re: How to verify newly burned disc "Thomas Schmitt" <scdbackup@gmx.net> - 2021-06-29 12:10 +0200
Re: How to verify newly burned disc Michael Lange <klappnase@freenet.de> - 2021-07-02 09:10 +0200
Re: How to verify newly burned disc "Thomas Schmitt" <scdbackup@gmx.net> - 2021-07-02 12:30 +0200
Re: How to verify newly burned disc Michael Lange <klappnase@freenet.de> - 2021-07-02 20:00 +0200
Re: How to verify newly burned disc "Thomas Schmitt" <scdbackup@gmx.net> - 2021-07-02 21:30 +0200
Re: How to verify newly burned disc Michael Lange <klappnase@freenet.de> - 2021-07-03 01:00 +0200
Re: How to verify newly burned disc Stefan Monnier <monnier@iro.umontreal.ca> - 2021-07-03 04:50 +0200
Re: How to verify newly burned disc "Thomas Schmitt" <scdbackup@gmx.net> - 2021-07-03 10:50 +0200
Re: How to verify newly burned disc [Was: Fatal error while burning CD] Richmond <richmond@criptext.com> - 2021-07-02 22:20 +0200
Re: How to verify newly burned disc [Was: Fatal error while burning CD] Greg Wooledge <greg@wooledge.org> - 2021-07-02 22:40 +0200
Re: How to verify newly burned disc [Was: Fatal error while burning CD] Richmond <richmond@criptext.com> - 2021-07-02 23:30 +0200
Re: How to verify newly burned disc [Was: Fatal error while burning CD] Greg Wooledge <greg@wooledge.org> - 2021-07-02 23:40 +0200
Re: How to verify newly burned disc "Thomas Schmitt" <scdbackup@gmx.net> - 2021-07-03 00:00 +0200
csiph-web