WH14NS40 Disc not properly formatted or damaged disc (rootdirs failing)

[Bullhead]

[UPDATE 5/12/21] I returned the drive, got a brand new one, and flashed it to MK WH16NS40 Rev1.05 . I ran Back to the Future through again and got this. Why is this still happening with a new drive?

Code: Select all

AV synchronization issues were found in file 'Q://Back to the Future-SEG_MainFeature_t44.mkv' (title #45)
AV sync issue in stream 0 at 0:48:31.325 : secondary stream video frame timecode differs by +41.702ms
AV sync issue in stream 0 at 0:48:32.576 : secondary stream video frame timecode differs by +208.541ms
AV sync issue in stream 0 at 0:48:32.743 : secondary stream video frame timecode differs by +166.83ms
AV sync issue in stream 0 at 0:48:33.076 : secondary stream video frame timecode differs by -83.425ms
AV sync issue in stream 0 at 0:48:33.118 : video frame timecode differs by -41.711ms
AV sync issue in stream 0 at 0:48:33.160 : video frame timecode differs by -41.708ms
AV sync issue in stream 0 at 0:48:33.181 : video frame timecode differs by -20.862ms
AV sync issue in stream 0 at 0:48:33.181 : secondary stream video frame timecode differs by -20.862ms
AV sync issue in stream 0 at 0:48:33.222 : video frame timecode differs by -20.859ms
AV sync issue in stream 0 at 0:48:33.222 : secondary stream video frame timecode differs by -20.859ms
AV sync issue in stream 0 at 0:48:33.222 : secondary stream video frame timecode differs by +20.851ms
AV sync issue in stream 0 at 0:48:33.222 : secondary stream video frame timecode differs by +187.684ms
AV sync issue in stream 0 at 0:48:33.264 : video frame timecode differs by -20.856ms
AV sync issue in stream 0 at 0:48:33.285 : secondary stream video frame timecode differs by -208.544ms
AV sync issue in stream 0 at 0:48:33.285 : secondary stream video frame timecode differs by -166.833ms
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 66606133248, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 66606133248, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 66606133248, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 66606133248, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 66606133248, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 66606133248, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 66606133248, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 66606133248, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 66606133248, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 66606133248, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 66606133248, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 61440-67584, attempting to work around
AV sync issue in stream 1 at 1:56:02.164 with duration of 0.833ms : broken timecode, apparent audio skew is -6962.205s
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 285603840, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 285603840, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 285603840, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 285603840, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 285603840, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 285603840, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 285603840, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 285603840, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 285603840, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 285603840, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 285603840, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 285603840, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 285603840, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 285603840, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 285603840, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 285603840, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 285603840, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 285603840, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 285603840, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 285603840, attempting to work around
Hash check failed for file 00294.m2ts at offset 285665280, file is corrupt.
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 285603840, attempting to work around
Error 'Scsi error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred while reading '/BDMV/STREAM/00294.m2ts' at offset '33208135680'
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred while reading '\Device\CdRom3' at offset '33208135680'
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred while reading '\Device\CdRom3' at offset '33208135680'
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred while reading '\Device\CdRom3' at offset '33208135680'
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred while reading '\Device\CdRom3' at offset '33208135680'
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred while reading '\Device\CdRom3' at offset '33208135680'
Error 'Scsi error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred while reading '/BDMV/STREAM/00294.m2ts' at offset '33208135680'
Error 'Scsi error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred while reading '/BDMV/STREAM/00294.m2ts' at offset '33208135680'
Error 'Scsi error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred while reading '/BDMV/STREAM/00294.m2ts' at offset '33208135680'
Error 'Scsi error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred while reading '/BDMV/STREAM/00294.m2ts' at offset '33208135680'
Error 'Scsi error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred while reading '/BDMV/STREAM/00294.m2ts' at offset '33208135680'
Error 'Scsi error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred while reading '/BDMV/STREAM/00294.m2ts' at offset '33208135680'
AV sync issue in stream 0 at 1:56:02.121 : video stream has 18 frames with invalid timecodes
Failed to save title 44 to file Q://Back to the Future-SEG_MainFeature_t44.mkv
Encountered 11 errors of type 'Read Error' - see http://www.makemkv.com/errors/read/
Encountered 2 errors of type 'HashCheck Error' - see http://www.makemkv.com/errors/hashcheck/...
0 titles saved, 1 failed

[UPDATE] My disc is now showing slight circular scratches, which I looked up and it seems like a physical drive problem. I still don't understand why two other 4k discs from the same pack worked fine.

[UPDATE] I was able to replicate the issue where the disc was opened successfully but then backs out (it does it on the second try) --> https://drive.google.com/file/d/1_L3DCB ... 6dva3/view

I just bought a brand new LG WH14NS40 and flashed it to MK WH16NS40 Rev1.05 and it works perfectly EXCEPT FOR BACK TO THE FUTURE PART 1 4k UHD. I bought the BTTF trilogy 4k UHD brand new in factory packaging and all discs are flawless. I tried BTTF Part 1 4k UHD first and I have hearing rattle sounds from the drive and would get read errors. I decided to try other discs in the set. I have since ripped BTTF Part 2 4k UHD and Part 3 4k UHD without issue. With BTTF 1 4k UHD, sometimes I get HashCheck Errors, sometimes I get "disc not properly formatted or damaged disc (rootdirs failing)", sometimes the drive will show No disc, and sometimes the titles will show up and, just as I'm selecting the checkboxes, it closes out of that screen and goes back to the default No disc screen. I'm also hearing a physical noise from the drive when it's trying to read (as if the disc is off balance and causing the spindle to vibrate), which is EXACTLY the same sound as the UH12NS40 drive it replaced (that drive was six years old).

Here is what happens:

• Disc is inserted

• MakeMKV recognizes drive and disc

• I open the disc with MakeMKV

• Sometimes it will pull up the titles perfectly but will close out after a few seconds

• Other times there is a Read Error of some type

--> https://drive.google.com/file/d/1-Zufg0 ... JIK8i/view

[dcoke22]

viewtopic.php?f=8&t=15055 <-- rip errors

Th optical drive is having trouble correctly reading all the bits on the disc. The disc is likely dirty (perhaps in a way invisible to the naked eye) or maybe damaged if it has circular scratches.

[Bullhead]

viewtopic.php?f=8&t=15055 <-- rip errors

Th optical drive is having trouble correctly reading all the bits on the disc. The disc is likely dirty (perhaps in a way invisible to the naked eye) or maybe damaged if it has circular scratches.

These issues are happening with a brand new disc before any of the scratches. I checked and the scratches are barely visible. I had to put my phone on macro to see them. This wouldn't explain why the issue was worse with the disc when it was brand new. There is also another user with the exact same issue on the exact same disc. viewtopic.php?f=1&t=23859&p=108745#p108745

[dcoke22]

Sometimes discs have a nearly invisible film on them even when brand new from a factory sealed package. I find a gentle cleaning with warm water and dish soap can help.

Ripping UHDs is hard. The data density is very high which makes correctly reading all the data harder. Physically, the discs are the same size as a CD, which might hold 700MB of data. The most dense UHDs might hold 100GB, which is more than 100x more data in the same physical space.

A standard DVD/blu-ray/UHD player is a lossy device. If they have trouble reading data off a disc, they keep going. Most of the time, the errors are small enough that a normal person won't even see it. MakeMKV, on the other, tries to read all the data correctly. This makes a hard problem even harder.

Personally, I have two different UHD capable drives on my desk I use with MakeMKV. When a disc won't rip with the drive I normally use, it will often (although not always) rip just fine with my other drive.

[Bullhead]

Sometimes discs have a nearly invisible film on them even when brand new from a factory sealed package. I find a gentle cleaning with warm water and dish soap can help.

Ripping UHDs is hard. The data density is very high which makes correctly reading all the data harder. Physically, the discs are the same size as a CD, which might hold 700MB of data. The most dense UHDs might hold 100GB, which is more than 100x more data in the same physical space.

A standard DVD/blu-ray/UHD player is a lossy device. If they have trouble reading data off a disc, they keep going. Most of the time, the errors are small enough that a normal person won't even see it. MakeMKV, on the other, tries to read all the data correctly. This makes a hard problem even harder.

Personally, I have two different UHD capable drives on my desk I use with MakeMKV. When a disc won't rip with the drive I normally use, it will often (although not always) rip just fine with my other drive.

Thank you very much for taking the time to write that out. It does make more sense in that context. Even when I was reading the sticky post about read errors, it didn't really explain what you did. I'll try a more thorough approach to cleaning the disc since the drives are new.