Sd card issue

FlightAware ADS-B Flight Tracking
1

I.m trying to setup PiAware 3.7.2, Wrote the image to the card using etcher but when I try to see it on my windows 10 pc, it says the file system is not recognized so I cannot edit the config file to setup wifi. What am I doing wrong?
Thanks in advance

2

Remove the sd-card and plug it in again.

3

Tried that and still not working

4

Maybe you wrote the image to another drive? (would not be good for those data)

Otherwise try again or try another sd-card.

Note that the sd-card will have two partitions, only the first one is accesible by Windows.
(it should just ignore the 2nd one)

5

I put the card in the pi and it work, I can do sudo nano /boot/piaware-config.txt and edit the file. I cannot get wifi to work tho.

6

The piaware-config.txt is only read on boot.

So set the correct values and do a reboot (sudo reboot).
Also be sure to save the file with Ctrl-O and Enter.

I believe there are some pitfalls with spaces and # in wifi names or passwords.

7

got it to work, had to add " wireless-type dhcp " to get it to work, now to find how to enable ssh as the pi will not be connected to a monitor when I get it in his final spot

8

https://flightaware.com/adsb/piaware/build/optional#wifi

9

This is already the default setting.

10

Enabling SSH is easy. Just type:- sudo raspi-config and go to interfacing options and you will see enable SSH

11

You need a monitor and a keyboard connected to Pi for that.
Writing an empty file named “ssh” in the boot folder, visible with a PC and card reader, is much easier.

12

Compounding on this solution to enable SSH, one may copy the raspbian image to a usb stick or hard drive of their choice (formatted fat32) and perform the following on any currently working linux system after plugging the drive in:

sudo mkdir /tmp/img
sudo mount /dev/sda1 /tmp/img
IMG="/tmp/img/`sudo ls /tmp/img |grep .img`"
SS=`sudo fdisk -l $IMG |grep "^Sector size" |awk '{print $4}'`
P1=`sudo fdisk -l $IMG |grep "^$IMG"1 |awk '{print $2}'`
P2=`sudo fdisk -l $IMG |grep "^$IMG"2 |awk '{print $2}'`
sudo mkdir /tmp/usb1 /tmp/usb2
sudo mount -v -o rw,offset=$((P1*=$SS)) -t vfat $IMG /tmp/usb1
sudo mount -v -o rw,offset=$((P2*=$SS)) -t ext4 $IMG /tmp/usb2

sudo touch /tmp/usb1/ssh

sudo sync
sudo umount /tmp/usb1
sudo umount /tmp/usb2
sudo umount /tmp/img

The above is if your usb stick/drive containing the image shows up as sda1 - adjust accordingly if needed as this assumes only one device being connected and the target image is the only .img file in the rot folder of the drive.

From there, whenever the “injected” image is burned, ssh will be enabled on the first boot by default. It’s the same as performing whatever @SoNic67 mentioned, but it will be there on any subsequently burned sd card. I use this method since I am constantly burning images to cards and it eliminates me having to pull/push the sdcard after burning and manually adding the ssh file to the boot partition.

13

kpartx is a much simpler way to achieve the same thing.

14

Yup, a few ways to skin a cat:

#USE KPARTX
sudo apt install -y kpartx

mkdir img
sudo mount /dev/sda1 img
sudo kpartx -av img/*.img
sudo mount /dev/mapper/loop0p1 /mnt
sudo touch /mnt/ssh
sudo kpartx -d img/*.img
sudo umount -l /mnt img
sudo sync
rm -rf img

*OR*

#USE LOSETUP
mkdir img
sudo mount /dev/sda1 img
sudo losetup -P /dev/loop0 img/*.img
sudo mount /dev/loop0p1 /mnt
sudo touch /mnt/ssh
sudo losetup -d /dev/loop0
sudo umount -l /mnt img
sudo sync
rm -rf img
15

@SoNic67 is right.
Slip-out micoSD card from RPi, slip-in into Desktop/Laptop using a card reader, and do following:

16

The Raspbian’s raspi-config command uses fdisk to expand file system. Below are the commands generated when I did following:

sudo raspi-onfig >> Advance Options >> Expand File system

pi@raspberrypi:~ $ sudo raspi-config

Welcome to fdisk (util-linux 2.33.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): Disk /dev/mmcblk0: 7.4 GiB, 7948206080 bytes, 15523840 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6c586e13

Device         Boot  Start      End  Sectors  Size Id Type
/dev/mmcblk0p1        8192   532479   524288  256M  c W95 FAT32 (LBA)
/dev/mmcblk0p2      532480 15523839 14991360  7.2G 83 Linux

Command (m for help): Partition number (1,2, default 2):
Partition 2 has been deleted.

Command (m for help): Partition type
   p   primary (1 primary, 0 extended, 3 free)
   e   extended (container for logical partitions)
Select (default p): Partition number (2-4, default 2): First sector (2048-15523839, default 2048): Last sector, +/-sectors or +/-size{K,M,G,T,P} (532480-15523839, default 15523839):
Created a new partition 2 of type 'Linux' and of size 7.2 GiB.
Partition #2 contains a ext4 signature.

Command (m for help):
Disk /dev/mmcblk0: 7.4 GiB, 7948206080 bytes, 15523840 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6c586e13

Device         Boot  Start      End  Sectors  Size Id Type
/dev/mmcblk0p1        8192   532479   524288  256M  c W95 FAT32 (LBA)
/dev/mmcblk0p2      532480 15523839 14991360  7.2G 83 Linux

Command (m for help): The partition table has been altered.
Syncing disks.