[PirateBox Raspberry Pi DIY] post installation problem

I'm having a few problems setting up a Raspberry Pi3 as a Piratebox, folowing the instructions in "[piratebox.cc];.
The main installation, when the Pi was connected via ethernet went without problems, and on the conclusion, when the ethernet connection was removed and the Pi re-booted, the Piratebox was evident on my mobile phone Wifi analyser, coming through loud and clear.The Andoid phone would also connect and login. Unfotunately my main PC, running Mageia Linux is ethernet only, so could not be used for subsequent Post Installation work. So, I moved to a laptop, dual boot for Magia 6 and Windows 7. Here was the first snag, the Mageia Network Centre, whilst having the Piratebox as a connectable Wifi would not connect, coming back with a "Connection Failed" message.This, no doubt since the ipaddress of the machine is manually set to a different sub domain. Booting into Windows, I was able to connect. I installed Putty, as instructed, and SSH'd into the Pi. No problem.
On executing the first command, "sudo /opt/pitatebox/rpi/bin/sdcard_share.sh". The machine asked for the user password, which was given. However, at this point the machine returned "ERROR: SWAP already exists". Is this a significant error or just a response on being asked to create something that already exists?

Hi,
this means that the partition no. 3 was already created (or is a leftover).

Just to double check the configuration state, please post the output of the following commands:

ls -1 /dev/mmc*
mount
cat /etc/fstab

best regards Matthias

Mathias, sorry for the delay in replying. I did complete the Post Installation setup, and there don't appear to be any problems. As you say, the problem might have bee an existing item. This machine does not have wifi ability, so I've had to use another, which seems to be having problems with logging into the forum. However, I've finally copied over the information you asked for I'm not conversant with the code system on this forum, but here goes!

[alarm@alarmpi ~]$ ls -l /dev/mmc*
brw-rw---- 1 root disk 179, 0 Feb 24 01:32 /dev/mmcblk0
brw-rw---- 1 root disk 179, 1 Feb 24 01:32 /dev/mmcblk0p1
brw-rw---- 1 root disk 179, 2 Feb 24 01:32 /dev/mmcblk0p2
brw-rw---- 1 root disk 179, 3 Feb 24 01:32 /dev/mmcblk0p3
brw-rw---- 1 root disk 179, 4 Feb 24 01:32 /dev/mmcblk0p4
[alarm@alarmpi ~]$ mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=470288k,nr_inodes=117572,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
/dev/mmcblk0p2 on / type ext4 (rw,relatime,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=37,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=12319)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
tmpfs on /var/log type tmpfs (rw,nosuid,noatime,size=102400k,mode=755)
tmpfs on /var/tmp type tmpfs (rw,nosuid,nodev,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,noatime,size=102400k,mode=755)
/dev/mmcblk0p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)
/dev/mmcblk0p4 on /mnt/sdshare type ext4 (rw,noatime,nodiratime,data=writeback)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=95836k,mode=700,uid=1000,gid=1000)
[alarm@alarmpi ~]$ cat /etc/fstab
/dev/mmcblk0p1 /boot vfat defaults,nofail 0 0
tmpfs   /var/log    tmpfs    defaults,noatime,nosuid,mode=0755,size=100m    0 0
tmpfs   /tmp    tmpfs    defaults,noatime,nosuid,mode=0755,size=100m    0 0
tmpfs   /var/tmp tmpfs   nodev,nosuid 0 0
tmpfs   /run tmpfs nodev,nosuid 0 0
UUID="8df270b0-2987-41f5-9dcd-638adc991339" none swap defaults 0 0
UUID="290caee9-1fa3-453f-93ef-391173c126b0" /mnt/sdshare ext4 defaults,noatime,nodiratime,data=writeback 0 0
[alarm@alarmpi ~]$

Rod (greybeard)

It totally looks to me, that you tried to setup the sdcard_share twice. Everything is already put into place and is active.

You need to describe your forum issues, that we can dig into that one, too.

best regards Matthias

I had a few issues with the original install, and went back and began again. So you're right. The original install must have created the other partitions. Thanks for the re-assurance.

Rod (greybeard)