User avatar
procount
Posts: 2397
Joined: Thu Jun 27, 2013 12:32 pm
Location: UK

Re: STICKY: PINN - An enhanced version of NOOBS.

Sun Nov 29, 2020 9:34 am

denavin wrote:
Sun Nov 29, 2020 2:19 am
Is there a way to consolidate them using PINN without rebuilding or losing all the data on them.
Have a look at How-to-Create-a-Multi-Boot-SD-card-out-of-2-existing-OSes-using-PINN
PINN - NOOBS with the extras... https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=142574

User avatar
procount
Posts: 2397
Joined: Thu Jun 27, 2013 12:32 pm
Location: UK

Re: STICKY: PINN - An enhanced version of NOOBS.

Sun Nov 29, 2020 12:45 pm

New PINN V3.5.3 beta version available for testing.

I'm not pushing this version out immediately as a self-update because it was created in a new build environment and I would like some feedback that nothing has broken in the process.
If you want to test it out, please download the zip file from https://sourceforge.net/projects/pinn/f ... p/download and install to a FAT32 SD card as usual (only this zip file is available at the moment, no image file for Etcher or Raspberry Pi Imaging Utility yet).

As I've classified this as a beta version, please take appropriate precautions and do not use it on important data or OS imaages.
I would like feedback on all aspects of the program and across a wide range of RPi models to ensure it is working properly. Once I get enough positive feedback (or no negative feedback) I will release it for self-update.

The following additional features are included in this version:

V3.5.3
  • buildroot - improve some build scripts
  • dualhdmi - fix license
  • Installation - Refactor close dialogs for better error handling
  • Memory - Display amount of Pi memory fitted
  • partuuid - Allow installation to USB without partuuid
  • BuildEnv - Buildenv updated to Ubuntu 20.04
There's only 2 main changes you may notice in this version. The first is that PINN now reports the amount of fitted memory your Pi model has, which is useful for the Pi4 if you have several different models and want to be sure you are using the right one. The second is that this version will allow you to install some OSes to USB even when they don't support PARTUUID partition mounting. At the moment, this only applies to LineageOS, but more may be added if they are found to be suitable.

The problem with installing OSes to USB without PARTUUID support, is that the partitions are referenced using device name, e.g. /dev/sda1. If you have several USB storage devices fitted, Linux is not too particular on what it calls them, so one boot your device might be called /dev/sda, the next it might be /dev/sdb and so the correct partition will not be found and booting will fail. For this reason, you need to make sure that only 1 USB is fitted when you boot the OS in order to ensure it is called /dev/sda, otheriwse it won't wotk.

This is the reason why USB booting up til now has not been supported in NOOBS or PINN for OSes that do not support PARTUUID mounting. PINN has now relaxed this requirement in order to allow LineageOS to be installed to USB in either USB boot mode or hybrid mode (boot from SD card with root on USB). HOWEVER, it does come with the above caveat, so please be aware of the limitations. A warning message is displayed in PINN for any OS that is installed using this method, so please be aware of the consequences.
PINN - NOOBS with the extras... https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=142574

HJAST101
Posts: 34
Joined: Thu Aug 27, 2020 12:53 pm

Re: STICKY: PINN - An enhanced version of NOOBS.

Sun Nov 29, 2020 4:56 pm

Hi there.
There's a partition (/dev/sda8) that has a file called README.txt that shows this

Code: Select all

Data Partition README

This is a 512MB ext4 format partition for you to use as a shared data partition between your currently installed OSes.

For example, you might want to use this to hold your /home directory.

How would I make this hold my /home directory? I've never installed a Linux distro with the home folder on a separate partition, so I'm completely clueless.

WODAK
Posts: 49
Joined: Thu Jan 23, 2020 1:53 pm

Re: STICKY: PINN - An enhanced version of NOOBS.

Sun Nov 29, 2020 6:02 pm

Hi!

I have seen that you have added the new OS Lineage 17.1. Thank you very much for that!

Now I'm trying to replace the previous installed Lineage 16 with Lineage 17.1 but I get an error message
"Cannot Reinstal/Replace lineage 17-rpi4. Partition not big enough for new Image."

any ideas how could I solve that problem or how could I replace the Lineage 16 with Lineage 17.1?

greetings!

User avatar
procount
Posts: 2397
Joined: Thu Jun 27, 2013 12:32 pm
Location: UK

Re: STICKY: PINN - An enhanced version of NOOBS.

Sun Nov 29, 2020 6:37 pm

WODAK wrote:
Sun Nov 29, 2020 6:02 pm
"Cannot Reinstal/Replace lineage 17-rpi4. Partition not big enough for new Image."

any ideas how could I solve that problem or how could I replace the Lineage 16 with Lineage 17.1?
1. start again ;)
2. Use PINN to backup all your OSes to USB stick, then install the ones you want + LineageOS17 to a new SD card.
3. Use Gparted to adjust the size of your existing partitions so that they match (or are bigger than) the Lineage 17 requirements.
PINN - NOOBS with the extras... https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=142574

WODAK
Posts: 49
Joined: Thu Jan 23, 2020 1:53 pm

Re: STICKY: PINN - An enhanced version of NOOBS.

Sun Nov 29, 2020 6:46 pm

OK...

I've tried....I've inserted an empty USB with folder OS and then I've booted to PINN...then when I select any of OS-es(Raspbian ,Libreelec, ....) the button backup is still disabled...any ideas?

I am using the latest PINN 3.5.2

User avatar
procount
Posts: 2397
Joined: Thu Jun 27, 2013 12:32 pm
Location: UK

Re: STICKY: PINN - An enhanced version of NOOBS.

Sun Nov 29, 2020 6:58 pm

Does it show your USB stick (/dev/sda1) as the destination target? What filesystem did you format it with? ext4, ntfs or FAT32? (check it is not exFAT)
PINN - NOOBS with the extras... https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=142574

User avatar
procount
Posts: 2397
Joined: Thu Jun 27, 2013 12:32 pm
Location: UK

Re: STICKY: PINN - An enhanced version of NOOBS.

Sun Nov 29, 2020 7:21 pm

HJAST101 wrote:
Sun Nov 29, 2020 4:56 pm
How would I make this hold my /home directory?
Not my specialism, but one way is to just mount his partition onto your home directory.
But before you do, you should probably copy any existing files on your home directory onto it
So maybe something like:

Code: Select all

mkdir /tmp/data                 #Create a folder as a mount point
sudo mount /dev/sda8 /tmp/data  #mount the data partition so you can access it
rsync -avr ~/* /tmp/data        #copy everything existing on your current home folder onto the data partition
sudo umount /tmp/data           #unmount the data partition
rmdir /tmp/data                 #remove the temporary mountpoint

sudo mount /dev/sda8 /home/pi   #mount your data partition onto your home directory
Using the above method, you'd have to mount your data partition on your home directory each time you reboot.
So the next step would be to put an entry in your /etc/fstab file (use sudo nano /etc/fstab to edit it)

e.g. add an extra line, something like:

Code: Select all

/dev/sda8    /home/pi   ext4  .....
PINN - NOOBS with the extras... https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=142574

WODAK
Posts: 49
Joined: Thu Jan 23, 2020 1:53 pm

Re: STICKY: PINN - An enhanced version of NOOBS.

Sun Nov 29, 2020 8:12 pm

procount wrote:
Sun Nov 29, 2020 6:58 pm
Does it show your USB stick (/dev/sda1) as the destination target? What filesystem did you format it with? ext4, ntfs or FAT32? (check it is not exFAT)
So sorry! my bad! It was formated with exFAT :oops:

tnx for your help!

denavin
Posts: 28
Joined: Thu Nov 26, 2020 4:15 am

Re: STICKY: PINN - An enhanced version of NOOBS.

Mon Nov 30, 2020 2:15 am

procount wrote:
Sun Nov 29, 2020 9:34 am
denavin wrote:
Sun Nov 29, 2020 2:19 am
Is there a way to consolidate them using PINN without rebuilding or losing all the data on them.
Have a look at How-to-Create-a-Multi-Boot-SD-card-out-of-2-existing-OSes-using-PINN
2. Insert your uSD card that has your customised Raspbian OS on it into the USB reader and insert it into a free USB slot of the PC. You need to note what device Linux has assigned it (e.g. /dev/sdb) and where it has been mounted (e.g. /media/<username>/boot or /root etc).
Some Linux OSes may automount the partitions on this SD card, so in this case you can type mount to identify the device and where it's partitions have been mounted and skip the next step. For this tutorial, we will assume the SD card is referenced as /dev/sdb with /dev/sdb1 mounted at /media/<username>/boot and /dev/sdb2 mounted at /media/<username>/root. If yours is mounted at a different location, please replace appropriately in the following steps.

After inserting the USB SC card reader into my PC running a Debian Windows (WSL)
~$ mount
rootfs on / type wslfs (rw,noatime)
none on /dev type tmpfs (rw,noatime,mode=755)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,noatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,noatime)
devpts on /dev/pts type devpts (rw,nosuid,noexec,noatime,gid=5,mode=620)
none on /run type tmpfs (rw,nosuid,noexec,noatime,mode=755)
none on /run/lock type tmpfs (rw,nosuid,nodev,noexec,noatime)
none on /run/shm type tmpfs (rw,nosuid,nodev,noatime)
none on /run/user type tmpfs (rw,nosuid,nodev,noexec,noatime,mode=755)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
C:\ on /mnt/c type drvfs (rw,noatime,uid=0,gid=0,case=off)
D:\ on /mnt/d type drvfs (rw,noatime,uid=0,gid=0,case=off)
E:\ on /mnt/e type drvfs (rw,noatime,uid=0,gid=0,case=off)
F:\ on /mnt/f type drvfs (rw,noatime,uid=0,gid=0,case=off)
G:\ on /mnt/g type drvfs (rw,noatime,uid=0,gid=0,case=off)
I:\ on /mnt/i type drvfs (rw,noatime,uid=0,gid=0,case=off)
J:\ on /mnt/j type drvfs (rw,noatime,uid=0,gid=0,case=off)
K:\ on /mnt/k type drvfs (rw,noatime,uid=0,gid=0,case=off)
I do not see where or if my USB SD card reader is mounted. It looks as though it is not, so following instructions;
3. If it has not been auto-mounted, you will need to manually mount the partitions on the device.
$ dmesg
Look for the recent logs at the end of the dmesg output to identify the name of the most recently added device. You then need to create a mountpoint for each partition on the device. We will assume the device has been assigned /dev/sdb and has 2 partitions (/dev/sdb1 and /dev/sdb2) named boot and root
I type;
~$ dmesg
[ 0.004023] Microsoft 4.4.0-19041.488-Microsoft 4.4.35

Is all I get back. It does not show anthing about ;
/dev/sdb and has 2 partitions (/dev/sdb1 and /dev/sdb2) named boot and root...
How do I proceed from here.
OBTW I am very new to Linux so please don't get too technical, I am still learning it.

User avatar
procount
Posts: 2397
Joined: Thu Jun 27, 2013 12:32 pm
Location: UK

Re: STICKY: PINN - An enhanced version of NOOBS.

Mon Nov 30, 2020 8:36 am

I see you are running Debian as WSL, so it is not producing the same results as pure debian.

You can substitute your "Linux PC" with a Raspberry Pi running Raspberry Pi OS (Raspbian). I only suggest using a PC because it is quicker.
PINN - NOOBS with the extras... https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=142574

denavin
Posts: 28
Joined: Thu Nov 26, 2020 4:15 am

Re: STICKY: PINN - An enhanced version of NOOBS.

Mon Nov 30, 2020 9:05 am

procount wrote:
Mon Nov 30, 2020 8:36 am
I see you are running Debian as WSL, so it is not producing the same results as pure debian.

You can substitute your "Linux PC" with a Raspberry Pi running Raspberry Pi OS (Raspbian). I only suggest using a PC because it is quicker.
I though that Debaian WSL might be the problem so I installed a virtual machine of Ubuntu 20.10 in Virtual Box.
I was able to get the USB SD card mounted and identified so I proceeded to #4 in the instructions. But when I went to copy the SD card I ran into an error when entering;

~sudo bsdtar --numeric-owner --format gnutar -cpvf ~/os/Raspbian/boot.tar . $ cd /media/<plg>/root

Ubuntu returned an error:
sudo: bsdtar: command not found

Do I need to use a different version of Linux? Should I just install a virtual machine of Ubuntu 20.04 Server or Core instead?

I used a virtual machine and not the Raspberry Pi because of the warning about the lack of memory and I only have one PC to use, so I would rather not try to setup a Dual Boot system just for this.

Or should I try installing a virtual machine of Raspbian on the PC since there are PC versions of Raspbian..

User avatar
procount
Posts: 2397
Joined: Thu Jun 27, 2013 12:32 pm
Location: UK

Re: STICKY: PINN - An enhanced version of NOOBS.

Mon Nov 30, 2020 9:18 am

I also use Ubuntu in a virtual machine and it works fine.
But Ubuntu does not come with bsdtar by default.
You can use plain tar instead and that should work. bsdtar just provides more compatibility with the number of OSes I need to use.

If you want to install bsdtar you can look here -> https://github.com/procount/pinn/blob/m ... pendencies
Just use `sudo make install` as the last step.
PINN - NOOBS with the extras... https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=142574

stereo_soul
Posts: 1
Joined: Mon Nov 30, 2020 2:51 pm

Re: STICKY: PINN - An enhanced version of NOOBS.

Mon Nov 30, 2020 2:58 pm

Hello there. I try to install raspberry OS lite and Recalbox through PINN, but there is problem-
recalbox try to install and download something like 8 mb of 1400, then report install is ok. raspberry os install next and its donload all 1400MB, and install correctly. If i boot to recalbox- kernel panic ( obviously). Raspberry os works fine.
How to install recalbox and raspbery OS dualboot if recalbox wont download all the files?

User avatar
procount
Posts: 2397
Joined: Thu Jun 27, 2013 12:32 pm
Location: UK

Re: STICKY: PINN - An enhanced version of NOOBS.

Mon Nov 30, 2020 3:08 pm

Recalbox has recently been updated in NOOBS. I've not tried it myself.
There are 3 versions of it - which model of RPi do you have?
PINN - NOOBS with the extras... https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=142574

denavin
Posts: 28
Joined: Thu Nov 26, 2020 4:15 am

Re: STICKY: PINN - An enhanced version of NOOBS.

Tue Dec 01, 2020 8:43 am

PINN is a very nice system but after spending 2 days to get it installed I finally had to dump it and give up. I was finally able to get it to work, though no matter how hard I tried I could not transfer over my already made SD card and their data successfully and lost all the data on one in the processes. So I started from scratch.

After attempting to get PINN to install, after 6 hour and 10 attempts, I was finally able I was able to get it to boot. I then spent the next 4 hours trying to get it to install any OS's at all. After many attempts PINN finally relented and allowed me to install my (will almost) all my chosen OS's, except for 2, Android and RISC OS.

With much joy I rebooted my Pi I was greeted by the PINN OS Selection Page. I choose Raspbian and hit Boot. My Pi instantly locked up then crashed. So I powered down and restarted the Pi. The system started then while booting crashed again, but it instantly rebooted. But instead of giving me the PINN OS Selection Page it booted directly into Raspbian. Having never worked with PINN I thought that this was normal....I would soon find, It was not.

I proceeded to configure Raspbian but it was very very slow. Instead of only taking about 5 minuets it tool over an HOUR. But I was finally able to get Raspbian up and running. But all was not good in the world of PINN. After rebooting to finish the configuration of Raspbian my Pi rebooted. then instantly crashed and rebooted again. But once more I was not greeted by the PINN OS Selection Page, instead my Pi booted directly into Raspbian. Well I though that this may also be normal.... But It Was NOT.

So I wanted to try out Ubuntu which I has also installed with PINN, I shut down Raspbian and rebooted my Pi. Once again it rebooted then instantly crashed the rebooted back into Raspbian and not into the PINN OS Selection Page.

Needless to say after spending now around 15 hours and 2 days my frustration level was high. I searched the Forums to no avail. Seems I was the only one that was having this problem as no one had posted anything like it anywhere including in a Google search.

So I figured that I would just go back to a single OS on the SD card. Or so I though. Upon attempting to format the SD card I found that for the 5 OS's I had installed on my SD card PINN had made 12 partitions. Upon putting the SD card in m PC and waiting 15 minuets for it to scan all the partitions. I was UNABLE to format it as no program I tried would identify a Drive letter that the program could format. Not SD Card Formatter, not Raspberry Pi Imager not even windows.The only way I was finally able to access the SD card was in Ubuntu with Gparted. Oh and yes it tool 15 minuets each time I tried a different program including Ubuntu and then Gparted which each took their own sweet time to read the SD card's partitions.

But even Gparted was having issues reading the SD card. Again after 2 more hours I was able to delete all 12 partitions and format the SD card. Then set about reinstalling Raspbian on to the SD card and now must spend even more time rebuilding all the data I had on it. Including my Web server and Web page that I was working on that is now LOST.

Though PINN may be useful it is far too BUGGY and difficult to be useful. My suggestion would be "don't screw with what works just to try something different".

I guess I will just keep swapping out SD card when ever I want to change OS's until such time as something MUCH better comes along that actually works without the need to spend days and hours just to find out that it does not.

Though I do want to Thank You for your help and assistance.......

User avatar
procount
Posts: 2397
Joined: Thu Jun 27, 2013 12:32 pm
Location: UK

Re: STICKY: PINN - An enhanced version of NOOBS.

Tue Dec 01, 2020 12:23 pm

@denavin - Sorry to hear about your trials and tribulations when using PINN. I would have to say that your experience is quite unusual, as you found when you searched unsuccessfully for answers to your problems on the forums and elsewhere. It was a pity that you didn't mention any of these issues in your previous posts as I could have helped you sort them out. It sounds like you have given up, which is a shame. But if you do want to try again, I suggest you open an issue on my github page and I could walk you through your problems one-to-one, like I have done with others. There have been over 180,000 downloads of PINN, and most people get on fine with it. So I do feel you have some other underlying problems which are not helping you here - maybe power supply or SD card related.

Nevertheless, I shall try to address some of your points below, also for the benefit of other readers.

denavin wrote:
Tue Dec 01, 2020 8:43 am
PINN is a very nice system but after spending 2 days to get it installed I finally had to dump it and give up. I was finally able to get it to work, though no matter how hard I tried I could not transfer over my already made SD card and their data successfully and lost all the data on one in the processes. So I started from scratch.
Being based on NOOBS, PINN was designed to be installed without special tools, i.e. a standard SD card format to FAT32 (required for a Pi to boot the partition in the first place) and an unzip (available on most Windows systems). So it should not take 2 days to get PINN installed. The advent of cheap SD cards larger than 32GB and the fact that Windows formats such cards to exFAT, has complicated the process now, requiring more special tools to format such SD cards as FAT32. However, PINN is also available as an image file which can be flashed to the SD card with the more up to date and popular tools such as Etcher and the Raspberry Pi Imaging Utility (which I believe can also flash the normal pinn-lite.zip file). I've also made some blank FAT32 images available of varying sizes which can be flashed to an SD card with Etcher or RPI imager, as an alternative to formatting the whole SD card.

Importing an existing SD card image has always been a bit of a challenge. However there are instructions in PINN's README_PINN documentation and also a complete tutorial in my wiki that I pointed you to. If the tutorial is followed correctly, you should not lose any data since it goes to great lengths to preserve your existing image.
denavin wrote:
Tue Dec 01, 2020 8:43 am
After attempting to get PINN to install, after 6 hour and 10 attempts, I was finally able I was able to get it to boot. I then spent the next 4 hours trying to get it to install any OS's at all. After many attempts PINN finally relented and allowed me to install my (will almost) all my chosen OS's, except for 2, Android and RISC OS.

With much joy I rebooted my Pi I was greeted by the PINN OS Selection Page. I choose Raspbian and hit Boot. My Pi instantly locked up then crashed. So I powered down and restarted the Pi. The system started then while booting crashed again, but it instantly rebooted. But instead of giving me the PINN OS Selection Page it booted directly into Raspbian. Having never worked with PINN I thought that this was normal....I would soon find, It was not.
Did you install the full PINN version, or PINN-lite? I always advocate using pinn-lite as it uses very little SD card space and is much quicker to install. IIRC, there are problems installing RiscOS when you have the PINN FULL (or NOOBS FULL) since it must occupy a particular position on the SD card which would be taken up by the much increased size of the RasPIOS and LibreELEC installation files nowadays.

The constant crashing you experienced is not normal. It suggests you might have a faulty SD card (which you should check with H2testw, since unfortunately, some larger SD cards can be fakes, reporting a larger size thna they actually are), or possibly a power supply problem which causes a crash when the CPU is put under load.

It is a feature of both NOOBS and PINN that on boot, it will automatically select the last OS booted and boot into that after about 10 secs. On first boot of PINN it will present the OS selection list and wait because there was no last OS booted. Of course there are many configuration options in PINN to alter this behaviour, such as setting the `forcetrigger` option to force the selection menu to be displayed. There are other options to change the timeouts and select specific OSes that you will find in the documentation. Did you check one of the "Sticky Default" boxes next to any of your chosen OSes? This would cause the behaviour you described.

denavin wrote:
Tue Dec 01, 2020 8:43 am
I proceeded to configure Raspbian but it was very very slow. Instead of only taking about 5 minuets it tool over an HOUR. But I was finally able to get Raspbian up and running. But all was not good in the world of PINN. After rebooting to finish the configuration of Raspbian my Pi rebooted. then instantly crashed and rebooted again. But once more I was not greeted by the PINN OS Selection Page, instead my Pi booted directly into Raspbian. Well I though that this may also be normal.... But It Was NOT.
By "configuring Raspbian", are you referring to the first configuration dialog that runs when you first boot into Raspbian? This has nothing to do with PINN and further suggests an underlying problem with your SD card, power supply, or maybe even network connection or server slowness if you are referring to the update process of Raspbian.
I definitely think you ticked the "sticky default" box next to Raspbian which would cause Raspbian to boot automatically each time (That's what that checkbox is for)

denavin wrote:
Tue Dec 01, 2020 8:43 am
So I wanted to try out Ubuntu which I has also installed with PINN, I shut down Raspbian and rebooted my Pi. Once again it rebooted then instantly crashed the rebooted back into Raspbian and not into the PINN OS Selection Page.

Needless to say after spending now around 15 hours and 2 days my frustration level was high. I searched the Forums to no avail. Seems I was the only one that was having this problem as no one had posted anything like it anywhere including in a Google search.
Your case is quite unusual. I have seen some download issues with Sourceforge recently where I host most of the OSes, but they generally sort themselves out, and not much I can do about that.

denavin wrote:
Tue Dec 01, 2020 8:43 am
So I figured that I would just go back to a single OS on the SD card. Or so I though. Upon attempting to format the SD card I found that for the 5 OS's I had installed on my SD card PINN had made 12 partitions. Upon putting the SD card in m PC and waiting 15 minuets for it to scan all the partitions. I was UNABLE to format it as no program I tried would identify a Drive letter that the program could format. Not SD Card Formatter, not Raspberry Pi Imager not even windows. The only way I was finally able to access the SD card was in Ubuntu with Gparted. Oh and yes it tool 15 minuets each time I tried a different program including Ubuntu and then Gparted which each took their own sweet time to read the SD card's partitions.
There is nothing special about the partitions PINN creates. Each OS typically requries 2 partitions (one FAT32 and one EXT4. Some, like Android, require 4 partitions). It is unfortunate that a Windows PC does not understand most Linux partitions, but SD card formatter should be able to cope with it. The fact that it didn't and that every tool you tried took a long time to scan the partitions suggests there is something wrong with your SD card. That is not normal and nothing to do with PINN.

denavin wrote:
Tue Dec 01, 2020 8:43 am
But even Gparted was having issues reading the SD card. Again after 2 more hours I was able to delete all 12 partitions and format the SD card. Then set about reinstalling Raspbian on to the SD card and now must spend even more time rebuilding all the data I had on it. Including my Web server and Web page that I was working on that is now LOST.
I don't know how you managed to delete your original data if you followed the tutorial to backup that data to a tar file. Rule #1 is always make a backup.
denavin wrote:
Tue Dec 01, 2020 8:43 am
Though PINN may be useful it is far too BUGGY and difficult to be useful. My suggestion would be "don't screw with what works just to try something different".
I dispute it is "BUGGY". There are a few known minor issues that I am slowly solving, but nothing that causes the slowness, crashing and data loss that you have experienced, which I think must be attributable to other problems.
"Difficult to use" is a highly subjective term. I don't think it is any more difficult to use than any other comparable program. It does help to first read the comprehensive documentation that I provided with it though.
denavin wrote:
Tue Dec 01, 2020 8:43 am
I guess I will just keep swapping out SD card when ever I want to change OS's until such time as something MUCH better comes along that actually works without the need to spend days and hours just to find out that it does not.
Though I do want to Thank You for your help and assistance.......
I only know of NOOBS, BerryBoot and RonR's Multiboot (PiBakery has unfortunately died) as alternatives. Maybe you will find one of those more suitable for you.

You're very welcome to my help and assistance. As I said, feel free to open a github issue if you want more detailed support on your issues if you want to continue. But I suggest you check your SD card, power supply and network connections are all reliable, because I think there is something else going on with your system that is causing you grief.
PINN - NOOBS with the extras... https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=142574

denavin
Posts: 28
Joined: Thu Nov 26, 2020 4:15 am

Re: STICKY: PINN - An enhanced version of NOOBS.

Tue Dec 01, 2020 9:09 pm

Thank you for your reply.

Please understand that I am not complaining but am seriously confused as to why I was having such problems.

I would like to continue a dialog with you but do not know how to go about that on GitHub. I really would like to get this to work.

As for HOW I managed to loose the "Root" partition I really have no idea. I had both partitions when I was trying to backup the SD card in Ubuntu. I ejected the card and closed Ubuntu for the night after writing my problems out in these forums. On the next day after your suggestion to use TAR rather than BSDTAR I fired up Ubuntu again and loaded my SD card only to find ONE partition left. I must admit that some of the time I spent trying to get this all to work was in trying desperately to recover the " ROOT" partition and the DATA that Gparted said was still there. But alas to my shagrin I was unable to so I opted to simply format the card and start again.

As for the SD card I used a SanDisk Ultra 128 GB XC SD card, so the quality should not be a problem and I have tested the card to make sure that it is functioning correctly with no errors and it passed. I am experienced using computers for many years and have learned my lesson about skimping out on good hardware long ago.

As for importing my exiting OS's I really never got the chance to attempt this but for the first time, after the loose of the "Root" partition there was not longer a need so I simply wanted to see how PINN would work and went with a (what I though would be) simple instillation from scratch.

I used PINN-LITE in both the .zip and .img formats and had problems with both equally. The .zip at first would not boot, I could not even get the PI to POST, no BIOS screen simply nothing. I though "oh great my PI had died" but I would POST with no SD card so at least I knew that my PI was not dead. I then tried the .img and used BlenaEtcher to flash the image to the SD card. But even that was plagued with problems. The Image would not verify and would not boot. This is when I tested the SD card to make sure that there was noting wrong with it even though I had been using this card for the last month with Raspbian on it. It passed testing so I tried the .zip and copy method again. This time I was able to get the PI to behave and POST and boot. I thought all was good until I attempted to load OS's

I wanted to load several Raspbian, RISC OS, Lineage OS, LebreELEC, RetroPI, LAKKA and one other Multi-Media OS that I can not recall the name of at this time but it is the only other one on the "Media" tab in PINN. I tried many times with each time getting errors. Some were that it could not write to the SD card or Could not connect I got this one trying to install Raspbian several times. One was Could not Find File for Linage. Other were simply NOT allowing me to "continue with selected" but no explanation of what could not be continued. Sorry I did not write down the messages, I should have but after several hours of this I was not in a good mood. I remembered having read that Lineage and RISC OS were not supported my PINN but since I saw them in the Install list I thought that the issue had been addressed and fixed. I started removing OS's one at a time starting with RISC OS. The process got a little further than previously and seemed to finish the instillation. But upon reboot it put me right back into the Install OS page again. This time I removed Lineage OS and tried again. This time upon reboot I was presented with the OS Selection Page. Then the fun started.

I selected Raspbian and you know the rest. Crash, power down, restart, crash, auto reboot into Raspbian, wanting to try another OS, reboot, crash, auto reboot right back into Raspbian again. this time instead of selecting reboot from the Raspbian menu I shutdown Raspbian and powered down the Pi, Restart, crash, auto reboot right back into Raspbian again. I tried a couple of more times but after I had been working on this for the number of hours I had been at it already I was in no mood to continue so I decided to format the SD card and ran into even more problems.

As for as configuring Raspbian yes it was the Initial install configuration but the slowness did not stop there upon rebooting back into the newly configured Raspbian the system was very laggy. Menus took forever to open, Chromium would take way too long to start, the whole Pi OS was sluggish and laggy. I have not idea why. It was at that time I wanted to try another OS and ran into more problems than I wanted to deal with at the time.

Now I understand the SD cards do not have a very fast DATA transfer rate as compared to HD's or SSD's. But the 15 minuet scan each time I wanted to do anything with the card was irritating to say the least. I first tried SD card fomatter, after waiting the 15 or so minuets it opened to a BLANK screen, no SD card info No interface NO nothing. I closed the program and tried to reload it but once again the 15 minuet scan started to I force closed that program by Killing the Process since I could not click on anything in the program and did not want to wait. I then tried Raspberry Pi Imager. After waiting the 15 minuets I tried to "Erase" the SD card only to be tolled that "No Drive Letter Could Be Identified To Erase". I then proceded to try Windows but like you said Windows had not ideas what to do with Linux partitions and refused to work. I then started up Virtual Box and started Ubuntu, loaded the USB reader into it and up popped all the partitions. I then went to Gparted and waited for it to scan for another 15 minuets. It was here that I was able to see ALL the partitions 12 in total. After deleting each indivual partition and confirming my selections Gparted proceed to do its work giving me back an empty SD card that I was NOW able to load into SD Card Formater and format then load Raspbian back onto it with no issues at all.

I have no idea what was going on but would like to try again if there is a way to get this whole thing to work. As of right now I have 5 SD card each with a single OS on them. If this can be done using ONE SD card that would be great.

As for the BUGGY comment please understand that after Hours and Hours of Failure after Failure I was just a little bit Miffed. I am sure that PINN is a good and functional application that has been successfully used many time by many people it just seemed that for me that was not the case and frustration got the better of me.

I do appreciate all the time you have taken and your offer for continued help which I will gladly accept.

Thank You for ALL you time and Help......

denavin
Posts: 28
Joined: Thu Nov 26, 2020 4:15 am

Re: STICKY: PINN - An enhanced version of NOOBS.

Tue Dec 01, 2020 10:31 pm

One more thing I noticed when I finally got Gparted to show me the partitions, that they were all only 512 MB. So I am wondering where does PINN put the Data for each of these OS's that are loaded. 512 MB is not allot of space for storage. Does PINN put this data in each Partition? Or does it make a separate folder or location for the data that will eventually be loaded on to the SD card for each OS.

THX1182
Posts: 50
Joined: Fri Oct 11, 2019 6:24 pm

Re: STICKY: PINN - An enhanced version of NOOBS.

Tue Dec 01, 2020 10:48 pm

Yo procount you deserve a christmas present or whatever, where can we donate some change to you??? :mrgreen:

User avatar
procount
Posts: 2397
Joined: Thu Jun 27, 2013 12:32 pm
Location: UK

Re: STICKY: PINN - An enhanced version of NOOBS.

Tue Dec 01, 2020 11:10 pm

@THX1182 - thanks. One day I'll set up a donate button :)
PINN - NOOBS with the extras... https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=142574

User avatar
procount
Posts: 2397
Joined: Thu Jun 27, 2013 12:32 pm
Location: UK

Re: STICKY: PINN - An enhanced version of NOOBS.

Tue Dec 01, 2020 11:49 pm

@denavin - I suggested raising an issue on my Github page to save spamming this forum with pages of dialog which were specific to you and may not interest so many others. You just need to go to https://github.com/procount/pinn/issues and click on the green New Issue button. If you are not already a member, just click on signup first (top right of page) and create a username with email and password.

Please remind me which model of RPi are you using, and what storage device and size you are using.
PINN - NOOBS with the extras... https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=142574

WODAK
Posts: 49
Joined: Thu Jan 23, 2020 1:53 pm

Re: STICKY: PINN - An enhanced version of NOOBS.

Wed Dec 02, 2020 5:49 pm

I bought a new Micro SD card (Samsung EVO PRO 128 GB) and tried to install 5 different OS systems from PINN resize ( https://pinn.mjh.nz/) page.

Code: Select all

http://pinn.mjh.nz/os_list.json?lineage17-rpi4=32000&raspberrypios32-bit=20000&retropie4=30000&libreelec_rpi4=15000&projectspace-1=18100 
I think there is an error when I try to install Lineage 17.1. I tried a couple of times to install different OS-es and every time I select Lineage 17.1 I get an error . When the process finishes It says that it could not install all OS-es. When I boot again I can see all OS-es installed except of Lineage 17....

Code: Select all

Error desc:
Executing: "/sbin/mkfs.fat -n boot0 /dev/mmcblk0p10"
Executing: "sh -o pipefail -c "wget  --retry-connrefused  --read-timeout=120 --tries=inf --no-verbose -O- http://downloads.sourceforge.net/project/pinn/os/lineage17-rpi4/boot.tar.xz | tee /tmp/fifo | xz -dcT 0 | bsdtar -xf - -C /mnt2  --no-same-owner  | sha512sum /tmp/fifo > /tmp/sha1.out.txt""
Calculated Checksum= "bc230fc7ff2a45f951b389d3024a4a1fb026bfabe946af152bb3b0bc3318ca67e7612493d106c7d6ec08ec3a292b81394c48581f51607c8816750c9eb6eb38f8"
Expected csum=  "bc230fc7ff2a45f951b389d3024a4a1fb026bfabe946af152bb3b0bc3318ca67e7612493d106c7d6ec08ec3a292b81394c48581f51607c8816750c9eb6eb38f8"
finished writing filesystem in 32.229 seconds
Executing: "sh -o pipefail -c "wget  --retry-connrefused --read-timeout=120 --tries=inf --no-verbose -O- http://downloads.sourceforge.net/project/pinn/os/lineage17-rpi4/system.tar.xz | tee /tmp/fifo | xz -dc | dd of=/dev/mmcblk0p11 conv=fsync obs=4M | sha512sum /tmp/fifo > /tmp/sha1.out.txt;""
Error: "Error downloading or writing OS to SD card
http://downloads.sourceforge.net/project/pinn/os/lineage17-rpi4/system.tar.xz:
2020-12-02 17:40:56 ERROR 404: Not Found.
xz: (stdin): File format not recognized
0+0 records in
0+0 records out
"
Client protocol version RFB 003.003

I think the error might be missing files. The file http://downloads.sourceforge.net/projec ... tem.tar.xz does not exsist. The link https://sourceforge.net/projects/pinn/f ... tem.img.xz does.

User avatar
procount
Posts: 2397
Joined: Thu Jun 27, 2013 12:32 pm
Location: UK

Re: STICKY: PINN - An enhanced version of NOOBS.

Wed Dec 02, 2020 6:05 pm

Oops - Looks like I forgot to change the file type! sorry :oops:
I hope I've just fixed it for direct downloads, but it might take 24 hours to be fixed via Matt's webpage if you want to do the partition resizing.

If you want it sooner, If you can get PINN to think that Lineage is still present (it might be a case of just setting `bootable=true` in /settings/installed_os.json), then you could probably do a direct re-install or replace of the failed Lineage, rather than having to reinstall everything.

Thanks for reporting it.
PINN - NOOBS with the extras... https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=142574

WODAK
Posts: 49
Joined: Thu Jan 23, 2020 1:53 pm

Re: STICKY: PINN - An enhanced version of NOOBS.

Wed Dec 02, 2020 6:24 pm

No problem...I made my own os_list.json with repaired links and I am installing it right now :)

Return to “General discussion”