The drives are unlocked and mounted.
Where do you see an password error?
You mean pulling your Plugin and the compile it?
With what do I compile it?
The drives are unlocked and mounted.
Where do you see an password error?
You mean pulling your Plugin and the compile it?
With what do I compile it?
Sorry for the late reply.
I thought that you are enumerating the drives in Encryption but it seems you are not.
I have now placed them in Crypttab and it now works, but throws an error.
I now get this:
root@openmediavault:~# omv-luks-start
/usr/sbin/omv-luks-start: line 37: /root/bash-spinner/spinner.sh: No such file or directory
Proceeding to unlock drives
Unlocking of drives ended, attempting to mount disks and encrypted containers
Mounting linux filesystems from /etc/fstab
Please enter passphrase for disk Hitachi_HTS542512K9SA00 (sda-crypt)! ****
Please enter passphrase for disk WDC_WD3200BEVT-24A23T0 (sdb-crypt)! ****
Invalid password file /run/systemd/ask-password/ask.fcjrTI
Failed to show password: Bad message
A dependency job for luks-mount.target failed. See 'journalctl -xe' for details.
Starting multi-user.target
Alles anzeigen
Here is the journalctl, no idea how much you need:
root@openmediavault:~# journalctl -xe
-- Logs begin at Sun 2019-11-03 17:59:17 CET, end at Sun 2019-11-03 18:52:35 CET. --
Nov 03 18:00:11 openmediavault smartd[1026]: Device: /dev/disk/by-id/ata-WDC_WD3200BEVT-24A23T0_WD-WX81A90D3797, type changed from 'scsi' to 'sat'
TOO LONG database: Western Digital Scorpio Blue Serial ATA
Nov 03 18:00:11 openmediavault systemd[1]: Started containerd container runtime.
-- Subject: Unit containerd.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit containerd.service has finished starting up.
--
-- The start-up result is done.
Nov 03 18:00:11 openmediavault systemd[1]: Starting Docker Application Container Engine...
-- Subject: Unit docker.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit docker.service has begun starting up.
Nov 03 18:00:11 openmediavault avahi-daemon[1038]: Server startup complete. Host name is openmediavault.local. Local service cookie is 1597797161.
Nov 03 18:00:11 openmediavault smartd[1026]: Device: /dev/disk/by-id/ata-WDC_WD3200BEVT-24A23T0_WD-WX81A90D3797 [SAT], enabled SMART Attribute Autosave.
Nov 03 18:00:11 openmediavault smartd[1026]: Device: /dev/disk/by-id/ata-TOO LONG
Nov 03 18:00:11 openmediavault smartd[1026]: Monitoring 2 ATA/SATA, 0 SCSI/SAS and 0 NVMe devices
Nov 03 18:00:11 openmediavault collectd[1237]: plugin_load: plugin "cpu" successfully loaded.
Nov 03 18:00:11 openmediavault collectd[1237]: plugin_load: plugin "df" successfully loaded.
Nov 03 18:00:11 openmediavault smartd[1026]: Device: /dev/disk/by-id/ata-Hitachi_HTS542512K9SA00_080703BB6200ABCD30UG [SAT], 1 Currently unreadable (pending) sectors
TOO LONG
Nov 03 18:00:12 openmediavault systemd[1]: Started LSB: Shell In A Box Daemon.
TOO LONG start-up result is done.
Nov 03 18:00:12 openmediavault avahi-daemon[1038]: Service "openmediavault - Web control panel" (/services/website.service) successfully established.
TOO LONG
Nov 03 18:00:12 openmediavault smartd[1026]: Device: /dev/disk/by-id/ata-Hitachi_HTS542512K9SA00_080703BB6200ABCD30UG [SAT], state written to /var/libTOO LONG
Nov 03 18:00:13 openmediavault systemd-cryptsetup[1011]: Set cipher aes, mode xts-plain64, key size 256 bits for device /dev/disk/by-uuid/736753f6-59bd-4b28-81ff-3e45935f2f1b.
Nov 03 18:00:14 openmediavault systemd[1]: Started Generate the prelogin message.
TOO LONG
Alles anzeigen
btw, is /run/systemd/ask-password/ask.fcjrTI a temporary file or supposed to be an fixed one? Because when I look into that folder there is not a single child in it.
I hope that somebody will see this...
I am playing around with OMV since a few days and your PLugin seems to fit my needs. However, there seem to be a few problems.
I have "activate before crypt target" enabled and now it does not start as wanted.
[btw, would it be possible to let the Webclient run before mounting?]
Now when I ssh to the Server and use
I get:
root@openmediavault:~# omv-luks-start
/usr/sbin/omv-luks-start: line 37: /root/bash-spinner/spinner.sh: No such file or directory
Proceeding to unlock drives
Unlocking of drives ended, attempting to mount disks and encrypted containers
Mounting linux filesystems from /etc/fstab
A dependency job for luks-mount.target failed. See 'journalctl -xe' for details.
Starting multi-user.target
root@openmediavault:~#
which means that I don´t get asked for my password and the drives will not be mounted.
Here is the Output:
-- Logs begin at Sun 2019-10-27 21:45:14 CET, end at Sun 2019-10-27 22:38:36 CET. --
Oct 27 22:01:04 POST TOO LONG
Oct 27 22:01:05 openmediavault nmbd[1358]: process_name_query_request: Name query from 192.168.1.109 on subnet 192.168.1.105 for name WPAD<00>
Oct 27 22:01:19 openmediavault nmbd[1358]: [2019/10/27 22:01:19.482146, 3] ../source3/nmbd/nmbd_incomingdgrams.c:269(process_local_master_announce)
Oct 27 22:01:19 openmediavault nmbd[1358]: process_local_master_announce: from DESKTOP-T0IPFNA<00> IP 192.168.1.109 to WORKGROUP<1e> for server DESKTOP-T0IPFNA.
Oct 27 22:01:19 openmediavault nmbd[1358]: [2019/10/27 22:01:19.482517, 3] ../source3/nmbd/nmbd_incomingdgrams.c:269(process_local_master_announce)
Oct 27 22:01:19 openmediavault nmbd[1358]: process_local_master_announce: from DESKTOP-T0IPFNA<00> IP 192.168.1.109 to WORKGROUP<1e> for server DESKTOP-T0IPFNA.
Oct 27 22:01:23 openmediavault monit[1189]: 'mountpoint_srv_dev-disk-by-label-data320GB' status failed (1) -- /srv/dev-disk-by-label-data320GB is not a mountpoint
Oct 27 22:01:23 openmediavault monit[1189]: 'mountpoint_srv_dev-disk-by-label-data120GB' status failed (1) -- /srv/dev-disk-by-label-data120GB is not a mountpoint
Oct 27 22:01:23 openmediavault monit[1189]: 'mountpoint_srv_dev-disk-by-label-Samsung_1TB' status failed (1) -- /srv/dev-disk-by-label-Samsung_1TB is not a mountpoint
Oct 27 22:01:53 openmediavault monit[1189]: 'mountpoint_srv_dev-disk-by-label-data320GB' status failed (1) -- /srv/dev-disk-by-label-data320GB is not a mountpoint
Oct 27 22:01:53 openmediavault monit[1189]: 'mountpoint_srv_dev-disk-by-label-data120GB' status failed (1) -- /srv/dev-disk-by-label-data120GB is not a mountpoint
Oct 27 22:01:53 openmediavault monit[1189]: 'mountpoint_srv_dev-disk-by-label-Samsung_1TB' status failed (1) -- /srv/dev-disk-by-label-Samsung_1TB is not a mountpoint
Oct 27 22:02:23 openmediavault monit[1189]: 'mountpoint_srv_dev-disk-by-label-data320GB' status failed (1) -- /srv/dev-disk-by-label-data320GB is not a mountpoint
Oct 27 22:02:23 openmediavault monit[1189]: 'mountpoint_srv_dev-disk-by-label-data120GB' status failed (1) -- /srv/dev-disk-by-label-data120GB is not a mountpoint
Oct 27 22:02:23 openmediavault monit[1189]: 'mountpoint_srv_dev-disk-by-label-Samsung_1TB' status failed (1) -- /srv/dev-disk-by-label-Samsung_1TB is not a mountpoint
Oct 27 22:02:54 openmediavault monit[1189]: 'mountpoint_srv_dev-disk-by-label-data320GB' status failed (1) -- /srv/dev-disk-by-label-data320GB is not a mountpoint
Oct 27 22:02:54 openmediavault monit[1189]: 'mountpoint_srv_dev-disk-by-label-data120GB' status failed (1) -- /srv/dev-disk-by-label-data120GB is not a mountpoint
Oct 27 22:02:54 openmediavault monit[1189]: 'mountpoint_srv_dev-disk-by-label-Samsung_1TB' status failed (1) -- /srv/dev-disk-by-label-Samsung_1TB is not a mountpoint
Oct 27 22:03:24 openmediavault monit[1189]: 'mountpoint_srv_dev-disk-by-label-data320GB' status failed (1) -- /srv/dev-disk-by-label-data320GB is not a mountpoint
Oct 27 22:03:24 openmediavault monit[1189]: 'mountpoint_srv_dev-disk-by-label-data120GB' status failed (1) -- /srv/dev-disk-by-label-data120GB is not a mountpoint
Oct 27 22:03:24 openmediavault monit[1189]: 'mountpoint_srv_dev-disk-by-label-Samsung_1TB' status failed (1) -- /srv/dev-disk-by-label-Samsung_1TB is not a mountpoint
Oct 27 22:03:54 openmediavault monit[1189]: 'mountpoint_srv_dev-disk-by-label-data320GB' status failed (1) -- /srv/dev-disk-by-label-data320GB is not a mountpoint
Oct 27 22:03:54 openmediavault monit[1189]: 'mountpoint_srv_dev-disk-by-label-data120GB' status failed (1) -- /srv/dev-disk-by-label-data120GB is not a mountpoint
Oct 27 22:03:54 openmediavault monit[1189]: 'mountpoint_srv_dev-disk-by-label-Samsung_1TB' status failed (1) -- /srv/dev-disk-by-label-Samsung_1TB is not a mountpoint
Oct 27 22:04:24 openmediavault monit[1189]: 'mountpoint_srv_dev-disk-by-label-data320GB' status failed (1) -- /srv/dev-disk-by-label-data320GB is not a mountpoint
Oct 27 22:04:24 openmediavault monit[1189]: 'mountpoint_srv_dev-disk-by-label-data120GB' status failed (1) -- /srv/dev-disk-by-label-data120GB is not a mountpoint
Oct 27 22:04:24 openmediavault monit[1189]: 'mountpoint_srv_dev-disk-by-label-Samsung_1TB' status failed (1) -- /srv/dev-disk-by-label-Samsung_1TB is not a mountpoint
Oct 27 22:04:54 openmediavault monit[1189]: 'mountpoint_srv_dev-disk-by-label-data320GB' status failed (1) -- /srv/dev-disk-by-label-data320GB is not a mountpoint
Alles anzeigen
What do I have to do to fix it?
Then when I want to disable "activate before crypt target", Save it and then try to Apply I get the message:
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-mkconf luks 2>&1' with exit code '1': jq - commandline JSON processor [version 1.5-1-a5b5cbe] Usage: jq [options] <jq filter> [file...] jq is a tool for processing JSON inputs, applying the given filter to its JSON text inputs and producing the filter's results as JSON on standard output. The simplest filter is ., which is the identity filter, copying jq's input to its output unmodified (except for formatting). For more advanced filters see the jq(1) manpage ("man jq") and/or https://stedolan.github.io/jq Some of the options include: -c compact instead of pretty-printed output; -n use `null` as the single input value; -e set the exit status code based on the output; -s read (slurp) all inputs into an array; apply filter to it; -r output raw strings, not JSON texts; -R read raw strings, not JSON texts; -C colorize JSON; -M monochrome (don't colorize JSON); -S sort keys of objects on output; --tab use tabs for indentation; --arg a v set variable $a to value <v>; --argjson a v set variable $a to JSON value <v>; --slurpfile a f set variable $a to an array of JSON texts read from <f>; See the manpage for more options. run-parts: /usr/share/openmediavault/mkconf/luks.d/01fstab exited with return code 2
Additionally when the drives are not mounted my snapraid pool shows under file Systems with the same total and used as the OS drive. Is this a problem? Would I write now to the OS if I write into the pool?
Could somebody help me with that?