Hello,
I followed these instructions on a fresh Buster install and this line:
Code
apt-get --yes --auto-remove --show-upgraded \
--allow-downgrades --allow-change-held-packages \
--no-install-recommends \
--option Dpkg::Options::="--force-confdef" \
--option DPkg::Options::="--force-confold" \
install openmediavault-keyring openmediavault
fails with:
Code
[ERROR ] Rendering exception occurred
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/salt/utils/templates.py", line 393, in render_jinja_tmpl
output = template.render(**decoded_context)
File "/usr/lib/python3/dist-packages/jinja2/asyncsupport.py", line 76, in render
return original_render(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 1008, in render
return self.environment.handle_exception(exc_info, True)
File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 780, in handle_exception
reraise(exc_type, exc_value, tb)
File "/usr/lib/python3/dist-packages/jinja2/_compat.py", line 37, in reraise
raise value.with_traceback(tb)
File "<template>", line 57, in top-level template code
File "/var/cache/salt/minion/extmods/modules/omv_utils.py", line 173, in get_root_filesystem
fs = openmediavault.fs.Filesystem.from_mount_point('/')
File "/usr/lib/python3/dist-packages/openmediavault/fs/__init__.py", line 95, in from_mount_point
device = pyudev.Devices.from_device_number(context, 'block', st.st_dev)
File "/usr/lib/python3/dist-packages/pyudev/device/_device.py", line 182, in from_device_number
raise DeviceNotFoundByNumberError(typ, number)
pyudev.device._errors.DeviceNotFoundByNumberError: No block device with number 22
Display More
Whole output here: https://pastebin.com/3dUNLFJt
Do you have any hint on what could be expected, as a block device number 22?
This is cat /etc/fstab:
Code
# /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/sda1 during installation
UUID=c29477ed-9bb2-4056-b91a-c34580ec3759 / btrfs defaults 0 0
# swap was on /dev/sda5 during installation
UUID=62094831-436c-417c-8e00-a0733447bdb3 none swap sw 0 0
Display More
and ls -l /dev/block:
Code
total 0
lrwxrwxrwx 1 root root 6 Aug 6 15:36 8:0 -> ../sda
lrwxrwxrwx 1 root root 7 Aug 6 15:36 8:1 -> ../sda1
lrwxrwxrwx 1 root root 6 Aug 6 15:36 8:16 -> ../sdb
lrwxrwxrwx 1 root root 7 Aug 6 15:36 8:17 -> ../sdb1
lrwxrwxrwx 1 root root 7 Aug 6 15:36 8:2 -> ../sda2
lrwxrwxrwx 1 root root 6 Aug 6 15:36 8:32 -> ../sdc
lrwxrwxrwx 1 root root 7 Aug 6 15:36 8:33 -> ../sdc1
lrwxrwxrwx 1 root root 7 Aug 6 15:36 8:5 -> ../sda5
I understand OMV is meant to work with a data partition which is distinct from the root fs, can you figure if the above error is related? I'd like to rule out other issues before reallocating the storage.