-
Notifications
You must be signed in to change notification settings - Fork 0
/
Backup.mw
377 lines (298 loc) · 14.2 KB
/
Backup.mw
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
== Backing up just PIM data ==
The following applies to all Qtopia PIM suite based derivations (FDOM, 2008.8, Qtopia). PIM data covers:
* Contacts, calendar appointments, and tasks
* E-Mails and text messages
To make a backup which can be easily restored later on use secure copy:
scp -pr [email protected]:~/Applications/ .
scp -pr [email protected]:~/Documents/ .
To restore do the reverse:
scp -pr Applications [email protected]:~/
scp -pr Documents [email protected]:~/
Make sure you restart to allow the Qtopia PIM suite to see the changes:
reboot
This way we can flash applicable distributions with minimal effort without loosing important data. To access the PIM data on the computer take a look at the following files and folders:
* Contacts, calendar appointments, and tasks are kept in <tt>~/Applications/Qtopia/qtopia_db.sqlite</tt>.
* E-Mails and text messages are kept in <tt>~/Applications/qtmail/mail/</tt>.
== Backing up just /home/root ==
To backup the home folder (all your personal files in theory).
From the desktop pc run:
ssh root@phone 'tar -cpz /home/root' > moko-home-`date +%Y%m%d-%H%M%S`.tar.gz
Where '''<tt>phone</tt>''' is the ip address of your phone (192.168.0.202).
Personally I added an entry to /etc/hosts so the above works for me. I also added the desktop key to /home/root/.ssh/authorized_keys on the phone as per the instructions in [[USB_Networking#SSH_Keys]].
If you want to check what is in the backup, run the following, replacing the filename with what was just created.
tar -tzf moko-home-20080802-203108.tar.gz | less
[http://timwise.wikispaces.com/my+neo+freerunner reference]
== Backing up everything ==
You may either :
* Backup the flash contents, in order to be able to restore (see below)
* or move the system to SD to be able to boot it from SD in case of need. See [[Moving current system from flash to SD]]
=== Backing-up flash images ===
{{note|Upload support is currently broken - [http://docs.openmoko.org/trac/ticket/676 #676], [http://docs.openmoko.org/trac/ticket/1843 #1843]}}
You will need the [[Dfu-util]] to make a backup of your existing image.
As when [[Flashing_the_Neo_FreeRunner|flashing]], you will need to be in [[Booting_the_Neo_FreeRunner#Log_into_U-Boot_in_the_NOR_Flash|U-Boot in the NOR Flash]]. Log into the NOR uBoot menu and select ''Set console to USB'' (for FreeRunner just stay in NOR uBoot menu, do not select or enter anything). Now you will be able to flash, make backups of your FreeRunner or query the FreeRunner with [[Dfu-util|dfu-util]]. Backup is fairly slow; it took over ten minutes to back up a 247 MB rootfs.
It is important that you connect the USB cable directly from your computer to your phone. If there is a hub between them, backup (and flashing) will mostly likely fail.
{{note|On a Windows host, omit the "./" or "sudo ./" that precedes the commands listed on this page}}
<pre>
sudo ./dfu-util -a kernel -R -U good-kernel.bin
sudo ./dfu-util -a rootfs -R -U good-rootfs.jffs2
sudo ./dfu-util -a splash -R -U good-splash.bin
sudo ./dfu-util -a u-boot -R -U good-u-boot.bin
sudo ./dfu-util -a u-boot_env -R -U good-u-boot_env.bin
</pre>
Here is what a successful dfu-util backup run looks like:
on the host PC:
<pre>
$ sudo ./dfu-util -a kernel -R -U good-kernel.img
dfu-util - (C) 2007 by Openmoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY
Opening USB Device 0x0000:0x0000...
Claiming USB DFU Runtime Interface...
Determining device status: state = appIDLE, status = 0
Device really in Runtime Mode, send DFU detach request...
Resetting USB...
Opening USB Device...
Found Runtime: [0x1d50:0x5119] devnum=12, cfg=0, intf=0, alt=3, name="kernel"
Claiming USB DFU Interface...
Setting Alternate Setting ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
Transfer Size = 0x1000
Resetting USB to switch back to runtime mode
</pre>
on the FreeRunner:
<pre>
DFU: Switching to DFU Mode
DEVICE_CONFIGURED: 1
Starting DFU Upload of partition 'kernel'
DEVICE_CONFIGURED: 1
</pre>
A failed run of dfu-util looks like this:
<pre>
dfu-util - (C) 2007 by Openmoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY
Opening USB Device 0x0000:0x0000...
Claiming USB DFU Runtime Interface...
Determining device status: state = appIDLE, status = 0
Device really in Runtime Mode, send DFU detach request...
Resetting USB...
Opening USB Device...
Found Runtime: [0x1d50:0x5119] devnum=20, cfg=0, intf=0, alt=6, name="rootfs"
Claiming USB DFU Interface...
Setting Alternate Setting ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
Transfer Size = 0x1000
dfu_upload error -110
</pre>
And shows demsg errors like this:
<pre>
usb 5-2: usbfs: USBDEVFS_CONTROL failed cmd dfu-util rqt 161 rq 2 len 4096 ret -110
</pre>
This error is detected within the Linux USB stack (drivers/usb/core/message.c) and looking at
errno.h for the negatived error status number, the reason is e.g.
{|
| 110 || ETIMEDOUT || Connection timed out
|-
| 84 || EILSEQ || Illegal byte sequence
|-
| 108 || ESHUTDOWN || Cannot send after transport endpoint shutdown
|-
| ... || ||
|}
Insure yourself, that you connect the FR directly to the computer (without any USB hubs), if you experience timed out connections
and use the
dfu-util -d [[USB Product IDs|0x1d50:0x5119]] ...
option, if the FR is not detected properly.
=== Backing-up flash images (alternative) ===
On the device:
<pre>
mkdir /var/tmp/root
mount /dev/root /var/tmp/root
</pre>
If you have om2008.9 you have to use:
<pre>
mount -t jffs2 /dev/mtdblock6 /var/tmp/root
</pre>
On your workstation:
<pre>
ssh [email protected] "mkfs.jffs2 -d /var/tmp/root -e 128 --pad --no-cleanmarkers -x lzo" | pv -W > rootfs.jffs2
</pre>
(The "| pv -W" is optional, it just gives you something to watch as the bytes fly by.)
On the device:
<pre>
umount /var/tmp/root
</pre>
=== Backing-up in a tar archive ===
ssh [email protected] "tar c /bin /etc /home /lib /opt /sbin /tmp /usr /var" | pv -s 2200000 -W > rootfs.tar
(The "| pv -W" is optional, it just gives you something to watch as the bytes fly by; the "-s" option presume you're transferring 2200000 bytes of data)
Extract it and use <code>mkfs.jffs2</code> if you want convert it to a jffs2 image.
==Backup Scripts==
If you plan on backing up frequently, using a script will simplify the process:
===Simple backup script===
This script works well if you want to configure it to backup always the same device.
<pre>
#!/bin/sh
#
# Back up all partitions of the phone to a backup directory,
# adding today's date to the saved filenames.
DATE=`date +%Y-%m-%d`
DFU=./dfu-util
BACKUP_DIR=bak/
${DFU} -a kernel -R -U ${BACKUP_DIR}kernel-${DATE}.bin
${DFU} -a rootfs -R -U ${BACKUP_DIR}rootfs-${DATE}.jffs2
${DFU} -a splash -R -U ${BACKUP_DIR}splash-${DATE}.bin
${DFU} -a u-boot -R -U ${BACKUP_DIR}u-boot-${DATE}.bin
${DFU} -a u-boot_env -R -U ${BACKUP_DIR}u-boot_env-${DATE}.bin
</pre>
===Interactive script===
This script is based on the above "Simple backup script" (by unknown). It does the backup of what you want and choose promting you for choices. Enjoy it! test it! contribute! You can find us at /server irc.freenode.net /j #openmoko and we'll be pleased to accept you help (ideas || code).
NOTE that the script works for me(tm) but it still needs some love. especially on traps and catches for wrong choices.
<pre>
#!/bin/bash
#############################################################################################################
## ##
## This script is Free Software, it's licensed under the GPLv3 and has ABSOLUTELY NO WARRANTY ##
## you can find and read the complete version of the GPLv3 @ http://www.gnu.org/licenses/gpl.html ##
## ##
## Q: what does this script do? ##
## A: the script back up all partitions of the phone to a backup directory, interactively, ##
## adding today's date to the saved filenames. ##
## ##
## IMPORTANT:!!! REMEMBER TO RUN THIS SCRIPT AS ROOT SINCE dfu-util HAS TO BE USED AS ROOT!!! ##
## ##
## based on the orginal simple backup script at http://wiki.openmoko.org/wiki/Backup ##
## ##
## this version has been conceived and written by cga, x77686d, Infoport, jomat at /server irc.freenode.net##
## /j #openmoko,#bash and my collegue aubba @ work. ##
## ##
## for any suggestions and contributions contact cga (or one of the above) in the #openmoko channel ##
## ##
#############################################################################################################
## let's roll!!
## sets the date format for the date in the backup file, change accordingly to your local custom if you need
DATE=`date +%d-%m-%Y`
## here the scripts try to find the dfu-util binary and set it as the DFU var:
if which dfu-util >/dev/null ; then
echo
echo "dfu-util found in your path"
echo
## 1 the function use this if you placed/linked dfu-util in your $PATH
DFU=dfu-util
elif ls dfu-util >/dev/null ; then
echo
echo "dfu-util found in current directory"
echo
## or 2 use following line if dfu-util is placed in the same directory where you run the script
DFU=./dfu-util
else
## or 3 if the script doesn't find dfu-util shows the link for installing it and exit
echo
echo "dfu-util NOT found! install and use howto @ http://wiki.openmoko.org/wiki/Dfu-util"
echo
exit 1
fi
## here we get the hex code for devices found with dfu-util --list
## the hex code is grabbed and the name of the device is shown accordingly and you are prompetd to chose the right one:
echo
echo 'these are the devices i found:'
echo
for device in `${DFU} --list | grep 0x | cut -f3 -d' ' | tr -d '[]'` ; do
if [ "$device" == '0x1457:0x5119' ] ; then
echo 'Neo 1973'
elif [ "$device" == '0x1d50:0x5119' ] ; then
echo "Neo FreeRunner"
else
echo 'other device found, DO NOT use dfu-util on this!!! it might bork it...'
exit 1
fi
done | nl
echo
echo 'choose the device to backup:'
echo
read selection
HEX=$(${DFU} --list | grep 0x | head -n $selection | tail -1 | cut -f3 -d' ' | tr -d '[]')
## use the built-in read command to ask you and use the directory for the backup
while [ -z "$BACKUP_DIR" ] ; do
echo
read -e -p $"enter the directory for the backup:" BACKUP_DIR
echo
## chek wether the dir exist and proceed, else create it and proceed.
if [ ! -d "$BACKUP_DIR" ] ; then
echo
echo -n "$BACKUP_DIR does not exist, create it? [Y/n] "
echo
read CREATE_DIR
if [ x"$CREATE_DIR" = xy -o x"$CREATE_DIR" = xY -o -z "$CREATE_DIR" ] ; then
mkdir -p -v "${BACKUP_DIR}"
else
BACKUP_DIR=
fi
fi
done
## here you get prompted to chose the backup you want, you can backup single files or all of them.
echo
echo 'choose the component to backup from the list:'
echo
select howto in kernel splash u-boot u-boot_env rootfs all quit; do
if [ "$howto" == "kernel" -o "$howto" == "all" ] ; then
${DFU} -d ${HEX} -a kernel -R -U ${BACKUP_DIR}/kernel-${DATE}.bin
fi
if [ "$howto" == "splash" -o "$howto" == "all" ] ; then
${DFU} -d ${HEX} -a splash -R -U ${BACKUP_DIR}/splash-${DATE}.bin
fi
if [ "$howto" == "u-boot" -o "$howto" == "all" ] ; then
${DFU} -d ${HEX} -a u-boot -R -U ${BACKUP_DIR}/u-boot-${DATE}.bin
fi
if [ "$howto" == "u-boot_env" -o "$howto" == "all" ] ; then
${DFU} -d ${HEX} -a u-boot_env -R -U ${BACKUP_DIR}/u-boot_env-${DATE}.bin
fi
if [ "$howto" == "rootfs" -o "$howto" == "all" ] ; then
${DFU} -d ${HEX} -a rootfs -R -U ${BACKUP_DIR}/rootfs-${DATE}.jffs2
fi
if [ "$howto" == "quit" ] ; then
exit 0
fi
echo
echo 'the component(s) has/have been backed up, what next? (press enter for menu)'
echo
done
exit 0
</pre>
=== Pretty GUI Script ===
[[NeoTool]] is a zenity-based script which allows you to both backup and Flash your device from a pretty GUI. It uses both the dfu-util method and the alternate method described on this page, and can produce flashable images of everything including rootfs. Check it out.
== Backing up the incremental rsync hardlink way ==
Following is a very simple implementation of
[http://www.mikerubel.org/computers/rsync_snapshots/ incremental rsync snapshots with hardlinks]. Just put it to /etc/cron.daily/backup-neo
on your PC and setup ssh keys between your PC and neo. It will then
daily try to backup all files in the / partition. Each successful
backup is hardlinked under a timestamped directory so you can access
old backups easily. In fact, you can even NFS mount /backup/neo to
phone and then chroot inside the backups to run programs in the
backup'ed environment.
#!/bin/bash
# /etc/cron.daily/backup-neo
rsync --delete -ax --numeric-ids 192.168.0.202:/ /backup/neo/latest 2> /dev/null
ret=$?
case $ret in
0)
# backup done, let's save it
cp -al /backup/neo/latest /backup/neo/`date -I`
;;
12)
# neo was not at home
;;
*)
echo "backup failed with return value $ret"
;;
esac
== Backing up internal flash when booted on external SD-card ==
#Freerunner
mkdir internal_flash
mount /dev/mtdblock6 internal_flash -t jffs2
Now you can pack directory or copy selected files out from it.
(This mounting is usefull also if your internal operating system is non-bootable. You can get files out or even repair the system using operating system on external card.)
== Weblinks ==
* [http://www.oesf.org/forum/index.php?showtopic=25994#entry178835 read jffs file system on pc]
[[Category:PIM]]
[[category:Advanced End User]]
[[Category:Flashing Openmoko]]