LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 05-14-2007, 07:44 AM   #1
slackware-elf
LQ Newbie
 
Registered: Sep 2006
Distribution: Slackware
Posts: 15

Rep: Reputation: 0
k3b breaks on multisession CD burn, Slack 11, Linux 2.6?


Hi all!

Anyone else had problems with k3b after moving to Slack 11 and a 2.6.x kernel?

Actually, the problem is below k3b. With a 2.4 kernel, my lilo.conf had the old SCSI emulation line, and I could use cdrecord and mkisofs with dev=0,0,0 and it all worked here on my Thinkpad T21. In 2.6, I removed SCSI emulation, as recommended, and cdrecord can no longer find any device to work with.

Code:
root@strawberry 08:32 slackpkg $ cdrecord dev=help
Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
cdrecord: Warning: Running on Linux-2.6.17.13
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
Supported SCSI transports for this platform:

Transport name:         sg
Transport descr.:       Generic transport independent SCSI
Transp. layer ind.:
Target specifier:       bus,target,lun
Target example:         1,2,0
SCSI Bus scanning:      supported
Open via UNIX device:   not supported

Transport name:         pg
Transport descr.:       SCSI transport for ATAPI over Parallel Port
Transp. layer ind.:
Target specifier:       bus,target,lun
Target example:         1,2,0
SCSI Bus scanning:      supported
Open via UNIX device:   not supported

Transport name:         ATA
Transport descr.:       ATA Packet specific SCSI transport
Transp. layer ind.:     ATAPI:
Target specifier:       bus,target,lun
Target example:         ATAPI:1,2,0
SCSI Bus scanning:      supported
Open via UNIX device:   not supported

Transport name:         ATA
Transport descr.:       ATA Packet specific SCSI transport using sg interface
Transp. layer ind.:     ATA:
Target specifier:       bus,target,lun
Target example:         1,2,0
SCSI Bus scanning:      supported
Open via UNIX device:   not supported

Transport name:         RSCSI
Transport descr.:       Remote SCSI
Transp. layer ind.:     REMOTE:
Target specifier:       rscsi@host:bus,target,lun
Target example:         REMOTE:rscsi@host:1,2,0
SCSI Bus scanning:      supported
Open via UNIX device:   not supported
Everything's "not supported." cdrecord -scanbus is worse.

Code:
root@strawberry 08:33 slackpkg $ cdrecord -scanbus
Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
cdrecord: Warning: Running on Linux-2.6.17.13
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
In the good old days, I think that gave me "0,0,0".

However, when I run k3b, I get a partial success. Possibly k3b just uses "/dev/hdc", which is the ultimate destination of my /dev/cdrom symlink. In k3b, I can burn a whole CD, and I can START a multisession CD, then burn one additional session. But after that, k3b gets a mkisofs error and refuses to burn additional sessions.

Here's the output from when I try to burn an additional multisession to a CD that has been burned entirely with k3b so far:

Code:
System
-----------------------
K3b Version: 0.12.17

KDE Version: 3.5.4
QT Version:  3.3.6
Kernel:      2.6.17.13
Devices
-----------------------
HL-DT-ST RW/DVD GCC-4240N 1203 (/dev/hdc, ) at /mnt/cdrom [CD-R; CD-RW; CD-ROM; DVD-ROM] [DVD-ROM; CD-ROM; CD-R; CD-RW] [SAO; TAO; RAW; SAO/R96P; SAO/R96R; RAW/R16; RAW/R96P; RAW/R96R]

mkisofs
-----------------------
/usr/bin/mkisofs: Input/output error. Read error on old image

mkisofs command:
-----------------------
/usr/bin/mkisofs -cdrecord-params 24759,36239 -prev-session /dev/hdc -gui -graft-points -volid K3b data project -volset  -appid K3B THE CD KREATOR (C) 1998-2005 SEBASTIAN TRUEG AND THE K3B TEAM -publisher  -preparer  -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-bill/k3bqdYzob.tmp -rational-rock -hide-list /tmp/kde-bill/k3bxkC0kc.tmp -joliet -hide-joliet-list /tmp/kde-bill/k3bC8ti4a.tmp -full-iso9660-filenames -iso-level 2 -path-list /tmp/kde-bill/k3b60O5Ha.tmp 

msinfo
-----------------------
24759,36239

msinfo command:
-----------------------
/usr/bin/cdrecord dev=/dev/hdc -msinfo
That's burning in TAO mode, with "Continue multisession" set.

Anyhow, I don't know if this is a k3b thing, or a kernel thing, or what. I'm just wondering if anyone else has had this particular problem. Looking at other posts, I'm grateful that I can at least burn CDs, but incremental backups get a little silly when you have to start a new CD after 30MB or so.

Thanks for taking a look.
Bill Powell

Last edited by slackware-elf; 05-14-2007 at 07:46 AM.
 
Old 05-14-2007, 09:39 AM   #2
Lenard
Senior Member
 
Registered: Dec 2005
Location: Indiana
Distribution: RHEL/CentOS/SL 5 i386 and x86_64 pata for IDE in use
Posts: 4,790

Rep: Reputation: 56
Try typing something like: cdrecord dev=ATA -scanbus

Also you really should update k3b: http://k3b.plainblack.com/
 
Old 05-14-2007, 10:00 AM   #3
slackware-elf
LQ Newbie
 
Registered: Sep 2006
Distribution: Slackware
Posts: 15

Original Poster
Rep: Reputation: 0
Thanks, Lenard!

I tried your command, and it seemed to work:

Code:
root@strawberry 10:52 bill $ cdrecord dev=ATA -scanbus
Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
cdrecord: Warning: Running on Linux-2.6.17.13
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
scsidev: 'ATA'
devname: 'ATA'
scsibus: -2 target: -2 lun: -2
Warning: Using badly designed ATAPI via /dev/hd* interface.
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
scsibus1:
        1,0,0   100) 'HL-DT-ST' 'RW/DVD GCC-4240N' '1203' Removable CD-ROM
        1,1,0   101) *
        1,2,0   102) *
        1,3,0   103) *
        1,4,0   104) *
        1,5,0   105) *
        1,6,0   106) *
        1,7,0   107) *
But when I try to burn to that device, it still won't work. New error, though.

Code:
root@strawberry 10:52 bill $ cdrecord -v -dev=1,0,0 backup.iso
cdrecord: No write mode specified.
cdrecord: Asuming -tao mode.
cdrecord: Future versions of cdrecord may have different drive dependent defaults.
cdrecord: Continuing in 5 seconds...
Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
cdrecord: Warning: Running on Linux-2.6.17.13
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
TOC Type: 1 = CD-ROM
scsidev: '1,0,0'
scsibus: 1 target: 0 lun: 0
cdrecord: No such file or directory. Cannot open '/dev/sg*'. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
Is there something I need to do to enable SCSI access? Like the line you used to put in lilo.conf for the 2.4 kernel? I thought 2.6 was supposed to just work.

Anyhow, thanks very much for the suggestion. Now I know the device number.

Bill
 
Old 05-14-2007, 10:08 AM   #4
Alien_Hominid
Senior Member
 
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247

Rep: Reputation: 53
If you have atapi (ide) cd-rom, scsi should be disabled in 2.6 kernel.
 
Old 05-14-2007, 10:34 AM   #5
Lenard
Senior Member
 
Registered: Dec 2005
Location: Indiana
Distribution: RHEL/CentOS/SL 5 i386 and x86_64 pata for IDE in use
Posts: 4,790

Rep: Reputation: 56
Try: cdrecord -v -dev=/dev/cdrom backup.iso

or adjust for your actual CD/DVD device; ls -al /dev/cdrom

$ ls -al /dev/cdrom
lrwxrwxrwx 1 root root 4 May 14 10:45 /dev/cdrom -> scd0

Same command adjusted: cdrecord -v dev=/dev/scd0 backup.iso
 
Old 05-14-2007, 10:50 AM   #6
masonm
Senior Member
 
Registered: Mar 2003
Location: Following the white rabbit
Distribution: Slackware64 13.37 Android 4.0
Posts: 2,248

Rep: Reputation: 46
You can also try re-running the k3bsetup2 app.
 
Old 05-14-2007, 01:32 PM   #7
slackware-elf
LQ Newbie
 
Registered: Sep 2006
Distribution: Slackware
Posts: 15

Original Poster
Rep: Reputation: 0
Fix: upgraded k3b to 1.0.1

Looks like the suggestion to upgrade was the winner. The k3b with Slack 11 is like 0.12 or something. I should have known I should upgrade when I saw a k3b package on http://linuxpackages.net. (Note: I also had to download the libdvdread package off the same site. The other dependencies seemed to come with my Slack 11 install.) In the changelog for k3b 1.0.1, it mentions a fix that involves broken ISOs in previous versions. I just burned 5 tracks, so it looks like they fixed it.

However, I still appreciate all the command-line suggestions, because my goal is to have a shell script for my daily backups. I'll post back here when I figure out what's up. In the meantime, it's nice to have k3b working.

Thanks, all!
Bill
 
Old 06-02-2007, 09:44 AM   #8
slackware-elf
LQ Newbie
 
Registered: Sep 2006
Distribution: Slackware
Posts: 15

Original Poster
Rep: Reputation: 0
Or is it an mkisofs problem?

Hey folks,

Thanks for the great suggestions so far. I THOUGHT the new k3b was working...but after that first test, things soured. I kept getting this message:

Read error on old image

So I went back to the command line, installed the most recent cdrtools. And a similar thing happened. I THOUGHT I got mkisofs so I could burn multiple sessions. But now I'm finding that after one, maybe two sessions, I get that error again. Why can't it read the old image, blast it?

Here are the mkisofs commands I use:

For the first session:

Code:
mkisofs -vv -f -r -l -posix-L -J -o  ~/backup.iso ./burndir
For subsequent sessions:

Code:
mkisofs -dev /dev/hdc -C 46939,71005 -prev-session /dev/hdc -vv -f -r -l -posix-L -J -o ~/backup.iso ./burndir
Where 46939,71005 is the output frome

Code:
cdrecord dev=/dev/hdc -msinfo
The only other difference is that I use a full path for backup.iso an
burndir.

So do these commands look faulty?

I'm using Slack 11, with a 2.6 kernel. Every time, cdrecord complains
about the 2.6 and suggests a 2.4; anyone else had trouble with Slack
11 and 2.6?

Oh, and here's ~/.mkisofsrc:

PUBL=Bill Powell, billpowellisalive.com
SYSI=Slackware Linux

I don't think it's the hardware; on previous iterations of Slack, I'd
burn multisession CDs all the time. I didn't pass those exact
parametrs to mkisofs, but they were quite similar.

Thanks for any advice!
 
  


Reply

Tags
burn, cd, cdrecord, cdrtools, error, k3b, mkisofs, multisession, slackware, slackware11


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
K3B will not continue multisession DoctorWynn Suse/Novell 6 05-10-2006 02:24 AM
k3b flaking out on DVD burn on slack 10.1 packetmover Slackware 2 12-05-2005 02:51 PM
CD-RW multisession problem on k3b JEPA Linux - Software 2 10-30-2005 08:12 AM
K3B cant continue multisession cd lockout Linux - Software 1 10-11-2005 05:47 AM
K3B Multisession Problem badawal Linux - Software 5 06-10-2005 03:42 PM


All times are GMT -5. The time now is 07:22 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration