¿ªÔÆÌåÓý

Date

 

Did you try "ssh pi@..." where the X's are the IP address of the pi?
On Aug 15, 2021, at 15:02, David AJ6RE <dc1@...> wrote:

Hi David,

I should have clarified that I am running the Pi headless, so I have an older Panasonic Toughbook laptop running Ubuntu hardwired via Ethernet to use as a keyboard/screen interface with the Rpi, on which I am just installing Hampi as the OS. I normally run SSH to get onto the Rpi, then enable VNC server to operate Hampi from the Toughbook.?

The HP laptop from which I flashed the original SD card is a separate Windows machine, but it worked fine that time, so I assume it has a good reader.?

Upon re-examining the second SD card on the Toughbook (Ubuntu) card reader I do indeed see the files you have listed above under the /boot directory. The files all seem to be there, including the SSH file. However, the Rpi still fails to connect via SSH.

The version of Hampi I was using was 1.0, and it appears that in subsequent releases SSH is already enabled. I think I will try flashing 2.0 and starting over. I am starting to suspect I just messed up the first card somehow. I do now see the readme instructions for creating a backup, so hopefully I won't repeat whatever mistake I may have made the first time around.?

Thanks again for you help.

73's?

David AJ6RE




?


Re: RealVNC loses connection

Mark Griffith
 

Carlos,

The first thing I would check is what is the signal strength from your Pi to the WiFi router.? You can do this with this simple command:

sudo iw wlan0 station dump | grep signal | awk '{print $2}'

This will print the dbm signal.? A -70 is the weakest you would want to go and have a reliable link.? -60 or better, with -20 being a super strong signal, would be good.

Another thing to check would be the number of WiFi failed data packets since the last reboot.

sudo iw wlan0 station dump | grep failed | awk '{print $3}'

A return of zero would of course be best.? If you have a lot of failed packets, there is something wrong.

The last thing to check would be the bit rate between the Pi and your WiFi router:

sudo iw wlan0 station dump | grep 'tx bitrate' | awk '{print $3}'

If you are using a 2.5GHz link, a rate of 61 would be the max.? Anything less would of course be less good.

These are values that are kept by the operating system, so they are the most accurate and relevant.

If you have a low signal, or low bit rate, it could be that at some point the link is just dropped for no apparent reason.? If so, then you'll need to move the Pi closer to the WiFi router, or get better antennas for the router, or look for interference on that frequency.? Microwave ovens and older cordless phones share the 2.5 GHz spectrum and have been in the past notorious for interference.

Hope this helps.

Mark
KD0QYN


On Sunday, August 15, 2021, 05:45:47 PM CDT, David Ranch <rpi4hamradio-groupsio@...> wrote:



Hello Carlos,

Since you're doing a connection from one internal host to another internal host, you are NOT going through your router or using it's port forward setting.
***Explain?? PC is ethernet and Pi is wireless, how is it not going thought the router?

Ah.. ok, I didn't remember hearing the Rpi was on wifi.? None the less, I bet the PC and the Rpi are still on the same LAN so while they are indeed using the router, they aren't going through any NAT / portforward functionality.?? My new suspect here is that your Rpi is periodically dropping it's Wifi connection.


This log entry is from your VNC Viewer and seems to indicate that the server isn't responding to keepalive packets.? Can you post some of the relevant logs from the VNC *Server* side of things?
***I am having trouble finding this file

-



Ping test.
***ping stopped when I lost connection running on cloud and on direct.

Right.. I bet you're loosing wifi connection on the Rpi side.? Do you have a HDMI monitor + USB keyboard connected on the Rpi?? If so, run a ping from the Rpi to the default gateway (aka your router) going.? See if that occasionally drops.? I bet it does.? If that's correct, you need to see what's going on here.? Here is a little script you can run on the Raspberry Pi to see what it think's it's Wifi signal strength is:

?/usr/local/bin/get-wifi-stats.sh
--
#!/bin/bash

# 05/25/21 - dranch - minor fixes
# 04/19/21 - dranch - original version

echo -en "\nWifi Signal strength: "
iw wlan0 station dump | grep signal | awk '{print $2}'?
echo -e "?? -70 dbm or less? : is a weak signal and the link will drop if it gets much weaker"
echo -e "?? -60 dbm to -50?? : is a good signal"
echo -e "?? -40 dbm or better: is a great signal"

echo -en "\nWifi RX speed: "
iw wlan0 station dump | grep 'rx bitrate' | awk '{print $3}'
echo -en "Wifi TX speed: "
iw wlan0 station dump | grep 'tx bitrate' | awk '{print $3}'
echo -en "Wifi session reconnects since last reboot (`uptime | awk '{print $3}'` days ago): "
iw wlan0 station dump | grep failed | awk '{print $3}'

echo " "
--


The output on one of my weakly connected Rpis is as follows:
--
Wifi Signal strength: -71
?? -70 dbm or less? : is a weak signal and the link will drop if it gets much weaker
?? -60 dbm to -50?? : is a good signal
?? -40 dbm or better: is a great signal

Wifi RX speed: 26.0
Wifi TX speed: 39.0
Wifi session reconnects since last reboot (35 days ago): 53
--

--David


Re: RealVNC loses connection

 

¿ªÔÆÌåÓý


Hello Carlos,

Since you're doing a connection from one internal host to another internal host, you are NOT going through your router or using it's port forward setting.
***Explain?? PC is ethernet and Pi is wireless, how is it not going thought the router?

Ah.. ok, I didn't remember hearing the Rpi was on wifi.? None the less, I bet the PC and the Rpi are still on the same LAN so while they are indeed using the router, they aren't going through any NAT / portforward functionality.?? My new suspect here is that your Rpi is periodically dropping it's Wifi connection.


This log entry is from your VNC Viewer and seems to indicate that the server isn't responding to keepalive packets.? Can you post some of the relevant logs from the VNC *Server* side of things?
***I am having trouble finding this file

-



Ping test.
***ping stopped when I lost connection running on cloud and on direct.

Right.. I bet you're loosing wifi connection on the Rpi side.? Do you have a HDMI monitor + USB keyboard connected on the Rpi?? If so, run a ping from the Rpi to the default gateway (aka your router) going.? See if that occasionally drops.? I bet it does.? If that's correct, you need to see what's going on here.? Here is a little script you can run on the Raspberry Pi to see what it think's it's Wifi signal strength is:

?/usr/local/bin/get-wifi-stats.sh
--
#!/bin/bash

# 05/25/21 - dranch - minor fixes
# 04/19/21 - dranch - original version

echo -en "\nWifi Signal strength: "
iw wlan0 station dump | grep signal | awk '{print $2}'?
echo -e "?? -70 dbm or less? : is a weak signal and the link will drop if it gets much weaker"
echo -e "?? -60 dbm to -50?? : is a good signal"
echo -e "?? -40 dbm or better: is a great signal"

echo -en "\nWifi RX speed: "
iw wlan0 station dump | grep 'rx bitrate' | awk '{print $3}'
echo -en "Wifi TX speed: "
iw wlan0 station dump | grep 'tx bitrate' | awk '{print $3}'
echo -en "Wifi session reconnects since last reboot (`uptime | awk '{print $3}'` days ago): "
iw wlan0 station dump | grep failed | awk '{print $3}'

echo " "
--


The output on one of my weakly connected Rpis is as follows:
--
Wifi Signal strength: -71
?? -70 dbm or less? : is a weak signal and the link will drop if it gets much weaker
?? -60 dbm to -50?? : is a good signal
?? -40 dbm or better: is a great signal

Wifi RX speed: 26.0
Wifi TX speed: 39.0
Wifi session reconnects since last reboot (35 days ago): 53
--

--David


Re: RealVNC loses connection

 

David thanks for your help.
Since you're doing a connection from one internal host to another internal host, you are NOT going through your router or using it's port forward setting.
***Explain?? PC is ethernet and Pi is wireless, how is it not going thought the router?

I assume that when you say "Viewer", you mean "RealVNC Viewer"?? I'm trying to be specific as there are probably more than a dozen different VNC clients out there for Linux.
***Correct RealVNC viewer.
***The only error file I found was the xsession log, see below.

This log entry is from your VNC Viewer and seems to indicate that the server isn't responding to keepalive packets.? Can you post some of the relevant logs from the VNC *Server* side of things?
***I am having trouble finding this file

Ping test.
***ping stopped when I lost connection running on cloud and on direct.

BTW 6m sprint was a dud, band was dead, with 4 antennas, 3 of them are stack sets not one contact.
***


Xsession: X session started for pi at Sun 15 Aug 2021 03:32:10 PM CDT
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/pi/.Xauthority
localuser:pi being added to access control list
dbus-update-activation-environment: setting USER=pi
dbus-update-activation-environment: setting LANGUAGE=en_US
dbus-update-activation-environment: setting TEXTDOMAIN=Linux-PAM
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting HOME=/home/pi
dbus-update-activation-environment: setting DESKTOP_SESSION=lightdm-xsession
dbus-update-activation-environment: setting XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting LOGNAME=pi
dbus-update-activation-environment: setting XDG_SESSION_CLASS=user
dbus-update-activation-environment: setting PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
dbus-update-activation-environment: setting XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting LANG=en_US
dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=lightdm-xsession
dbus-update-activation-environment: setting XAUTHORITY=/home/pi/.Xauthority
dbus-update-activation-environment: setting XDG_GREETER_DATA_DIR=/var/lib/lightdm/data/pi
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting GDMSESSION=lightdm-xsession
dbus-update-activation-environment: setting NO_AT_BRIDGE=1
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting LC_ALL=en_US
dbus-update-activation-environment: setting PWD=/home/pi
** Message: 15:32:12.154: main.vala:101: Session is LXDE-pi
** Message: 15:32:12.154: main.vala:102: DE is LXDE
** Message: 15:32:12.312: main.vala:133: log directory: /home/pi/.cache/lxsession/LXDE-pi
** Message: 15:32:12.312: main.vala:134: log path: /home/pi/.cache/lxsession/LXDE-pi/run.log


 

Hi David,

I should have clarified that I am running the Pi headless, so I have an older Panasonic Toughbook laptop running Ubuntu hardwired via Ethernet to use as a keyboard/screen interface with the Rpi, on which I am just installing Hampi as the OS. I normally run SSH to get onto the Rpi, then enable VNC server to operate Hampi from the Toughbook.?

The HP laptop from which I flashed the original SD card is a separate Windows machine, but it worked fine that time, so I assume it has a good reader.?

Upon re-examining the second SD card on the Toughbook (Ubuntu) card reader I do indeed see the files you have listed above under the /boot directory. The files all seem to be there, including the SSH file. However, the Rpi still fails to connect via SSH.

The version of Hampi I was using was 1.0, and it appears that in subsequent releases SSH is already enabled. I think I will try flashing 2.0 and starting over. I am starting to suspect I just messed up the first card somehow. I do now see the readme instructions for creating a backup, so hopefully I won't repeat whatever mistake I may have made the first time around.?

Thanks again for you help.

73's?

David AJ6RE




?


 

I have been booting debian environments from thumb drives for 15+ years, since "live" iso releases became a thing. Very handy for poking around the occasional windows box, etc. USB 3.O makes the current crop as fast as pretty much anything. 73


On Sun, Aug 15, 2021, 11:58 Marty Hartwell <mhartwe@...> wrote:

Ok, I know what those are, so you are booting off those instead of the micro SD drive, right?

I watched a video that talked about doing that, but am not sure I wanted to go that

route at this time. So am not at all familiar with the ins and outs of the use.


Marty kd8bk


On 8/15/21 11:45 AM, Dave R wrote:
aka thumb drive. The little SD cards are a pain on the pi400. Mine is velcro'd to the desk. The USB 3.0 flash drive plugs into a USB 3.0 hub. 73



On Sun, Aug 15, 2021, 09:07 Marty Hartwell <mhartwe@...> wrote:

Hi

Don't know what "USB Flash" is, I just go to the menu item to backup SD card, make

sure to have the backup disk in the adapter and let it go. I agree it isn't real fast but then

I am not usually in a real hurry or come back after awhile and it is finished.

I then have a good back up of the Micro SD card. I use the Ultra 64GB cards and

designate two cards for each Pi 4 4GB I have. I usually backup after each use and

then switch to even out activity.


Marty kd8bj


On 8/14/21 3:35 PM, Dave R wrote:
Does it work on USB Flash? That's what I'm using. 73

On Sat, Aug 14, 2021, 11:10 Marty Hartwell <mhartwe@...> wrote:

HI

Is there a reason to not use the built in SD backup tool? This works well for me.


Marty kd8bj


On 8/14/21 12:58 PM, Fred Hillhouse wrote:

I am not using Hampi but I recently made a backup ?of my image on my PiZ-W. I think I used instruction I found on Raspberry forum. I backed up to an USB drive then restored to a new uSD. I am currently using my back up so I know it works.

?

Fred N7FMH

?

From: [email protected] [mailto:[email protected]] On Behalf Of David AJ6RE
Sent: Friday, August 13, 2021 8:34 PM
To: [email protected]
Subject: [RaspberryPi-4-HamRadio] SD Cards Erased Upon Removal? #hampi #hardware #pi #raspberrypi #usability

?

After successfully using my Rpi 4 B+ for a few months as part of my homebrew mobile manpack rig I decided to back up the SD card prior to installing a GPS dongle. I did a sudo shutdown -h now and powered down. When I stuck the SD card it into my PC it was blank, save for the volume label.?

After failed attempts to recover the data, I flashed a new card, installed Hampi again, started reconfiguring Flrig etc., Then I decided to double-check the new card. I did the graceful shutdown before pulling the card out but evidently wiped that one as well at some point in the process. All files were gone but for a couple of text files and the volume label.

Subsequent online research indicates maybe I didn't let the pi shut down all the way before pulling the card. I did not know to wait for flashing lights after shutting down. However, I'm pretty sure I powered it down all the way after several seconds.?After spending hours flashing cards and looking forward to the prospect of going back to square one yet again and then reconfiguring the software again, and hoping it doesn't happen a third time, I am thinking the pi may just be too fragile a system to rely upon for emergency/mobile comms. It seems crazy that the SD card should be so vulnerable to erasure simply by being extracted from the Pi.?

At this point I am planning on just using the Toughbook that I was using as a keyboard/screen interface to host the software and cut out the Pi. It's a shame since I've invested countless hours in getting Hampi up and running.

Has anyone else had this experience?

David AJ6RE??




This email has been checked for viruses by Avast antivirus software.



 

¿ªÔÆÌåÓý

Ok, I know what those are, so you are booting off those instead of the micro SD drive, right?

I watched a video that talked about doing that, but am not sure I wanted to go that

route at this time. So am not at all familiar with the ins and outs of the use.


Marty kd8bk


On 8/15/21 11:45 AM, Dave R wrote:

aka thumb drive. The little SD cards are a pain on the pi400. Mine is velcro'd to the desk. The USB 3.0 flash drive plugs into a USB 3.0 hub. 73



On Sun, Aug 15, 2021, 09:07 Marty Hartwell <mhartwe@...> wrote:

Hi

Don't know what "USB Flash" is, I just go to the menu item to backup SD card, make

sure to have the backup disk in the adapter and let it go. I agree it isn't real fast but then

I am not usually in a real hurry or come back after awhile and it is finished.

I then have a good back up of the Micro SD card. I use the Ultra 64GB cards and

designate two cards for each Pi 4 4GB I have. I usually backup after each use and

then switch to even out activity.


Marty kd8bj


On 8/14/21 3:35 PM, Dave R wrote:
Does it work on USB Flash? That's what I'm using. 73

On Sat, Aug 14, 2021, 11:10 Marty Hartwell <mhartwe@...> wrote:

HI

Is there a reason to not use the built in SD backup tool? This works well for me.


Marty kd8bj


On 8/14/21 12:58 PM, Fred Hillhouse wrote:

I am not using Hampi but I recently made a backup ?of my image on my PiZ-W. I think I used instruction I found on Raspberry forum. I backed up to an USB drive then restored to a new uSD. I am currently using my back up so I know it works.

?

Fred N7FMH

?

From: [email protected] [mailto:[email protected]] On Behalf Of David AJ6RE
Sent: Friday, August 13, 2021 8:34 PM
To: [email protected]
Subject: [RaspberryPi-4-HamRadio] SD Cards Erased Upon Removal? #hampi #hardware #pi #raspberrypi #usability

?

After successfully using my Rpi 4 B+ for a few months as part of my homebrew mobile manpack rig I decided to back up the SD card prior to installing a GPS dongle. I did a sudo shutdown -h now and powered down. When I stuck the SD card it into my PC it was blank, save for the volume label.?

After failed attempts to recover the data, I flashed a new card, installed Hampi again, started reconfiguring Flrig etc., Then I decided to double-check the new card. I did the graceful shutdown before pulling the card out but evidently wiped that one as well at some point in the process. All files were gone but for a couple of text files and the volume label.

Subsequent online research indicates maybe I didn't let the pi shut down all the way before pulling the card. I did not know to wait for flashing lights after shutting down. However, I'm pretty sure I powered it down all the way after several seconds.?After spending hours flashing cards and looking forward to the prospect of going back to square one yet again and then reconfiguring the software again, and hoping it doesn't happen a third time, I am thinking the pi may just be too fragile a system to rely upon for emergency/mobile comms. It seems crazy that the SD card should be so vulnerable to erasure simply by being extracted from the Pi.?

At this point I am planning on just using the Toughbook that I was using as a keyboard/screen interface to host the software and cut out the Pi. It's a shame since I've invested countless hours in getting Hampi up and running.

Has anyone else had this experience?

David AJ6RE??




This email has been checked for viruses by Avast antivirus software.



 

¿ªÔÆÌåÓý


Hello David,


The SD card is a 32 GB SanDisk and the reader is built into the same laptop I used to flash the image. I used an SD adapter for Micro SD with it. After originally flashing the image I was able to see all the files and add the requisite SSH file to them. Later, after finding the card wiped, I tried putting it back in the Pi, which did not allow me SSH access, indicating the card was indeed wiped.

The whole issue of "finding the card wiped" is just bizzare to me.? It's not common so something else must be happening here assuming that once you shutdown the Rpi with a "sudo shutdown -h now", wait for the power LED to blink 10 times and then it should go OFF.? At that point, you should remove power from the Rpi and the card should be safe.?? If you've not seeing this LED blink behavior, you might have a power supply issue:

??


Next, it's worth mentioning that there seems to be a good number of fake SD cards out there.? Hopefully you're getting your cards from a reputable source but one way to confirm your cards are legitimate is to use the official SD Card formatter from the SD Association.? This is a Windows / MacOS program and is very easy to use:

??

Also, do remember that SD cards don't last forever and their life depends on their use.? Older versions of the Raspbian OS defaulted to writing a lot of log files to the SD card which would wear out the card.? Newer versions of the Raspberry Pi OS are much better here but if the cards you're using were previously used in say smartphones or other devices, they might be getting at the end of their useful life.


Next, how old is this laptop?? A 32GB SD card should work fine with an SD card reader that supports SDHC.? You probably WON'T find any labeling on your laptop that will show this so you'll have to research in the laptop's manual.? Even then, it might be hard to find.


You keep mentioning "ssh".? Do you not have an HDMI monitor connected to the Rpi to see what happens at boot time?? There is a specific sequence that you should see and depending on the state of the SD card, you can better understand what's happening (rainbow screen, multiple raspberry icons in the upper left, scrolling kernel text, etc).


The second card I tried was a 32 GB Lexar. It was wiped except for an empty folder called overlays and under the root were cmdline.txt, config.text and issue.txt and nothing else.

Was it just overlays or were there also other files in there?? Here is what a working /boot directory looks like:
--
rpi3:/boot $ ls -la
total 22393
drwxr-xr-x? 3 root root??? 3072 Dec 31? 1969 .
drwxr-xr-x 22 root root??? 4096 Oct 14? 2017 ..
-rwxr-xr-x? 1 root root?? 23946 Sep? 7? 2019 bcm2708-rpi-b.dtb
-rwxr-xr-x? 1 root root?? 24205 Sep? 7? 2019 bcm2708-rpi-b-plus.dtb
-rwxr-xr-x? 1 root root?? 23723 Sep? 7? 2019 bcm2708-rpi-cm.dtb
-rwxr-xr-x? 1 root root?? 23671 Sep? 7? 2019 bcm2708-rpi-zero.dtb
-rwxr-xr-x? 1 root root?? 24407 Sep? 7? 2019 bcm2708-rpi-zero-w.dtb
-rwxr-xr-x? 1 root root?? 25293 Sep? 7? 2019 bcm2709-rpi-2-b.dtb
-rwxr-xr-x? 1 root root?? 26463 Sep? 7? 2019 bcm2710-rpi-3-b.dtb
-rwxr-xr-x? 1 root root?? 27082 Sep? 7? 2019 bcm2710-rpi-3-b-plus.dtb
-rwxr-xr-x? 1 root root?? 25261 Sep? 7? 2019 bcm2710-rpi-cm3.dtb
-rwxr-xr-x? 1 root root?? 52296 Sep? 7? 2019 bootcode.bin
-rwxr-xr-x? 1 root root???? 147 Sep? 2? 2017 cmdline.txt
-rwxr-xr-x? 1 root root???? 119 Sep? 2? 2017 cmdline.txt.linpac-broken
-rwxr-xr-x? 1 root root???? 147 Sep? 2? 2017 cmdline.txt.linpac-works
-rwxr-xr-x? 1 root root??? 1663 Sep? 2? 2017 config-jessie.txt
-rwxr-xr-x? 1 root root??? 1688 Nov 22? 2017 config.txt
-rwxr-xr-x? 1 root root?????? 0 Sep? 2? 2017 config.txt-NOT-NATIVE-STRETCH-VER
-rwxr-xr-x? 1 root root?? 18693 Sep? 7? 2019 COPYING.linux
-rwxr-xr-x? 1 root root????? 41 Mar 17? 2018 .firmware_revision
-rwxr-xr-x? 1 root root??? 2644 Sep? 7? 2019 fixup_cd.dat
-rwxr-xr-x? 1 root root??? 6729 Sep? 7? 2019 fixup.dat
-rwxr-xr-x? 1 root root??? 9801 Sep? 7? 2019 fixup_db.dat
-rwxr-xr-x? 1 root root??? 9801 Sep? 7? 2019 fixup_x.dat
-rwxr-xr-x? 1 root root???? 145 Aug 15? 2017 issue.txt
-rwxr-xr-x? 1 root root 5310800 Sep? 7? 2019 kernel7.img
-rwxr-xr-x? 1 root root 5026968 Sep? 7? 2019 kernel.img
-rwxr-xr-x? 1 root root??? 1494 Sep? 7? 2019 LICENCE.broadcom
-rwxr-xr-x? 1 root root?? 18974 Aug 15? 2017 LICENSE.oracle
drwxr-xr-x? 2 root root?? 15360 Sep? 7? 2019 overlays
-rwxr-xr-x? 1 root root? 685572 Sep? 7? 2019 start_cd.elf
-rwxr-xr-x? 1 root root 4855080 Sep? 7? 2019 start_db.elf
-rwxr-xr-x? 1 root root 2878340 Sep? 7? 2019 start.elf
-rwxr-xr-x? 1 root root 3792520 Sep? 7? 2019 start_x.elf
--


Finally, you mentioned in another email that you're using Ubuntu.? While that should work, you might consider learning using the official Raspberry Pi OS image for now.? It has the best support possible for your Raspberry Pi hardware and is very stable, reliable, and tuned for low system resources.? Ubuntu on the other hand is usually VERY heavy weight (depends on the specific sub-version you use) and can run slower, leave less resources for enduser programs to run, etc.? Something to consider.

--David


 

aka thumb drive. The little SD cards are a pain on the pi400. Mine is velcro'd to the desk. The USB 3.0 flash drive plugs into a USB 3.0 hub. 73



On Sun, Aug 15, 2021, 09:07 Marty Hartwell <mhartwe@...> wrote:

Hi

Don't know what "USB Flash" is, I just go to the menu item to backup SD card, make

sure to have the backup disk in the adapter and let it go. I agree it isn't real fast but then

I am not usually in a real hurry or come back after awhile and it is finished.

I then have a good back up of the Micro SD card. I use the Ultra 64GB cards and

designate two cards for each Pi 4 4GB I have. I usually backup after each use and

then switch to even out activity.


Marty kd8bj


On 8/14/21 3:35 PM, Dave R wrote:
Does it work on USB Flash? That's what I'm using. 73

On Sat, Aug 14, 2021, 11:10 Marty Hartwell <mhartwe@...> wrote:

HI

Is there a reason to not use the built in SD backup tool? This works well for me.


Marty kd8bj


On 8/14/21 12:58 PM, Fred Hillhouse wrote:

I am not using Hampi but I recently made a backup ?of my image on my PiZ-W. I think I used instruction I found on Raspberry forum. I backed up to an USB drive then restored to a new uSD. I am currently using my back up so I know it works.

?

Fred N7FMH

?

From: [email protected] [mailto:[email protected]] On Behalf Of David AJ6RE
Sent: Friday, August 13, 2021 8:34 PM
To: [email protected]
Subject: [RaspberryPi-4-HamRadio] SD Cards Erased Upon Removal? #hampi #hardware #pi #raspberrypi #usability

?

After successfully using my Rpi 4 B+ for a few months as part of my homebrew mobile manpack rig I decided to back up the SD card prior to installing a GPS dongle. I did a sudo shutdown -h now and powered down. When I stuck the SD card it into my PC it was blank, save for the volume label.?

After failed attempts to recover the data, I flashed a new card, installed Hampi again, started reconfiguring Flrig etc., Then I decided to double-check the new card. I did the graceful shutdown before pulling the card out but evidently wiped that one as well at some point in the process. All files were gone but for a couple of text files and the volume label.

Subsequent online research indicates maybe I didn't let the pi shut down all the way before pulling the card. I did not know to wait for flashing lights after shutting down. However, I'm pretty sure I powered it down all the way after several seconds.?After spending hours flashing cards and looking forward to the prospect of going back to square one yet again and then reconfiguring the software again, and hoping it doesn't happen a third time, I am thinking the pi may just be too fragile a system to rely upon for emergency/mobile comms. It seems crazy that the SD card should be so vulnerable to erasure simply by being extracted from the Pi.?

At this point I am planning on just using the Toughbook that I was using as a keyboard/screen interface to host the software and cut out the Pi. It's a shame since I've invested countless hours in getting Hampi up and running.

Has anyone else had this experience?

David AJ6RE??




This email has been checked for viruses by Avast antivirus software.



 

¿ªÔÆÌåÓý

Hi

In the Pi menu selection it is I think under Preferences, or Utilities, and is a standard item for

creating a backup. It isn't real fast but it does work.

Marty kd8bj


On 8/14/21 10:14 PM, David AJ6RE wrote:

Hi Marty, no, I didn't know there was one.?


 

¿ªÔÆÌåÓý

Hi

Don't know what "USB Flash" is, I just go to the menu item to backup SD card, make

sure to have the backup disk in the adapter and let it go. I agree it isn't real fast but then

I am not usually in a real hurry or come back after awhile and it is finished.

I then have a good back up of the Micro SD card. I use the Ultra 64GB cards and

designate two cards for each Pi 4 4GB I have. I usually backup after each use and

then switch to even out activity.


Marty kd8bj


On 8/14/21 3:35 PM, Dave R wrote:

Does it work on USB Flash? That's what I'm using. 73

On Sat, Aug 14, 2021, 11:10 Marty Hartwell <mhartwe@...> wrote:

HI

Is there a reason to not use the built in SD backup tool? This works well for me.


Marty kd8bj


On 8/14/21 12:58 PM, Fred Hillhouse wrote:

I am not using Hampi but I recently made a backup ?of my image on my PiZ-W. I think I used instruction I found on Raspberry forum. I backed up to an USB drive then restored to a new uSD. I am currently using my back up so I know it works.

?

Fred N7FMH

?

From: [email protected] [mailto:[email protected]] On Behalf Of David AJ6RE
Sent: Friday, August 13, 2021 8:34 PM
To: [email protected]
Subject: [RaspberryPi-4-HamRadio] SD Cards Erased Upon Removal? #hampi #hardware #pi #raspberrypi #usability

?

After successfully using my Rpi 4 B+ for a few months as part of my homebrew mobile manpack rig I decided to back up the SD card prior to installing a GPS dongle. I did a sudo shutdown -h now and powered down. When I stuck the SD card it into my PC it was blank, save for the volume label.?

After failed attempts to recover the data, I flashed a new card, installed Hampi again, started reconfiguring Flrig etc., Then I decided to double-check the new card. I did the graceful shutdown before pulling the card out but evidently wiped that one as well at some point in the process. All files were gone but for a couple of text files and the volume label.

Subsequent online research indicates maybe I didn't let the pi shut down all the way before pulling the card. I did not know to wait for flashing lights after shutting down. However, I'm pretty sure I powered it down all the way after several seconds.?After spending hours flashing cards and looking forward to the prospect of going back to square one yet again and then reconfiguring the software again, and hoping it doesn't happen a third time, I am thinking the pi may just be too fragile a system to rely upon for emergency/mobile comms. It seems crazy that the SD card should be so vulnerable to erasure simply by being extracted from the Pi.?

At this point I am planning on just using the Toughbook that I was using as a keyboard/screen interface to host the software and cut out the Pi. It's a shame since I've invested countless hours in getting Hampi up and running.

Has anyone else had this experience?

David AJ6RE??




This email has been checked for viruses by Avast antivirus software.



 

Hi James, I did try putting the card back in the Pi, and could not connect via SSH. I have not reformatted the same card--I used a different one.?

Based on your suggestion (and others here) I have checked the original card on a Linux machine (Ubuntu) and did find that in addition to the volume label were two other files I could not see from the Windows machine:?

IndexerVolumeGuid

WPSettings.dat

I have just begun learning Linux and will stick with it. There are many things to like about it. It did not occur to me that the Pi might contain its own backup utility however.

To you and everyone else who responded, thanks very much for your suggestions. I appreciate your feedback.

73's,

David AJ6RE






 

Dave, thanks for sharing your experience. I will re-examine the cards on a Linux system and see if there is anything there. However the Pi would not take my SSH so I am not optimistic.

I did read on another forum that some users were having SD cards getting repeatedly "burned up" by their Pi's, but others (like you, having lots of experience with multiple units running all the time), were incredulous. I am new at this so it is completely within the realm of possibility that this is a matter of operator error. This was indeed flashed from a Windows machine, but originally I was able to see the files on that machine, so unless the Pi reformatted the card I don't see why it would now be unreadable on the same machine.


 

David, thank you for the very helpful information. The SD card is a 32 GB SanDisk and the reader is built into the same laptop I used to flash the image. I used an SD adapter for Micro SD with it. After originally flashing the image I was able to see all the files and add the requisite SSH file to them. Later, after finding the card wiped, I tried putting it back in the Pi, which did not allow me SSH access, indicating the card was indeed wiped. The second card I tried was a 32 GB Lexar. It was wiped except for an empty folder called overlays and under the root were cmdline.txt, config.text and issue.txt and nothing else.


 

Fred, thanks for the suggestion. I didn't think to look for backup instructions for the Pi, since I didn't even know it had that capability.?


 

Hi Marty, no, I didn't know there was one.?


 

Hi Dave, no I might try that next instead, Thanks for the suggestion.


Re: RealVNC loses connection

 

¿ªÔÆÌåÓý


Hello Carlos,


Pi and client are sitting next to each other, router is 7ft away, PC is ethernet connected.? I have the Pi as? 192.168.1.10 on port 5900.? I have real VNC setup for both cloud and direct connection.?
I went into the router and Nat Filtering was set to secure, changed to open.? I believe this is what you are referring to.

Since you're doing a connection from one internal host to another internal host, you are NOT going through your router or using it's port forward setting.


Which VNC?? I am using RealVNC server on the Pi and Viewer on the desktop PC.
Changed KeepAliveInterval from 30 to 15 and KeepAliveResponse from 30 to 60 on the viewer.
***Disconnected within 5mts.***

I assume that when you say "Viewer", you mean "RealVNC Viewer"?? I'm trying to be specific as there are probably more than a dozen different VNC clients out there for Linux.


<13> 2021-08-14T20:02:14.199Z carlosmint vncviewer[6553]: Child: 6562: CConnection: close: [NoKeepAliveResponse] Timed out waiting for response to "keep alive" message

This log entry is from your VNC Viewer and seems to indicate that the server isn't responding to keepalive packets.? Can you post some of the relevant logs from the VNC *Server* side of things?


One other thing you might do is on the client machine, open another terminal window and PING the VNC server IP of 192.168.1.10 and when the VNC session seems to drop, do you also see your pings stop responding?


--David
KI6ZHD


Re: RealVNC loses connection

 

David, thanks for the reply.
I was at extreme frustration point when I posted and just sorta puked out HELP.
Pi OS is the default Raspbian, 8G.? Internet speed is 250 synched.? PC is Mint 19 Tara, CPU AMD A4-5300 APU with Radeon

Pi and client are sitting next to each other, router is 7ft away, PC is ethernet connected..? I have the Pi as? 192.168.1.10 on port 5900.? I have real VNC setup for both cloud and direct connection.?
I went into the router and Nat Filtering was set to secure, changed to open.? I believe this is what you are referring to.
Which VNC?? I am using RealVNC server on the Pi and Viewer on the desktop PC.
Changed KeepAliveInterval from 30 to 15 and KeepAliveResponse from 30 to 60 on the viewer.
***Disconnected within 5mts.***
VNC Log?? See the end of the reply for last 50 to 70 entries.

?Time to head out to the contest station for the 50m sprint.
Thanks
Carlos
08-14T19:59:09.743Z carlosmint vncviewer[6553]: Child: 6562: CSession: connection error: Hosted Connection-Broker error: Timed out waiting for target principal
<13> 2021-08-14T19:59:09.743Z carlosmint vncviewer[6553]: Child: 6562: CConnection: close: [Hosted] VNC Server is not currently listening for Cloud connections.
<14> 2021-08-14T19:59:13.748Z carlosmint vncviewer[6553]: Child: 6562: CModuleReconnector: Attempting reconnect...
<13> 2021-08-14T19:59:13.748Z carlosmint vncviewer[6553]: Child: 6562: CSession: Connecting to tqvU1p-nKpcX-hScywy (Hosted)
<14> 2021-08-14T19:59:13.748Z carlosmint vncviewer[6553]: Child: 6562: ServerIdConnector: Using cached Viewer credentials bKHDFy-mfiwR-JMrcw1
<13> 2021-08-14T19:59:14.120Z carlosmint vncviewer[6553]: Child: 6562: CSession: Beginning RFB connection to raspberrypi
<14> 2021-08-14T19:59:14.120Z carlosmint vncviewer[6553]: Child: 6562: CSession: Encryption set to 'Server'
<14> 2021-08-14T19:59:14.179Z carlosmint vncviewer[6553]: Child: 6562: CConnection: Server supports RFB protocol version 5.0
<14> 2021-08-14T19:59:14.179Z carlosmint vncviewer[6553]: Child: 6562: CConnection: Using RFB protocol version 5.0
<14> 2021-08-14T19:59:14.203Z carlosmint vncviewer[6553]: Child: 6562: CProtoPostV4: Server selected cipher suite RA4-PSK_128 [0x0602] (algorithms: RSA-OAEP, ECDHE-Curve25519, PSK, SHA-256, AES-GCM-128)
<14> 2021-08-14T19:59:14.253Z carlosmint vncviewer[6553]: Child: 6562: CProtoPostV4: Server offered authentication method UserPasswd(1) [required=1]
<13> 2021-08-14T19:59:14.253Z carlosmint vncviewer[6553]: Child: 6562: CProtoPostV4: Choosing authentication method UserPasswd(1)
<14> 2021-08-14T19:59:14.311Z carlosmint vncviewer[6553]: Child: 6562: CProtoPostV4: Server offered empty authentication list (auth completed)
<13> 2021-08-14T19:59:14.311Z carlosmint vncviewer[6553]: Child: 6562: CConnection: Authentication successful
<14> 2021-08-14T19:59:14.347Z carlosmint vncviewer[6553]: Child: 6562: CConnection: Peer user agent vncserver-x11/6.7.4 (LXDE; Raspbian GNU/Linux 10; Linux 5.10.17; armv7l; en_US)
<14> 2021-08-14T19:59:14.412Z carlosmint vncviewer[6553]: Child: 6562: FTMsgWriter: Advertised share 3888316702, flags 0x80
<14> 2021-08-14T19:59:14.412Z carlosmint vncviewer[6553]: Child: 6562: QualSelector: Server pixel format depth 24 (32 bpp) little-endian rgb888
<14> 2021-08-14T19:59:14.412Z carlosmint vncviewer[6553]: Child: 6562: QualSelector: Requesting ZRLE2 encoding (line speed 0 kbit/s)
<14> 2021-08-14T19:59:14.412Z carlosmint vncviewer[6553]: Child: 6562: QualSelector: Using pixel format depth 6 (8 bpp) rgb222
<14> 2021-08-14T19:59:14.412Z carlosmint vncviewer[6553]: Child: 6562: QualSelector: requesting initial update
<14> 2021-08-14T19:59:14.417Z carlosmint vncviewer[6553]: Child: 6562: ftExtension: directory '' of share 3888316702 requested to depth 0
<14> 2021-08-14T19:59:14.417Z carlosmint vncviewer[6553]: Child: 6562: FTMsgWriter: Sent 1 filename(s), marshalled=85
<14> 2021-08-14T19:59:14.417Z carlosmint vncviewer[6553]: Child: 6562: FTMsgWriter: Sent EOF share 3888316702
<14> 2021-08-14T19:59:14.503Z carlosmint vncviewer[6553]: Child: 6562: QualSelector: Requesting JRLE encoding (line speed 2864 kbit/s)
<14> 2021-08-14T19:59:14.503Z carlosmint vncviewer[6553]: Child: 6562: ftExtension: 0-123 of Stylus-Photo-R200 via VNC from carlosmint requested (compressed)
<14> 2021-08-14T19:59:14.510Z carlosmint vncviewer[6553]: Child: 6562: QualSelector: Requesting full color (line speed 2864 kbit/s)
<14> 2021-08-14T19:59:14.510Z carlosmint vncviewer[6553]: Child: 6562: QualSelector: Using pixel format depth 24 (32 bpp) little-endian rgb888
<13> 2021-08-14T20:02:14.199Z carlosmint vncviewer[6553]: Child: 6562: CConnection: close: [NoKeepAliveResponse] Timed out waiting for response to "keep alive" message
<14> 2021-08-14T20:02:21.260Z carlosmint vncviewer[6553]: Child: 6562: CModuleReconnector: Attempting reconnect...
<13> 2021-08-14T20:02:21.260Z carlosmint vncviewer[6553]: Child: 6562: CSession: Connecting to tqvU1p-nKpcX-hScywy (Hosted)
<14> 2021-08-14T20:02:21.261Z carlosmint vncviewer[6553]: Child: 6562: ServerIdConnector: Using cached Viewer credentials bKHDFy-mfiwR-JMrcw1
<13> 2021-08-14T20:02:21.886Z carlosmint vncviewer[6553]: Child: 6562: CSession: Beginning RFB connection to raspberrypi
<14> 2021-08-14T20:02:21.886Z carlosmint vncviewer[6553]: Child: 6562: CSession: Encryption set to 'Server'
<14> 2021-08-14T20:02:21.968Z carlosmint vncviewer[6553]: Child: 6562: CConnection: Server supports RFB protocol version 5.0
<14> 2021-08-14T20:02:21.968Z carlosmint vncviewer[6553]: Child: 6562: CConnection: Using RFB protocol version 5.0
<14> 2021-08-14T20:02:21.990Z carlosmint vncviewer[6553]: Child: 6562: CProtoPostV4: Server selected cipher suite RA4-PSK_128 [0x0602] (algorithms: RSA-OAEP, ECDHE-Curve25519, PSK, SHA-256, AES-GCM-128)
<14> 2021-08-14T20:02:22.074Z carlosmint vncviewer[6553]: Child: 6562: CProtoPostV4: Server offered authentication method UserPasswd(1) [required=1]
<13> 2021-08-14T20:02:22.074Z carlosmint vncviewer[6553]: Child: 6562: CProtoPostV4: Choosing authentication method UserPasswd(1)
<14> 2021-08-14T20:02:22.137Z carlosmint vncviewer[6553]: Child: 6562: CProtoPostV4: Server offered empty authentication list (auth completed)
<13> 2021-08-14T20:02:22.137Z carlosmint vncviewer[6553]: Child: 6562: CConnection: Authentication successful
<14> 2021-08-14T20:02:22.175Z carlosmint vncviewer[6553]: Child: 6562: CConnection: Peer user agent vncserver-x11/6.7.4 (LXDE; Raspbian GNU/Linux 10; Linux 5.10.17; armv7l; en_US)
<14> 2021-08-14T20:02:22.448Z carlosmint vncviewer[6553]: Child: 6562: FTMsgWriter: Advertised share 3888316703, flags 0x80
<14> 2021-08-14T20:02:22.448Z carlosmint vncviewer[6553]: Child: 6562: QualSelector: Server pixel format depth 24 (32 bpp) little-endian rgb888
<14> 2021-08-14T20:02:22.448Z carlosmint vncviewer[6553]: Child: 6562: QualSelector: Requesting ZRLE2 encoding (line speed 0 kbit/s)
<14> 2021-08-14T20:02:22.448Z carlosmint vncviewer[6553]: Child: 6562: QualSelector: Using pixel format depth 6 (8 bpp) rgb222
<14> 2021-08-14T20:02:22.448Z carlosmint vncviewer[6553]: Child: 6562: QualSelector: requesting initial update
<14> 2021-08-14T20:02:22.450Z carlosmint vncviewer[6553]: Child: 6562: ftExtension: directory '' of share 3888316703 requested to depth 0
<14> 2021-08-14T20:02:22.450Z carlosmint vncviewer[6553]: Child: 6562: FTMsgWriter: Sent 1 filename(s), marshalled=85
<14> 2021-08-14T20:02:22.450Z carlosmint vncviewer[6553]: Child: 6562: FTMsgWriter: Sent EOF share 3888316703
<14> 2021-08-14T20:02:22.541Z carlosmint vncviewer[6553]: Child: 6562: QualSelector: Requesting JRLE encoding (line speed 10024 kbit/s)
<14> 2021-08-14T20:02:22.541Z carlosmint vncviewer[6553]: Child: 6562: ftExtension: 0-123 of Stylus-Photo-R200 via VNC from carlosmint requested (compressed)
<14> 2021-08-14T20:02:22.550Z carlosmint vncviewer[6553]: Child: 6562: QualSelector: Requesting full color (line speed 10024 kbit/s)
<14> 2021-08-14T20:02:22.550Z carlosmint vncviewer[6553]: Child: 6562: QualSelector: Using pixel format depth 24 (32 bpp) little-endian rgb888
<13> 2021-08-14T20:02:28.442Z carlosmint vncviewer[6553]: Child: 8357: CConnection: close: [NoKeepAliveResponse] Timed out waiting for response to "keep alive" message
<14> 2021-08-14T20:02:29.449Z carlosmint vncviewer[6553]: Child: 8357: CModuleReconnector: Attempting reconnect...
<13> 2021-08-14T20:02:29.449Z carlosmint vncviewer[6553]: Child: 8357: CSession: Connecting to 192.168.1.10:5900 (Chooser for Direct UDP/Direct TCP via proxy settings)
<13> 2021-08-14T20:04:14.393Z carlosmint vncviewer[6553]: Child: 8357: CConnection: close: [ViewerClosed] VNC Viewer closed
<13> 2021-08-14T20:04:14.407Z carlosmint vncviewer[6553]: Child: 6562: CConnection: close: [ViewerClosed] VNC Viewer closed
<13> 2021-08-14T20:04:20.437Z carlosmint vncviewer[6553]: AbApp: stopped


 

Does it work on USB Flash? That's what I'm using. 73


On Sat, Aug 14, 2021, 11:10 Marty Hartwell <mhartwe@...> wrote:

HI

Is there a reason to not use the built in SD backup tool? This works well for me.


Marty kd8bj


On 8/14/21 12:58 PM, Fred Hillhouse wrote:

I am not using Hampi but I recently made a backup ?of my image on my PiZ-W. I think I used instruction I found on Raspberry forum. I backed up to an USB drive then restored to a new uSD. I am currently using my back up so I know it works.

?

Fred N7FMH

?

From: [email protected] [mailto:[email protected]] On Behalf Of David AJ6RE
Sent: Friday, August 13, 2021 8:34 PM
To: [email protected]
Subject: [RaspberryPi-4-HamRadio] SD Cards Erased Upon Removal? #hampi #hardware #pi #raspberrypi #usability

?

After successfully using my Rpi 4 B+ for a few months as part of my homebrew mobile manpack rig I decided to back up the SD card prior to installing a GPS dongle. I did a sudo shutdown -h now and powered down. When I stuck the SD card it into my PC it was blank, save for the volume label.?

After failed attempts to recover the data, I flashed a new card, installed Hampi again, started reconfiguring Flrig etc., Then I decided to double-check the new card. I did the graceful shutdown before pulling the card out but evidently wiped that one as well at some point in the process. All files were gone but for a couple of text files and the volume label.

Subsequent online research indicates maybe I didn't let the pi shut down all the way before pulling the card. I did not know to wait for flashing lights after shutting down. However, I'm pretty sure I powered it down all the way after several seconds.?After spending hours flashing cards and looking forward to the prospect of going back to square one yet again and then reconfiguring the software again, and hoping it doesn't happen a third time, I am thinking the pi may just be too fragile a system to rely upon for emergency/mobile comms. It seems crazy that the SD card should be so vulnerable to erasure simply by being extracted from the Pi.?

At this point I am planning on just using the Toughbook that I was using as a keyboard/screen interface to host the software and cut out the Pi. It's a shame since I've invested countless hours in getting Hampi up and running.

Has anyone else had this experience?

David AJ6RE??




This email has been checked for viruses by Avast antivirus software.