apollon77

Hey, I'm currently using Debian Wheezy Armbian and think on Upgrading to Jessie. This should be no problem using the Upgrade script as in documentation. Now I've seen that also Ubuntu Trusty ist available. Is there an upgrade from Debian Wheezy to Ubuntu Trusty possible? Does it have any consequences? Or should I stay within Debian? And as additional question: I currently backup the following directories: /etc /root /home /var/backups /var/lib /var/local /var/opt /var/mail /srv /opt /usr/local Is this enough? Or how should I backup before such a upgrade procedure? Thank you for your infos. Ingo

Ok, so if I upgrade from Wheezy to Jessie I should check that before rebooting ... correct?! @Igor: Or does that get's corrected automatically by your upgrade-script?

I have that in my /etc/fstab too and on http://www.armbian.com/cubietruck/it is listed as a performance tweak ... When this is needed to do?

How should I do this?! Normally I simply use it :-) I'm not the linux freak :-)

After problems with NAND earlier I changed to /boot on SD-card and root on SATA ... have to check this (should be possible while checking where /boot ist, or ?!) :-) So I assume I need to upgrade to Legacy Jessie first and then change to vanilla kernel by installing uboot , kernel and dtb files? Or change kernel first whicl still on wheezy and upgrade then to Jessie ... correct?

Hi, as I had set up my CubieTruck I decided to go with Legacy Wheezy ... Now I think about become a bit more current :-) Option 1 is to Upgrade to Legacy Jessie ... This is described in the documentation and hopefully should work that way, Correkt? Or Option 2 would be to go to Vanilla Jessie. Is this possible too? How? Thank you for your support, Ingo

Great, worked :-)

I've seen on webpage that there is a new kernel 3.4.109. I'm currently using 3.4.108 and apt-get update/upgrade delivered new root and also new uboot, but noit new kernel ... is this known or "as planned"?

I can remove all other files from sd except /boot ... correct?!

Hm, still not visible when calling "mount" or "df" ... first ... Then I created /media/mmc as direciry and rebooted again ... now it seems to work: root@cubietruck:~# df Filesystem 1K-blocks Used Available Use% Mounted on rootfs 961433632 1830376 910765180 1% / /dev/root 961433632 1830376 910765180 1% / devtmpfs 1023328 0 1023328 0% /dev tmpfs 131072 256 130816 1% /run tmpfs 5120 0 5120 0% /run/lock tmpfs 131072 0 131072 0% /run/shm /dev/mmcblk0p1 30687916 971196 28464012 4% /media/mmc /dev/mmcblk0p1 30687916 971196 28464012 4% /boot tmpfs 1048576 0 1048576 0% /tmp So solved mow. You are great!! Thank you for all your help!!

But to the question from above: When my rootfs comes from sata and I boot from SD - what do I need to have in my /etc/fstab? I thought that I need to mount the "/boot" directory from SD card as "/boot" in my system in order that the files are correctly used for booting AND also for the next kernel-updates or such that modify filesin the "/boot" on SD ... Or do I missunderstand something completely?

when I do this then the system boots but there is nbo /boot mounted ... hm ... which boot files were used now?

And what would be the correct content for /boot for sd? /dev/mmcblk0p1 /boot vfat defaults 0 2 which I found via google :-)

Ok, 1. Done 2. Done 3. first line of boot.cmd is now after change: setenv bootargs console=tty1 root=/dev/sda1 rootwait rootfstype=ext4 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_no_mali_mem_reser ve sunxi_fb_mem_reserve=16 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 enforcing=0 loglevel=1 After this: root@cubietruck:/boot# mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr Image Name: Created: Sat Aug 1 21:30:04 2015 Image Type: ARM Linux Script (uncompressed) Data Size: 1480 Bytes = 1.45 kB = 0.00 MB Load Address: 00000000 Entry Point: 00000000 Contents: Image 0: 1472 Bytes = 1.44 kB = 0.00 MB 4. Were already there 5. Done ... result after reboot: root@cubietruck:~# df Filesystem 1K-blocks Used Available Use% Mounted on rootfs 961433632 1819268 910776288 1% / /dev/root 961433632 1819268 910776288 1% / devtmpfs 1023328 0 1023328 0% /dev tmpfs 131072 252 130820 1% /run tmpfs 5120 0 5120 0% /run/lock tmpfs 131072 0 131072 0% /run/shm /dev/nand1 16334 6010 10324 37% /boot tmpfs 1048576 0 1048576 0% /tmp So effect as before ... Is there any way to check which files used to boot up? Maybe the mountpoint for /boot is stored somewhere on sata and therefor I need to unmount /boot and mount to /boot on sd card one time so that correct files are used?

Yes I want to get away from nand, but I need rootfs on sata because the home-automation applicated make much i/o ... and ideally do not want to need to install everything new :-( Before I changed the boot.scr it was always booted from sd when the card was inserted. Then I changed the rootfs-location and generated new src file and rebooted as you said. Should cleaning /dev/nand1 (where boot is mounted on) bring an effect? Or should I try to resize my sata to have a second partition sda2 and then use fresh sd-boot-image and install to sda2 with script and then change rootfs to sda1 ? Or installing anything new ...?!

How can I see if the boot was done by SD card? I changed that line and recreated the scr-file and rebootet with sd-card in the slot. Reboot was successfull, but /boot is mounted to /dev/nand1 ... ?! So this is not the correct place at latest when an update should be done, or ?!

PS: I hope the "no" meaned that I do NOT need anything special and all updates will work before ...

Thwn I will go that way ... will do tomorrow :-) Thank you for all your help!!

Will all updates and such work after that like normal or do I need to think of special things ?

What would I need to do to boot from sd and use rootfs on sata without ioverwriting all sata content :-) What do I need to change on sd card that rootfs is used from sata?

And while fixing my kernel-update problems I installed the nand completely new from sd.SO it should be the correct one as in the 3.4.108 sd-image. Does the rootfs on sata come into play somehow? I use the Cubietruck for home automation. There are two node.js apps running and I installed ups-tools for my apc. I have set up some "Monitoring" where some ports and the IP itself are "Ping"ed every minute to detect if the port or machine goes offline. But nothing more ...

Did you delete your last post with question on uboot? I had installed new uboot as I tried to upgrade to 3.4.108 from 3.4.107. worked without an error. Then I needed to setup /boot newly from sd with the 3.4.108 image if you remember ... is uboot on that or not?! Do I need to install uboot packet manually now (again)?

Hey Igor, bad news, had the same effect today with kernel 3.4.108 :-( system just halted, no services responded. Just like with 1.3.107 :-( Any idea on it?

Ok, have now installed from fresh sd-image 3.4.108 to nand2. With this nand1 (boot) got newly written too and then I only changed to root in uEnv.txt and everything went well. I only needed to deinstall the only partially installed 3.4.108 kernel-image from hdd and copy the /lib/modules-Files again but after that now my old system is back :-)) Thank you for all your help ... hopefully you can reproduce. I I can help in testing or such simply tell me !

Hm ... it must have been too late yesterday ... On sda1 the lib/modules directory for 3.4.108 exists and has all files. I have now unpacked the 3.4.108 deb file and used the file from there and copied again to nand1. Will try to reboot tomorrow (can't get to the device to get sd card out :-) ).