bedna Posted June 16 Share Posted June 16 (edited) I ran an update on my orangpi PC2. Setting up armbian-zsh (24.5.1) ... cp: cannot create directory '/home/unifi/.oh-my-zsh': No such file or directory cp: cannot create regular file '/home/unifi/.zshrc': No such file or directory chown: cannot access '/home/unifi/.oh-my-zsh': No such file or directory chown: cannot access '/home/unifi/.zshrc': No such file or directory Witch is to be expected to fail, because that is a system user I accedentally gave an above 1000 UID Unifi is UID 1003, my regular user bedna (1000) is the owner of /home/bedna I don't mind, I don't use zsh anyway, but figured you would want to know about this. Edit I spoke to early, the update actually breaks the system. Seems to be network related because it gets stuck at that if I connect a display to the device. I have restored a backup and retried 2 times, same thing, so there is presumably something wrong on your side here. This is what the terminal gave during the update, and as you can see, it looks like it all goes smooth, something in the firmware or kernel? Spoiler Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages have been kept back: armbian-bsp-cli-orangepipc2 The following packages will be upgraded: armbian-config armbian-firmware armbian-plymouth-theme armbian-zsh containerd.io docker-ce docker-ce-cli docker-ce-rootless-extras docker-compose-plugin linux-dtb-current-sunxi64 linux-image-current-sunxi64 linux-u-boot-orangepipc2-current 12 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 204 MB of archives. After this operation, 54.3 MB of additional disk space will be used. Do you want to continue? [Y/n] y Get:2 https://download.docker.com/linux/debian bullseye/stable arm64 containerd.io arm64 1.6.33-1 [21.6 MB] Get:1 http://fi.mirror.armbian.de/apt bullseye/main arm64 armbian-config all 24.5.1 [136 kB] Get:5 http://fi.mirror.armbian.de/apt bullseye/main arm64 armbian-zsh all 24.5.1 [11.8 MB] Get:3 http://armbian.hosthatch.com/apt bullseye/main arm64 armbian-firmware all 24.5.1 [90.4 MB] Get:9 https://download.docker.com/linux/debian bullseye/stable arm64 docker-ce-cli arm64 5:26.1.4-1~debian.11~bullseye [13.2 MB] Get:10 https://download.docker.com/linux/debian bullseye/stable arm64 docker-ce arm64 5:26.1.4-1~debian.11~bullseye [15.4 MB] Get:11 https://download.docker.com/linux/debian bullseye/stable arm64 docker-ce-rootless-extras arm64 5:26.1.4-1~debian.11~bullseye [8390 kB] Get:12 https://download.docker.com/linux/debian bullseye/stable arm64 docker-compose-plugin arm64 2.27.1-1~debian.11~bullseye [10.8 MB] Get:4 http://armbian.hosthatch.com/apt bullseye/main arm64 armbian-plymouth-theme all 24.5.1 [108 kB] Get:6 http://fi.mirror.armbian.de/apt bullseye/main arm64 linux-dtb-current-sunxi64 arm64 24.5.1 [113 kB] Get:7 http://fi.mirror.armbian.de/apt bullseye/main arm64 linux-image-current-sunxi64 arm64 24.5.1 [31.3 MB] Get:8 http://fi.mirror.armbian.de/apt bullseye/main arm64 linux-u-boot-orangepipc2-current arm64 24.5.1 [336 kB] Fetched 204 MB in 23s (8926 kB/s) (Reading database ... 49264 files and directories currently installed.) Preparing to unpack .../00-armbian-config_24.5.1_all.deb ... Unpacking armbian-config (24.5.1) over (23.11.1) ... Preparing to unpack .../01-armbian-firmware_24.5.1_all.deb ... Unpacking armbian-firmware (24.5.1) over (23.11.1) ... Preparing to unpack .../02-armbian-plymouth-theme_24.5.1_all.deb ... Unpacking armbian-plymouth-theme (24.5.1) over (23.11.1) ... Preparing to unpack .../03-armbian-zsh_24.5.1_all.deb ... Unpacking armbian-zsh (24.5.1) over (23.11.1) ... Preparing to unpack .../04-containerd.io_1.6.33-1_arm64.deb ... Unpacking containerd.io (1.6.33-1) over (1.6.31-1) ... Preparing to unpack .../05-docker-ce-cli_5%3a26.1.4-1~debian.11~bullseye_arm64.deb ... Unpacking docker-ce-cli (5:26.1.4-1~debian.11~bullseye) over (5:26.1.3-1~debian.11~bullseye) ... Preparing to unpack .../06-docker-ce_5%3a26.1.4-1~debian.11~bullseye_arm64.deb ... Unpacking docker-ce (5:26.1.4-1~debian.11~bullseye) over (5:26.1.3-1~debian.11~bullseye) ... Preparing to unpack .../07-docker-ce-rootless-extras_5%3a26.1.4-1~debian.11~bullseye_arm64.deb ... Unpacking docker-ce-rootless-extras (5:26.1.4-1~debian.11~bullseye) over (5:26.1.3-1~debian.11~bullseye) ... Preparing to unpack .../08-docker-compose-plugin_2.27.1-1~debian.11~bullseye_arm64.deb ... Unpacking docker-compose-plugin (2.27.1-1~debian.11~bullseye) over (2.27.0-1~debian.11~bullseye) ... Preparing to unpack .../09-linux-dtb-current-sunxi64_24.5.1_arm64.deb ... Armbian 'linux-dtb-current-sunxi64' for '6.6.31-current-sunxi64': 'preinst' starting. Armbian 'linux-dtb-current-sunxi64' for '6.6.31-current-sunxi64': 'preinst' finishing. Unpacking linux-dtb-current-sunxi64 (24.5.1) over (23.11.1) ... Preparing to unpack .../10-linux-image-current-sunxi64_24.5.1_arm64.deb ... Armbian 'linux-image-current-sunxi64' for '6.1.63-current-sunxi64': 'prerm' starting. Armbian 'linux-image-current-sunxi64' for '6.1.63-current-sunxi64': 'prerm' finishing. Armbian 'linux-image-current-sunxi64' for '6.6.31-current-sunxi64': 'preinst' starting. Armbian 'linux-image-current-sunxi64' for '6.6.31-current-sunxi64': 'preinst' finishing. Unpacking linux-image-current-sunxi64 (24.5.1) over (23.11.1) ... Armbian 'linux-image-current-sunxi64' for '6.1.63-current-sunxi64': 'postrm' starting. Armbian 'linux-image-current-sunxi64' for '6.1.63-current-sunxi64': 'postrm' finishing. Preparing to unpack .../11-linux-u-boot-orangepipc2-current_24.5.1_arm64.deb ... Unpacking linux-u-boot-orangepipc2-current (24.5.1) over (23.11.1) ... Setting up linux-image-current-sunxi64 (24.5.1) ... Armbian 'linux-image-current-sunxi64' for '6.6.31-current-sunxi64': 'postinst' starting. dkms: running auto installation service for kernel 6.6.31-current-sunxi64:. update-initramfs: Generating /boot/initrd.img-6.6.31-current-sunxi64 update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.6.31-current-sunxi64 Image Name: uInitrd Created: Sun Jun 16 06:56:09 2024 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 17266336 Bytes = 16861.66 KiB = 16.47 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.6.31-current-sunxi64 to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.6.31-current-sunxi64' update-initramfs: Armbian: done. Remove unused generated file: /boot/initrd.img-6.1.63-current-sunxi64 Remove unused generated file: /boot/uInitrd-6.1.63-current-sunxi64 Armbian: update last-installed kernel symlink to 'Image'... '/boot/Image' -> 'vmlinuz-6.6.31-current-sunxi64' Armbian: Debian compat: linux-update-symlinks install 6.6.31-current-sunxi64 boot/vmlinuz-6.6.31-current-sunxi64 I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.6.31-current-sunxi64 I: /initrd.img.old is now a symlink to boot/initrd.img-6.6.31-current-sunxi64 I: /vmlinuz is now a symlink to boot/vmlinuz-6.6.31-current-sunxi64 I: /initrd.img is now a symlink to boot/initrd.img-6.6.31-current-sunxi64 Armbian 'linux-image-current-sunxi64' for '6.6.31-current-sunxi64': 'postinst' finishing. Setting up armbian-zsh (24.5.1) ... cp: cannot create directory '/home/unifi/.oh-my-zsh': No such file or directory cp: cannot create regular file '/home/unifi/.zshrc': No such file or directory chown: cannot access '/home/unifi/.oh-my-zsh': No such file or directory chown: cannot access '/home/unifi/.zshrc': No such file or directory Setting up linux-dtb-current-sunxi64 (24.5.1) ... Armbian 'linux-dtb-current-sunxi64' for '6.6.31-current-sunxi64': 'postinst' starting. Armbian: DTB: symlinking /boot/dtb to /boot/dtb-6.6.31-current-sunxi64... 'dtb' -> 'dtb-6.6.31-current-sunxi64' Armbian 'linux-dtb-current-sunxi64' for '6.6.31-current-sunxi64': 'postinst' finishing. Setting up armbian-config (24.5.1) ... Setting up linux-u-boot-orangepipc2-current (24.5.1) ... Armbian 'uboot-orangepipc2-current' for '2024.01-S866c-Pa03c-H2b63-V1521-B2e16-R448a': 'postinst' starting. Armbian 'uboot-orangepipc2-current' for '2024.01-S866c-Pa03c-H2b63-V1521-B2e16-R448a': 'postinst' finishing. Setting up containerd.io (1.6.33-1) ... Setting up docker-compose-plugin (2.27.1-1~debian.11~bullseye) ... Setting up armbian-firmware (24.5.1) ... Setting up docker-ce-cli (5:26.1.4-1~debian.11~bullseye) ... Setting up docker-ce-rootless-extras (5:26.1.4-1~debian.11~bullseye) ... Setting up armbian-plymouth-theme (24.5.1) ... update-initramfs: deferring update (trigger activated) Setting up docker-ce (5:26.1.4-1~debian.11~bullseye) ... docker.service is a disabled or a static unit not running, not starting it. docker.socket is a disabled or a static unit not running, not starting it. Processing triggers for man-db (2.9.4-2) ... Processing triggers for initramfs-tools (0.140) ... update-initramfs: Generating /boot/initrd.img-6.6.31-current-sunxi64 update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.6.31-current-sunxi64 Image Name: uInitrd Created: Sun Jun 16 06:56:57 2024 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 17265738 Bytes = 16861.07 KiB = 16.47 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.6.31-current-sunxi64 to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.6.31-current-sunxi64' update-initramfs: Armbian: done. Edited June 16 by bedna 0 Quote Link to comment Share on other sites More sharing options...
Igor Posted June 17 Share Posted June 17 On 6/16/2024 at 7:04 AM, bedna said: I have restored a backup and retried 2 times, same thing, so there is presumably something wrong on your side here. Hmm, can you give us a bit more information on how to reproduce this? If I start with a clean image, which you have used? Bullseye is not well maintained by upstream, so we don't provide images anymore. Its suggested to use Bookworm from some time. Edit: https://github.com/armbian/build/blob/main/lib/functions/compilation/packages/armbian-zsh-deb.sh#L40-L54 Looks like this doesn't work well in your case. Needs some adjustments, ideas are welcome. 0 Quote Link to comment Share on other sites More sharing options...
going Posted June 17 Share Posted June 17 16.06.2024 в 08:04, bedna сказал: cp: cannot create directory '/home/unifi/.oh-my-zsh': No such file or directory 16.06.2024 в 08:04, bedna сказал: Unifi is UID 1003, my regular user bedna (1000) is the owner of /home/bedna Do I understand correctly? Are you logged in as a "benda" user? There is another user "unifi" in your OS, but he does not have a home directory? Or does the directory exist but the user "1003" has write rights? Who has "sudo" rights? UID 1003 or 1000? 0 Quote Link to comment Share on other sites More sharing options...
going Posted June 17 Share Posted June 17 3 часа назад, Igor сказал: Edit: https://github.com/armbian/build/blob/main/lib/functions/compilation/packages/armbian-zsh-deb.sh#L40-L54 Looks like this doesn't work well in your case. Needs some adjustments, ideas are welcome. Before these actions, it is necessary to verify users with UID >= 1000. And in the loop for the found users, first check the existence of the home directory and if it exists, then do these actions (cp, chown). 0 Quote Link to comment Share on other sites More sharing options...
bedna Posted Wednesday at 07:04 AM Author Share Posted Wednesday at 07:04 AM (edited) Oh crap! I missed these repliess, I must make sure to activate email notification, I'm sorry! I honestly just left it unupdated, it's not a huge issue for me, I don't really use it for other than testing a script. The img it was installed from was "Armbian_community_24.5.0-trunk.93_Orangepipc2_bookworm_current_6.6.18_minimal" and I am aware it IS a "community release", that's why I didn't put a massive amount of investigation. On 6/17/2024 at 4:07 PM, going said: Are you logged in as a "benda" user? Close.. "bedna".. xD But yes, bedna is UID 1000, the ONLY sudo user. 1003 is a system user, no home, no login shell IIRC. Edit. I made a check, and it actually is supposed to have a home in /home/unifi (MY BAD.. xD unifi:x:1003:1003:System user for Unifi,,,:/home/unifi:/usr/sbin/nologin So that is on me, I probably forgot to use the --system option or smthn, it is not a big deal and most likely not connected to the network failing at boot anyway. And the zsh is just super strange, I never use it even though I know it comes with the img. (I now realize, the option in the installation is just selecting the shell, there is absolutely a zsh installed on the opi, I have just not noticed it) I will try with a fresh image and come back with results, when I get time... Edit 2: https://github.com/armbian/build/blob/2a2e609e3c5e55404759ea9a2cf010b268c2f356/lib/functions/compilation/packages/armbian-zsh-deb.sh#L49C3-L49C129 awk -F'[:]' '{if (\$3 >= 1000 && \$3 != 65534 || \$3 == 0) print ""\$1":"\$3" "\$6"/.zshrc"}' /etc/passwd | xargs -n2 chown -R Is the "culprit". In this situation it IS my bad as shown above, not sure what I did because the directory was not created, but the entry in /etc/passwd clearly exist. A solution would be to run [-d <user-home-path found in passwd> ], but tbh, babysitting at that level is imho a bit too far... This is on me.. But the system freezing at boot trying to connect to network, I will look deeper into. Edited Wednesday at 07:33 AM by bedna 0 Quote Link to comment Share on other sites More sharing options...
going Posted Wednesday at 12:55 PM Share Posted Wednesday at 12:55 PM This script assumes that there should be one user on your system with a UID >= 1000. https://github.com/armbian/build/blob/main/lib/functions/compilation/packages/armbian-zsh-deb.sh#L40-L54 In general, this is not true. If you need an administrator user without a home directory, you can create one with a UID < 1000. But in this case, zsh will not work correctly for him. Or fix the situation manually. 5 часов назад, bedna сказал: But the system freezing at boot trying to connect to network, I will look deeper into. There may be two problems here. There is no clock on the device and the OS makes a request to a remote time server at startup and if it does not receive a timestamp, then it just waits. It looks like it's stuck. 1) The external internet connection is not working. 2) You have updated the kernel package. Your OS is Debian Bullseye. Packages are collected in the ubuntu noble environment (24.04). This may have caused the Ethernet connection to break down. P.S. Try installing Ubuntu 24.04 on your device. And your 4 year updates won't create any problems. 0 Quote Link to comment Share on other sites More sharing options...
bedna Posted Wednesday at 05:51 PM Author Share Posted Wednesday at 05:51 PM 4 hours ago, going said: There is no clock on the device and the OS makes a request to a remote time server at startup and if it does not receive a timestamp, then it just waits. It looks like it's stuck. 1) The external internet connection is not working. 2) You have updated the kernel package. Your OS is Debian Bullseye. Yeah, I didn't react to the comment about if I was using bullseye, I was 100% sure I had a bookworm img installed, but that might not be the case. Thank you for providing feedback, but I will reinstall with the latest community img and see what that leads to. 0 Quote Link to comment Share on other sites More sharing options...
bedna Posted Wednesday at 05:54 PM Author Share Posted Wednesday at 05:54 PM (edited) 5 hours ago, going said: There is no clock on the device and the OS makes a request to a remote time server at startup and if it does not receive a timestamp, then it just waits. It looks like it's stuck. 1) The external internet connection is not working. 2) You have updated the kernel package. Your OS is Debian Bullseye. Yeah, I didn't react to the comment about if I was using bullseye, I was 100% sure I had a bookworm img installed, but that might not be the case, I must have dreamt I installed the only opiPC2 img I had downloaded on my computer. 5 hours ago, going said: And your 4 year updates won't create any problems. WDYM? I updated that system at least once a week up until it no longer worked. Worked flawlessly up until I made the post. Thank you for providing feedback, but I will reinstall with the latest community img and see what that leads to. Edited Wednesday at 05:59 PM by bedna I tried to edit the above post to add info, but instead it made a new post, and now I can not delete any of them.. Mods, feel free to clean up.. 0 Quote Link to comment Share on other sites More sharing options...
going Posted Wednesday at 07:12 PM Share Posted Wednesday at 07:12 PM @bedna It's possible that I'm wrong. Here the user seems to have found a problem and this is a corrupted dts for OPI-PC2: https://forum.armbian.com/topic/35635-armbian-242-is-broken-on-orange-pi-pc2/?do=findComment&comment=195299 0 Quote Link to comment Share on other sites More sharing options...
bedna Posted Wednesday at 08:16 PM Author Share Posted Wednesday at 08:16 PM @going Interesting.... update-initramfs: Armbian: Symlinking /boot/uInitrd-6.6.31-current-sunxi64 to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.6.31-current-sunxi64' update-initramfs: Armbian: done. Remove unused generated file: /boot/initrd.img-6.1.63-current-sunxi64 Remove unused generated file: /boot/uInitrd-6.1.63-current-sunxi64 Armbian: update last-installed kernel symlink to 'Image'... '/boot/Image' -> 'vmlinuz-6.6.31-current-sunxi64' Armbian: Debian compat: linux-update-symlinks install 6.6.31-current-sunxi64 boot/vmlinuz-6.6.31-current-sunxi64 I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.6.31-current-sunxi64 I: /initrd.img.old is now a symlink to boot/initrd.img-6.6.31-current-sunxi64 I: /vmlinuz is now a symlink to boot/vmlinuz-6.6.31-current-sunxi64 I: /initrd.img is now a symlink to boot/initrd.img-6.6.31-current-sunxi64 Armbian 'linux-image-current-sunxi64' for '6.6.31-current-sunxi64': 'postinst' finishing. I wiped the sd-card, but I have access to a backup to before running this update.. You guys need/want something from me? 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.