I have a problem with overwriting dvd+rw discs with k3b. When the disc contains data and I want to format it and burn something else onto the disc K3b asks if I want to automatically format the dvd-rw before burning the new contents. When I answer yes, K3b starts formatting the disc afterwhich it always reports that the formatting was unsuccessful. After the failed formatting the disc seems totally trashed, I cannot mount it and the system can't even recognize the medium. Reloading the disc/tray doesn't help.

here follows some commandline debugging;

#dmesg

sr 1:0:1:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 2098.027325] sr 1:0:1:0: [sr0] Sense Key : Illegal Request [current]
[ 2098.027332] Info fld=0x0
[ 2098.027335] sr 1:0:1:0: [sr0] Add. Sense: Logical block address out of range
[ 2098.027343] end_request: I/O error, dev sr0, sector 0
[ 2098.027350] Buffer I/O error on device sr0, logical block 0
[ 2098.027356] Buffer I/O error on device sr0, logical block 1
[ 2098.027362] Buffer I/O error on device sr0, logical block 2
[ 2098.027366] Buffer I/O error on device sr0, logical block 3
[ 2098.027370] Buffer I/O error on device sr0, logical block 4
[ 2098.027374] Buffer I/O error on device sr0, logical block 5
[ 2098.027377] Buffer I/O error on device sr0, logical block 6
[ 2098.027381] Buffer I/O error on device sr0, logical block 7
[ 2098.027385] Buffer I/O error on device sr0, logical block 8
[ 2098.027389] Buffer I/O error on device sr0, logical block 9
[ 2098.033335] sr 1:0:1:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 2098.033344] sr 1:0:1:0: [sr0] Sense Key : Illegal Request [current]
[ 2098.033351] Info fld=0x0
[ 2098.033353] sr 1:0:1:0: [sr0] Add. Sense: Logical block address out of range
[ 2098.033361] end_request: I/O error, dev sr0, sector 0
[ 2516.710608] sr0: CDROM not ready yet.

#dvd+rw-format -force /dev/dvdrw1
* BD/DVD±RW/-RAM format utility by <appro@fy.chalmers.se>, version 7.1.
:-( mounted media doesn't appear to be DVD±RW, DVD-RAM or Blu-ray

#wodim -format -force /dev/dvdrw1
wodim: No write mode specified.
wodim: Asuming -tao mode.
wodim: Future versions of wodim may have different drive dependent defaults.
Device was not specified. Trying to find an appropriate drive...
Detected CD-R drive: /dev/sr0
Error trying to open /dev/sr0 exclusively (Device or resource busy)... retrying in 1 second.
Device type : Removable CD-ROM
Version : 5
Response Format:
Capabilities :
Vendor_info : 'HL-DT-ST'
Identification : 'DVDRAM GSA-4167B'
Revision : 'DL13'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Using generic SCSI-3/mmc DVD-R(W) driver (mmc_mdvd).
Driver flags : SWABAUDIO BURNFREE
Supported modes: PACKET SAO
wodim: Track 1 has unknown length.
wodim: Use tsize= option in SAO mode to specify track size.

#dvd+rw-mediainfo /dev/dvdrw1
INQUIRY: [HL-DT-ST][DVDRAM GSA-4167B][DL13]
GET [CURRENT] CONFIGURATION:
Mounted Media: 14h, DVD-RW Sequential
Media ID: RITEKW01
Current Write Speed: 2.0x1385=2770KB/s
Write Speed #0: 2.0x1385=2770KB/s
GET [CURRENT] PERFORMANCE:
Write Performance: 2.0x1385=2770KB/s@[0 -> 2298495]
Speed Descriptor#0: 02/2298495 R@3.3x1385=4584KB/s W@2.0x1385=2770KB/s
READ DVD STRUCTURE[#0h]:
Media Book Type: 00h, DVD-ROM book [revision 0]
Legacy lead-out at: 2298496*2KB=4707319808
READ DISC INFORMATION:
Disc status: blank
Number of Sessions: 1
State of Last Session: empty
"Next" Track: 1
Number of Tracks: 1
READ FORMAT CAPACITIES:
unformatted: 2297888*2048=4706074624
00h(800): 2297888*2048=4706074624
10h(10): 2297888*2048=4706074624
15h(10): 2297888*2048=4706074624
READ TRACK INFORMATION[#1]:
Track State: blank
Track Start Address: 0*2KB
Next Writable Address: 0*2KB
Free Blocks: 2298496*2KB
Track Size: 2298496*2KB
READ CAPACITY: 0*2048=0

So, with wodim's format I can get the disc into useable state again. Can someone explain what goes under the hood here and why does K3b fail to format the disc everytime.

I'm not 100% sure but this seems to happen only when I want to automatically erase the disc and burn the new contents immediately.
If I first format the disc and try to burn after that it works. Is the device too slow to respond or what can cause behavior like this?

My K3B always does this on FC11 with a certain type of Verbatim DVD-RW. However, after it has reported the error I just reinsert the disc and then it writes 100% correctly. All the data is on the DVD at the end of the operation and it is readable... doesn't this happen there too?

Appears to be a glitch / false error... at least in my FC11 setup.

rylan76, does this happen to you only with Verbatim discs?
I think this bug is more linux related than anything else. I would have to verify this but I'm fairly sure there would be no errors like this under FreeBSD.
This is off topic but under FreeBSD everything works just like it should, but with linux I'm constantly battling with errors that shouldn't be present in production quality systems. Sadly, I can't get the desktop/system management comfort that the distribution I use offers with anything *BSD variant. (ports is good, but the less CLI for basic stuff, the better).

Yes, it only happens with some Verbatim DVD-RW discs I bought about a year ago.

K3B always complains it cannot format the disc when I rewrite it, but then I just re-insert the same disc, and there it goes... Other DVD-RW discs (non - Verbatim brandnames) work just fine from the get-go.

BTW, I seem to have the EXACT same model of LG DVD-RW drive you have...!

Not sure, I think it might be something to do with the model / type of disc used, in combination with the LG "HL-DT-ST" range of drives?

Hmm I like the CLI. I get nervous when you must do most stuff "automagically" in the GUI, without the precise control you get when using the CLI and typing commands to get stuff done. The trend though does seem to be to go more "GUI-ey" with a lot of things. However, I have found that if you WANT to go CLI, you usually CAN, at least up to Fedora 11 which is my current distro. Can't speak for BSD, never even seen a system that runs it.

Yeah, Linux might be a bit more unstable or fiddly than BSD, but I think that is a side effect of a quite lively and vibrant community doing constant, strong development of the kernel, drivers, etc.