[SOLVED] CD/DVD/BD/M-Disc drives not writing

dchmelik · 05-04-2013, 02:47 AM

I just built a new Slackware PC with an LG CD/DVD/BD/M-Disc writer, and a reader that reads maybe everything else but the M-Disc (and maybe not BD-DL.) I tried to write a plain OS DVD in K3B, and it says I do not have 'permission,' after it starts to write anyway and ruins the disc (though my user is in the cdrom group.) With cdrecord, it seems both 'cdrecord -scanbus,' 'crecord dev=help' give no info about devices that can be used. Do these drives even have Linux drivers yet? They just seemed like the standard new optical drive when I bought them.

business_kid · 05-04-2013, 11:35 AM

Are you on the standard kernel? Sounds like a kernel packet writing problem.

jefro · 05-04-2013, 04:38 PM

If you are trying to use a common disc in this then it should work as any drive should.

Try a live usb maybe of some other OS to double check.

M-disc's are meant to be read by common drives. They should also be supported by burning.

"Almost any DVD burning software will work with the M-WRITER™ drive. In fact, current operating systems ("Windows Vista"©, "Windows 7"©, "Mac OS X"© and many Linux© distributions) come with compatible software pre-installed and will recognise the M-Writer™ drive automatically. Additionally, the M-WRITER™ drive works with most common third party software. Some older operating systems such as "Windows XP"© will require third-party software as DVD burning software is not included by Microsoft™."

dchmelik · 05-04-2013, 07:08 PM

Quote:

Originally Posted by business_kid

Are you on the standard kernel? Sounds like a kernel packet writing problem.

yes

Quote:

Originally Posted by jeffro

If you are trying to use a common disc in this then it should work as any drive should. Try a live usb maybe of some other OS to double check.

Ok

Quote:

M-disc's are meant to be read by common drives. They should also be supported by burning.

As I said, I was using a plain DVD, not anything newer than that yet.

jefro · 05-04-2013, 10:11 PM

Then we are left to choose between OS, application and hardware.
Usually when it says no permission it tends to mean that. Some user level setting has not been enabled. I don't know how slackware does that. Some others here would know.

dchmelik · 05-04-2013, 10:22 PM

Quote:

Originally Posted by jefro

Then we are left to choose between OS, application and hardware.
Usually when it says no permission it tends to mean that. Some user level setting has not been enabled. I don't know how slackware does that. Some others here would know.

Slackware does it with the cdrom group, which my user is in, and it starts writing anyway, ruining the disc, then stops

business_kid · 05-05-2013, 04:09 AM

I would spend an hour with some of the strange options in cdrecord(now wodim?). He has information options, and tweaks to get around most buggy drives of the last millenium. This millenium, I'm not so sure. And if you do one more cd in a terminal with the verbose flag set it will tell you exactly what it meets.

jefro · 05-05-2013, 12:41 PM

Test with some other live usb installs or even put some windows on to test.

If the drive is new, it could be faulty.

Remove the drive and test on other system.

edorig · 05-08-2013, 09:40 AM

Quote:

Originally Posted by dchmelik

With cdrecord, it seems both 'cdrecord -scanbus,' 'crecord dev=help' give no info about devices that can be used.

Have you tried a dmesg |grep DVD ? If your drive is detected at boot, this should tell you the corresponding
device file. You could then try to do a cdrecord -dummy /dev/sd? and look at the error messages.
I think the 'permission denied' error message that you are getting is not related with the write permissions
on the drive, but with the possibility of setting the highest priority for the cdrecord process.
If that is the case, your cdrecord process may be interrupted by the scheduler while it is writing to
the disk, leading to a premature end of the CD writing process. In practice, it means that you will
need to be root to write CDs reliably. I have no idea whether cdrecord is secure enough to be made
setuid root.

business_kid · 05-08-2013, 11:37 AM

Quote:

Originally Posted by edorig

I have no idea whether cdrecord is secure enough to be made
setuid root.

Everyone is paranoid to a different level, but I would set it setuid root without a secondś hesitation. Itś solid.

dchmelik · 05-17-2013, 03:31 AM

I made a DVD with a Live DVD, so this appears to be a Slackware 14.0 problem or one of its kernel. Could any admin move this to the Slackware sub-forum?

Code:

root@cosmos:~# dmesg|grep dvd
[    8.565979] sr0: scsi3-mmc drive: 1x/1x writer dvd-ram cd/rw xa/form2 cdda tray
[    8.612057] sr1: scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw xa/form2 cdda tray
root@cosmos:~# cdrecord -dummy /dev/sd
cdrecord: No write mode specified.
cdrecord: Assuming -sao mode.
cdrecord: If your drive does not accept -sao, try -tao.
cdrecord: Future versions of cdrecord may have different drive dependent defaults.
Cdrecord-ProDVD-ProBD-Clone 3.01a08 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2012 Joerg Schilling
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open or use SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.

edorig · 05-17-2013, 01:54 PM

From the dmesg output, it appears that your CD-ROM drive is one of /dev/sr0 (slow one, 1x) or /dev/sr1 (fast one, 40x). The command to type is cdrecord -dummy /dev/sr0 or cdrecord -dummy /dev/sr1 (you don't have a /dev/sd device).
Concerning the writing of CDs and DVDs, cdrecord (CDs) and growisofs (DVDs) have different methods to write to
optical disk, so it is conceivable that only one of these programs is not compatible with your drive.
Can you determine the version of growisofs on the Live DVD growisofs --version and the installed one ?

business_kid · 05-17-2013, 02:01 PM

Quote:

cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open or use SCSI driver.

Depending on what you're using, you may need
/dev/sg0 & /dev/sg1
or
/dev/pg0 & /dev/pg1

Create them as symlinks in /dev to sr0, sr1.

Then try your luck.

dchmelik · 05-17-2013, 08:28 PM

oops... ok.

Code:

d@cosmos:~$ cdrecord -dummy /dev/sr0
cdrecord: No write mode specified.
cdrecord: Assuming -sao mode.
cdrecord: If your drive does not accept -sao, try -tao.
cdrecord: Future versions of cdrecord may have different drive dependent defaults.
Cdrecord-ProDVD-ProBD-Clone 3.01a08 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2012 Joerg Schilling
cdrecord: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.
cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2).
cdrecord: WARNING: This causes a high risk for buffer underruns.
cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler.
cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
cdrecord: WARNING: This causes a high risk for buffer underruns.
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open or use SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
d@cosmos:~$ cdrecord -dummy /dev/sr1
cdrecord: No write mode specified.
cdrecord: Assuming -sao mode.
cdrecord: If your drive does not accept -sao, try -tao.
cdrecord: Future versions of cdrecord may have different drive dependent defaults.
Cdrecord-ProDVD-ProBD-Clone 3.01a08 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2012 Joerg Schilling
cdrecord: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.
cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2).
cdrecord: WARNING: This causes a high risk for buffer underruns.
cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler.
cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
cdrecord: WARNING: This causes a high risk for buffer underruns.
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open or use SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.

Code:

root@cosmos:~# cdrecord -dummy /dev/sr0
cdrecord: No write mode specified.
cdrecord: Assuming -sao mode.
cdrecord: If your drive does not accept -sao, try -tao.
cdrecord: Future versions of cdrecord may have different drive dependent defaults.
Cdrecord-ProDVD-ProBD-Clone 3.01a08 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2012 Joerg Schilling
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open or use SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
root@cosmos:~# cdrecord -dummy /dev/sr1
cdrecord: No write mode specified.
cdrecord: Assuming -sao mode.
cdrecord: If your drive does not accept -sao, try -tao.
cdrecord: Future versions of cdrecord may have different drive dependent defaults.
Cdrecord-ProDVD-ProBD-Clone 3.01a08 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2012 Joerg Schilling
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open or use SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.

jefro · 05-17-2013, 08:52 PM

I get this from the output.

Cannot open '/dev/pg*'. Cannot open or use SCSI driver.
try 'cdrecord -scanbus'.
try 'cdrecord dev=help'.