Summary: | Write speed | ||
---|---|---|---|
Product: | [Applications] k3b | Reporter: | Simone Zorzetto <zorzetto.simone> |
Component: | Burning/Hardware | Assignee: | k3b developers <k3b> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | michalm, scdbackup, trueg |
Priority: | NOR | ||
Version: | 17.04.3 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Simone Zorzetto
2017-08-04 20:34:47 UTC
Hi,
the failure by
> :-[ WRITE@LBA=7e70h failed with SK=6h/NOT READY TO READY CHANGE,
> MEDIUM MAY HAVE CHANGED]: Input/output error
is not necessarily caused by the high speed. (Although i have heard
DVD+R derail inside the drive at 20x speed. What a noise.)
The drive had a moment of inconsciousness and then reports to have
recovered from that. Nevertheless its reply to the emergency exit
by SCSI command FLUSH CACHE says again that it is busy or brainless.
The progress messages say that drive speed had reached just 6.3x
before the failure happened.
About the speed setting: growisofs asks the drive for speeds and
chooses what it deems best for the given speed wish of the user.
Either the drive did not offer 8x speed or growisofs failed to
properly choose that speed.
Program dvd+rw-mediainfo will tell the speed values offered by
the drive for the given medium. So insert a blank DVD+R from the same
box or spindle. Close the tray. Then run
dvd+rw-mediainfo /dev/sr0
and look for lines like
Write Speed #0: 16.0x1385=22160KB/s
Write Speed #1: 12.0x1385=16620KB/s
Write Speed #2: 8.0x1385=11080KB/s
If there is no "8.0x" line, then the drive does not offer that speed.
(It would still be ok to request it to use 8x, but it will probably not
obey.)
Have a nice day :)
Thomas
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |