aristide

Hi Igor, Thank you for your help. After returning from vacation, I tried your suggestion. Unfortunately, something went wrong during the install of the new kernel, and my Cubietruck won't boot. It is set up to boot from nand, with / on SATA (actually three partitions with '/', '/var' and '/srv' on SATA) and /boot on nand. When I boot from an SD-card (old copy I had), I can mount all partitions, and also those from the nand-flash (see listings of files on nand1 and nand2). Is there a way to repair the system without reinstalling everything ? The boot partition on /dev/nand1 is effectively small (32M). May be some files could be deleted, and the partition later be expanded (there seem to be nothing on /dev/nand2, which is over 7G). There might be a problem though on the nand flash. Sfdisk can not list the two partitions on it: Thanks again and best regards 20170801_boot_log.txt dev_nand1.txt

Hi, I found a similar thread about space problem on /boot when upgrading the kernel, but it was with debian jessie, not Ubuntu, and the proposed "trick" doesn't seem to work anymore: This is what I get: Actually, I am facing this problem since I set up my system a year ago, but didn't take the time to solve it. But now, I would like to finish the aimed set up of the device (home server) and would like to get this out of the way. Thanks for any suggestion.

Lately, I had time to try again. I made a backup of the booting sdcard, and then 'apt-get update' and 'apt-get upgrade' with it. Then a backup again and install to nand (boot from nand, root-fs on sata). All went fine, so I cross my fingers and am going on with the wished configuration of my cubietruck. Thank you very much Igor for all your help and your work with Armbian.

I have run fsck on the root fs, it is clean. I hade disabled the 'lirc' daemon by creating the file '/etc/init/lirc.override' (because it reacted to the remote of my tv, which I didn't want ), but no other modification to IR system. I have deleted the file to re-enable 'lirc', but with no success. By doing this, I remembered that modules could be disabled too, so I tried to disable some modules in the file '/etc/modules', and then '/etc/modprobe.d/blacklist.conf', with no success (sometimes, it hangs at another point, but it still hangs ). I guess I have to update my "sdcard-install" and move it to NAND again (I can save an image of my working sdcard in case the update would fail too). Thank you again for your help. I will report back when I am done with the above.

I booted from sdcard and changed the loglevel as you advised. When I capture the boot log with gtkterm, it sometimes add empty lines in the text, so that the log gets very long. I have pasted it to 'pastebin.com', here the link to see it: http://pastebin.com/dyJ1j8qm Thank you for helping.

I don't know how to change loglevel to 9. Is there a "howto" somewhere ? I guess the console is already at serial ttyS0,115200, as I can connect with GTKScreen. Currently, I can't copy/paste the output in a "readable" way (bad encoding) and will try on monday again.

Replaying to myself. I bought a cable to see the output of the serial console to see what was happening (or not ) on the cubietruck after the failed install. Thanks to this thread http://forum.armbian.com/index.php/topic/690-upgrade-error-with-armbian-500-on-cubieboard2-running-from-nand/ I found out, that the upgrade of the kernel failed to create a 'uImage' file on the '/boot' partition and could reboot my cubietruck from NAND. Now it is stucked again. Output of the boot process, short before it gets stucked: I guess the ir-stuff was updated and went wrong. I don't know if it's related, but before the upgrade, I disabled 'lirc' on my device. Is there a way to 'repair' this ? The device is supposed to boot from NAND and '/' is on '/dev/sda1'. I can mount '/dev/sda1' if I boot from sdcard. Thanks in advance and regards Yann

Hi, In december, I was able to install a working system to nand (boot from nand, system on sata), but didn't have the nessery time to finish the configuration. Today I rebooted my cubietruck for the first time since then, and tried updating all the installed packages with 'apt-get update and apt-get dist-upgrade'. One of the updates (an important one, see below) failed with the following error: and: Confident as I am, I rebooted the device. Unfortunately, it does not come up as expected. I still have the SD-card used for the install in december (and can boot the cubietruck with it), so I could start from scratch again. But may be there is something I could do to "save" the NAND/SATA installation. Sorry if a solution to this problem has already been posted, I didn't find one. Thanks and regards Yann