Any idea where to clean up the remaining mountpoint apparently still listed somewhere?
There are no more references in config.xml or in fstab.
In OMV 4 the command omv-mkconf monit should have resolved the issue too. AFAIK the omv-mkconf command of OMV3 und OMV4 distributes some configuration changes to the several Linux-related configuration files.
... and using the Proxmox-kernel is also recommended / necessary.
Also dass es einen Port auf andere Systeme gibt, davon habe ich bisher noch nichts vernommen. Aber das ist doch ein Skript? Würde dir der Quellcode dazu nichts nützen für eine eigene Anpassung? Sollte eigentlich hier zu finden sein: OpenMediaVault-Plugin-Developers / openmediavault-autoshutdown
Are you booting on a flash drive? If yes, maybe your flash drive is going to die.
Also wenn es mit IP-Adresse geht, aber nicht über den Namen, dann hat es definitiv mit der Namensauflösung zu tun. Das Thema hatten wir hier im Forum auch schon mehrfach. Meistens stellte es sich dann als Problem der restlichen IT-Infrastruktur heraus (z.B. neuer Router, anderer Provider), wenn die Settings in OMV korrekt waren und es somit daran nicht liegen konnte. Manchmal half auch ein schnöder Reboot von OMV-System und Router.
Ein guter Test ist auch, mal als DNS-Setting in OMV mal 8.8.8.8 auszuprobieren.
Ping http://www.google.de geht nicht.
Wenn du das von einem anderem PC im gleichen Netzwerk wie das NAS ausprobierst, geht es dann?
Ich habe es gerade mal von meinem OMV System ausprobiert:
ping https://www.google.de => Geht nicht "unknown host"
ping http://www.google.de => Geht nicht "unknown host"
ping www.google.de => Geht! Eine Antwort kommt zurück.
Oft sind daran falsche oder fehlende DNS Settings schuld. Bitte checke mal deine Netzwerkeinstellungen. Dort gibt es eine Möglichkeit, DNS Adressen zu konfigurieren.
Mithilfe von 3L Kaffe und ca. 8.5 Std. konnte ich alles von OMV entfernen und neu installieren.
Das ist schade das ein Upgrade von 4 auf 5 nicht problemlos läuft.
Vielleicht ist das ´ne Erklärung dafür: OMV 5.0 - finally out! :-)
4.1.36-1 (siehe ganz oben)
Ah, habe ich übersehen.
Geht ein Update auf die 5 problemlos?
Es wird eher empfohlen, OMV 5 neu zu installieren. Es gibt aber einen langen Thread hier über ein Script, dass das Update durchführt:
Upgrade Scripts for non-interactive major release upgrades (2->3, 3->4, 4->5)
Einige haben das Update wohl schon erfolgreich absolviert. Vor dem Update solltest du auf jeden Fall ein Image deines Bootlaufwerks machen, damit du wieder zurück kommst, sollte doch was schiefgehen.
There are two different plugins available:
a) OMV-unionfilesystems
b) OMV-mergerfsfolders
In your case you don´t need b) if you want to pool complete drives.
For the different mergerfs policies you may want to see the documentation.
or you may have a look here UnionFS and file distribution
Welche OMV Version benutzt du? OMV 4 oder 5? "/sharedfolders" wurde in OMV 5 Version wieder deaktiviert, da es viele Probleme damit gab: OMV 5.3.3-1 disabling /sharedfolder/ feature - why?
You should be extremely careful if you do manual changes in the config.xml file. Normally this is not necessary and not recommended also.
But if you intend to do it you should always be able to restore the original version.
Then I installed the flash media plugin and followed its instructions on how to remove the swap partition.
Normally it is not necessary to edit /etc/fstab in order to remove the swap partition for the flash media plugin. This step is noticed as "optional". You should undo the change of the fstab file and restore config.xml from the backup copy you hopefully have created before modifying the main openmediavault configuration database.
edstiles Do you maybe have a Samba recycle bin activated, where the moved files are still contained? Moving files to another system means deletion on the original location.
This leads to the situation that discs are not available when the computer wants to access them.
Same issue would therefore apply for eSata
I would agree with this statement. If an external eSATA device isn´t available in an mdadm configuration the raid status would be set to degraded too similar to USB.
Am I safe to assume that it does not have the same restrictions as USB when it comes to RAID setups?
If you pay attention that the external eSATA box is accessible from OMV, I would confirm this.
eSATA is meanwhile outdated because it is slower than USB especially in a port multiplier (PM) configuration, where several disk devices are connected by one eSATA connector. The bandwidth of one Sata connection is shared by all connected devices.
Nevertheless I think it is more reliable then USB. In my setup I use a snapraid / unionfs pool out of three 8TB disks for my movie collection. The disks are located in an ICYCube 4-Bay case and connected via eSATA directly to one SATA connector with PM support of the ASROCK C2550D4i motherboard. All disks are detected in OMV as separate devices.
I take care that the external box is switched on when the NAS system is booted. I have no stability problems. The only drawback is that the disk transfer rate is slower when more than one disk is accessed at the same time. This should be avoided if possible. But in my unionfs configuration if only one disk is active the availaible disk transfer rate can saturate a standard gigabit Ethernet connection (almost) completely.
The better approach would have been a host bus adaptor in IT mode with a connection to an external DAS box. But the ASROCK board has only one PCIe slot and this slot is already used by a 4x USB3 card, which I use for external backup with several USB3 disk enclosures.
, I had abschmiert translate to smears and not crashes, deepl is usually a better option.
The translation result of any online translation tool is not always perfect. You always have to pay attention to whether the translation fits the context. This is a really nice example: "abschmieren" means "to lubricate" but in IT-context it has mostly the meaning of a system crash.
I must confess I hatte das nicht bemerkt. Du bist right again. 😁
Really interesting grammar!
There are some threads started in German where e.g. geaves responds in English. Personally I would prefer an answer in a different language than no answer at all
Maybe you´ll find the answer here: How to restore a backup done with openmediavault backup plugin (and fsarchiver option)?
Why isn't it possible to use the backup to restore the system?
You would need an image backup of your installation e.g. created with CloneZilla. With such an image you would be able to restore the complete system. As I know the OMV backup plugin does create a backup of the OMV settings or maybe of the OMV installation, not of the whole system. But maybe I am wrong and someone else can give a correct answer. I have never used the OMV backup plugin. I always use CloneZilla.
Sonst kann das nämlich auf manche Leute ziemlich irritierend wirken. 😉
Google translate is your friend. There are several examples here in the forum regarding threads with mixed languages.
