Articles Hierarchy

Articles Home » RPI » RPI System Update

RPI System Update

summary:
new berry boot
2014 raspbian (no noobs) and install script
2015 raspbian (no noobs) and SD cards / partitions, SD read/write speed
ext HD
import raspbian to berryboot
berryboot bootmenu remote
NOOBS bootmenu remote
summary: multiboot, custom OS, bootmenu remote

new berry boot
prior BLOG about RPI system update, and RASPBIAN image versus NOOBS versus Berryboot here
Now i have following situation:
- the new install script installall.sh
and the installed projects needs to be tested
- i see there is some update from RPI and also from BERRYBOOT and i want give it a try again.

for RPI there is no version number system, just a date mentioned..
Raspbian / Debian Wheezy / Version: December 2014 / Release date: 2014-12-24
downloaded file: 2014-12-24-wheezy-raspbian.zip 1.007GB ( not NOOBS )


for Berryboot: berryboot-20140814.zip 29.5MB
i not find the list what is the actual RASPBIAN you will download from that site.
i use a good 16GB card / SD format / unzip to it. on HDMI TV and WIFI download
- Snowshoe ( test again for just smart TV )
- RASPBIAN 2014.06 831MB
the Snowshoe download worked, the OS not, still same bullshit with URL line calling hundred time google..
the RASPBIAN download i try 6 times, did not work, a restore of a old backup from USB stick worked but the boot hang at a camera error??
now i try download from sourceforge here and copy to USB stick, but 10 more tries / changing mirror.../ also did not work.
its a waste of time!
ok, after 3 days/20 more tries i got the Berryboot Debian_Wheezy_Raspbian_2014.06.img192 872MB
make the SD card with berryboot, and boot it, format SD and restore from USB stick to SD and boot was ok, even impressive write speed ( USB stick to SD ), it not makes up the hours getting the image.
on the next boot it hang again with the camera LED on ( i enabled the camera at raspi-config ) is there a bug?
but i try again and start working on the system.
incl. below dist-upgrade... looks good, so finally i have a berryboot SD system running.


new raspbian (no noobs) and install script
if you want look about raspbian revision history and if there's a new one: see here
and while that download is running i can burn a other 8GB SD card / SD Format / with
Win32 Disk Imager ( after UNZIP the newest RASPBIAN now 3.27GB)
boot, setup config ok
new look indicates that here we have a real change!


so back on the SSH / PUTTY i try my
./installall.sh virginRPI
manually:
vncserver :1
pw enter pw enter n enter
sudo reboot
start VNC viewer to 192.168.1.101:1, pw and see:



sudo nano .config/lxterminal/lxterminal.conf font size [14] for terminal and MC ( via VNC needed)
sudo nano /boot/config.txt buy/use your own codec / this only works for my RPI cpu
# video codec KLL
decode_MPG2=0x75131f48
decode_WVC1=0x79d39575
# take control of red camera LED
disable_camera_led=1

more info here

myTOOLs_installation:
./installall.sh pycaminst and test one snapshot
./installall.sh pyaudioinst and test keyboard
./installall.sh installPID and start arduino IDE



but actually i noticed that i can not answer following question:
if i not get the update from RASPBIAN, but i do the UPDATE / UPGRADE on a older system,
will it be same? or is a new RASPBIAN release like a WIN7 to WIN8 ...
so, here i now find the answer:RPI say:
Update: we just released a new version of Raspbian! Its available on our downloads page and if you already have a previous version, you can get the update by entering the following commands in your terminal:
sudo apt-get update
sudo apt-get dist-upgrade
sudo apt-get install raspberrypi-ui-mods

i try that on a older SD with a 09 / 2014 RASPBIAN
ok, don't forget the
sudo reboot but then see

here i noticed that the change from MIDORY to EPIPHANY is not done by the dist-upgrade, so need additionally: ( installes a lot of GNOME... )
sudo apt-get install epiphany-browser
sudo apt-get purge midori
sudo rm /home/pi/Desktop/midori.desktop
sudo reboot

a test with a 2013 RASPBIAN show that the dist-upgrade not work from there??


2015 raspbian (no noobs) and SD cards / partitions, SD read/write speed
i see a new raspbian version from 31.1.2015 and i download the 2015-01-31-raspbian.zip 1024MB
i burn it ( Win32DiskImager ) to a 8GB SD card, ( setup from HDMI TV )
fix IP and install xrdp only. ++ update upgrade.
now from that i made a backup ( again Win32DiskImager )
Now there was a ongoing discussion about SD cards... in forum
and i wanted to test something.
from the forum info and speed tests thinking is now that the very expensive and fast cards are not required for RPI.
And i have no idea how valid my SD benchmark is:
a not tuned system on any SD card, and a file about a size of 10MB,
and a copy of it from SD to ramdisk ( /run/shm/ ) ( READ TEST )
and a copy of it from ramdisk ( /run/shm/ ) to SD ( WRITE TEST )
using the command:
rsync -ah --progress /run/shm/10mbtestfile ~/10mbtestfile ( for the write test )
will show a 6 .. 15MB/s speed Class 4 .. Class 10 ( U3 ) or higher
where 15MB/s is my read speed by a USB ( 2.0 ) card reader to PC too.
and it looks like much higher ( up to 20MB/s ) possible with CPU tuning.
what looks nice but i have the idea that THAT is very questionable.
that 2 speeds ( cpu and SD card ) should not be linked by the same clock??
or better, if linked still should have separate tuning variables.
But what i know, there can be much more dependencies i not understand.
( there was talking at the RPI beginning and overclocking test that SD cards died...
now solved see here)
Think about it, you buy a new / faster cpu for your PC and then the hard disk spins faster??
but here is the question, i do not know where is the bottleneck? the cpu or the SD card link
anyhow, in both cases its useless to buy very expensive SD cards.
here again my ( much lower ) data ( using a old RPI B )
SanDisk Ultra U1 16GB micro SD HC I___write 7.47MB/s - read 9.13MB/s
SanDisk Ultra 8GB (10) micro SD HC I___write 7.47MB/s - read 8.42MB/s
Kingston 8GB (4) micro SD HC_________write 7.39MB/s - read 8.36MB/s
Apacer 8GB (10) micro SD HC__________write 6.37MB/s - read 7.95MB/s

But the size matters!
mostly we go for 8GB SD systems / that's reasonable for raspbian system, for backup / restore,
but prizes drop, and when a 32GB is cheaper as 2 16GB , but 2 32GB cheaper as a 64GB, its clearly ( USD / GB ) a best buy
but as i also compare the prize range for the different types 0.65USD to 4USD / 1GB you must look closely that you compare the same types. ( example i not see sandisk PLUS cards here, but same type named for CAMERA or SMARTPHONE ??? whatever that could mean in spec.
from a internet source (02/2015)
SanDisk - 32GB SDSDB-032G-B35 Secure Digital High Capacity (SDHC) Card Class 4
21.00USD
SanDisk - Ultra 32GB SDHC UHS-I Class 10 Memory Card - Black/Gray/Red
24.99USD
SanDisk - Ultra Plus 32GB SDHC Class 10 UHS-1 Memory Card - Black/Gray/Red
24.99USD
SanDisk - 32GB Ultra Secure Digital High Capacity (SDHC) High Performance Card Class 6
27.79USD
SanDisk - Extreme 32GB SDHC Class 10 UHS-1 Memory Card - Black/Gold
27.99USD
SanDisk - Extreme PLUS 32GB microSDHC UHS-3 Class U-3 Memory Card - Red/Gold
34.99USD
SanDisk - Extreme PLUS 32GB SDHC UHS-3 Memory Card - Black
39.99USD
SanDisk - Extreme Pro 32GB SDHC Memory Card - Black/Red
39.99USD
SanDisk - Pixtor 32GB SDHC Class 10 Memory Card - Black/Red
69.99USD
SanDisk - Pixtor Advanced 32GB SDHC Class 10 UHS-3 Memory Card - Black/Gold
97.99USD
SanDisk - Extreme PRO 32GB SDHC/SDXC Class 3 UHS-II Memory Card - Black/Red
129.99USD

Now as i buy a new mobile for the GF ( quad cpu / 1GB ram / kitkat ) and she seems to use camera... i need anyway a bigger / better SD card, and also can test it here.
despite the above list about sundisk cards i go for that one, 20USD.

and that is what i want to test first, use the 8GB image of the already setup new system and store it to the 32GB card.

system runs, first do that SD speed test again:

Samsung EVO U1 32GB micro SDHC UHS-1 / Class 10 U1___write 6.67MB/s - read 7.76MB/s
not impressive at all.
pls see, when i burn the SD card i had a 13MB/sec PC .. USB,..cardreader .. SD card, so its definitely a hardware thing, and has nothing to do with the card not able for 48MB/s
and now same test ramdisk and to / from the

Kingston 8GB USB stick_______________write 6.63MB/s - read 7.89MB/s

and just for curiosity, a other SD card in the card reader connected to RPI / like the USB stick,
Apacer 8GB (10) micro SD HC__________write 7.44MB/s - read 8.34MB/s
( VIA card_reader faster as used as system SD)

still all only half of the speed compared to info from ktb in forum but he also uses the RPI 2 in some of the tests. hmmm
more SD card info here


i see no other way as to play with that overclocking on my own card:
on a original / non overclocked system i run that SD read / write 10MB file again
SD card: Apacer 8GB (10) micro SD HC
i do: sudo raspi-config overclocking:
NONE i did this to check, now i see in cat /boot/config.txt
arm_freq=700 / core_freq=250 / sdram_freq=400 / over_voltage=0
write 7.01MB/s / read 7.90MB/s
MODEST
arm_freq=800 / core_freq=250 / sdram_freq=400 / over_voltage=0
write 7.45MB/s / read 8.29MB/s
MEDIUM
arm_freq=900 / core_freq=250 / sdram_freq=450 / over_voltage=2
write 7.91MB/s / read 8.80MB/s
HIGH
arm_freq=950 / core_freq=250 / sdram_freq=450 / over_voltage=6
write 8.07MB/s / read 9.45MB/s
TURBO
arm_freq=1000 / core_freq=500 / sdram_freq=600 / over_voltage=6
write 10.66MB/s / read 12.06MB/s
NONE
arm_freq=700 / core_freq=250 / sdram_freq=400 / over_voltage=0
write 6.92MB/s / read 7.74MB/s
now that was a test with my working card, it was anyway the slowest, and has lots of installs, like webserver..running
now the new Samsung EVO U1 32GB micro SDHC UHS-1 / Class 10 U1
arm_freq=800 / core_freq=250 / sdram_freq=400 / over_voltage=0
?why that is on MODEST setting already?? i did not do! ( and why i checked? )
NONE
arm_freq=700 / core_freq=250 / sdram_freq=400 / over_voltage=0
write 6.91MB/s / read 8.15MB/s
TURBO
arm_freq=1000 / core_freq=500 / sdram_freq=600 / over_voltage=6
write 10.52MB/s / read 12.12MB/s
no differences between the cards. ( set back to MODEST )


test1 enlarge system partition by raspi-config

with sudo raspi-config
i try use the full SD card.



test2 add a data partition
overwrite the card with same image again.
now i want try to use the rest of the card as a new partition ( first try!! )
step-1-
check on existing partitions
sudo fdisk -l
make a partition:
sudo fdisk /dev/mmcblk0
p -- show partition
n -- new partition
p -- primary
3 -- new partition number
15523840 -- as my mmcblk0p2 ended with 15523839
return -- for default 61407231 ( end of 32GB?? ) here i made a mistake: if you make some MB smaller its more likely you can use it on a other SD card too while restore!
p -- show new / future partitions
w -- write what you have done
step -2-
make a file system
mkfs -v -t ext4 /dev/mmcblk0p3
step -3-
try to mount it
cd /mnt/
sudo mkdir data
sudo mount -t auto -v /dev/mmcblk0p3 /mnt/data
... i will try ext4
df -h very good 22GB "drive"
additionally adjust
sudo chmod -Rv 777 /mnt/data
sudo chown -R pi:pi /mnt/data
step -4-
sudo nano /etc/fstab
new line 4
/dev/mmcblk0p3 /mnt/data ext4 defaults 0 0

and test with
sudo reboot
i am very lucky!!!

here a short ref to the web links i used for info:
Link Link Link


ways of BACKUP
at first i take the card to a card reader and on PC try a win32diskimager
45min, get a 32GB file, but can zip it down to 2.1GB in a hour more.
take the cardreader to RPI, and cleanup the usb stick, and use a other SDsystem

where sda1 2 3 are the 32GB card partitions.
now i try to backup only that 7..GB system partition with linux tools.
first i go
cd /media/KINGSTON/ my place for the backup file
sudo dd bs=4M if=/dev/sda2 of=32GBp2.img but expecting it could fail because of size problems ?stick is FAT32.
yes, he copied 4.3GB ( at 10MB/s ) and stopped. next try
sudo dd bs=4M if=/dev/sda2 | gzip > /media/KINGSTON/32GBp2.img.zip
7.9GB copy to 2.1GB in 7046sec at 1.1MB/s
sudo dd bs=4M if=/dev/sda1 | gzip > /media/KINGSTON/32GBp1.img.zip
59MB copy to 12MB in 28sec at 2.1MB/s
sudo dd bs=4M if=/dev/sda3 | gzip > /media/KINGSTON/32GBp3.img.zip
23.5GB copy to 22.8MB in 4344sec at 5.4MB/s
WTF, for backup a empty partition??
well, you never know, it might be that it has no data now, but it contains all above work!!
but most likely it will be usable on the very same SD card only. while the restore of 1 and 2 might make a 8GB card running??
and "dd" is a low level tool, it might even backup deleted files..
but besides the "dd" i see this, looks interesting, esp. because i hate to sit in front of a frozen terminal ( for hours ), not seeing any progress...
( ok in a second putty window can start a "top" to see if still something is running ( zip 94cpu%) and with "ls -l /media/KINGSTON" i can check the file growing)
anyhow, i would say PC / Win32Dinsimager / ZIP is the winner, but only about time ( < 2h ),
the main idea here was just to create and backup a smaller system partition! and a separate data partition on SD cards bigger as 8GB .so --> better use a linux PC for the backup!
a other interesting tool see here, will check later.

this was a good day play linux, and i know i am still far from a system administrator,
but i feel, thanks to RASPBERRY PI i know more about linux now, as i learned in 25 years using windows PCs.


ext HD
as the work with SD image and only 8GB USB stick is difficult i think for the first time to
connect a BIG drive to transport between WIN7 PC and RPI.
and as usual, nothing is easy.
when i boot the RPI something was very slow.. but i see the drive in file manager
but a copy to that drive did not work "permission" but even with sudo not.
so i try to look at it with "ls -la /media/Iomega HDD/" and got the error Iomega not found
the " " in the name seems not nice for debian.
so back on win7 i go drive properties and give it a better name

back on RPI the ls -la works, but still can not copy/write.
googling i found lots of info about mount / remount, sudo mount -o remount,rw /...
that a drive is mounted as read only because it has errors..
but that was not of help.
in a raspberry forum post i see very small note:
What have you tried so far?
(I'm going to guess that the magic bullet you are looking for is: apt-get install ntfs-3g)

thats the funny thing, RPI can read NTFS drives little bit but you must do this install if that's the problem, but how to know?

if you type
mount
and find in the long list
/dev/sdb1 on /media/MYDRIVE type ntfs (ro ....

do a
sudo apt-get install ntfs-3g
sudo reboot
and check again with
mount
i see
/dev/sdb1 on /media/MYDRIVE type fusectl (rw ....
and the copy / write works fine.
so much for USB PLUG AND PLAY
and a short speed check here too:
write from SD to HD 2.57MB/s, read from HD to SD 7.39MB/s


import raspbian to berryboot
after now i am more lucky with the linux tools, and i have a linux debian ( amd 64 ) on a harddisk for my PC
i want try something again:
BERRYBOOT and the idea to add the newest debian raspbian (01/2015) ,
what i just setup, update and backup, following this
on the DEBIAN LINUX PC:
sudo apt-get update
sudo apt-get install squashfs-tools
sudo apt-get install kpartx


now, the manual looks so easy, but first point: where i get the image from?

-01-
i try a copy of the dd zip i made yesterday copy USB stick copy LINUX PC, unzip ERROR

-02-
use .tar.gz from win PC on a new good SD image 8GB, copy USB stick, boot linux,
unzip with
tar -xvzf SD_8GB_debian2015_fixIP_xrdp_update.tar.gz -C .

sudo kpartx -av SD_8GB_debian2015_fixIP_xrdp_update.img
add map loop0p1 (254:0): 0 114688 linear /dev/loop0 8192
device-mapper: resume ioctl on loop0p2 failed: Invalid argument
create/reload failed on loop0p2
add map loop0p2 (0:0): 0 15400960 linear /dev/loop0 122880


sudo mount /dev/mapper/loop0p2 /mnt
mount: special device /dev/mapper/loop0p2 does not exist

and the kpartx failed as i see so many times in forum questions.

-03-
but i found a workaround in web:
here
he make a image of a SD and burns it on a USB and mounts it from linux computer
hmm, he might be dirty, but i am lazy!
on my PC booting from the debian linux HD i just use cardreader with the RPI SD card, hotplug: and filemanager comes up with all partitions
/media/1263ae8d-aaf3-41b6-9ac0-03e7fecb5d6a is the RPI system partition
sudo sed -i "s/^\/dev\/mmcblk/#\0/g" /media/1263ae8d-aaf3-41b6-9ac0-03e7fecb5d6a/etc/fstab
seems ok, and now
sudo mksquashfs /media/1263ae8d-aaf3-41b6-9ac0-03e7fecb5d6a debian_to_berryboot.img -comp lzo -e lib/modules
even see a progress bar, ? <10 min
Parallel mksquashfs: Using 2 processors
Creating 4.0 filesystem on debian_to_berryboot.img, block size 131072.
[=================================================================================================\] 74550/74550 100%
and at the end a long list???
Exportable Squashfs 4.0 filesystem, lzo compressed, data block size 131072
compressed data, compressed metadata, compressed fragments, compressed xattrs
duplicates are removed
Filesystem size 1185655.75 Kbytes (1157.87 Mbytes)
48.81% of uncompressed filesystem size (2429318.42 Kbytes)
Inode table size 1109787 bytes (1083.78 Kbytes)
36.94% of uncompressed inode table size (3003898 bytes)
Directory table size 972836 bytes (950.04 Kbytes)
47.61% of uncompressed directory table size (2043540 bytes)
Number of duplicate files found 2923
Number of inodes 83814
Number of files 60877
Number of fragments 4989
Number of symbolic links 16590
Number of device nodes 81
Number of fifo nodes 1
Number of socket nodes 1
Number of directories 6264
Number of ids (unique uids + gids) 29
Number of uids 10
root (0)
man (6)
hplip (107)
kll (1000)
unknown (2625)
libuuid (100)
messagebus (102)
colord (103)
usbmux (106)
unknown (114)
Number of gids 28
root (0)
lpadmin (108)
video (44)
audio (29)
tty (5)
kmem (15)
disk (6)
adm (4)
shadow (42)
colord (107)
bluetooth (110)
kll (1000)
unknown (2625)
users (100)
utmp (43)
crontab (102)
fuse (103)
messagebus (106)
unknown (1001)
staff (50)
unknown (124)
libuuid (101)
ssl-cert (109)
nogroup (65534)
avahi-autoipd (104)
netdev (111)
uucp (10)
mail (8)

anyhow, that file
ls -la debian_to_berryboot.img
-rw-r--r-- 1 root root 1214111744 Feb 15 02:54 debian_to_berryboot.img
i copy to USB stick

on TV ( HDMI monitor ) with the RPI and the berry boot SD ( my "big" 16GB ) and usb stick
i boot berryboot / edit menu / press mouse add OS from file /
find the file on USB stick, OK
write system to SD card very fast: < 10min
EXIT boot
and i have the newest RASPBIAN in berry boot.
i hope one of the specialists from the forum can verify that idea,

and now i understand the "sed" a little bit and to use the SD again i needed to delete in the 2 or in my case 3 lines the "#" at the beginning ( anyhow RPI booted but it did not show my /mnt/data/ partition ( under that name ) ( but as it booted i could do the change back under running conditions,
i not needed to go back to linux PC for it. anyhow better do a backup of the file first
? or i need to test, forget even the sed command line and just rename the
/etc/fstab to /etc/fstab.org, so it will not conflict with berryboot and still SD might work

here a snap from the berryboot system booting with the updated raspbian as default
on headless working, the raspbian had the xrdp installed already.


what i see now is the "sed" edit /etc/fstab and a /etc/.fstab
was that existing or made by berryboot?

i wish i know what i am doing here

p.s. with NOOBS also can do this see here


that all looks too easy now, and from the forum i not got a confirmation about that,
so i just try again, i use my "work" 8GB SD ( as i need a backup of it anyway, and want play with NOOBS on it later)
and want transfer it to the same 16GB berryboot SD system.

back on the debian linux PC:
use 8GB SD work ( Apacer ) in card reader
backup / remove fstab
sudo mv /media/c1398422-7a7c-4863-8a8f-45a1db26b4f2/etc/fstab /media/c1398422-7a7c-4863-8a8f-45a1db26b4f2/etc/fstab.org
make berryboot image
sudo mksquashfs /media/c1398422-7a7c-4863-8a8f-45a1db26b4f2 debian_to_berryboot2.img -comp lzo -e lib/modules
8 min 1.9GB image
copy to USB 3min

boot berryboot on TV
edit menu
import image from USB 4min
set default exit boot
complains about missing fstab but boots
wlan internet connection ok and actually looks like
the berryboot wpa_supplicant.conf works ( from berryboot partition )
my new interfaces fix ip eth0:101 wlan0 102 ( from new imported partition )
and see later, the USB stick was found!

now test to boot the "modified" SD i copy from:
complains about missing fstab but boots
but the USB stick was not mounted.. so undo the change i did for copy berryboot
sudo cp /etc/fstab.org /etc/fstab
sudo reboot ok
pls note, the result is that the system now sees the USB stick again, but there is no fstab entry for the stick! ??
internet via wlan ok
summary:
the fast easy way to convert a raspian SD system into a berryboot partition works,
and the timing
8min ( PC squashfs (directly from card reader) ) + 3 min ( PC usb copy ) + 4 min ( RPI berryboot import )
is remarkable!


not yet ready to play more with NOOBS,
i think you think you have only a windows computer and can not do above,
actually you lie, there is a RPI? it run linux, why he can not do it?
-a- install squashfs
sudo apt-get update
sudo apt-get install squashfs-tools

-b- look where is the usb card reader and the SD RPI system
copy and sed the fstab again
sudo cp /media/c1398422-7a7c-4863-8a8f-45a1db26b4f2/etc/fstab /media/c1398422-7a7c-4863-8a8f-45a1db26b4f2/etc/fstab.org
sudo sed -i "s/^\/dev\/mmcblk/#\0/g" /media/c1398422-7a7c-4863-8a8f-45a1db26b4f2/etc/fstab

now we try make the image directly to a USB stick, because there might be no other space here.
sudo mksquashfs /media/c1398422-7a7c-4863-8a8f-45a1db26b4f2 /media/KINGSTON/IMAGE/debian_to_berryboot3.img -comp lzo -e lib/modules
3h45m for the 1.9GB image
yes, its slow, but you see the progress and with a other putty window can see the file grow on the USB stick.
( i used the MEDIUM tuned berryboot system from below, just moved the log text up here )
In forum i see a remark you could simply add/copy the image file to the berryboot SD ??
and it would come up in the boot menu, check that too, but for that i need to switch the 2 SD cards first, boot the one i just backup, and copy from USB directly to berryboot ( in USB card reader ).
i found that berryboot image storage at /media/usb1/images/
if no space you need to delete a old one first.
but if you are in a hurry, better use a PC, i also tested a linux USB stick see here
still i did the 2 step: squashfs SD to USB, copy to berryboot SD
you can do all in one step IF you have 2 cardreaders ( and not use data USB stick or harddisk..).
to use above copied system you need to berryboot bootmenu newsystem SET DEFAULT.


today i see that at berryboot anyhow the new
- berryboot PI 2 ( not as upgrade, its separate ) and the
- 2015raspbian
is available: OS list


UPDATE 21.09.2015
i try again but test RPI2 for this?
a usb card reader with a good RASPBIAN only plus CAM SERVER,
to free that SD card and have a backup of that good setup in a berryboot SD.
( while that berryboot and RPI camera setup is all for RPI1B )
sudo apt-get update
sudo apt-get install squashfs-tools
# not need sudo apt-get install kpartx

no problem
plugin SD card reader and find Raspbian root as
/media/13d368bf-6dbf-4751-8ba1-88bed06bef77
make a backup of the fstab file
sudo sed -i "s/^\/dev\/mmcblk/#\0/g" /media/13d368bf-6dbf-4751-8ba1-88bed06bef77/etc/fstab
looks like
cat /media/13d368bf-6dbf-4751-8ba1-88bed06bef77/etc/fstab
proc /proc proc defaults 0 0
#/dev/mmcblk0p1 /boot vfat defaults 0 2
#/dev/mmcblk0p2 / ext4 defaults,noatime 0 1
# a swapfile is not a swap partition, so no using swapon|off from here on, use
dphys-swapfile swap[on|off] for that
cd /media/usbstick/berryboot go to a dir at usbstick ( so later not need copy )
sudo mksquashfs /media/13d368bf-6dbf-4751-8ba1-88bed06bef77 RPICAM_to_berryboot.img -comp lzo -e lib/modules
and my xrdp and putty window closes.
i try again from /home/pi/.. but again stopped after some seconds.
so i hoped i can beat that 3hour test for RPI1B, but not lucky.


back to the linux PC ( debian on a old HDD )
same commands, just copy from here worked and now i also try to do that with a noobs SD:

# noobs SD in card reader
sudo cp /media/root/etc/fstab /media/root/etc/fstab.org
sudo sed -i "s/^\/dev\/mmcblk/#\0/g" /media/root/etc/fstab
cat /media/root/etc/fstab
sudo mksquashfs /media/root noobsnoir_to_berryboot.img -comp lzo -e lib/modules
sudo cp /media/root/etc/fstab.org /media/root/etc/fstab
sudo umount /dev/sdc6 ...
# use berryboot SD
sudo cp noobsnoir_to_berryboot.img /media/berryboot/images/



berryboot bootmenu remote
if you work like me headless / remote,
there is no much use in a RPI SD system noobs or berryboot with a bootmenu to select operating systems,
unless you can select them also remote
here i try again for berryboot
but first i try to log the info about the different partitions berryboot and Raspbian ( noobs later )
RASPBIAN

BERRYBOOT

in berryboot the /boot/ is empty, the berry "boot" is under /mount/xxxxxxxx/
and there find the files cmdline.txt
smsc95xx.turbo_mode=N elevator=deadline quiet bootmenutimeout=10 datadev=mmcblk0p2
i changed see here to
smsc95xx.turbo_mode=N elevator=deadline quiet bootmenutimeout=10 datadev=mmcblk0p2 vncinstall ipv4=192.168.1.101/255.255.255.0/192.168.1.1
pls note: that is ONE LINE only, delimiter is space.

and the file config.txt i added my new tuning
#KLL tuning MEDIUM
arm_freq=900
core_freq=250
sdram_freq=450
over_voltage=2

# KLL
decode_MPG2=0x75131f48
decode_WVC1=0x79d39575
# take control of red camera LED
disable_camera_led=1


ok, now with the vncinstall in the berryboot boot cmdline.txt
you can now login remote into the bootmenu, but
-a- VNC must be adjusted OPTIONS / expert / FullColour TRUE
-b- timing: you can adjust a longer time in bootmenu as 10sec
start the VNC adjust IP

( without the :1 you use for remote loging raspbian

)
and press connect nearly same time, when you powerup the RPI

and use EDIT if you want to backup, delete, add OS or change parameters: set default, edit tuning

i wonder if NOOBS can do this too?


NOOBS bootmenu (remote?)
for starting a new NOOBS project i use the ( nearly new ) 32GB samsung EVO class 10
means format it first.
SDFormatter V4.0 option setting FORMAT SIZE ADJUSTMENT ON
get latest NOOBS / Offline and network install / Version: 1.4.0 / Release date: 2015-02-18
( 2 .. 3 h )
so have time to work here:
see here under Advanced Usage (for experts and teachers) / How to create a custom OS version
... copies created from your custom OS version (these instructions assume you're only using a single OS at a time with NOOBS - they won't work if you're running multiple OSes from a single SD card). could mean also not working with copy from a NON NOOBS raspbian SD? hmmm
anyhow it means there is no way of backup/restore in NOOBS like in berryboot.

first i wanted to use a old NOOBS SD and try do that copy job,
while the download is running on the win7 PC i connect card reader with NOOBS system SD to RPI, but not lucky, not find a old NOOBS SD, better anyway use new system only.

first download did not work ( stop 130MB), try again, second download failed ( stop 550MB), now try the TORRENT, 6 times the speed,ok
the unzip to the new formatted SD first give me some errors, have too try 3 times.
just to test the multiboot i copy the Raspbian 2 time with new name / and change in os.json
but i not see it when i boot NOOBS, only see raspbian, data, scratch
also because on the TV i can only use the WIFI / and that's not enabled at NOOBS boot menu
and i made some mistake with the copy setup.
and, as i enabled the data partition i possibly violated the a single OS rule??
here the info "mount" and "df -h" of the noobs SD card in card reader "sdb_"

sdb6 the boot
sdb7 the root with 27GB ( i did not use the extend file system in raspi-config !)


i think i have to do it again, on a 8GB card and without the data partition thing.
setup and info

and look via card reader

now i have a installed NOOBS single OS system ( already setup little bit with fix IP, MC, XRDP ) on a 8GB SD card
and i will follow the above manual to make a NOOBS multiboot custom OS on a 32GB card.
when you look forum .. you find questions like it not worked, and answers like it does work,
never talking about the situation.., like the manual is also not precise about that!
( like i try it from a linux PC via card reader and it did not work.. i have to learn much more)
the chapter How to create a custom OS version with point 1 .. 9
talks about work assuming
- PC with WINDOWS or LINUX,
- internet connection for download newest NOOBS
- card reader and SD card ( i would say for multi OS start with 16GB... )
- SD formatter software win / mac here
- unzip software

until it comes to the critical part
9 i and 9 ii
what suddenly assumes you work

- on a RPI, ( and not on the PC with card reader on the OLD SD card )
- with the NOOBS single OS system, ( i used the just setup 8GB SD card system )
it also does not mention:
- i think there should not be any USB drive mounted / or need to --excluded them
- i think there must be used only 40% of the root space + 40% TAR + 20% XZ, and at the end of XZ job the TAR is deleted
- it assumes you recorded the size of the tar files ( between the tar and the xz job )
- and also recorded the partition size
- and no word that the XZ (root) might take 4 hours
and it also not mention that the resulting 2 XZ need to be copied back to the PC to go on with the making of the new SD.

using on RPI ( running "old ( 2 hours) " single OS NOOBS )
sudo -s
cd boot

tar -cvpf boot_work.tar .
works fast and gives a 15MB file, please note the "." needed at the end
xz -e boot_work.tar
gives a 10MB file and the TAR is deleted.
cd ..
i see a other funny point, the manual show a command at the end of a english sentence and finish the sentence with a ".",
well i got a file named boot_work.tar..xz LOL
but only after i deleted the "-9" what give me xz: cannot allocate memory ( default is "-6" )

now i should do
tar -cvpf root_work.tar /* --exclude=proc/* --exclude=sys/* --exclude=dev/pts/*
but i try a different command ( from forum / its little bit smaller file then and see also here):
tar -cvpf root_work.tar --one-file-system /
and a
ls -la show
2452162560 root_work.tar

xz -e root_work.tar
daytime it shutdown ?overheat? at XZ 450MB, i deleted and try again.
it worked after 4h at the second try at night time.

copy the 2 XZ files and the recorded info to PC
copy into 32GB SD card ( via card reader ) inside a
/os/Raspbian_work/ directory ( what i copy from /os/Raspbian/ )

edit partitions.json using names "root_work" "boot_work"
14909440 boot_work.tar --> in partitions.json : "uncompressed_tarball_size": 15, "partition_size_nominal": 60,
2437324800 root_work.tar --> in partitions.json : "uncompressed_tarball_size": 2438 "partition_size_nominal": 6300,

edit os.json
"name": "Raspbian_work",
"description": "my old ( single OS NOOBS ) system",

rename flavours.json to flavours.json.notused

i forget to change the icon name, so i not see any icons at install and boot select:
Raspbian.png to Raspbian_work.png
but i think i still can do now / in the SD root / recovery /os/Raspbian_work/ .

here a snap of the boot install menu after 5 min of resizing recovery??

the erase/rename of the flavours.json to .notused in Raspbian_work worked well (that in Raspbian is still active )
and i could select the new and the old Raspbian and the extracting of 2 filesystems of about 5GB needed 30min.
both systems work ( via boot menu on TV )

i think an other time i should try again using a linux PC and copy and zip from SD via card reader
directly to the new SD in a second card reader / like on my laptop.
but need to find the correct TAR commands from there.
and hopefully one day there is info how to do it from a multi NOOBS OS system to a new SD, and
also from a RASPBIAN only SD.
the SD from card reader looks like this:



for the remote operated boot selection looks there is a way like here:
How to bypass the Recovery splashscreen and boot directly into a fixed partition
Add a text file named autoboot.txt to the root directory of NOOBS.
Add boot_partition= to the file and save it to disk.

like 5 of "/dev/mmcblk0p5"
does that mean you can not reboot and select from VNC... but you can modify that file and reboot.
have to try now as i work headless only.

but first i get confused, i see in
/media/SETTINGS/
is that the root directory of NOOBS?

should i add the file there or just edit noobs.conf?
no, i think it must be in in sdb1 what i not see from here???
but i see the recovery / root / partition from windows, i try here:

and i ended up in my WORK system,
but could not find anything else:
not see my USB stick, the NOOBS recovery boot , the NOOBS SETTINGS

the idea to edit the file from here and just reboot might not work.
GRRRR! again, the manual not say exactly where you have to go, what situation you have to be in, to make / change that file.
anyhow, i not yet tested if that file worked, so mod the card from windows again
change to =6 ( boot partition of the new system )
but there is nothing installed / i not even did the raspi-config from TV, so first must find IP.. ( router / status / DHCP clients )
putty login ok

the file thing worked, just hope your RPI / SD card / is not too far away.
but again i try to change that autoboot.txt file from running situation:
boot noobs32 part 8 ( Raspbian_work )
sudo -s
mkdir /mnt/recov
nano /etc/fstab

new line4:
/dev/mmcblk0p1 /recov vfat defaults 0 0
mount /dev/mmcblk0p1 /mnt/recov
check with
df -h
cd /mnt/recov
cp autoboot.txt autoboot.txt.8
cp autoboot.txt autoboot.txt.6
nano autoboot.txt.6
change 8 to 6
cp autoboot.txt.6 autoboot.txt
reboot

did work, now here ( noobs new system ) do again:
sudo -s
nano /etc/fstab
new line4:
/dev/mmcblk0p1 /recov vfat defaults 0 0
mkdir /mnt/recov


( on both systems also can make a bash (.6) or (.8))
nano bootchange.sh
sudo mount /dev/mmcblk0p1 /mnt/recov
sudo cp /mnt/recov/autoboot.txt.6 /mnt/recov/autoboot.txt
sudo reboot

chmod +x bootchange.sh
./bootchange.sh

as i still have no fix IP on the new system i have to play with the putty login IP each time i change


summary: multiboot, custom OS, bootmenu remote
now, this was a long way for me to use berryboot and noobs as
+ MULTIBOOT
++ bring in a custom OS ( limited with NOOBS to a copy from a NOOBS single OS card )
+++ and even do the boot selection from remote
while for the experts that all seems to be very easy: here DougieLawson write "The only justification for multi boot managers like Berryboot or NOBS is if you are tens of miles or more from your RPi."
hm, i better say nothing
But how about that idea:
you build a ROBOT with a RPI what changes the SD card in an other RPI:
make a RPI SD REVOLVER


UPDATE 22.09.2015
as i just play again with convert raspbian and noobs raspbian to berryboot images ( using a debian PC )
i want a full update on the BERRYBOOT and just as a general idea use berryboot as a backup system
because i noticed i have some unused SD cards but i did not dare to overwrite them and not see it as useful to image them to PC.
-a- get the newest berryboot system
berryboot-20140814.zip
berryboot-20150916-pi2-only.zip
but want use RPI1B only for this.
-b- format and setup my samsung 32GB SD with berryboot-20140814.zip (unzip )
-c- edit / add ( RPI1 tuning )
MODEST: arm_freq=800 / core_freq=250 / sdram_freq=400 / over_voltage=0
config.txt#KLL modest tuneing, codec and led setup
arm_freq=800
decode_MPG2=0x75131f48
decode_WVC1=0x79d39575
# take control of red camera LED
disable_camera_led=1

edit / add vncstartup for fix IP
cmdline.txtsmsc95xx.turbo_mode=N elevator=deadline quiet bootmenutimeout=10 vncinstall ipv4=192.168.1.101/255.255.255.0/192.168.1.1

pls note that that will be changed by berryboot at setup again.
-d- now do a headless startup of berryboot RPI1B system with VNC to 192.168.1.101 ( NO :1 !!)
and load the usual xxx/Raspbian OS per ethernet/router/internet.
( i not try that for long time, hope today the download not fails )
now in sudo raspi-config not much to setup / name...
sudo apt-get update
( as i want keep that system only as a reference not do upgarde ( to new kernel... ) but need minimum
sudo apt-get install -y xrdp / test / and shutdown.
reboot with USB stick with 4 converted debian OS / VNC berryboot menu editor / and add/copy OS
( some hickups that he not see the USB stick for second copy.., but the copy is very fast, as it is only a copy ( and not a install...) of the 1 .. 2GB only squashfs files. ) but yes, the copy to USB stick and from USB to SD is slower, better boot the linux PC for it.
sadly the RPICAM not come up on WIFI ( berryboot overwrites the /etc/network/interfaces ) and the webserver ( on ethernet ) shows a error.
Error in RaspiMJPEG: Restart RaspiMJPEG (./RPi_Cam_Web_Interface_Installer.sh start) or the whole RPi. ??