Posts by ajaja
-
-
How could this be made more intuitive?
Is there a way to skip the need to touching the label? As it could be an assumption, being the only reason for being at that page.
-
"select" was a typo I corrected to "device"
-
It did, but I think so only because I did something different while selecting. I touched the label "Device *" then it turned red and said, "This field is required." and the dropdown menu worked. Touching the label "Device *" is not intuitive.
Thanks
-
Hmmmm
I now get this at Storage | Disks when I Wipe it.
Code
Display MoreWarning: Partition table header claims that the size of partition table entries is 0 bytes, but this program supports only 128-byte entries. Adjusting accordingly, but partition table may be garbage. Warning: Partition table header claims that the size of partition table entries is 0 bytes, but this program supports only 128-byte entries. Adjusting accordingly, but partition table may be garbage. Creating new GPT entries in memory. GPT data structures destroyed! You may now partition the disk using fdisk or other utilities. 1+0 records in 1+0 records out 4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.0526162 s, 79.7 MB/s 8192+0 records in 8192+0 records out 4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.440035 s, 9.5 MB/s
-
I am trying to add a brand-new 16TB disk. I see it at Storage | Disks and can Wipe it. When I try to Create the volume at Storage | File Systems it is not available in the dropdown selector.
How do I add this new drive?
-
openmediavault-mergerfs - done
So I am in Wisconsin for a while and am back at it. I did a fresh install of 6.0.5-3 (Shaitan) on my server. I want to merge the file systems of a few of my drives as I've done before. I just don't understand how to do it with the current plug-in interface.
Do I place something like this in 'Paths' field:
/dev/disk/by-uuid/ffd38b91-901e-47e5-a388-e58632a7b2c9-part1/dev/disk/by-uuid/f41eded5-63d6-4b9c-8bfc-2a909e6331ec-part1
-
So I keep getting this similar error with plug-in installs/removals and system updates.
What can I do to get my system back and running?Code
Display MoreReading package lists... Building dependency tree... Reading state information... Calculating upgrade... The following packages have been kept back: pve-headers-5.4 The following packages will be upgraded: openmediavault Preconfiguring packages ... 1 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. 1 not fully installed or removed. Need to get 0 B/2348 kB of archives. After this operation, 24.6 kB of additional disk space will be used. (Reading database ... (Reading database ... 5% (Reading database ... (Reading database ... 100% (Reading database ... 99557 files and directories currently installed.) Preparing to unpack .../openmediavault_6.0.5-3_all.deb ... Unpacking openmediavault (6.0.5-3) over (6.0.5-1) ... Setting up openmediavault (6.0.5-3) ... Creating configuration database ... Migrating configuration database ... Setting up Salt environment ... [ERROR ] Command '/usr/bin/patch' failed with return code: 1 [ERROR ] stdout: patching file /tmp/__salt.tmp.kwr1nu00 (read from /lib/python3/dist-packages/salt/modules/network.py) Reversed (or previously applied) patch detected! Skipping patch. 1 out of 1 hunk ignored -- saving rejects to file /tmp/__salt.tmp.lre3lr0f [ERROR ] retcode: 1 [ERROR ] Command '/usr/bin/patch' failed with return code: 1 [ERROR ] stdout: patching file /tmp/__salt.tmp.rf8atsee (read from /lib/python3/dist-packages/salt/fileserver/roots.py) Reversed (or previously applied) patch detected! Skipping patch. 1 out of 1 hunk ignored -- saving rejects to file /tmp/__salt.tmp.7_1_3349 [ERROR ] retcode: 1 Processing system modifications ... Processing triggers for rsyslog (8.2102.0-2) ... Processing triggers for openmediavault (6.0.5-3) ... Restarting engine daemon ... Updating workbench configuration files ... Setting up openmediavault-zfs (6.0.2) ... modprobe: FATAL: Module zfs not found in directory /lib/modules/5.14.0-0.bpo.2-amd64 dpkg: error processing package openmediavault-zfs (--configure): installed openmediavault-zfs package post-installation script subprocess returned error exit status 1 Processing triggers for openmediavault (6.0.5-3) ... Restarting engine daemon ... Errors were encountered while processing: openmediavault-zfs
Thanks
-
looks like zfs is not installed on your system.
Ugh. I just uninstalled ZFS plugin, and reinstalled the plugin:
Code
Display MoreCreated symlink /etc/systemd/system/multi-user.target.wants/zfs.target → /lib/systemd/system/zfs.target. zfs-import-scan.service is a disabled or a static unit, not starting it. Setting up zfs-zed (2.0.6-pve1~bpo10+1) ... Created symlink /etc/systemd/system/zed.service → /lib/systemd/system/zfs-zed.service. Created symlink /etc/systemd/system/zfs.target.wants/zfs-zed.service → /lib/systemd/system/zfs-zed.service. Setting up openmediavault-zfs (6.0) ... modprobe: FATAL: Module zfs not found in directory /lib/modules/5.14.0-0.bpo.2-amd64 dpkg: error processing package openmediavault-zfs (--configure): installed openmediavault-zfs package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.31-13+deb11u2) ... Processing triggers for openmediavault (6.0.3-1) ... Restarting engine daemon ... Errors were encountered while processing: openmediavault-zfs
-
UUIDs
Code
Display Moreblkid /dev/sdf1: LABEL="WDC10TB2YHZ3Z6D" UUID="38fad4a7-7d34-4e7d-b5a3-32e0588deead" UUID_SUB="c8365bff-6b44-45ef-ae79-30a8a7bd6207" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="b465b5fe-1baf-408d-a3d5-6e16a5a84697" /dev/sdh1: UUID="45EF-1513" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="d45d5be0-3110-450f-a589-03c2f96f85a8" /dev/sdh2: UUID="843ef7cf-f9fa-485f-bbd9-ca60e7b82742" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="9e947ff4-5920-470f-8c24-2aeafd37fb9d" /dev/sdh3: UUID="6a4f43ee-b458-4084-96c8-9cb298c33826" TYPE="swap" PARTUUID="dadda76f-ed21-4a64-a539-90f79de4626f" /dev/sdd1: LABEL="WD10TBA02YJD8UYD" UUID="ffd38b91-901e-47e5-a388-e58632a7b2c9" UUID_SUB="35e8fe5a-1ac0-4a98-b81a-8831308b1049" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="c1e6273c-c847-4171-afa3-7dc7c968041a" /dev/sdg1: LABEL="WD60TBB0V9GKYAUL" UUID="a60318d3-e959-4665-a9ab-9a78d50992d0" UUID_SUB="66ec42fb-b001-43cc-abbb-9e3faef82ec1" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="8ff480db-1c24-47ff-aab1-0f9582040b9a" /dev/sda1: LABEL="WD12TBA09KG52WDL" UUID="c7a7fd91-0550-4531-ad7e-26d7b937916c" UUID_SUB="59b7412f-4f41-4edf-bd0d-65d40a62d7b2" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="ad4cc314-f459-46d9-8e24-352eb9ffef85" /dev/sde1: LABEL="ST8TB188ZR10P2GE" UUID="f41eded5-63d6-4b9c-8bfc-2a909e6331ec" UUID_SUB="fa9a51a7-ea69-4c32-8d6b-982396390e9c" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="e9f3ae7e-df0e-4e70-9f9a-bb0870dc8fb7" /dev/sdb1: LABEL="TOBA8TB6K5LJF96F" UUID="107e5a85-e2fc-4b46-b434-043c63df8bc5" UUID_SUB="4469de0f-d79d-406f-8eb5-8afdc828b08d" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="c13b8c53-3d41-4855-8444-4e422fc8327c" /dev/sdc1: LABEL="TOBA8TB5K5MSF96F" UUID="e4d1a650-565f-43e7-914e-ee7c49134797" UUID_SUB="9a01b2c2-37ab-4db6-9060-f10d266d1c9b" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="baa3c754-c0aa-492e-b69c-8240733f691b" /dev/sdi1: LABEL="Zenith" UUID="9323196876188285012" UUID_SUB="16174935876269510914" BLOCK_SIZE="512" TYPE="zfs_member" PARTLABEL="zfs-7916fe0d87611ebc" PARTUUID="e6cb7e6f-a2de-104b-bc7d-dbb30405bc03" /dev/sdj1: LABEL="Zenith" UUID="9323196876188285012" UUID_SUB="17783954537649735424" BLOCK_SIZE="512" TYPE="zfs_member" PARTLABEL="zfs-2f36a35be2ea3598" PARTUUID="0e0bbbf7-ecac-3540-a525-47629e8795fb" /dev/sdk1: LABEL="Zenith" UUID="9323196876188285012" UUID_SUB="12752816909777006034" BLOCK_SIZE="512" TYPE="zfs_member" PARTLABEL="zfs-ae698de9fa4eb248" PARTUUID="9644d7db-0aa0-5f4f-9871-f81dccd6263f" /dev/sdl1: LABEL="Zenith" UUID="9323196876188285012" UUID_SUB="17043407025018494781" BLOCK_SIZE="512" TYPE="zfs_member" PARTLABEL="zfs-1dd329b760afbadb" PARTUUID="35fe100f-76d3-6342-8866-a54c9b6e00f1" /dev/sdi9: PARTUUID="aaf39754-5aa6-124b-9376-411cd230bbe1" /dev/sdj9: PARTUUID="c17a91a3-29a5-de4d-8999-8f2c02c7b946" /dev/sdk9: PARTUUID="1f5fb934-2af8-0e4c-87ff-2f3fb2dee8e2" /dev/sdl9: PARTUUID="0f46e5ed-ce0a-e74d-95ed-c9ff7ee4d73a"
-
…post your fstab file.
Code
Display Morecat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sdj2 during installation UUID=843ef7cf-f9fa-485f-bbd9-ca60e7b82742 / ext4 noatime,nodiratime,errors=remount-ro 0 1 # /boot/efi was on /dev/sdj1 during installation UUID=45EF-1513 /boot/efi vfat umask=0077 0 1 # swap was on /dev/sdj3 during installation #UUID=6a4f43ee-b458-4084-96c8-9cb298c33826 none swap sw 0 0 # >>> [openmediavault] /dev/disk/by-id/ata-WDC_WD120EMFZ-11A6JA0_9KG52WDL-part1 /srv/dev-disk-by-id-ata-WDC_WD120EMFZ-11A6JA0_9KG52WDL-part1 btrfs defaults,nofail 0 2 /dev/disk/by-id/ata-WDC_WD100EMAZ-00WJTA0_2YJD8UYD-part1 /srv/dev-disk-by-id-ata-WDC_WD100EMAZ-00WJTA0_2YJD8UYD-part1 btrfs defaults,nofail 0 2 /dev/disk/by-id/ata-ST8000DM004-2CX188_ZR10P2GE-part1 /srv/dev-disk-by-id-ata-ST8000DM004-2CX188_ZR10P2GE-part1 btrfs defaults,nofai0 2 /dev/disk/by-id/ata-TOSHIBA_MG05ACA800E_97B6K5LJF96F-part1 /srv/dev-disk-by-id-ata-TOSHIBA_MG05ACA800E_97B6K5LJF96F-part1 btrfs defaults,nofail 0 2 /dev/disk/by-id/ata-TOSHIBA_MG05ACA800E_97A5K5MSF96F-part1 /srv/dev-disk-by-id-ata-TOSHIBA_MG05ACA800E_97A5K5MSF96F-part1 btrfs defaults,nofail 0 2 /dev/disk/by-id/ata-WDC_WD100EMAZ-00WJTA0_2YHZ3Z6D-part1 /srv/dev-disk-by-id-ata-WDC_WD100EMAZ-00WJTA0_2YHZ3Z6D-part1 btrfs defaults,nofail 0 2 /srv/dev-disk-by-id-ata-TOSHIBA_MG05ACA800E_97A5K5MSF96F-part1:/srv/dev-disk-by-id-ata-ST8000DM004-2CX188_ZR10P2GE-part1:/srv/dev-disk-by-id-ata-TOSHIBA_MG05ACA800E_97B6K5LJF96F-part1:/srv/dev-disk-by-id-ata-WDC_WD100EMAZ-00WJTA0_2YJD8UYD-part1:/srv/dev-disk-by-id-ata-WDC_WD100EMAZ-00WJTA0_2YHZ3Z6D-part1 /srv/6a966440-66f7-4a88-b88b-da3e8ed4dafd fuse.mergerfs direct_io,defaults,allow_other,use_ino,dropcacheonclose=true,func.getattr=newest,category.create=ff,minfreespace=2048G,fsname=Store:6a966440-66f7-4a88-b88b-da3e8ed4dafd,x-systemd.requires=/srv/dev-disk-by-id-ata-TOSHIBA_MG05ACA800E_97A5K5MSF96F-part1,x-systemd.requires=/srv/dev-disk-by-id-ata-ST8000DM004-2CX188_ZR10P2GE-part1,x-systemd.requires=/srv/dev-disk-by-id-ata-TOSHIBA_MG05ACA800E_97B6K5LJF96F-part1,x-systemd.requires=/srv/dev-disk-by-id-ata-WDC_WD100EMAZ-00WJTA0_2YJD8UYD-part1,x-systemd.requires=/srv/dev-disk-by-id-ata-WDC_WD100EMAZ-00WJTA0_2YHZ3Z6D-part1 0 0 # <<< [openmediavault]
-
So I am still without my mergerFS volume, and just realized that my ZFS volume is also missing. I am quite ignorant to this, so I attached a bunch of images. I hoping on getting some guidance.
¯\_(ツ)_/¯
Thanks
-
Do you have a backup copy of your OMV 5 fstab that had your mergerfs configuration in it?
Found this:
Code
Display More2021Sept23 root@omvFive:~# cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sdj2 during installation UUID=843ef7cf-f9fa-485f-bbd9-ca60e7b82742 / ext4 noatime,nodiratime,errors=remount-ro 0 1 # /boot/efi was on /dev/sdj1 during installation UUID=45EF-1513 /boot/efi vfat umask=0077 0 1 # swap was on /dev/sdj3 during installation #UUID=6a4f43ee-b458-4084-96c8-9cb298c33826 none swap sw 0 0 # >>> [openmediavault] /dev/disk/by-id/ata-WDC_WD120EMFZ-11A6JA0_9KG52WDL-part1 /srv/dev-disk-by-id-ata-WDC_WD120EMFZ-11A6JA0_9KG52WDL-part1 btrfs defaults,nofail 0 2 /dev/disk/by-id/ata-WDC_WD100EMAZ-00WJTA0_2YJD8UYD-part1 /srv/dev-disk-by-id-ata-WDC_WD100EMAZ-00WJTA0_2YJD8UYD-part1 btrfs defaults,nofail 0 2 /dev/disk/by-id/ata-ST8000DM004-2CX188_ZR10P2GE-part1 /srv/dev-disk-by-id-ata-ST8000DM004-2CX188_ZR10P2GE-part1 btrfs defaults,nofail 0 2 /dev/disk/by-id/ata-TOSHIBA_MG05ACA800E_97B6K5LJF96F-part1 /srv/dev-disk-by-id-ata-TOSHIBA_MG05ACA800E_97B6K5LJF96F-part1 btrfs defaults,nofail 0 2 /dev/disk/by-id/ata-TOSHIBA_MG05ACA800E_97A5K5MSF96F-part1 /srv/dev-disk-by-id-ata-TOSHIBA_MG05ACA800E_97A5K5MSF96F-part1 btrfs defaults,nofail 0 2 /srv/dev-disk-by-id-ata-ST8000DM004-2CX188_ZR10P2GE-part1:/srv/dev-disk-by-id-ata-WDC_WD100EMAZ-00WJTA0_2YJD8UYD-part1:/srv/dev-disk-by-id-ata-TOSHIBA_MG05ACA800E_97A5K5MSF96F-part1:/srv/dev-disk-by-id-ata-TOSHIBA_MG05ACA800E_97B6K5LJF96F-part1 /srv/6a966440-66f7-4a88-b88b-da3e8ed4dafd fuse.mergerfs direct_io,defaults,allow_other,use_ino,dropcacheonclose=true,func.getattr=newest,category.create=epff,minfreespace=2048G,fsname=Store:6a966440-66f7-4a88-b88b-da3e8ed4dafd,x-systemd.requires=/srv/dev-disk-by-id-ata-ST8000DM004-2CX188_ZR10P2GE-part1,x-systemd.requires=/srv/dev-disk-by-id-ata-WDC_WD100EMAZ-00WJTA0_2YJD8UYD-part1,x-systemd.requires=/srv/dev-disk-by-id-ata-TOSHIBA_MG05ACA800E_97A5K5MSF96F-part1,x-systemd.requires=/srv/dev-disk-by-id-ata-TOSHIBA_MG05ACA800E_97B6K5LJF96F-part1 0 0 # <<< [openmediavault]
-
Do you have a backup copy of your OMV 5 fstab that had your mergerfs configuration in it?
Not a recent/current one. I did have a copy&past text file a while back. I think it might be on my OMV on one of the random drives that are not currently stitched together with mergerFS. I am looking.
-
Wait for the OS and its plugins to mature or just configure it by hand in fstab which is what I do.
Here I am after running imv-release-upgrade and now realizing that my mergerFS 'volume' is no longer. I need help with something I mostly do not understand. I am willing to edit my /etc/fstab, but I fear doing more damage. So please excuse my ignorance while I attempt to sort out my situation.
I will attach my current/etc/fstab with the hope that someone will say, 'Oh, this simple info is missing. Add this." Let's see where this goes.Code
Display More# /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sdj2 during installation UUID=843ef7cf-f9fa-485f-bbd9-ca60e7b82742 / ext4 noatime,nodiratime,errors=remount-ro 0 1 # /boot/efi was on /dev/sdj1 during installation UUID=45EF-1513 /boot/efi vfat umask=0077 0 1 # swap was on /dev/sdj3 during installation #UUID=6a4f43ee-b458-4084-96c8-9cb298c33826 none swap sw 0 0 # >>> [openmediavault] /dev/disk/by-id/ata-WDC_WD120EMFZ-11A6JA0_9KG52WDL-part1 /srv/dev-disk-by-id-ata-WDC_WD120EMFZ-11A6JA0_9KG52WDL-part1 btrfs defaults,nofail 0 2 /dev/disk/by-id/ata-WDC_WD100EMAZ-00WJTA0_2YJD8UYD-part1 /srv/dev-disk-by-id-ata-WDC_WD100EMAZ-00WJTA0_2YJD8UYD-part1 btrfs defaults,nofail 0 2 /dev/disk/by-id/ata-ST8000DM004-2CX188_ZR10P2GE-part1 /srv/dev-disk-by-id-ata-ST8000DM004-2CX188_ZR10P2GE-part1 btrfs defaults,nofail 0 2 /dev/disk/by-id/ata-TOSHIBA_MG05ACA800E_97B6K5LJF96F-part1 /srv/dev-disk-by-id-ata-TOSHIBA_MG05ACA800E_97B6K5LJF96F-part1 btrfs defaults,nofail 0 2 /dev/disk/by-id/ata-TOSHIBA_MG05ACA800E_97A5K5MSF96F-part1 /srv/dev-disk-by-id-ata-TOSHIBA_MG05ACA800E_97A5K5MSF96F-part1 btrfs defaults,nofail 0 2 /dev/disk/by-id/ata-WDC_WD100EMAZ-00WJTA0_2YHZ3Z6D-part1 /srv/dev-disk-by-id-ata-WDC_WD100EMAZ-00WJTA0_2YHZ3Z6D-part1 btrfs defaults,nofail 0 2 /srv/dev-disk-by-id-ata-TOSHIBA_MG05ACA800E_97A5K5MSF96F-part1:/srv/dev-disk-by-id-ata-ST8000DM004-2CX188_ZR10P2GE-part1:/srv/dev-disk-by-id-ata-TOSHIBA_MG05ACA800E_97B6K5LJF96F-part1:/srv/dev-disk-by-id-ata> # <<< [openmediavault]
Thank you
-
Is this an issue? If so what should I do?
Ran 'omv-firstaid' selected 'Clean apt' got this:
1. Cleaning apt cache files...
W: chown to _apt:root of directory /var/cache/apt/archives/partial failed - SetupAPTPartialDirectory (30: Read-only file system)
W: chmod 0700 of directory /var/cache/apt/archives/partial failed - SetupAPTPartialDirectory (30: Read-only file system)
W: chown to _apt:root of directory /var/lib/apt/lists/auxfiles failed - SetupAPTPartialDirectory (30: Read-only file system)
W: chmod 0755 of directory /var/lib/apt/lists/auxfiles failed - SetupAPTPartialDirectory (30: Read-only file system)
W: Not using locking for read only lock file /var/cache/apt/archives/lock
W: chown to _apt:root of directory /var/lib/apt/lists/partial failed - SetupAPTPartialDirectory (30: Read-only file system)
W: chmod 0700 of directory /var/lib/apt/lists/partial failed - SetupAPTPartialDirectory (30: Read-only file system)
W: chown to _apt:root of directory /var/lib/apt/lists/auxfiles failed - SetupAPTPartialDirectory (30: Read-only file system)
W: chmod 0755 of directory /var/lib/apt/lists/auxfiles failed - SetupAPTPartialDirectory (30: Read-only file system)
W: Not using locking for read only lock file /var/lib/apt/lists/lock
2. Clearing available dpkg packages...
dpkg: error: unable to access dpkg database directory '/var/lib/dpkg' for bulk available update: Read-only file system
ERROR: Command 'omv-aptclean' returned non-zero exit status 2.
-
see post #2
Thanks.
I ran:
Code
Display Morecd /etc/apt/sources.list.d sudo mv omv-extras-org.list omv-extras-org.bak echo "deb https://openmediavault-plugin-developers.github.io/packages/debian arrakis main" | sudo tee omv-extras-org.list cd /etc/apt/trusted.gpg.d/ sudo wget https://openmediavault-plugin-developers.github.io/packages/debian/omvextras2026.asc sudo apt-key add omvextras2026.asc sudo apt-get update
For now my production OMV4 box seems more stable while I bring my new machine online. I hope to have the new one finished before OMV6 is deemed 'release.'
-
Same here with My OMV4 production server.
df -h / : /dev/nvme0n1p1 226G 172G 44G 80% /
awk '$2 == "/" { print $4 }' /proc/mounts : rw,noatime,nodiratime,errors=remount-ro
omv-aptclean ends with
Code
Display More… Ign:49 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-docker stretch/main Translation-en Ign:40 https://dl.bintray.com/openmediavault-plugin-developers/arrakis stretch/main all Packages Err:41 https://dl.bintray.com/openmediavault-plugin-developers/arrakis stretch/main amd64 Packages 403 Forbidden Ign:42 https://dl.bintray.com/openmediavault-plugin-developers/arrakis stretch/main Translation-en Err:43 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-testing stretch/main amd64 Packages 403 Forbidden Ign:44 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-testing stretch/main all Packages Ign:46 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-testing stretch/main Translation-en Ign:47 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-docker stretch/main all Packages Err:48 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-docker stretch/main amd64 Packages 403 Forbidden Ign:49 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-docker stretch/main Translation-en Fetched 22.2 MB in 1min 12s (307 kB/s) Reading package lists... Done W: The repository 'https://dl.bintray.com/openmediavault-plugin-developers/arrakis stretch Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. W: The repository 'https://dl.bintray.com/openmediavault-plugin-developers/arrakis-testing stretch Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. W: The repository 'https://dl.bintray.com/openmediavault-plugin-developers/arrakis-docker stretch Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. E: Failed to fetch https://dl.bintray.com/openmediavault-plugin-developers/arrakis/dists/stretch/main/binary-amd64/Packages 403 Forbidden E: Failed to fetch https://dl.bintray.com/openmediavault-plugin-developers/arrakis-testing/dists/stretch/main/binary-amd64/Packages 403 Forbidden E: Failed to fetch https://dl.bintray.com/openmediavault-plugin-developers/arrakis-docker/dists/stretch/main/binary-amd64/Packages 403 Forbidden E: Some index files failed to download. They have been ignored, or old ones used instead.
-
Might be worth to check out what is not working. Maybe it is not related to Yacht. Or it is something that can be fixed.
Thanks for mentioning this. I kind of suspect that there is something else going on. I will try to list the signs and symptoms to come up with a diagnosis.
-
I have several containers, and Yacht is acting; can I say, wonky.
So, what will happen to my installed containers if I pull Yacht out from under them?
Also can I swap over to Portainer?Thanks