Still getting errors. I'm thinking a fresh install might help, maybe just to eliminate any clone info that might be causing problems. Should I consider OMV5 instead of OMV6? The hardware isn't "new" but it's definitely not old. Lenovo mini form factor, Intel 3GHz. 4G RAM.
Posts by ramack
-
-
Did you check/tick the "fstab" option when you created the remote mount? It looks like it's optional in the plugin UI but I don't think it is . I don't know why you are seeing those time zone errors.
Yes, I checked the box with similar/same results.
No, I was using smb/cifs. NFS makes sense now that you point it out. But would that affect mounting?
-
Hi,
Relatively new OMV6 install (cloned from a HDD to SDD). I'm trying to remote mount a Zyxel NAS326 in OMV6, but have having errors when applying the change. I've tried several iterations that have succeeded for others, but not working for me. (Options/ver 3 to 2, rebooting, refreshing etc). Could this possibly be a result of cloning my original install from a HDD to a SSD and the UUID is wrong?
After applying changing I get a big red box pop-up, only including the false ID.
Code
Display MoreFailed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color remotemount 2>&1' with exit code '1': debian: ID: restart_N326_remotemount Function: cmd.run Name: systemctl restart 'srv-dce5f521\x2de7e1\x2d4663\x2d9e1d\x2db228d4b24858.mount' Result: False Comment: Command "systemctl restart 'srv-dce5f521\x2de7e1\x2d4663\x2d9e1d\x2db228d4b24858.mount'" run Started: 17:36:03.275958 Duration: 22.988 ms Changes: ---------- pid: 43412 retcode: 1 stderr: Job failed. See "journalctl -xe" for details. stdout:Output of journalctl -xe
Code
Display Moresudo journalctl -xe [sudo] password for Rich: Oct 24 17:36:32 openmediavault kernel: input: PixArt HP USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2:1.0/0003:03F0:604A.0065/input/input112 Oct 24 17:36:32 openmediavault kernel: hid-generic 0003:03F0:604A.0065: input,hidraw2: USB HID v1.11 Mouse [PixArt HP USB Optical Mouse] on usb-0000:00:1d.0-2/inpu> Oct 24 17:36:33 openmediavault php[42924]: Unknown or deprecated time zone [tz=]. Please reconfigure your time zone settings. Oct 24 17:36:33 openmediavault omv-engined[43745]: Unknown or deprecated time zone [tz=]. Please reconfigure your time zone settings. Oct 24 17:36:39 openmediavault php[42924]: Unknown or deprecated time zone [tz=]. Please reconfigure your time zone settings. Oct 24 17:36:39 openmediavault omv-engined[43752]: Unknown or deprecated time zone [tz=]. Please reconfigure your time zone settings. Oct 24 17:36:45 openmediavault php[42924]: Unknown or deprecated time zone [tz=]. Please reconfigure your time zone settings. Oct 24 17:36:45 openmediavault omv-engined[43759]: Unknown or deprecated time zone [tz=]. Please reconfigure your time zone settings. Oct 24 17:36:50 openmediavault autoshutdown[609]: root: INFO: 'main(): ------------------------------------------------------' Oct 24 17:36:50 openmediavault autoshutdown[609]: root: INFO: 'main(): New supervision cycle started, checking system activity' Oct 24 17:36:51 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): Retrieve list of active IPs for: enp0s25' Oct 24 17:36:51 openmediavault php[42924]: Unknown or deprecated time zone [tz=]. Please reconfigure your time zone settings. Oct 24 17:36:51 openmediavault omv-engined[43821]: Unknown or deprecated time zone [tz=]. Please reconfigure your time zone settings. Oct 24 17:36:56 openmediavault sudo[31360]: pam_unix(sudo:session): session closed for user root Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.3 is active' Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.5 is active' Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.7 is active' Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.8 is active' Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.10 is active' Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.20 is active' Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.22 is active' Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.24 is active' Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.39 is active' Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.47 is active' Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.48 is active' Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.54 is active' Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.70 is active' Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.72 is active' Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.73 is active' Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.74 is active' Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.202 is active' Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): Active IPs found in the specified range -> no shutdown' Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: 'main(): Active check failed, 1 cycles until shutdown ...' Oct 24 17:36:57 openmediavault autoshutdown[609]: root: INFO: 'main(): Sleep for 20s' Oct 24 17:36:58 openmediavault php[42924]: Unknown or deprecated time zone [tz=]. Please reconfigure your time zone settings. Oct 24 17:36:58 openmediavault omv-engined[43935]: Unknown or deprecated time zone [tz=]. Please reconfigure your time zone settings. Oct 24 17:37:04 openmediavault php[42924]: Unknown or deprecated time zone [tz=]. Please reconfigure your time zone settings. Oct 24 17:37:04 openmediavault omv-engined[43943]: Unknown or deprecated time zone [tz=]. Please reconfigure your time zone settings. Oct 24 17:37:06 openmediavault sudo[43942]: Rich : TTY=pts/0 ; PWD=/ ; USER=root ; COMMAND=/usr/bin/journalctl -xe Oct 24 17:37:06 openmediavault sudo[43942]: pam_unix(sudo:session): session opened for user root(uid=0) by Rich(uid=1002)Codesudo blkid /dev/sdb1: UUID="b19d92a6-e2e0-4b5f-8a73-772915a100a1" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="b2aff62a-cf62-4adc-946c-bfbdec0a3361" /dev/sda1: UUID="071ed228-4729-40a6-9843-5dd0249af839" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="d6df43fd-01"Any ideas? Thanks.
-
ramack Not sure I follow the logic of your 2nd para. The choice seems to be (A) rsync desktop to zyxel NAS, then rsync zyxel to OMV, or (B) rsync desktop to zyxel NAS, then rsync desktop to OMV. Why does OMV install become redundant?
Going by the A or B options you've outlined, I am wanting A. Since in addition to my Debian desktop, I also backup other Windows PCs to the NAS326(RAID 1). I'm wanting to use OMV as a backup target for the NAS326, maybe run that backup 2-3 times/month.
I wouldn't say OMV would become redundant (although it backing up the NAS326 is a redundant backup and a good thing data wise), but running a rsync CRON job from my desktop to backup the NAS326 to OMV didn't seem like a good use of resources and isn't using the power of OMV. -
Don't use the admin user. Use a normal user created in the GUI of OMV.
Is this a ssh connection? Or via smb or something else?
In Zyxel I had been using admin as user only because when trying the rsync option (before the OP) by default Zyxel uses admin. The other backup options allowed different user names. I tried different users just to see if it made any difference (it did not) and the screenshot included in the first post had admin as user. After reading the OMV howto that CrashTest pointed to and how it's highly recommended to implement a regular user with read access (not R/W) that make a lot of sense to prevent over writing.
My daily desktop is Debian Bullseye and I use rsync to backup my desktop to the NAS326 and had considered just creating a CRON job to rsync the NAS326 to OMV, but that really defeats the OMV install. So I'm trying to make the most of both NASs. Otherwise I might as well replace the OMV install with a Debian server install.Last night I did try mounting the NAS326 to OMV, but had mount errors that I'll troubleshoot this afternoon.
As far as SSH or smb is what Zyxel uses? I don't know, I haven't been able to find any logs.
-
Great idea, love it! I'll check out the plugin. Thank you.
-
This is probably more of a Zyxel question than OMV, but Zyxel support is somewhat lacking.
As the subject states, I'm setting up OMV(1x 4TB) for the target of a backup job for a new Zyxel NAS326 2x 4TB RAID 1. The NAS326 is the target for frequent backup jobs for PCs on my home network.
OMV Host Name - OpenMediaVault
Shared Folders - OMVShared
The issue is I can't complete the connection in creating a backup job from the NAS326 to OMV without error. The OMV and NAS326 are visible from devices on the network, credentials are correct etc.
In the field for Share Name I've tried OMV host name and the Shared Folder name.
Any ideas what I'm doing wrong?
-
I ran GParted Live and poked around. The boot flags were set to "boot". I changed that to eif_boot(I think that was the flag) and rebooted. Boot and access to OMV now "appears" to be working.
I'm marking this issue [SOLVED] for now since I think I've found the solution [hopefully, ha].
-
I did another install, but instead of from a USB, I burned the .iso to a DVD. This gets a little further. I now get the typical boot splash screen, followed by the errors above.
-
Hi,
I'm new to OMV, I had it initially setup on a 1TB Hitachi HDD, but not fully up and running when I decided to scavenge the HDD from my unsupported out of warranty Western Digital MyCould NAS. As far as I can tell, the OMV install is not producing any errors, the more I'm digging into this, I think it's due to the recycling of the WD Red 4TB NAS drive and trying to install OMV on that drive.
Once I removed the HHD from the MyCloud enclosure, using GParted, I deleted all partitions and re-partitioned to one ext4 partition. Then I installed OMV 6 from a USB thumb drive. When the install was completed, I rebooted the machine Lenovo 64bit Intel 3Ghz CPU.
when it's coming out of BIOS I get
error: file '/grub/i386-pc/normal.mod' not found.
grub rescue>
Like I stated above, I don't think this is an OMV issue, I think it's more "basic" than that and I'm going after grub problems and solutions. So far I haven't found one yet.
Anyone have any ideas?
Thanks,