Gentoo Archives: gentoo-amd64

From: Richard Fish <bigfish@××××××××××.org>
To: gentoo-amd64@l.g.o
Subject: Re: [gentoo-amd64] k3b error
Date: Mon, 06 Feb 2006 15:17:25
Message-Id: 7573e9640602060715s3d69cbb2n6d46c460cdd5524f@mail.gmail.com
In Reply to: [gentoo-amd64] k3b error by Gavin Seddon
1 On 2/6/06, Gavin Seddon <gavin.m.seddon@×××××××××××××.uk> wrote:
2 > Track 01: 36 of 57 MB written (fifo 59%) [buf 5%] 9.1x.
3 > Track 01: 37 of 57 MB written (fifo 45%) [buf 85%] 8.7x.
4 > /usr/bin/cdrecord: Success. write_g1: scsi sendcmd: no error
5 > CDB: 2A 00 00 00 4A 79 00 00 1F 00
6 > status: 0x2 (CHECK CONDITION)
7 > Sense Bytes: 70 00 03 00 00 47 E8 0A 00 00 00 00 0C 00 00 00
8 > Sense Key: 0x3 Medium Error, Segment 0
9 > Sense Code: 0x0C Qual 0x00 (write error) Fru 0x0
10
11 > /usr/bin/cdrecord -v gracetime=2 dev=/dev/hdc speed=32 -tao
12 > driveropts=burnfree -eject
13 > -data /home/mbpssgms/install-x86-minimal-2005.1-r1.iso '
14
15 Well, one thing that bothers me is that your system is not able to
16 keep the fifo or the drive buffer full, which considering that 32x is
17 only 4.8MB/s, it should be able to. Possibly you have something
18 misconfigured, but I don't know what.
19
20 1. Check your cabling and drive jumpers. (Is this the only device on
21 the secondary channel?)
22
23 2. Check that DMA is enabled for your hard drive (hdparm /dev/hdX).
24
25 3. If by chance the drive you are reading from is hdd, use -immed with cdrecord.
26
27 Also, try dropping to 16x or even 8x and see if the results improve.
28
29 -Richard
30
31 --
32 gentoo-amd64@g.o mailing list