🐛Error 'Scsi error - ILLEGAL REQUEST:INVALID FIELD IN CDB' occurred while issuing SCSI command 460200010..00100 to device #720
Comments
|
If youre having issues, please remember to read the wiki and follow the instructions carefully |
|
Can you use the image |
|
I would also need the full output from MakeMKVcon the lines you have posted could be related to multiple issues.
Was this working while MakeMKV was updated ? |
|
ok tried with another image using I'll try looking at the solution for #140, didn't see that when searching for issues, so I guess I need to get better at searching. I have to run but will try your item 1 and get back to this as soon as I can. |
|
Hmm, here's my MakeMKVcon output: root@807e327afc33:/home/arm# makemkvcon -r info disk:0 |
|
WOoow, I've been typing that wrong. I'm stupid. it should be disc not disk.... I also upgraded MakeMKV to 1.17.3 at least for the running of it manually: Now it looks like that same message 5010 failed to open disk from #140. So onto the next step. root@807e327afc33:/home/arm# makemkvcon -r info disc:0 |
|
Ok interesting, if I mount the drive and pass in the file: source instead it seems to get some info not sure if it is everything the arm_ripper is expecting though or if I can get away with not using disc at any point. In the Portainer Docker console to debug I ran: Then I ran Which gave me: Do you see any future concerns if I modified the code to use a file: source instead of a disc: source? |
|
Darn didn't seem to work, I ran And it output the following: But when I check |
|
Oh I need the word |
|
From the output from the last test, possibly the disk is corrupt? Have you tried with a different DVD/Blueray/CD in the drive to confirm, 1 the disk isn't bad, or 2 the drive hasn't failed? |
1337-server
changed the title
|
Well that latest error was an issue with the drive. I ended up unplugging and plugging the drive back in and rebooting the host. I was able to finally successfully call the mkv directly using (Also used a different disc first to see if that was my problem, but finally saw some mounting errors when trying to mount manually which is why I unplugged, plugged it back in, and rebooted.) However, I am still unable to run the main arm command successfully, it still errors on disk:0. Which has me thinking it is the same issue as #140 So I guess I will have to try their solution of just using a usb drive / adapter. Darn. (I might try to manually run the rest of the code with this file to see if I can get the end result, but I don't think all of the commands will work with Thanks all for your help, very helpful folks here!! |
|
Closing as resolved |
|
yah. thanks for closing this. I think I was doing stuff wrong in the end. or had the wrong drive. or should not have been running it in a VM. thanks for all the support and quick responses! |
|
I am having a similar issue with proxmox and a Blu-ray drive that I have connected by sata. I have tried a lot of different options in attempting to get the sata connection to work, but I did not come up with anything. I was eventually able to get a usb blu-ray player to work with minimal issues. Can you explain a little where you are putting "file:" Thanks |
|
I was testing a what the automatic ripper does by running the raw command through a shell session. I ran this as shown above: But instead put the work Also I switched to a DVD in that above file call. I don't think it was working at all with bluerays because I bought the wrong drives. Make sure you buy from this list and flash the firmware to open libra. I have yet to buy the correct drive and try it again with a blue ray. |
|
I've also been trying to use a SATA blu-ray drive in a Proxmox VM. Following an absolute wizard's suggestion, it's finally working. In Proxmox, add arguments to the VM (
Reference: https://forum.proxmox.com/threads/how-to-do-a-scsi-passthrough.111505/post-483233 |
|
Sweet, thanks for adding that info here!! I will have to give this a try on my setup and if I get it working too, I'll reply. |
Is there an existing issue for this?
Does this issue exist in the latest version?
Describe the bug?
I setup the 1337server/automatic-ripping-machine:latest docker image.
I bought my own key for makemkv because I kept getting the error to upgrade or register.
Now I get the error:
PRGV:0,0,65536
MSG:2004,16777216,4,"Error 'Scsi error - ILLEGAL REQUEST:INVALID FIELD IN CDB' occurred while issuing SCSI command 460200010..00100 to device 'SG:dev_21:0'","Error '%1' occurred while issuing SCSI command %4 to device '%2:%3'","Scsi error - ILLEGAL REQUEST:INVALID FIELD IN CDB","SG","dev_21:0","460200010..00100"
MSG:5010,0,0,"Failed to open disc","Failed to open disc"
Which appears to be happening after:
[02-11-2023 19:52:51] INFO ARM: Using MakeMKV to get information on all the tracks on the disc. This will take a few minutes...
[02-11-2023 19:52:52] INFO ARM: Found 0 titles
So maybe when it is calling "get_track_info"?
I'm not sure. I'm confused as to why I'd have a Scsi error if I'm using Sata. Also I'm seeing it get the name of the DVD so it is apparently there and mounted.
I've tried a DVD and a Blueray and they both give this same error at this same point.
Anyone know what my problem is or is this a bug?
Is there an easy way to set the debug level to debug instead of just info?
To Reproduce
Steps to Reproduce:
Built from source files ?
What architecture are you seeing the problem on?
Other (Please state in
Anything elsesection)Expected behavior?
Expected behavior?
Not sure, how to get past this error or what to debug next?
Relevant log output
Anything else?
I am running this in a docker container on a proxmox x64 server.
From the settings page:
Python version: 3.8.10
A.R.M version: 2.6.12
Update Available: update image You are on the latest version
Code of Conduct
The text was updated successfully, but these errors were encountered: