Page 1 of 2
"No disc" message
Posted: Mon Apr 26, 2021 7:46 pm
by vacantrush
I have MakeMKV 1.16.3 installed, have a registered license and generally have had zero issues ripping BluRays with MakeMKV and that's why I purchased it!
I am having issues with one particular disc though - the Chasing Legends cycling documentary BluRay. I am able to watch the BluRay on my Xbox One X without any issues, so that's a relief. I thought maybe my WH16NS40 drive could be the issue, but I was able to insert three different BluRays and MakeMKV recognized them without any issues. When loading the Chasing Legends BluRay, the drive spins, makes a bunch of noises and such for an entire minute while "loading..." and eventually displays "No disc"
Hopefully the description of my experience and the information below will be enough to begin troubleshooting...
Debug log started at Mon Apr 26 19:23:03 2021 , written by MakeMKV v1.16.3 win(x64-release)
001005:0000 MakeMKV v1.16.3 win(x64-release) started
001004:0000 Debug logging enabled, log will be saved as file://C:\Users\REDACTED/MakeMKV_log.txt
Using 262272KB for read cache.
Network access is ENABLED, CURL version 7.72.0/Schannel/1.41.0 (x86_64-pc-win32) , proxy server not set.
DEBUG: Code 3 at HFuPt/Gy+]n6ub.|sx^Z;r\.:29395310
SDF v07e: HL-DT-ST_BD-RE__WH16NS40_1.03_211711211653_M68ICEL1411
Application exited at Mon Apr 26 19:44:18 2021
Drive Information
OS device name: E:
Manufacturer: HL-DT-ST
Product: BD-RE WH16NS40
Revision: 1.03
Serial number: M68ICEL1411
Firmware date: 2117-11-21 16:53
Bus encryption flags: 17
Highest AACS version: 70
LibreDrive Information
Status: Possible (with patched firmware)
Drive platform: MT1959
Harware support: Yes
Firmware support: No
Firmware type: Original (patched version available)
Firmware version: 1.03
DVD all regions: Possible (with patched firmware)
BD raw data read: Possible (with patched firmware)
BD raw metadata read: Possible (with patched firmware)
Unrestricted read speed: Possible (with patched firmware)
No disc inserted
Re: "No disc" message
Posted: Mon Apr 26, 2021 10:25 pm
by Billycar11
Clean the disc
Re: "No disc" message
Posted: Tue Apr 27, 2021 4:10 pm
by vacantrush
Billycar11 wrote: ↑Mon Apr 26, 2021 10:25 pm
Clean the disc
It's a brand new disc. I lightly cleaned it with a lint-free microfiber cloth anyways. No change.
Re: "No disc" message
Posted: Tue Apr 27, 2021 4:52 pm
by Woodstock
Lint-free cloths don't deal with the chemical film more and more packaging deposits on discs. See the topic, "If you're experiencing read errors" above.
Re: "No disc" message
Posted: Wed Apr 28, 2021 2:26 pm
by vacantrush
Alright, I mixed a drop of Dawn dish soap in a bowl with warm water. Using a soft dish towel, I cleaned the bottom of the disc, rinsed and wiped dry. It still does not read the disc.
Debug log started at Wed Apr 28 14:21:54 2021 , written by MakeMKV v1.16.3 win(x64-release)
001005:0000 MakeMKV v1.16.3 win(x64-release) started
001004:0000 Debug logging enabled, log will be saved as file://C:\Users\User/MakeMKV_log.txt
Using 262272KB for read cache.
Network access is ENABLED, CURL version 7.72.0/Schannel/1.41.0 (x86_64-pc-win32) , proxy server not set.
DEBUG: Code 3 at HFuPt/Gy+]n6ub.|sx^Z;r\.:29395310
SDF v07e: HL-DT-ST_BD-RE__WH16NS40_1.03_211711211653_M68ICEL1411
Any other ideas?
Re: "No disc" message
Posted: Wed Apr 28, 2021 10:21 pm
by Billycar11
clean disc
new disc
clean drive
get BU40N
Re: "No disc" message
Posted: Wed Apr 28, 2021 11:42 pm
by dcoke22
If there's another optical drive you can try, that could help. Perhaps on another computer? Or a friend?
Re: "No disc" message
Posted: Tue May 18, 2021 8:21 pm
by vacantrush
Coincidentally, I have two WH16NS40 drives. Yesterday, I swapped them out. Same issue as before.
Re: "No disc" message
Posted: Wed May 19, 2021 12:56 am
by Billycar11
vacantrush wrote: ↑Tue May 18, 2021 8:21 pm
Coincidentally, I have two WH16NS40 drives. Yesterday, I swapped them out. Same issue as before.
should have gotten a BU40N not the same drive.
by chance this is not a UHD disc is it? because you dont have the firmware for that
Re: "No disc" message
Posted: Fri May 28, 2021 3:50 am
by Ravik
Here's something additional information that may be relevant to this conversation. Hope it helps!
I am also encountering a "no disc" error, where the drive cannot read my disc. The disc is brand new from a sealed package and 100% scratch-free from what I can see with 20/20 vision. I also have both an LG-WH16NS40 and ASUS BW-16D1HT which are both LibreDrive enabled via updated firmware, and the ASUS drive is only a week old (also fresh out of box). So here we have an ideal testing scenario.
As I said the disc is "brand new" and fresh from a sealed case and has no visible defects on the surface or the label whatsoever. Yet it will not load in either my LG or ASUS drives. So for kicks I downloaded PowerDVD 21 to see if I could get it to open through a third-party application, but no luck. And honestly I didn't expect anything special there because the disc doesn't appear to be load in either drives via "My Computer". This falls in-line with the "drive cannot read disc" theory.
...but then I took the disc over to my PS4 PRO and tried to load it using the Bluray application...and it WORKED!
I'm absolutely shocked by this result. Because unless the PlayStation features some kind of overreading access that I'm unaware of and can see part of the lead-in on the disc that normal drives cannot...there should be no reason my PS4 can read the disc and my LibreDrive LG and ASUS drives can't. It just doesn't add up.
edit: I've attempted to load the disc in my PC drives at least a dozen times since with zero success. But the PlayStation loads every time.
Thoughts?
-Ravik-
Re: "No disc" message
Posted: Fri May 28, 2021 6:09 am
by Billycar11
Ravik wrote: ↑Fri May 28, 2021 3:50 am
.
Thoughts?
-Ravik-
Those drives are trash they are literally the same get a BU40N and watch it work
But before doing that it is best to clean the disc to rule that out
Re: "No disc" message
Posted: Sat May 29, 2021 6:55 am
by Ravik
Well, "trash" may be a bit of an over-exaggeration since they normally work great for me (and rip full speed vs. as opposed to the BU40N), but I will consider picking up a BU40N to give this the a proper testing. I'll post my results once I have one in-hand. I also ordered a replacement disc to vet the "bad mastering" theory. I've run into this issue before with at least two other discs, and buying a replacement disc seemed to fix the issues. However, I'm obsessed with figuring this out now, so I'm willing to throw some money at this problem to see if we can perhaps identify the issue.
EDIT: BU40N ordered. We'll see how your claim holds up shortly. I'm cautiously optimistic, yet simultaneously hopeful. And if it DOES read, then I think I know what the problem is. Stay tuned!
Re: "No disc" message
Posted: Fri Jun 04, 2021 9:55 pm
by Ravik
@Billycar11 — Confirmed success with the BU40N. You were right! This little drive is amazing.
Which leads me to my theory: I believe console drives feature enhanced overreading capabilities (that or the lens isn't limited by the base firmware). This makes sense because over-reading and lead-in methods are known forms of copy protection used by some systems, and disc-based consoles typically need to offer support for a wide variation of optical media.
That said, I do believe the "no disc" error has more to do with bad mastering of the disc than as a security measure, and I have a second disc still en route to test this. It wouldn't make sense from a business standpoint for movie companies to engineer their Bluray discs so they couldn't be played on commercial Bluray drives, right??
I'll post my results with the replacement disc once it arrives, but in the meantime I can at least confirm that an LG BUF0N is an excellent drive for reading discs with a "no disc" error. And if you're getting this error on a working BUF0N then try reading it in a console. If it reads, then your BUF0N may be damaged or you may be dealing with a non-standard optical format. Otherwise if you're getting a fail on both systems then your disc is likely just trashed and will need to be replaced.
Cheers!
-Ravik-
Re: "No disc" message
Posted: Sat Jun 05, 2021 4:35 am
by Billycar11
Ravik wrote: ↑Fri Jun 04, 2021 9:55 pm
@Billycar11 — Confirmed success with the BU40N. You were right! This little drive is amazing.
Cheers!
-Ravik-
nice glad it worked out for you.
you see i have no reason to make it up i just know from testing so many of these drives i even recommend them to people who are not buying from me
Re: "No disc" message
Posted: Sun Aug 01, 2021 10:40 am
by masterdot
I have a similar problem.
It did try to rip Fanboys yesterday (german release) and after that my Asus seems to be broken.
It did try to decrypt, but ended with no key for that disc (anyway: what could I do? It did save some dump file?)
I did try several discs now, did restart etc, but nothing did help.
The other drive (a pioneer) is working fine. Didnt try the fanboys disc yet.
May it be possible that the disc did damage the drive? Or is it a urban legend?
Thanks for your help!
Btw: the BU40N seems to be the best drive avaible, right? It is possible to put two drives in one 5,25" slot?
Code: Select all
Drive Information
OS device name: /dev/sr0
Manufacturer: ASUS
Product: BW-16D1HT
Revision: 3.00
Serial number: xxx
Firmware date: 2115-11-03 11:10
Bus encryption flags: 1F
Highest AACS version: 72
LibreDrive Information
Status: Enabled
Drive platform: MT1959
Firmware type: Original (unpatched)
Firmware version: 3.00
DVD all regions: Yes
BD raw data read: Yes
BD raw metadata read: Yes
Unrestricted read speed: Yes
No disc inserted
Followup:
I did flash the ASUS with the latest mk firmware. It works again and seems to be invincible against the fanboys bluray.
It still can't read the disc completly, it starts well, but in the end it stops with errors.
I dont dare to put the disc into the pioneer drive
But the firmware update was a easy thing and has a great effect. Thanks for that!
Code: Select all
MakeMKV v1.16.4 linux(x64-release) started
Using LibreDrive mode (v06.2 id=0FA242DD4D0B)
Using direct disc access mode
Loaded content hash table, will verify integrity of M2TS files.
Title #00053.mpls has length of 50 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00054.mpls has length of 29 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00055.mpls has length of 340 seconds which is less than minimum title length of 900 seconds and was therefore skipped
File 00100.mpls was added as title #0
Title #00017.mpls has length of 8 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00003.m2ts has length of 19 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00004.m2ts has length of 11 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00005.m2ts has length of 5 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00008.m2ts has length of 7 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00009.m2ts has length of 7 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00010.m2ts has length of 1 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00011.m2ts has length of 1 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00013.m2ts has length of 10 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00014.m2ts has length of 10 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00015.m2ts has length of 23 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00016.m2ts has length of 50 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00017.m2ts has length of 29 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00032.m2ts has length of 1 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00033.m2ts has length of 1 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00034.m2ts has length of 1 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00041.m2ts has length of 4 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00050.m2ts has length of 4 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00051.m2ts has length of 4 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00018.m2ts has length of 340 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00069.m2ts has length of 30 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00056.m2ts has length of 128 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00080.m2ts has length of 318 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00081.m2ts has length of 226 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00082.m2ts has length of 605 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00083.m2ts has length of 605 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00084.m2ts has length of 134 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Operation successfully completed
Saving 1 titles into directory /output/STORKS
AV synchronization issues were found in file '/output/STORKS/title_t00.mkv' (title #1)
AV sync issue in stream 5 at 0:00:00 : Forced subtitles track #5 turned out to be empty and was removed from output file
AV sync issue in stream 7 at 0:00:00 : Forced subtitles track #7 turned out to be empty and was removed from output file
AV sync issue in stream 9 at 0:00:00 : Forced subtitles track #9 turned out to be empty and was removed from output file
1 titles saved
Using LibreDrive mode (v06.2 id=0FA242DD4D0B)
Using direct disc access mode
Loaded content hash table, will verify integrity of M2TS files.
Using Java runtime from /usr/bin/java
Title #00003.mpls has length of 11 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00004.mpls has length of 12 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00005.mpls has length of 7 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00051.mpls has length of 129 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00052.mpls has length of 153 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00053.mpls has length of 152 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00054.mpls has length of 133 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00199.mpls has length of 60 seconds which is less than minimum title length of 900 seconds and was therefore skipped
File 00009.mpls was added as title #0
Title #00061.mpls has length of 129 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00062.mpls has length of 153 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00063.mpls has length of 152 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00064.mpls has length of 133 seconds which is less than minimum title length of 900 seconds and was therefore skipped
File 00522.mpls was added as title #1
Title #00523.mpls has length of 470 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00524.mpls has length of 66 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00525.mpls has length of 52 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00526.mpls has length of 102 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00527.mpls has length of 95 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00528.mpls has length of 82 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00529.mpls has length of 70 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00530.mpls has length of 348 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00531.mpls has length of 317 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00532.mpls has length of 530 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00533.mpls has length of 698 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00538.mpls has length of 220 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00539.mpls has length of 132 seconds which is less than minimum title length of 900 seconds and was therefore skipped
File 00540.mpls was added as title #2
Title #00006.mpls has length of 129 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00007.mpls has length of 153 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title 00001.mpls is equal to title 00009.mpls and was skipped
Title 00554.mpls is equal to title 00522.mpls and was skipped
Title #00100.mpls has length of 132 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title 00602.mpls is equal to title 00009.mpls and was skipped
Title #00001.m2ts has length of 11 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00002.m2ts has length of 12 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00003.m2ts has length of 7 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00004.m2ts has length of 67 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00005.m2ts has length of 65 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00007.m2ts has length of 65 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00008.m2ts has length of 65 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00009.m2ts has length of 10 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00011.m2ts has length of 60 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00013.m2ts has length of 129 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00014.m2ts has length of 153 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00015.m2ts has length of 152 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00016.m2ts has length of 133 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00023.m2ts has length of 66 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00024.m2ts has length of 52 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00025.m2ts has length of 102 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00026.m2ts has length of 95 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00027.m2ts has length of 82 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00028.m2ts has length of 70 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00029.m2ts has length of 348 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00030.m2ts has length of 317 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00031.m2ts has length of 530 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00032.m2ts has length of 116 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00033.m2ts has length of 220 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00034.m2ts has length of 132 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title 00035.m2ts is equal to title 00540.mpls and was skipped
Title #00036.m2ts has length of 115 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00037.m2ts has length of 39 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00038.m2ts has length of 139 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00039.m2ts has length of 82 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00040.m2ts has length of 68 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00041.m2ts has length of 135 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Title #00044.m2ts has length of 60 seconds which is less than minimum title length of 900 seconds and was therefore skipped
Operation successfully completed
Saving 1 titles into directory /output/Fanboys
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00000.m2ts' at offset '17303470080'
Error 'Posix error - Input/output error' occurred while reading '/dev/sr0' at offset '17303470080'
Error 'Posix error - Input/output error' occurred while reading '/dev/sr0' at offset '17303470080'
Error 'Posix error - Input/output error' occurred while reading '/dev/sr0' at offset '17303470080'
Error 'Posix error - Input/output error' occurred while reading '/dev/sr0' at offset '17303470080'
Error 'Posix error - Input/output error' occurred while reading '/dev/sr0' at offset '17303470080'
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00000.m2ts' at offset '17303470080'
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00000.m2ts' at offset '17303470080'
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00000.m2ts' at offset '17303470080'
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00000.m2ts' at offset '17303470080'
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00000.m2ts' at offset '17303470080'
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00000.m2ts' at offset '17303470080'
Failed to save title 0 to file /output/Fanboys/Fanboys-T1_t00.mkv
Encountered 11 errors of type 'Read Error' - see http://www.makemkv.com/errors/read/
0 titles saved, 1 failed