Posts by rz259

I have two OMV installations and had the same problem on one machine - in my case it helped to rename the file /etc/rsyslog.d/openmediavault-pamtally2.conf - the configuration changes could be applied without any trouble.

Can I safely delete the file?

Ok, just ran omv-release-upgrade - took about 10 minutes on my machine. After rebooting OMV 7.7 was running on my systems. the only problem I had was that I still the plugins from OMV 6 and the openmediavault-md plugin was not available.

After running fix6to7upgrade everything was fine.

@ryecoaaron: Thanks a lot for your help.

Rudi

thx for your quick response - I'll give it a try tomorrow.

How long does it take approximately? And where do I find the fix6to7upgrade script? currently it's not on my machine

Rudi

Hi,

I am currently running OMV 6.9.16-1 (Shaitan) and would like to upgrade to OMV 7. What is the best rsp. the recommended way to upgrade? My OMV installation is running on a AMD64 platform and using RAID5 composed of 4 disks. I have installed some additional plugins (compose, borgbackup, autoshutdown).

Do I have to uninstall OMV-extras and those plugins?

I saw a answer from crashtest to post with update problem sdescribing his procedure to upgrade for sbcs.

Can I use this procedure or is there a better/simpler one? I was a bit astonished about the advice to unplug the disks and also running commands like

wget -O - https://github.com/OpenMediaVa…ckages/raw/master/install | bash

and to select the correct boot disk for grub.

I was hoping for doing the upgrade all over with ssh.

Thx for any advice,

Rudi

Hm, I suppose it's not the disk, i suspect the dock rsp. its SATA interface - I think I will start with it and then we'll see if the problem persists....

Unfortunately the long test does not terminate normally - it says "Aborted by host".

BernH

Thanks for the hints - the disks are pretty new but I bought them not as a All in one drive, instad I bought the housing and the disk separately. ANd no, the drives are not being carried around, the stay at their places since they are intended for ANS backup.

Currently all works fine, the errors do not show up any more. However I will watch the situation - maybe it's the cable or maybe it's the electronics in the housing...

Thx for your answer, I forgot to mention that both disks are pretty new, they are in use for about 2 months.

Regarding the SMART attributes - with OK I meant there are no errors shown and they are identical for both drives.

The attribute 5 is shown as good, however all others are labelled als type "Old age" and Status "Unknown" - but again, this applies to both disks and only one is causing trouble...

I have run a short SMART test which showed no errors and also have initiated a long SMART test but that will last several hours - I'll supply the information when the test has completed.

Hello,

i'vr got two NAS systems both with an external USB disk for backup purposes (both drives are Seagate drives with 8 TB ). One of them causes from time to time some problems.

First I get an monirotring alert email saying that the file system cannot be read:

Event:       Does not exist
Description: unable to read filesystem '/srv/dev-disk-by-uuid-d3ecd81f-af22-49ee-92f6-1d15085893f3' state

This triggered the monitoring system to: restart

Then I got two emails saying that the mountpoint does not exist:

Event:       Status failed
Description: status failed (1) -- /srv/dev-disk-by-uuid-d3ecd81f-af22-49ee-92f6-1d15085893f3 is not a mountpoint

This triggered the monitoring system to: alert

After that

Event:       Exists
Description: succeeded getting filesystem statistics for '/srv/dev-disk-by-uuid-d3ecd81f-af22-49ee-92f6-1d15085893f3'

This triggered the monitoring system to: alert

And last I get an email saying that the mountpoint exists

Event:       Status succeeded
Description: status succeeded (0) -- /srv/dev-disk-by-uuid-d3ecd81f-af22-49ee-92f6-1d15085893f3 is a mountpoint

This triggered the monitoring system to: alert

This seems very strange to me - I had this problems several times but backup with BorgBackup worked without problems for me. However yesterday the mountpoint did not exist any longer, even the disk was no longer accessible (did not show up when I checked with lsblk). I had to switch off and on the disk, after that the disk was at least visible when running lsblk. After that I had to break the locks for borgbackup and everything was fine - I started a backup yesterday and tonight - everything was ok.

Now I get the above mentioned messages again - how can I find out what the problem is? Is there anything to analyze my problems?

When I look at the smart statistics in OMV I find that most attributes are ok - in fact the attributes for both backup drives are identical.

Thanks for any hints,

Rudi

Ok, thanks a lot for the explanation- I think I will remove the S.M.A.R.T udn the filsstem widgetes too or maybe I close the dashboard tab after checking;-)

Well. I think I found the problem. I used to have the OMV dashboard open in a browser tab and it seems that this keeps the disks running.

Once I closed the tab and checked after a certain period everything was ok. When I leave the dashboard open in the browser tab it remains open - perhaps I have too much infos on the dashboard.

I checked several times closing and reopeing the tab and this seems to be the source why the disk don't spin down.

Is this a known behaviour?

Very strange - I did nothing (at least nothing I would be aware of) and now the temperature is back to 32 degress.

Don't know since when it fell back but it must hve been in the last tow days.

Wait a minute - I had installed another plugin for backup purposes, but I never used it, so I removed it - maybe this was the reason However I hadn't used it at all...

But the most important is that the normal temperature is back again. I will re-enable the BorgBackup archive and then see, what happens...

How can I check if Borgackup is really disabled? Is there a log file or something like this I can see?

I am asking because the only way I found to disable Borgbackup is to disable the Archive -but maybe there is a better solution.

And I checked the entries in /et/cron.d - there is a file for BorgBackup which runs every hour.

So if I did not disable borgbackup correctoy maybe it is still running...

Then I don't understand it - I set the "Advanced Power Management" (in Storage - Disks) to 1 (Minimum power usage with standby (spindown)" and the spindown time to 30 minutes.

I did this also for the external backup disk (a 8 TB usb drive) - however even the usb drive has a temperate of 40 degrees although it should do nothing....

If it's not a problem of Borgbackup - what could be the reason?

Well, sthat's strange, since I have not configured anything like hourly borg runs. I noticed that borg runs in the night but after I remarked this I even disabled the plugin - still the disk temperature is very hign.

I just rebootedthe nas and will see if that changes anything.

BTW: Of course it might be a coincidence that the temperate rose when running the backup and did not go down after the backup - however that would be a strange coincidence.

Hello all,

I've got a question regarding disk spindown - a few days ago I installed Borgbackup and did my first backup. Since then the disks seem to run always (temperature is around 40 - 45 degrees), although I set the to spindown after 30 minutes.

Before installing and running BorgBackup the disks were around 30 degrees - so I assume it has something to do with Borgbackup. It seems as if Borgbackup prevents the spindown. Even my USB backup drive is around 40 degrees although no backup is running.

What can I do about this behaviour? I'd like to suspend disks if not needed.

Thanks for reading and helping;-)

Rudi

^{Hello Chente,}

^{thanks a lot for your help. I recreated the filesystem in the GUI and was then able to create the filesytem and then the share.}

^{Currently the first backup is running1}

^{Thanks again,}

^Rudi

Ok, so I tried to create a new shared folder for my backup disk, but unfortunately I failed;-(

Here's the situation:

I attached an USB drive with 8 TB and I formatted the drive with ext4 and mounted the disk to /media/backup on the command line - everything's fine so far. I could use Borgackup on the command line without any problems.

The disk is visible as /dev/sde (both in the console and also in OMV).

However when I tied to create a shared folder I ran into problems. In the page where I can add a shared folder , I have to select a file system - unfortunately I only can see a filesystem for the RAID I created and I also can see a file system for the NVE disk containing the OS - no filesystem for /dev/sde.

I then tried to create a new file system, but of course this did not work, since /dev/sde already contains a file system. I could not mount it either since the device is not shown in the list. Unmounting /dev/sde and then mount it from OMV did not work either.

So I am puzzled - any hint what could be the problem here?

Thanks a lot for your hints,

Rudi

Thanks for the hint!

Currently I am a bit stuck since the housings I bought for my disks are complete junk. One worked just for yesterday and the second never worked. So I sent them back and ordered other housings - I hope they will be of better quality.

The new housings are supposed to arrive on Thursday - then I can continue with my backup - so if I have further questions it'll be not before Thursday;-)

Sorry for writing inside the quote;-)

No, it's not really a problem, it's just that I only use shares to "partition" my data into separate logical units (like Videos, Music, ...) which I like to share between different users and computers - so that does not really apply for backup.

However, it's not a problem - I just wanted to make sure that I understand the concept.

Thanks again,

Rudi

Quote from chente

Reading your post I think that all your questions are answered in the document. If you have questions after reading it, don't hesitate to ask. And if you have suggestions for improvements to the document to improve understanding, they are also appreciated.

Thanks for pointing me to this documentation. In fact I had searched but I did not find what I was looking for. I am using OMV 6 and the link to the online docs for OMV 6 says that this topic does not yet exist.

If I understand the dos right I have to create a shared folder for the repository - why do I need such a shared repository? When I am using borgbackup in the shell I just need to mount the USB device and can save it in the folder where the device is mounted.