forum.pistar.uk

I have a 16GB SD card on my Dual slot mmdvm running 3.4.13
I am getting no space errors while trying to do the pistar-update command:
Any advice on what I should do?

pi-star@pi-star(rw):~$ sudo bash
root@pi-star(rw):pi-star# rpi-rw
root@pi-star(rw):pi-star# pistar-update
Updating OS...

Get:1 http://httpredir.debian.org jessie-backports InRelease [166 kB]
Ign http://httpredir.debian.org jessie-backports InRelease
Ign http://httpredir.debian.org jessie-backports Release.gpg
Get:2 http://mirrordirector.raspbian.org jessie InRelease [14.9 kB]
Ign http://mirrordirector.raspbian.org jessie InRelease
Get:3 http://mirrordirector.raspbian.org jessie Release.gpg [473 B]
Err http://mirrordirector.raspbian.org jessie Release.gpg
Error writing to the file - write (28: No space left on device)
...
Get:21 http://mirrordirector.raspbian.org jessie/non-free armhf Packages [84.2 kB]
Err http://mirrordirector.raspbian.org jessie/non-free armhf Packages
Error writing to output file - write (28: No space left on device)

That's strange because Pi-Star should normally have all the space it needs on a 4 GB card, but you could try expanding the root partition: Good luck!

Yep the sudo pistar-expand was the solution!
This was strange as we have several of these and this is the first time I have had this happen...
Thank you very much!
Bill

This post just saved my butt. TTT it goes!

On the newer releases of Pi-Star, it automatically expands the filesystem to fill the capacity of the card at build time.
That saves the need for running the command that Toshen supplied for the older versions.

N7HHI wrote: ↑Wed Jan 27, 2021 1:57 pm On the newer releases of Pi-Star, it automatically expands the filesystem to fill the capacity of the card at build time.
That saves the need for running the command that Toshen supplied for the older versions.

Exactly so, but that came in 4.0 ish...

W0GEN wrote: ↑Wed Jun 20, 2018 10:45 pm I have a 16GB SD card on my Dual slot mmdvm running 3.4.13

Its the older image running here, thats why it was not auto-expanded.

Very odd.... I am running 4.1.2 but the dashboard links to QRZ went to somewhere else unhelpful ...

I looked around the forum and it seems some updates now run automatically while the hotspot is running, if I've read that right, so I tried to see if I could do a

Sudo Apt-get update
Sudo Apt-Get Upgrade...

The update works but the Upgrade fails and suggested I need to run apt --fix-broken install

The issue seems to be raspberrypi-bootloader and it is wittering about it being (=1.20210108-1) but has (1.2021022-1 is installed)

I tried fixing that but got garbage about not enough room on card (16GB) so I'm not convinced the 'expand' has run on setting up the card initially with v4.1.2..

Suffice to say the Pi will no longer update and I can't get it to address the lack of space short of wiping the SD card and reflashing it... even that may not works because to me it looks as if the auto-updates are getting things screwed up.

OK. I finally got the pistar updated to 4.1.3 and found the other thread on RadioID vs QRZ with proposed changes.

SO the hotspot is running again, but not how I want it. The links to the Pi-star-local for the 'Callsign' look up edit changes didn't work and after browsing all the config pages I can't find it.

looked at the underlying .php files to edit those direct where they were once rem'd out but clearly they have changed to with no update info on the forum to make sense of them anymore.

SO I'm still stuck with a corrupt RadioID database... not a good move guys even if it was intended to help the RadioID site.

Given up again.

G0KDT wrote: ↑Mon Feb 01, 2021 3:57 pm
I looked around the forum and it seems some updates now run automatically while the hotspot is running, if I've read that right, so I tried to see if I could do a

Sudo Apt-get update
Sudo Apt-Get Upgrade...

The proper commands for update and upgrade in the ssh connection are:
sudo pistar-update
sudo pistar-upgrade

G0KDT wrote: ↑Mon Feb 01, 2021 5:35 pm OK. I finally got the pistar updated to 4.1.3 and found the other thread on RadioID vs QRZ with proposed changes.

SO the hotspot is running again, but not how I want it. The links to the Pi-star-local for the 'Callsign' look up edit changes didn't work and after browsing all the config pages I can't find it.

looked at the underlying .php files to edit those direct where they were once rem'd out but clearly they have changed to with no update info on the forum to make sense of them anymore.

SO I'm still stuck with a corrupt RadioID database... not a good move guys even if it was intended to help the RadioID site.

Given up again.

Look at the following post for the instructions on how to fix the RadioID.net vs. QRZ.com issue:
viewtopic.php?p=16596#p16596

The PopupWidth and PopupHeight boxes have been removed, so you will only see the "Service" box under the Lookup heading.