no, i use manual decryption only when needed. (once a week or so)
Beiträge von peekaa
-
-
Some outputs:
first boot:
Code
Alles anzeigenroot@woodenbox:~# uname -r 6.12.32+bpo-amd64 root@woodenbox:~# blkid /dev/sda1: LABEL="fsys" UUID="630deb7d-e3e3-4eb1-b9f1-5b7858c34f34" BLOCK_SIZE="4096" TYPE="ext4" PARTUUI D="b7bfccc6-01" root@woodenbox:~# findmnt --real TARGET SOURCE FSTYPE OPTIONS / /dev/sda1 ext4 rw,noatime,nod ├─/var/folder2ram/var/log /dev/sda1[/var/log] ext4 rw,noatime,nod ├─/var/folder2ram/var/tmp /dev/sda1[/var/tmp] ext4 rw,noatime,nod ├─/var/folder2ram/var/lib/openmediavault/rrd /dev/sda1[/var/lib/openmediavault/rrd] ext4 rw,noatime,nod ├─/var/folder2ram/var/spool /dev/sda1[/var/spool] ext4 rw,noatime,nod ├─/var/folder2ram/var/lib/rrdcached /dev/sda1[/var/lib/rrdcached] ext4 rw,noatime,nod ├─/var/folder2ram/var/lib/monit /dev/sda1[/var/lib/monit] ext4 rw,noatime,nod └─/var/folder2ram/var/cache/samba /dev/sda1[/var/cache/samba] ext4 rw,noatime,nod
After reboot:
Code
Alles anzeigenroot@woodenbox:~# uname -r 6.12.32+bpo-amd64 root@woodenbox:~# findmnt --real TARGET SOURCE FSTYPE OPTIONS / /dev/sdc1 ext4 rw,noat ├─/var/folder2ram/var/log /dev/sdc1[/var/log] ext4 rw,noat ├─/srv/dev-disk-by-uuid-3fa12aae-eeac-4a5e-b93b-a72ae45c3930 │ /dev/sdb1 ext4 rw,rela ├─/var/folder2ram/var/tmp /dev/sdc1[/var/tmp] ext4 rw,noat ├─/var/folder2ram/var/lib/openmediavault/rrd /dev/sdc1[/var/lib/openmediavault/rrd] │ ext4 rw,noat ├─/var/folder2ram/var/spool /dev/sdc1[/var/spool] ext4 rw,noat ├─/var/folder2ram/var/lib/rrdcached /dev/sdc1[/var/lib/rrdcached] ext4 rw,noat ├─/var/folder2ram/var/lib/monit /dev/sdc1[/var/lib/monit] ext4 rw,noat └─/var/folder2ram/var/cache/samba /dev/sdc1[/var/cache/samba] ext4 rw,noat root@woodenbox:~# blkid /dev/sdb1: LABEL="green" UUID="3fa12aae-eeac-4a5e-b93b-a72ae45c3930" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="aaa" PARTUUID="c667e169-371b-4dd1-b560-f4e5b479ab5c" /dev/sda: UUID="d0ad7958-97f0-46d0-9f03-17f0c4f638f3" TYPE="crypto_LUKS" /dev/sdc1: LABEL="fsys" UUID="630deb7d-e3e3-4eb1-b9f1-5b7858c34f34" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="b7bfccc6-01" root@woodenbox:~# cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sdb1 during installation UUID=630deb7d-e3e3-4eb1-b9f1-5b7858c34f34 / ext4 noatime,nodiratime,errors=remount-ro 0 1 # swap was on /dev/sdb5 during installation #UUID=137af709-b018-4fa7-8ba3-3ccf22656733 none swap sw 0 0 # >>> [openmediavault] /dev/disk/by-uuid/3fa12aae-eeac-4a5e-b93b-a72ae45c3930 /srv/dev-disk-by-uuid-3fa12aae-eeac-4a5e-b93b-a72ae45c3930 ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2 /dev/disk/by-uuid/a3cbf8f1-bb39-4228-9593-daf2713ef348 /srv/dev-disk-by-uuid-a3cbf8f1-bb39-4228-9593-daf2713ef348 ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2 # <<< [openmediavault]
-
sata.
-
Services - Autoshutdown
-
Lately, for about a month or two, when I turn on the server, my disks don't boot. I see the disks as missing in the web administration. When I restart the server, everything is ok. My server automatically shuts down every night. Thank you for your help.
woodenbox
Version
7.7.10-1 (Sandworm)
Processor
Intel(R) Celeron(R) CPU J1800 @ 2.41GHz
Kernel
Linux 6.12.32+bpo-amd64
/dev/sda
WDC WD20EFAX-68B2RN1
WD-WXA2A51NC6XY
ATA 1.82 TiB/dev/sdb
WDC WD10EZRX-00A3KB0
WD-WCC4J1RD8291
ATA 931.51 GiB -
I keep getting emails from one instance of omv (odroid):
subject [blackboxrotava] Cron <root@blackboxrotava> if test -x /usr/sbin/apticron; then /usr/sbin/apticron --cron; else true; fi
text: W: http://apt.armbian.com/dists/bookworm/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
pls help what to do.
-
-
I'll just write a procedure my upgrade to omv7 via ssh/putty: The first bug at the beginning somehow went through, attachment. Then it ran for a long time, then it stopped on "removing obsolete config file...", attachment. Then I had to do a hard reboot, then reloaded putty and ran omv-upgrade. And then it ran about 10 minutes, then restarted. All ok, except for the web gui (Bad Gateway): I run in ssh: omv-salt stage run deploy, and now hopefully everything is ok.
Thank you for omv.
-
Feature request: if all the update process could be in omv-upgrade - even the applying configuration in web management. So we do not have to do upgrade twitce - first in terminal and secong in web management.
-
this helped me network card suspend wol g
-
Same here. I have one hdd with LUKS2. And there was also too slow start with message "A start job is running"... So I add x-systemd.device-timeout=4ms to fstab:
defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl,x-systemd.device-timeout=4ms
Another issue found when looking for solution: in crypttab there should be record about this disk, but its empty.
-
For the last couple of weeks my drives have not been waking up from their sleep. After some updates. I have omv 5.6., two HDDs.Autoshutdown puts the drives to sleep in the evening (Suspend), and in the morning when they don't connect after awaking server with wol command from my computer. I get these emails:
after reboot all is fine.
---------
[woodenbox] Monitoring alert -- Status failed mountpoint_srv_dev-disk-by-uuid-3fa12aae-eeac-4a5e-b93b-a72ae45c3930
The system monitoring needs your attention.
Host: \woodenbox
Date: Sat, 16 Oct 2021 03:43:47
Service: mountpoint_srv_dev-disk-by-uuid-3fa12aae-eeac-4a5e-b93b-a72ae45c3930
Event: Status failed
Description: status failed (1) -- /srv/dev-disk-by-uuid-3fa12aae-eeac-4a5e-b93b-a72ae45c3930 is not a mountpoint
This triggered the monitoring system to: alert
---------------------
[woodenbox] Monitoring restart -- Does not exist filesystem_srv_dev-disk-by-uuid-3fa12aae-eeac-4a5e-b93b-a72ae45c3930
The system monitoring needs your attention.
Host: \woodenbox
Date: Sat, 16 Oct 2021 03:43:17
Service: filesystem_srv_dev-disk-by-uuid-3fa12aae-eeac-4a5e-b93b-a72ae45c3930
Event: Does not exist
Description: unable to read filesystem '/srv/dev-disk-by-uuid-3fa12aae-eeac-4a5e-b93b-a72ae45c3930' state
This triggered the monitoring system to: restart
---------------
Thanks for the advice.
-
No, I refer to autoshutdown.conf or smb.conf etc. Thank you.
-
How to restore from backup config files where is on top written that
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
Thank you.
-
OK, disabled, but still my notebook shows there is no wis server....
-
-
Yes, that is working. Anyway when I delete cache in standard mode, its not working. FF 78.6 esr .
-
After reboot I have this issue: [How-To] Fix full OS filesystem - GUI login loop. i do not have disks full:
Code
Alles anzeigenoot@blackbox:~# df Filesystem 1K-blocks Used Available Use% Mounted on udev 951248 0 951248 0% /dev tmpfs 204384 6616 197768 4% /run /dev/mmcblk1p1 14859624 1630940 12600300 12% / tmpfs 1021912 0 1021912 0% /dev/shm tmpfs 5120 4 5116 1% /run/lock tmpfs 1021912 0 1021912 0% /sys/fs/cgroup tmpfs 1021912 0 1021912 0% /tmp folder2ram 1021912 10524 1011388 2% /var/log folder2ram 1021912 0 1021912 0% /var/tmp folder2ram 1021912 716 1021196 1% /var/lib/openmediavault/rrd folder2ram 1021912 616 1021296 1% /var/spool folder2ram 1021912 18992 1002920 2% /var/lib/rrdcached folder2ram 1021912 4 1021908 1% /var/lib/monit folder2ram 1021912 1604 1020308 1% /var/cache/samba /dev/sda1 3844640564 607695508 3236928672 16% /srv/dev-disk-by-label-ff4t tmpfs 204380 0 204380 0% /run/user/0
This was helpfull https://pcmac.biz/openmediavault-5-login-loop-issue/, anyway after night I am were I was again: loop.
CodePRETTY_NAME="Armbian 20.11.3 Buster" NAME="Debian GNU/Linux" VERSION_ID="10" odroid hc2, ff 78.6esr 64bit, gnome
/var/log/nginx/openmediavault-webgui_error.log is clear, omv-firstaid used, credentials 100% correct.
Thank you if you can help.
-
I had to delete record in /etc/monit/filesystem.conf (not to get monit mails about error) and delete folder in /srv (erase record in web management in Storage - Disks).
-
Well, somehow the missing filesystem record is still there, button "Delete" makes nothing. See attachment. Thank you.