Re: Blanking/Formating a BD-RE
The thing I want to get is the following: I need to get the difference between a written bd-re (containing toc/filesytem/data/..) and an empty one. But here my problem starts. When I do a dvd+rw-mediainfo on a media which was formatted (after it was written with an iso) with dvd+rw- format I get the following info: [EMAIL PROTECTED] /]# dvd+rw-mediainfo /dev/hdb INQUIRY:[Optiarc ][BDRW BD-M100A ][1.0e] GET [CURRENT] CONFIGURATION: Mounted Media: 43h, BD-RE Media ID:SONY/ES1 Current Write Speed: 2.0x4495=8991KB/s Write Speed #0:2.0x4495=8991KB/s Speed Descriptor#0:01/11826175 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s BD SPARE AREA INFORMATION: Spare Area:393216/393216=100.0% free READ DISC INFORMATION: Disc status: complete Number of Sessions:1 State of Last Session: complete Number of Tracks: 1 READ FORMAT CAPACITIES: formatted: 11826176*2048=24220008448 00h(3000): 11826176*2048=24220008448 01h(800): 11564032*2048=23683137536 30h(3000): 11826176*2048=24220008448 30h(5000): 11564032*2048=23683137536 30h(1000): 12088320*2048=24756879360 31h(800): 12219392*2048=25025314816 READ TRACK INFORMATION[#1]: Track State: complete Track Start Address: 0*2KB Free Blocks: 0*2KB Track Size:11826176*2KB FABRICATED TOC: Track#1 : [EMAIL PROTECTED] Track#AA : [EMAIL PROTECTED] Multi-session Info:[EMAIL PROTECTED] READ CAPACITY: 11826176*2048=24220008448 Compared with a new one (fresh from the box): [EMAIL PROTECTED] ~]# dvd+rw-mediainfo /dev/hdb INQUIRY:[Optiarc ][BDRW BD-M100A ][1.0e] GET [CURRENT] CONFIGURATION: Mounted Media: 43h, BD-RE Media ID:SONY/ES1 Current Write Speed: 2.0x4495=8991KB/s Write Speed #0:2.0x4495=8991KB/s Speed Descriptor#0: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 01h(800): 11564032*2048=23683137536 30h(3000): 11826176*2048=24220008448 30h(5000): 11564032*2048=23683137536 30h(1000): 12088320*2048=24756879360 31h(800): 12219392*2048=25025314816 READ TRACK INFORMATION[#1]: Track State: blank Track Start Address: 0*2KB Free Blocks: 0*2KB Track Size:0*2KB Here you can see the difference: in the first output even when I format the disc with dvd+rw-format it says completed and that it has a TOC. On the fresh media it says blank which is perfect for me. Anyone has an idea how to know from the dvd+rw-mediainfo output if it is really blank or if it contains data ? yours Arnold Am 05.03.2008 um 14:20 schrieb Andy Polyakov: If someone can provide me some tool or instructions how to do it I could try it on another PC with BD-RE drive. If the only goal is to render media unmountable, then, as Thomas suggested, you should find a way to nullify beginning of media. One way is to 'dd if=/dev/zero bs=1k count=64 | growisofs -Z /dev/cdrom=/ dev/fd/0'. If you ought to nullify the whole thing, e.g. for privacy reasons, then 'growisofs -Z /dev/cdrom=/dev/zero' would do. However!!! As it's time consuming procedure it's probably more appropriate to spend this time on 'dvd+rw-format -format=full /dev/ cdrom', because it will also verify media for eventual defects. On the other hand if current data-set is much less than media capacity and you want to nullify only this data, you can save time by figuring out how large is the data-set and adjusting count in above mentioned dd command accordingly. For example take 1k-blocks value from 'df -k /mnt/cdrom' output and feed it as count to dd. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Blanking/Formating a BD-RE
Hi, what I could use else for writing and cleaning BD-RE ? I am only a bystander here because i got no BD drive to do experiments with. But if you want to do the experiments for then i would be willing to invest some work into the problem. First experiment proposal: Find out whether your Linux supports the drive as normal random access block device: dd if=/dev/zero bs=2048 count=512 of=/dev/sr# with # being the appropriate number. (I assume your kernel log is full of complaints with the block device address of your drive.) If this works without error message, then try to eject, reload and mount your BD-RE. The expected outcome is that mounting does not work any more because you overwrote the head of the filesystem image by above dd command and its 1 MB of zeros. There is of course the risk that this experiment leads to the same evil problems as your previous experiments. So prepare for reboot. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Blanking/Formating a BD-RE
Hi ! How should I test it with a Windows application as I run Linux ? yours Arnold Am 24.02.2008 um 04:43 schrieb Bill Davidsen: Joerg Schilling wrote: Arnold Maderthaner [EMAIL PROTECTED] wrote: Yes I'm running it as root on RHEL5.1 with newest cdrecord with the patch that Joerg send. Btw. after that crash the BD-RE drive cannot be used anymore. I had to reboot the system. If you need to reboot, you found a kernel bug. In the sense that the kernel could detect that the drive was in a problem state and do the type of initialization which occurs at boot and device probe time. There are other things possibly involved. The kernel just passes commands, so the application might be sending some command (not wrong, just different than what the Windows application uses) which locks up the firmware. To test you could leave the system up and power cycle the drive (plug and unplug power cable). Unlikely, but not impossible. You could call this an application bug or a firmware bug, but if power cycle of the drive clears it, it is likely to be firmware response to the command sent. If the kernel passes the application command to the device, it's reasonably hard to see this as a kernel bug in the usual sense. It would be good to know what command the Windows application sends to do the same function, it would help clarify the nature of the problem, and obviously the solution. -- Bill Davidsen [EMAIL PROTECTED] Woe unto the statesman who makes war without a reason that will still be valid when the war is over... Otto von Bismark
Re: Blanking/Formating a BD-RE
Joerg Schilling wrote: Arnold Maderthaner [EMAIL PROTECTED] wrote: Yes I'm running it as root on RHEL5.1 with newest cdrecord with the patch that Joerg send. Btw. after that crash the BD-RE drive cannot be used anymore. I had to reboot the system. If you need to reboot, you found a kernel bug. In the sense that the kernel could detect that the drive was in a problem state and do the type of initialization which occurs at boot and device probe time. There are other things possibly involved. The kernel just passes commands, so the application might be sending some command (not wrong, just different than what the Windows application uses) which locks up the firmware. To test you could leave the system up and power cycle the drive (plug and unplug power cable). Unlikely, but not impossible. You could call this an application bug or a firmware bug, but if power cycle of the drive clears it, it is likely to be firmware response to the command sent. If the kernel passes the application command to the device, it's reasonably hard to see this as a kernel bug in the usual sense. It would be good to know what command the Windows application sends to do the same function, it would help clarify the nature of the problem, and obviously the solution. -- Bill Davidsen [EMAIL PROTECTED] Woe unto the statesman who makes war without a reason that will still be valid when the war is over... Otto von Bismark
Re: Blanking/Formating a BD-RE
Hi ! I applied the patch and now I get this: [EMAIL PROTECTED] bin]# ./cdrecord dev=3,0,0 blank=all Cdrecord-ProDVD-ProBD-Clone 2.01.01a37 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2008 J?rg Schilling scsidev: '3,0,0' scsibus: 3 target: 0 lun: 0 Linux sg driver version: 3.5.34 ./cdrecord: Warning Linux Bus mapping botch. ./cdrecord: Warning Linux Bus mapping botch. ./cdrecord: Warning Linux Bus mapping botch. ./cdrecord: Warning Linux Bus mapping botch. Using libscg version 'schily-0.9'. Device type: Removable CD-ROM Version: 5 Response Format: 2 Capabilities : Vendor_info: 'LITE-ON ' Identifikation : 'BD B LH-2B1S' Revision : 'AL09' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Using generic SCSI-3/mmc-3 BD-RE driver (mmc_bdre). Driver flags : NO-CD BD MMC-3 BURNFREE Supported modes: PACKET SAO LAYER_JUMP Starting to write CD/DVD/BD at speed 2 in real BLANK mode for single session. Last chance to quit, starting real write0 seconds. Operation starts. Running pad based emulation to blank the medium. secsize 2048 padbytes 25025314816 padblocks 12219392 maxblocks 12219392 Track 00:0 of 23866 MB pad written. ./cdrecord: Input/output error. write_g1: scsi sendcmd: no error CDB: 2A 00 00 13 38 86 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 72 0B 00 00 00 00 00 0E 09 0C 00 00 00 02 00 00 Sense Key: 0x0 No Additional Sense, Segment 11 Sense Code: 0x00 Qual 0x02 (end-of-partition/medium detected) Fru 0x0 Sense flags: Blk 0 (not valid) resid: 63488 cmd finished after 231.684s timeout 100s write track pad data: error after 2579771392 bytes ./cdrecord: Input/output error. read buffer cap: scsi sendcmd: fatal error CDB: 5C 00 00 00 00 00 00 00 0C 00 resid: 12 cmd finished after 0.000s timeout 100s ./cdrecord: Cannot blank disk, aborting. ./cdrecord: Input/output error. prevent/allow medium removal: scsi sendcmd: fatal error CDB: 1E 00 00 00 00 00 cmd finished after 0.000s timeout 100s and in /var/log/messages I get this errors: Feb 22 09:59:23 smooth kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Feb 22 09:59:23 smooth kernel: ata3.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x2a data 63488 out Feb 22 09:59:23 smooth kernel: res 40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4 (timeout) Feb 22 09:59:28 smooth kernel: ata3: port is slow to respond, please be patient (Status 0x80) Feb 22 09:59:33 smooth kernel: ata3: device not ready (errno=-16), forcing hardreset Feb 22 09:59:33 smooth kernel: ata3: soft resetting port Feb 22 10:00:03 smooth kernel: ata3.00: qc timeout (cmd 0xa1) Feb 22 10:00:03 smooth kernel: ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) Feb 22 10:00:03 smooth kernel: ata3.00: revalidation failed (errno=-5) Feb 22 10:00:03 smooth kernel: ata3: failed to recover some devices, retrying in 5 secs Feb 22 10:00:13 smooth kernel: ata3: port is slow to respond, please be patient (Status 0x80) Feb 22 10:00:18 smooth kernel: ata3: device not ready (errno=-16), forcing hardreset Feb 22 10:00:18 smooth kernel: ata3: soft resetting port Feb 22 10:00:48 smooth kernel: ata3.00: qc timeout (cmd 0xa1) Feb 22 10:00:48 smooth kernel: ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) Feb 22 10:00:48 smooth kernel: ata3.00: revalidation failed (errno=-5) Feb 22 10:00:48 smooth kernel: ata3.00: limiting speed to UDMA/100:PIO3 Feb 22 10:00:48 smooth kernel: ata3: failed to recover some devices, retrying in 5 secs Feb 22 10:00:58 smooth kernel: ata3: port is slow to respond, please be patient (Status 0x80) Feb 22 10:01:03 smooth kernel: ata3: device not ready (errno=-16), forcing hardreset Feb 22 10:01:03 smooth kernel: ata3: soft resetting port Feb 22 10:01:34 smooth kernel: ata3.00: qc timeout (cmd 0xa1) Feb 22 10:01:34 smooth kernel: ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) Feb 22 10:01:34 smooth kernel: ata3.00: revalidation failed (errno=-5) Feb 22 10:01:34 smooth kernel: ata3.00: disabled Feb 22 10:01:34 smooth kernel: ata3: EH complete yours Arnold Am 21.02.2008 um 19:23 schrieb Joerg Schilling: Arnold Maderthaner [EMAIL PROTECTED] wrote: The only thing I want to have is that I cannot mount it anymore with the previous filesystem (all tracks should be removed). I already tried cdrecord dev=x,y,z blank=all but it didn't work: [EMAIL PROTECTED] bin]# ./cdrecord dev=3,0,0 blank=all Cdrecord-ProDVD-ProBD-Clone 2.01.01a37 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2008 J?rg Schilling scsidev: '3,0,0' scsibus: 3 target: 0 lun: 0 Linux sg driver version: 3.5.34 ./cdrecord: Warning Linux Bus mapping botch. ./cdrecord: Warning Linux Bus mapping botch. ./cdrecord: Warning Linux Bus mapping botch. ./cdrecord: Warning Linux Bus mapping botch. Using libscg version 'schily-0.9'. Device type: Removable CD-ROM Version: 5 Response Format: 2 Capabilities : Vendor_info: 'LITE-ON ' Identifikation : 'BD B LH-2B1S'
Re: Blanking/Formating a BD-RE
Arnold Maderthaner wrote: Hi ! I applied the patch and now I get this: [EMAIL PROTECTED] bin]# ./cdrecord dev=3,0,0 blank=all Cdrecord-ProDVD-ProBD-Clone 2.01.01a37 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2008 J?rg Schilling scsidev: '3,0,0' scsibus: 3 target: 0 lun: 0 Linux sg driver version: 3.5.34 ./cdrecord: Warning Linux Bus mapping botch. ./cdrecord: Warning Linux Bus mapping botch. ./cdrecord: Warning Linux Bus mapping botch. ./cdrecord: Warning Linux Bus mapping botch. Using libscg version 'schily-0.9'. Device type: Removable CD-ROM Version: 5 Response Format: 2 Capabilities : Vendor_info: 'LITE-ON ' Identifikation : 'BD B LH-2B1S' Revision : 'AL09' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Using generic SCSI-3/mmc-3 BD-RE driver (mmc_bdre). Driver flags : NO-CD BD MMC-3 BURNFREE Supported modes: PACKET SAO LAYER_JUMP Starting to write CD/DVD/BD at speed 2 in real BLANK mode for single session. Last chance to quit, starting real write0 seconds. Operation starts. Running pad based emulation to blank the medium. secsize 2048 padbytes 25025314816 padblocks 12219392 maxblocks 12219392 Track 00:0 of 23866 MB pad written. ./cdrecord: Input/output error. write_g1: scsi sendcmd: no error CDB: 2A 00 00 13 38 86 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 72 0B 00 00 00 00 00 0E 09 0C 00 00 00 02 00 00 Sense Key: 0x0 No Additional Sense, Segment 11 Sense Code: 0x00 Qual 0x02 (end-of-partition/medium detected) Fru 0x0 Sense flags: Blk 0 (not valid) resid: 63488 cmd finished after 231.684s timeout 100s write track pad data: error after 2579771392 bytes ./cdrecord: Input/output error. read buffer cap: scsi sendcmd: fatal error CDB: 5C 00 00 00 00 00 00 00 0C 00 resid: 12 cmd finished after 0.000s timeout 100s ./cdrecord: Cannot blank disk, aborting. ./cdrecord: Input/output error. prevent/allow medium removal: scsi sendcmd: fatal error CDB: 1E 00 00 00 00 00 cmd finished after 0.000s timeout 100s You are running as root, correct? This looks like stuff I used to get when no running as root. -- E. Robert Bogusta It seemed like a good idea at the time -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Blanking/Formating a BD-RE
Yes I'm running it as root on RHEL5.1 with newest cdrecord with the patch that Joerg send. Btw. after that crash the BD-RE drive cannot be used anymore. I had to reboot the system. yours Arnold Am 22.02.2008 um 15:06 schrieb Rob Bogus: Arnold Maderthaner wrote: Hi ! I applied the patch and now I get this: [EMAIL PROTECTED] bin]# ./cdrecord dev=3,0,0 blank=all Cdrecord-ProDVD-ProBD-Clone 2.01.01a37 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2008 J?rg Schilling scsidev: '3,0,0' scsibus: 3 target: 0 lun: 0 Linux sg driver version: 3.5.34 ./cdrecord: Warning Linux Bus mapping botch. ./cdrecord: Warning Linux Bus mapping botch. ./cdrecord: Warning Linux Bus mapping botch. ./cdrecord: Warning Linux Bus mapping botch. Using libscg version 'schily-0.9'. Device type: Removable CD-ROM Version: 5 Response Format: 2 Capabilities : Vendor_info: 'LITE-ON ' Identifikation : 'BD B LH-2B1S' Revision : 'AL09' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Using generic SCSI-3/mmc-3 BD-RE driver (mmc_bdre). Driver flags : NO-CD BD MMC-3 BURNFREE Supported modes: PACKET SAO LAYER_JUMP Starting to write CD/DVD/BD at speed 2 in real BLANK mode for single session. Last chance to quit, starting real write0 seconds. Operation starts. Running pad based emulation to blank the medium. secsize 2048 padbytes 25025314816 padblocks 12219392 maxblocks 12219392 Track 00:0 of 23866 MB pad written. ./cdrecord: Input/output error. write_g1: scsi sendcmd: no error CDB: 2A 00 00 13 38 86 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 72 0B 00 00 00 00 00 0E 09 0C 00 00 00 02 00 00 Sense Key: 0x0 No Additional Sense, Segment 11 Sense Code: 0x00 Qual 0x02 (end-of-partition/medium detected) Fru 0x0 Sense flags: Blk 0 (not valid) resid: 63488 cmd finished after 231.684s timeout 100s write track pad data: error after 2579771392 bytes ./cdrecord: Input/output error. read buffer cap: scsi sendcmd: fatal error CDB: 5C 00 00 00 00 00 00 00 0C 00 resid: 12 cmd finished after 0.000s timeout 100s ./cdrecord: Cannot blank disk, aborting. ./cdrecord: Input/output error. prevent/allow medium removal: scsi sendcmd: fatal error CDB: 1E 00 00 00 00 00 cmd finished after 0.000s timeout 100s You are running as root, correct? This looks like stuff I used to get when no running as root. -- E. Robert Bogusta It seemed like a good idea at the time -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Blanking/Formating a BD-RE
Arnold Maderthaner [EMAIL PROTECTED] wrote: Yes I'm running it as root on RHEL5.1 with newest cdrecord with the patch that Joerg send. Btw. after that crash the BD-RE drive cannot be used anymore. I had to reboot the system. If you need to reboot, you found a kernel bug. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Blanking/Formating a BD-RE
Do you know where I should post it or what I could use else for writing and cleaning BD-RE ? yours Arnold Am 22.02.2008 um 17:56 schrieb Joerg Schilling: Arnold Maderthaner [EMAIL PROTECTED] wrote: Yes I'm running it as root on RHEL5.1 with newest cdrecord with the patch that Joerg send. Btw. after that crash the BD-RE drive cannot be used anymore. I had to reboot the system. If you need to reboot, you found a kernel bug. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
Blanking/Formating a BD-RE
Hi ! How can I format/blank a BD-RE so that it appears as new (never written) media ? I have tried with newest cdrecord version and dvd+rw- tools but I don't know how to format it. Hope someone can help me with my BD-RE problems. yours Arnold -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Blanking/Formating a BD-RE
Arnold Maderthaner [EMAIL PROTECTED] wrote: Hi ! How can I format/blank a BD-RE so that it appears as new (never written) media ? I have tried with newest cdrecord version and dvd+rw- tools but I don't know how to format it. Hope someone can help me with my BD-RE problems. BD-RE cannot ever be turned back into never written state. Cdrecord simulates a blank option Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Blanking/Formating a BD-RE
Hi, The only thing I want to have is that I cannot mount it anymore with the previous filesystem (all tracks should be removed). Tracks ? Plural ? On BD-RE ? From the specs i read that BD-RE is overwriteable media like DVD-RAM or DVD+RW. So the operating system does not see any tracks but a random access disk. It would therefore try to read the filesystem info from the default address on such disks. In case of a ISO 9660 filesystem this would be the blocks beginning with number 16 (= 32 kB). If your drive has address /dev/sr0 this command dd bs=2048 skip=16 count=1 if=/dev/sr0 | od -c | less will show the decisive line 000 001 C D 0 0 1 001 \0 If you overwrite the first 32 blocks by zeros then the media will surely not be recognized as mountable ISO filesystem. dd bs=2048 count=32 if=/dev/zero of=/dev/sr0 Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
