Update-initramfs warnings on unminimize

While doing unminimize on a Jetson Nano connected via SSH, I saw these warnings:

update-initramfs: deferring update (trigger activated)
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Processing triggers for initramfs-tools (0.130ubuntu3.10) ...
update-initramfs: Generating /boot/initrd.img-4.9.140-tegra
cryptsetup: WARNING: failed to detect canonical device of /dev/root
cryptsetup: WARNING: could not determine root device from /etc/fstab
Warning: couldn't identify filesystem type for fsck hook, ignoring.
I: The initramfs will attempt to resume from /dev/zram3
I: (UUID=6c05db5a-4241-4a1e-9ee4-525a6238088a)
I: Set the RESUME variable to override this.
/sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/aarch64-linux-gnu_EGL.conf: No such file or directory
/sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/aarch64-linux-gnu_GL.conf: No such file or directory

What do they mean, and will this cause any problems with booting process?

Hi,

Other users also report this. We are checking it.

Thanks.

Is there any update? I’m getting the same error when running sudo apt upgrade.

qingyao@jetson ~> sudo apt update
[sudo] password for qingyao:
Get:1 file:/var/cuda-repo-10-2-local-10.2.89  InRelease
Ign:1 file:/var/cuda-repo-10-2-local-10.2.89  InRelease
Get:2 file:/var/visionworks-repo  InRelease
Ign:2 file:/var/visionworks-repo  InRelease
Get:3 file:/var/visionworks-sfm-repo  InRelease
Ign:3 file:/var/visionworks-sfm-repo  InRelease
Get:4 file:/var/visionworks-tracking-repo  InRelease
Ign:4 file:/var/visionworks-tracking-repo  InRelease
Get:5 file:/var/cuda-repo-10-2-local-10.2.89  Release [574 B]
Get:5 file:/var/cuda-repo-10-2-local-10.2.89  Release [574 B]
Get:6 file:/var/visionworks-repo  Release [2,001 B]
Get:6 file:/var/visionworks-repo  Release [2,001 B]
Get:7 file:/var/visionworks-sfm-repo  Release [2,005 B]
Get:7 file:/var/visionworks-sfm-repo  Release [2,005 B]
Get:8 file:/var/visionworks-tracking-repo  Release [2,010 B]
Get:8 file:/var/visionworks-tracking-repo  Release [2,010 B]
Hit:15 http://ports.ubuntu.com/ubuntu-ports bionic InRelease
Get:16 http://ports.ubuntu.com/ubuntu-ports bionic-updates InRelease [88.7 kB]
Get:17 http://ports.ubuntu.com/ubuntu-ports bionic-backports InRelease [74.6 kB]
Hit:13 https://repo.download.nvidia.cn/jetson/common r32.4 InRelease
Hit:14 https://repo.download.nvidia.cn/jetson/t210 r32.4 InRelease
Get:18 http://ports.ubuntu.com/ubuntu-ports bionic-security InRelease [88.7 kB]
Get:19 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages [733 kB]
Get:20 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 DEP-11 Metadata [290 kB]
Get:21 http://ports.ubuntu.com/ubuntu-ports bionic-updates/restricted arm64 Packages [1,552 B]
Get:22 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe arm64 Packages [986 kB]
Get:23 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe Translation-en [348 kB]
Unpacking busybox-static (1:1.27.2-2ubuntu3.3) over (1:1.27.2-2ubuntu3.2) ...
Preparing to unpack .../2-librbd1_12.2.13-0ubuntu0.18.04.4_arm64.deb ...
Unpacking librbd1 (12.2.13-0ubuntu0.18.04.4) over (12.2.13-0ubuntu0.18.04.3) ...
Preparing to unpack .../3-librados2_12.2.13-0ubuntu0.18.04.4_arm64.deb ...
Unpacking librados2 (12.2.13-0ubuntu0.18.04.4) over (12.2.13-0ubuntu0.18.04.3) ...
Preparing to unpack .../4-linux-libc-dev_4.15.0-118.119_arm64.deb ...
Unpacking linux-libc-dev:arm64 (4.15.0-118.119) over (4.15.0-117.118) ...
Preparing to unpack .../5-snapd_2.46.1+18.04_arm64.deb ...
Unpacking snapd (2.46.1+18.04) over (2.45.1+18.04.2) ...
Setting up linux-libc-dev:arm64 (4.15.0-118.119) ...
Setting up librados2 (12.2.13-0ubuntu0.18.04.4) ...
Setting up busybox-initramfs (1:1.27.2-2ubuntu3.3) ...
Setting up snapd (2.46.1+18.04) ...
Installing new version of config file /etc/apparmor.d/usr.lib.snapd.snap-confine.real ...
Installing new version of config file /etc/profile.d/apps-bin-path.sh ...
snapd.failure.service is a disabled or a static unit, not starting it.
snapd.snap-repair.service is a disabled or a static unit, not starting it.
Setting up busybox-static (1:1.27.2-2ubuntu3.3) ...
Setting up librbd1 (12.2.13-0ubuntu0.18.04.4) ...
Processing triggers for libc-bin (2.27-3ubuntu1.2) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Processing triggers for gnome-menus (3.13.3-11ubuntu1.1) ...
Processing triggers for dbus (1.12.2-1ubuntu1.2) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for desktop-file-utils (0.23-1ubuntu3.18.04.2) ...
Processing triggers for initramfs-tools (0.130ubuntu3.10) ...
update-initramfs: Generating /boot/initrd.img-4.9.140-tegra
cryptsetup: WARNING: failed to detect canonical device of /dev/root
cryptsetup: WARNING: could not determine root device from /etc/fstab
Warning: couldn't identify filesystem type for fsck hook, ignoring.
I: The initramfs will attempt to resume from /dev/zram3
I: (UUID=6084a8f7-b9a5-416a-8ee7-be704760bb85)
I: Set the RESUME variable to override this.
/sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/aarch64-linux-gnu_EGL.conf: No such file or directory
/sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/aarch64-linux-gnu_GL.conf: No such file or directory
Processing triggers for bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...

Hello,

I have also seen this warning on Jetson boards. But IIRC, I have seen this on an Ubuntu 18.04 installation on x86_64 systems as well. Since, the update-initramfs utility comes from the Ubuntu rootfs (don’t think NVIDIA modifies it in anyway), other Ubuntu users may have reported it.

Having said that, I will wait for other users’ comments as it bothers me as well :-)

It’s one thing that I noticed, but what bothers me is how slow everything is from booting, desktop manager, SSH access, and serial console. I suspect it’s SD card, but I have already used Samsung Pro Endurance 64 GB.

I can use 32 GB SD card or less. But, is it really the main cause of the slowdown?

I only have the dev kit not the production jetson nano, so I don’t know how fast eMMC is, but I don’t want to buy another unit until I figure out how to optimize this Jetson Nano dev kit performance.

I haven’t even started machine learning yet. Just basic operations of the OS. But there are so few guidelines out there to optimize it.

I have used a sufficient power supply and whatever I can find from jetsonhacks, this forum, and blog articles.

Perhaps unminimize wasn’t a good idea in the 1st place.

Maybe Ubuntu is the problem. If we look at raspbian OS, it’s optimized for the raspberrypi board, and once I install something like Ubuntu Mate, it’s significantly slow.

Next time I would set up Jetson Nano without a desktop, but since the first setup relies on desktop, it’s a pain to restart the process to uninstall the desktop.

Technically this only installs documentation for packages already installed. “unminimize” should have no effect on package updates (other than perhaps when documentation updates, then the updated doc would also be installed).