Thanks for the quick reply tkaiser.
Hello, I have a new OMV 4 installation on my Odroid C2
My syslog is filled with this looping every 10 seconds:
Any thoughts on why or how to stop it?
For information, I had the same problem with OMV_4_Odroid_C2.img.xz dated 2018-06-03
chmod 755 / seems to have fixed this.
Thanks once again for the work on OMV and supporting these little boxes.
I have a N54L with 4x3TB and a 4TB drive in the DVD bay. I use it for SnapRAID mainly.
I don't recall having to use any custom BIOS to boot from the DVD bay drive, just change BIOS boot order.
I used gparted to make a small partition on that drive for the OS - you can run the OS from the internal USB port on a thumb drive but not worth risking as all the re-writing will eventually kill it. The rest of the 4TB drive is for SnapRAID parity.
I got ECC ram for reasons tkaiser stated. I put a small USB3 card inside but I've never got it running reliably to be honest, I gave up trying to sort it as I rarely need to import/export via USB anyway, so USB2 will do.
I don't know much about RAID, but another way to pool two drives into one would be the union-filesystems plugin via omv-extras
- check the log files
- SD card is new-ish, but is it ok?
fsck and badblocks found nothing wrong with the card (plugged it into another system).
I couldn't find anything amongst the log files - it looks like some log files haven't been updated for a month, which is longer than I've had any problems with this box.
What is the main log file which would show a problem during boot?
Bumping once before I go for a reinstallation - any ideas welcome!
Do you mean install OMV from a USB or SD
install it to a USB or SD ?
Either is possible - use something like Etcher to write an installation ISO to USB/SD
If you mean installing it to a USB or SD, then the main thing is to turn on the flash memory plugin:
e.g. see omv on a SDHC card
This plugin is on by default for RaspPi and similar devices, but wouldn't be on by default in x86
My RaspPi had been running OMV 3.0.97 on Armbian just fine, but tonight is partly broken.
WebGUI loads but gives a 504 gateway timeout.
SSH gives immediate closed connection (can't enter my key's password).
I connected a monitor and keyboard, I note "failed to start LSB" for ProFtp daemon and same for nmbd and smbd
I think there was another failure message but it scrolled up too fast to read.
It says eth0 is up and I can ping it fine from my laptop.
Back to the login prompt on the monitor, when I enter a username it says "inconsistency detected by ld.so dl-version.c: 224"
and I can't log in as I'm not asked for the password. So can't run the firstaid script.
SD card is a new-ish Kingston, space on the system partition is plentiful. A few reboots with no change.
Any thoughts on the problem?
If I'm creating a new folder (e.g. in media or srv) I always do it in the webGUI under 'shared folders', then adjust permissions if needed.
I use mc over SSH a bit and making subfolders is fine but making top level folders in media or srv leads to the sort of problems you described.
Had some tweaking to get this running as intended this seems to do it:
This rsyncs anything from the last 14 days, based on checksum differences.
Aha, that seems to do the trick:
So for the record, the only other thing I did was run this on BoxA:
ssh-keygen -e -f new-rsync-key
...to export my public key in the right format. I copied the output of that to the keys tab of UserMe in the users section on BoxB in the webui, where it sits alongside UserMe's proper password-protected SSH key.
So far so good! Thanks subzero79!
Thanks for the reply!Quote
The userme is trying to write to rootfs folder /backupfolder
Sorry, that was an oversimplification on my part. The target part is more like userme@targetip:/srv/123456789etc/backupfolder - and permissions are OK for userme
SSH works fine, I'm using putty regularly with pka on all my OMV boxes.
What I'm trying to do is allow unattended rsyncs by using a new key without a password, e.g. using this guide.
I created a new keypair on BoxA and added the new pubkey to userme on BoxB via the GUI, but I get the same result as above.
Should I create a new 'rsync' user with their own key so the target part is userrsync@targetip:/srv/123456789etc/backupfolder
and then adjust permissions accordingly?
Hello all, can anyone help an rsync newbie?
I have two OMV machines (call them BoxA and BoxB), both on my home network.
I need to rsync one folder from BoxA to BoxB using the command line, because I want to rsync only items from the last X days:
I've generated a new ssh key pair (without a password) on BoxA with ssh-keygen, then put the contents of the public key file in userme/.ssh/authoried_keys on BoxB
Then on BoxA, from ssh as [username] I tried:
But I got this error:
Any pointers welcome!
Fix provided by Igor here:
It worked for me. I wrote OMV to another SD card, booted in that, created a user for SSH, then followed Igor's instructions above.
I also tried the update to u-boot 5.40 in my quick reinstall, via the main OMV webui update procedure, and that was fine too.
Better ask in Armbian forum. It's important that certain persons there are aware that Armbian's 'update policy' is somewhat problematic
OK have done so. Will update here if I get anywhere. Thanks again.
In case you installed some updates within the last week please look here: https://forum.armbian.com/topi…-with-u-boot-default-538/
Thanks tkaiser, that would explain it, I updated most things yesterday through OMV webui update.
So is there any way to revert this problem? I can edit the SD contents on another linux system.
I have an OdroidC2 which has been running OMV3 happily for months. Now it won't boot at all.
I plugged the HDMI into the TV - nothing. However, it's fine with a fresh OMV install on another micro SD card. So the C2 itself is fine.
So what can I try to see if I can resurrect the old installation? gparted suggests the partitions are OK. No problems at all until today.
Thanks, that's helpful although so far I can only get it to work with authentication turned off.
It would be good to have this work with public key authentication but I'll keep working on it.
Thank you, looks like rsync is the one to get my head around.