Bug 383140 - Write speed
Summary: Write speed
Status: RESOLVED WORKSFORME
Alias: None
Product: k3b
Classification: Applications
Component: Burning/Hardware (show other bugs)
Version: 17.04.3
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-04 20:34 UTC by Simone Zorzetto
Modified: 2022-12-06 05:21 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Simone Zorzetto 2017-08-04 20:34:47 UTC
I've set write speed to 8x to burn a dvd but the program have start job at maximum speed and have also failed:

Burned media
-----------------------
DVD+R

Devices
-----------------------
CDEmu Virt. CD/DVD-ROM 1.10 (/dev/sr1, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD+R) [DVD-ROM, DVD+R, CD-ROM, CD-R] [SAO, TAO, RAW, SAO/R96R, RAW/R16, RAW/R96R] [%7]
ATAPI iHBS212   2 HL05 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, BD-ROM, BD-R, BD-RE, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R sequenziale, DVD-R sequenziale a doppio strato, DVD-R jump a doppio strato, DVD-RAM, DVD-RW a riscrittura limitata, DVD-RW sequenziale, DVD+RW, DVD+R, DVD+R a doppio strato, CD-ROM, CD-R, CD-RW, BD-ROM, BD-R sequenziale (SRM), BD-R casuale (RRM), BD-RE] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Riscrittura limitata, Salto di livello, Registrazione casuale, Registrazione sequenziale, Registrazione sequenziale + POW] [%7]

System
-----------------------
K3b Version: 17.4.0
KDE Version: 5.31.0
Qt Version:  5.7.1
Kernel:      4.10.0-30-generic

Used versions
-----------------------
growisofs: 7.1

growisofs
-----------------------
Executing 'builtin_dd if=/dev/fd/0 of=/dev/sr0 obs=32k seek=0'
/dev/sr0: "Current Write Speed" is 16.4x1352KBps.
          0/4566968320 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU   0.0%
=== last message repeated 6 times. ===
   19857408/4566968320 ( 0.4%) @4.3x, remaining 91:35 RBU 100.0% UBU  16.3%
   48857088/4566968320 ( 1.1%) @6.3x, remaining 43:09 RBU 100.0% UBU  87.3%
:-[ WRITE@LBA=7e70h failed with SK=6h/NOT READY TO READY CHANGE, MEDIUM MAY HAVE CHANGED]: Input/output error
:-( write failed: Input/output error
/dev/sr0: flushing cache
:-[ FLUSH CACHE failed with SK=2h/LOGICAL UNIT NOT READY, LONG WRITE IN PROGRESS]: Resource temporarily unavailable
/dev/sr0: closing track
/dev/sr0: closing disc

growisofs command:
-----------------------
/usr/bin/growisofs -Z /dev/sr0=/dev/fd/0 -use-the-force-luke=notray -use-the-force-luke=tty -use-the-force-luke=4gms -use-the-force-luke=tracksize:2229965 -use-the-force-luke=dao:2229965 -dvd-compat -speed=8 -use-the-force-luke=bufsize:32m
Comment 1 Thomas Schmitt 2017-08-05 07:51:39 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
Comment 2 Justin Zobel 2022-11-06 09:24:46 UTC
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!
Comment 3 Bug Janitor Service 2022-11-21 05:14:55 UTC
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!
Comment 4 Bug Janitor Service 2022-12-06 05:21:39 UTC
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!