Can't get my new Raspberry Pi to boot

[jamessct]

I received this starter Raspberry Pi 3 starter pack, and opened it today:

https://www.amazon.co.uk/Create-Raspber ... +kit&psc=1

My first attempt to boot it up went fine, but I decided I wanted to put it in the case before using it any further. I shut it down using the shutdown option in the top left menu, and removed all cables. Next time I tried booting it up after carefully inserting it into the case, nothing came up on the screen. I've tried removing it from the case, and booting it up with another display but still no luck. I had a read of the booting sticky on here, which mentions the significance of the LEDs. I have a solid red LED only, which if I'm not mistaken suggests an issue with reading the SD card.

Is it possible that an official SD with the OS preloaded could have become corrupted after only one use? Where do I go from here? I am a complete beginner to the Raspberry Pi and was very much relying on it working with a straightforward set-up.

Thanks in advance for any advice.

[klricks]

Are you sure the board is properly snapped into the case and the SD card is fully inserted in the slot?

[Dis93]

Whilst corruption is possible, it is unlikely. Take the microSD card out and reinsert it. I have my Pi3b in a case and a couple of times I have put a card into the Pi and missed the slot due to a small gap in the case and inserted the card below the slot. Doh!

[jamessct]

Yep, to clarify I have tried unplugging and replugging everything in and out of the case a number of times now to no avail. microSD included.

I certainly have the microSD inserted as fully as it goes, what I am worrying about is whether it is possible that I have managed to push something out of place on the board while putting it in the case? This hopefully shouldn't be the case as I was careful with it and there isn't any visible damage to it - I just worry as the Pi seems so fragile Assuming everything is inserted properly, does this mean either damage to the hardware or corruption to the SD card as the options?

[Dis93]

It is hard not to sound condescending when trouble shooting on a forum, I'm trying not to be... you do have the microSD card with the contacts facing down onto the board?
I think the Pi is quite robust for what it is, it was designed for kids to play about with and I've found the ports really solid.
Have you taken the Pi out of the case and tried everything again?

[Rive]

Eliminate the sdcard as the problem. Get another sdcard, and using diskimager, write the raspbian jessie image to it. Be sure to expand the file system.

In general, some advice on updating and upgrading:
DO NOT do 'rpi-update'
DO NOT do 'dist-upgrade'

DO:

Code: Select all

sudo apt-get update
sudo apt-get upgrade

If it boots, then you have a problem with the image on sdcard or sdcard, if it doesn't boot, then something else is the issue; it possibly may have been damaged somehow, or you may have mis-configuration.

You are just chasing your tail atm.


jesssie:
https://www.raspberrypi.org/downloads/raspbian/


diskimager:
https://sourceforge.net/projects/win32d ... t/download


For future reference, when you shutdown via menu, Do Not remove power to the pi3 until the red and green light are both solid (otherwise, this issue (non-boot) can occur).

[jamessct]

It is hard not to sound condescending when trouble shooting on a forum, I'm trying not to be... you do have the microSD card with the contacts facing down onto the board?
I think the Pi is quite robust for what it is, it was designed for kids to play about with and I've found the ports really solid.
Have you taken the Pi out of the case and tried everything again?

Don't worry about sounding condescending, I don't doubt it is entirely possible I'm doing something stupid!

However, I can say for sure the microSD is going in the correct way. I've also just given it another go out of the case now that it has had some time switched off and I'm still getting just the solid red light and no display. Tried plugging it into an old monitor with an analogue cable (I am correct in saying this can be done?) to eliminate an issue with the TV or HDMI cable, still no joy!

As for the other reply regarding eliminating the microSD as the issue, I have to go away for the next hour or so but I may need some clarification on how to go about this step later

[Rive]

Tried plugging it into an old monitor with an analogue cable (I am correct in saying this can be done?)

No. HDMI or DVI. VGA requires a special component to work. Try your HDTV via HDMI instead.

[jamessct]

Ah right, I only really have one HDMI screen to hand that I can plug into at the moment (the original one I was using). It seems pretty unlikely that the display is the issue though given the solid red light status. I've found a spare SD, will give that a shot tomorrow.

Cheers everyone that has chimed in so far

[rpdom]

DO NOT do 'dist-upgrade

You keep saying this, but I don't understand why.

Have you had a bad experience of dist-upgrade on another system?

On Raspbian it should be fine to run it instead of plain upgrade. It is nothing like the rpi-update (there is no "raspi-update" command).

[jamessct]

....And it is working once more with the new microSD installed. Seems my official raspberry one managed to become defunct with just one use, don't know what that's about but I see now it isn't showing up on my PC either.

Ah well, I'm off to play with my new toy

[Rive]

DO NOT do 'dist-upgrade

You keep saying this, but I don't understand why.

Have you had a bad experience of dist-upgrade on another system?

On Raspbian it should be fine to run it instead of plain upgrade. It is nothing like the rpi-update (there is no "raspi-update" command).

opps. i meant 'rpi".

Yeah it breaks things. I want what i have installed to work ( I have a heavily customized/modified debian-raspbian OS on my Pi3, I don't have the time to go through it all and fix stuff after a 'dist-upgrade'). Hell, I rely on backup images, because I made so many changes that I can't remember what they are anymore. In any event, I will never use dist-upgrade again. ever.

Anyone who has customized their OS, needs to also seriously consider using dist-upgrade. Safer to stick with 'apt-get upgrade' instead.

Using upgrade keeps to the rule: under no circumstances are currently installed packages removed, or packages not already installed retrieved and installed.

apt-get upgrade will not change what is installed (only versions),
apt-get dist-upgrade will install or remove packages as necessary to complete the upgrade,
apt upgrade will automatically install but not remove packages.
apt full-upgrade performs the same function as apt-get dist-upgrade

[klricks]

...... ( I have a heavily customized/modified debian-raspbian OS on my Pi3,.....

Did any of your modifications include adding / changing the default repository / source lists? If so all bets are off as to keeping a stable OS after upgrades..

[rpdom]

Anyone who has customized their OS, needs to also seriously consider using dist-upgrade. Safer to stick with 'apt-get upgrade' instead.

If you have something in your "customised" OS that depends on a particular version of a package being installed, then you are better off not even using upgrade.

dist-upgrade will only remove packages if they clash with a newer version of another package, and will only add packages if dependencies of an installed package change because of an upgrade.

Also, upgrade or dist-upgrade will tell you what it is going to do and then ask if that is OK, unless you use the -y option. I'd recommend never using the -y option with dist-upgrade and actually reading what it is planning to do.

Stating that dist-upgrade is dangerous to use is just spreading FUD. For the majority of users (those that haven't mangled their OS), it is perfectly safe and telling them not to use it could prevent them receiving necessary updates.

[Rive]

Anyone who has customized their OS, needs to also seriously consider using dist-upgrade. Safer to stick with 'apt-get upgrade' instead.

If you have something in your "customised" OS that depends on a particular version of a package being installed, then you are better off not even using upgrade.

dist-upgrade will only remove packages if they clash with a newer version of another package, and will only add packages if dependencies of an installed package change because of an upgrade.

Also, upgrade or dist-upgrade will tell you what it is going to do and then ask if that is OK, unless you use the -y option. I'd recommend never using the -y option with dist-upgrade and actually reading what it is planning to do.

Stating that dist-upgrade is dangerous to use is just spreading FUD. For the majority of users (those that haven't mangled their OS), it is perfectly safe and telling them not to use it could prevent them receiving necessary updates.

I use upgrade all the time, no issues, I use dist-upgrade and it wiped out my custom lxpanel lockscreen keybinding in config/openbox/lxde-pi-rc.xml.
In any event, I am fine with apt-get update. I have backups that I can restore anytime if need be.

apt-get update
apt-get upgrade

All I will ever use, and all I will ever recommend to others.

New theme I am working on atm... replacing old system icons with new custom ones...
http://s32.postimg.org/s5m5ga6h1/2016_0 ... _scrot.png