capote
(Marko)
December 8, 2023, 9:14am
1
NethServer Version: NS8 RC1
Before I get serious about switching to NS8, I wanted to configure a backup.
The obvious attempt to use a Minio container on the Synology Diskstation failed because the provided container is broken.
„Fatal glibc error: CPU does not support x86-64-v2“
opened 11:54AM - 01 Nov 23 UTC
closed 04:08PM - 01 Nov 23 UTC
community
fixed
After upgrading my Docker based minio installation from RELEASE.2023-10-25T06-33… -25Z to RELEASE.2023-11-01T01-57-10Z the container refuses to start on [older CPU](https://ark.intel.com/content/www/us/en/ark/products/33927/intel-xeon-processor-e5420-12m-cache-2-50-ghz-1333-mhz-fsb.html).
## Expected Behavior
The minio container starts.
## Current Behavior
The minio container fails to start with the exit code 127 and the following error message: `Fatal glibc error: CPU does not support x86-64-v2`. No other output is provided.
## Steps to Reproduce (for bugs)
1. `docker run -it minio/minio:RELEASE.2023-11-01T01-57-10Z`
## Context
While I understand this is an old CPU, my understanding is that minio itself does not require these CPU instructions. Furthermore, the [binary](https://dl.min.io/server/minio/release/linux-amd64/minio.RELEASE.2023-11-01T01-57-10Z) used in the docker image works on the same machine so it seems the issue comes with the new base image. In fact, when trying to run the new base image I encounter the same error.
```sh
$ docker run registry.access.redhat.com/ubi9/ubi-minimal:9.2
Fatal glibc error: CPU does not support x86-64-v2
```
## Regression
Yes:
- [RELEASE.2023-11-01T01-57-10Z](https://github.com/minio/minio/releases/tag/RELEASE.2023-11-01T01-57-10Z)
- #18313
- #18329
## Your Environment
* Version used (`minio --version`):
```
minio version RELEASE.2023-11-01T01-57-10Z (commit-id=55e713db0a367f6cccee00af49f00c269e6ca619)
Runtime: go1.21.3 linux/amd64
License: GNU AGPLv3 <https://www.gnu.org/licenses/agpl-3.0.html>
Copyright: 2015-2023 MinIO, Inc.
```
* Server setup and configuration: N/A
* Operating System and version (`uname -a`):
`Linux mir 6.1.53-gentoo-x86_64-jmk-selinux #1 SMP PREEMPT_DYNAMIC Thu Sep 14 13:12:26 CEST 2023 x86_64 Intel(R) Xeon(R) CPU E5420 @ 2.50GHz GenuineIntel GNU/Linux`
* Hardware:
```
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Xeon(R) CPU E5420 @ 2.50GHz
stepping : 6
microcode : 0x60b
cpu MHz : 2500.082
cache size : 6144 KB
physical id : 0
siblings : 8
core id : 0
cpu cores : 8
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu de tsc msr pae mce cx8 apic sep mca cmov pat clflush acpi mmx fxsr sse sse2 ht syscall nx lm constant_tsc rep_good nopl cpuid tsc_known_freq pni est ssse3 cx16 sse4_1 hypervisor lahf_lm
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit mmio_unknown
bogomips : 5000.02
clflush size : 64
cache_alignment : 64
address sizes : 38 bits physical, 48 bits virtual
power management:
```
The alternative, an SMB backup, was supposed to be a no-brainer.
But I failed miserably, and the documentation contains practically no useful information.
https://docs.nethserver.org/projects/ns8/en/latest/backup.html
In preparation, I set up a new share on the Synology called “NS8-BAK”.
The user only responsible for the backup is also called “NS8-BAK” and has the read/write rights for the share.
Transferring the information to the GUI proved more difficult than expected and has so far been unsuccessful.
What have I misunderstood or done wrong here?
Sincerley, Marko
2 Likes
davidep
(Davide Principi)
December 8, 2023, 10:56am
2
You’re right the docs and the UI do not help.
IIRC in the URL field you’d type just the share name, NS8-BAK
3 Likes
capote
(Marko)
December 8, 2023, 11:20am
3
As soon as you get it right, it’s easy…
3 Likes
davidep
(Davide Principi)
December 11, 2023, 11:27am
4
The URL field has a placeholder that should help to fill that field. In Windows share case the placeholder is Share name
I opened a PR for the docs, to add a table with some examples of the possible URL field values. This is a preview: Backup and restore — NS8 documentation
Any idea to improve the UI further?
2 Likes
capote
(Marko)
December 11, 2023, 3:55pm
5
What misled me was the label “URL” at the top left.
In my opinion, this has no guiding significance and should be removed.
The UI’s naming convention could also be standardized.
Above the fields for entering the parameters is the title of the field, which indicates the required content.
The label smb:
to the left of the first field could be omitted.
Instead, the field “Name of the share at top directory level” could be displayed above the field.
Inside the field could display:
Example: for the real Share “//vol1/NS-BAK” use only “NS8-BAK”
1 Like
davidep
(Davide Principi)
Split this topic
December 29, 2023, 9:10am
6
2 posts were split to a new topic: Restore of a module (Dokuwiki)