Yoyojacky: Created page with "==INSTALLING OPERATING SYSTEM IMAGES ON LINUX== Etcher is typically the easiest option for most users to write images to SD cards, so it is a good place to start.
If you'r..."

2018-03-01T05:24:58Z

Created page with "==INSTALLING OPERATING SYSTEM IMAGES ON LINUX== Etcher is typically the easiest option for most users to write images to SD cards, so it is a good place to start. If you'r..."

New page

==INSTALLING OPERATING SYSTEM IMAGES ON LINUX==
Etcher is typically the easiest option for most users to write images to SD cards, so it is a good place to start. 
If you're looking for more advanced options on Linux, you can use the standard command line tools below. 
<pre>
Note: use of the dd tool can overwrite any partition of your machine.
If you specify the wrong device in the instructions below, you could delete your primary Linux partition.
Please be careful.
</pre>
==DISCOVERING THE SD CARD MOUNT POINT AND UNMOUNTING IT==
* Run lsblk to see which devices are currently connected to your machine.
<pre>
If your computer has a slot for SD cards, insert the card.
If not, insert the card into an SD card reader, then connect the reader to your computer.
</pre>
* Run lsblk again.
<pre>
The new device that has appeared is your SD card (you can also usually tell from the listed device size).
The naming of the device will follow the format described in the next paragraph.
The left column of the results from the lsblk command gives the device name of your SD card
and the names of any partitions on it (usually only one, but there may be several if the card was previously used).
It will be listed as something like /dev/mmcblk0 or /dev/sdX (with partition names /dev/mmcblk0p1 or /dev/sdX1 respectively),
where X is a lower-case letter indicating the device (eg. /dev/sdb1).
The right column shows where the partitions have been mounted (if they haven't been, it will be blank).

If any partitions on the SD card have been mounted, unmount them all with umount,
for example umount /dev/sdX1 (replace sdX1 with your SD card's device name, and change the number for any other partitions).
</pre>
==COPYING THE IMAGE TO THE SD CARD==
<pre>
In a terminal window, write the image to the card with the command below,
making sure you replace the input file if= argument with the path to your .img file,
and the /dev/sdX in the output file of= argument with the correct device name.
This is very important, as you will lose all the data on the hard drive if you provide the wrong device name.
Make sure the device name is the name of the whole SD card as described above, not just a partition.
For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1.
</pre>
* dd bs=4M if=2017-11-29-raspbian-stretch.img of=/dev/sdX conv=fsync
<pre>
Please note that block size set to 4M will work most of the time.
If not, try 1M, although this will take considerably longer.
</pre>
Also note that if you are not logged in as root you will need to prefix this with sudo.
==COPYING A ZIPPED IMAGE TO THE SD CARD==
In Linux it is possible to combine the unzip and SD copying process into one command, 
which avoids any issues that might occur when the unzipped image is larger than 4GB. 
This can happen on certain filesystems that do not support files larger than 4GB (e.g. FAT), 
although it should be noted that most Linux installations do not use FAT and therefore do not have this limitation. 

The following command unzips the zip file (replace 2017-11-29-raspbian-stretch.zip with the appropriate zip filename), 
and pipes the output directly to the dd command. 
This in turn copies it to the SD card, as described in the previous section. 
----
<pre>
unzip -p 2017-11-29-raspbian-stretch.zip | sudo dd of=/dev/sdX bs=4M conv=fsync
</pre>
==CHECKING THE IMAGE COPY PROGRESS==
By default, the dd command does not give any information about its progress, so it may appear to have frozen. 
It can take more than five minutes to finish writing to the card. 
If your card reader has an LED, it may blink during the write process. 
 
To see the progress of the copy operation, you can run the dd command with the status option. 
<pre>
dd bs=4M if=2017-11-29-raspbian-stretch.img of=/dev/sdX status=progress conv=fsync
</pre>
If you are using an older version of dd, the status option may not be available. 
You may be able to use the dcfldd command instead, which will give a progress report showing how much has been written. 
Another method is to send a USR1 signal to dd, which will let it print status information. 
Find out the PID of dd by using
<pre>
pgrep -l dd or ps a | grep dd
</pre>
Then use
<pre>
kill -USR1 PID
</pre>
to send the USR1 signal to dd.
==CHECKING WHETHER THE IMAGE WAS CORRECTLY WRITTEN TO THE SD CARD==
After dd has finished copying, you can check what has been written to the SD card by dd-ing from the card back to another image on your hard disk; 
truncating the new image to the same size as the original; 
and then running diff (or md5sum) on those two images. 

If the SD card is bigger than the original image size, dd will make a copy of the whole card. 
We must therefore truncate the new image to the size of the original image. 
Make sure you replace the input file if= argument with the correct device name. 
diff should report that the files are identical. 
<pre>
dd bs=4M if=/dev/sdX of=from-sd-card.img
truncate --reference 2017-11-29-raspbian-stretch.img from-sd-card.img
diff -s from-sd-card.img 2017-11-29-raspbian-stretch.img
</pre>
Run sync. This will ensure the write cache is flushed and that it is safe to unmount your SD card.
 
Remove the SD card from the card reader. 
----

Linux - Revision history

Yoyojacky: Created page with "==INSTALLING OPERATING SYSTEM IMAGES ON LINUX== Etcher is typically the easiest option for most users to write images to SD cards, so it is a good place to start. If you'r..."

Yoyojacky: Created page with "==INSTALLING OPERATING SYSTEM IMAGES ON LINUX== Etcher is typically the easiest option for most users to write images to SD cards, so it is a good place to start.
If you'r..."