[solved] Disk Images doesn't work (at least for me)

Help and Support Raspberry Pi
1

Hi,

Today I tried to install last release on both a pi 1 and pi 2. So I downloaded the 2 disks images 2016.04-1. I checked the checksum and it was ok for both image. I did this after

For pi 1

$ gunzip -d OSMC_TGT_rbp1_20160403.img.gz
$ sudo dd if=OSMC_TGT_rbp1_20160403.img of=/dev/sdc

For pi 2

$ gunzip -d OSMC_TGT_rbp2_20160403.img.gz
$ sudo dd if=OSMC_TGT_rbp2_20160403.img of=/dev/sdc

I boot pi 1 and installation was done. After restart, the boot is blocked and I can’t do anything except remove power supply. I tried to reboot several times, reinstall image on sd, reinstall osmc, but it never started. Below a link to a pictureshot :wink: (30 days public)

http://ovh.to/xuos2eG

For the pi 2 the problem is simple. When I boot the pi, I have a rainbow screen and that’s all. I also tried to reinstall image on sd card. I checked if a partition was created and with content, it was done with installation boot and files.

One more point, SD cards aren’t the same. Yesterday a friend told me that he couldn’t install osmc. He used windows and the image maker, but I couldn’t tell you more.

2

Use the official OSMC installer.

Or append conv=fdatasync. There’s no evidence your buffer is getting written out or even to the right device.

3

I successfully installed a raspbian on sd card yesterday.
I tried multiples way for pi 2, this morning.

First try : dd with sync

SD state

$ lsblk
NAME                   MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sdc                      8:32   1   7,2G  0 disk  
├─sdc1                   8:33   1    60M  0 part  /run/media/ioo/boot
└─sdc2                   8:34   1     3G  0 part  /run/media/ioo/eda95d8a-9cdd-4224-96d0-890b4791600c

Installation

$ gunzip -d OSMC_TGT_rbp2_20160403.img.gz
$ sudo dd if=OSMC_TGT_rbp2_20160403.img of=/dev/sdc
524288+0 enregistrements lus
524288+0 enregistrements écrits
268435456 bytes (268 MB, 256 MiB) copied, 45,6097 s, 5,9 MB/s
$ sync

SD state after

$ lsblk
NAME                   MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sdc                      8:32   1   7,2G  0 disk  
└─sdc1                   8:33   1   243M  0 part  /run/media/ioo/35D0-C06B

Checksum of files in sd

$ for i in $(ls .);do md5sum $i;done
84d279839c772d3a040b80187388975b bootcode.bin
d2c61a0cc814b4657ef8690d9484c40f cmdline.txt
f32be7a0c6d16d01f540d1e6023b640b config.txt
f2e185f06d16f857f639a2246ab85431 filesystem.tar.xz
bbd14a866e6df4f852b1667442450e06 fixup_cd.dat
585b909f6700f1b347cda29c2d359f3f kernel.img
9420edea03120b1298621e98bea5b29f start_cd.elf

Result : blocked on rainbow screen

Second try : dd with conv option

SD state

$ sudo dd if=/dev/zero of=/dev/sdc bs=512 count=20 conv=fdatasync
20+0 enregistrements lus
20+0 enregistrements écrits
10240 bytes (10 kB, 10 KiB) copied, 0,0207219 s, 494 kB/s
$ lsblk
NAME                   MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sdc                      8:32   1   7,2G  0 disk

Installation

$ sudo dd if=OSMC_TGT_rbp2_20160403.img of=/dev/sdc conv=fdatasync
524288+0 enregistrements lus
524288+0 enregistrements écrits
268435456 bytes (268 MB, 256 MiB) copied, 110,341 s, 2,4 MB/s
$ lsblk
NAME                   MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sdc                      8:32   1   7,2G  0 disk
└─sdc1                   8:33   1   243M  0 part  /run/media/ioo/35D0-C06B

Checksum of files in sd

$ for i in $(ls .);do md5sum $i;done
84d279839c772d3a040b80187388975b  bootcode.bin
d2c61a0cc814b4657ef8690d9484c40f  cmdline.txt
f32be7a0c6d16d01f540d1e6023b640b  config.txt
7742d7bc87c1be9c69834680e4f44456  filesystem.tar.xz
bbd14a866e6df4f852b1667442450e06  fixup_cd.dat
585b909f6700f1b347cda29c2d359f3f  kernel.img
9420edea03120b1298621e98bea5b29f  start_cd.elf

Result : blocked on rainbow screen

As you can see, filesystem.tar.gz md5sum are not the same.

Third try : osmc installer on archlinux.

I used this archlinux package AUR (en) - osmc-installer-bin

checksum of file on sd card

84d279839c772d3a040b80187388975b  bootcode.bin
d2c61a0cc814b4657ef8690d9484c40f  cmdline.txt
f32be7a0c6d16d01f540d1e6023b640b  config.txt
7742d7bc87c1be9c69834680e4f44456  filesystem.tar.xz
bbd14a866e6df4f852b1667442450e06  fixup_cd.dat
585b909f6700f1b347cda29c2d359f3f  kernel.img
513abe7a87e579f5a9a209169f66b9bd  preseed.cfg
9420edea03120b1298621e98bea5b29f  start_cd.elf

Result : blocked on rainbow screen

As you can see, one more files is in sd card preseed.cfg

My last try was with installer and 2016.02-3 image and the pi is still blocked on rainbow screen :confused:

4

Indicates wrong image. Post a picture of the Pi you are installing your Pi1 image and a picture of the Pi you are installing your Pi2 image

5

Looks correct for a Pi2

84d279839c772d3a040b80187388975b  bootcode.bin
d2c61a0cc814b4657ef8690d9484c40f  cmdline.txt
f32be7a0c6d16d01f540d1e6023b640b  config.txt
7742d7bc87c1be9c69834680e4f44456  filesystem.tar.xz
bbd14a866e6df4f852b1667442450e06  fixup_cd.dat
585b909f6700f1b347cda29c2d359f3f  kernel.img
209f70af41d2d26fbe2930027d642139  preseed.cfg
9420edea03120b1298621e98bea5b29f  start_cd.elf
6

Pi 1 : onboard Raspberry Pi © 2011.12 but it’s not blocked on rainbow screen. it’s a sd card

Pi 2 : onboard Raspberry Raspberry Pi model B+ V1 2 © Raspberry Pi 2014. Blocked on rainbow screen, it’s a micro sd card. Raspbian install with rpbi 2 image was successfull yesterday

7

This is a Pi1 not a Pi2! Use the Pi1 Image and it will boot.

8

You think the same way as me, What a noob ! I am really sorry you waste your time for such an easy information to understand. Thank you very much for your help, I downloaded image of raspberry 1 and installation works like a charm.

I had a look in raspbian images and both rpbi1 and 2 firmware are in /boot, so it worked :confused:

Thank you again