docker-ripper is doing a great job on audio and video optical disks for me right now and its been running most of the day - awesome stuff!
Beiträge von Nick0
-
-
EDIT#1: Just used your one and it looks like its working fine. Will update later on.
EDIT#2: All looks good. I just ssh'd in and it looks like its ripping away nicely. Thanks!
OK, sorry - here is my latest stab at it:
Hopefully this isn't totally wrong.
Code
Alles anzeigenversion: '3.3' services: docker-ripper: container_name: Ripper volumes: - '/srv/dev-disk-by-uuid-00aa265f-40dd-4db1-821e-e32892a6ed2c/compose/ripper/config/:/config:rw' - '/srv/dev-disk-by-uuid-00aa265f-40dd-4db1-821e-e32892a6ed2c/compose/ripper/out/:/out:rw' devices: - '/dev/sr0:/dev/sr0' - '/dev/sg2:/dev/sg2' ports: - 'port:9090:9090' # optional - port for the integrated web ui environment: - PREFIX=OPTIONAL_WEB_UI_PATH_PREFIX # optional - path prefix for the integrated web ui - USER=OPTIONAL_WEB_UI_USERNAME # optional - user name for the integrated web ui (requires PASS to be set) - PASS=OPTIONAL_WEB_UI_PASSWORD # optional - password for the integrated web ui (requires USER to be set) privileged: true # optional - only use when your drive is not detected inside the container image: rix1337/docker-ripper:manual-latest
-
Ah, thanks ryecoaaron - I did try that but I get the same error:
Code
Alles anzeigenFailed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; docker compose --file '/srv/dev-disk-by-uuid-00aa265f-40dd-4db1-821e-e32892a6ed2c/compose/ripper/ripper.yml' --env-file '/srv/dev-disk-by-uuid-00aa265f-40dd-4db1-821e-e32892a6ed2c/compose/ripper/ripper.env' --env-file '/srv/dev-disk-by-uuid-00aa265f-40dd-4db1-821e-e32892a6ed2c/compose/global.env' up -d 2>&1': 1 error(s) decoding: * error decoding 'ports': Invalid ip address: port OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; docker compose --file '/srv/dev-disk-by-uuid-00aa265f-40dd-4db1-821e-e32892a6ed2c/compose/ripper/ripper.yml' --env-file '/srv/dev-disk-by-uuid-00aa265f-40dd-4db1-821e-e32892a6ed2c/compose/ripper/ripper.env' --env-file '/srv/dev-disk-by-uuid-00aa265f-40dd-4db1-821e-e32892a6ed2c/compose/global.env' up -d 2>&1': 1 error(s) decoding: * error decoding 'ports': Invalid ip address: port in /usr/share/openmediavault/engined/rpc/compose.inc:676 Stack trace: #0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(620): OMVRpcServiceCompose->{closure}('/tmp/bgstatusaM...', '/tmp/bgoutputcN...') #1 /usr/share/openmediavault/engined/rpc/compose.inc(679): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure)) #2 [internal function]: OMVRpcServiceCompose->doCommand(Array, Array) #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array) #4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('doCommand', Array, Array) #5 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Compose', 'doCommand', Array, Array, 1) #6 {main}
-
Hello all,
I'm trying to install docker-ripper as I have a ton of discs to rip.
I am getting this error and here's my compose file. I'm using the compose plugin. I have no idea where to begin in working out what that error means.
Any help would be very much appreciated, as always.
Thanks,
Nick.
-
Great and thank you Soma
-
Mine is saying that a new version is available, the web updater gives me a 404 and pulling a new image using docker image pull nextcloud:latest doesn't change anything. So, do I wait for the new image as their GitHub page says the latest image is 27.0.1 at the moment?
Ta,
Nick.
-
Ah! Thank you - so obvious that I didn't see it!
-
If you get this error in Nextcloud in Administration >> Overview
Edit .../nextcloud/nginx/site-confs/default.conf
and change line
add_header X-Robots-Tag "none" always;
to
add_header X-Robots-Tag "noindex, nofollow" always;
and restart the nextcloud container.
Or delete default.conf and restart nextcloud. The new version of default.conf will be put in place.
Just seen this over in the original thread so I ventured once more into the CL and fired up nano.
Here's what I've done and I am still getting the error. Is this something to do with indentation or did I mess something else up that I can't see? I did remember to restart the container.
Thanks
Code# HTTP response headers borrowed from Nextcloud `.htaccess` add_header Referrer-Policy "no-referrer" always; add_header X-Content-Type-Options "nosniff" always; add_header X-Download-Options "noopen" always; add_header X-Frame-Options "SAMEORIGIN" always; add_header X-Permitted-Cross-Domain-Policies "none" always; add_header X-Robots-Tag "no index, nofollow" always; add_header X-XSS-Protection "1; mode=block" always;
I did try tabbing the other lines over but that results in a red mark where I've tabbed so decided that was probably some kind of warning
-
Hi,
Thank you for this - I haven't got around to doing anything yet but all my Dockers are already on the data drives.
All the best,
Nick.
-
OK, many thanks and that all seems to make sense to me.
I'll try a rebuild as soon as I get the time and I'll post back here
ifwhen I get stuck, or (if by some other-worldly miracle); I manage to do it all by myself. I'll probably continue to dd my clones but not before checking out the link you sent me - that could be easier!Thank you again,
Nick.
-
Ah, yes - I know how to install it to USB but what changes do I need to make so that it hooks up to my data drives and everything works?
I have data, Piwigo and Nextcloud on my data drives, together with all my docker stuff.
Sorry if this is vague but happy to detail anything else you may need.
Thanks,
Nick.
-
When flash media wears out, it goes "read only". This give the appearance to the OS of "write-protected". Until the flash devices controller detects the problem and sets the entire device to "read only", some individual storage locations (usually 4k in size) refuse to write. This means that file updates did not write or may have been "partially" written creating the potential for system files to be corrupted and / or out of sync.
What may have been written, may not have been fully written, etc., can only be a matter of speculation but if it's kernel or system file related, I wouldn't trust EXT4's journaling feature to completely clean it up.
Your call.OK, thank you for explaining this.
How would I go about rebuilding like you said earlier?
Thanks,
Nick.
-
Another update.
Well, the clone seems good this time. I got a list of entries regarding orphaned files of which I vowed to remember the exact message but, as usual, a short time later I have forgotten. My bad.
After those, it booted straight into OMV. I now also have access to the web GUI again without the 502 message and I am performing an update now. I'll see how it goes for a week and if all is well I will clone the system disk to avoid this happening again. I'll resolve this thread then, too.
Just for other people's information, I think that the past two disk issues (with write-protect errors) are due to me buying cheap (SanDisk branded) USB drives off of the 'Bay. I'm not doing this again. Also, I originally was not using the flash memory plugin.
Thanks, crashtest for your help,
Nick.
-
Did it occur to you that you might have cloned some corrupt files?
Did it (fix itself)? Going forward, I wouldn't be surprised if odd things happen from time to time.
_________________________________________________________
If it was me, I'd rebuild. With a known good install; I'd clone my boot drive when it's working properly, before there's a boot drive failure. You'd have known good backup.Yes, I think this may have happened (corrupt files), but on the second clone only, as I had some errors on first boot (the ones that I ran fdisk on. The first time I cloned it, this didn't happen and I still have that disk, so i will clone it again. I think the first failed disk was just a write-protect problem, but the second had other issues, it would seem.
The odd things you mentioned seem to be happening as I'm getting regular emails reporting this:
"/etc/cron.daily/openmediavault-pending_config_changes:
Segmentation fault"I'll try cloning what I believe to be the good disk and report back. I'm only doing this as I don't know how to rebuild things as you suggested.
Thanks for your help,
Nick.
-
Update: For some reason, it has fixed itself overnight. Odd.
-
Hello all,
A short while ago, my system disk failed and I fixed it in the end by cloning it using dd.
This evening, I saw the same symptoms (disk write-protected) so I cloned the disk again. There were still problems booting so I ran fdisk and agreed to all the fixes. Now when I boot up, I get an error, and on running fsck, I get this - please see the entry in red. This is one of my data disks.
Can anyone help me with this, please?
Thanks,
Nick.
EDIT: Also, forgot to say that when I try to log into the web GUI, I get a "502 - Bad Gateway" banner (in red) at the bottom of the page.
Code
Alles anzeigenroot@omvper210up:~# fdisk -l Disk /dev/sdb: 558.91 GiB, 600127266816 bytes, 1172123568 sectors Disk model: ST3600057SS Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 63973638-7AB1-443D-AB0D-3EEEB94DB675 Device Start End Sectors Size Type /dev/sdb1 2048 1172123534 1172121487 558.9G Linux filesystem Disk /dev/sda: 4.55 TiB, 5000981078016 bytes, 9767541168 sectors Disk model: ST5000LM000-2AN1 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 333B7F94-8FB1-43B5-9398-EFA310DF8122 Device Start End Sectors Size Type /dev/sda1 2048 9767541134 9767539087 4.5T Linux filesystem GPT PMBR size mismatch (30629375 != 31260671) will be corrected by write. The backup GPT table is not on the end of the device. Disk /dev/sdc: 14.91 GiB, 16005464064 bytes, 31260672 sectors Disk model: Cruzer Blade Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: D36D99AF-FC10-49D3-8BFA-A0F958C7F854 Device Start End Sectors Size Type /dev/sdc1 2048 1050623 1048576 512M EFI System /dev/sdc2 1050624 28628991 27578368 13.2G Linux filesystem /dev/sdc3 28628992 30627839 1998848 976M Linux swap
-
You need to bash into the container to run that command.
docker exec -it nextcloud bash (assuming your container is named nextcloud)
or
In Portainer, click the >_ icon next to your nextcloud container, then click connect. This will open a sort of terminal window with you bashed into the container.Either way, once you are bashed in, run the command
Just used this to run occ db:add-missing-indices and it worked a treat - thank you!
-
Many thanks and I will resolve it!
-
Hi - Did you figure out what the issue was? I'm seeing the same thing. I created a fileshare with guest access, and one for user access, but I don't (even) get a chance to log in. When I connect with my mac on the same network, the OMV server reports this:
Thank you!
Sorry, I never worked it out so and ended up installing Nextcloud using the brilliant guide on here and haven't looked back.
Good luck and if you work it out then I'd still be interested, sorry i can't help you here.
Nick.
-
Hi BernH,
Thanks for this.
Sorry, it's me being unclear and not explaining things properly. My docker containers are all on the data drive, like this:
Coderoot@omvper210up:~# docker info | grep Root Docker Root Dir: /srv/dev-disk-by-uuid-12e915d2-077d-412b-9876-a2ff94c50866/docker
As I said before I have two data drives in the machine, a 5TB and a 500GB
/srv/dev-disk-by-uuid-12e915d2-077d-412b-9876-a2ff94c50866 is the 5TB drive that my Nextcloud data is on, so that holds the docker containers for Nextcloud and Piwigo, alongside the Nextcloud data. The Piwigo data is stored on the 500GB drive.
So I think we're on the same page, or else I am totally not getting what you mean!
Cheers,
Nick.