Re: BD-R formatting help
I'm trying not to throw away *too* many of these darn expensive discs. Hey. Your boss could afford a BD burner two years ago ! It must have cost a little fortune. ;) That may be, but it is still painful to me to be tossing these babies in the rubbish bin! :'( Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Joerg Schilling wrote: maybe you missed the _point_ of the riddle Indeed. I was not aware of that. Did you post the READ FORMAT CAPACITIES: He used a very old cdrecord to read the data and for this reason, the mail did not include all information That may be, but it also did not include that information because it was not sent prior to today. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Thomas Schmitt wrote: Indeed. I was not aware of that. Did you post the READ FORMAT CAPACITIES: of a dvd+rw-mediainfo run on such a media ? NO, but if you'd like to see it, here it is. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com INQUIRY:[MATSHITA][BD-MLT SW-5582 ][BZE6] GET [CURRENT] CONFIGURATION: Mounted Media: 41h, BD-R SRM+POW Media ID: PHILIP/R02 Current Write Speed: 2.0x4495=8991KB/s Write Speed #0:2.0x4495=8991KB/s Write Speed #1:1.0x4495=4496KB/s Speed Descriptor#0:01/12088319 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s Speed Descriptor#1:01/12088319 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s BD SPARE AREA INFORMATION: Spare Area:60736/131072=46.3% free POW RESOURCES INFORMATION: Remaining Replacements:16843296 Remaining Map Entries: 0 Remaining Updates: 0 READ DISC INFORMATION: Disc status: appendable Number of Sessions:1 State of Last Session: incomplete Next Track: 1 Number of Tracks: 2 READ TRACK INFORMATION[#1]: Track State: partial incremental Track Start Address: 0*2KB Free Blocks: 0*2KB Track Size:12058848*2KB READ TRACK INFORMATION[#2]: Track State: complete incremental Track Start Address: 12058848*2KB Free Blocks: 0*2KB Track Size:29472*2KB FABRICATED TOC: Track#1 : [EMAIL PROTECTED] Track#AA : [EMAIL PROTECTED] Multi-session Info:[EMAIL PROTECTED] READ CAPACITY: 12088320*2048=24756879360
Re: BD-R formatting help
Joerg Schilling wrote: He used a very old cdrecord to read the data and for this reason, the mail did not include all information My cdrecord reports that it is build 2.01.01a33. Exactly what version do you think I should be using? Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Joerg Schilling wrote: The way I understand the problem, you will not get benefits from setting up spare areas for a BD-R that is written in a single shot. Jörg That would be the wrong way to look at the problem. If you burn in the mode that is Live Verify it will absolutely make a difference! Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Thomas Schmitt wrote: My understanding from specs is that it is Defect Management. I.e. the drive will write a portion of its buffer to media. Then it will checkread as long as the data is still in the buffer. If a read error occurs, then it will take relocation measures and write the content again from buffer to Spare Area. The checkread usually cuts write speed by half. Exactly. It does cut the speed in half (because it is reading and writing all of the data) but when your data is important or when the media is expensive, you don't want to throw away the disc on a bad burn like you would with a DVD that didn't verify after the burn. This (my) understanding of MMC-5 makes me wonder why Matt's burner worked around the scratch rather than running into it and to replace the casualties by spare sectors. Did it examine the blank media for damages ? Matt: Did you scratch before or after formatting ? Ok, I suppose your words are a better explanation of what happened. It burned all the way up to the scratch and must have relocated the data to the spare and continued to the burn. I don't mean to say that it located the bad spot before hand. It found it when it tried to read back the scratched area and failed. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Joerg Schilling wrote: Customer Service [EMAIL PROTECTED] wrote: Joerg Schilling wrote: He used a very old cdrecord to read the data and for this reason, the mail did not include all information My cdrecord reports that it is build 2.01.01a33. The latest version is a53. a33 is from August 2007 Ok, I've got your new build, what exactly do you want to see? I've sent quite a few info files at this point and I'd rather not redo all of them. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Thomas Schmitt wrote: Unfortunately it has been about two years since I created this disc. Did you test whether your burner is still able to format a BD-R to default spare size ? No, I haven't done it again, I'm trying not to throw away *too* many of these darn expensive discs. It would appear that dvd+rw-format has never been able to format a BD-R, as currently if you put ssa=anything with a BD-R disc, it will fail. That would mean that when I did it the last time, I used growisofs which itself performs a format (I am not sure whether it is as it goes or whether it is just done at the beginning of the burn). Probably something like: -use-the-force-luke=spare:min,wrvfy Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Thomas Schmitt wrote: I assume you have disabled all automounters and similar programs which could access the drive. So this could come from the device driver trying to learn about the present media. In the embedded 2.4.32 install, there is no automounter. Nothing happens unless I explicitly run it. In the stock Ubuntu install, I haven't disabled anything. Does this kernel log protesting start as soon as you insert the media into the drive or does it start only when you run dvd+rw-format ? No it only starts complaining after I run dvd+rw-format. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Joerg Schilling wrote: OK, thank you. BZW: it seems that the spare size if your other disk was not changed Yes, that is kind of the problem. dvd+rw-format doesn't seem to be doing anything at all. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Andy Polyakov wrote: The source code change mentioned in originating post is correct and will be included [though in modified form] to next dvd+rw-tools update. Great, any idea when you are planning your next release? This I can't reproduce. In other words I managed to format BD-R disc with -ssa=4G, i.e. unit succeeded to format it with ~4GB spare area. Have you managed to record BD-R in this particular unit at all? Same question about BD-RE? What I'm trying to say is that the unit might simply be broken... Another option is a kernel bug, maybe in SATA support (as you mentioned it's SATA connected). Have you managed to record a DVD? I have been able to record on this drive before. As long as I don't try to pre-format a BD-R. And I have never had any problems with the BD-RE's. I have also been able to record DVD's with this unit. I am going to move to a SATA unit soon, but right now I'm still tinkering with the same kind of drive that you have. Here's what I'm actually trying to do: I want to demonstrate to the customer how wonderful Blu-Ray is for data integrity. I want to say something like see it can even detect a defect in the media on the fly and still successfully complete a burn. I want to be able to make a small scratch on the disc and then watch it burn around the scratch and keep going (I have actually done this). Problem is that a small scratch is hard to see and a large scratch is a really big chunk of disc capacity (hence my -ssa=4G). Side note about spare area capacity. There is something they call TDMA, Temporary Disc Management Area, residing in Lead-In. As you allocate spare area, part of it will be reserved for *additional* TDMA regions. Relevant question is what part of it? MMC specification says that default value is up to vendor and in Panasonic case it seem to be 1/2 of spare area capacity. This means that if you ask your unit for spare area utilization data right after format, you'll see that 1/2 of it is already used. Well, it's not actually used, but reserved for TDMAs. Whether it's excessive or not, time will show. Meanwhile I'm considering adding extra option to dvd+rw-format, which would allow you to specify which portion of spare area will be reserved for TDMA. A. Wait, are you saying that if you used -ssa=4G you are actually going to get 2G of spare and 2G of TDMA? Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Andy Polyakov wrote: Releases turned to be feature driven lately and as no new features were required (e.g. HD-DVD was dismissed) I had no immediate plans so far. But as option to specify TDMA allocation is of apparent interest, it might be appropriate to consider release in foreseeable future, i.e. from week to month. Ok, I'll try to keep my eyes open for it. Do you do an announce on this list? I.e. you suffered from this problem with non-SATA unit? To reiterate. You run dvd+rw-format and kernel starts logging test unit ready: meduim error. As you start dvd+rw-format in text console (i.e. without starting windowing system), the kernel log appears as dvd+rw-format output. Error messages are emitted till you press ctrl-c. Is it correctly understood? Do you see any output from dvd+rw-format? Like process indicator? What does dvd+rw-format print exactly? Basically I'm running low on ideas, primarily because I couldn't reproduce this... Your description sounds about right. Andy: would you like an ssh session to see it for yourself? [Don't kill the messenger...] Yes. The real problem is that we don't know how TDMA is used exactly and therefore it's hard to judge if it's excessive or not. It surely varies from application to application and it might be that for your purposes (I assume you pretty much fill the media up at once) it's absolutely excessive. Best is to ask vendor for recommendation. A. I can't say for anyone else, but in my case, I would say that half is excessive. I kind of suspect that this would be how most users are going to use blu-ray anyways. I know there are several other very interesting uses for this type of media, but I think the most common will be the most boring. Just plain old burning something big. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Thomas Schmitt wrote: As for Matt's idea with the scratch demo: I have DVDs which look like an ice stadium and they work perfectly. Others have no scratch and they failed to verify after one or two burns. One can hardly drill holes without endangering the drive. But how about a few dots with a black felt tip marker ? Tell me how it worked out ... when it finally works. It isn't an idea, it works. I placed a small scratch on the disc (maybe 1mm) and burned several GB of data (enough to fill well past the scratch). When it is finished you can definitely tell where the burn approached the scratch and kind of skipped over it and moved to the next viable area. It is really a nice visual. Problem is 1mm is kind of hard to image and I was looking to make a bigger scratch. How do you figure that drilling a hole in a disc will endanger the drive? Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Thomas Schmitt wrote: Hi, When it is finished you can definitely tell where the burn approached the scratch and kind of skipped over it and moved to the next viable area. Interesting. How did it know in advance where the bad sectors are before trying to write to them ? But how did you manage to engage Defect Management ? Did i miss the solution of the formatting riddle ? You didn't miss the solution, but maybe you missed the _point_ of the riddle ;-) It is not that I cannot turn on defect management. It is that I cannot turn on defect management with an arbitrary spare size. For my experiment, the size of the scratch was small enough that the default size of the spare was enough to take care of it. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Joerg Schilling wrote: Customer Service [EMAIL PROTECTED] wrote: Joerg Schilling wrote: Thomas Schmitt [EMAIL PROTECTED] wrote Can it be that the BD-R was already treated with a format command previously ? MMC-5 4.5.3.5 BD-R Recording Models says Once the recording mode has been established, it is not changeable. This is why I asked him to run cdrecord -minf From the output of cdrecord that I just sent, it looks (to me) like the disc is still blank. As if the command failed before it even made it far enough to touch the disc. Sorry, please add a -v this should give you the formatted capacity list in addition. Jörg As you wish... I am not sure whether you guys like attachments or whether you want things inline, so I just attached it. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com Cdrecord-ProDVD-ProBD-Clone 2.01.01a33 (i686-pc-linux-gnu) Copyright (C) 1995-2007 Jörg Schilling TOC Type: 1 = CD-ROM Using libscg version 'schily-0.9'. atapi: 1 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'MATSHITA' Identifikation : 'BD-MLT SW-5582 ' Revision : 'BZE6' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Current: BD-R sequential recording Profile: BD-R sequential recording (current) Profile: BD-R random recording Profile: BD-RE Profile: BD-ROM Profile: DVD-RAM Profile: DVD+R/DL Profile: DVD+R Profile: DVD+RW Profile: DVD-RW restricted overwrite Profile: DVD-RW sequential recording Profile: DVD-R/DL layer jump recording Profile: DVD-R/DL sequential recording Profile: DVD-R sequential recording Profile: DVD-ROM Profile: CD-RW Profile: CD-R Profile: CD-ROM Profile: Removable Disk Using generic SCSI-3/mmc-3 BD-R driver (mmc_bdr). Driver flags : NO-CD BD MMC-3 BURNFREE Supported modes: PACKET SAO Drive buf size : 6684672 = 6528 KB Current Secsize: 2048 Disk type: 'BDR' (BD-R) Disk class: 01 Manufacturer: 'PHILIP' Media type: 'R02' Disk: is not in cartridge Media cartrige: write protect is off Free Spare Blocks: 0 Alloc Spare Blocks: 0 rzone size: 40 rzone number: 1 border number: 1 ljrs: 0 track mode: 4 copy: 0 damage: 0 reserved track: 0 blank: 1 incremental: 1 fp: 0 data mode: 1 lra valid: 0 nwa valid: 1 rzone start:0 next wr addr: 0 free blocks:12219392 blocking factor:32 rzone size: 12219392 last recorded addr: 0 read compat lba:0 Capacity Blklen/Sparesz. Type 12219392 200704 Unformated or Blank Media 1182617612288 Reserved (0) 118261760 Reserved (0) 57968640 Reserved (0) 120883200 Reserved (0) Mounted media class: BD Mounted media type: BD-R sequential recording Disk Is not erasable data type:standard disk status: empty session status: empty BG format status: none first track: 1 number of sessions: 1 first track in last sess: 1 last track in last sess: 1 Disk Is unrestricted Disk type: DVD, HD-DVD or BD Track Sess Type Start Addr End Addr Size == 1 1 Blank 0 12219391 12219392 -1 Next writable address: 0 Remaining writable size:12219392
Re: BD-R formatting help
Joerg Schilling wrote: OK, so this medium holds 200704 spare sectors. I am not sure whether this is the default or whether this is a result of a format call. BTW: Is this a Philips Medium? Jörg Attached is the output of cdrecord -v -minfo on a fresh-from-the-cellophane BD-R. Yes, these are both Philips branded discs. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com Cdrecord-ProDVD-ProBD-Clone 2.01.01a33 (i686-pc-linux-gnu) Copyright (C) 1995-2007 Jörg Schilling TOC Type: 1 = CD-ROM Using libscg version 'schily-0.9'. atapi: 1 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'MATSHITA' Identifikation : 'BD-MLT SW-5582 ' Revision : 'BZE6' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Current: BD-R sequential recording Profile: BD-R sequential recording (current) Profile: BD-R random recording Profile: BD-RE Profile: BD-ROM Profile: DVD-RAM Profile: DVD+R/DL Profile: DVD+R Profile: DVD+RW Profile: DVD-RW restricted overwrite Profile: DVD-RW sequential recording Profile: DVD-R/DL layer jump recording Profile: DVD-R/DL sequential recording Profile: DVD-R sequential recording Profile: DVD-ROM Profile: CD-RW Profile: CD-R Profile: CD-ROM Profile: Removable Disk Using generic SCSI-3/mmc-3 BD-R driver (mmc_bdr). Driver flags : NO-CD BD MMC-3 BURNFREE Supported modes: PACKET SAO Drive buf size : 6684672 = 6528 KB Current Secsize: 2048 Disk type: 'BDR' (BD-R) Disk class: 01 Manufacturer: 'PHILIP' Media type: 'R02' Disk: is not in cartridge Media cartrige: write protect is off Free Spare Blocks: 0 Alloc Spare Blocks: 0 rzone size: 40 rzone number: 1 border number: 1 ljrs: 0 track mode: 4 copy: 0 damage: 0 reserved track: 0 blank: 1 incremental: 1 fp: 0 data mode: 1 lra valid: 0 nwa valid: 1 rzone start:0 next wr addr: 0 free blocks:12219392 blocking factor:32 rzone size: 12219392 last recorded addr: 0 read compat lba:0 Capacity Blklen/Sparesz. Type 12219392 200704 Unformated or Blank Media 1182617612288 Reserved (0) 118261760 Reserved (0) 57968640 Reserved (0) 120883200 Reserved (0) Mounted media class: BD Mounted media type: BD-R sequential recording Disk Is not erasable data type:standard disk status: empty session status: empty BG format status: none first track: 1 number of sessions: 1 first track in last sess: 1 last track in last sess: 1 Disk Is unrestricted Disk type: DVD, HD-DVD or BD Track Sess Type Start Addr End Addr Size == 1 1 Blank 0 12219391 12219392 -1 Next writable address: 0 Remaining writable size:12219392
Re: BD-R formatting help
Thomas Schmitt wrote: ./dvd+rw-format -ssa=4G /dev/dvd But when I execute this command, it says that it is invalid for the detected media. || (mmc_profile != 0x12 mmc_profile != 0x43 mmc_profile != 0x41 ssa) ) After making the above change, it then gets past this portion If i get the code of dvd+rw-format.cpp 0.7.1 right then you are not supposed to use option -ssa together with profile 0x41. You are supposed to use option -force. At other spots in the code i find traces that ssa is well expected, though. Your code change should have had a chance for success. You will notice that the code has: force=ssa=1; so if you choose ssa, you are automatically setting force too. sr0: CDROM (ioctl) error, command: Test Unit Ready 00 00 00 00 00 Deferred sr00:00: sense key Medium Error Additional sense indicates Format command failed This does not look as if it was from dvd+tools but rather from the kernel. Do you see that in a log file or does it appear with the format run on terminal ? This actually shows up in the log as well as on the terminal. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Thomas Schmitt wrote:
I can by no means find a potential origin of
that message in dvd+rw-tools. Nor would my
local Linux kernel print me these messages
Did you already tell what operating system and
version you use ? (I assume sr0 is Linux
That particular error message was being printed by a very pared down
2.4.32 kernel that was running on an embedded slackware 10 install.
In order to do the current testing, I've thrown the unit into a default
x86 install of Ubuntu Gutsy.
I have downloaded and compiled the dvd+rw-tools V7.1 as Ubuntu seems to
be behind on their builds.
To be complete, attached messages.txt is what gets printed to
/var/log/messages when I try the same command.
The terminal screen begins scrolling this text until I CTL-C:
hdc: error code: 0x70 sense_key: 0x03 asc: 0x57 ascq:0x00
And I find the attachment dmesg.txt.
Matt Schulte
Commtech, Inc.
Voice: 316-636-1131
Fax: 316-636-1163
http://www.commtech-fastcom.com
Nov 21 16:22:23 ubuntu kernel: [27428.609016] cdrom: This disc doesn't have any
tracks I recognize!
Nov 21 16:22:29 ubuntu kernel: [27434.616377] hdc: media error (bad sector):
status=0x51 { DriveReady SeekComplete Error }
Nov 21 16:22:29 ubuntu kernel: [27434.616387] hdc: media error (bad sector):
error=0x30 { LastFailedSense=0x03 }
Nov 21 16:22:29 ubuntu kernel: [27434.616391] ide: failed opcode was: unknown
Nov 21 16:22:29 ubuntu kernel: [27434.617816] end_request: I/O error, dev hdc,
sector 0
Nov 21 16:22:29 ubuntu kernel: [27434.618802] hdc: media error (bad sector):
status=0x51 { DriveReady SeekComplete Error }
Nov 21 16:22:29 ubuntu kernel: [27434.618808] hdc: media error (bad sector):
error=0x30 { LastFailedSense=0x03 }
Nov 21 16:22:29 ubuntu kernel: [27434.618811] ide: failed opcode was: unknown
Nov 21 16:22:29 ubuntu kernel: [27434.620260] end_request: I/O error, dev hdc,
sector 0
Nov 21 16:22:29 ubuntu kernel: [27434.626333] hdc: media error (bad sector):
status=0x51 { DriveReady SeekComplete Error }
Nov 21 16:22:29 ubuntu kernel: [27434.626342] hdc: media error (bad sector):
error=0x30 { LastFailedSense=0x03 }
Nov 21 16:22:29 ubuntu kernel: [27434.626346] ide: failed opcode was: unknown
Nov 21 16:22:29 ubuntu kernel: [27434.627793] end_request: I/O error, dev hdc,
sector 0
Nov 21 16:22:29 ubuntu kernel: [27434.628785] hdc: media error (bad sector):
status=0x51 { DriveReady SeekComplete Error }
Nov 21 16:22:29 ubuntu kernel: [27434.628791] hdc: media error (bad sector):
error=0x30 { LastFailedSense=0x03 }
Nov 21 16:22:29 ubuntu kernel: [27434.628794] ide: failed opcode was: unknown
Nov 21 16:22:29 ubuntu kernel: [27434.630246] end_request: I/O error, dev hdc,
sector 0
Nov 21 16:22:29 ubuntu kernel: [27434.631259] hdc: media error (bad sector):
status=0x51 { DriveReady SeekComplete Error }
Nov 21 16:22:29 ubuntu kernel: [27434.631264] hdc: media error (bad sector):
error=0x30 { LastFailedSense=0x03 }
Nov 21 16:22:29 ubuntu kernel: [27434.631267] ide: failed opcode was: unknown
Nov 21 16:22:29 ubuntu kernel: [27434.632715] end_request: I/O error, dev hdc,
sector 0
Nov 21 16:22:29 ubuntu kernel: [27434.633690] hdc: media error (bad sector):
status=0x51 { DriveReady SeekComplete Error }
Nov 21 16:22:29 ubuntu kernel: [27434.633695] hdc: media error (bad sector):
error=0x30 { LastFailedSense=0x03 }
Nov 21 16:22:29 ubuntu kernel: [27434.633698] ide: failed opcode was: unknown
Nov 21 16:22:29 ubuntu kernel: [27434.635255] end_request: I/O error, dev hdc,
sector 0
Nov 21 16:22:29 ubuntu kernel: [27434.637129] hdc: media error (bad sector):
status=0x51 { DriveReady SeekComplete Error }
Nov 21 16:22:29 ubuntu kernel: [27434.637134] hdc: media error (bad sector):
error=0x30 { LastFailedSense=0x03 }
Nov 21 16:22:29 ubuntu kernel: [27434.637138] ide: failed opcode was: unknown
Nov 21 16:22:29 ubuntu kernel: [27434.638354] end_request: I/O error, dev hdc,
sector 0
Nov 21 16:22:29 ubuntu kernel: [27434.639327] hdc: media error (bad sector):
status=0x51 { DriveReady SeekComplete Error }
Nov 21 16:22:29 ubuntu kernel: [27434.639332] hdc: media error (bad sector):
error=0x30 { LastFailedSense=0x03 }
Nov 21 16:22:29 ubuntu kernel: [27434.639335] ide: failed opcode was: unknown
Nov 21 16:22:29 ubuntu kernel: [27434.640993] end_request: I/O error, dev hdc,
sector 0
Nov 21 16:22:29 ubuntu kernel: [27434.641962] hdc: media error (bad sector):
status=0x51 { DriveReady SeekComplete Error }
Nov 21 16:22:29 ubuntu kernel: [27434.641968] hdc: media error (bad sector):
error=0x30 { LastFailedSense=0x03 }
Nov 21 16:22:29 ubuntu kernel: [27434.641971] ide: failed opcode was: unknown
Nov 21 16:22:29 ubuntu kernel: [27434.643674] end_request: I/O error, dev hdc,
sector 0
Nov 21 16:22:29 ubuntu kernel: [27434.644808] hdc: media error (bad sector):
status=0x51 { DriveReady SeekComplete Error }
Nov 21 16:22:29 ubuntu kernel: [27434.644814] hdc: media error (bad sector):
error=0x30 { LastFailedSense=0x03 }
Nov 21 16:22:29 ubuntu kernel: [27434.644817] ide:
Re: BD-R formatting help
Joerg Schilling wrote: What does cdrecord -minfo show for this medium? Hello, I'm at a different email address, but it's still me. So here is the cdrecord -minfo output: Cdrecord-ProDVD-ProBD-Clone 2.01.01a33 (i686-pc-linux-gnu) Copyright (C) 1995-2007 Jörg Schilling Using libscg version 'schily-0.9'. Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'MATSHITA' Identifikation : 'BD-MLT SW-5582 ' Revision : 'BDB2' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Using generic SCSI-3/mmc-3 BD-R driver (mmc_bdr). Driver flags : NO-CD BD MMC-3 BURNFREE Supported modes: PACKET SAO Mounted media class: BD Mounted media type: BD-R sequential recording Disk Is not erasable data type:standard disk status: empty session status: empty BG format status: none first track: 1 number of sessions: 1 first track in last sess: 1 last track in last sess: 1 Disk Is unrestricted Disk type: DVD, HD-DVD or BD Track Sess Type Start Addr End Addr Size == 1 1 Blank 0 12219391 12219392 Next writable address: 0 Remaining writable size:12219392 Matt Schulte -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Joerg Schilling wrote: Thomas Schmitt [EMAIL PROTECTED] wrote: Can it be that the BD-R was already treated with a format command previously ? MMC-5 4.5.3.5 BD-R Recording Models says Once the recording mode has been established, it is not changeable. This is why I asked him to run cdrecord -minfo From the output of cdrecord that I just sent, it looks (to me) like the disc is still blank. As if the command failed before it even made it far enough to touch the disc. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
You indicated it's BDB2 firmware? Is it latest? We both know that there is BZE6 available for SW-5582. Do you know how they number their releases? For example is BZxx later than BDxx? What I'm implying firmware upgrade might be due to make it work with arbitrary ... Cheers. A. I completely forgot that we updated the firmware on this bad boy. Let me give that a shot first. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BD-R formatting help
Andy Polyakov wrote: This is not intentional. In other words it's a bug and it will be looked into. Suggested code modification might be appropriate, but I'd rather not say it without double-checking. In a course of few days. Meanwhile please submit dvd+rw-mediainfo output (even garbled one you mentioned you obtain if you don't reload media). cdrecord does not show format descriptors. Updating the firmware didn't do it. I'm attaching three different mediainfo outputs. mediainfo1 is a blank disc before attempting to do anything to it. mediainfo2 is the same disc after running: ./dvd+rw-format -ssa=4G /dev/dvd(and before I ejected the disc) mediainfo3 is the same disc after ejecting and injecting. You will notice that 1 and 3 are the same. Matt Schulte Commtech, Inc. Voice: 316-636-1131 Fax: 316-636-1163 http://www.commtech-fastcom.com INQUIRY:[MATSHITA][BD-MLT SW-5582 ][BZE6] GET [CURRENT] CONFIGURATION: Mounted Media: 41h, BD-R SRM Media ID: PHILIP/R02 Current Write Speed: 2.0x4495=8991KB/s Write Speed #0:2.0x4495=8991KB/s Write Speed #1:1.0x4495=4496KB/s Speed Descriptor#0:01/12219391 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s Speed Descriptor#1:01/12219391 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s 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: unformatted: 12219392*2048=25025314816 00h(3000): 11826176*2048=24220008448 32h(0):11826176*2048=24220008448 32h(0):5796864*2048=11871977472 32h(0):12088320*2048=24756879360 READ TRACK INFORMATION[#1]: Track State: invisible incremental Track Start Address: 0*2KB Next Writable Address: 0*2KB Free Blocks: 12219392*2KB Track Size:12219392*2KB READ CAPACITY: 0*2048=0 INQUIRY:[MATSHITA][BD-MLT SW-5582 ][BZE6] GET [CURRENT] CONFIGURATION: Mounted Media: 41h, BD-R SRM Media ID: PHILIP/R02 Current Write Speed: 2.0x4495=8991KB/s Write Speed #0:2.0x4495=8991KB/s Write Speed #1:1.0x4495=4496KB/s Speed Descriptor#0:01/10220543 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s Speed Descriptor#1:01/10220543 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s READ DISC INFORMATION: Disc status: appendable Number of Sessions:1 State of Last Session: empty Next Track: 1 Number of Tracks: 1 READ FORMAT CAPACITIES: INQUIRY:[MATSHITA][BD-MLT SW-5582 ][BZE6] GET [CURRENT] CONFIGURATION: Mounted Media: 41h, BD-R SRM Media ID: PHILIP/R02 Current Write Speed: 2.0x4495=8991KB/s Write Speed #0:2.0x4495=8991KB/s Write Speed #1:1.0x4495=4496KB/s Speed Descriptor#0:01/12219391 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s Speed Descriptor#1:01/12219391 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s 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: unformatted: 12219392*2048=25025314816 00h(3000): 11826176*2048=24220008448 32h(0):11826176*2048=24220008448 32h(0):5796864*2048=11871977472 32h(0):12088320*2048=24756879360 READ TRACK INFORMATION[#1]: Track State: invisible incremental Track Start Address: 0*2KB Next Writable Address: 0*2KB Free Blocks: 12219392*2KB Track Size:12219392*2KB READ CAPACITY: 0*2048=0
