Avatar: Fire and Ash UHD - BW-16D1HT fails at same offset during both MKV extraction and full Backup

[whswede]

Hi,

I am having a reproducible issue with the new Avatar: Fire and Ash UHD.

Drive Information:

ASUS BW-16D1HT
Firmware 3.10
LibreDrive enabled
Firmware type: Patched (microcode access re-enabled)

Disc Information:

Avatar: Fire and Ash UHD
Retail disc, purchased new
Label: AVATAR_FIRE_AND_ASH
UHD BD-ROM (triple layer)
AACS2.0/C v82

The disc opens normally in MakeMKV. All playlists are scanned successfully and the main feature is detected correctly.

However, both MKV extraction and a full Backup with "Decrypt video files" enabled fail at exactly the same location every time:

Scsi error - ILLEGAL REQUEST: INVALID FIELD IN CDB

while reading:

/BDMV/STREAM/00294.m2ts

at offset:

2913730560

I have tested the following:

Multiple attempts
Retry Count increased from 10 to 50
Disc cleaned thoroughly with water and mild detergent
Full Backup with decrypt enabled
Standard MKV extraction

All tests fail at exactly the same file and offset.

Additional observations:

Other UHD discs rip successfully on the same drive.
LibreDrive appears to be functioning normally.
The disc structure is read correctly.
The main feature is detected correctly.
A Panasonic UB820 standalone player appears to play the disc normally, although I have not yet watched the entire movie.

What makes me question whether this is a simple bad-disc issue is that the error is consistently:

ILLEGAL REQUEST: INVALID FIELD IN CDB

rather than the more typical MEDIUM ERROR / UNRECOVERED READ ERROR.

After the initial failure, MakeMKV repeatedly retries the read operation and generates many instances of:

OS error - The specified request is not a valid operation for the target device

always at the same offset.

Has anyone else seen this with Avatar: Fire and Ash UHD?

Does this look like:

a defective disc,
a known issue with this UHD release,
or a compatibility issue between this title and certain UHD drives such as the BW-16D1HT?

Any feedback would be appreciated.

Thanks.

[bplewis24]

I don't have the details handy, but I had been having at least a similar issue with this disc. For me, it would always fail around 31GB or 32GB into the rip. Is that the same for you?

[dcoke22]

Try power cycling your drive and rebooting your computer.

[whswede]

Update:

After rebooting Windows, the behavior changed significantly.

The rip no longer fails at /BDMV/STREAM/00294.m2ts offset 2913730560.

This time MakeMKV progressed for about 55 minutes and produced approximately 28.7 GB before failing.

The new failure occurred at:

/BDMV/STREAM/00681.m2ts

offset 25980358656

The error remains:

ILLEGAL REQUEST: INVALID FIELD IN CDB

[dcoke22]

How is your drive connected to your computer? It is in an external enclosure?

[whswede]

The drive is connected internally via SATA directly to the motherboard. It is not in an external enclosure.

[bplewis24]

I don't have the details handy, but I had been having at least a similar issue with this disc. For me, it would always fail around 31GB or 32GB into the rip. Is that the same for you?

So, I just received my replacement disc. For me the offset is occuring at 2686666752. By the way, I have the same drive and firmware (Asus BW-16D1HT 3.10). This is the second disc I'm having this issue with. And I can confirm the supplier mentioned they have multiple complaints on this disc.

I'm going to attempt one more rip and see if the offset is the same place. I couldn't get a reading on the file size at time of failure because the file was removed upon failure.

[whswede]

Update:

I have now tested multiple MKV extraction attempts, a full Backup, increased Retry Count to 50, Windows reboot, and a complete power-off restart.

The failure point is not completely consistent, but all attempts eventually fail with:

Scsi error - ILLEGAL REQUEST: INVALID FIELD IN CDB

Failures observed so far:

00294.m2ts @ 2913730560
00681.m2ts @ 25980358656
00684.m2ts @ 9851068416
00684.m2ts @ 9855645696
Backup failed at disc offset 66730065920

The two most recent MKV extraction attempts both failed in 00684.m2ts at nearly the same offset.

[Andyg4000]

Did you managed to fix this? - Thanks

I am seeing:-

Too many AV synchronization issues in file '/BDMV/STREAM/00681.m2ts' (title #-) , future messages will be printed only to log file
Hash check failed for file 00681.m2ts at offset 16659965952, file is corrupt.
Hash check failed for file 00681.m2ts at offset 16660162560, file is corrupt.
Hash check failed for file 00681.m2ts at offset 16660359168, file is corrupt.
Hash check failed for file 00681.m2ts at offset 16660555776, file is corrupt.
Too many hash check errors in file 00681.m2ts.

[whswede]

I returned the disc a week or so ago and I am waiting for the replacement. Will post back with results.

[Andyg4000]

OK - Thanks for the reply

[whswede]

Update: Received the replacement disc and ran a full set of tests.

MKV extraction (latest MakeMKV): Two attempts, both failed. Most recent fail: title 11, offset 367392768 — same ILLEGAL REQUEST: INVALID FIELD IN CDB error, different offset than the original disc.
Full raw Backup (Decrypt unchecked): 174 files failed hash check, with many separate STREAM files failing right at offset 0, spread across the whole disc structure. Since this bypasses decryption entirely, it rules out an AACS/decryption-handling issue.
DVDFab UHD Ripper (different engine entirely): Couldn't read the disc at all — ejected it.

So the failure now spans two completely different ripping engines, two separate physical discs, and both raw and decrypted read modes — all with a fully unlocked LibreDrive setup (BD raw data/metadata read: Yes, AACS v82). At this point it doesn't look like a MakeMKV bug or a single defective disc, but something more fundamental with this pressing/drive combination. Posting in case anyone else confirms similar results with a different tool.

[whswede]

For anyone following: swapped from my ASUS BW-16D1HT to a Verbatim external drive with a Pioneer BDR-UD04 mechanism, running in Direct disc access mode. Clean full rip of the replacement disc with MakeMKV, ZERO errors!

Seems it was the ASUS drive that was the actual problem. However it worked fine with other 4k-titles just a day or so ago and I will retry other titles onwards.

[Andyg4000]

Update: Received the replacement disc and ran a full set of tests.

MKV extraction (latest MakeMKV): Two attempts, both failed. Most recent fail: title 11, offset 367392768 — same ILLEGAL REQUEST: INVALID FIELD IN CDB error, different offset than the original disc.
Full raw Backup (Decrypt unchecked): 174 files failed hash check, with many separate STREAM files failing right at offset 0, spread across the whole disc structure. Since this bypasses decryption entirely, it rules out an AACS/decryption-handling issue.
DVDFab UHD Ripper (different engine entirely): Couldn't read the disc at all — ejected it.

So the failure now spans two completely different ripping engines, two separate physical discs, and both raw and decrypted read modes — all with a fully unlocked LibreDrive setup (BD raw data/metadata read: Yes, AACS v82). At this point it doesn't look like a MakeMKV bug or a single defective disc, but something more fundamental with this pressing/drive combination. Posting in case anyone else confirms similar results with a different tool.

I played the UHD on a Sony PS5, it did glitch middway through ... but when re-played it was OK.

For MakeMKV I am seeing :-

Code: Select all

The source file '/BDMV/STREAM/00681.m2ts' is corrupt or invalid at offset 17069813760, attempting to work around
The source file '/BDMV/STREAM/00681.m2ts' is corrupt or invalid at offset 17069813760, attempting to work around
The source file '/BDMV/STREAM/00681.m2ts' is corrupt or invalid at offset 17069813760-17069819904, attempting to work around
The source file '/BDMV/STREAM/00681.m2ts' is corrupt or invalid at offset 17069819904, attempting to work around
The source file '/BDMV/STREAM/00681.m2ts' is corrupt or invalid at offset 17069819904, attempting to work around
The source file '/BDMV/STREAM/00681.m2ts' is corrupt or invalid at offset 17069819904, attempting to work around
The source file '/BDMV/STREAM/00681.m2ts' is corrupt or invalid at offset 17069819904, attempting to work around
The source file '/BDMV/STREAM/00681.m2ts' is corrupt or invalid at offset 17069819904, attempting to work around
The source file '/BDMV/STREAM/00681.m2ts' is corrupt or invalid at offset 17069819904, attempting to work around
The source file '/BDMV/STREAM/00681.m2ts' is corrupt or invalid at offset 17069819904, attempting to work around
The source file '/BDMV/STREAM/00681.m2ts' is corrupt or invalid at offset 17069819904, attempting to work around
The source file '/BDMV/STREAM/00681.m2ts' is corrupt or invalid at offset 17069819904, attempting to work around
The source file '/BDMV/STREAM/00681.m2ts' is corrupt or invalid at offset 17069819904, attempting to work around
The source file '/BDMV/STREAM/00681.m2ts' is corrupt or invalid at offset 17069819904, attempting to work around
The source file '/BDMV/STREAM/00681.m2ts' is corrupt or invalid at offset 17069819904, attempting to work around
The source file '/BDMV/STREAM/00681.m2ts' is corrupt or invalid at offset 17069819904, attempting to work around
The source file '/BDMV/STREAM/00681.m2ts' is corrupt or invalid at offset 17069819904, attempting to work around
The source file '/BDMV/STREAM/00681.m2ts' is corrupt or invalid at offset 17069819904, attempting to work around
The source file '/BDMV/STREAM/00681.m2ts' is corrupt or invalid at offset 17069819904, attempting to work around
The source file '/BDMV/STREAM/00681.m2ts' is corrupt or invalid at offset 17069819904, attempting to work around
The source file '/BDMV/STREAM/00681.m2ts' is corrupt or invalid at offset 17069819904, attempting to work around
The source file '/BDMV/STREAM/00681.m2ts' is corrupt or invalid at offset 17069819904, attempting to work around
The source file '/BDMV/STREAM/00681.m2ts' is corrupt or invalid at offset 17069819904, attempting to work around
The source file '/BDMV/STREAM/00681.m2ts' is corrupt or invalid at offset 17069819904, attempting to work around
Too many AV synchronization issues in file '/BDMV/STREAM/00681.m2ts' (title #-) , future messages will be printed only to log file
Error 'OS error - {Data Overrun} A data overrun error occurred' occurred while reading '\Device\CdRom1' at offset '25795848192'

[whswede]

Thanks for that — useful data point. Between your PS5 glitch (recoverable) and my Panasonic UB820 playing the original disc perfectly fine, it seems like normal playback tolerates this disc a lot better than ripping does — buffered/retry-friendly playback vs. raw sector-by-sector extraction.
Your MakeMKV log is interesting too: "corrupt or invalid... attempting to work around" is a softer failure mode than the hard ILLEGAL REQUEST errors I was getting, and it's a different file (00681.m2ts) and a different drive (\Device\CdRom1 — what drive/mechanism are you running?). Combined with my results, it looks less like a single bad disc and more like this pressing having some genuinely marginal sectors that different drives/players handle with very different tolerance.
For what it's worth, my fix was switching from the ASUS BW-16D1HT to a Pioneer BDR-UD04 (Verbatim external), which ripped clean in Direct disc access mode. Might be worth trying a different drive if you can before giving up on the disc — curious whether it's specifically ASUS/MediaTek-based drives struggling here, or something else.