luisv

Sorry guys... I was able to backup the disc successfully, then used Handbrake to convert the backup to MKV.

Thanks, I'll give it a try! Again, thanks for the help!

Backing up is working! What Handbrake settings are you using as I prefer to preserve all surround sound formats. Since this question is out of the MakeMKV docker realm, feel free to PM me about Handbrake. Thanks for your help!

Yes, Day of the Soldado.

Here are the results now; however, I still get the error when trying to rip the disc.

Now this error: sh: cp : not found

I get the following message, sorry, never tried console access for a container before. sh: /usr/bin: Permission denied

Is that performed within the docker or docker properties?

I checked the MakeMKV forums and I don't see any posts for this specific disc. Sorry, but I don't recall if other discs have required Java or not as it usually works or works once the docker is updated. I went back a few versions, stopped at v1.8.0 as all had the same issue / failure. I'll keep my eye on the MakeMKV forums for any updates as it's a recently released disc, so others should have similar issues. Thanks for your time!

As luck would have it, it seems to be related to the new disk. I grabbed a bunch of others that were succesful and they are working just fine. Wierd, I've never had an issue like this before, so I assumed it was due to the upgrade. Is there a way to run a previous version of the container? Sorry, but I don't recall what version I was previously running.

After the upgrade, I inserted a disk to rip and after 20 seconds or so, it errors out. I ripped a disk successfully last week or so.

Upgraded docker to the 1.12.3 and receiving this error today. Any ideas? kernel: makemkvcon[4276]: segfault at 8 ip 000000000060c65d sp 000014cf32b8beb0 error 4 in makemkvcon[400000+5db000]

Thanks! I'll see what I can do.

Current cables are 18" long, going with 8 - 10" instead, but yes, I'll make sure there's no strain on the connectors. Thanks!

It's a small form factor ITX build, so yes, cable management is tight with SATA and power cables in close proximity of one another. I used a SATA power cable adapter as it was easier to route than the PSU SATA cable, but I can remove it and reroute things. I also ordered shorter SATA data cables to help with the rats nest. I'm using an EVGA G3 650w power supply. The preclear completed successfully and no additional errors were found; however, here are the UDMA CRC error counts: Parity - 2 Disk 1 - 3 Disk 2 - 2 Disk 3 -1 After 2 Parity checks, the CRC errors remained the same... no other errors found.

For sure, many thanks and kudos to @dlandon @Squid @Frank1940 and those behind the scenes that worked on this!

Just noticed this in the log. Mar 30 09:29:40 MiniVault kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT0._GTF, AE_NOT_FOUND (20170728/psparse-550) Mar 30 09:29:40 MiniVault kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) Mar 30 09:29:40 MiniVault kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT3._GTF, AE_NOT_FOUND (20170728/psparse-550) Mar 30 09:29:40 MiniVault kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) Mar 30 09:29:40 MiniVault kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT0._GTF, AE_NOT_FOUND (20170728/psparse-550) Mar 30 09:29:40 MiniVault kernel: ata4.00: configured for UDMA/133 Mar 30 09:29:40 MiniVault kernel: ata4: EH complete Mar 30 09:29:40 MiniVault kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Mar 30 09:29:40 MiniVault kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) Mar 30 09:29:40 MiniVault kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT2._GTF, AE_NOT_FOUND (20170728/psparse-550) Mar 30 09:29:40 MiniVault kernel: ata1.00: configured for UDMA/133 Mar 30 09:29:40 MiniVault kernel: ata1: EH complete Mar 30 09:29:40 MiniVault kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) Mar 30 09:29:40 MiniVault kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT2._GTF, AE_NOT_FOUND (20170728/psparse-550) Mar 30 09:29:40 MiniVault kernel: ata3.00: configured for UDMA/133 Mar 30 09:29:40 MiniVault kernel: ata3: EH complete Mar 30 09:29:41 MiniVault kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) Mar 30 09:29:41 MiniVault kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT1._GTF, AE_NOT_FOUND (20170728/psparse-550) Mar 30 09:29:41 MiniVault kernel: ata2.00: configured for UDMA/133 Mar 30 09:29:41 MiniVault kernel: ata2: EH complete

No sure totally understandable. Just wanted to indicate that parts weren't repurposed.

Everything being used in this second smaller system is brand new, no drive enclosure, no additional controller card, using the built-in controller of the Asrock Z370M-ITX Motherboard.

Hmm... new cables and new 650w PSU. Safe to assume, nothing to worry about at this point of time?

Currently running this on four HGST 6TB drives and on step 2 zeroing, all four indicated a UDMA CRC error count with a count of 1.

Worked perfectly, thanks!

Any thoughts on what I should do? Migrated without an issue and Tautulli runs perfectly, but should I delete/ remove the PleyPy docker? I ask as the migration instructions said to use the existing PlexPy appdata folder for /config, so I assume if I remove PlexPy it would delete that PlexPay appdata folder and break Tautilli.

Great, very easy process to migrate. Should I leave the PlexPy docker in place, but not running or can it be removed?

Folders? Where do you set that?