@ Bruno

Please reassign if the real culprit isn't dvd+rw-tools

CC: (none) => doktor5000, marja11
Assignee: bugsquad => bruno
Source RPM: (none) => dvd+rw-tools

For reference, related issues were reported in forums, see URL field. https://forums.mageia.org/en/viewtopic.php?f=7&t=10909

Last time this worked for me was with mga2 or mga3 IIRC, the same DVD-RAM used then (which is still readable now) is not recognised in either k3b or brasero as writeable or erasable media.

FWIW, after manually loading the module "pktcdvd" for packet writing and then mounting the DVD-RAM with "mount -t udf -o rw,noatime,async,users /dev/pktcdvd/dvdram /media/dvdram" I can normally write to the DVD-RAM as a regular harddisk as expected, so not sure there really is any culprit here.


This is what dvd+rw-tools says about the disk:

[doktor5000@Mageia5]â[20:02:46]â[~] dvd+rw-format /dev/dvdrw 
* BD/DVD±RW/-RAM format utility by <appro@fy.chalmers.se>, version 7.1.
* 4.6GB DVD-RAM media detected.
- media is already formatted, lead-out is currently at
  4473408 KiB which is 100.0% of total capacity.
- you have the option to re-run dvd+rw-format with:
  -format=full  to perform full (lengthy) reformat;
  -ssa[=none|default|max]
                to grow, eliminate, reset to default or
                maximize Supplementary Spare Area.

[doktor5000@Mageia5]â[19:58:50]â[~] sudo dvd+rw-mediainfo /dev/dvdrw 
INQUIRY:                [HL-DT-ST][BD-RE  BH16NS40 ][1.03]
GET [CURRENT] CONFIGURATION:
 Mounted Media:         12h, DVD-RAM
 Current Write Speed:   3.0x1385=4155KB/s
 Write Speed #0:        3.0x1385=4155KB/s
 Speed Descriptor#0:    00/2040094 R@5.0x1385=6925KB/s W@3.0x1385=4155KB/s
READ DVD STRUCTURE[#0h]:
 Media Book Type:       00h, DVD-ROM book [revision 0]
 Legacy lead-out at:    2314080*2KB=4739235840
DVD-RAM SPARE AREA INFORMATION:
 Primary SA:            6784/12800=53.0% free
 Supplementary SA:      58368/58368=100.0% free
DVD-RAM WRITE PROTECTION STATUS:
 Persistent Write Protection is off
READ DISC INFORMATION:
 Disc status:           other
 Number of Sessions:    1
 State of Last Session: complete
 "Next" Track:          1
 Number of Tracks:      1
READ FORMAT CAPACITIES:
 formatted:             2236704*2048=4580769792
 00h(800):              2236704*2048=4580769792
 00h(800):              2295072*2048=4700307456
 01h(800):              2226976*2048=4560846848
 01h(800):              2217248*2048=4540923904
FABRICATED TOC:
 Track#1  :             14@0
 Track#AA :             14@2236704
 Multi-session Info:    #1@0
READ CAPACITY:          2236704*2048=4580769792


What I also noticed is that we don't have any udev rules for DVD-RAM devices/media:

[doktor5000@Mageia5]â[19:50:20]â[~] grep -Ri dvdram /usr/lib/udev/rules.d/
[doktor5000@Mageia5]â[19:51:01]â[~]

No clue what to do of that bug :-( And I don't have the related HW to perform any test myself.

(In reply to Bruno Cornec from comment #3)
> No clue what to do of that bug :-( And I don't have the related HW to
> perform any test myself.

CC'ing pkg-bugs@ml

CC: (none) => pkg-bugs
Whiteboard: (none) => NEEDHELP

Hi Michael,

Thank you for having taken the needed time to report this issue!

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja

@ Michael:

No reply, so closing as OLD since Mageia 5 is no longer maintained.

==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==

Resolution: (none) => OLD
Status: NEW => RESOLVED