Darksurf

Members
  • Posts

    164
  • Joined

  • Last visited

Posts posted by Darksurf

  1. 3 hours ago, tuxbass said:

    Anyone knows how does the ripper image compare to https://github.com/jlesage/docker-makemkv?

    Interesting, I'm not sure other than that docker also has a webUI? The scripts have similar lines, (they are effectively doing similar/the same thing) but that docker breaks it up into a few scripts rather than 1.  If you test it let us know how it works. My only issue with rix docker is that if I try to use a full key, it doesn't work, it only uses the beta key even though I have entered the purchased key. Not really an issue as re-installing/updating the docker fixes the betakey problem.

  2. 2 hours ago, kizer said:

    @Darksurf

     

    Did you make sure the target drive was completely empty with the exception of a single folder clear-me

     

    Yes. If you check my post above you'll see ls -al of disks5-10 look like this:

     

    Quote

    /mnt/disk5:
    total 16
    drwxrwxrwx  1 nobody users  16 Jul 10 18:35 ./
    drwxr-xr-x 18 root   root  360 Jul 10 00:12 ../
    drwxrwxrwx  1 nobody users   0 Jul 10 18:35 clear-me/
     

    /mnt/disk6:
    total 16
    drwxrwxrwx  1 nobody users  16 Jul 10 18:35 ./
    drwxr-xr-x 18 root   root  360 Jul 10 00:12 ../
    drwxrwxrwx  1 nobody users   0 Jul 10 18:35 clear-me/
     

    /mnt/disk7:
    total 16
    drwxrwxrwx  1 nobody users  16 Jul 10 18:34 ./
    drwxr-xr-x 18 root   root  360 Jul 10 00:12 ../
    drwxrwxrwx  1 nobody users   0 Jul 10 18:34 clear-me/
     

    /mnt/disk8:
    total 16
    drwxrwxrwx  1 nobody users  16 Jul 10 18:34 ./
    drwxr-xr-x 18 root   root  360 Jul 10 00:12 ../
    drwxrwxrwx  1 nobody users   0 Jul 10 18:34 clear-me/
     

    /mnt/disk9:
    total 16
    drwxrwxrwx  1 nobody users  16 Jul 10 18:33 ./
    drwxr-xr-x 18 root   root  360 Jul 10 00:12 ../
    drwxrwxrwx  1 nobody users   0 Jul 10 18:33 clear-me/

    /mnt/disk10:
    total 16
    drwxrwxrwx  1 nobody users  16 Jul 10 18:33 ./
    drwxr-xr-x 18 root   root  360 Jul 10 00:12 ../
    drwxrwxrwx  1 nobody users   0 Jul 10 18:33 clear-me/

     

    I ran unbalance on these drives 3 times to be sure, checked there were no files left, then did a full rm -rf /mnt/disk#/* on each drive I planned to wipe and then mkdir -p /mnt/disk#/clear-me on every disk I planned to wipe. I'm 100% positive the drives were empty besides the clear-me folder.

    I doubt its a problem, but these drives are all formatted BTRFS not XFS. It could also be some incompatibility with 6.10.3, not sure. I ended up just removing them from the machine and creating a new config for the array and rebuilding the parity drives.

  3. What is up with the zero drive script? It immediately gives up.

     

    *** Clear an unRAID array data drive ***  v1.4
    
    Checking all array data drives (may need to spin them up) ... 
    
    Checked 10 drives, did not find an empty drive ready and marked for clearing!
    
    To use this script, the drive must be completely empty first, no files
    or folders left on it.  Then a single folder should be created on it
    with the name 'clear-me', exactly 8 characters, 7 lowercase and 1 hyphen.
    This script is only for clearing unRAID data drives, in preparation for
    removing them from the array.  It does not add a Preclear signature.
    Script Finished Jul 10, 2022  19:21.37
    
    Full logs for this script are available at /tmp/user.scripts/tmpScripts/ZeroDisks_ShrinkArray/log.txt
    
    ^C
    root@Oceans:~# ls -al /mnt/disk*
    /mnt/disk1:
    total 16
    drwxrwxrwx   1 nobody users   84 Jul 10 04:30 ./
    drwxr-xr-x  18 root   root   360 Jul 10 00:12 ../
    drwxrwxrwx+  1 nobody users  190 Jul 10 18:28 Docker/
    drwxrwxrwx   1 nobody users   14 Jul  4 22:49 Downloads/
    drwxrwxrwx   1 nobody users   60 Jul  6 03:26 ZDRIVE/
    drwxrwxrwx   1 nobody users    0 Jul 20  2021 appdata/
    drwxrwxrwx   1 nobody users   16 Apr 16  2021 home/
    drwxrwxrwx   1 nobody users 1884 Jul  9 04:40 system/
    drwxrwxrwx   1 nobody users  138 Dec 31  2017 tftp/
    
    /mnt/disk10:
    total 16
    drwxrwxrwx  1 nobody users  16 Jul 10 18:33 ./
    drwxr-xr-x 18 root   root  360 Jul 10 00:12 ../
    drwxrwxrwx  1 nobody users   0 Jul 10 18:33 clear-me/
    
    /mnt/disk2:
    total 16
    drwxrwxrwx   1 nobody users  12 Jul 10 04:30 ./
    drwxr-xr-x  18 root   root  360 Jul 10 00:12 ../
    drwxrwxrwx+  1 nobody users 260 Jul  9 23:38 Docker/
    
    /mnt/disk3:
    total 16
    drwxrwxrwx   1 nobody users  84 Jul 10 04:30 ./
    drwxr-xr-x  18 root   root  360 Jul 10 00:12 ../
    drwxrwxrwx+  1 nobody users 188 Jul  9 23:38 Docker/
    drwxrwxrwx   1 nobody users   0 Jul  6 22:31 Downloads/
    drwxr-xr-x   1 nobody users   0 May  9 09:08 ISOs/
    drwxrwxrwx   1 nobody users  32 Jul  6 22:28 ZDRIVE/
    drwxrwxrwx   1 nobody users   0 Jul 20  2021 appdata/
    drwxrwxrwx   1 nobody users  16 Jul  6 21:50 home/
    drwxrwxrwx   1 nobody users 394 Jul  6 22:31 system/
    
    /mnt/disk4:
    total 16
    drwxrwxrwx   1 nobody users  66 Jul 10 04:30 ./
    drwxr-xr-x  18 root   root  360 Jul 10 00:12 ../
    drwxrwxrwx+  1 nobody users 170 Jul  6 12:48 Docker/
    drwxrwxrwx   1 nobody users   8 Jun  5  2021 ZDRIVE/
    drwxrwxrwx   1 nobody users   0 Jul 20  2021 appdata/
    drwxrwxrwx   1 nobody users  38 Jul  6 12:47 home/
    drwxrwxrwx   1 nobody users  96 Jul  6 12:48 system/
    drwxrwxrwx   1 nobody users   0 Dec 31  2017 tftp/
    
    /mnt/disk5:
    total 16
    drwxrwxrwx  1 nobody users  16 Jul 10 18:35 ./
    drwxr-xr-x 18 root   root  360 Jul 10 00:12 ../
    drwxrwxrwx  1 nobody users   0 Jul 10 18:35 clear-me/
    
    /mnt/disk6:
    total 16
    drwxrwxrwx  1 nobody users  16 Jul 10 18:35 ./
    drwxr-xr-x 18 root   root  360 Jul 10 00:12 ../
    drwxrwxrwx  1 nobody users   0 Jul 10 18:35 clear-me/
    
    /mnt/disk7:
    total 16
    drwxrwxrwx  1 nobody users  16 Jul 10 18:34 ./
    drwxr-xr-x 18 root   root  360 Jul 10 00:12 ../
    drwxrwxrwx  1 nobody users   0 Jul 10 18:34 clear-me/
    
    /mnt/disk8:
    total 16
    drwxrwxrwx  1 nobody users  16 Jul 10 18:34 ./
    drwxr-xr-x 18 root   root  360 Jul 10 00:12 ../
    drwxrwxrwx  1 nobody users   0 Jul 10 18:34 clear-me/
    
    /mnt/disk9:
    total 16
    drwxrwxrwx  1 nobody users  16 Jul 10 18:33 ./
    drwxr-xr-x 18 root   root  360 Jul 10 00:12 ../
    drwxrwxrwx  1 nobody users   0 Jul 10 18:33 clear-me/
    
    /mnt/disks:
    total 0
    drwxrwxrwt  2 nobody users  40 Jul 10 00:11 ./
    drwxr-xr-x 18 root   root  360 Jul 10 00:12 ../

     

  4. On 7/7/2022 at 10:18 AM, Stan464 said:

    Backblaze does have a Personal one with an Docker Container to work around the "Restrictions" which does look pretty good. I used an alternative method which wasnt ideal and moved away from Backblaze.

    But i may revisit due to the Docker Container now being avail.

    Lemme know the name of that docker with a link. This could be my solution!

  5. I'm running a Ryzen Threadripper 3970X with 128G UECC memory in an ASROCK Creator TRX40 board, latest Beta BIOS, no stability issues. This could be various issues.

    1. Are you updated to the latest BIOS version?

    2. do you have fTPM disabled or enabled? If enabled, you'll want the latest BIOS update that fixes an fTPM stuttering issue. https://www.amd.com/en/support/kb/faq/pa-410

    3. What speed are you running your Unbuffered ECC Memory at? Don't expect greater than 2933mhz for ECC memory on Ryzen 3XXX or lower. Some only work at 2666mhz.

    4. If your Memory speeds aren't the problem, check your memory timings. There can be multiple jedec settings for timings or none requiring you to enter them manually to spec.

    5. In the BIOS have you disabled all power saving nonsense such as suspend to RAM, aggressive ASPM, ALPM, etc. (I've found aggressive power management implementation in my old supermicro server board was a problem for my HDDs)

    6. If you've done all the above, is your motherboard auto overclocking the CPU or RAM? disable auto-overclocking.

     

     

    As for specifics, I need to know the exact hardware in the build including the memory being used and what clock speeds and timings its rated for and what you have configured.

    Your logs here show normal gskill memory (non-ecc) and its running at the wrong speed and voltage (F4-3600C16-8GVKC running at 2133mhz and 1.2V). I also hope you're using UDIMM and not RDIMM ECC as RDIMM shouldn't work at all.

    Getting SMBIOS data from sysfs.
    SMBIOS 3.3.0 present.
    
    Handle 0x0018, DMI type 17, 92 bytes
    Memory Device
        Array Handle: 0x0010
        Error Information Handle: 0x0017
        Total Width: Unknown
        Data Width: Unknown
        Size: No Module Installed
        Form Factor: Unknown
        Set: None
        Locator: DIMM 0
        Bank Locator: P0 CHANNEL A
        Type: Unknown
        Type Detail: Unknown
        Speed: Unknown
        Manufacturer: Unknown
        Serial Number: Unknown
        Asset Tag: Not Specified
        Part Number: Unknown
        Rank: Unknown
        Configured Memory Speed: Unknown
        Minimum Voltage: Unknown
        Maximum Voltage: Unknown
        Configured Voltage: Unknown
        Memory Technology: Unknown
        Memory Operating Mode Capability: Unknown
        Firmware Version: Unknown
        Module Manufacturer ID: Unknown
        Module Product ID: Unknown
        Memory Subsystem Controller Manufacturer ID: Unknown
        Memory Subsystem Controller Product ID: Unknown
        Non-Volatile Size: None
        Volatile Size: None
        Cache Size: None
        Logical Size: None
    
    Handle 0x001A, DMI type 17, 92 bytes
    Memory Device
        Array Handle: 0x0010
        Error Information Handle: 0x0019
        Total Width: 64 bits
        Data Width: 64 bits
        Size: 8 GB
        Form Factor: DIMM
        Set: None
        Locator: DIMM 1
        Bank Locator: P0 CHANNEL A
        Type: DDR4
        Type Detail: Synchronous Unbuffered (Unregistered)
        Speed: 2133 MT/s
        Manufacturer: Unknown
        Serial Number: 00000000
        Asset Tag: Not Specified
        Part Number: F4-3600C16-8GVKC
        Rank: 1
        Configured Memory Speed: 2133 MT/s
        Minimum Voltage: 1.2 V
        Maximum Voltage: 1.2 V
        Configured Voltage: 1.2 V
        Memory Technology: DRAM
        Memory Operating Mode Capability: Volatile memory
        Firmware Version: Unknown
        Module Manufacturer ID: Bank 5, Hex 0xCD
        Module Product ID: Unknown
        Memory Subsystem Controller Manufacturer ID: Unknown
        Memory Subsystem Controller Product ID: Unknown
        Non-Volatile Size: None
        Volatile Size: 8 GB
        Cache Size: None
        Logical Size: None
    
    Handle 0x001D, DMI type 17, 92 bytes
    Memory Device
        Array Handle: 0x0010
        Error Information Handle: 0x001C
        Total Width: Unknown
        Data Width: Unknown
        Size: No Module Installed
        Form Factor: Unknown
        Set: None
        Locator: DIMM 0
        Bank Locator: P0 CHANNEL B
        Type: Unknown
        Type Detail: Unknown
        Speed: Unknown
        Manufacturer: Unknown
        Serial Number: Unknown
        Asset Tag: Not Specified
        Part Number: Unknown
        Rank: Unknown
        Configured Memory Speed: Unknown
        Minimum Voltage: Unknown
        Maximum Voltage: Unknown
        Configured Voltage: Unknown
        Memory Technology: Unknown
        Memory Operating Mode Capability: Unknown
        Firmware Version: Unknown
        Module Manufacturer ID: Unknown
        Module Product ID: Unknown
        Memory Subsystem Controller Manufacturer ID: Unknown
        Memory Subsystem Controller Product ID: Unknown
        Non-Volatile Size: None
        Volatile Size: None
        Cache Size: None
        Logical Size: None
    
    Handle 0x001F, DMI type 17, 92 bytes
    Memory Device
        Array Handle: 0x0010
        Error Information Handle: 0x001E
        Total Width: 64 bits
        Data Width: 64 bits
        Size: 8 GB
        Form Factor: DIMM
        Set: None
        Locator: DIMM 1
        Bank Locator: P0 CHANNEL B
        Type: DDR4
        Type Detail: Synchronous Unbuffered (Unregistered)
        Speed: 2133 MT/s
        Manufacturer: Unknown
        Serial Number: 00000000
        Asset Tag: Not Specified
        Part Number: F4-3600C16-8GVKC
        Rank: 1
        Configured Memory Speed: 2133 MT/s
        Minimum Voltage: 1.2 V
        Maximum Voltage: 1.2 V
        Configured Voltage: 1.2 V
        Memory Technology: DRAM
        Memory Operating Mode Capability: Volatile memory
        Firmware Version: Unknown
        Module Manufacturer ID: Bank 5, Hex 0xCD
        Module Product ID: Unknown
        Memory Subsystem Controller Manufacturer ID: Unknown
        Memory Subsystem Controller Product ID: Unknown
        Non-Volatile Size: None
        Volatile Size: 8 GB
        Cache Size: None
        Logical Size: None

     

  6. 19 hours ago, Vr2Io said:

    I divide my data in two group, one is frequently change and other is rather static.

     

    Each assign 8 bay in total 16 bay in same enclosure, so 8 bay in normal array parity and 8 bay in raid0 pool. That's all live data.

     

    The aim was I can copy / regen data in quick way by raid0 to raid0 most time. And I can easy free up 20 bays for temporary use.

    Thats a good point! I never really considered RAID0 as a option, but if you think about it, I have an array with dual parity. The likelihood that I'll have an issue there AND with a Backup RAID0 Pool isn't high, and only 1 week worth of revert/recovery if the RAID0 fails isn't that big of a deal. This isn't mission critical business data. Its just my personal tinker toys, Plex server, dockers for wikis, other webservices, etc, and a couple VMs that are actually self configured/deployable via yaml scripts using yip to act as a kubernetes cluster for Linux package building.

     

    My cache pool is a RAID0 and the mover runs daily with zero issues. I can see this being a valid option as well for personal use.

  7. 7 hours ago, Stan464 said:

    I use Duplicacy with Storage Backend. as an example. Backblaze B2.

    Wow, I've not looked at backblaze pricing, but $70/year for unlimited personal seems pretty amazing and $5/TB/Month for Backblaze B2 is pretty good too when looking from a business perspective! Thats definitely one option considering I'd have to buy multiple (5-6) drives at $250 each minimum to have a local backup and I'd most likely go with the personal backup option if that were allowed.

     

    Thanks for the input!

    • Like 1
  8. So its been a dream of mine to get an LTO Tape Drive one day and run backups. In reality, my wife will never let me spend that kind of money for a drive. HDDs on the other hand are far cheaper for the same amount of storage (~30T).

     

    So I've been upgrading my cute Original WD Red 3T drives to Seagate EXOS 3x14T and 3x8T drives. But newer larger drives don't exactly have the same level of reliability in my experience in Datacenters. So I'd like to make use of the extra drive bays I'm freeing up. I have 12 bays. I plan to use 6 for my array with dual parity. I'd like to use the other 4-6 bays for a weekly backup.

     

    Evidently you cannot create 2 arrays in Unraid so my 2nd Array for weekly backup idea isn't going to work. What do you recommend here? Should I just create a "pool" for backups with no parity? should I risk BTRFS RAID6 pool as a backup solution, or just go the more expensive route to BTRFS RAID10 pool? Something else?

     

    The server is on a 1500Watt UPS. Risk of unclean shutdown is low. writes would only be weekly and incremental. No need to completely rewrite the entire backup.

  9. On 5/23/2022 at 3:18 AM, ThatDude said:

    Hey, did you ever get anywhere with installing virt-sparsify ?

     

    Unfortunately, no. The Dependency Hell threw a wrench in it. I've not tried since. Dealing with such deps on a static system is risky. This kind of power is really needed on the hypervisor side. You would also have to script/add/install all the deps and tool itself on every install due to the static nature of unraid (which is fair).  That being said, if all the deps and the tool were installed from the beginning, this would be far less of a problem.

  10. 15 hours ago, Squid said:

    I have linux VMs. They are actually build nodes used to build packages for a linux distribution.  So my VMs accept jobs to compile and packages inside containers, upload said packages, then delete everything and start another job. I'm not sure if your suggestion works in this scenario does it?

  11. 32 minutes ago, pk1057 said:

    I digged around,

    made a fork of the project and switched from ripit to abcde wich is more versatile and mature then ripit.

     

    With abcde there are no encoding problems !

    You might be able to perform a pull request to update the main project is you have through testing and proof of stability.

  12. Is anyone else having issues with memory ballooning not working in VMs? I check my linux VMs and they have virtio_ballooning loaded, but their memory won't increase past initial size.

     

    I'm using an ASROCK Creator TRX40 w/ Ryzen Threadripper 3970X 64G DDR4.  I'm using the rule initial memory is 1core=1G and Max is 1core=2G. I'm doing this on 3 VMs 8core, 8core, and 4core.  None of which see their memory balloon while  compiling software and they end up crashing with OOM errors.

     

     

    oceans-diagnostics-20210528-1427.zip

    • Like 1
  13. That's awesome! It would be nice if we could get a lifespan meter somewhere in the open (it seems my method may be inaccurate and yours would be better). I want to make sure my server uptime doesn't take a bad turn when I need to order an SSD and it takes a week to get here. I'd like some pre-emptive warning/monitoring so I can plan accordingly rather than have items live on a shelf for years.

     

    Thanks for the correction! I'm learning something new everyday.

  14. I'm curious if it would be possible to store a MAX TBW for SSDs in the warranty information in the Identity drive info, then have a running comparison of what smartctl shows for nvme/ssds to show how close you are to reaching that maximum so someone would know to prepare for a replacement. You'll see after doing a smartctl -a /dev/nvme0n1 I have a "Data Units Written" of 9.67 TB. This unit has a MAX TBW of 1800. Now, this isn't my cache drive, this is my desktop. But if you're using an SSD as a cache drive, I'm sure you could see how the SSD would quickly deteriorate and fail.  My cache SSD on my server is currently at 169TBW with a maximum of  530TBW before failure. Having this SSD lifespan viewable from the dashboard would be very helpful. My SSD in my server is only 1year old, but its used heavily for an open source project.

     

     

    jcfrosty@Zero ~ $ sudo smartctl -a /dev/nvme0n1
    Password: 
    smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.11.0-sabayon] (local build)
    Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
    
    === START OF INFORMATION SECTION ===
    Model Number:                       Sabrent Rocket 4.0 1TB
    Serial Number:                      03F10797054463199045
    Firmware Version:                   EGFM11.1
    PCI Vendor/Subsystem ID:            0x1987
    IEEE OUI Identifier:                0x6479a7
    Total NVM Capacity:                 1,000,204,886,016 [1.00 TB]
    Unallocated NVM Capacity:           0
    Controller ID:                      1
    Number of Namespaces:               1
    Namespace 1 Size/Capacity:          1,000,204,886,016 [1.00 TB]
    Namespace 1 Formatted LBA Size:     512
    Namespace 1 IEEE EUI-64:            6479a7 2220653435
    Local Time is:                      Sat Apr 17 11:32:39 2021 CDT
    Firmware Updates (0x12):            1 Slot, no Reset required
    Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
    Optional NVM Commands (0x005d):     Comp DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
    Maximum Data Transfer Size:         512 Pages
    Warning  Comp. Temp. Threshold:     70 Celsius
    Critical Comp. Temp. Threshold:     90 Celsius
    
    Supported Power States
    St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
     0 +    10.73W       -        -    0  0  0  0        0       0
     1 +     7.69W       -        -    1  1  1  1        0       0
     2 +     6.18W       -        -    2  2  2  2        0       0
     3 -   0.0490W       -        -    3  3  3  3     2000    2000
     4 -   0.0018W       -        -    4  4  4  4    25000   25000
    
    Supported LBA Sizes (NSID 0x1)
    Id Fmt  Data  Metadt  Rel_Perf
     0 +     512       0         2
     1 -    4096       0         1
    
    === START OF SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED
    
    SMART/Health Information (NVMe Log 0x02)
    Critical Warning:                   0x00
    Temperature:                        45 Celsius
    Available Spare:                    100%
    Available Spare Threshold:          5%
    Percentage Used:                    1%
    Data Units Read:                    7,506,169 [3.84 TB]
    Data Units Written:                 18,893,007 [9.67 TB]
    Host Read Commands:                 56,347,067
    Host Write Commands:                289,751,028
    Controller Busy Time:               583
    Power Cycles:                       118
    Power On Hours:                     14,438
    Unsafe Shutdowns:                   55
    Media and Data Integrity Errors:    0
    Error Information Log Entries:      271
    Warning  Comp. Temperature Time:    0
    Critical Comp. Temperature Time:    0
    
    Error Information (NVMe Log 0x01, max 63 entries)
    No Errors Logged
    

     

     

    Screenshot_20210417_113435.png

    • Like 1
  15. I really could use this. I use my personal server for an OpenSource Linux project so giving my team members access would be really handy.

    I'd like to see

    1. Multiple users enabled for WebUI (simple checkbox within the user profile would be nice)
    2. Different levels of access. (Example: Restart VMs, VM Access, but not Creation/Deletion or root host shell access)
    3. Log Users login and change actions (VM/docker reboot, deletion, creation, etc)

    Just some SMB features could be handy.

  16. 9 hours ago, JTok said:

    Whoops! typed the wrong filename. I think it should work now.

    I can't seem to update the plugin even though it tells me there's an update.

    I tried removing the plugin to reinstall it, and now it still fails so it never installs.
     

    plugin: updating: vmbackup.plg
    Removing package: xmlstarlet-1.6.1-x86_64-1_slonly
    Removing files:
    Removing package: pigz-2.3-x86_64-2_slonly
    Removing files:
    
    +==============================================================================
    | Installing new package /boot/config/plugins/vmbackup/packages/xmlstarlet-1.6.1-x86_64-1_slonly.txz
    +==============================================================================
    
    Verifying package xmlstarlet-1.6.1-x86_64-1_slonly.txz.
    Installing package xmlstarlet-1.6.1-x86_64-1_slonly.txz:
    PACKAGE DESCRIPTION:
    # xmlstarlet (command line xml tool)
    #
    # XMLStarlet is a command line XML toolkit that can be used to
    # transform, query, validate, and edit XML documents and files using
    # a simple set of shell commands, which work similarly to 'grep',
    # 'sed', 'awk', 'tr', 'diff', or 'patch' on plain text files.
    #
    # Homepage https://sourceforge.net/projects/xmlstar/
    #
    Executing install script for xmlstarlet-1.6.1-x86_64-1_slonly.txz.
    Package xmlstarlet-1.6.1-x86_64-1_slonly.txz installed.
    
    +==============================================================================
    | Installing new package /boot/config/plugins/vmbackup/packages/pigz-2.3-x86_64-2_slonly.txz
    +==============================================================================
    
    Verifying package pigz-2.3-x86_64-2_slonly.txz.
    Installing package pigz-2.3-x86_64-2_slonly.txz:
    PACKAGE DESCRIPTION:
    # pigz (Parallel gzip)
    #
    # pigz, which stands for parallel implementation of gzip, is a fully
    # functional replacement for gzip that exploits multiple processors and
    # multiple cores to the hilt when compressing data. pigz was written by
    # Mark Adler, and uses the zlib and pthread libraries.
    #
    # Home page: http://www.zlib.net/pigz/
    #
    Package pigz-2.3-x86_64-2_slonly.txz installed.
    
    +==============================================================================
    | Skipping package vmbackup-v0.2.2-2021.02.03 (already installed)
    +==============================================================================
    
    plugin: run failed: /bin/bash retval: 1

     

     

    After upgrade to stable 6.9.0 from RC1, I tried to install the plugin again. Still Fails:


     

    plugin: installing: https://raw.githubusercontent.com/jtok/unraid.vmbackup/master/vmbackup.plg
    plugin: downloading https://raw.githubusercontent.com/jtok/unraid.vmbackup/master/vmbackup.plg
    plugin: downloading: https://raw.githubusercontent.com/jtok/unraid.vmbackup/master/vmbackup.plg ... done
    No such package: xmlstarlet*. Can't remove.
    No such package: pigz*. Can't remove.
    
    +==============================================================================
    | Installing new package /boot/config/plugins/vmbackup/packages/xmlstarlet-1.6.1-x86_64-1_slonly.txz
    +==============================================================================
    
    Verifying package xmlstarlet-1.6.1-x86_64-1_slonly.txz.
    Installing package xmlstarlet-1.6.1-x86_64-1_slonly.txz:
    PACKAGE DESCRIPTION:
    # xmlstarlet (command line xml tool)
    #
    # XMLStarlet is a command line XML toolkit that can be used to
    # transform, query, validate, and edit XML documents and files using
    # a simple set of shell commands, which work similarly to 'grep',
    # 'sed', 'awk', 'tr', 'diff', or 'patch' on plain text files.
    #
    # Homepage https://sourceforge.net/projects/xmlstar/
    #
    Executing install script for xmlstarlet-1.6.1-x86_64-1_slonly.txz.
    Package xmlstarlet-1.6.1-x86_64-1_slonly.txz installed.
    
    +==============================================================================
    | Installing new package /boot/config/plugins/vmbackup/packages/pigz-2.3-x86_64-2_slonly.txz
    +==============================================================================
    
    Verifying package pigz-2.3-x86_64-2_slonly.txz.
    Installing package pigz-2.3-x86_64-2_slonly.txz:
    PACKAGE DESCRIPTION:
    # pigz (Parallel gzip)
    #
    # pigz, which stands for parallel implementation of gzip, is a fully
    # functional replacement for gzip that exploits multiple processors and
    # multiple cores to the hilt when compressing data. pigz was written by
    # Mark Adler, and uses the zlib and pthread libraries.
    #
    # Home page: http://www.zlib.net/pigz/
    #
    Package pigz-2.3-x86_64-2_slonly.txz installed.
    
    +==============================================================================
    | Installing new package /boot/config/plugins/vmbackup/vmbackup-v0.2.2-2021.02.03.txz
    +==============================================================================
    
    Verifying package vmbackup-v0.2.2-2021.02.03.txz.
    Installing package vmbackup-v0.2.2-2021.02.03.txz:
    PACKAGE DESCRIPTION:
    Package vmbackup-v0.2.2-2021.02.03.txz installed.
    plugin: run failed: /bin/bash retval: 126

     

  17. On 1/10/2021 at 5:29 AM, rix said:

    Latest image includes ccextractor v.0.88

    Let me know if something needs to be changed.

     

    jlesage's image includes a line in the settings.conf that guides to the binary.

    https://github.com/jlesage/docker-makemkv/blob/master/rootfs/defaults/settings.conf

     

    app_ccextractor = "/usr/bin/ccextractor"

     

    Please try without changing settings.conf first.

     

    The ccextractor thing is still an issue as the location settings do not match. ccextractor wasn't installed in /usr/bin/ccextractor. Its been installed in /usr/local/bin/ccextractor .  So the errors still exist. I've not added that settings.conf.
     

    MSG:5015,131072,4,"Saving 1 titles into directory file:///out/DVD/ADDAMSFAMILY using profile 'Default' from file '/config/default.mmcp.xml'","Saving %1 titles into directory %2 using profile '%3' from file '%4'","1","file:///out/DVD/ADDAMSFAMILY","Default","/config/default.mmcp.xml"
    MSG:4040,0,1,"Unable to execute external program 'ccextractor' as its path is not set in preferences","Unable to execute external program '%1' as its path is not set in preferences","ccextractor"
    MSG:4040,0,1,"Unable to execute external program 'ccextractor' as its path is not set in preferences","Unable to execute external program '%1' as its path is not set in preferences","ccextractor"
    MSG:4040,0,1,"Unable to execute external program 'ccextractor' as its path is not set in preferences","Unable to execute external program '%1' as its path is not set in preferences","ccextractor"

     

    Side note unrelated to ccextractor:

    I've been noticing sometimes the docker will lockup (its rare overall, but I have it running 24/7 whether its in use or not, I mean why not?). Well sometimes after ripping a few discs, the docker will just peg once CPU core and has a hard time progressing. I couldn't really figure out what was going on. I just know that attempting to kill/stop the docker would result in the docker just being hard locked and refusing to stop. Showing the log from WebUI fails and you cannot access the terminal either. Unplugging the optical drive would allow the docker to stop (its an external USB3 bluray drive).  After plugging the drive back in and starting the docker again I noticed that sometimes the output files in /out are not being placed there as the root folder but in another folder called "," and inside that folder is another folder that is the drive name "DRV:0,2,999,12,"BD-RE ASUS BW-12D1S-U E401"" and in that folder is where the output is being placed during the RIP. I couldn't figure this out for the longest time. I'd have to reboot the server to fix it and force it to rip in the correct location. 

    Well I think I finally discovered it today. The issue occurred again last night, I started doing some investigating of the script (no issues found), started looking for any issues and eventually jumped into the host servers /dev folder only to find /dev/sr0 was not a block device but a FOLDER! I couldn't think of why this would happen so I stopped the docker, removed the drive, deleted that folder, connected the drive back and now /dev/sr0 is a block device again! This explains what's probably happening when I reboot the machine as the block device gets recreated then. I started a new rip and surprise, its ripping like it's supposed to in the correct folder now!  OK, time to investigate the docker. Now I noticed something interesting. Its passing optical drive configuration AS A PATH! What is should be doing is passing /dev/sr0 as a DEVICE. would it be possible to tweak the docker to do that? Or is it possibly my old config is being kept in place during updates? Just figured I'd pass on this info.  Thanks for everything you do! this Docker is GOLD.

     

    Screenshot_20210112_092510.thumb.png.df748535a633335925dbf274bf881120.png

    Screenshot_20210112_092559.png

     

    Here is my current config and it seems to be working without extra parameters or anything:

     

    [2415694.831852] usb 8-4: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd
    [2415694.845100] usb-storage 8-4:1.0: USB Mass Storage device detected
    [2415694.845260] usb-storage 8-4:1.0: Quirks match for vid 174c pid 55aa: 400000
    [2415694.845331] scsi host1: usb-storage 8-4:1.0
    [2415695.868323] scsi 1:0:0:0: CD-ROM            ASUS     BW-12D1S-U       E401 PQ: 0 ANSI: 0
    [2415695.876630] sr 1:0:0:0: Power-on or device reset occurred
    [2415695.899356] sr 1:0:0:0: [sr0] scsi3-mmc drive: 125x/125x writer dvd-ram cd/rw xa/form2 cdda tray
    [2415695.905593] sr 1:0:0:0: Attached scsi CD-ROM sr0
    [2415695.905667] sr 1:0:0:0: Attached scsi generic sg1 type 5

     

    Screenshot_20210112_122257.thumb.png.6ffce69cd119bb947a31c2bef6723703.png

  18. On 1/10/2021 at 5:29 AM, rix said:

    Latest image includes ccextractor v.0.88

    Let me know if something needs to be changed.

     

    jlesage's image includes a line in the settings.conf that guides to the binary.

    https://github.com/jlesage/docker-makemkv/blob/master/rootfs/defaults/settings.conf

     

    app_ccextractor = "/usr/bin/ccextractor"

     

    Please try without changing settings.conf first.

    Thanks, this was a blueray, but I've seen it with DVDs as well. I'll give it a test and see how it goes!