I *think* I found the cause of the issues, in a round-about way.
It looks like I have a flaky SATA port on my motherboard. Plugged into
another port and things have been working fine thus far (3 burns later -
all functional).
It took some effort to get to that conclusion, as I ruled out my current
desktop installation, a new install of Ubuntu and a Fedora installation
to arrive at this point.
Grover's Law (http://grover.open2space.com/node/137) strikes again... sighs.
Shawn
Shawn wrote:
sata drive. Kubuntu 9.10.
@bogi. K3B knows about the drive - otherwise I wouldn't be able to tell
it to burn....
Gustin Johnson wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Is this a SATA or a PATA drive? What distro are you using?
Shawn wrote:
I'm on my second new CD drive in a month. The first was failing to burn
useful CDs - could not do bootable CDs, data-cds were hit and miss if
they worked, etc.
Now that I have a brand new drive, K3B is having nothing but problems
writing. As near as I can tell it is getting a hardware error when
writing. But this is a BRAND NEW drive just bought today, which seems
to function fine other than burning.
I had problems with permissions initally - K3B complained that it didn't
have permission to run cdrecord (which is now 'wodim' in *buntu due to
some licensing issues). I ripped out K3B, and the related tools, then
reinstalled them until I was able to at least start K3B without
warnings/errors. But I think the original problem may be that the
system now has two different drives set up, maybe....
When I try to burn a CD (with Brasero or K3B) the cue sheet is "sent",
but then when it tries to write the data it fails immediately and the
debug logs give me this:
Errno: 5 (Input/output error), write_g1 scsi sendcmd: no error
CDB: 2A 00 00 00 2C AF 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 04 00 00 00 00 0A 00 00 00 00 08 03 00 80
Sense Key: 0x4 Hardware Error, Segment 0
Sense Code: 0x08 Qual 0x03 (logical unit communication crc error
(ultra-dma/32)) Fru 0x0
Sense flags: Blk 0 (not valid) actual retry count 0
cmd finished after 0.959s timeout 200s
/usr/bin/wodim: A write error occured.
/usr/bin/wodim: Please properly read the error message above.
write track data: error after 23427072 bytes
Is this something worth trying to fix? Or should I return the drive and
go with a different brand (new drive is a Samsung)
Shawn
_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAksuhTEACgkQwRXgH3rKGfMisACeOFTEwGMSd64B6cWnBF3ZCH6+
1n0Anio/AR0Rfnd3Ggdn3p0HGQG5N/Qo
=mznh
-----END PGP SIGNATURE-----
_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
