ILLEGAL REQUEST:INVALID FIELD IN CDB

Please post here for issues related to UHD discs
Post Reply
Rainer
Posts: 11
Joined: Tue Oct 30, 2018 7:20 pm

ILLEGAL REQUEST:INVALID FIELD IN CDB

Post by Rainer » Sat Feb 02, 2019 11:19 am

Log files:
I got several times something like
001011:0000 DEBUG: Code 03DF/03/E064BA3E3F81
DEBUG: Code 2147483648 at z3q2Zsw5q;dm{R\<:121265223
005085:0000 Loaded content hash table, will verify integrity of M2TS files.
001003:0020 DEBUG: Code 3221225628 at lWJ!.;^m82Xk/T<8[g6r6&f*:213130398
001003:0020 DEBUG: Code 3221225628 at sJb*g0<30Km#ErJn:121262417
001003:0020 DEBUG: Code 3221225653 at sJb*g0<30Km#ErJn:121262417
001003:0020 DEBUG: Code 3221225653 at sJb*g0<30Km#ErJn:121262417
001003:0020 DEBUG: Code 3221225653 at sJb*g0<30Km#ErJn:121262417
001003:0020 DEBUG: Code 3221225653 at sJb*g0<30Km#ErJn:121262417
001003:0020 DEBUG: Code 101000192 at 9?`hsEse`7s9iol;:121269317
001003:0020 DEBUG: Code 101000192 at sJb*g0<30Km#ErJn:121262417
001003:0020 DEBUG: Code 101000192 at 9?`hsEse`7s9iol;:121269317
001003:0020 DEBUG: Code 101000192 at sJb*g0<30Km#ErJn:121262417
001003:0020 DEBUG: Code 101000192 at 9?`hsEse`7s9iol;:121269317
001003:0020 DEBUG: Code 101000192 at sJb*g0<30Km#ErJn:121262417
001003:0020 DEBUG: Code 101000192 at 9?`hsEse`7s9iol;:121269317
001003:0020 DEBUG: Code 101000192 at sJb*g0<30Km#ErJn:121262417
001003:0020 DEBUG: Code 101000192 at 9?`hsEse`7s9iol;:121269317
001003:0020 DEBUG: Code 101000192 at sJb*g0<30Km#ErJn:121262417
001003:0020 DEBUG: Code 101000192 at 9?`hsEse`7s9iol;:121269317
001003:0020 DEBUG: Code 101000192 at sJb*g0<30Km#ErJn:121262417
001003:0020 DEBUG: Code 101000192 at 9?`hsEse`7s9iol;:121269317
001003:0020 DEBUG: Code 101000192 at sJb*g0<30Km#ErJn:121262417
002003:0000 Error 'Scsi error - ILLEGAL REQUEST:INVALID FIELD IN CDB' occurred while reading '/BDMV/STREAM/00294.m2ts' at offset '28946657280'
001003:0020 DEBUG: Code 0 at )pYKsF6-M{40&1/[qlb:29397679
001003:0020 DEBUG: Code 0 at )pYKsF6-M{40&1/[qlb:121265131
001003:0020 DEBUG: Code 0 at J@5gvt}TIca8)f[\edO^:121265154
001003:0020 DEBUG: Code 233 at 3gInKawCDkgLi/3Ykxx2NnIA:0
001003:0020 DEBUG: Code 233 at 2nAIG0mf0KV8PnJDWiuASZPv:0
001003:0020 DEBUG: Code 233 at QlNTUa60yeqMU2wNassejOzn:0
001003:0020 DEBUG: Code 233 at Im2HGSTqrLv1rOCnhsSHtQaH:0
001003:0020 DEBUG: Code 233 at J4XG6o2O+VqDSUC88C1+U6oL:0
001003:0020 DEBUG: Code 233 at M78vO2ygza+luxoq7lSzyl8f:0
001003:0020 DEBUG: Code 233 at sj5Sn7RDzAAvtaMxmxTAxQZ9:0
001003:0020 DEBUG: Code 233 at 0PzOALO3B5rud4LFVA6g3mNL:0
001003:0020 DEBUG: Code 233 at oO5gwMXfXl9g+5Jk40cRaGUx:0
001003:0020 DEBUG: Code 233 at WGp/UDtAGuzKyjXyyCsb72Mq:0
Encountered 12 unclassified errors
error=0x06052400 count=7 name=Scsi error - ILLEGAL REQUEST:INVALID FIELD IN CDB
error=0xC000009C count=1 name=OS error - STATUS_DEVICE_DATA_ERROR
error=0xC00000B5 count=4 name=OS error - {Gerät-Zeitüberschreitung} Das Zeitlimit des angegebenen E/A-Vorgangs auf hs wurde erreicht, bevor der E/A-Vorgang abgeschlossen wurde
005069:0080 Backup failed
Only after the last cleaning I got a slightly different log:
Debug log started at Sat Feb 02 10:04:57 2019 , written by MakeMKV v1.14.2 win(x64-release)
Using 262272KB for read cache.
001005:0000 MakeMKV v1.14.2 win(x64-release) started
001004:0000 Debug logging enabled, log will be saved as C:\Users\Rainer/MakeMKV_log.txt
DEBUG: Code 2365587456 at 3tu+2QPU[=7Te!Z9e:29394620
005072:0000 Backing up disc into folder "D:/DVD/MakeMKV/backup/Test"
001011:0000 DEBUG: Code 03DF/03/E064BA3E3F81
DEBUG: Code 2147483648 at z3q2Zsw5q;dm{R\<:121265223
005085:0000 Loaded content hash table, will verify integrity of M2TS files.
001003:0020 DEBUG: Code 3221225628 at lWJ!.;^m82Xk/T<8[g6r6&f*:213130398
001003:0020 DEBUG: Code 3221225628 at sJb*g0<30Km#ErJn:121262417
001003:0020 DEBUG: Code 3221225653 at sJb*g0<30Km#ErJn:121262417
001003:0020 DEBUG: Code 3221225653 at sJb*g0<30Km#ErJn:121262417
001003:0020 DEBUG: Code 3221225653 at sJb*g0<30Km#ErJn:121262417
001003:0020 DEBUG: Code 3221225653 at sJb*g0<30Km#ErJn:121262417
001003:0020 DEBUG: Code 3221225653 at sJb*g0<30Km#ErJn:121262417
001003:0020 DEBUG: Code 3221225653 at sJb*g0<30Km#ErJn:121262417
001003:0020 DEBUG: Code 3221225653 at sJb*g0<30Km#ErJn:121262417
001003:0020 DEBUG: Code 3221225653 at sJb*g0<30Km#ErJn:121262417
001003:0020 DEBUG: Code 3221225653 at sJb*g0<30Km#ErJn:121262417
001003:0020 DEBUG: Code 3221225653 at sJb*g0<30Km#ErJn:121262417
002003:0000 Error 'OS error - {Gerät-Zeitüberschreitung} Das Zeitlimit des angegebenen E/A-Vorgangs auf hs wurde erreicht, bevor der E/A-Vorgang abgeschlossen wurde' occurred while reading '/BDMV/STREAM/00294.m2ts' at offset '29045618688'
001003:0020 DEBUG: Code 0 at )pYKsF6-M{40&1/[qlb:29397679
001003:0020 DEBUG: Code 0 at )pYKsF6-M{40&1/[qlb:121265131
001003:0020 DEBUG: Code 0 at J@5gvt}TIca8)f[\edO^:121265154
001003:0020 DEBUG: Code 233 at G7wWmAGLfoXY799KIZcI6ho3:0
001003:0020 DEBUG: Code 233 at BEhdN7q2TqPAF8jINHKo8r7+:0
001003:0020 DEBUG: Code 233 at ldO6yaTzydIEAFtGhUWkjTEg:0
Encountered 11 unclassified errors
error=0xC000009C count=1 name=OS error - STATUS_DEVICE_DATA_ERROR
error=0xC00000B5 count=10 name=OS error - {Gerät-Zeitüberschreitung} Das Zeitlimit des angegebenen E/A-Vorgangs auf hs wurde erreicht, bevor der E/A-Vorgang abgeschlossen wurde
005069:0080 Backup failed
005080:0204 Backup failed.
Application exited at Sat Feb 02 11:05:31 2019
I cleaned the disc 3 time but get again and agin the same error? Could the disc still be the problem? Other discs work.
What does code 233 mean?
Are unclassified errors normal?

After the first times (with Invalid Field in CDB message) the drive was gone and didn't show up in windows/makemkv. Only after I removed the disc and reconnected the drive (USB) it was shown in MakeMKV again.

thedigitalhobo
Posts: 39
Joined: Thu Jun 13, 2013 1:49 am
Contact:

Re: ILLEGAL REQUEST:INVALID FIELD IN CDB

Post by thedigitalhobo » Wed Mar 27, 2019 2:51 am

Just ran into the same issue.
No problem with most other discs.

Restarted the program immediately after, and got:
DEBUG: Code 3221225488 at /#i^dV2 QD51N^S+0^g8:29394390
The program can't find any usable optical drives.

Robert89
Posts: 2
Joined: Tue Mar 26, 2019 12:13 pm

Re: ILLEGAL REQUEST:INVALID FIELD IN CDB

Post by Robert89 » Wed Mar 27, 2019 1:39 pm

I have the same problem, this error never happened in the past

haemaker
Posts: 3
Joined: Tue Jan 01, 2019 2:21 am

Re: ILLEGAL REQUEST:INVALID FIELD IN CDB

Post by haemaker » Thu Apr 25, 2019 3:36 am

I just had the same problem. I fixed it by reverting to v1.12.3. I think Libradrive has some unresolved issues, going to a version before Libradrive works better on some disks.

Post Reply