I performed a basic "apt-get update" and then "apt-get upgrade" on my odroid c2 and now cannot boot. While updating I received a dialog about the kernel being updated with the same version, and needing to reboot soon to avoid any issues. So, I let the update finish and then rebooted. Now it will not boot.
I use my box primarily as a emby (play) and nextcloud (work) server. I am traveling for the next week and rely on the device for remote access to files and such. The latest emby version was released which allowed me to access my media again, their 3.1.1 version had an issue with reverse proxy, and so the 3.2 version was required to have any remote access to my media, otherwise I would have waited until I returned to do any updates.
On a related note, I was feeling ready to donate some money to this project, however it is issues like this that have me feel like reverting to the default ubuntu install for the C2 and minimizing it on my own... I appreciate the efforts here and want to see this improve. Thanks.
Code: Select all
Unpacking setup-odroid (0.0.1-25) over (0.0.1-23) ... Processing triggers for systemd (215-17+deb8u5) ... Setting up linux-image-3.14.79+ (3.14.79-20161215-C2) ... Hmm. There is a symbolic link /lib/modules/3.14.79+/build However, I can not read it: No such file or directory Therefore, I am deleting /lib/modules/3.14.79+/build Hmm. The package shipped with a symbolic link /lib/modules/3.14.79+/source However, I can not read the target: No such file or directory Therefore, I am deleting /lib/modules/3.14.79+/source Running depmod. Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/Image 3.14.79+ /boot/vmlinuz-3.14.79+ run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.14.79+ /boot/vmlinuz-3.14.79+ run-parts: executing /etc/kernel/postinst.d/copy_dtb 3.14.79+ /boot/vmlinuz-3.14.79+ run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.14.79+ /boot/vmlinuz-3.14.79+ update-initramfs: Generating /boot/initrd.img-3.14.79+ run-parts: executing /etc/kernel/postinst.d/uImage 3.14.79+ /boot/vmlinuz-3.14.79+ run-parts: executing /etc/kernel/postinst.d/uInitrd 3.14.79+ /boot/vmlinuz-3.14.79+ Setting up emby-server (3.1.2-12.2) ... insserv: warning: current start runlevel(s) (empty) of script `emby-server' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `emby-server' overrides LSB defaults (0 1 6). Setting up setup-odroid (0.0.1-25) ... Adding user `nw' to group `tty' ... Adding user nw to group tty Done. patching file c2_init.sh Hunk #1 succeeded at 37 (offset -1 lines). ln: failed to create hard link ‘/boot/initrd.img-3.14.79+.dpkg-bak’ => ‘/boot/initrd.img-3.14.79+’: Operation not permitted update-initramfs: Generating /boot/initrd.img-3.14.79+ Image Name: uInitrd Created: Thu Dec 29 09:49:19 2016 Image Type: AArch64 Linux RAMDisk Image (uncompressed) Data Size: 4239240 Bytes = 4139.88 kB = 4.04 MB Load Address: 00000000 Entry Point: 00000000 patching file boot.ini Hunk #1 FAILED at 53. 1 out of 1 hunk FAILED -- saving rejects to file boot.ini.rej patching file boot.ini Hunk #1 FAILED at 4. 1 out of 1 hunk FAILED -- saving rejects to file boot.ini.rej patching file boot.ini Hunk #1 succeeded at 37 (offset -60 lines). patching file boot.ini Hunk #1 succeeded at 37 with fuzz 2 (offset -60 lines). Hunk #2 succeeded at 70 (offset -60 lines). patching file /boot/boot.ini Hunk #1 succeeded at 87 (offset -60 lines). patching file boot.ini Hunk #1 FAILED at 49. 1 out of 1 hunk FAILED -- saving rejects to file boot.ini.rej