jimandroidpc
-
Posts
36 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by jimandroidpc
-
-
Thanks for posting the link.
@fredall here is the link i used before to fix my fans. im gonna try get working and then freeze updates.
https://forum.armbian.com/topic/44379-fancontrol-bookworm-solved/
Let me know if it works for you.
-
I need this also to install OMV.
-
22 hours ago, gprovost said:
@pekkal @taziden Yes could be a failing PSU. Unfortunately some PSU are using a brand of capacitor that doesn't fulfill their advertise MTBF :-/
So better you check with a voltmeter you still get 12V between the (+) and (-) pins.
@jimandroidpc What kind of crash you are referring ? after OMV update can you SSH in or use serial console ? It seems your issue is a failing OMV upgrade, something not related to hardware. Is it an just update or an upgrade (OMV4 to OMV5) you are doing ?
Fixed with this -- https://forum.openmediavault.org/index.php?thread/31630-solved-omv-accepts-login-but-brings-me-back-to-the-login-screen/
as much as Id like it to be OMV isnt really production ready software with errors like these.
-
Yea this ia the 2nd time ive ran an update on OMV and had crashes and now i cant login to the weblogin even after trying to reset pw etc.
Sent from my LM-G710 using Tapatalk -
Will the helios64 be the future for kobol? Do you expect any more helios4 board runs?
Sent from my LM-G710 using Tapatalk -
So no ECC?
Sent from my LM-G710 using Tapatalk -
From my syslogI originally posted this on the OMV forums but got no replies as I figured it was more likely related the their software.
Anyway
I updated my Helios4 w/ OMV4.x overnight and then was getting this message
"Invalid RPC response. Please check the syslog for more information."
Error #0: OMV\Rpc\Exception: Invalid RPC response. Please check the syslog for more information. in /usr/share/php/openmediavault/rpc/rpc.inc:186 Stack trace: #0 /usr/share/php/openmediavault/rpc/proxy/json.inc(97): OMV\Rpc\Rpc::call('LuksMgmt', 'openContainer', Array, Array, 3) #1 /var/www/openmediavault/rpc.php(45): OMV\Rpc\Proxy\Json->handle() #2 {main}
Found a few other threads with simiular but different errors - I ran
"dpkg -l | grep openm"
The output was...
root@helios4:~# dpkg -l | grep openm
ii openmediavault 4.1.30-1 all openmediavault - The open network attached storage solution
ii openmediavault-flashmemory 4.2.1 all folder2ram plugin for OpenMediaVault
ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive
ii openmediavault-luksencryption 3.0.5 all OpenMediaVault LUKS encryption plugin
ii openmediavault-lvm2 4.0.7-1 all OpenMediaVault Logical Volume Manager (LVM2) plugin
ii openmediavault-netatalk 4.0.7-1 all OpenMediaVault netatalk (AppleTalk Protocol Suite) plugin
ii openmediavault-nut 4.0.13-1 all OpenMediaVault Network UPS Tools (NUT) plugin
ii openmediavault-omvextrasorg 4.1.16 all OMV-Extras.org Package Repositories for OpenMediaVault
ii openmediavault-rsnapshot 4.2.1 all OpenMediaVault rsnapshot backup plugin.
Any ideas on how to handle this? Ive had a few issues with updates running periodically on omv on my helios4 and dont to have to redo OMV again if there is a simple fix. As of right now I cant mount any of my drives.
Thanks
Sent from my LM-G710 using Tapatalk
Dec 30 11:34:22 localhost omv-engined[22219]: PHP Fatal error: Uncaught TypeError: Argument 2 passed to array_keys_exists() must be of the type array, null given, called in /usr/share/php/openmediavault/system/filesystem/backend/manager.inc on line 284 and defined in /usr/share/php/openmediavault/functions.inc:140#012Stack trace:#012#0 /usr/share/php/openmediavault/system/filesystem/backend/manager.inc(284): array_keys_exists(Array, NULL)#012#1 /usr/share/php/openmediavault/system/filesystem/backend/manager.inc(130): OMV\System\Filesystem\Backend\Manager->enumerate()#012#2 /usr/share/php/openmediavault/system/filesystem/filesystem.inc(855): OMV\System\Filesystem\Backend\Manager->getBackendById('/dev/mapper/sda...')#012#3 /usr/share/openmediavault/engined/rpc/fstab.inc(178): OMV\System\Filesystem\Filesystem::getImpl('/dev/mapper/sda...')#012#4 [internal function]: OMVRpcServiceFsTab->getByFsName(Array, Array)#012#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)#012#6 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod in /usr/share/php/openmediavault/functions.inc on line 140
Sent from my LM-G710 using Tapatalk
-
I originally posted this on the OMV forums but got no replies as I figured it was more likely related the their software.
Anyway
I updated my Helios4 w/ OMV4.x overnight and then was getting this message
"Invalid RPC response. Please check the syslog for more information."
Error #0: OMV\Rpc\Exception: Invalid RPC response. Please check the syslog for more information. in /usr/share/php/openmediavault/rpc/rpc.inc:186 Stack trace: #0 /usr/share/php/openmediavault/rpc/proxy/json.inc(97): OMV\Rpc\Rpc::call('LuksMgmt', 'openContainer', Array, Array, 3) #1 /var/www/openmediavault/rpc.php(45): OMV\Rpc\Proxy\Json->handle() #2 {main}
Found a few other threads with simiular but different errors - I ran
"dpkg -l | grep openm"
The output was...
root@helios4:~# dpkg -l | grep openm
ii openmediavault 4.1.30-1 all openmediavault - The open network attached storage solution
ii openmediavault-flashmemory 4.2.1 all folder2ram plugin for OpenMediaVault
ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive
ii openmediavault-luksencryption 3.0.5 all OpenMediaVault LUKS encryption plugin
ii openmediavault-lvm2 4.0.7-1 all OpenMediaVault Logical Volume Manager (LVM2) plugin
ii openmediavault-netatalk 4.0.7-1 all OpenMediaVault netatalk (AppleTalk Protocol Suite) plugin
ii openmediavault-nut 4.0.13-1 all OpenMediaVault Network UPS Tools (NUT) plugin
ii openmediavault-omvextrasorg 4.1.16 all OMV-Extras.org Package Repositories for OpenMediaVault
ii openmediavault-rsnapshot 4.2.1 all OpenMediaVault rsnapshot backup plugin.
Any ideas on how to handle this? Ive had a few issues with updates running periodically on omv on my helios4 and dont to have to redo OMV again if there is a simple fix. As of right now I cant mount any of my drives.
Thanks
Sent from my LM-G710 using Tapatalk -
ECC RAM?
Sent from my LM-G710 using Tapatalk -
Impressive! Same form factor as the helios4? Can we use our excisting power supply and case?
Sent from my LM-G710 using Tapatalk -
Is the CPU cache also ECC ? Does that matter either way in this device?
Sent from my LM-G710 using Tapatalk -
My OMV was updated & running fine. doing rsnapshots from 1 drive to another. just started getting this error after the last update. Any ideas?
-
Would this be working for the lemaker banana pi or pro? I can test next week.
Sent from my LM-G710 using Tapatalk -
15 hours ago, gprovost said:
@jimandroidpc I tested again the patch and it works. Patch it's for OMV4, didn't tested on OMV3 or 5.
sudo patch < helios4-omv-luks.patch /usr/share/php/openmediavault/system/storage/luks/container.inc patching file /usr/share/php/openmediavault/system/storage/luks/container.incThe maintainer of openmediavault-luksencryption plugin hasn't yet did the modification, so you still need to use the patch.
If you can't use the patch, just open the patch file and look at the two +/- lines, you will see it's pretty straight forward, so you can manually modify the code.
@gprovost I manually made the change and confirmed the encryption. Now transfer speeds are 75-80MB/sec up/down compared to 50-55 on XTS.
-
-
Happened on the latest version of OMV for the Libre Renegade - this " systemctl stop serial-getty@ttyS2.service" stopped it.. for now.
-
Just now, gprovost said:
I just told you what the patch does, so you should be able to figure if the target file was modified or not.
If you are unsure then better wait the next OMV LUKS plugin upgrade, hopefully this new feature might be added by then.
I checked a new encryption and it still says XTS - so from what i can tell its not applied. I may just wait, thanks for looking into it - if I can help id be happy to but im learning as I go
-
3 minutes ago, gprovost said:
@jimandroidpc Well does the patch get applied ? the patch just modifies 2 lines in /usr/share/php/openmediavault/system/storage/luks/container.inc to add -c aes-cbc-essiv:sha256 to the crypsetup luksFormat command.
Anyhow I just rise a change request on the OMV LUKS plugin and it seems the maintainer is going to make the improvement since this change could benefit many ARM SoC based board : https://forum.openmediavault.org/index.php/Thread/11592-LUKS-disk-encryption-plugin/?postID=198390#post198390
@fpabernard Well hopefully one day there will be a refresh revision of Helios4.
I cant tell if its applied or not
-
21 hours ago, gprovost said:
@jimandroidpc I attached a dirty patch to hard code the right cipher in OMV LUKS plug-in. So when you create an encrypted device under OMV it will use the right cipher : aes-cbc-essiv:sha256
It's far to be the ideal way, we should actually request to the developer of the OMV LUKS plug-in to add the possibility for user to choose the cipher.
To apply the patch
sudo patch -d/ -p0 < helios4-omv-luks.patch
not working for me.. still used the XTS default in OMV - did I need to modify the file or command at all? I had it copied on a usb drive I mounted.
-
Adapted from another thread by tkaiser, this fixed it. has to do with ttys0 -> ttys2
Source Code
echo ':msg, contains, "Serial Getty on ttyS2" ~' >>/etc/rsyslog.d/omv-armbian.conf
echo ':msg, contains, "Service hold-off time over" ~' >>/etc/rsyslog.d/omv-armbian.conf
Then reboot. Or search for the service and disable it.
-
Armbianmonitor:
Mar 9 12:31:24 renegade liblogging-stdlog: [origin software="rsyslogd" swVersion="8.24.0" x-pid="1209" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Mar 9 12:31:28 renegade systemd[1]: Stopped Serial Getty on ttyS2.
Mar 9 12:31:28 renegade systemd[1]: Started Serial Getty on ttyS2.
Mar 9 12:31:38 renegade systemd[1]: Stopped Serial Getty on ttyS2.
Mar 9 12:31:38 renegade systemd[1]: Started Serial Getty on ttyS2.
Getting the bootloop serial getty message on my Libre Renegade OMV4. Logs enclosed. I tried some of the fixes I saw on other threads but to no avail. Those looked like they were for diff devices, but may be CPU specific?
Any ideas?
-
18 hours ago, gprovost said:
@jimandroidpc Please refer to this thread where quite a bunch of benchmarking numbers and important remarks were shared : https://forum.armbian.com/topic/8486-helios4-cryptographic-engines-and-security-accelerator-cesa-benchmarking/
Did you used the right cipher : aes-cbc-essiv:sha256 ? Other cipher won't be accelerated by the CESA engine.
Anyway I encourage to follow up on the thread I shared.
No, I didnt use the CBC cipher - I was using OMV image with the XTS. Is there a way to make OMV use the other cipher?
-
Running benchmarks on my drive, HGST 2tb 7200rpm OMV with LUKS set up - Default Encryption (XTS), BTRFS, EXT4, XFS
Copying a 30gb file over SMB, I average around 50-55MB/sec to and from the Helios4 from my windows10 desktop NVME system drive. Is everyone else getting similar speed? I expected transfer speed to be a bit higher, but I understand XTS may be slowing this down...
-
What file systems are you all running? Btrfs/zfs? Encryption? Does it max out a 1gbit Ethernet on file transfers?
Sent from my ZTE A2017U using Tapatalk
Anyone have any output from a wattmeter on power usage?
Bullseye Armbian image
in Helios 4
Posted
Installed thew newest bullseye image then omv then updated and it woulsnt boot. My plan is to freeze updates since its a firewalled NAS. Fan works fine on the base install