NajChris11

Members
  • Posts

    8
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

NajChris11's Achievements

Newbie

Newbie (1/14)

2

Reputation

  1. Was having issues connecting to my other containers and this fixed it. Thanks!
  2. Thank you for your response! It looks like that was a hardware failure on my end that appears any time I try to rip one particular CD. Thank you though! I'll look into ways to modify the .sh file to either omit special characters or to substitute them with friendlier characters.
  3. Hey! I had a weird problem with Docker the other day, and after a restart, I went back into the Ripper log to find these errors. Any ideas as to how I can remedy this? scsi_read error: sector=188698 length=27 retry=0 Sense key: 3 ASC: 11 ASCQ: 0 Transport error: Medium reading data from medium System error: Input/output error scsi_read error: sector=188698 length=13 retry=1 Sense key: 3 ASC: 11 ASCQ: 0 Transport error: Medium reading data from medium System error: Input/output error scsi_read error: sector=188698 length=6 retry=2 Sense key: 3 ASC: 11 ASCQ: 0 Transport error: Medium reading data from medium System error: Input/output error These errors repeated for a few days until I caught them. They actually may have been the cause of the Docker error but I'm not entirely sure. Any help would be appreciated!
  4. I've actually come across the same problem! If you can use the command line to check where the files would normally be located, the files are all there and will show up in a normal file manager after a quick rename. But yeah I think tweaking the the .sh file to maybe even omit special characters would definitely help. @Phonejudgement
  5. This is the thread for docker-ripper right? Thats the container i was running and that's what it says when I try to use it to rip audio CDs. I'm installing the latest update right now and I can take a screenshot to include if necessary. Thanks.
  6. Hey guys. Anyone else having this problem? I can get the Ripper container to rip ISOs and DVDs without a problem... but anytime I use CDs, there's suddenly a problem. I checked in the Ripper.log file, and it says that "Rip file *insert here* not found... Ripping *insert here*... Trying again without paranoia. cdparanoia III release 10.2 (September 11, 2008) 006: Could not read any data from drive cdparanoia could not find a way to read audio from this drive. 006: Could not read any data from drive cdparanoia could not find a way to read audio from this drive. cdparanoia failed on track *insert here* Rip file *insert here* not found..." I've tried reinstalling the container several times. Any help would be appreciated.
  7. Hello! I just installed the Ripper docker image for the purpose of ripping my CDs. Unfortunately, it feels like I've hit every roadblock since starting. Initially, I was using the docker log and I saw that it simply said, "09.08.2020 23:13:36 : CD detected: Saving MP3 and FLAC" After waiting and not seeing any files get processed, I decided to check the appdata log and found these errors. This one claims that it can't find matching metadata for the disk: "No connection to internet? The error message is: cannot connect to cddb db: freedb.freedb.org:8880 [Invalid argument] at /usr/share/perl5/CDDB_get.pm line 310." This one simply won't let the disk be read at all: " 23:13:37: Ripping "01 Track 01"... cdparanoia III release 10.2 (September 11, 2008) 006: Could not read any data from drive cdparanoia could not find a way to read audio from this drive. Rip file 01 Track 01.rip not found.." Any ideas as to what could cause this? Thank you.