- Package:
- dvd+rw-tools
- Source:
- dvd+rw-tools
- Description:
- DVD+-RW/R tools
- Submitter:
- Martin Emrich
- Date:
- 2010-01-30 15:09:09 UTC
- Severity:
- important
I have a NEC ND-1300A DVD Recorder. With +R/+RW Media, it works fine,
but with DVD-R(W), I get these messages all over again:
martin@garrett:~/bin$ growisofs -dvd-compat
-Z/dev/cdrecorder=/home/martin/temp/t3shrink.iso
Executing 'builtin_dd if=/home/martin/temp/t3shrink.iso
of=/dev/cdrecorder obs=32k seek=0'
/dev/cdrecorder: "Current Write Speed" is 2.0x1385KBps.
:-! "COMMAND SEQUENCE ERROR"@LBA=0h. Is media being read?
:-! the LUN appears to be stuck at 0h, retrying in 5 secs...
0/4682485760 ( 0.0%) @0x, remaining ??:??
:-! "COMMAND SEQUENCE ERROR"@LBA=0h. Is media being read?
:-! the LUN appears to be stuck at 0h, retrying in 5 secs...
0/4682485760 ( 0.0%) @0x, remaining ??:??
:-! "COMMAND SEQUENCE ERROR"@LBA=0h. Is media being read?
:-! the LUN appears to be stuck at 0h, retrying in 5 secs...
growisofs does not react to SIGTERM, I have to SIGKILL it.
My Device: "DVD_RW ND-1300A ", Firmware revision 1.08.
Ciao
Martin Emrich
This sound too very much as if user was running growisofs 5.16. I mean "command sequence error" in the very beginnig of -dvd-compat DVD-R recording is pretty much the definition of 5.14 through 5.16. Martin! Can you really confirm that 'growisofs -version' returns 5.17? Is it possible that old version was present on your $PATH by the time you experienced the problem? E.g. I can see you were standing in ~/bin and if you have/had old version there and . in your $PATH, then you might as well have picked old version. What would 'which growisofs' print by the time you experienced the problem? Signals get blocked in the very beginning of recording. It was necessary to do that to overcome firmware problems in some units. So that it a way, yes, you have to kill -KILL it is it hangs early enough. If problem persists with 5.17 (really with 5.17, run explicitly /usr/bin/growisofs if you have to:-), submit 'dvd+rw-mediainfo /dev/cdrecorder verbose' output right after growisofs suffers from this error. A.
Hi, having the same problem as bug #231693. I can swear it's not an <=5.16 version, this is 5.21 (kernel 2.4.26): /dev/sr0: "Current Write Speed" is 2.0x1385KBps. :-! "COMMAND SEQUENCE ERROR"@LBA=0h. Is media being read? :-! the LUN appears to be stuck at 0h, retrying in 5 secs... $ dvd+rw-mediainfo /dev/dvdrw verbose INQUIRY: [TOSHIBA ][DVD-ROM SD-R5112][1031] MODE SENSE[#3Fh]: 01: 00 0a 00 00 00 00 00 00 00 00 05: 60 c4 08 10 00 00 00 00 00 00 00 00 00 96 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 08: 04 00 00 00 00 00 00 00 00 00 0D: 00 0e 00 3c 00 4b 0E: 04 00 00 00 00 4b 01 ff 02 ff 00 00 00 00 1A: 00 03 00 00 00 96 00 00 24 ea 1D: 00 00 04 00 00 78 00 00 2A: 3f 17 f5 77 29 23 1b 90 00 10 08 00 1b 90 00 18 0b 06 0b 06 00 01 00 00 00 00 0b 06 00 05 00 00 0b 06 00 00 08 45 00 00 06 e4 00 00 05 83 00 00 02 c2 READ DVD STRUCTURE[#FF]: STRUCTURE#00 40:2052 STRUCTURE#01 40:8 STRUCTURE#02 40:2052 STRUCTURE#03 40:192 STRUCTURE#04 40:2052 STRUCTURE#05 40:8 STRUCTURE#06 40:24 STRUCTURE#07 40:24580 STRUCTURE#0e 40:68 STRUCTURE#0f 40:22 STRUCTURE#10 40:2052 STRUCTURE#c0 40:8 STRUCTURE#ff 40:56 GET [CURRENT] CONFIGURATION: 0000: 00 10 00 00 00 08 00 00 00 09 00 00 00 0a 00 00 00 11 00 00 00 13 00 00 00 14 01 00 0001: 00 00 00 02 0002: 00 00 00 00 0003: 29 00 00 00 0004: 02 00 00 00 001D: 0021: 01 00 01 01 10 00 00 00 0023: 002F: 46 00 00 00 0100: 0105: 0107: 1c 00 00 00 0108: 33 37 4c 52 30 33 30 32 36 34 20 20 Mounted Media: 14h, DVD-RW Sequential READ DVD STRUCTURE[#0eh]: 00 42 00 00 01 40 d6 fd 9e d8 21 00 02 0e 08 06 88 85 0d 00 03 4d 43 43 20 30 31 00 04 52 57 31 31 6e 39 00 05 06 88 85 0d 00 00 00 Media ID: MCC 01RW11n9 GET CURRENT PERFORMANCE: 02 00 00 00 00 00 00 00 00 00 0a 8c 00 23 10 1f 00 00 0a 8c Write Performance: 1.9x1385=2700KB/s@[0 -> 2297887] GET PERFORMANCE: 00 00 00 00 00 23 12 7f 00 00 05 46 00 00 0a 8c Speed Descriptor#0: 00/2298495 R@1.0x1385=1350KB/s W@1.9x1385=2700KB/s READ DVD STRUCTURE[#10h]: 32 02 02 00 00 03 00 00 00 26 12 7f 00 00 00 00 Media Book Type: 32h, DVD-RW book [revision 2] Legacy lead-out at: 2298496*2KB=4707319808 READ DVD STRUCTURE[#0h]: 32 02 02 00 00 03 00 00 00 03 00 00 00 00 00 00 Media Book Type: 32h, DVD-RW book [revision 2] Last border-out at: 0*2KB=0 READ DISC INFORMATION: 00 20 10 01 01 01 01 20 ff 00 00 00 00 00 00 00 Disc status: blank Number of Sessions: 1 State of Last Session: empty Number of Tracks: 1 READ FORMAT CAPACITIES: unformatted: 2297888*2048=4706074624 00h(800): 2297888*2048=4706074624 10h(10): 2297888*2048=4706074624 15h(10): 2297888*2048=4706074624 READ TRACK INFORMATION[#1]: 00 22 01 01 00 04 61 01 00 00 00 00 00 00 00 00 Track State: invisible incremental Track Start Address: 0*2KB Next Writable Address: 0*2KB Free Blocks: 2297888*2KB Track Size: 2297888*2KB :-[ READ TOC failed with SK=5h/ASC=24h/ACQ=00h]: Input/output error READ CAPACITY: 1*2048=2048
Is it minimally blanked media? See http://lists.debian.org/cdwrite/2004/08/msg00237.html. Seems like Toshiba units fail to "tell" that DAO is the only available option. There is remote possibility that media reload might help in this situation. I.e. if one finds -use-the-force-luke=dao longer to type than reload tray. A.
V Čt, 09. 09. 2004 v 16:15, Andy Polyakov píše: I have always used blank=fast since that was enough for later burning with cdrecord.ProDVD. Never needed to blank=all a DVD-RW. well, after spending a hour by blank=all the growisofs really burns data without complaints. couldn't the growisofs be smart enough to fall back to dao instead of annoying "crying for dao" (=printing those errors). Or how about using dao by default? Petr
P> well, after spending a hour by blank=all the growisofs really burns data It's not about growisofs, but about Toshiba firmware. growisofs is capable of detecting when DAO is the only option and it's known to work with a number of units. Toshiba firmware apparently leads it to wrong conclusions and you have to help it by complementing growisofs command line with -use-the-force-luke=dao. Or how about formatting the media for Restricted Overwrite *once* and forgetting all this blanking and DAO issues? It's way more practical. A.
Hi! Today, I tried burning a DVD-R, and it works (growisofs 5.21). So at some time between 5.16 and 5.21, the bugs seems to be fixed. As soon as I get to it, I'll try a DVD-RW too. Ciao Martin