Bug 146573
Summary: | cdrecord does not blank CDRW in QSI drives; QSI drives do not support CDRW blanking with cdrecord | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | morgan read <mstuff> | ||||||||
Component: | cdrtools | Assignee: | Harald Hoyer <harald> | ||||||||
Status: | CLOSED WONTFIX | QA Contact: | |||||||||
Severity: | medium | Docs Contact: | |||||||||
Priority: | medium | ||||||||||
Version: | 8 | CC: | triage | ||||||||
Target Milestone: | --- | Keywords: | Reopened | ||||||||
Target Release: | --- | ||||||||||
Hardware: | i686 | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | bzcl34nup | ||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2009-01-09 06:52:00 UTC | Type: | --- | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
morgan read
2005-01-29 22:16:29 UTC
Created attachment 110412 [details]
output of cdrecord -scanbus
Created attachment 110413 [details]
output of cdrecord speed=2 blank=all dev=ATA:1,0,0 -v
i can confirm this bug, see the two attachments i've sent Created attachment 110414 [details]
output of cdrecord speed=2 blank=all dev=1,0,0 -v
btw, i'm using an up-to-date FC3
*** This bug has been marked as a duplicate of 145865 *** No it's not. See comment at https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145865#c6 Morgan. Hi Morgan, FC3 is now being maintained by Fedora Legacy. We only focus on security issues, since FC3 has entered maintenance mode. According to bug #13729 at launchpad.net (that is, <https://launchpad.net/distros/fedora/+source/cdrtools/+bug/13729/+viewstatus>), which deals with problems blanking CDRW's in QSI drives: "It is impossible to burn a cd-rw with nautilus. It opens druid if empty cd-rw is inserted, but reports an error. However it is possible to burn a cd-rw with cdrecord (with different frontends). It is impossible to erase a cd-rw with cdrecord (CLI or with frontend like xcdroast). However, it is possible to erase a cd-rw with cdrdao." So it looks like there are some workarounds for this problem. I am closing this bug, because we in Fedora Legacy don't know how to fix this problem and there appear to be workarounds. However, if you are now using FC4 or FC5, and are still encountering this problem, you are welcome to reopen the bug and reassign it to Fedora Core 4 or 5, so it can go back into Red Hat's queue. Have you submitted a bug report on this to the upstream maintainers of cdrecord? You might consider doing that too, Morgan, if you haven't already. Sorry we cannot do any more on this. No worries here. I'm on fc5, it's still the same bug, but whether the bug's with the software or the hard ware I guess is a moot point. Does work with cdrdao. I'm not sure of the protocol - does one just keep updating the bug as one upgrades through the core versions? I've long since realised the hardware's cr#p. QSI is junk, so more than agree 'wontfix' might be best resolution - but, will reopen for fc5 and let someone more knowledgable than I make that decision. As suggested I posted a bug report to the maintainer of cdrtools - Jörg Schilling, somehow I suspect he's not going to be so interested (just the impression I get from his website:). Who is the relevant maintainer of cdrtools as used by fc? me Oh, good. Looks like there may be a fix to this in the "-immed" option to cdrecord? See: https://launchpad.net/distros/fedora/+source/cdrtools/+bug/13729 (See also the man page for "-immed".) PS My suspicions were correct. But, from amongst the noise was this comment: > BTW: The most probable reason for your problem is a linux kernel bug. > > The Linux kernel does most likely modify the SCSI command. > > I had a similar experience a few years ago. Booting the same Hardware > with Solaris did cure the problem. Fedora Core 5 is no longer maintained. Is this bug still present in Fedora 8? Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers [root@morgansoldmachine ~]# uname -r 2.6.24.3-34.fc8 [root@morgansoldmachine ~]# cdrecord blank=all -force dev=/dev/cdrw Device type : Removable CD-ROM Version : 5 Response Format: 2 Capabilities : Vendor_info : 'QSI ' Identification : 'DVD/CDRW SBW-081' Revision : 'NXC5' Device seems to be: Generic mmc2 DVD-ROM. Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-2 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Speed set to 706 KB/s Waiting for drive to calm down. Starting to write CD/DVD at speed 4.0 in real force BLANK mode for single session. Last chance to quit, starting real write in 0 seconds. Operation starts. Errno: 5 (Input/output error), blank unit scsi sendcmd: no error CDB: A1 00 00 00 00 00 00 00 00 00 00 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 24 00 00 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x24 Qual 0x00 (invalid field in cdb) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.000s timeout 9600s Starting to write CD/DVD at speed 4.0 in real force BLANK mode for single session. No chance to quit anymore. Operation starts. Errno: 5 (Input/output error), blank unit scsi sendcmd: no error CDB: A1 00 00 00 00 00 00 00 00 00 00 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 24 00 00 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x24 Qual 0x00 (invalid field in cdb) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.000s timeout 9600s wodim: Cannot blank disk, aborting. [root@morgansoldmachine ~]# Looks like it's still a bug in f8 M. This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '8'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 8's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 8 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |