Switching On and OFF Is there an ideal sequence

[Rastus]

When we have a unit working and connected to the TV It comes to a time when it has to be disconnected, and when we get into a plane running again.
Is there a ideal or correct was to switch all the various bits of kit and software on and off??

[trapdoor]

Just unplug it to power down. The RPi is very robust, unlike a PC!!

To power up, I connect the power and usually wait a couple of minutes before attaching with the iPad and starting up the apps, just to ensure all of the subsystems (ARF, DVB module etc) have initialised as I have had a problem with the ARF sometimes failing to transmit if you connect to the unit as soon as the SSID comes up.

[Admin]

Usually a raspberry pi must be halted before removing the power, or the disk can be trashed.
I use a very neat trick where I boot the disk in a readonly mode, this makes it tolerant to removing the power without halting.
There is the odd occasion when the disk is in a writable mode, for instance when you enter the license key. At some point in the future, it is likely that updates will be done whilst the system is running, and hence similar care will need to be taken

Thx
Lee

[Rastus]

How do we manage to adopt your trick Lee
 
" very neat trick where I boot the disk in a read only mode"

Please??

[Admin]

How do we manage to adopt your trick Lee
  " very neat trick where I boot the disk in a read only mode"
Please??

Sorry, I did not explain well enough.
The PilotAware software installation does this automatically.
So pulling the power should not be an issue.

I was trying to explain that in a normal Raspberry Pi installation, such as installing NOOBS, you should
not simply pull the power, because this will cause the SD card to no longer reboot.

For PilotAware - no such worries

[rasputin2068]

Hello Lee

Finally got it all sorted and working yesterday, better power supply , could connect with IPad and Nexus no problem.
Disconnected the Nexus and left the pilot aware running whilst I went out for a few hours. Tried to reconnect the wireless with both devices but it didn't show up.
Reformatted the card and copied the files over, fired up the Pi again but it stops at the same point. Picture attached.

[Admin]

just out of interest, have you connected an RJ45 to the Ethernet port, or did you have one connected during installation ?

[rasputin2068]

No it was completely stand alone.

[Admin]

I have never seen this hang on sshd, no idea what could cause that.
Just to confirm, this is Pi B+ ?

Does the hoot hang every time at the same point ?

Just zoomed in on display a little, i notice what looks like a hostapd error ?
This would possibly point to a WiFi dongle issue ?

Thx
Lee

[onkelmuetze]

I have the same two "fails" (....mount_unionfs... and ...checkroot-bootclean.sh...) on startup, but the device runs fine anyway.

[rasputin2068]

It looks like the Wi-Fi dongle has failed.
Fortunately I bought two at the same time, I have tried it with the second one and the boot now completes.
The first one had only been used for 5 hours maximum.

I have also sent a request for a licence code.

regards

Steve

[Admin]

I have the same two "fails" (....mount_unionfs... and ...checkroot-bootclean.sh...) on startup, but the device runs fine anyway.

These boot messages are irrelevant - but also annoying.
I have managed to cleanup the boot messsages in my internal build, except for one boot
message I cannot seem to resolve.

These have no effect on the operation of PilotAware, I have tried to put some debug messages into
the boot log, to indicate when the various interfaces are up and running.
I intend to add these to the webserver interface to indicate success/failure of the interfaces.

Of course if the WiFi fails, then there will be no webserver to indicate the failure!