I'm on a 10 year old Intel Xeon with ZFS and docker plugins. Used Zoki instructions in post #2 of this thread and am now on 7.4. Only had to touch the keyboard twice during the massive upgrade, and then reboot at the end. Everything seems solid. Very nice!
Posts by MiddleMan
-
-
I bought old used supermicro board (<$100) and used Xeon chip (<$30) and slapped into a cheapo server case. Unlike the waste of money on the Synology that failed me, this is way cheaper and has, to date, outlived it.
Only real money spent was on power supply (platinum certified), good fans, and the server grade Samsung ECC RAM was a steal (DDR4 was more expensive than DDR4 ECC at the time) The hard disks were a wash in any given case. After monitoring these threads for a while, my cost was lower than some fancily set up ARM-based option. It uses a little (and I mean a little) more energy than a Rasberry Pi v4 as measured with my Kill-A-Watt and takes up more space, but I didn't and still don't notice it on the energy bill and it's in a corner of the living space that's rarely accessed.
The fans are barely audible, except on boot-up (rare).
Offering this as food for thought.
Good idea to use pi as backup to primary. I hadn't considered this before, but the wheels are turning now. I have old 3 that is bored.
-
HGST (WD Gold) was my decision for new data drives in OMV. WD gives excellent support if you want (or in my case need) to switch them from 512e to 4Kn. I'm using ZFS and it matters in that case. From years past I have some 3 and 6 GB Black drives that are 7 years old and SMART reports them as healthy after many years of heavy use. I used 4TB Red NAS Plus and HGST in a Synology that I currently use for my OMV media drives. One out of 3 WD and 0 of 3 HGST has failed in 8 years. As reported by SMART, they are healthy and they have only been powered down due to blackouts or maintenance. In the research HGST used to win out hands down and thankfully, when WD bought them, they didn't change anything but the label. So, that 's how I wound up deciding on new (much larger capacity) data drives on my OMV. It has been running flawlessly for ~3 years thus far.
Toshiba, in my experience, make really good laptop drives, but those aren't NAS. Between 25 and 15 years ago (yup I'm aged), I used to love Seagate, but ultimately all but one failed between 3-5 years, so I continue to avoid them - and the Ironwolf does not have a good reputation (based on my research and feedback from local data warehouses).
To be honest I'm not a fanboy of any company, and just look at the research available, what I see posted online, inquire about what friends and co-workers are using and, ultimately make my decisions on those things. Some manufacturers stink in certain model variants, sizes, and even firmware releases. It all comes down to knowing your use-case (requirements) and doing a lot of homework and networking certainly doesn't hurt. Or roll the dice, and take your chances. There's a lot I don't have the experience to say about other manufacturers offerings, so I'm just sharing my experiences.
In any case, always, always, always, have a good back-up scheme that you trust, and don't forget to test it occasionally for the real event. Also ensure that you have the resources to replace failed hardware in a pinch. The more important the data, the more you'll spend because it is valuable, tangibly or emotionally.
-
Apologies in advance if this has been discussed and resolved. I put time into searching and looking though this section and did not find an answer.
I have a Windows 10 user on the network who can't access their home folder directly. It is all lower case, as is their username but selecting it gives them error "Windows cannot access".
However, they can reach their home folder in the same way by selecting homes and then their username.
I'm wondering if this is maybe related to samba, or could they be caching old credentials.
-
-
@Combatsatellite Glad you found a solution.
borg isn't easy. Too much nuance -IMHO. But when it works, it works.
Is this all because you're on port 23, or is that how you have your ssh server set up (telnet port)? Mine is all internal network and on default port 22.
-
I tried getting help on this earlier to backup local workstation to OMV, and never got resolution.
I wound up:
1) unistalling borgbackup from OMV
2) initialized a repo in my OMV @ /home/MiddleMan/borgbackups via ssh
3) run borg to backup workstation via script called by cron job originally, now via vorta. I attached some notes. Hope they help.
My ssh to /home/MiddleMan is via key; no password authentication allowed.
I suspect that OMV implementation is to backup OMV and/or data to another location. Not really sure.
-
Good info. I'll start monitoring. If it is due to security update, I'll just roll with the punches. Thanks!
-
Interesting. Thanks for the information ryecoaaron. I wasn't aware of that.
What happened to me a couple of days ago:
System updated dbus dbus-user-session isc-dhcp-client isc-dhcp-common libdbus-1-3 a few days ago, and OMV requested reboot.
After rebooting, I decided to update my VM (also Debian based) and noticed that I couldn't ssh in. I am in the webadmin panel for this VM every day, so I investigated. It turns out that KVM was not running because it was no longer installed.
So I reinstalled the plugin. Evidently, the VM dashboard was not enabled any longer either, so I asked my question, and you reminded me of the widget. I enabled the widget and back to business.
Still curious how kvm got uninstalled or disabled. But it falls to backup services, so not critical.
-
Understood. Thank you.
-
KVM disappeared after security updates were downloaded and installed today- ??? - I dunno why.
After reinstalling KVM plugin and starting the VM I have, I noticed that KVM is not listed in the services grid on the dashboard. I'm wondering if it should or if this is by design or limitation.
Thank you.
-
First time editing OMV environment variable - by hand at least...
I'm planning on editing /etc/default/openmediavault and adding the line as follows:OMV_SSL_CERTIFICATE_CHECK_EXPIRY_DAYS="15"Is it correct to put double quotes around the numerical valueOr better to run - THIS IS WHAT THE DOCS SAY TO DO:
# omv-env set -- OMV_SSL_CERTIFICATE_CHECK_EXPIRY_DAYS "15"
Then I run:
# monit restart omv-engined
# omv-salt stage run prepare
# omv-salt stage run deploy
This gives me a little buffer in case I have to go on a trip.
Thank you!
-
Awesome! Thank you.
-
I set up my OMV to use local certificate for SSL to OMV UI - default of 1 year lifetime. Notification (email) system is set up and tests successfully. OMV system is in use on local LAN only.
So, my question: Is there a way to configure OMV to notify me (in any way, but especially email) when the local certificate is getting close to expire so I don't run into access issues?
Thanks!
-
-
I deleted the original task 1) Because I set something up incorrectly with the original backup and decided to use dd instead of fsarvhiver. 2) because the interface allowed me to do it.
As a note, I'm using USB Backup to backup my shares to external USB and seems to be working flawlessly. My new manually run dd is saved to one of those shares, and then copied off to USB, as well.
I'll try reinstalling and report back.
Thank you for your time.
***Reinstalling openmediavualt-backup has fixed the issue.
-
ryecoaaron, I appreciate you being candid, and what you provide to this community. I think that I will disable that from the Workbench view and leave well enough alone. Thanks for your time and explanation.
-
Hi all,
I deleted scheduled backup job and created a new one. However, when I now browse to backup > schedule I get the following:
500 - Internal Server Error Failed to execute XPath query '//system/crontab/job[uuid='32664b22-5a9d-11ec-8834-6f00f75b23ee']'.
Thank you for any assistance.
-
-
Odd thing is that the drive is dedicated to backup using usb-backup plugin. Not sure why it's still mounted. Maybe I'll wipe, run a backup job on it, and then swap them out. I'll follow docs closely. Thanks for your time!