User avatar
RaTTuS
Posts: 10549
Joined: Tue Nov 29, 2011 11:12 am
Location: North West UK
Contact: Twitter YouTube

Re: USB boot now working on Pi3

Mon Sep 12, 2016 8:37 am

you may find the files in /lost+found
How To ask Questions :- http://www.catb.org/esr/faqs/smart-questions.html
WARNING - some parts of this post may be erroneous YMMV

1QC43qbL5FySu2Pi51vGqKqxy3UiJgukSX
Covfefe

User avatar
johnb_summers
Posts: 285
Joined: Thu Aug 04, 2016 7:48 pm
Location: Bushey UK

Re: USB boot now working on Pi3

Mon Sep 12, 2016 2:15 pm

RaTTuS wrote:you may find the files in /lost+found
The lost files don't matter as there is a mirror site and a backup of all the files, but what I did discover is that while files are being copied that it froze for a few seconds and during that time the hard disk made an odd vibrating sound, so I connected meters to the pi and monitored its voltage and current consumption, I found that during this freezing and disk vibration that the power supply output current went over 1 amp while the voltage dropped to below 4.8 volt, the hard drive also gained corrupted files that cant be removed, so I renamed the directory and created a new one with the same old name and moved the none corrupted files into the new directory with new versions of the corrupted ones, {removed links as it was just crashed}
Last edited by johnb_summers on Mon Sep 12, 2016 2:46 pm, edited 1 time in total.
MyPi Developer
http://mypiworld.com/
http://mypi.tech/

https://www.youtube.com/watch?v=US2nyRgg-SY&nohtml5=False

User avatar
RaTTuS
Posts: 10549
Joined: Tue Nov 29, 2011 11:12 am
Location: North West UK
Contact: Twitter YouTube

Re: USB boot now working on Pi3

Mon Sep 12, 2016 2:37 pm

you may need a better PSU ?
How To ask Questions :- http://www.catb.org/esr/faqs/smart-questions.html
WARNING - some parts of this post may be erroneous YMMV

1QC43qbL5FySu2Pi51vGqKqxy3UiJgukSX
Covfefe

asandford
Posts: 1998
Joined: Mon Dec 31, 2012 12:54 pm
Location: Waterlooville

Re: USB boot now working on Pi3

Wed Sep 14, 2016 10:42 pm

johnb_summers wrote: I think you know what I mean, experimenting or investigating will do but NEVER playing, if you use that word to describe what you yourself are doing then you don't take what your doing seriously or are making out it is not important to you, either way you are letting your ego get in the way of advancement and if part of a team the advancement of the team, on the front line nothing is reliable, that's why its called the front line and the ideas that make it reliable and part of occupied territory are 90% from fresh eyes, old engineers are just that, old, and btw I am in my 60's.
What a load of old codswallop, I 'play (1.5)' with all sorts of things all the time, but in an appropriate environment.

hippy
Posts: 7156
Joined: Fri Sep 09, 2011 10:34 pm
Location: UK

Re: USB boot now working on Pi3

Thu Sep 15, 2016 12:28 am

I have been w-----g about with other things but fully intend to have a play with both USB and PXE booting when I get the chance.

I have always found "playing" to be a perfectly apt choice of term to describe getting enjoyment from experimenting and investigating things. Having fun doesn't mean there's no seriousness involved.

underscore
Posts: 9
Joined: Thu Sep 15, 2016 7:35 am

Re: USB boot now working on Pi3

Thu Sep 15, 2016 11:44 am

Hello everyone, first post here :-)
Bevore investigating, I'm giving an eye to the netboot tutorial

https://www.raspberrypi.org/documentati ... utorial.md

As the example netboot a single machine, I would like to know in netmasq how to netboot two different folders/full raspbian installations) towards two different pi3 machines (i guess identified by the mac address) serving two different purposes.

mikerr
Posts: 2825
Joined: Thu Jan 12, 2012 12:46 pm
Location: UK
Contact: Website

Re: USB boot now working on Pi3

Thu Sep 15, 2016 3:07 pm

underscore wrote:Hello everyone, first post here :-)
Bevore investigating, I'm giving an eye to the netboot tutorial

https://www.raspberrypi.org/documentati ... utorial.md

As the example netboot a single machine, I would like to know in netmasq how to netboot two different folders/full raspbian installations) towards two different pi3 machines (i guess identified by the mac address) serving two different purposes.
After it gets bootcode.bin from your tftp server it looks for <serial>/start.elf
If it finds that file/folder then it continues loading all other files from that folder including cmdline.txt which is where you specify the nfs path for root

If you don't pre setup folders for each connecting pi, then all pi will get the same files from the tftp root (and so run same image)

E.g. I have

Code: Select all

ls /tftproot

bootcode.bin
8ac79944/

and

Code: Select all

ls /tftproot/8ac79944
cmdline.txt
config.txt
kernel7.img
kernel.img
overlays/
start.elf
You get the serial from the last 8 digits of cat /proc/cpuinfo

One of my cmdline.txt:

Code: Select all

dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.0.2:/nfs/raspilite rw ip=dhcp elevator=deadline rootwait
Android app - Raspi Card Imager - download and image SD cards - No PC required !

asandford
Posts: 1998
Joined: Mon Dec 31, 2012 12:54 pm
Location: Waterlooville

Re: USB boot now working on Pi3

Thu Sep 15, 2016 10:43 pm

underscore wrote:Hello everyone, first post here :-)
Bevore investigating, I'm giving an eye to the netboot tutorial

https://www.raspberrypi.org/documentati ... utorial.md

As the example netboot a single machine, I would like to know in netmasq how to netboot two different folders/full raspbian installations) towards two different pi3 machines (i guess identified by the mac address) serving two different purposes.
iSCSI network boot also works, so you could boot from different targets (some mucking about involed plus you need the inrfrastructure to support it).

underscore
Posts: 9
Joined: Thu Sep 15, 2016 7:35 am

Re: USB boot now working on Pi3

Fri Sep 16, 2016 9:13 pm

i'm stucked following the original guide

https://www.raspberrypi.org/documentati ... utorial.md

My pi3 server is setted to use 192.168.100.14, my broadcast is 192.168.100.255.
Also the router/gateway/dns has dchp enabled, though i reserved the first 30 for static use.

The guide state to check in daemon log for a bootcode.bin request.
I don't see such a request in daemon log (i'm keeping an empty /tftpboot in order to see such a request).
Here is my daemon.log

Code: Select all

Sep 16 20:59:25 raspberrypi dnsmasq-dhcp[538]: 653460281 available DHCP subnet: 192.168.100.255/255.255.255.0
Sep 16 20:59:25 raspberrypi dnsmasq-dhcp[538]: 653460281 vendor class: PXEClient:Arch:00000:UNDI:002001
Sep 16 20:59:25 raspberrypi dnsmasq-dhcp[538]: 653460281 PXE(eth0) b8:27:eb:4c:d8:be proxy
Sep 16 20:59:25 raspberrypi dnsmasq-dhcp[538]: 653460281 tags: eth0
Sep 16 20:59:25 raspberrypi dnsmasq-dhcp[538]: 653460281 broadcast response
Sep 16 20:59:25 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  1 option: 53 message-type  2
Sep 16 20:59:25 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 54 server-identifier  192.168.100.14
Sep 16 20:59:25 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
Sep 16 20:59:25 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size: 17 option: 97 client-machine-id  00:44:44:44:44:44:44:44:44:44:44:44:44:44...
Sep 16 20:59:25 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size: 32 option: 43 vendor-encap  06:01:03:0a:04:00:50:58:45:09:14:00:00:11...
Sep 16 20:59:28 raspberrypi dnsmasq-dhcp[538]: 653460281 available DHCP subnet: 192.168.100.255/255.255.255.0
Sep 16 20:59:28 raspberrypi dnsmasq-dhcp[538]: 653460281 vendor class: PXEClient:Arch:00000:UNDI:002001
Sep 16 20:59:28 raspberrypi dnsmasq-dhcp[538]: 653460281 PXE(eth0) b8:27:eb:4c:d8:be proxy
Sep 16 20:59:28 raspberrypi dnsmasq-dhcp[538]: 653460281 tags: eth0
Sep 16 20:59:28 raspberrypi dnsmasq-dhcp[538]: 653460281 broadcast response
Sep 16 20:59:28 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  1 option: 53 message-type  2
Sep 16 20:59:28 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 54 server-identifier  192.168.100.14
Sep 16 20:59:28 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
Sep 16 20:59:28 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size: 17 option: 97 client-machine-id  00:44:44:44:44:44:44:44:44:44:44:44:44:44...
Sep 16 20:59:28 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size: 32 option: 43 vendor-encap  06:01:03:0a:04:00:50:58:45:09:14:00:00:11...
Sep 16 20:59:30 raspberrypi dnsmasq-dhcp[538]: 653460281 available DHCP subnet: 192.168.100.255/255.255.255.0
Sep 16 20:59:30 raspberrypi dnsmasq-dhcp[538]: 653460281 vendor class: PXEClient:Arch:00000:UNDI:002001
Sep 16 20:59:30 raspberrypi dnsmasq-dhcp[538]: 653460281 PXE(eth0) b8:27:eb:4c:d8:be proxy
Sep 16 20:59:30 raspberrypi dnsmasq-dhcp[538]: 653460281 tags: eth0
tcpdump look like this

Code: Select all

[email protected]:/var/log# sudo tcpdump -i eth0 port bootpc
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
21:01:26.035059 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from b8:27:eb:4c:d8:be (oui Unknown), length 320
21:01:26.035983 IP 192.168.100.14.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 314
21:01:28.427420 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from b8:27:eb:4c:d8:be (oui Unknown), length 320
21:01:28.428340 IP 192.168.100.14.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 314
21:01:30.426975 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from b8:27:eb:4c:d8:be (oui Unknown), length 320
21:01:30.427871 IP 192.168.100.14.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 314
21:01:32.426550 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from b8:27:eb:4c:d8:be (oui Unknown), length 320
21:01:32.427445 IP 192.168.100.14.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 314
21:01:34.426109 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from b8:27:eb:4c:d8:be (oui Unknown), length 320
21:01:34.426973 IP 192.168.100.14.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 314
can you advise?

User avatar
DougieLawson
Posts: 38528
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK
Contact: Website Twitter

Re: USB boot now working on Pi3

Fri Sep 16, 2016 9:25 pm

underscore wrote: can you advise?
Try this: viewtopic.php?f=28&t=159212&p=1034463#p1034463
It's not quite the same as the published way to get network booting working, but I did it so I could get a USB stick working then use that same USB stick as the filesystem for tftp and nfs to get network booting working.
Note: Any requirement to use a crystal ball or mind reading will result in me ignoring your question.

I'll do your homework for you for a suitable fee.

Any DMs sent on Twitter will be answered next month.
All non-medical doctors are on my foes list.

underscore
Posts: 9
Joined: Thu Sep 15, 2016 7:35 am

Re: USB boot now working on Pi3

Sat Sep 17, 2016 9:57 am

Hi Dougie, well I'm coming to netbooting interest from a previous usb stick configuration (which take time to build starting from sd)
that got abruptly corrupted, still don't know if for the power (usb hub) or the stick (verbatim) or for pure bad luck.

Anyway my hw is
-one pi3 on which i'm trying the static ip / server configuration.
-one pi3 which i'm struggling to netboot
- a SINGLE hdmi monitor (being the tv)
- a suse linux laptop which in the end can be used (that would be my hope) to netboot both pi3 as client1 and client2 always with the same ip (have to buy two different coloured case to distinguish :-) )

i don't understand the thread you suggested me in at least 3 points.
First of all let's eliminate messages before you.

- xapbob before you point to a german blog from which i seem to understand two things , that we need to send somehow an option 43 and that the string "pxe-service=0,"Raspberry Pi Boot" must be changed to add 3 spaces at the end.
You did not use those suggestions, right ? I see no related changes in your dnsmasq configuration.
Didn't got if this gentleman is using Suse on the pi or somewhere else.

Now coming to your message in the thread.
- do we need an unix server program to serve files mounted specifically from a vfat partition?
this is totally strange to me :shock:
- i'm confused about the use of ip addresses outside your usual schema and the passage detached from your normal network.
why did you set a fixed ip outside your usual schema?
Can't we have in the same network an adsl router (giving some ip via dhcp),a whatever dnsmasq server netbooting pi3 clients providing them with ip and disks AND multiple pi3 clients?

User avatar
DougieLawson
Posts: 38528
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK
Contact: Website Twitter

Re: USB boot now working on Pi3

Sat Sep 17, 2016 6:12 pm

The files on my USB stick are partition #1 VFAT, /boot just like a Jessie SDCard, partition #2 rootfs ext4 just like a Jessie SDCard.

That's built exactly like https://www.raspberrypi.org/documentati ... des/msd.md
It's a good idea to get that running on your RPi3 first.

You should be able to run nfs-kernel-server with a NFS share and dnsmasq with tftp on a SuSE system with no trouble.
Note: Any requirement to use a crystal ball or mind reading will result in me ignoring your question.

I'll do your homework for you for a suitable fee.

Any DMs sent on Twitter will be answered next month.
All non-medical doctors are on my foes list.

joaocalas
Posts: 1
Joined: Sun Sep 18, 2016 3:11 pm

Re: USB boot now working on Pi3

Sun Sep 18, 2016 3:17 pm

Hello everyone! I recently aquired mi first rasoberry pi3 model b and an official power adapter with 5v and 2.5A...my question is: Is it possible to boot from an usb drive or hard drive using this?

Triple-Boot – RetroPie v4.0.2 + Raspbian + KODI (LibreELEC, OpenELEC or OSMC – you decide!)

http://www.multibootpi.com/builds/retro ... ou-decide/

thanks in advance ;)

Magiclegs
Posts: 2
Joined: Sun Sep 18, 2016 3:42 pm

Re: USB boot now working on Pi3

Sun Sep 18, 2016 4:02 pm

I followed the instructions detailed at the top of this thread and everything seemed to be going so well until reboot. Without the sd card, the boot gets stuck at the message "nonblocking pool is initiated". It seems to detect the drive and partitions fine. I'm a novice at this by the way. Here is a summary of the things I have tried:
-downloaded the new bootcode.bin and put it onto a fat32 formatted sd card as instructed in this thread. This hung the boot process with a 'kernel panic'.
-I tried replacing the 'current' bootcode file with the new one I downloaded manually, but it didn't help; I get stuck at the nonblocking pool message again.
-I increased the timeout for usb as instructed on this thread.

None of this has worked for me. Is anyone able to help? I was really enjoying myself up until this! Btw, the usb drive I'm using is one of the approved compatible ones as far as I can understand; a Sandisk Fit 16GB.

As a side note, how can I tell if the OS is running from USB while in Raspbian? My system still boots when I reinsert the sd card; I'm wondering if I'm stuck in some hinterland of booting from sd, but running from USB if that's even possible?

malvcr
Posts: 50
Joined: Mon Apr 13, 2015 3:31 am

Re: USB boot now working on Pi3

Sun Sep 18, 2016 4:26 pm

I have some little crossed feelings about this ...

Yesterday I received several PiDrives (314 GB) from WDLabs, and my first test was to try this booting experience.

But they don't boot at al, not even once, without the SD card in place, neither with the SD with only the bin file there (needs all the boot partition content to work).

Then I reconnected my SSD and it worked (I won't repeat the reboot test in this moment).

Later I will remake all the exercise from scratch to double check.

Oh, and I am using the special WDLabs cable. And I think it is needed, because when I use a standard USB 2.0 cable, the hard disk has a very hard crack noise when the shutdown is finished (as if some process is broken before time). When using the cable, the shutdown is very gentle.

User avatar
DougieLawson
Posts: 38528
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK
Contact: Website Twitter

Re: USB boot now working on Pi3

Sun Sep 18, 2016 6:08 pm

You MUST follow the detailed instructions at: https://www.raspberrypi.org/documentati ... des/msd.md

And it should "just work". Hard drive booting won't work on my B+ with just bootcode.bin on an SDCard (because that needs max_usb_current=1). The RPi3 doesn't need that option as max_usb_current is always set.
Note: Any requirement to use a crystal ball or mind reading will result in me ignoring your question.

I'll do your homework for you for a suitable fee.

Any DMs sent on Twitter will be answered next month.
All non-medical doctors are on my foes list.

underscore
Posts: 9
Joined: Thu Sep 15, 2016 7:35 am

Re: USB boot now working on Pi3

Sun Sep 18, 2016 8:55 pm

DougieLawson wrote:The files on my USB stick are partition #1 VFAT, /boot just like a Jessie SDCard, partition #2 rootfs ext4 just like a Jessie SDCard.

That's built exactly like https://www.raspberrypi.org/documentati ... des/msd.md
It's a good idea to get that running on your RPi3 first.

You should be able to run nfs-kernel-server with a NFS share and dnsmasq with tftp on a SuSE system with no trouble.
ok so..
1) installed jessie lite on an sd card
2) i created an usb stick by the meant of and used it to enable usb/net on my couple of pi3
3) booted both pi3 a couple of time with the usb stick.
4) i added the usb stick to the pi3 'server' editing /etc/fstab

Code: Select all

/dev/sda2 /tftp ext4 defaults,noatime 0 1
/dev/sda1 /tftp/boot vfat defaults 0 0
5) i have given the pi3 'server' a static ip editing dhcpcd.conf

Code: Select all

interface eth0

static ip_address=192.168.100.14/24
static routers=192.168.100.2
static domain_name_servers=192.168.100.2 
6) Updated /tftp/boot/cmdline.txt with

Code: Select all

dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.100.14:/tftp elevator=deadline rootwait ip=dhcp rw
6) Install dnsmasq on pi3 'server' and configure it with

Code: Select all

port=0
dhcp-range=192.168.100.50,192.168.100.255,300h
log-dhcp
enable-tftp
tftp-root=/tftp/boot
pxe-service=0,"Raspberry Pi Boot"
7)
Install nfs-kernel-server and configure it with

[email protected]:~ $ cat /etc/exports
/tftp *(rw,sync,no_subtree_check,no_root_squash)

8)
tested tftp from a macbook

ftp> get bootcode.bin
Received 50956 bytes in 0.3 seconds
tftp> get /tftp/boot/bootcode.bin
Received 50956 bytes in 0.2 seconds

now if i plug the pi3 'client' with nothing but a network cable to the same switch this is what i see in daemon.log

Code: Select all

ep 18 20:32:50 raspberrypi dnsmasq-dhcp[538]: 653460281 DHCPDISCOVER(eth0) b8:27:eb:4c:d8:be
Sep 18 20:32:50 raspberrypi dnsmasq-dhcp[538]: 653460281 tags: eth0
Sep 18 20:32:50 raspberrypi dnsmasq-dhcp[538]: 653460281 DHCPOFFER(eth0) 192.168.100.120 b8:27:eb:4c:d8:be
Sep 18 20:32:50 raspberrypi dnsmasq-dhcp[538]: 653460281 requested options: 43:vendor-encap, 60:vendor-class, 67:bootfile-name,
Sep 18 20:32:50 raspberrypi dnsmasq-dhcp[538]: 653460281 requested options: 128, 129, 130, 131, 132, 133, 134, 135, 66:tftp-server
Sep 18 20:32:50 raspberrypi dnsmasq-dhcp[538]: 653460281 next server: 192.168.100.14
Sep 18 20:32:50 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  1 option: 53 message-type  2
Sep 18 20:32:50 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 54 server-identifier  192.168.100.14
Sep 18 20:32:50 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 51 lease-time  12d12h
Sep 18 20:32:50 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 58 T1  6d6h
Sep 18 20:32:50 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 59 T2  10d22h30m
Sep 18 20:32:50 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option:  1 netmask  255.255.255.0
Sep 18 20:32:50 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 28 broadcast  192.168.100.255
Sep 18 20:32:50 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
Sep 18 20:32:50 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size: 17 option: 97 client-machine-id  00:44:44:44:44:44:44:44:44:44:44:44:44:44...
Sep 18 20:32:50 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size: 32 option: 43 vendor-encap  06:01:03:0a:04:00:50:58:45:09:14:00:00:11...
Sep 18 20:32:51 raspberrypi dnsmasq-dhcp[538]: 653460281 available DHCP range: 192.168.100.50 -- 192.168.100.255
Sep 18 20:32:51 raspberrypi dnsmasq-dhcp[538]: 653460281 vendor class: PXEClient:Arch:00000:UNDI:002001
Sep 18 20:32:51 raspberrypi dnsmasq-dhcp[538]: 653460281 DHCPDISCOVER(eth0) b8:27:eb:4c:d8:be
Sep 18 20:32:51 raspberrypi dnsmasq-dhcp[538]: 653460281 tags: eth0
Sep 18 20:32:51 raspberrypi dnsmasq-dhcp[538]: 653460281 DHCPOFFER(eth0) 192.168.100.120 b8:27:eb:4c:d8:be
Sep 18 20:32:51 raspberrypi dnsmasq-dhcp[538]: 653460281 requested options: 43:vendor-encap, 60:vendor-class, 67:bootfile-name,
Sep 18 20:32:51 raspberrypi dnsmasq-dhcp[538]: 653460281 requested options: 128, 129, 130, 131, 132, 133, 134, 135, 66:tftp-server
Sep 18 20:32:51 raspberrypi dnsmasq-dhcp[538]: 653460281 next server: 192.168.100.14
Sep 18 20:32:51 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  1 option: 53 message-type  2
Sep 18 20:32:51 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 54 server-identifier  192.168.100.14
Sep 18 20:32:51 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 51 lease-time  12d12h
Sep 18 20:32:51 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 58 T1  6d6h
Sep 18 20:32:51 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 59 T2  10d22h30m
Sep 18 20:32:51 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option:  1 netmask  255.255.255.0
Sep 18 20:32:51 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 28 broadcast  192.168.100.255
Sep 18 20:32:51 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
Sep 18 20:32:51 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size: 17 option: 97 client-machine-id  00:44:44:44:44:44:44:44:44:44:44:44:44:44...
Sep 18 20:32:51 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size: 32 option: 43 vendor-encap  06:01:03:0a:04:00:50:58:45:09:14:00:00:11...
Sep 18 20:32:53 raspberrypi dnsmasq-dhcp[538]: 653460281 available DHCP range: 192.168.100.50 -- 192.168.100.255
Sep 18 20:32:53 raspberrypi dnsmasq-dhcp[538]: 653460281 vendor class: PXEClient:Arch:00000:UNDI:002001
Sep 18 20:32:53 raspberrypi dnsmasq-dhcp[538]: 653460281 DHCPDISCOVER(eth0) b8:27:eb:4c:d8:be
Sep 18 20:32:53 raspberrypi dnsmasq-dhcp[538]: 653460281 tags: eth0
Sep 18 20:32:53 raspberrypi dnsmasq-dhcp[538]: 653460281 DHCPOFFER(eth0) 192.168.100.120 b8:27:eb:4c:d8:be
Sep 18 20:32:53 raspberrypi dnsmasq-dhcp[538]: 653460281 requested options: 43:vendor-encap, 60:vendor-class, 67:bootfile-name,
Sep 18 20:32:53 raspberrypi dnsmasq-dhcp[538]: 653460281 requested options: 128, 129, 130, 131, 132, 133, 134, 135, 66:tftp-server
Sep 18 20:32:53 raspberrypi dnsmasq-dhcp[538]: 653460281 next server: 192.168.100.14
Sep 18 20:32:53 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  1 option: 53 message-type  2
Sep 18 20:32:53 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 54 server-identifier  192.168.100.14
Sep 18 20:32:53 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 51 lease-time  12d12h
Sep 18 20:32:53 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 58 T1  6d6h
Sep 18 20:32:53 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 59 T2  10d22h30m
Sep 18 20:32:53 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option:  1 netmask  255.255.255.0
Sep 18 20:32:53 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 28 broadcast  192.168.100.255
Sep 18 20:32:53 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
Sep 18 20:32:53 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size: 17 option: 97 client-machine-id  00:44:44:44:44:44:44:44:44:44:44:44:44:44...
Sep 18 20:32:53 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size: 32 option: 43 vendor-encap  06:01:03:0a:04:00:50:58:45:09:14:00:00:11...
Sep 18 20:32:55 raspberrypi dnsmasq-dhcp[538]: 653460281 available DHCP range: 192.168.100.50 -- 192.168.100.255
Sep 18 20:32:55 raspberrypi dnsmasq-dhcp[538]: 653460281 vendor class: PXEClient:Arch:00000:UNDI:002001
Sep 18 20:32:55 raspberrypi dnsmasq-dhcp[538]: 653460281 DHCPDISCOVER(eth0) b8:27:eb:4c:d8:be
Sep 18 20:32:55 raspberrypi dnsmasq-dhcp[538]: 653460281 tags: eth0
Sep 18 20:32:55 raspberrypi dnsmasq-dhcp[538]: 653460281 DHCPOFFER(eth0) 192.168.100.120 b8:27:eb:4c:d8:be
Sep 18 20:32:55 raspberrypi dnsmasq-dhcp[538]: 653460281 requested options: 43:vendor-encap, 60:vendor-class, 67:bootfile-name,
Sep 18 20:32:55 raspberrypi dnsmasq-dhcp[538]: 653460281 requested options: 128, 129, 130, 131, 132, 133, 134, 135, 66:tftp-server
Sep 18 20:32:55 raspberrypi dnsmasq-dhcp[538]: 653460281 next server: 192.168.100.14
Sep 18 20:32:55 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  1 option: 53 message-type  2
Sep 18 20:32:55 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 54 server-identifier  192.168.100.14
Sep 18 20:32:55 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 51 lease-time  12d12h
Sep 18 20:32:55 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 58 T1  6d6h
Sep 18 20:32:55 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 59 T2  10d22h30m
Sep 18 20:32:55 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option:  1 netmask  255.255.255.0
Sep 18 20:32:55 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 28 broadcast  192.168.100.255
Sep 18 20:32:55 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
Sep 18 20:32:55 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size: 17 option: 97 client-machine-id  00:44:44:44:44:44:44:44:44:44:44:44:44:44...
Sep 18 20:32:55 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size: 32 option: 43 vendor-encap  06:01:03:0a:04:00:50:58:45:09:14:00:00:11...
Sep 18 20:32:57 raspberrypi dnsmasq-dhcp[538]: 653460281 available DHCP range: 192.168.100.50 -- 192.168.100.255
Sep 18 20:32:57 raspberrypi dnsmasq-dhcp[538]: 653460281 vendor class: PXEClient:Arch:00000:UNDI:002001
Sep 18 20:32:57 raspberrypi dnsmasq-dhcp[538]: 653460281 DHCPDISCOVER(eth0) b8:27:eb:4c:d8:be
Sep 18 20:32:57 raspberrypi dnsmasq-dhcp[538]: 653460281 tags: eth0
Sep 18 20:32:57 raspberrypi dnsmasq-dhcp[538]: 653460281 DHCPOFFER(eth0) 192.168.100.120 b8:27:eb:4c:d8:be
Sep 18 20:32:57 raspberrypi dnsmasq-dhcp[538]: 653460281 requested options: 43:vendor-encap, 60:vendor-class, 67:bootfile-name,
Sep 18 20:32:57 raspberrypi dnsmasq-dhcp[538]: 653460281 requested options: 128, 129, 130, 131, 132, 133, 134, 135, 66:tftp-server
Sep 18 20:32:57 raspberrypi dnsmasq-dhcp[538]: 653460281 next server: 192.168.100.14
Sep 18 20:32:57 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  1 option: 53 message-type  2
Sep 18 20:32:57 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 54 server-identifier  192.168.100.14
Sep 18 20:32:57 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 51 lease-time  12d12h
Sep 18 20:32:57 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 58 T1  6d6h
Sep 18 20:32:57 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 59 T2  10d22h30m
Sep 18 20:32:57 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option:  1 netmask  255.255.255.0
Sep 18 20:32:57 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  4 option: 28 broadcast  192.168.100.255
Sep 18 20:32:57 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
Sep 18 20:32:57 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size: 17 option: 97 client-machine-id  00:44:44:44:44:44:44:44:44:44:44:44:44:44...
Sep 18 20:32:57 raspberrypi dnsmasq-dhcp[538]: 653460281 sent size: 32 option: 43 vendor-encap  06:01:03:0a:04:00
and then nothing happen...i don't understand why the boot does not seems to proceed.
I must have done a very stupid mistake but to me look like your example which i tried to closely follow.

User avatar
DougieLawson
Posts: 38528
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK
Contact: Website Twitter

Re: USB boot now working on Pi3

Sun Sep 18, 2016 9:29 pm

Which version of the bootcode do you have?

Code: Select all

[email protected]:/boot# sha1sum bootcode.bin
3720811a5cc5593a1c4aec18cbfc6fcff0aa5d0a  bootcode.bin
[email protected]:/boot#
That comes with the sudo BRANCH=next rpi-update 4.4.17-v7+ #902 kernel
Note: Any requirement to use a crystal ball or mind reading will result in me ignoring your question.

I'll do your homework for you for a suitable fee.

Any DMs sent on Twitter will be answered next month.
All non-medical doctors are on my foes list.

malvcr
Posts: 50
Joined: Mon Apr 13, 2015 3:31 am

Re: USB boot now working on Pi3

Mon Sep 19, 2016 12:24 am

My last test for today (I god a headache doing this).

I made a full clean install following the instructions on the PiDrive device with all the latest software versions.

It doesn't boot without the SD card, no way.

When I add the empty TIMEOUT file, it boots, but only the first time after I provide the electricity. When I made a reboot (by shutdown or pressing Ctrl-Alt-Delete), it is gone ... color screen but frozen. I even included the program_usb_timeout=1 ... but it is the same.

So, I will keep the SD card, just that with only the /boot partition contents on it.

User avatar
DougieLawson
Posts: 38528
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK
Contact: Website Twitter

Re: USB boot now working on Pi3

Mon Sep 19, 2016 12:37 am

Have you done the one-shot boot with

Code: Select all

program_usb_boot_mode=1
in config.txt?

Check that with a vcgencmd otp_dump | grep 17: command.
Note: Any requirement to use a crystal ball or mind reading will result in me ignoring your question.

I'll do your homework for you for a suitable fee.

Any DMs sent on Twitter will be answered next month.
All non-medical doctors are on my foes list.

malvcr
Posts: 50
Joined: Mon Apr 13, 2015 3:31 am

Re: USB boot now working on Pi3

Mon Sep 19, 2016 12:58 am

Yes, ...

program_usb_boot_mode=1

This is a RPI3 I have been using to try this booting procedure since several weeks ago. So that was already burned on it.

If it is safe to do it in another RPI3, I could try with another machine just in case "something" happened with the machine I am using right now to boot the PiDrive (was the same machine I used to try a SanDisk SSD before). :-) ... this type of raspberries don't grow on the trees, and this is why I restricted my tests to only one machine.

User avatar
DougieLawson
Posts: 38528
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK
Contact: Website Twitter

Re: USB boot now working on Pi3

Mon Sep 19, 2016 1:12 am

Your machines, your choice. It doesn't stop them booting from a regular SDCard.
Note: Any requirement to use a crystal ball or mind reading will result in me ignoring your question.

I'll do your homework for you for a suitable fee.

Any DMs sent on Twitter will be answered next month.
All non-medical doctors are on my foes list.

underscore
Posts: 9
Joined: Thu Sep 15, 2016 7:35 am

Re: USB boot now working on Pi3

Mon Sep 19, 2016 6:28 am

DougieLawson wrote:Which version of the bootcode do you have?

Code: Select all

[email protected]:/boot# sha1sum bootcode.bin
3720811a5cc5593a1c4aec18cbfc6fcff0aa5d0a  bootcode.bin
[email protected]:/boot#
That comes with the sudo BRANCH=next rpi-update 4.4.17-v7+ #902 kernel
i think you were answering to malvcr but we are multiple asking and the thread goes complicate :-)
Mine is like your.

[email protected]:/ $ shasum /boot/bootcode.bin
3720811a5cc5593a1c4aec18cbfc6fcff0aa5d0a /boot/bootcode.bin
[email protected]:/ $ shasum /tftp/boot/bootcode.bin
3720811a5cc5593a1c4aec18cbfc6fcff0aa5d0a /tftp/boot/bootcode.bin

(i start to get paranoid, i checked both copies!)

the point to me is that both nfs-kernel-server and dnsmasq are not the kind of programs one is usually fluent in before buying headless/diskless computers.
The guide on the website didn't worked for me.
You are using a Pi2 as server while i have a Pi3 also for that role..
Is it maybe possible to publish a stripped down jessie lite image with a working configuration enabled?

User avatar
DougieLawson
Posts: 38528
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK
Contact: Website Twitter

Re: USB boot now working on Pi3

Mon Sep 19, 2016 10:29 am

I've never looked at Jessie Lite. I'll see what I can do today or tomorrow.
Note: Any requirement to use a crystal ball or mind reading will result in me ignoring your question.

I'll do your homework for you for a suitable fee.

Any DMs sent on Twitter will be answered next month.
All non-medical doctors are on my foes list.

mikerr
Posts: 2825
Joined: Thu Jan 12, 2012 12:46 pm
Location: UK
Contact: Website

Re: USB boot now working on Pi3

Mon Sep 19, 2016 10:35 am

I've had a USB booting Jessie Lite image up for a while at
https://sourceforge.net/projects/pi-usb-root/

That can be written direct to USB disk with win32diskimager
Android app - Raspi Card Imager - download and image SD cards - No PC required !

Return to “General discussion”