Nein, das geht leider nicht.
Posts by macom
-
-
Just a word of warning to everyone who wants to try AI agents. They can cause serious harm. Openclaw comes with security warnings that should not only be read, but also understood and followed. This is nothing specific to Openclaw, but applies to all AI agents.
-
Sorry, I have no further idea what might be wrong.
-
Did you check the "Windows Network" folder in the file manager from your screenshot?
-
Have you enabled smb? There is no screenshot showing this.
-
Don't use ACL, use only permissions. Use the resetperms plugins to reset the shared folder.
omv8:omv8_plugins:resetperms [omv-extras.org]
Then create a user and give him permissions on the shared folder.
-
-
+1 for UrBackup. Run it on Windows and Linux clients.
-
Run omv-upgrade from CLI.
-
I re-did config following guides
What exactly did you do? Maybe screenshots of the different configuration you have done might help to identify a missing step.
Only configurations related to network shares.
-
Usually I do updates from the WebGUI
That is the correct way. But sometimes you get better information when you run the update from the CLI.
-
Post the output of omv-upgrade in a code box.
Did you run the fix7to8upgrade script after you release-upgraded from OMV7 to OMV8?
-
Try sudo postfix flush to flush/purge all mails in the queue.
You can have a look at the mail queue with mailq
-
In this case it does not matter if it is raid or not. So this guide applies
omv8:new_user_guide [omv-extras.org]
After you created a shared folder, added it to the smb service, enabled the service, created a user, give that user permissions to read/write data on that shared folder.
-
Sorry. So I dont need the plugin installed to use diskclone?
The diskclone plugin has not been ported to OMV8. The plugin is using dd (a standard Linux tool) in the background. So you can use the dd command instead of the plugin. You can search on google or ask chatgpt how to clone a disk using dd.
Alternative is to use clonezilla
-
The advantage of cloning the disk is, that the UUID will be the same. So you can just replace the old disk with the cloned one and OMV will not notice any difference. So no need to point shared folders to the new disk etc
Of course you could achieve the same by copying the data over and then change the UUID.
Never use the original disk and the clone at the same time.
-
......... replace: header Subject: Monitoring restart -- Does not exist nginx: Subject: [OMV.local] Monitoring restart -- Does not exist nginx
and
.........replace: header Subject: Monitoring restart -- header Subject: Monitoring alert -- Exists nginx: Subject: [OMV.local] Monitoring alert -- Exists nginx
These mail are coming from the monitoring system. The first one is mentioning that nginx, that is the webserver for showing the GUI of OMV, has not started. The monitoring system is then trying to start nginx.
The second mail is telling that his was successful and that nginx is now running.
So here is the question, why nginx is not starting or only after the monitoring system has started.
and these are also sent as emails (about 55 emails)
Does this mean, you get these same ~55 mails at every reboot?
-
That looks all ok. Do you still have recent log entries regarding nginx?
-
In some threads here in the forum it has been reported, that spindown does not work reliably. WD drives where mentioned. In some cases it worked without issues when hd-idle was installed and used.
If you found an explanation in the meantime, it would be nice to share it here.
-
These are now messages from Postfix with errors.
You show only warnings.
Try disabling and enabling Notifications in the GUI of OMV.
