Using USB to boot on Pi3

[Soumyajit Chatterjee]

Dear Concern,

I have been trying hard to boot my Pi 3 through my pen drive. The details of what I am trying can be summarized as follows:

1) USB Drive has RedSleeve burnt in it.
2) The regular sd card has latest Raspbian.

I have tried all the possible alternatives to make it boot through the USB drive but all in vain.
Any help will highly be helpful.

[DougieLawson]

You need the BRANCH=next firmware/bootcode/kernel.
Get that with sudo BRANCH=next rpi-update && rebootand the system will come back up with a 4.9.13-v7+ kernel.

You need to enable your RPI3 for USB/PXE booting and copy the SDCard to your USB stick.

Try following these simple clear and concise instructions
https://www.raspberrypi.org/documentati ... des/msd.md

[RaTTuS]

have you read this thread viewtopic.php?f=63&t=155167

[Soumyajit Chatterjee]

You need the BRANCH=next firmware/bootcode/kernel.
Get that with sudo BRANCH=next rpi-update && rebootand the system will come back up with a 4.9.13-v7+ kernel.

You need to enable your RPI3 for USB/PXE booting and copy the SDCard to your USB stick.

Try following these simple clear and concise instructions
https://www.raspberrypi.org/documentati ... des/msd.md

Thanks for answering!!! I have already tried this... But here the issue that I am facing is that rpi-update is not working and is giving an error of connection refused. And, the other query is that if I copy the contents of the sd card to the usb stick both of them will have the same OS.

[Soumyajit Chatterjee]

have you read this thread viewtopic.php?f=63&t=155167

Thanks!!!.. But I am trying with two different OSs in the sd card and usb disk respectively.

[DougieLawson]

... the issue that I am facing is that rpi-update is not working and is giving an error of connection refused.

Finally, you've told us the error that needs to be fixed.

Get the results from these commands.
ip addr show
ip route
ping -c3 $(ip route | awk '/default/ {print $3}')
ping -c3 8.8.8.8
ping -c3 google.com
cat /etc/resolv.conf
traceroute raw.githubusercontent.com

The instructions tell you how to copy your SDCard to your USB stick, they also tell you exactly what needs to change once you've done that copy.

[Soumyajit Chatterjee]

... the issue that I am facing is that rpi-update is not working and is giving an error of connection refused.

Finally, you've told us the error that needs to be fixed.

Get the results from these commands.
ip addr show
ip route
ping -c3 $(ip route | awk '/default/ {print $3}')
ping -c3 8.8.8.8
ping -c3 google.com
cat /etc/resolv.conf
traceroute raw.githubusercontent.com

The instructions tell you how to copy your SDCard to your USB stick, they also tell you exactly what needs to change once you've done that copy.

ip addr show

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group defaul

t qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP gr

oup default qlen 1000
link/ether b8:27:eb:a9:f5:bb brd ff:ff:ff:ff:ff:ff
inet 192.168.2.100/24 brd 192.168.2.255 scope global eth0
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP g

roup default qlen 1000
link/ether b8:27:eb:fc:a0:ee brd ff:ff:ff:ff:ff:ff
inet 192.168.1.13/24 brd 192.168.1.255 scope global wlan0
valid_lft forever preferred_lft forever


ip route


0.0.0.0 dev eth0 scope link metric 202
default via 192.168.1.1 dev wlan0
default dev eth0 scope link metric 202
default via 192.168.1.1 dev wlan0 metric 303
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.13
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.13 metric 303
192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.100 metric 202

ping -c3 $(ip route | awk '/default/ {print $3}')
ping: unknown host eth0


ping -c3 8.8.8.8

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

--- 8.8.8.8 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2003ms


ping -c3 google.com
PING google.com (216.58.220.206) 56(84) bytes of data.

--- google.com ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2003ms


cat /etc/resolv.conf
# Generated by resolvconf
nameserver 192.168.1.1

traceroute raw.githubusercontent.com
traceroute to raw.githubusercontent.com (151.101.12.133), 30 hops max, 60 byte packets
1 http://www.routerlogin.com (192.168.1.1) 8.783 ms 8.985 ms 9.044 ms
2 10.5.20.2 (10.5.20.2) 9.099 ms 9.153 ms 9.283 ms
3 10.118.1.54 (10.118.1.54) 9.786 ms 10.034 ms 10.106 ms
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 * * *

A few more information, from my side:
1) I am able to access internet from the Pi3.
2) Pi 3 is connected to the internet via Wifi.
3) The internet is operating behind a proxy.
4) sudo UPDATE_SELF=0 rpi-update
*** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
*** No hash received from github: https://api.github.com/repos/Hexxeh/rpi ... ads/master
curl: (7) Failed to connect to api.github.com port 443: Connection refused
5) sudo rpi-update
*** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
*** Performing self-update
!!! Failed to download update for rpi-update!
!!! Make sure you have ca-certificates installed and that the time is set correctly
6) I am able to use git clone...

[DougieLawson]

How is it connected, it looks like your default route should be by WiFi (wlan0)?

sudo ip route del 0.0.0.0 dev eth0
sudo ip route del default dev eth0

What's in /etc/network/interfaces
What's in /etc/dhcpcd.conf

[Soumyajit Chatterjee]

How is it connected, it looks like your default route should be by WiFi (wlan0)?

sudo ip route del 0.0.0.0 dev eth0
sudo ip route del default dev eth0

What's in /etc/network/interfaces
What's in /etc/dhcpcd.conf

Yes, the default is wifi,

/etc/network/interfaces

# interfaces(5) file used by ifup(8) and ifdown(8)

# Please note that this file is written to be used with dhcpcd
# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'

# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d

auto wlan0
iface lo inet loopback

iface eth0 inet dhcp

allow-hotplug wlan0
iface wlan0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

allow-hotplug wlan1
iface wlan1 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf




/etc/dhcpcd.conf
# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.

# Allow users of this group to interact with dhcpcd via the control socket.
#controlgroup wheel

# Inform the DHCP server of our hostname for DDNS.
hostname

# Use the hardware address of the interface for the Client ID.
clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
#duid

# Persist interface configuration when dhcpcd exits.
persistent

# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit

# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Most distributions have NTP support.
option ntp_servers
# Respect the network MTU.
# Some interface drivers reset when changing the MTU so disabled by default.
#option interface_mtu

# A ServerID is required by RFC2131.
require dhcp_server_identifier

# Generate Stable Private IPv6 Addresses instead of hardware based ones
slaac private

# A hook script is provided to lookup the hostname if not set by the DHCP
# on the server to actually work.
option rapid_commit

# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Most distributions have NTP support.
option ntp_servers
# Respect the network MTU.
# Some interface drivers reset when changing the MTU so disabled by default.
#option interface_mtu

# A ServerID is required by RFC2131.
require dhcp_server_identifier

# Generate Stable Private IPv6 Addresses instead of hardware based ones
slaac private

# A hook script is provided to lookup the hostname if not set by the DHCP
# server, but it should not be run by default.
nohook lookup-hostname

[DougieLawson]

sudo ifconfig eth0 down
sudo ifconfig eth0 0.0.0.0

If that doesn't work then pull the cable out of the ethernet and reboot.

Then see if sudo BRANCH=next rpi-update works.

[Soumyajit Chatterjee]

sudo ifconfig eth0 down
sudo ifconfig eth0 0.0.0.0

If that doesn't work then pull the cable out of the ethernet and reboot.

Then see if sudo BRANCH=next rpi-update works.

No.. Still showing same error... I have pulled the cable out.. Still no luck..
Another thing that I tried:
sudo UPDATE_SELF=0 rpi-update
*** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
*** No hash received from github: https://api.github.com/repos/Hexxeh/rpi ... ads/master
curl: (7) Failed to connect to api.github.com port 443: Connection refused
Btw... Thanks for the help...

[DougieLawson]

You need to fix your borken networking. Once you've done that it should "just work™".

[Soumyajit Chatterjee]

You need to fix your borken networking. Once you've done that it should "just work™".

All the things that were to be "tweaked" I am done with them. Don't know from where still the problem is existing....

[DougieLawson]

I'd start with a reboot of your router and end with a phone call to your ISP.

[Soumyajit Chatterjee]

I'd start with a reboot of your router and end with a phone call to your ISP.

... I think I will have to proceed the same way.. I have just installed a fresh copy of Raspbian with only Wifi connected and let's see what is left as surprise...

[Soumyajit Chatterjee]

At last after three installations of the Raspbian OS (I owe this to my senior @Abhijit Da)

All these are from the command terminal of Pi 3
1) Run:

Code: Select all

sudo -i

2) Run:

Code: Select all

export http_proxy=http://proxy.server.ip.addr:port

Code: Select all

export https_proxy=http://proxy.server.ip.addr:port

These two are the main steps that he told me to add....
3) BRANCH=next rpi-update



Thanks to all who tried to help me....