Upgrade 561->571 pupsave gets damaged

[paulh177]

Acer Aspire One AoA150-Aw, 1GB ram.

Puppy 561 frugal install with 2GB pupsave. Works fine.

Copied existing 561 pupsave to new directory, where I also copied puppy_precise_5.7.1.sfs, vmlinux and initrd.gz all from the new 571 "modern" iso.

I've now run 571 a number of times, recopying the 561 save-file each time, allowing it to upgrade the 561 save-file.

On each occasion, the first boot and shutdown goes OK, then the next boot is OK, but on shutting down after second boot, the shutdown screen displays a scrolling list of errors as follows (taken from /var/log/messages)

Code: Select all

Aug 30 08:22:36 puppypc15751 user.crit kernel: [   67.410582] EXT2-fs (loop1): error: ext2_lookup: deleted inode referenced: 33216

.

On each subsequent boot, a brief similar message is displayed during the boot sequence (but partially overwritten by the other normal boot messages).

I have tried running e2fsck on the 561 save-file copy prior to running the 571 upgrade, and though it finds a few 0times and inodes to fix, the upgrade sequence goes on to occur as I describe above anyway.

[lightheaded1]

I have a similar problem . when creating the savefile my computer locks up . when it is located at bootup the prompt tells me I have a bad block or corrupt super block and goes to loading the s.f.s but the file is still mounted . I even pulled the hard drive thinking it was infected .

[illidan.modeler]

Acer Aspire One AoA150-Aw, 1GB ram.

Puppy 561 frugal install with 2GB pupsave. Works fine.

Copied existing 561 pupsave to new directory, where I also copied puppy_precise_5.7.1.sfs, vmlinux and initrd.gz all from the new 571 "modern" iso.

I've now run 571 a number of times, recopying the 561 save-file each time, allowing it to upgrade the 561 save-file.

On each occasion, the first boot and shutdown goes OK, then the next boot is OK, but on shutting down after second boot, the shutdown screen displays a scrolling list of errors as follows (taken from /var/log/messages)

Code: Select all

Aug 30 08:22:36 puppypc15751 user.crit kernel: [   67.410582] EXT2-fs (loop1): error: ext2_lookup: deleted inode referenced: 33216

.

On each subsequent boot, a brief similar message is displayed during the boot sequence (but partially overwritten by the other normal boot messages).

I have tried running e2fsck on the 561 save-file copy prior to running the 571 upgrade, and though it finds a few 0times and inodes to fix, the upgrade sequence goes on to occur as I describe above anyway.

Excuse me, off topic for a bit. Are you using Slacko or Precise? I did not think there is a v5.7 for Slacko. Am I not correct?

[paulh177]

This is Precise.
My bad for not providing full enough information.

I have no idea if Slacko versions keep pace with Precise - I guess you could check Barry's blog?