Puppy Linux Discussion Forum

[PaulBx1]

As of Puppy 4.1.2, "puppy pfix=fsck" does not work. This is a manual alternative:

Boot "puppy pfix=ram"

In a console window, mount the volume containing your pupsave. Then "cd" there.

modprobe cryptoloop
modprobe aes
losetup-FULL -e aes /dev/loop6 pup_save_crypta.2fs
e2fsck /dev/loop6

This procedure assumes heavy encryption and will need modification for light encryption (perhaps someone else can contribute that recipe). It also assumes your pupsave is named "pup_save_crypta.2fs", of course.

[vtpup]

I need assistance here for the commands needed to do an fsck on a light encrypted pup save -- anyone?

[MU]

I'm in hurry, so just a quick guess:

losetup-FULL -e xor /dev/loop6 pup_save_crypta.2fs
e2fsck /dev/loop6

http://noforum.de/man2html.php?page=losetup

Mark

[Pizzasgood]

According to the comments in the scripts in Puppy 4.2, that xor is a different one from the xor used for the encryption. According to the scripts it works like this:

[vtpup]

Thanks Mu and pizzasgood-

I'm using 4.1.2, not 4.2 -- but that didn't make a difference, pizzasgood solution worked.

I did try Mu's suggetsion first but I got an error message after entering the password. Thanks Mu for giving it a shot that quickly!

Thanks pizzasgood once again for the massive amount of help you give people here.

To clarify for others the steps that worked for me:

In my case my savefile was on sda6/puppy412/ and was named pup_save_cryptx.2fs, change that if your setup is different (marked in blue below). So:

1.) Boot puppy CD w/ puppy pfix=ram option
2.) Mount sda6
3.) open terminal
4.) type and enter modprobe cryptoloop
5.) type and enter losetup -E 1 /dev/loop6 /mnt/sda6/puppy412/pup_save_cryptx.2fs
6.) answer the password prompt
7.) type and enter e2fsck /dev/loop6
8.) you may be asked if you want to correct specific problems -- I answered yes to all, however it's possible not to if you feel something shouldn't be changed.

Thanks once again Pizzasgood, Mu, and PaulBx1 for this. You guys are great!

Makes me wonder if there's a simple bugfix in 4.1.2's code so that you can do an fsck as you are supposed to at the bootup password prompt. Functionality is supposed to be: hit ENTER instead of password, then in answer to the red prompt, hit any other letter.

I'd really like to do a routine fsck every month or so using the normal bootup method.

[Pizzasgood]

I'll take a look later tonight and see if it's still a problem in 4.2.1. If it isn't, I can throw together a 4.1.2 frugal really quick and test with that. Can't be too hard to fix.

[heaths]

Hi thanks for your replies
simulationcredit

[Pizzasgood]

Well, in the init script from 4.2.1 I found this at lines 742-753:

[vtpup]

Thanks for that Pizzasgood, I will try it later tonight.

I'm wondering if the reason for long delay, and/or reason it wouldn't mount is that the fsck process is throwing a Y/N question for the user, but possibly the user doesn't see or answer it? Maybe a subsequent silent abort leaves things mixed up. I don't know just throwing out a possibility since the code I used earlier definitely requires sitting by the keyboard. I had to hold down the Y key for autorepeat to get through all of the Y/N queries. Guess I had a lot of errors.

Is the fsck in initrd set to auto-fix errors, or does it still query?

Thanks again, and happy 4th of july (assuming you're in the states)!

[Pizzasgood]

This is the code for fsk_func in Puppy 4.2.1 (Lines 56-85 of init):

[vtpup]

[stiginge]

Hi Paul BX, I've had trouble with my heavy encrypted savefile, documented here:

http://www.murga-linux.com/puppy/viewtopic.php?t=72236

I used the code you provided above but it doesn't seem to work due to some block issue, have you seen this before?