STICKY: PINN - An enhanced version of NOOBS.

[procount]

Oh that's a shame. You didn't need to format anything, just copy the files as instructed.
Formatting just the e: drive would have been recoverable, but SD card formatter will have formatted the whole card erasing all the other partitions on it.

[Haris1977]

I couldn’t copy the files (disk space was exceeded). I couldnt delete my sd card’s files too: disk seemed write-protected (but it wasn’t). I think i couldnt even format the e: partition (not 100% sure about that)

Anyway i think my problem is my old usb to sd card adapter (not even micro sd). Will try the fix tomorrow and report back

Any idea why do i get all these partitions shown in my win10 ? I remember back in win7 era i could only see e: partition

[procount]

Latest Win10 is just getting better at displaying all the partitions on an SD card, even if it doesn't understand the ext partitions and thinks you should reformat them (don't do that!)

[Haris1977]

@Haris1977 - Please try https://sourceforge.net/projects/pinn/f ... p/download
(Unzip and copy everything EXCEPT recovery.cmdline over your existing PINN version)

• Fixed initial focus
• Changed tab order.
• Added shortcut keys U & D
• Added CEC keys 1,2,3,4 for Up,Down,Cancel,Boot

Any adjusted boot order is only saved if you click the BOOT button. Cancel will revert back to the original order.
(I've not been able to test the CEC function myself yet).

@procount

I just tried pinn-32a.zip. It seems to work as the initial focus is now fixed. CEC keys 1,2,3,4 though seems to do nothing (at least in my tv/set up) but i think it is a minor thing as you can change the boot order by just using your mouse (or U,D keyboard keys - they work as expected). I guess you should remove this option.

You can update with this interim version i suppose (with 1,2,3,4 cec keys removed).

[procount]

Thanks for checking.
I have released it as v3.2.1 as is and will look at the CEC keys when I can test it on a TV.

[procount]

So after testing, the 1&2 program keys map correctly to Up and Down on a Samsung TV. 3&4 don't work because they are masked by the Exit and Play buttons for Cancel and Boot respectively, since they do the same thing. If you have a different TV make/brand, you may need to map different CEC keys to these functions (see the wiki).

[Haris1977]

So after testing, the 1&2 program keys map correctly to Up and Down on a Samsung TV. 3&4 don't work because they are masked by the Exit and Play buttons for Cancel and Boot respectively, since they do the same thing. If you have a different TV make/brand, you may need to map different CEC keys to these functions (see the wiki).

I have my own cec_keys.json file. So maybe this file conflicts with the system. Thanks for your answer

[procount]

Yes, if you have your own CEC file, you'll have to map some CEC keys to the up and down keys.
Something like:

Code: Select all

    "bootSelection": {
        "any": {
            "Key_U":        "CEC_User_Control_Number1",
            "Key_D":        "CEC_User_Control_Number2",

[Haris1977]

Thanks:)

[ZHDarkstar]

I've got one of those touchscreen cases that ends up with the official touchscreen upside down. I have the lcd_rotate workaround working for Raspbian just fine, however PINN itself is still upside down for me. Is there a file that I can edit so PINN is rotated properly as well?

[procount]

Just create a config.txt file for PINN with the same lcd rotation settings in it.
For ease, go to the Maintenance menu, highlight the PINN entry and click the edit config button. Then enter your settings there.
Exit (press ok) and reboot.

[max11]

Hello,
i am working with pinn 3.2.1. and raspi 3b+
On the sdcard (64GB) are 4 OS (raspbian, retropie,libreelec, xbian) + 2 project-spaces. Now i wanted to backup raspbian(stretch).
I installed a 32 GB-card via usb-stick, formatted as FAT32, with an os-folder on it - nothing else.
Raspbian says there are 30 GB free - so the card is working and has enough space for just raspbian. As Raspbian is with all my data about 7GB pinn tells me it needs 2.3 GB space. But sometimes it tells me it needs 841 MB only (strange enough).
In the lower left corner it shows:

Destination Drive: sda storage device
Needed 841 MB
Available 30485 MB

But after confirming that i want to backup and confirming the suggested name(s) i always get an error, saying "An error occurred backing up.Perhaps there is no disk space?"

What am i doing wrong?
Regards
Max

[procount]

I'm not sure what is going wrong.
(Since the backup data will be compressed, the required space is only a conservative estimate, it may vary from that. 2.3GB sounds about right, but 841MB is obviously wrong).
Have a look at the troubleshooting section of my wiki @ https://github.com/procount/pinn/wiki/Troubleshooting
Maybe try following section 3 or 6 to provide a debug log. Something obvious may stick out, otherwise try posting the output. (Maybe better to open a github issue rather than filling the forum up with debug info.

EDIT: It could just be some missing meta files, especially if you installed the OSes with a much earlier version of PINN.

[max11]

Installation was done using Pinn 3.2.1 and using the recovery.cmdline provided by the tool from https://pinn.mjh.nz/
It looks like :
runinstaller quiet ramdisk_size=32768 root=/dev/ram0 init=/init vt.cur_default=1 elevator=deadline no_group no_default_source select="allnetwork" disablesdimages alt_image_source=http://pinn.mjh.nz/os_list.json?raspbia ... ace-2=8368

config.txt contains only hdmi(group/mode)

I checked dmesg ... it says "run fsck " .... all done - result the same.

[max11]

attached my dmesg

dmesg.zip

(9.02 KiB) Downloaded 267 times

[procount]

The contents of /tmp/debug would be quite useful....

[max11]

Hi ,
i had/have a hell of a problem entering recovery: Am connected via vncshare to the raspi. Pressingcrtl-alt-F2 i enter the recovery, but then the
(Notebook-)keyboard is disconnected and i have to enter via a tiny usb-keyboard, which is unfortunately sometimes repeating characters on its own...
So i tried about 15 times ... login (root) always works, password (raspberry) never. So i am stuck short of entering. I then connected at that stage via putty, entered login and password .. and succeeded.by entering /mnt/savelog.
As the backup problem arises before booting an os is loaded

log.zip

(5.13 KiB) Downloaded 268 times

i hope the enclosed log is sufficient.
Not knowing how to leave the recovery-mode (crtl-Alt-F1 doesn't work in putty i switched off the power ... copied the log and zipped it.
I btw couldn't find an error - except that libreelec sems to have a problem - but libreelec is not at all involved ...

[procount]

Thanks for the log. I think I can see a problem there so I will need to try and replicate it.
In the meantime, you might like to try deselecting "Raspbian Full" and see if you can back up the other OSes.

You cannot enter recovery mode through VNC. Ctrl-alt-f2 is just for a local keyboard/monitor - use ctrl-alt-f1 to return to the desktop.
For remote operation, you have to use ssh (putty). To exit from this shell, just type 'exit'.

[procount]

@max11 - I confirm this bug. It looks like I forgot about backing up OSes with spaces in their names, like "Raspbian full".
A fix will be on its way shortly.

[max11]

Hello,
thank you for your fast reply.
Yes, i tried to backup Libreelec... and succeeded immediately.

Thank you for your effort

[procount]

PINN has been updated to v3.2.2

V3.2.2

• Backup hotfix - Fix for OSnames with spaces.
• Translations - Updated IT & zh_TW
• Iconsizes - fixed to 40x40
• Download - ignore partials

This is a quick Hotfix release to fix the backup of OSes that have spaces in their name.
It also includes some other minor changes.

[max11]

Hello,
i installed the update and made a backup of my raspbian full. This backup ended with the information, that there was an error and i should read the debug.log.
I cannot find the debug.log.
Anyway, i tried to reinstall the backup (with the replace-function) and succeeded but only in so far, that the basic (pure) raspbian was installed - all my changes that i had made -like additional programs- are missing.
Where is my mistake?

[procount]

The debug log refers to the /tmp/debug file, which was part of the log you provided previously as part of your troubleshooting. It is only temporary, so if you have rebooted since then, it will have been lost. If it happens again, just follow the same troubleshooting instructions to capture the log.

When you backup the OS to your USB stick, it changes the names to something like "Raspbian_Full#20190516_161800" by appending the date and time of the backup (unless you edit it manually). Taht way you can store multiple backups on the same drive and uniquely identify them.
OS names with that format are shown in a different category called "Backup". Did you re-install "Raspbian_Full#2019XXXX_YYYYYY" from "Backup", or did you just re-install "Raspbian_Full" from "General", which would have been the original image?

One useful tip when you originally install your OSes is to always install at least one empty ProjectSpace if you have enough room. This will allow you to replace the ProjectSpace by a backup and do a comparison against the original OS. Or you could reinstall your backup to another SD card and verify it that way. It's always a good idea to test the backup before deleting the original.

[max11]

I repeated the backup-procedure and again after 6945 MB of 9514MB the same error happened: Backed up with errors.
I checked the log and there is the same error like before, when i couldn't backup at all.
It says 'disk full' - although it was an empty 32GB card.
The log is attached.

Backup.zip

(4.55 KiB) Downloaded 271 times

[procount]

I suspect your USB stick is formatted as FAT32, and the size of your backup file is >4GB, which is the largest permissible file size on FAT32.

Try formatting your USB stick as NTFS or EXT4, recreate your /os folder, then try backing up again. That should work.
I'll have to put a check in for that in a future version....