Creed just hangs in the middle of ripping.
https://pastebin.com/2hyGyfB7
Creed
Re: Creed
Does Linux log anything regarding the hang?
The debug code at the end of the log also occurs earlier at the same location. Mike's the one with the magic debug decoder ring, so this is one that he'll have to answer.
The debug code at the end of the log also occurs earlier at the same location. Mike's the one with the magic debug decoder ring, so this is one that he'll have to answer.
MakeMKV Frequently Asked Questions
FAQ about BETA and PERMANENT keys.
How to aid in finding the answer to your problem: Activating Debug Logging
FAQ about BETA and PERMANENT keys.
How to aid in finding the answer to your problem: Activating Debug Logging
Re: Creed
usb 4-6: reset SuperSpeed USB device number 3 using xhci_hcd
[ 1316.882997] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1316.883000] sr 7:0:0:0: [sr0] tag#0 Sense Key : Medium Error [current]
[ 1316.883002] sr 7:0:0:0: [sr0] tag#0 Add. Sense: L-EC uncorrectable error
[ 1316.883004] sr 7:0:0:0: [sr0] tag#0 CDB: Read(10) 28 00 00 f8 bd 60 00 00 c0 00
[ 1316.883005] print_req_error: critical medium error, dev sr0, sector 65205632
[ 1374.999476] usb 4-6: reset SuperSpeed USB device number 3 using xhci_hcd
[ 1411.851559] usb 4-6: reset SuperSpeed USB device number 3 using xhci_hcd
[ 1316.882997] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1316.883000] sr 7:0:0:0: [sr0] tag#0 Sense Key : Medium Error [current]
[ 1316.883002] sr 7:0:0:0: [sr0] tag#0 Add. Sense: L-EC uncorrectable error
[ 1316.883004] sr 7:0:0:0: [sr0] tag#0 CDB: Read(10) 28 00 00 f8 bd 60 00 00 c0 00
[ 1316.883005] print_req_error: critical medium error, dev sr0, sector 65205632
[ 1374.999476] usb 4-6: reset SuperSpeed USB device number 3 using xhci_hcd
[ 1411.851559] usb 4-6: reset SuperSpeed USB device number 3 using xhci_hcd
Re: Creed
OK, it looks like Linux is not passing through the read error to MakeMKV.
By the log, this is a USB drive, powered by the USB port. Is it plugged into a fully-powered USB 3.x port, or a hub? USB-powered drives can shut down if you spin them too fast for the available USB power. A fully-powered USB 3.x should not have this issue, but a non-powered hub can be a problem.
Do you have available a USB flash drive big enough to hold the movie, and formatted in NTFS? If so, can you set that as the destination drive, and try the rip again? Flash drives can't accept full read speed (usually), which throttles MakeMKV, and MAY make this problem "go away". If it does, getting full power to the drive will be the permanent fix.
By the log, this is a USB drive, powered by the USB port. Is it plugged into a fully-powered USB 3.x port, or a hub? USB-powered drives can shut down if you spin them too fast for the available USB power. A fully-powered USB 3.x should not have this issue, but a non-powered hub can be a problem.
Do you have available a USB flash drive big enough to hold the movie, and formatted in NTFS? If so, can you set that as the destination drive, and try the rip again? Flash drives can't accept full read speed (usually), which throttles MakeMKV, and MAY make this problem "go away". If it does, getting full power to the drive will be the permanent fix.
MakeMKV Frequently Asked Questions
FAQ about BETA and PERMANENT keys.
How to aid in finding the answer to your problem: Activating Debug Logging
FAQ about BETA and PERMANENT keys.
How to aid in finding the answer to your problem: Activating Debug Logging
Re: Creed
I was referring to slowing the write - the Samsung SSD will accept data faster than even MakeMKV can pull from an optical disk, so it won't serve as a "throttle".
Using a USB flash drive limits the writing speed, so MakeMKV can't spin the optical disk as fast. A USB 2.x flash drive is optimal for testing, because it will limit read speeds to the 5-6x range. If that makes the rip succeed, then the optical drive is not able to run at full speed with the power available.
Using a USB flash drive limits the writing speed, so MakeMKV can't spin the optical disk as fast. A USB 2.x flash drive is optimal for testing, because it will limit read speeds to the 5-6x range. If that makes the rip succeed, then the optical drive is not able to run at full speed with the power available.
MakeMKV Frequently Asked Questions
FAQ about BETA and PERMANENT keys.
How to aid in finding the answer to your problem: Activating Debug Logging
FAQ about BETA and PERMANENT keys.
How to aid in finding the answer to your problem: Activating Debug Logging
Re: Creed
Drat.... I have so many 64- and 128-GB flash drives I use for transfers I forget that not everyone does that.
MakeMKV Frequently Asked Questions
FAQ about BETA and PERMANENT keys.
How to aid in finding the answer to your problem: Activating Debug Logging
FAQ about BETA and PERMANENT keys.
How to aid in finding the answer to your problem: Activating Debug Logging