What do you see on the dashboard? See the cpu-temp widget?
That's correct, the CPU temp widget doesn't report correctly on my setup. But I haven't had to fool with them in the past - they just show up and work. I'll investigate over the weekend time permitting.
The guide doesn't have specific instructions for every board. So, what change did you make? What is the output of: sensors
tried to follow the guide step by step. but it was unable to ever execute cpu-temp to get the reading. unsure why. Was thinking maybe the directories on my install are different or something and it was a low priority for me so I didn't look further.
I can take another crack at it if you want.
Where are you looking at the temperature? If you are seeing the wrong temp in the cputemp widget, then that just means the default zone it reports from is not the correct zone. This thread explains how to customize it - Guide - Custom cpu temp script for openmediavault-cputemp plugin
followed instructions but I'm not getting the cpu-temp program to run for some reason. I'll mess around with it, for not I just pulled it off the dashboard.
great, thanks !! i'll give that a try.
Where are you looking at the temperature? If you are seeing the wrong temp in the cputemp widget, then that just means the default zone it reports from is not the correct zone. This thread explains how to customize it - Guide - Custom cpu temp script for openmediavault-cputemp plugin
The CPU temperature misreports, or I'm reading it sideways.. just a heads up!
It reports my CPU as -273.3 celcius
Homebridge which runs in docker reports correctly at 41 degrees C
If you did the scripted OMV install, after installing Debian, OMV-Extras is automatically installed by the script.
__________________________________
I have no doubt that performance is better.
Just curious, did you do a price comparison? An R-PI5, 8GB, with a case, a power supply and other bits and pieces can add up. No to mention that you doubled the R-PI5's max RAM and you got a good sized SSD in the bargain.
if you haven't played with mini-ITX yet - it really is a fun and configurable as a Pi - and surprisingly affordable.
If you did the scripted OMV install, after installing Debian, OMV-Extras is automatically installed by the script.
__________________________________
I have no doubt that performance is better.
Just curious, did you do a price comparison? An R-PI5, 8GB, with a case, a power supply and other bits and pieces can add up. No to mention that you doubled the R-PI5's max RAM and you got a good sized SSD in the bargain.
i did some research ahead of time and found a youtube video comparing a similar setup in price, electricity usage and performance of the Pi5 vs one of these little setups. For me the 2.5 gb ethernet and onboard nvme were the big deals.
as far as omv-extras installs - that's what I was trying to say. Followed process from that page and used their script.
Just a post to the group that i received my intel M100 puck - a BosGame MiniPC with 16GB, and 512SSD. Ripped out the 512SSD and put in a faster 2TB SSD (sufficient for my needs). Big deal for me on this puck was the onboard SSD and 2.5GB ethernet port - which my PI4 rig never approached having.
I'm not a linux guy so honestly it took me 2 or 3 builds to get the partitioning right, lol - but i left 128GB for OMV (7) to use and used the remaining 1.8TB partition for storage. I put my Compose, Data and DockerBackup folders on that partition along with a shared folder for time machine backups.
Composed Homebridge and Home Assistant into containers and fired them up. Restored my backups of each.
I followed the guide to set up OMV Extras for setup after a base install of Debian. Everything is working very well - and I'm getting more then 2x the throughput i had with my PI. If anyone is looking at PI5 - you should look at the M100 as well. For me, it's a better solution.
I'm going to order a Raspi 5 in the next few days - waiting on a good SSD hat or Argon40 to get stuff out. At that point I'll rebuild OMV. is there anything in particular that might be useful for me to look for or report back to the development team? Happy to pass anything up that might help.
Alles anzeigenThe issue has been resolved but implementing the fix has taken another route:
In the interim, after booting into Raspberry OS, Bookworm 64bit Lite:
Run the following in an SSH session;sudo apt-get update
sudo apt-get upgrade -y
# Run the following preinstall scriptwget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/preinstall | sudo bash
sudo reboot
# Run the following install script
wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/install | sudo bash
There will be an automated reboot at the end of the script, then log into the GUI.
not sure if this was your intent - but i was in fudging around anyway - so I ran the above process. may have made zero difference as my install was already working well - but I can report everything is STILL working after script(s) if that is helpful information.. It did state that it updated many modules. On first glance my CPU utilization and temperature are trending a little lower than what i have been observing previously. I also observed it adding ETH0 to the database - which I don't recall seeing previously. I'm assuming this is the fix. So. Fix is good!
What is your application - meaning what are you going to use OMV for? Most of my geek friends use TrueNAS - but i wanted something the size of a hockey puck - so I went the PI route. For 6 months or so I just ran homebridge / home assistant natively in the PIOS and set up time machine shares (my only other application of device) manually with Samba - I could do it but it was a pain in the ass.
So I started reading up on NAS options and came across many comparing OMV and TrueNAS - one thing that was clear, TrueNAS had higher system requirements and a heavier footprint than OMV. I hadn't used Docker before - I'm a MacOS and Windows expert - i just play in Linux. But i was so pleased on my first experience with OMV6 that I stopped looking. It makes so many manual tasks web driven, and has a nice platform of plugins and docker. Now i don't have to choose between home assistant and homebridge, i run them both and use the plugin i prefer on either platform. And my secondary goal of one small box to back up all the Macs is perfectly suited to the M.2 media i have attached.
You may now see why I ask your application. Mine is very basic in nature. I don't RAID. I don't back it up. I use it more as an appliance.
Wondering why you are questioning me? Here, during the setup process, my macOS device is perfectly happy to set up the omv-smb-share-timemachine target, but it does not offer the option to set the max size. Honest!
Hey Jack. I use time machine backups and though i have migrated an old backup volume thru several OMV installs (so I don't see the option to change size, it's not a new backup) i do remember getting the prompt with OMV6. (From MacOS Settings). I don't know if it makes any difference but i enforce SMB3 in my SMB/CIFS settings - MacOS prefers SMB3 and requires SMB2 - i think from my reading. attached is a screenshot of my settings if that helps - works here?
hope that helps!
Alles anzeigenNote that this is for an OMV7 install on an R-PI4 (possibly others) that brick the install, when changing network settings.
(For ref: The interface name on this R-PI was end0 ) :
Until this issue is addressed by the install, I found a temporary fix.
At the location:
/etc/systemd/network/I created the file 10-persistent-net.link
#With the following contents:
[Match]
MACAddress=dc:a6:32:57:17:77 #Insert the Mac address for your wired interface here
[Link]
Name=eth0
________________________________________________________________________
This came from Debian's document, -> Network Interface Names where they address various interface naming schemes.
if ya'll care to close the loop - after following the help on this thread - I've had no further issues. I have applied updates as they have come in and run a couple of containers for iOT stuff - no issues here.
What is the output of ip addr? Is it possible that the system was previously configured via eth0? OMV added support for DSA network interfaces (e.g. this end0) some times ago.
no it appears that the default PIOS starts with end0 and somewhere along the way OMV uses eth0. Maybe PI is being weird because i have never seen end0
lucid3ye - I know you know what you are doing but have you checked the name assigned to your ethernet in the GUI (network > Interfaces) vs looking at the diagnotic report (diagnostics > report).
I have found that there is a difference in the name (eth0 vs. end0) and this will cause issues when setting up services that rely on the network.
The fix is easy if this is the case and you need to do this before configuring anything else. Just delete incorrect interface from GUI. Don't apply changes. Add correct interface name. Save. Apply.
winner winner - chicken dinner. Issues resolved and thank you.
Alles anzeigenA couple things:
First, with the following comment:I was not addressing you, lucid3ye.
You have a different set of circumstances, that does not include "raspi-config", so I don't know why or where the snark is coming from. But I will say this; it's not helpful when forum users inject themselves into the middle of a direct conversation with a specific user, with quotes and comments that don't apply and snark added as garnish. Problems are not dealt with by "piling on". They're solved one-at-a-time.
In any case, I did the test run and found what appears to be a systemd network issue.Having cut my computing teeth on a Commodore 64 and DOS 1.X, 2.X, etc., I seriously doubt that you were building systems when I was in diapers. In my diaper days, "a computer" might have been crossing over from tubes to some of the very first, experimental, TTL circuity. Building a system at that time would have taken the equivalent of a tractor trailer van full of equipment, DARPA PhD's (ARPA at that time), a ton of money and resources.
Further, having been retired for a bit over 13 years now, it's possible that I may be older than you are.You followed an install guide for OMV 6.0, to install OMV7 RC1. Had you followed the install for OMV 6.0, as it was written, OMV6 would have installed flawlessly. (Absent hardware problems and user induced mystery issues.) OMV7? Obviously, there are no guarantees. At the moment, I'm working on the OMV7 install guide for AMD64 ISO - one thing at a time.
With the above noted, if you think you can write a guide for installing OMV7 on R-PI's that's succinct, not confusing for beginners, that will support broadest cross section of users (beginners and enthusiasts alike), and you're willing to support it, please feel free. I'll even publish it on the Wiki for you, so you won't have to go through the Markdown and HTLM learning curves.
You see, the support angle comes with trying to figure out hardware issues, build problems, and how users go off the beaten path. The latter, not following instructions or deviating without admitting it, is easily where +60% of installation issues come from and it's where a LOT of forum time is wasted. (As forum contributors look into the "crystal ball" of their expertise, experience and intuition trying to figure issues out, remotely.)
___________________________________________________________________________
Reading through your posts, it appeared that you might have a DNS issue which might indicate a problem with your local router, the router's configuration or your DCHP server, if it's separate from the router. (This is what I was talking about when saying you have a different set of circumstances.)
Local hostname lookups have very little to do with your R-PI (assuming it's not being used as a DNS or DHCP server). If you have local DNS, you could misname the R-PI's hostname and it's domain suffix, in OMV, and it wouldn't matter.
You can setup a crude form of local DNS by:
1. Setting up static DHCP leases for the IP address(es) of your server(s) which should include their hostname(s).
2. In my setup, I statically address my OMV servers with the same IP address used for their static DHCP leases.
(While optional, static server addressing eliminates a server's reliance on network connections and an external, DHCP, process.)
When clients do a hostname lookup, the local Router/DCHP Server acts as a local DNS and returns an IP address. This has worked well for me. It might work for you.
it actually sounds like we cut our teeth on the same equipment and same OSes, lol. Again sorry for being snarky.
Problem is resolved.. turned out to be the eth0 / end0 named in another comment. Everything is running swimmingly now.
lucid3ye - I know you know what you are doing but have you checked the name assigned to your ethernet in the GUI (network > Interfaces) vs looking at the diagnotic report (diagnostics > report).
I have found that there is a difference in the name (eth0 vs. end0) and this will cause issues when setting up services that rely on the network.
The fix is easy if this is the case and you need to do this before configuring anything else. Just delete incorrect interface from GUI. Don't apply changes. Add correct interface name. Save. Apply.
This sir is the problem. Many Thanks - going to attempt your fix. I noticed on dashboard end0 is grabbing and IP while when i look under network settings its using eth0 which doesn't exist. Couldn't get this to change - your process above i will try!
pleased to report that with time everything just seemed to start working as i stuck with it and configured. I'm not sure if there is some issue on my network - but i don't think that was the issue as the host would simply stop responding - all that being said. It seems like when you initially enable SMB/CIFS something happens that makes the hostname temporarily unresponsive. If you continue using the IP address - eventually the system resolves to the hostname again via all protocols.
also - while I'm an expert at networking and hardware - linux - i am no expert. I'm learning. So all of the help in the forum was appreciated. It forced me to try some different things i wasn't thinking through. For instance, when hostname stopped responding reverting to IP. That's a no-brainer I should have done, lol.
lucid3ye - I know you know what you are doing but have you checked the name assigned to your ethernet in the GUI (network > Interfaces) vs looking at the diagnotic report (diagnostics > report).
I have found that there is a difference in the name (eth0 vs. end0) and this will cause issues when setting up services that rely on the network.
The fix is easy if this is the case and you need to do this before configuring anything else. Just delete incorrect interface from GUI. Don't apply changes. Add correct interface name. Save. Apply.
pleased to report that with time everything just seemed to start working as i stuck with it and configured. I'm not sure if there is some issue on my network - but i don't think that was the issue as the host would simply stop responding - all that being said. It seems like when you initially enable SMB/CIFS something happens that makes the hostname temporarily unresponsive. If you continue using the IP address - eventually the system resolves to the hostname again via all protocols.
to update this thread - i continued to configure using IP address. Once I had my Homebridge up - it seemed to push out the hostname for whatever reason, and magically hostname started working everywhere.
currently I'm backing up via Timemachine to shared folder - and homebridge is up and running with a plugin acting up that I don't blame on OMV7.
Thanks for the help. I hope that the information I provided was helpful to someone.
