Scsi error - HARDWARE ERROR:TRACK FOLLOWING ERROR
Posted: Tue Aug 08, 2023 1:25 pm
Hello forum, Ive been reading the forum for a while but this is my first post. I recently ran into an error that I wanted to discuss that I believe runs contrary to the previous discussion but first some backstory.
backstory: After having a few amazon kindle titles vanish from my kindle, that I paid money for, due to some amazon->author pissing match I realized that my digital copies on Vudu/Movies Anywhere/Amazon Video were not as safe as I would like. So I have embarked on ripping my entire video collection to streaming format to place on my Plex server. First using MakeMKV to rip the feature film and then Handbrake to process the video into h.264/h.265 format for smaller file size. I have over 400 Blueray, 75 DVD that werent replaced by Bluray, and maybe 12 UHD discs. So far I have ripped 283 of the titles not including entire complete series of TV shows like Clone Wars, Firefly, Avatar the Last Airbender, and Farscape. I have been doing this since mid June now keeping my device running from around 8am to around 10pm non-stop.
So I have now had this issue of a track following error 3 times now, spaced waaaay far apart. Like I could rip another 75 discs before this appears again. But there is a trend that simply cannot be ignored because I simply do not believe in coincidences. Here are the common trends
Based on a lot of experimentation I think I can safely say that the discs are not injured or defective. I can also say that given my blu-ray drive seems to work on ever title that ISNT these 3 Dreamworks Animation titles I think we can rule out a 'failing drive'. I can entertain the possibility that maybe a higher end drive might be needed for some Dreakworks titles (actually had no problem with my 3 Madagascar movies and the 1 Penguins movie). However the fact that the drive itself could read this portion of the disc at slower speeds may indicate that its only when trying to rip at the full 6x speed thats the problem.
One comment that I read in my investigation was someone suggesting copy protection does not include hardware read errors. Whoever said that must be a Millenial or GenZ. Any GenX worth his/her Salt remembers that the original copy protection in the old Infocom games (zork etc) deliberately put errors on the disc to circumvent the C:\>copy.exe command. Hence how the utility diskcopy.exe evolved in order to copy everything including sector errors.
Given that the only way to repeat this bug is with these specific dreaworks titles and only with makemkv, Is it not possible that Dreamworks Studio engineered a disc that plays perfectly fine in a regular player at 1x speeds but somehow fails at higher speeds? Could they not have altered the geometry of that portion of the disc to have narrower lands and dots to make reading at faster speeds extremely difficult?
backstory: After having a few amazon kindle titles vanish from my kindle, that I paid money for, due to some amazon->author pissing match I realized that my digital copies on Vudu/Movies Anywhere/Amazon Video were not as safe as I would like. So I have embarked on ripping my entire video collection to streaming format to place on my Plex server. First using MakeMKV to rip the feature film and then Handbrake to process the video into h.264/h.265 format for smaller file size. I have over 400 Blueray, 75 DVD that werent replaced by Bluray, and maybe 12 UHD discs. So far I have ripped 283 of the titles not including entire complete series of TV shows like Clone Wars, Firefly, Avatar the Last Airbender, and Farscape. I have been doing this since mid June now keeping my device running from around 8am to around 10pm non-stop.
So I have now had this issue of a track following error 3 times now, spaced waaaay far apart. Like I could rip another 75 discs before this appears again. But there is a trend that simply cannot be ignored because I simply do not believe in coincidences. Here are the common trends
- All 3 discs are a DREAMWORKS Animation blu-ray (The Croods, Home, Megamind)
- all 3 disc are pristinely clean with no scratches no smudges. We're talking mirror polish here, one was never even played before
- All 3 discs play fine on my PS5, PS4, and Sony BD player
- All 3 discs I limited the rip to the bare essentials (just the main feature mpls title, no subtitles, and just the 1 lossless audio track like TrueHD or DTS-HD MA so I can reprocess that later as 640k AC3 or 1536k E-AC3)
- In every case the segment map is a single segment of the entire movie
- In every case I encounter this error right around the 50% point of that m2ts file
- In every case repeated tries results in error at the same spot
- In every case I can browse in windows file explorer to the /BDMV/STREAM/xxxxx.m2ts and copy that encrypted file to my computer storage. However, when it gets to the 50% mark the xfer rate drops from 7MB/sec to around 1MB/sec for about 5 min before resuming
Based on a lot of experimentation I think I can safely say that the discs are not injured or defective. I can also say that given my blu-ray drive seems to work on ever title that ISNT these 3 Dreamworks Animation titles I think we can rule out a 'failing drive'. I can entertain the possibility that maybe a higher end drive might be needed for some Dreakworks titles (actually had no problem with my 3 Madagascar movies and the 1 Penguins movie). However the fact that the drive itself could read this portion of the disc at slower speeds may indicate that its only when trying to rip at the full 6x speed thats the problem.
One comment that I read in my investigation was someone suggesting copy protection does not include hardware read errors. Whoever said that must be a Millenial or GenZ. Any GenX worth his/her Salt remembers that the original copy protection in the old Infocom games (zork etc) deliberately put errors on the disc to circumvent the C:\>copy.exe command. Hence how the utility diskcopy.exe evolved in order to copy everything including sector errors.
Given that the only way to repeat this bug is with these specific dreaworks titles and only with makemkv, Is it not possible that Dreamworks Studio engineered a disc that plays perfectly fine in a regular player at 1x speeds but somehow fails at higher speeds? Could they not have altered the geometry of that portion of the disc to have narrower lands and dots to make reading at faster speeds extremely difficult?