I would be grateful for a bit of advice on tweaking my current system.
I am running OMV6 on my home server with a number of dockers on it - PiHole, TVHeadend, Jellyfin, Home Assistant etc.
Until fairly recently, I had no remote access to the server but I decided to try and get the Home Assistant app on my phone working when I disconnected from my home network.
Content embedded from external sources will not be displayed without your consent.
Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
and managed to get things working - I had to adapt things slightly, as I used the docker version of Cloudflare, but everything was working fine.
However, everything suddenly stopped working - it turns out that the fee domain name that I set up (via the recommended Freenom site) is no longer active and Freenom domains are no longer usable with Clodflare in any event.
What are my options, now:
1. Buy a cheap domain name and continue to use Cloudflare?
2. Have a go with another method, like Wireguard, for instance?
Another thing that has occurred to me is that, in addition to Home Assistant, I might like to have access to the entirety of my server, remotely - e.g. the ability to schedule on TVHeadend, access to my home storage. Would this have a bearing on what method I choose?
I recently managed to recover most of the files from a hard drive that I recently wiped.
However, I now have another hard drive that is full of duplicates and I need to try and get rid of those and put everything back in its original state.
The HDD is formatted as ext4 but is being shared to my network via Samba.
I am running Dupeguru on a Windows laptop.
One option, in particular, is causing me some issues. Do I want to enable the option for "Ignore duplicates hardlinking to the same file"?
The reason I ask is that, before I wiped the hard drive, I had some RSnapshot backups on the disk, which I understand uses hardlinking to save space.
Any advice on what this option really does, and whether I should use it, would be very much appreciated.
Further to the below, I have accepted that whatever is on the HDD is probably gone and that it just isn't worth it, financially, to try and recover anything - i.e. I am going to have a go, myself, and see what I can get back (if anything).
I let Testdisk do its thing and got the following two screens:
Any further advice, on what to do now, would be much appreciated.
Something catastrophic has just happened on my hard drive, when trying to change caddies and it is now not being recognized by Linux.
The drive is 14TB and formatted as ext4.
I am running Puppy Linux and whenever I plug the hard drive in, it is not recognized - i.e. cannot be mounted.
Most of the information on there is replacable but there are a few things that I do not think I have backed up (i.e. a few photos of someone that has since passed away).
If anyone can get it working again I would be more than happy to pay them 30 Euros for their help!
I would be really grateful for some initial advice on setting up a way to backup my system to a friend's house.
At the moment, I am running OMV6 on my home server, which contains a folder called "DATA", which I would like to set up.
The only remote access I have is via Cloudflare to give access to Home Assistant, which is running via Docker.
I have an Odroid HC2, with OMV6 also on it that I would like to use to back up the "DATA" file to it. I have a friend who says he is happy for me to leave the device plugged into his home network for a backup every evening.
Any advice on where to start would be much appreciated.
A few initial questions:
1. How do I securely expose my "DATA" folder so that the remote HC2 can access it? Can I do this with Cloudflare also?
2. Is it better to "Push" the files from my "DATA" folder to the HC2 or instead have the HC2 "Pull" the files from the the folder?
I always find it a bit of a struggle knowing whether to use a USB device's in-built spindown option against OMV's and whether there will ever be a conflict between the two.
I have decided to return the above enclosure as it just does not work as described.
so I can not only put my 14TB HDD in it but also my 6TB backup HDD.
I am not, however, convinced that those docking stations are designed for constant use. I was wondering whether I could attach lay my hard drives flat and connect them via a couple of these cables:
and it does not spindown the hard drive after 10 minutes as advertised.
This is a firmware update to change this but it does not seem to work - I can see that the device is set to never spindown, which is weird as the default should be 10 minutes.
I tried setting OMV to spin the hard drive down as well but that does not work either - can OMV only spin down SATA harddrives, rather than USB?
Is there anything else I can try to spin the harddrive down?
I did find the following on Amazon reviews but the firmware, that Dr Alan Priest found, no longer exists.
4.0 out of 5 stars Solidly built, works well, sleep function fiddly to set up Reviewed in the United Kingdom on 18 March 2023Size Name: USB 3.0 to SATA HDD CaddyColour Name: SilverVerified Purchase The product is easy to set up, well constructed and has a pleasing appearance in terms of design. Unless you upgrade the firmware, the drive remains powered up and spinning continuously, which obviously is not energy-efficient and may shorten the life of the hard disk you fit inside. It comes with instructions to download and update the firmware. I followed the instructions to the letter, and in my case this didn't work. The software tried three times and the final result was a big FAIL. With the original download I kept getting a message "firmware and device not matched". Not wanting to be beaten I spent about two hours Googling and browsing the web. Eventually I solved the problem by downloading a more up-to-date firmware from a third party driver site– Station Drivers. Search for AS Media then ASM-105x. the firmware version that worked for me was 140704_A1_A9_0. Just follow the instructions in the original PDF but substitute the new firmware file. Before you click the "play" to update, make sure you set the sleep timer to be something like 10 minutes (or 5 minutes according to your preference). I'm not sure that you can change this after you've updated the firmware, which might be the problem with the original download and instructions. I like everything about this product except the sleep function, which took me over two hours faffing about to set up properly, hence only 3 stars even though it's now working. Other than this, I can recommend this product. NB this is my own review. I purchased the product and no one has offered me any incentive to write this.
Thanks ever so much for this guys - really helpful.
I think my immediate priority, now, is to immediately get a 3.5" hard drive enclosure, so I can at least start backing things up. I can then start worrying about cloud backups as my "1" of the 3-2-1.
Is there anything in particular, I should look out for in a hard drive enclosure or are they much the same?
I would prefer one that lies flat, if possible, for stability reasons.
Found a copy of Amazon best buys, that could be likely candidates:
The first uses a ASM225CM chip, whereas the second uses ASM1153E - is there any real difference between these?
The second one seems to use aluminum, which I assume shall offer better cooling - but can it be used flat (not absolutely clear)?
The 3-minute autosleep, on the first, is also a bit severe (unless it can be changed). I always use at least 10 minutes to avoid unnecessary wear and tear.
I would really appreciate some advice on setting up some proper redundancy on my system.
At the moment, I do not really have any proper backup strategy - combination of various hard drives and cloud storage.
What I really want is a proper 3-2-1 method and I was wondering what other people do to achieve this.
My server is a mini x86 PC, so I only have USB3.0 Ports.
I have an external WD Essentials Drive (14TB) attached, that I use for all my Data - a lot of this is just recordings, so non-essential.
I also have a spare 6TB 3.5" WD Red that I am thinking of using as a backup drive.
1. Should I buy an external caddy, plug the 6TB into that, and then use that for backups or
2. Should I sell the 6TB drive and buy a 5TB 2.5" external drive instead?
I really would prefer not to have to worry about a separate power supply for another 3.5" external drive, but it is a bit inconvenient that 2.5" hard drives have not moved on from 5TB.
I guess my other options would be to buy a dual-bay hard drive enclosure and put both hard drives in that (though they all seem pretty expensive).
Any advice or information on what other people are doing, would be much appreciated.
Is there anything else to do or can I deploy a new stack with the following, that I have copied and modified from your post?
Code
# Note: 192.168.1.xxx is an example network, you must update all these to match your own.
# Thanks to http://tonylawrence.com/posts/unix/synology/free-your-synology-ports/ for your reference post
# More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/
version: "3"
services:
pihole:
container_name: pihole
image: pihole/pihole:latest
hostname: pihole
domainname: $URL # <-- Update on enviromen.env file
networks:
ph_network: # <-- MACVlan Name You need to create first in Portainer WebGUI.
ipv4_address: 192.168.1.69 # <-- Update to your desired Pihole IPv4
# https://www.youtube.com/watch?v=4741-YR31fM
# https://www.youtube.com/watch?v=o7nn6Tv-PAw
cap_add:
- NET_ADMIN # Recommended but not required (DHCP needs NET_ADMIN)
ports:
- "53:53/tcp"
- "53:53/udp"
- "67:67/udp" # Only required if you are using Pi-hole as your DHCP server
- "80:80/tcp"
environment:
ADMIN_EMAIL: $email
FTLCONF_LOCAL_IPV4: 192.168.1.69 # <-- Update (match ipv4_address of PiHole)
VIRTUAL_HOST: pihole.$URL # <-- Update (match hostname + domainname)
WEBPASSWORD: Password123 # <-- Add password (if required)
PIHOLE_DNS_: 1.1.1.1;1.0.0.1 # <-- Change by your prefered DNS service like 1.1.1.1
TZ: Europe/London # <-- Your Time Zone here
IPv6: "false"
# Volumes store your data between container upgrades
volumes:
- '/SSD/appdata/pihole:/etc/pihole'
- '/SSD/appdata/pihole/dnsmasq.d:/etc/dnsmasq.d'
# https://github.com/pi-hole/docker-pi-hole#note-on-capabilities
restart: unless-stopped
networks:
ph_network:
external: true
Thanks raulfg3 - I have had another look at your post and I am seriously confused.
I found setting up TVHeadend and Jellyfin quite easy on Docker but I am finding pihole has too many options and I really do not understand what I am doing.
Perhaps I should start from the absolute beginning and try to follow your guide again.
At the moment, my router deals with assigning ip addresses for all my devices, including my OMV server. They all have been assigned static ip addresses. My OMV server therefore has a static address of 192.168.1.68. My router's address is 192.168.1.254.
In OMV, I have network set to DHCP.
First question - as per the above, I need to change DHCP in OMV itself on the server.
Should I change to the following?
IPv4
Method - Static
Address - 192.168.1.68
netmask - 255.255.255.0
gateway - 192.168.1.254
IPv6
Method - disabled
What, if anything, should I add in respect of DNS?
Had another look and it seems that using PiHole as a DHCP server just complicates things - am happy to use the router for this.
I think the following should now work:
Code
version: "3"
# More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/
services:
pihole:
container_name: pihole
image: pihole/pihole:latest
# For DHCP it is recommended to remove these ports and instead add: network_mode: "host"
ports:
- "53:53/tcp"
- "53:53/udp"
- "8080:80/tcp" # Have done this so I do not have to change OMV's default port
environment:
TZ:Europe/London
WEBPASSWORD: 'Password123'
# Volumes store your data between container upgrades
volumes:
- /SSD/appdata/pihole:/etc/pihole
- /SSD/appdata/dnsmasq.d:/etc/dnsmasq.d #I understand that it is better practice than above
# https://github.com/pi-hole/docker-pi-hole#note-on-capabilities
restart: unless-stopped
Display More
This site uses cookies. By continuing to browse this site, you are agreeing to our use of cookies.More DetailsClose