Pupsave error with VanillaDpup 11.0.153 when a Microsoft Reserved partition exists. . [SOLVED]

[TerryH]

I did a manual frugal install to internal nvme drive(nvme0n1p7), on which I encountered a previously reported error where after entering woofwoof, it returns an error and has a 60 second pause. After the pause the boot continues to a desktop, however the pupsave doesn't run when clicked form the Leave GUI.

I ran pupsave in a terminal to check and saw the partition reporting in the screen displayed is messed from partition nvme0n1p2 which is a MS reserved partition. I was unable to create a pupsave in n1p7 due to the messed up display. I then from a different Puppy install deleted the pupsave directories copied from the Vanilladpup.img. Booted back into Vanilla Dpup and ran pupsave and while failing on n1p7 again, I was able to create a pupsave using sda3, which is a flash drive which wasn't inserted when the screen shot below was taken.

I then (back in Puppy) copied that pupsave to n1p7 and rebooted and am able to save to the pupsave in n1p7. Pupsave is still not possible to the nvme drive due to the issue created due to the filesystem type of nvme0n1p2 being unknown, which messes up the display of subsequent partitions.

[bugnaw333]

Maybe the "unknown" file sytem created by MS is to allocate for the system recovery--whatever. Here is mine:

[TerryH]

Maybe the "unknown" file sytem created by MS is to allocate for the system recovery--whatever. Here is mine:

It has to do with the difference between MBR based systems and UEFI. The UEFI systems can't use hidden sectors like in MBR systems, so microsoft creates this reserved partition. No idea what actually goes in there, maybe some sort of cache.

Regardless, of its use, pupsave doesn't like it.

[bigpup]

Nothing can use the partition but Windows OS.

Microsoft Reserved Partition
https://en.wikipedia.org/wiki/Microsoft ... _Partition

[TerryH]

Nothing can use the partition but Windows OS.

Microsoft Reserved Partition
https://en.wikipedia.org/wiki/Microsoft ... _Partition

This is NOT about attempting to use this partition. The existence of the partition messes up how pupsave displays partition information, making it error when attempting to create save folders.

[dimkr]

@TerryH What is the output of
lsblk -r -o type,name,fstype,size? I believe type is an empty string, it should be easy to make pupsave skip lines like this.

[dimkr]

Reproduced this problem in a Windows VM, please try to replace /usr/sbin/pupsave with https://raw.githubusercontent.com/vanil ... in/pupsave or grab 11.0.154 (10-20 mins from now )

(And don't copy the save folder from the image, it simply won't work. 11.0.x save folders contain a file named .pfscrypt that says which directories are encrypted, so when you copy the save folder but don't enable encryption the boot prompt will ask you to provide the passphrase to unlock these directories when they're not encrypted in first place - it will fail)

[TerryH]

So far I haven't had time to check the new release. I downloaded the new pupsave script. I was able to create new pupsave folders and saves are functioning as expected. I've marked this issue as solved.

Thank you.