Issues brining BD disks from the command line - write failures
First off I want to say thank all of you that work on this software that makes it possible to do this stuff. I'm more impressed than you can imagine. Now that I have hopefully 'buttered you up' a little bit, I'm in need of assistance, and I have exhausted my google skills in an attempt to find an answer to the issue. At this point I'm trying trial and error, and at $1.25 a disc, it's getting expensive. A (large) part of my issue is me; I had this working at one point, didn't write down _exactly_ all the requirements and process I followed, and there have been quite a few kernel and program updates since it worked. I am trying to backup large .wav files ( 1.3 - 2+GB in size) to BD-R media. When I had it working, I would create a 25GB file with truncate, use mkudffs to format the file as a filesystem, loopback mount it, and copy data over to the file system, sync a couple of times, dismount and the use cdrecord or growisofs (I have tried both) to burn the image to the media. I have two burners, on two different systems, so I know I'm pretty sure I'm not having a hardware issue. One is attached via a SAS controller via an eSATA breakout cable to an external eSATA enclosure: description: SCSI CD-ROM product: BD-RE WH14NS40 vendor: HL-DT-ST physical id: 0.0.0 bus info: scsi@4:0.0.0 logical name: /dev/cdrom1 logical name: /dev/cdrw1 logical name: /dev/dvd1 logical name: /dev/dvdrw1 logical name: /dev/sr1 version: 1.00 capabilities: removable audio configuration: status=ready *-medium physical id: 0 logical name: /dev/cdrom1 The other burner is connected via internal onboard SATA controller: description: DVD-RAM writer product: BD-RE BH08LS20 vendor: HL-DT-ST physical id: 0.1.0 bus info: scsi@2:0.1.0 logical name: /dev/cdrom1 logical name: /dev/cdrw1 logical name: /dev/dvd1 logical name: /dev/dvdrw1 logical name: /dev/sr0 version: 1.00 capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram configuration: ansiversion=5 status=nodisc I'm now _way_ behind on moving this stuff off to removable media and I'm starting to get a bit desperate. This last attempt, on the external burner using growisofs, new server and fresh OS load is finally prompted me to annoy you with a plea for help. This is as far as it got that time: growisofs -speed=1 -Z /dev/sr1=/mnt/md9/bdburn/BDBurn.udf Executing 'builtin_dd if=/mnt/md9/bdburn/BDBurn.udf of=/dev/sr1 obs=32k seek=0' /dev/sr1: pre-formatting blank BD-R for 24.8GB... /dev/sr1: "Current Write Speed" is 2.0x4390KBps. 949059584/250 ( 3.8%) @0.3x, remaining 216:40 RBU 100.0% UBU 29.2% 951975936/250 ( 3.8%) @0.2x, remaining 217:40 RBU 100.0% UBU 20.8% 954499072/250 ( 3.8%) @0.2x, remaining 218:19 RBU 100.0% UBU 12.5% WRITE@LBA=720a0h failed with SK=3h/WRITE ERROR]: Input/output error write failed: Input/output error /dev/sr1: flushing cache /dev/sr1: closing track /dev/sr1: closing session CLOSE SESSION failed with SK=5h/INVALID FIELD IN CDB]: Input/output error /dev/sr1: reloading tray Am I creating too large of a file to burn to the media - I note that growisofs is saying "preformatting to 24.8 GB"? This is the size I have used int he past that worked. This is my actual UDF file size. ls -al /mnt/md9/bdburn/BDBurn.udf -rw-r--r-- 1 root root 250 May 6 17:39 /mnt/md9/bdburn/BDBurn.udf _any_ help in getting this sorted will be greatly appreciated. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org Archive: http://lists.debian.org/51891f73.1000...@yahoo.com
Re: Issues brining BD disks from the command line - write failures
Hi,
> 954499072/250 ( 3.8%) @0.2x, remaining 218:19 RBU 100.0% UBU 12.5%
> WRITE@LBA=720a0h failed with SK=3h/WRITE ERROR]: Input/output error
This is a failure of the drive to write to the medium.
It has nothing to do with your preparations of BDBurn.udf,
but rather with the relation of drive and medium.
I.e. they do not like each other (any more).
The speed is very low. Possibly the drive relocated many
blocks to the Spare Area. Possibibly that Spare area is now
full and further bad blocks could not be replaced by spares.
> CLOSE SESSION failed with SK=5h/INVALID FIELD IN CDB]: Input/output error
This is not the reason of failure. But it could be a known
growisofs bug, that causes an error message at the end of
a burn run. Andy Polyakov, the author of growisofs, stated that
it is harmless. (Some doubts have arised meanwhile, though.)
> Am I creating too large of a file to burn to the media
growisofs is supposed to refuse in that case.
But it started writing and failed early (after only 1 GB).
> I note that growisofs is saying "preformatting to 24.8 GB"?
This stems from growisofs' habit to format BD-R by default.
To my own experience (with libburn, not with growisofs) BD-R are
more likely to fail if they are formatted. This is contrary to
the theoretical advantages of formatting ("Defect Management").
> _any_ help in getting this sorted will be greatly appreciated.
It might help to try writing to unformatted BD-R.
growisofs option -use-the-force-luke=spare:none will prevent
formatting of a blank BD-R before writing starts:
growisofs -speed=1 -use-the-force-luke=spare:none \
-Z /dev/sr1=/mnt/md9/bdburn/BDBurn.udf
My own programs cdrskin and xorriso do not format BD-R by default:
cdrskin -v speed=1 dev=/dev/sr1 /mnt/md9/bdburn/BDBurn.udf
xorriso -as cdrecord -v speed=1 dev=/dev/sr1 /mnt/md9/bdburn/BDBurn.udf
-
Since growisofs announced
/dev/sr1: "Current Write Speed" is 2.0x4390KBps.
i assume that the drive does not offer speed 1.
You may inquire the list of speeds by
dvd+rw-mediainfo /dev/sr1
Look for output lines like
Write Speed #0:4.0x4495=17980KB/s
Speed Descriptor#0:00/11826175 R@8.0x4495=35960KB/s W@4.0x4495=17980KB/s
(this is RITEK/BR2 media on Optiarc BD RW BD-5300S)
Or perform
cdrskin dev=/dev/sr1 --list_speeds
or
xorriso -outdev /dev/sr1 -list_speeds
and look at the end of their text output.
-
Have a nice day :)
Thomas
--
To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Archive: http://lists.debian.org/12401623645803380...@scdbackup.webframe.org
Re: Issues brining BD disks from the command line - write failures
I put in a fresh new, blank disc and I got some interesting errors --
I'll try this on the other system with the other burner here in a bit.
ls -al /dev/sr*
brw-rw 1 root cdrom 11, 0 May 7 13:02 /dev/sr0
brw-rw 1 root cdrom 11, 1 May 7 13:02 /dev/sr1
# growisofs -speed=1 -use-the-force-luke=spare:none -Z
/dev/sr1=/mnt/md9/bdburn/BDBurn.udf
:-[ READ FORMAT CAPACITIES failed with SK=3h/ASC=19h/ACQ=00h]:
Input/output error
# dvd+rw-mediainfo /dev/sr1
INQUIRY:[HL-DT-ST][BD-RE WH14NS40 ][1.00]
GET [CURRENT] CONFIGURATION:
Mounted Media: 41h, BD-R SRM
Media ID: OTCBDR/001
Current Write Speed: 4.0x4495=17984KB/s
Write Speed #0:4.0x4495=17984KB/s
Write Speed #1:2.0x4495=8992KB/s
Speed Descriptor#0:00/12219391 R@6.0x4495=26976KB/s
W@4.0x4495=17984KB/s
Speed Descriptor#1:00/12219391 R@6.0x4495=26976KB/s
W@2.0x4495=8992KB/s
:-[ READ BD SPARE INFORMATION failed with SK=5h/INVALID FIELD IN CDB]:
Input/output error
READ DISC INFORMATION:
Disc status: blank
Number of Sessions:1
State of Last Session: empty
"Next" Track: 1
Number of Tracks: 1
READ FORMAT CAPACITIES:
:-[ READ FORMAT CAPACITIES failed with SK=3h/ASC=19h/ACQ=00h]:
Input/output error
:-[ READ TRACK INFORMATION failed with SK=3h/ASC=19h/ACQ=00h]:
Input/output error
On 05/07/2013 12:52 PM, Thomas Schmitt wrote:
Hi,
954499072/250 ( 3.8%) @0.2x, remaining 218:19 RBU 100.0% UBU 12.5%
WRITE@LBA=720a0h failed with SK=3h/WRITE ERROR]: Input/output error
This is a failure of the drive to write to the medium.
It has nothing to do with your preparations of BDBurn.udf,
but rather with the relation of drive and medium.
I.e. they do not like each other (any more).
The speed is very low. Possibly the drive relocated many
blocks to the Spare Area. Possibibly that Spare area is now
full and further bad blocks could not be replaced by spares.
CLOSE SESSION failed with SK=5h/INVALID FIELD IN CDB]: Input/output error
This is not the reason of failure. But it could be a known
growisofs bug, that causes an error message at the end of
a burn run. Andy Polyakov, the author of growisofs, stated that
it is harmless. (Some doubts have arised meanwhile, though.)
Am I creating too large of a file to burn to the media
growisofs is supposed to refuse in that case.
But it started writing and failed early (after only 1 GB).
I note that growisofs is saying "preformatting to 24.8 GB"?
This stems from growisofs' habit to format BD-R by default.
To my own experience (with libburn, not with growisofs) BD-R are
more likely to fail if they are formatted. This is contrary to
the theoretical advantages of formatting ("Defect Management").
_any_ help in getting this sorted will be greatly appreciated.
It might help to try writing to unformatted BD-R.
growisofs option -use-the-force-luke=spare:none will prevent
formatting of a blank BD-R before writing starts:
growisofs -speed=1 -use-the-force-luke=spare:none \
-Z /dev/sr1=/mnt/md9/bdburn/BDBurn.udf
My own programs cdrskin and xorriso do not format BD-R by default:
cdrskin -v speed=1 dev=/dev/sr1 /mnt/md9/bdburn/BDBurn.udf
xorriso -as cdrecord -v speed=1 dev=/dev/sr1 /mnt/md9/bdburn/BDBurn.udf
-
Since growisofs announced
/dev/sr1: "Current Write Speed" is 2.0x4390KBps.
i assume that the drive does not offer speed 1.
You may inquire the list of speeds by
dvd+rw-mediainfo /dev/sr1
Look for output lines like
Write Speed #0:4.0x4495=17980KB/s
Speed Descriptor#0:00/11826175 R@8.0x4495=35960KB/s W@4.0x4495=17980KB/s
(this is RITEK/BR2 media on Optiarc BD RW BD-5300S)
Or perform
cdrskin dev=/dev/sr1 --list_speeds
or
xorriso -outdev /dev/sr1 -list_speeds
and look at the end of their text output.
-
Have a nice day :)
Thomas
--
To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Archive: http://lists.debian.org/51894a3e.1030...@yahoo.com
Re: Issues brining BD disks from the command line - write failures
Hi, > :-[ READ FORMAT CAPACITIES failed with SK=3h/ASC=19h/ACQ=00h]: 3,19,00 is not listed among the official SCSI error codes. 3,x,y means "Medium error". The other two components would tell what kind of medium error. E.g. 3,C0,00 would be "Write error". > :-[ READ BD SPARE INFORMATION failed with SK=5h/INVALID FIELD IN CDB]: It looks like the drive refuses to tell anything about BD peculiarities. > Media ID: OTCBDR/001 First time i see "Optodisc Technology Corporation" as manufacturer. My list says that they are 1x-4x high-to-low media. (The other type "LTH" is quite problematic. But HTL should be ok.) Well, if more than one drive fails with these, then you will have to try a different medium type. E.g with a different nominal speed (Optodisc has "1x-6x" OTCBDR/002) or from a brand that sells from a different manufacturer (Brand Verbatim is "VERBAT" or "MBI"). BD-RE are more expensive than BD-R, but usually less error prone. At least you would surely buy a different medium type. (And you most surely can revive spoiled BD-RE as soon as you find a drive which can handle them.) Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org Archive: http://lists.debian.org/32514623672553567...@scdbackup.webframe.org
Re: Issues brining BD disks from the command line - write failures
Hi, > or a bad enclosure maybe? Rather not. The growisofs error message indicates media problems. > Current: DVD-R sequential recording That's a different game ... > Sense Key: 0x3 Medium Error, deferred error, Segment 0 > Sense Code: 0x0C Qual 0x00 (write error) Fru 0x0 ... but quite the same error as with growisofs. > like there is some sort of issue with DMA access to the drive? No transport problems to see. The drive dislikes the medium. (Any medium ?) > Do I have a coincidence not only getting a brand new dead burner but some > sort of bus damage to this system? If the burner is new then complain to the seller and demand replacement. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org Archive: http://lists.debian.org/22081623689829268...@scdbackup.webframe.org
