SingletonMillerWiki - User contributions [en]

Backup SD Image

2012-08-22T17:50:08Z

Ajd:

[[Category: RaspberryPi]]
At some point in your use of the RPi, you're going to think "I've made a whole heap of changes to my RPi build, what if it breaks and I lose everything? How do I stop that happening?".

The answer is 'you can't' hardware fails, power glitches, <code> sudo rm -rf * </code>, human error, all these types of thing can corrupt your precious SD card.

The solution is 'back it up'.

The ideal solution is to create an device image of your current SD card so you can completely rebuilt it rather than starting from a vanilla debian or fedora build.

== Creating an SD Image ==
You've probably already used an image tool to burn your SD card from an process similar to [[Setup:RPI]].

===Windows===
I used the windows tool [https://launchpad.net/win32-image-writer win32-image-writer].
win32-image-writer can also be used to create an image file.

# Shutdown you RPI using <code> sudo shutdown -h now </code>.
# Remove the power from the micro USB connection
# Remove the SD card from the RPi slot.
# Insert the SD card into your Windows PC card slot
# Run the ''win32-image-writer'' utility on the windows PC
::* Select the SD card in the ''device'' drop down. If you have more than one device, be careful to select to correct one.
::* Select the Imager Name to write to, make sure you select a *.img filename.
::* Press ''read'' button to burn a binary image of the SC card to the file.

The process is slow and the imager file generated will be approximated the same size as the SD card capacity. This is because the image is a binary clone of the SD card.
The img file may be zipped to reduce its size after the process is completed.

===Linux===
This uses the method given Raspberry Pi Easy SD Card Set Up referenced above: but in reverse. Any Linux machine can be used and it assumes the SD Card being backed up is not mounted. So if you only have one SD card you can't use your Pi, you have to use another Linux machine. However, if you have two SD cards capable of booting a Pi, use the one you aren't backing up to boot Pi and the backup the other, via a USB - SD card reader.

If you are using another Linux machine you can back it up to that machine or to anything, such as a NAS, that it can see. If your using your Pi it will have to be backed up to some form of extarnal storage, such as a USB HDD or a NAS.

The instruction here back up the SD card to a mount point on the Linux machine doing the backup.

Firstly, create a directory on the Linux host to mount the location that will receive the backup. e.g.

<pre>
mkdir /media/cifshares
</pre>

Secondly, mount the location that will receive the backup:

<pre>
sudo mount -t cifs //hostname/sharename -o username=xxxx,password=yyyy /media/cifshares
</pre>

Note: the hostname can be substituted with the IP address of the machine receiving the backup.

Thirdly, insert the SD card into the machine doing the backup and note its device assignment; as per the Easy CD card set up. Make sure all partions are dismounted. For the following illustration, assume that the SD card to be backed up is ''sdb''. If the SD card does not get mounted, ''df -h'' does not recognise it. ''sfdisk -l'' can be used to see unmounted devices.

Finally, use the ''dd'' comand to backup the SD card image

<pre>
dd bs=1M if=/dev/sdb of=/media/cifshares/SD_Card_Image.img
</pre>

Note: I've now successfully put an image back onto an SD card. So it does work.

== Regular Backup ==
If you make regular changes to your RPi its worthwhile spending the time creating these images. Time spent backing up is always saved in rebuilding.

== References ==
#[http://elinux.org/RPi_Easy_SD_Card_Setup http://elinux.org/RPi_Easy_SD_Card_Setup]

Backup SD Image

2012-06-30T19:47:50Z

Ajd:

[[Category: RaspberryPi]]
At some point in your use of the RPi, you're going to think "I've made a whole heap of changes to my RPi build, what if it breaks and I lose everything? How do I stop that happening?".

The answer is 'you can't' hardware fails, power glitches, <code> sudo rm -rf * </code>, human error, all these types of thing can corrupt your precious SD card.

The solution is 'back it up'.

The ideal solution is to create an device image of your current SD card so you can completely rebuilt it rather than starting from a vanilla debian or fedora build.

== Creating an SD Image ==
You've probably already used an image tool to burn your SD card from an process similar to [[Setup:RPI]].

===Windows===
I used the windows tool [https://launchpad.net/win32-image-writer win32-image-writer].
win32-image-writer can also be used to create an image file.

# Shutdown you RPI using <code> sudo shutdown -h now </code>.
# Remove the power from the micro USB connection
# Remove the SD card from the RPi slot.
# Insert the SD card into your Windows PC card slot
# Run the ''win32-image-writer'' utility on the windows PC
::* Select the SD card in the ''device'' drop down. If you have more than one device, be careful to select to correct one.
::* Select the Imager Name to write to, make sure you select a *.img filename.
::* Press ''read'' button to burn a binary image of the SC card to the file.

The process is slow and the imager file generated will be approximated the same size as the SD card capacity. This is because the image is a binary clone of the SD card.
The img file may be zipped to reduce its size after the process is completed.

===Linux===
This uses the method given Raspberry Pi Easy SD Card Set Up referenced above: but in reverse. Any Linux machine can be used and it assumes the SD Card being backed up is not mounted. So if you only have one SD card you can't use your Pi, you have to use another Linux machine. However, if you have two SD cards capable of booting a Pi, use the one you aren't backing up to boot Pi and the backup the other, via a USB - SD card reader.

If you are using another Linux machine you can back it up to that machine or to anything, such as a NAS, that it can see. If your using your Pi it will have to be backed up to some form of extarnal storage, such as a USB HDD or a NAS.

The instruction here back up the SD card to a mount point on the Linux machine doing the backup.

Firstly, create a directory on the Linux host to mount the location that will receive the backup. e.g.

<pre>
mkdir /media/cifshares
</pre>

Secondly, mount the location that will receive the backup:

<pre>
sudo mount -t cifs //hostname/sharename -o username=xxxx,password=yyyy /media/cifshares
</pre>

Note: the hostname can be substituted with the IP address of the machine receiving the backup.

Thirdly, insert the SD card into the machine doing the backup and note its device assignment; as per the Easy CD card set up. Make sure all partions are dismounted. For the following illustration, assume that the SD card to be backed up is ''sdb''. If the SD card does not get mounted, ''df -h'' does not recognise it. ''sfdisk -l'' can be used to see unmounted devices.

Finally, use the ''dd'' comand to backup the SD card image

<pre>
dd bs=1M if=/dev/sdb of=/media/cifshares/SD_Card_Image.img
</pre>

Note: As yet I haven't actually tried to reload a saved image. So be warned.

== Regular Backup ==
If you make regular changes to your RPi its worthwhile spending the time creating these images. Time spent backing up is always saved in rebuilding.

== References ==
#[http://elinux.org/RPi_Easy_SD_Card_Setup http://elinux.org/RPi_Easy_SD_Card_Setup]

Backup SD Image

2012-06-30T19:46:07Z

Ajd:

[[Category: RaspberryPi]]
At some point in your use of the RPi, you're going to think "I've made a whole heap of changes to my RPi build, what if it breaks and I lose everything? How do I stop that happening?".

The answer is 'you can't' hardware fails, power glitches, <code> sudo rm -rf * </code>, human error, all these types of thing can corrupt your precious SD card.

The solution is 'back it up'.

The ideal solution is to create an device image of your current SD card so you can completely rebuilt it rather than starting from a vanilla debian or fedora build.

== Creating an SD Image ==
You've probably already used an image tool to burn your SD card from an process similar to [[Setup:RPI]].

===Windows===
I used the windows tool [https://launchpad.net/win32-image-writer win32-image-writer].
win32-image-writer can also be used to create an image file.

# Shutdown you RPI using <code> sudo shutdown -h now </code>.
# Remove the power from the micro USB connection
# Remove the SD card from the RPi slot.
# Insert the SD card into your Windows PC card slot
# Run the ''win32-image-writer'' utility on the windows PC
::* Select the SD card in the ''device'' drop down. If you have more than one device, be careful to select to correct one.
::* Select the Imager Name to write to, make sure you select a *.img filename.
::* Press ''read'' button to burn a binary image of the SC card to the file.

The process is slow and the imager file generated will be approximated the same size as the SD card capacity. This is because the image is a binary clone of the SD card.
The img file may be zipped to reduce its size after the process is completed.

===Linux===
This uses the method given Raspberry Pi Easy SD Card Set Up referenced above: but in reverse. Any Linux machine can be used and it assumes the SD Card being backed up is not mounted. So if you only have one SD card you can't use your Pi, you have to use another Linux machine. However, if you have two SD cards capable of booting a Pi, use the one you aren't backing up to boot Pi and the backup the other, via a USB - SD card reader.

If you are using another Linux machine you can back it up to that machine or to anything, such as a NAS, that it can see. If your using your Pi it will have to be backed up to some form of extarnal storage, such as a USB HDD or a NAS.

The instruction here back up the SD card to a mount point on the Linux machine doing the backup.

Firstly, create a directory on the Linux host to mount the location that will receive the backup. e.g.

<pre>
mkdir /media/cifshares
</pre>

Secondly, mount the location that will receive the backup:

<pre>
sudo mount -t cifs //hostname/sharename -o username=xxxx,password=yyyy /media/cifshares
</pre>

Note: the hostname can be substituted with the IP address of the machine receiving the backup.

Thirdly, insert the SD card into the machine doing the backup and note its device assignment; as per the Easy CD card set up. Make sure all partions are dismounted. For the following illustration, assume that the SD card to be backed up is ''sdb''. If the SD card does not get mounted, ''sf -h'' does not recognise it. ''sfdisk -l'' can be used to see unmounted devices.

Finally, use the ''dd'' comand to backup the SD card image

<pre>
dd bs=1M if=/dev/sdb of=/media/cifshares/SD_Card_Image.img
</pre>

Note: As yet I haven't actually tried to reload a saved image. So be warned.

== Regular Backup ==
If you make regular changes to your RPi its worthwhile spending the time creating these images. Time spent backing up is always saved in rebuilding.

== References ==
#[http://elinux.org/RPi_Easy_SD_Card_Setup http://elinux.org/RPi_Easy_SD_Card_Setup]

Remote Desktop

2012-06-14T20:41:41Z

Ajd:

[[Category: RaspberryPi]]

== Resources ==

[http://www.raspberrypi.org/phpBB3/viewtopic.php?f=47&t=5814&p=90752]

This describes how to use your RPi as a remote terminal to a Windows machine. It assumes that the Widows machine has Remote Desktop installed and enabled.

Firstly, install the remote desktop package on you RPi:

<pre>
sudo app-get install rdesktop
</pre>

Haveing installed the remote desktop on the RPi the remote machine is accessed by something such as the example below

<pre>
rdesktop -x:l -r sound:remote hostname
</pre>

''hostname'' can be replaced by an IP address

For a list of option see

<pre>
man rdesktop
</pre>

The example above indicates that the remote machine is on a LAN, i.e. -x:l gives maximum bandwidth and that the sound is to be left on the remote machine.

Remote Desktop

2012-06-14T20:40:00Z

Ajd:

[[Category: RaspberryPi]]

[[http://www.raspberrypi.org/phpBB3/viewtopic.php?f=47&t=5814&p=90752]]

This describes how to use your RPi as a remote terminal to a Windows machine. It assumes that the Widows machine has Remote Desktop installed and enabled.

Firstly, install the remote desktop package on you RPi:

<pre>
sudo app-get install rdesktop
</pre>

Haveing installed the remote desktop on the RPi the remote machine is accessed by something such as the example below

<pre>
rdesktop -x:l -r sound:remote hostname
</pre>

''hostname'' can be replaced by an IP address

For a list of option see

<pre>
man rdesktop
</pre>

The example above indicates that the remote machine is on a LAN, i.e. -x:l gives maximum bandwidth and that the sound is to be left on the remote machine.

Remote Desktop

2012-06-14T20:39:40Z

Ajd:

[[Category: RaspberryPi]]

[http://www.raspberrypi.org/phpBB3/viewtopic.php?f=47&t=5814&p=90752]

This describes how to use your RPi as a remote terminal to a Windows machine. It assumes that the Widows machine has Remote Desktop installed and enabled.

Firstly, install the remote desktop package on you RPi:

<pre>
sudo app-get install rdesktop
</pre>

Haveing installed the remote desktop on the RPi the remote machine is accessed by something such as the example below

<pre>
rdesktop -x:l -r sound:remote hostname
</pre>

''hostname'' can be replaced by an IP address

For a list of option see

<pre>
man rdesktop
</pre>

The example above indicates that the remote machine is on a LAN, i.e. -x:l gives maximum bandwidth and that the sound is to be left on the remote machine.

Remote Desktop

2012-06-14T20:12:00Z

Ajd:

[[Category: RaspberryPi]]

'''Needs a reference. RPi website down'''

This describes how to use your RPi as a remote terminal to a Windows machine. It assumes that the Widows machine has Remote Desktop installed and enabled.

Firstly, install the remote desktop package on you RPi:

<pre>
sudo app-get rdesktop
</pre>

'''The above command needs checking. The RPi website was down when I tried to check.'''

Haveing installed the remote desktop on the RPi the remote machine is accessed by something such as the example below

<pre>
rdesktop -x:l -r sound:remote hostname
</pre>

''hostname'' can be replaced by an IP address

For a list of option see

<pre>
man rdesktop
</pre>

The example above indicates that the remote machine is on a LAN, i.e. -x:l gives maximum bandwidth and that the sound is to be left on the remote machine.

Remote Desktop

2012-06-14T20:09:46Z

Ajd:

[[Category: RaspberryPi]]

'''Needs a reference. RPi website down'''

This describes how to use your RPi as a remote terminal to a Windows machine. It assumes that the Widows machine has Remote Desktop installed and enabled.

Firstly, install the remote desktop package on you RPi:

<pre>
sudo app-get rdesktop
</pre>

'''The above command needs checking. The RPi website was down when I tried to check.'''

Haveing installed the remote desktop on the RPi the remote machine is accessed by something such as the example below

<pre>
rdesktop -x:l -r sound:remote hostname
</pre>

''hostname'' can be replaced by an IP address

For a list of option see

<pre>
man rdesktop
</pre>

The example above indicates that the remote machine is on a local LAN, i.e. -x:l gives maximum bandwidth and that the sound is to be left on the remote machine.

Remote Desktop

2012-06-14T20:06:21Z

Ajd:

[[Category: RaspberryPi]]

'''Needs a reference. RPi website down'''

This describes how to use your RPi as a remote terminal to a Windows machine. It assumes that the Widows machine has Remote Desktop installed and enabled.

Firstly, install the remote desktop package on you RPi:

<pre>
sudo app-get rdesktop
</pre>

'''The above command needs checking. The RPi website was down when I tried to check.'''

Haveing installed the remote desktop on the RPi the remote machine is accessed by something such as the example below

<pre>
rdesktop -x:l -r sound:remote hostname
</pre>

''hostname'' can be replaced by an IP address

see

<pre>
man rdesktop
</pre>

For a list of options. The example above indicates that the remote machine is on a local LAN, i.e. -x:l gives maximum bandwidth and that the sound is to be left on the remote machine.

Remote Desktop

2012-06-14T20:04:53Z

Ajd:

[[Category: RaspberryPi]]

This describes how to use your RPi as a remote terminal to a Windows machine. It assumes that the Widows machine has Remote Desktop installed and enabled.

Firstly, install the remote desktop package on you RPi:

<pre>
sudo app-get rdesktop
</pre>

'''The above command needs checking. The RPi website was down when I tried to check.'''

Haveing installed the remote desktop on the RPi the remote machine is accessed by something such as the example below

<pre>
rdesktop -x:l -r sound:remote hostname
</pre>

''hostname'' can be replaced by an IP address

see

<pre>
man rdesktop
</pre>

For a list of options. The example above indicates that the remote machine is on a local LAN, i.e. -x:l gives maximum bandwidth and that the sound is to be left on the remote machine.

Remote Desktop

2012-06-14T20:03:47Z

Ajd:

[[Category: RaspberryPi]]

This describes how to use your RPi as a remote terminal to a Windows machine. It assumes that the Widows machine has Remote Desktop installed and enabled.

Firstly, install the remote desktop package on you RPi:

<pre>
sudo app-get rdesktop
</pre>

The above command needs checking. The RPi website was down when I tried to check.

Haveing installed the remote desktop on the RPi the remote machine is accessed by something such as the example below

<pre>
rdesktop -x:l -r sound:remote hostname
</pre>

''hostname'' can be replaced by an IP address

see

<pre>
man rdesktop
</pre>

For a list of options. The example above indicates that the remote machine is on a local LAN, i.e. -x:l gives maximum bandwidth and that the sound is to be left on the remote machine.

Remote Desktop

2012-06-14T19:42:04Z

Ajd: Created page with "Category: RaspberryPi This describes hoy to use your RPi as a remote terminal to a Windows machine. It assumes that the Widows machine has Remote Desktop installed and enabled."

[[Category: RaspberryPi]]

This describes hoy to use your RPi as a remote terminal to a Windows machine. It assumes that the Widows machine has Remote Desktop installed and enabled.

ListOfRaspberryPiHow-Tos

2012-06-14T19:40:12Z

Ajd:

[[Category:RaspberryPi]]
== Topics ==
This page is a list to the available RaspberryPi How-Tos.

;[[Setup:RPI]]
: initial setup and configuration and updates.

;[[HDMI Configuration]]
: HDMI references and example problem/solution
;[[AddingUsers:RPi]]
: add a user and assign super user privledges.

;[[Updating the RPi Software]]
: Up to date software offers perfromance and security benefits

;[[Updating RPi Firmware]]
: Up to date firmware offers perfromance and security benefits

;[[Static IP Config]]
: network static IP address is useful if you RPi is to be accessed remotely

;[[Enable SSH]]
: enable SSH to allow remote login

;[[Setup VNC]]
: to access via remote desktop

;[[Expand Image to fill SD card]]
: Use the spare space assuming your SD card is larger than the default image you installed.

;[[Backup SD Image]]
: So you don't undo all your great work in a ''flash''.

;[[Enable Sound]]
: As of {{REVISIONDAY2}}/{{REVISIONMONTH}}/{{REVISIONYEAR}} the sound driver is still Alpha and is disabled by default, use this guide to enable and test sound on your RPi.

;[[Playing Music]]
: Finally something useful to do with your RPi

;[[Playing Videos]]
: Playing videos is a fun thing to do!

;[[Accessing Network Shares]]
: SD cards just aren't big enough.

;[[Run Quake]]
: Just in case you get bored or are planning a LAN party.

;[[Setting up a Torrent Server]]
: Setup your RPi to get he latest RPi distro using torrents.

;[[Remote Desktop]]
: Use your RPi as a remote terminal to a Windows machine.

Remote Login

2012-06-14T19:36:53Z

Ajd: Created page with "==Remote Login== This describes how to use your RPi as a terminal to a remote Windows machine. It assumes that the Windows machine has remote login facilities and that they tur..."

==Remote Login==

This describes how to use your RPi as a terminal to a remote Windows machine.

It assumes that the Windows machine has remote login facilities and that they turned on.

ListOfRaspberryPiHow-Tos

2012-06-14T19:35:00Z

Ajd:

[[Category:RaspberryPi]]
== Topics ==
This page is a list to the available RaspberryPi How-Tos.

;[[Setup:RPI]]
: initial setup and configuration and updates.

;[[HDMI Configuration]]
: HDMI references and example problem/solution
;[[AddingUsers:RPi]]
: add a user and assign super user privledges.

;[[Updating the RPi Software]]
: Up to date software offers perfromance and security benefits

;[[Updating RPi Firmware]]
: Up to date firmware offers perfromance and security benefits

;[[Static IP Config]]
: network static IP address is useful if you RPi is to be accessed remotely

;[[Enable SSH]]
: enable SSH to allow remote login

;[[Setup VNC]]
: to access via remote desktop

;[[Expand Image to fill SD card]]
: Use the spare space assuming your SD card is larger than the default image you installed.

;[[Backup SD Image]]
: So you don't undo all your great work in a ''flash''.

;[[Enable Sound]]
: As of {{REVISIONDAY2}}/{{REVISIONMONTH}}/{{REVISIONYEAR}} the sound driver is still Alpha and is disabled by default, use this guide to enable and test sound on your RPi.

;[[Playing Music]]
: Finally something useful to do with your RPi

;[[Playing Videos]]
: Playing videos is a fun thing to do!

;[[Accessing Network Shares]]
: SD cards just aren't big enough.

;[[Run Quake]]
: Just in case you get bored or are planning a LAN party.

;[[Setting up a Torrent Server]]
: Setup your RPi to get he latest RPi distro using torrents.

;[[Remote Login]]
: Use your RPi as a remote terminal to a Windows machine.

ListOfRaspberryPiHow-Tos

2012-06-14T19:34:44Z

Ajd:

[[Category:RaspberryPi]]
== Topics ==
This page is a list to the available RaspberryPi How-Tos.

;[[Setup:RPI]]
: initial setup and configuration and updates.

;[[HDMI Configuration]]
: HDMI references and example problem/solution
;[[AddingUsers:RPi]]
: add a user and assign super user privledges.

;[[Updating the RPi Software]]
: Up to date software offers perfromance and security benefits

;[[Updating RPi Firmware]]
: Up to date firmware offers perfromance and security benefits

;[[Static IP Config]]
: network static IP address is useful if you RPi is to be accessed remotely

;[[Enable SSH]]
: enable SSH to allow remote login

;[[Setup VNC]]
: to access via remote desktop

;[[Expand Image to fill SD card]]
: Use the spare space assuming your SD card is larger than the default image you installed.

;[[Backup SD Image]]
: So you don't undo all your great work in a ''flash''.

;[[Enable Sound]]
: As of {{REVISIONDAY2}}/{{REVISIONMONTH}}/{{REVISIONYEAR}} the sound driver is still Alpha and is disabled by default, use this guide to enable and test sound on your RPi.

;[[Playing Music]]
: Finally something useful to do with your RPi

;[[Playing Videos]]
: Playing videos is a fun thing to do!

;[[Accessing Network Shares]]
: SD cards just aren't big enough.

;[[Run Quake]]
: Just in case you get bored or are planning a LAN party.

;[[Setting up a Torrent Server]]
: Setup your RPi to get he latest RPi distro using torrents.

;[[Remot Login]]
: Use your RPi as a remote terminal to a Windows machine.

Backup SD Image

2012-06-14T19:30:07Z

Ajd:

[[Category: RaspberryPi]]
At some point in your use of the RPi, you're going to think "I've made a whole heap of changes to my RPi build, what if it breaks and I lose everything? How do I stop that happening?".

The answer is 'you can't' hardware fails, power glitches, <code> sudo rm -rf * </code>, human error, all these types of thing can corrupt your precious SD card.

The solution is 'back it up'.

The ideal solution is to create an device image of your current SD card so you can completely rebuilt it rather than starting from a vanilla debian or fedora build.

== Resources ==
[http://elinux.org/RPi_Easy_SD_Card_Setup http://elinux.org/RPi_Easy_SD_Card_Setup]

== Creating an SD Image ==
You've probably already used an image tool to burn your SD card from an process similar to [[Setup:RPI]].

===Windows===
I used the windows tool [https://launchpad.net/win32-image-writer win32-image-writer].
win32-image-writer can also be used to create an image file.

# Shutdown you RPI using <code> sudo shutdown -h now </code>.
# Remove the power from the micro USB connection
# Remove the SD card from the RPi slot.
# Insert the SD card into your Windows PC card slot
# Run the ''win32-image-writer'' utility on the windows PC
::* Select the SD card in the ''device'' drop down. If you have more than one device, be careful to select to correct one.
::* Select the Imager Name to write to, make sure you select a *.img filename.
::* Press ''read'' button to burn a binary image of the SC card to the file.

The process is slow and the imager file generated will be approximated the same size as the SD card capacity. This is because the image is a binary clone of the SD card.
The img file may be zipped to reduce its size after the process is completed.

===Linux===
This uses the method given Raspberry Pi Easy SD Card Set Up referenced above: but in reverse. Any Linux machine can be used and it assumes the SD Card being backed up is not mounted. So if you only have one SD card you can't use your Pi, you have to use another Linux machine. However, if you have two SD cards capable of booting a Pi, use the one you aren't backing up to boot Pi and the backup the other, via a USB - SD card reader.

If you are using another Linux machine you can back it up to that machine or to anything, such as a NAS, that it can see. If your using your Pi it will have to be backed up to some form of extarnal storage, such as a USB HDD or a NAS.

The instruction here back up the SD card to a mount point on the Linux machine doing the backup.

Firstly, create a directory on the Linux host to mount the location that will receive the backup. e.g.

<pre>
mkdir /media/cifshares
</pre>

Secondly, mount the location that will receive the backup:

<pre>
sudo mount -t cifs //hostname/sharename -o username=xxxx,password=yyyy /media/cifshares
</pre>

Note: the hostname can be substituted with the IP address of the machine receiving the backup.

Thirdly, insert the SD card into the machine doing the backup and note its device assignment; as per the Easy CD card set up. Make sure all partions are dismounted. For the following illustration, assume that the SD card to be backed up is ''sdb''.

Finally, use the ''dd'' comand to backup the SD card image

<pre>
dd bs=1M if=/dev/sdb of=/media/cifshares/SD_Card_Image.img
</pre>

Note: As yet I haven't actually tried to reload a saved image. So be warned.

== Regular Backup ==
If you make regular changes to your RPi its worthwhile spending the time creating these images. Time spent backing up is always saved in rebuilding.

Backup SD Image

2012-06-14T19:27:54Z

Ajd: /* Linux */

[[Category: RaspberryPi]]
At some point in your use of the RPi, you're going to think "I've made a whole heap of changes to my RPi build, what if it breaks and I lose everything? How do I stop that happening?".

The answer is 'you can't' hardware fails, power glitches, <code> sudo rm -rf * </code>, human error, all these types of thing can corrupt your precious SD card.

The solution is 'back it up'.

The ideal solution is to create an device image of your current SD card so you can completely rebuilt it rather than starting from a vanilla debian or fedora build.

== Resources ==
[http://elinux.org/RPi_Easy_SD_Card_Setup http://elinux.org/RPi_Easy_SD_Card_Setup]

== Creating an SD Image ==
You've probably already used an image tool to burn your SD card from an process similar to [[Setup:RPI]].

===Windows===
I used the windows tool [https://launchpad.net/win32-image-writer win32-image-writer].
win32-image-writer can also be used to create an image file.

# Shutdown you RPI using <code> sudo shutdown -h now </code>.
# Remove the power from the micro USB connection
# Remove the SD card from the RPi slot.
# Insert the SD card into your Windows PC card slot
# Run the ''win32-image-writer'' utility on the windows PC
::* Select the SD card in the ''device'' drop down. If you have more than one device, be careful to select to correct one.
::* Select the Imager Name to write to, make sure you select a *.img filename.
::* Press ''read'' button to burn a binary image of the SC card to the file.

The process is slow and the imager file generated will be approximated the same size as the SD card capacity. This is because the image is a binary clone of the SD card.
The img file may be zipped to reduce its size after the process is completed.

===Linux===
This uses the method given Raspberry Pi Easy SD Card Set Up referenced above: but in reverse. Any Linux machine can be used and it assumes the SD Card being backed up is not mounted. So if you only have one SD card you can't use your Pi, you have to use another Linux machine. However, if you have two SD cards capable of booting a Pi, use the one you aren't backing up to boot Pi and the backup the other, via a USB - SD card reader.

If you are using another Linux machine you can back it up to that machine or to anything, such as a NAS, that it can see. If your using your Pi it will have to be backed up to some form of extarnal storage, such as a USB HDD or a NAS.

The instruction here back up the SD card to a mount point on the Linux machine doing the backup.

Firstly, create a directory on the Linux host to mount the location that will receive the backup. e.g.

<pre>
mkdir /media/cifshares
</pre>

Secondly, mount the location that will receive the backup:

<pre>
sudo mount -t cifs //hostname/sharename -o username=xxxx,password=yyyy /media/cifshares
</pre>

Note: the hostname can be substituted with the IP address of the machine receiving the backup.

Thirdly, insert the SD card into the machine doing the backup and note its device assignment; as per the Easy CD card set up. Make sure all partions are dismounted. For the following illustration, assume that the SD card to be backed up is sdb.

Finally, use the dd comand to backup the SD card image

<pre>
dd bs=1M if=/dev/sdb of=/media/cifshares/SD_Card_Image.img
</pre>

Note: As yet I haven't actually tried to reload a saved image. So be warned.

== Regular Backup ==
If you make regular changes to your RPi its worthwhile spending the time creating these images. Time spent backing up is always saved in rebuilding.

Backup SD Image

2012-06-14T19:27:11Z

Ajd:

[[Category: RaspberryPi]]
At some point in your use of the RPi, you're going to think "I've made a whole heap of changes to my RPi build, what if it breaks and I lose everything? How do I stop that happening?".

The answer is 'you can't' hardware fails, power glitches, <code> sudo rm -rf * </code>, human error, all these types of thing can corrupt your precious SD card.

The solution is 'back it up'.

The ideal solution is to create an device image of your current SD card so you can completely rebuilt it rather than starting from a vanilla debian or fedora build.

== Resources ==
[http://elinux.org/RPi_Easy_SD_Card_Setup http://elinux.org/RPi_Easy_SD_Card_Setup]

== Creating an SD Image ==
You've probably already used an image tool to burn your SD card from an process similar to [[Setup:RPI]].

===Windows===
I used the windows tool [https://launchpad.net/win32-image-writer win32-image-writer].
win32-image-writer can also be used to create an image file.

# Shutdown you RPI using <code> sudo shutdown -h now </code>.
# Remove the power from the micro USB connection
# Remove the SD card from the RPi slot.
# Insert the SD card into your Windows PC card slot
# Run the ''win32-image-writer'' utility on the windows PC
::* Select the SD card in the ''device'' drop down. If you have more than one device, be careful to select to correct one.
::* Select the Imager Name to write to, make sure you select a *.img filename.
::* Press ''read'' button to burn a binary image of the SC card to the file.

The process is slow and the imager file generated will be approximated the same size as the SD card capacity. This is because the image is a binary clone of the SD card.
The img file may be zipped to reduce its size after the process is completed.

===Linux===
This uses the method given Raspberry Pi Easy SD Card Set Up referenced above: but in reverse. Any Linux machine can be used and it assumes the SD Card being backed up is not mounted. So if you only have one SD card you can't use your Pi, you have to use another Linux machine. However, if you have two SD cards capable of booting a Pi, use the one you aren't backing up to boot Pi and the backup the other, via a USB - SD card reader.

If you are using another Linux machine you can back it up to that machine or to anything, such as a NAS, that it can see. If your using your Pi it will have to be backed up to some form of extarnal storage, such as a USB HDD or a NAS.

The instruction here back up the SDd to a mount point on the Linux machine doing the backup.

Firstly, create a directory on the Linux host to mount the location that will receive the backup. e.g.

<pre>
mkdir /media/cifshares
</pre>

Secondly, mount the location that will receive the backup:

<pre>
sudo mount -t cifs //hostname/sharename -o username=xxxx,password=yyyy /media/cifshares
</pre>

Note: the hostname can be substituted with the IP address of the machine receiving the backup.

Thirdly, insert the SD card into the machine doing the backup and note its device assignment; as per the Easy CD card set up. Make sure all partions are dismounted. For the following illustration, assume that the SD card to be backed up is sdb.

Finally, use the dd comand to backup the SD card image

<pre>
dd bs=1M if=/dev/sdb of=/media/cifshares/SD_Card_Image.img
</pre>

Note: As yet I haven't actually tried to reload a saved image. So be warned.

== Regular Backup ==
If you make regular changes to your RPi its worthwhile spending the time creating these images. Time spent backing up is always saved in rebuilding.

Backup SD Image

2012-06-14T19:25:21Z

Ajd:

[[Category: RaspberryPi]]
At some point in your use of the RPi, you're going to think "I've made a whole heap of changes to my RPi build, what if it breaks and I lose everything? How do I stop that happening?".

The answer is 'you can't' hardware fails, power glitches, <code> sudo rm -rf * </code>, human error, all these types of thing can corrupt your precious SD card.

The solution is 'back it up'.

The ideal solution is to create an device image of your current SD card so you can completely rebuilt it rather than starting from a vanilla debian or fedora build.

== Resources ==
[http://elinux.org/RPi_Easy_SD_Card_Setup http://elinux.org/RPi_Easy_SD_Card_Setup]

== Creating an SD Image ==
You've probably already used an image tool to burn your SD card from an process similar to [[Setup:RPI]].

===Windows===
I used the windows tool [https://launchpad.net/win32-image-writer win32-image-writer].
win32-image-writer can also be used to create an image file.

# Shutdown you RPI using <code> sudo shutdown -h now </code>.
# Remove the power from the micro USB connection
# Remove the SD card from the RPi slot.
# Insert the SD card into your Windows PC card slot
# Run the ''win32-image-writer'' utility on the windows PC
::* Select the SD card in the ''device'' drop down. If you have more than one device, be careful to select to correct one.
::* Select the Imager Name to write to, make sure you select a *.img filename.
::* Press ''read'' button to burn a binary image of the SC card to the file.

The process is slow and the imager file generated will be approximated the same size as the SD card capacity. This is because the image is a binary clone of the SD card.
The img file may be zipped to reduce its size after the process is completed.

===Linux===
This uses the method given Raspberry Pi Easy SD Card Set Up referenced above: but in reverse. Any Linux machine can be used and it assumes the SD Card being backed up is not mounted. So if you only have one SD card you can't use your Pi, you have to use another Linux machine. However, if you have two SD cards capable of booting a Pi, use the one you aren't backing up to boot Pi and the backup the other, via a USB - SD card reader.

If you are using another Linux machine you can back it up to that machine or to anything, such as a NAS, that it can see. If your using your Pi it will have to be backed up to some form of extarnal storage, such as a USB HDD or a NAS.

The instruction here back up the SDd to a mount point on the Linux machine doing the backup.

Firstly, create a directory on the Linux host to mount the location that will receive the backup. e.g.

<pre>
mkdir /media/cifshares
</pre>

Secondly, mount the location that will receive the backup:

<pre>
sudo mount -t cifs //hostname/sharename -o username=xxxx,password=yyyy /media/cifshares
</pre>

Thirdly, insert the SD card into the machine doing the backup and note its device assignment; as per the Easy CD card set up. Make sure all partions are dismounted. For the following illustration, assume that the SD card to be backed up is sdb.

Finally, use the dd comand to backup the SD card image

<pre>
dd bs=1M if=/dev/sdb of=/media/cifshares/SD_Card_Image.img
</pre>

Note: As yet I haven't actually tried to reload a saved image. So be warned.

== Regular Backup ==
If you make regular changes to your RPi its worthwhile spending the time creating these images. Time spent backing up is always saved in rebuilding.

Backup SD Image

2012-06-14T19:11:03Z

Ajd:

[[Category: RaspberryPi]]
At some point in your use of the RPi, you're going to think "I've made a whole heap of changes to my RPi build, what if it breaks and I lose everything? How do I stop that happening?".

The answer is 'you can't' hardware fails, power glitches, <code> sudo rm -rf * </code>, human error, all these types of thing can corrupt your precious SD card.

The solution is 'back it up'.

The ideal solution is to create an device image of your current SD card so you can completely rebuilt it rather than starting from a vanilla debian or fedora build.

== Resources ==
[http://elinux.org/RPi_Easy_SD_Card_Setup http://elinux.org/RPi_Easy_SD_Card_Setup]

== Creating an SD Image ==
You've probably already used an image tool to burn your SD card from an process similar to [[Setup:RPI]].

===Windows===
I used the windows tool [https://launchpad.net/win32-image-writer win32-image-writer].
win32-image-writer can also be used to create an image file.

# Shutdown you RPI using <code> sudo shutdown -h now </code>.
# Remove the power from the micro USB connection
# Remove the SD card from the RPi slot.
# Insert the SD card into your Windows PC card slot
# Run the ''win32-image-writer'' utility on the windows PC
::* Select the SD card in the ''device'' drop down. If you have more than one device, be careful to select to correct one.
::* Select the Imager Name to write to, make sure you select a *.img filename.
::* Press ''read'' button to burn a binary image of the SC card to the file.

The process is slow and the imager file generated will be approximated the same size as the SC card capacity. This is because the image is a binary clone of the SD card.
The img file may be zipped to reduce its size after the process is completed.

===Linux===
This uses the method given Raspberry Pi Easy SD Card Set Up referenced above: but in reverse. Any Linux machine can be used and it assumes the SD Card being backed up is not mounted. So if you only have one SD card you can't use your Pi, you have to use another Linux machine. However, if you have two SD cards capable of booting a Pi, use the one you aren't backing up to boot Pi and the backup the other, via a USB - SD card reader.

If you are using another Linux machine you can back it up to that machine or to anything, such as a NAS, that it can see. If your using your Pi it will have to be backed up to some form of extarnal storage, such as a USB HDD or a NAS.

The instruction here back up the SDd to a mount point on the Linux machine doing the backup.

Firstly mount the location that will receive the backup:

== Regular Backup ==
If you make regular changes to your RPi its worthwhile spending the time creating these images. Tim spent backing up is always saved in rebuilding.

HDMI Configuration

2012-06-13T20:10:52Z

Ajd:

[[Category: RaspberryPi]]

[http://www.69b.org/prox-pi.php/rpo/phpBB3/viewtopic.php?f=5&t=5851 http://www.69b.org/prox-pi.php/rpo/phpBB3/viewtopic.php?f=5&t=5851]

[http://elinux.org/R-Pi_ConfigurationFile http://elinux.org/R-Pi_ConfigurationFile]

[http://elinux.org/RPi_config.txt http://elinux.org/RPi_config.txt]

[http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7693 http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7693]

Example Problem:
1920 x 1080 @ 60Hz Monitor
Image format provided by RasPi, as above. Reported by monitor and by RasPi.

<pre>
tvservice -s
</pre>

Reduced image size.

lxde -> Preferences -> Monitor reports 1824 x 984

Solution (Information obtained from above references):
Generated a /boot/config.txt file
added line

<pre>
disable_overscan=1
</pre>

This put the image at full 1920 x 1080. This also put the image right to the edges; this is too close. Edited the config.txt to read.

<pre>
disable_overscan=1
overscan_left=5
overscan_right=5
overscan_top=5
overscan_bottom=5
</pre>

This gave the image a 5 pixel border.

Occasionally the RasPi reboots with a centralised colour reference square, but generally boots normally.

References above also give information as to disable the RasPi HDMI Hot-Plug Detection which will enable the HDMI output even if no Monitor is detected.

HDMI Configuration

2012-06-13T20:08:27Z

Ajd:

[[Category: RaspberryPi]]

[http://www.69b.org/prox-pi.php/rpo/phpBB3/viewtopic.php?f=5&t=5851 http://www.69b.org/prox-pi.php/rpo/phpBB3/viewtopic.php?f=5&t=5851]

[http://elinux.org/R-Pi_ConfigurationFile http://elinux.org/R-Pi_ConfigurationFile]

[http://elinux.org/RPi_config.txt http://elinux.org/RPi_config.txt]

[http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7693 http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7693]

Example Problem:
1920 x 1080 @ 60Hz Monitor
Image format provided by RasPi, as above. Reported by monitor and by RasPi.

<pre>
tvservice -s
</pre>

Reduced image size.

lxde -> Preferences -> Monitor reports 1824 x 984

Solution (Information obtained from above references):
Generated a /boot/config.txt file
added line

<pre>
disable_overscan=1
</pre>

This put the image at full 1920 x 1080. This put the image right to the edges, but was a too close. Edited the config.txt to read.

<pre>
disable_overscan=1
overscan_left=5
overscan_right=5
overscan_top=5
overscan_bottom=5
</pre>

This gave the image a 5 pixel border.

Occasionally the RasPi reboots with a centralised colour reference square, but generally boots normally.

References above also give information as to disable the RasPi HDMI Hot-Plug Detection which will enable the HDMI output even if no Monitor is detected.

HDMI Configuration

2012-06-13T20:07:26Z

Ajd:

[[Category: RaspberryPi]]

[http://www.69b.org/prox-pi.php/rpo/phpBB3/viewtopic.php?f=5&t=5851 http://www.69b.org/prox-pi.php/rpo/phpBB3/viewtopic.php?f=5&t=5851]

[http://elinux.org/R-Pi_ConfigurationFile http://elinux.org/R-Pi_ConfigurationFile]

[http://elinux.org/RPi_config.txt http://elinux.org/RPi_config.txt]

[http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7693 http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7693]

Example Problem:
1920 x 1080 @ 60Hz Monitor
Image format provided by RasPi, as above. Reported by monitor and by RasPi.

<pre>
tvservice -s
</pre>

Reduced image size.

lxde -> Preferences -> Monitor reports 1824 x 984

Solution (Information obtained from above references):
Generated a /boot/config.txt file
added line

<pre>
disable_overscan=1
</pre>

This put the image at full 1920 x 1080. This put the image right to the edges, but was a too close. Edited the config.txt to read.

<pre>
disable_overscan=1
overscan_left=5
overscan_right=5
overscan_top=5
overscan_bottom=5
</pre>

This gave the image a 5 pixel border.

Occasionally the RasPi reboots with a centralised colour reference square, but generally boots normally.

References above also give information as to disable the RasPi HDMI Hot-Plug Detection which will eneble the HDMI output even if no Monitor is detected.

ListOfRaspberryPiHow-Tos

2012-06-13T20:04:56Z

Ajd:

HDMI Configuration

2012-06-13T20:03:41Z

Ajd:

[[Category: RaspberryPi]]

[http://www.69b.org/prox-pi.php/rpo/phpBB3/viewtopic.php?f=5&t=5851 http://www.69b.org/prox-pi.php/rpo/phpBB3/viewtopic.php?f=5&t=5851]

[http://elinux.org/R-Pi_ConfigurationFile http://elinux.org/R-Pi_ConfigurationFile]

[http://elinux.org/RPi_config.txt http://elinux.org/RPi_config.txt]

[http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7693 http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7693]

Original Problem:
1920 x 1080 @ 60Hz Monitor
Image format provided by RasPi, as above. Reported by monitor and by RasPi.

<pre>
tvservice -s
</pre>

Reduced image size.

lxde -> Preferences -> Monitor reports 1824 x 984

Solution (Information obtained from above references):
Generated a /boot/config.txt file
added line

<pre>
disable_overscan=1
</pre>

This put the image at full 1920 x 1080. This put the image right to the edges, but was a too close. Edited the config.txt to read.

<pre>
disable_overscan=1
overscan_left=5
overscan_right=5
overscan_top=5
overscan_bottom=5
</pre>

This gave the image a 5 pixel border.

Occasionally the RasPi reboots with a centralised colour reference square, but generally boots normally.

References above also give information as to disable the RasPi HDMI Hot-Plug Detection which will eneble the HDMI output even if no Monitor is detected.

HDMI Configuration

2012-06-13T19:59:50Z

Ajd:

[[Category: RaspberryPi]]

[http://www.69b.org/prox-pi.php/rpo/phpBB3/viewtopic.php?f=5&t=5851 http://www.69b.org/prox-pi.php/rpo/phpBB3/viewtopic.php?f=5&t=5851]

[http://elinux.org/R-Pi_ConfigurationFile http://elinux.org/R-Pi_ConfigurationFile]

[http://elinux.org/RPi_config.txt http://elinux.org/RPi_config.txt]

[http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7693 http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7693]

Original Problem:
1920 x 1080 @ 60Hz Monitor
Image format provided by RasPi, as above. Reported by monitor and by RasPi.

tvservice -s

Reduced image size.

lxde -> Preferences -> Monitor reprts 1824 x 984

Solution (Information obtained from above references):
Generated a /boot/config.txt file
added line

disable_overscan=1

This put the image at full 1920 x 1080. This put the image right to the edges, but was a too close. Edited the config.txt to read.

disable_overscan=1
overscan_left=5
overscan_right=5
overscan_top=5
overscan_bottom=5

This gave the image a 5 pixel border.

Occasionally the RasPi reboots with a centralised colour reference square, but generally boots normally.

References above also give information as to disable the RasPi HDMI Hot-Plug Detection which will eneble the HDMI output even if no Monitor is detected.

Backup SD Image

2012-06-08T19:23:56Z

Ajd:

ListOfRaspberryPiHow-Tos

2012-06-08T19:17:07Z

Ajd:

[[Category:RaspberryPi]]
== Topics ==
This page is a list to the available RaspberryPi How-Tos.

;[[Setup:RPI]]
: initial setup and configuration and updates.

;[[HDMI Configuration]]
: Coming Soon. I've done what I wanted, need to write it up

;[[AddingUsers:RPi]]
: add a user and assign super user privledges.

;[[Updating the RPi Software]]
: Up to date software offers perfromance and security benefits

;[[Updating RPi Firmware]]
: Up to date firmware offers perfromance and security benefits

;[[Static IP Config]]
: network static IP address is useful if you RPi is to be accessed remotely

;[[Enable SSH]]
: enable SSH to allow remote login

;[[Setup VNC]]
: to access via remote desktop

;[[Expand Image to fill SD card]]
: Use the spare space assuming your SD card is larger than the default image you installed.

;[[Backup SD Image]]
: So you don't undo all your great work in a ''flash''.

;[[Enable Sound]]
: As of {{REVISIONDAY2}}/{{REVISIONMONTH}}/{{REVISIONYEAR}} the sound driver is still Alpha and is disabled by default, use this guide to enable and test sound on your RPi.

;[[Playing Music]]
: Finally something useful to do with your RPi

;[[Accessing Network Shares]]
:

;[[Run Quake]]
: Just in case you get bored or are planning a LAN party.

;[[Setting up a Torrent Server]]
: Setup your RPi to get he latest RPi distro using torrents.

ListOfRaspberryPiHow-Tos

2012-06-08T19:15:59Z

Ajd:

[[Category:RaspberryPi]]
== Topics ==
This page is a list to the available RaspberryPi How-Tos.

;[[Setup:RPI]]
: initial setup and configuration and updates.

;[[HDMI Configuration]]
: coming Soon

;[[AddingUsers:RPi]]
: add a user and assign super user privledges.

;[[Updating the RPi Software]]
: Up to date software offers perfromance and security benefits

;[[Updating RPi Firmware]]
: Up to date firmware offers perfromance and security benefits

;[[Static IP Config]]
: network static IP address is useful if you RPi is to be accessed remotely

;[[Enable SSH]]
: enable SSH to allow remote login

;[[Setup VNC]]
: to access via remote desktop

;[[Expand Image to fill SD card]]
: Use the spare space assuming your SD card is larger than the default image you installed.

;[[Backup SD Image]]
: So you don't undo all your great work in a ''flash''.

;[[Enable Sound]]
: As of {{REVISIONDAY2}}/{{REVISIONMONTH}}/{{REVISIONYEAR}} the sound driver is still Alpha and is disabled by default, use this guide to enable and test sound on your RPi.

;[[Playing Music]]
: Finally something useful to do with your RPi

;[[Accessing Network Shares]]
:

;[[Run Quake]]
: Just in case you get bored or are planning a LAN party.

;[[Setting up a Torrent Server]]
: Setup your RPi to get he latest RPi distro using torrents.