Is install-dev-tools broken in 24.10.2?

just tried to install dev tools but received this error

  • FORCE_ARG=
  • [[ ‘’ == --\f\o\r\c\e ]]
  • [[ ! -S /var/run/middleware/middlewared.sock ]]
  • PACKAGES=(make open-iscsi python3-cryptography python3-pip python3-pyfakefs python3-pyotp python3-pytest python3-pytest-asyncio python3-pytest-dependency python3-pytest-rerunfailures python3-pytest-timeout snmp sshpass zstd)
  • PIP_PACKAGES=()
  • ‘[’ -f /usr/local/libexec/disable-rootfs-protection ‘]’
  • /usr/local/libexec/disable-rootfs-protection
    Flagging root dataset as developer mode
    Setting readonly=off on dataset boot-pool/ROOT/24.10.1/opt
    Setting readonly=off on dataset boot-pool/ROOT/24.10.1/usr
    cannot mount ‘boot-pool/ROOT/24.10.1/usr’: Read-only file system
    property may be set but unable to remount filesystem
    /usr/bin/apt: setting 0o755 on file.
    Traceback (most recent call last):
    File “/usr/local/libexec/disable-rootfs-protection”, line 117, in
    chmod_files()
    File “/usr/local/libexec/disable-rootfs-protection”, line 53, in chmod_files
    os.chmod(entry.path, new_mode)
    OSError: [Errno 30] Read-only file system: ‘/usr/bin/apt’
2 Likes

I got the same issue after upgrade

Any body has resovled this?

1 Like

I suggest you report this using the bug report button directly from inside TrueNAS.

OK, I’ve open a ticket, hope it will be fixed soon.
https://ixsystems.atlassian.net/browse/NAS-133291

1 Like

The ticket have been closed, with follow commands, the issue can be solved:

$sudo systemd-sysext unmerge
$sudo install-dev-tools
$sudo systemd-sysext merge
1 Like

That looks like at least two commands.
Should they be used like so:
sudo systemd-sysext unmerge install-dev-tools
sudo systemd-sysext merge

Or another way?

sudo systemd-sysext unmerge
install-dev-tools
sudo systemd-sysext merge

:slight_smile:

1 Like

it seems like you’ll need to leave it unmerged when installing anything with apt-get though

1 Like

Yes,and I always get this warning after apt-get install,but seems don’t matter:

Preparing to unpack .../screen_4.9.0-4_amd64.deb ...
Unpacking screen (4.9.0-4) ...
Setting up initramfs-tools (0.142) ...
update-initramfs: deferring update (trigger activated)
Setting up screen (4.9.0-4) ...
Processing triggers for debianutils (5.7-0.5~deb12u1) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for initramfs-tools (0.142) ...
ln: failed to create hard link '/boot/initrd.img-6.6.44-production+truenas.dpkg-bak': Read-only file system
cp: cannot create regular file '/boot/initrd.img-6.6.44-production+truenas.dpkg-bak': Read-only file system
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)
1 Like

Has anyone being able to get past the Read-only file system issue when running initramfs-tools?

I tried the steps marked as solution, but that read-only file system issue keeps preventing me from rebuilding init image

Same, though I’m on Fangtooth now, 25.04.0 … was trying to install the old nvidia 470 drivers for my K80 but can’t get past this point, even tried setting readonly=off on the zfs boot-pool dataset for / but that never updated, always says “on” :confused:

Turns out I had to reboot after doing install-dev-tools for the /boot path to be writable. Unfortunately now I am stuck at…

Error! Bad return status for module build on kernel: 6.12.15-production+truenas (x86_64)
Consult /var/lib/dkms/nvidia-tesla-470/470.256.02/build/make.log for more information.
dpkg: error processing package nvidia-tesla-470-kernel-dkms (–configure):
installed nvidia-tesla-470-kernel-dkms package post-installation script subprocess returned error exit status 10

make.log

make[3]: *** [scripts/Makefile.build:229: /var/lib/dkms/nvidia-tesla-470/470.256.02/build/nvidia/os-mlock.o] Error 1
make[2]: *** [/usr/src/linux-headers-truenas-production-amd64/Makefile:1940: /var/lib/dkms/nvidia-tesla-470/470.256.02/build] Error 2
make[1]: *** [Makefile:227: __sub-make] Error 2
make: *** [Makefile:80: modules] Error 2

I had problems compiling the 470.xx drivers with the new 6.12.x kernel used by Fangtooth, but some Google search helped.

The issue is that the driver is old and needs patch for compiling with the 6.12.x kernel series.

I found the patches here: CachyOS-PKGBUILDS/nvidia/nvidia-470xx-utils at master · CachyOS/CachyOS-PKGBUILDS · GitHub (download the 6.12 patch) and apply it onto the NVIDIA driver code. Unfortunately I don’t have the code anymore to try to give you the exact patch command, but I did get it to compile (without DKMS) and my GeForce GT 730 is now recognized by nvidia-smi.

2 Likes

Thank you so much!!

I grabbed the patch and the driver (.run), extracted it, and applied the patch using patch < ../../kernel-6.12.patch in the NVIDIA-Linux-x86_64-470.256.02/kernel directory, patch tool said couldn’t find the file so I provided it nvidia-drm/nvidia-drm-drv.c which ended successfully I guess (no errors).

However running nvidia-installer didn’t work.

I then found this thread/post https://www.linuxquestions.org/questions/showthread.php?p=6535368, and that seems to have installed correctly.

1 Like