you can use duckdns even without flashing the router or by a cheap domain with access to nameservers.
I am using inwx.com.
you can use duckdns even without flashing the router or by a cheap domain with access to nameservers.
I am using inwx.com.
you can use duckdns even without flashing the router or by a cheap domain with access to nameservers.
I am using inwx.com.
I don't know how to do this without loosing access to my Home Assistance server.
Best regards.
It took me a while to understand how DDNS works, and I think I'll give it a try. Unfortunately, I didn't find a DDNS OMV plugin. But using OMV to update the IP will not be the best choice in my case. Even if I intend to run this machine 24/7, there is no data on it that I might critically need. So the best choice is to run a cron job on the Raspberry Pi running my Home Assistant instance I think. This little guy will remain on everytime.
Best regards.
It took me a while to understand how DDNS works, and I think I'll give it a try. Unfortunately, I didn't find a DDNS OMV plugin. But using OMV to update the IP will not be the best choice in my case. Even if I intend to run this machine 24/7, there is no data on it that I might critically need. So the best choice is to run a cron job on the Raspberry Pi running my Home Assistant instance I think. This little guy will remain on everytime.
Best regards.
what about to use duckdns docker?: https://hub.docker.com/r/linuxserver/duckdns/
what about to use duckdns docker?: https://hub.docker.com/r/linuxserver/duckdns/
As I explained before, there are no guarantees that the computer with OMV will be on 24/7. However, the RPi remains on all the time. I already implemented a task in crom to update the IP every 10 minutes.
Best regards.
Nextcloud up and running as it should! Certbot didn't show any error with duckdns. My Home Assistant RPi is in charge of updating the IP from now on.
Next steps will be system backup, data backup and DNLA, I guess. I bougth a reasonably large USB flash drive for the system backup, and intend to use the external 4TB drive for data backups.
Best regards.
I am a bit confused about which plugin to install for system backup. Looking into the OMV plugins session, I found the following plugins that I think could be usefull:
- openmediavault-backup 5.2.4
- openmediavault-borgbackup 5.1.9
- openmediavault-rsnapshot 5.0.4
But I don't know which one is most suitable for my case.
Best regards.
for os backup use openmediavault-backup 5.2.4, for data backup use rsync
for os backup use openmediavault-backup 5.2.4, for data backup use rsync
Openmediavault-backup 5.2.4 then!
I was intending to use openmediavault-usbbackup 5.0.9-1 for data backup. Is there any major advantage in using rsync instead?
Best regards.
I was intending to use openmediavault-usbbackup 5.0.9-1 for data backup. Is there any major advantage in using rsync instead?
For easy data restoration, in a matter of minutes, yes. Take a look -> here.
Rsync backup is explained as is the restoration process.
I'm getting this recurring error when creating the file system:
Error: The backup GPT table is corrupt, but the primary appears OK, so that will be used.
I've already fdisk the disk, deleting all partitions and starting over, I've gdisk the disk trying to recover from the damage, and I've already zeroed the disk using dd, which took forever, without success. Has anyone had this same error?
Best regards.
Have you looked at -> SMART stat's for the drive?
I already had done all that!
Best regards.
Have you looked at -> SMART stat's for the drive?
Nope. I didn't even start monitoring it. I'll give it a try.
Best regards.
S.M.A.R.T. returned the folowing info:
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-5.10.0-0.bpo.9-amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org
Read Device Identity failed: scsi error unsupported scsi opcode
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
Alles anzeigen
Best regards.
I already had done all that!
Best regards.
There's a lot of info out there to say you done all that.
How is the drive connected?
Is it part or are you trying to set it as part of a RAID?
Do you have any important DATA on the drive?
If not, you can try to redo the partition table (aka initialize the drive) to see if the error goes away)
Just remember that you if you do any thing on fdisk/gdisk, you'll loose everything on the drive.
You can also completely delete the partition table (from CLI) and create the FS from OMV Gui.
It will create a new partition table and format it with the selected FS type.
Probably you'll have some references to the old partition on the disk, showing in the OMV Gui that will need to be cleared.
NOTE: This is a post that I think is quite relevant:
This comment from the creator of gdisk seems helpfull:
partitioning - Fixing corrupt backup GPT table? - Ask Ubuntu
ZitatNote that
gdisk
also has av
command that should turn up details about most GPT problems. Also, this page describesgdisk
's repairing options. As to merging two separate blocks of unallocated space, that's done in GParted or the like by moving intervening partition(s). This is a risky operation, so do it only if necessary. Alternatively, you could create two partitions and use LVM to create a logical volume that would span both partitions, even though they're non-contiguous. – Rod Smith
Dec 6, 2013 at 18:13
There's a lot of info out there to say you done all that.
Yes, indeed! But the majority of the posts are about fixing an usual error in the GPT tables.
How is the drive connected?
Is it part or are you trying to set it as part of a RAID?
It is an USB flash drive that I bought for system backup. I finally determined that is a fake drive (faulty or overrated capacity), and that is the source of the problem.
Alles anzeigenDo you have any important DATA on the drive?
If not, you can try to redo the partition table (aka initialize the drive) to see if the error goes away)
Just remember that you if you do any thing on fdisk/gdisk, you'll loose everything on the drive.
You can also completely delete the partition table (from CLI) and create the FS from OMV Gui.
It will create a new partition table and format it with the selected FS type.
Probably you'll have some references to the old partition on the disk, showing in the OMV Gui that will need to be cleared.
The drive was new, so there wasn´t any data on it.
I have tried to redo the partition, redo the GPT, rebuild the backup GPT from main, zerofill the drive, all unsuccessful.
I used both the Debian CLI and the OMV GUI.
NOTE: This is a post that I think is quite relevant:
This comment from the creator of gdisk seems helpfull:
partitioning - Fixing corrupt backup GPT table? - Ask Ubuntu
That post was my first try.
Best regards.
It is an USB flash drive that I bought for system backup. I finally determined that is a fake drive (faulty or overrated capacity), and that is the source of the problem.
So many people make this mistake, to include myself, in times past. (Some us learn the hard way.) SanDisk or Samsung, original flash manufactures, are the only brands I'll use now. And I make sure they're not bulk or ordered on-line. They have to be in a retail blister pack. That avoids fakes.
So many people make this mistake, to include myself, in times past. (Some us learn the hard way.) SanDisk or Samsung, original flash manufactures, are the only brands I'll use now. And I make sure they're not bulk or ordered on-line. They have to be in a retail blister pack. That avoids fakes.
Shame on me! The one I bought was a Sandisk 128GB in a blister pack. But Sandisk don´t make this particular flash drive in this capacity. Also, there are a few mechanical details that points towards a fake drive.
I already ordered another one, this time from Amazon
Best regards.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!