"Happy Holidays to ALL of YOU!"
This bug exist in most/all modern WOOF built PUPs
Note: Although this has been observed in several PUPs, I am reporting it from a recent Carolina view.
Scenario
Here's a problem that Carolina is plagued by too. I have a "Compressed NTFS file system that I am testing Carolina from on a PC that is used to dual boot various OSes. This is rather a first for me, because I rarely use this method for running PUPs. But, I got started as a result of trying to help someone else in the forum.
The Boot manager is a Carolina installed GRUB4DOS to the MBR on the HDD. The menu.lst entry points to /LinuxBoots/Carolina (SDA5) folder where the contents of the Carolina ISO exist. On initial booting/pfix=ram all is well as its has always been. There is no GRUB4DOS error in getting the system booting and running properly accessing all HDD/USB partitions that exist. The funning system has NO ERRORs for anything it is doing. After desktop tailoring, I take the system thru Shutdown as I have done using Live media for years...ONLY THIS time, I select the option to store the save-session data to a file that is created in /LinuxBoots/Carolina folder.
So I now have a booting Carolina system with a Carolina file created of my session activities. This file is save by Carolina in the boot Carolina folder, as one would expect.
On reboot the system fails starting at the point when it attempts to reference the save file. It seems to find the file, but the file is not what the boot process wants to see.
Problem at boot
Normal boot messages leading up to the following:
loading drivers to access disk drives ..... done
searching for Puppy files ... pupsave zdrive adrive ... done
loading personal file /LinuxBoots/Carolina/linasave-005_01.4fs (sda5) ...
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Dumping last lines of /tmp/bootinit.log
mount: mounting /dev/loop1 on /pup_rw failed: Invalid argument
e2fsck: 1.41.9 (22-Aug-2009)
e2fsck: Invalid argument while trying to open /dev/loop1
mount: mounting /dev/loop1 on /pup_rw failed: Invalid argument
Dumping last lines of kernel.log
<6>[ 6.825671] aufs 3.2-20120326
<6>[ 6.828294] fuse init (API version 7.17)
<3>[ 11.066059] Ext4-fs (loop1):unable to read superblock
<3>[ 11.080042] Ext4-fs (loop1):unable to read superblock
Pausing for 60 seconds
.... system lockup follows ...
-------------------------------------
Problem at desktop skipping save-session
Starting the system via pfix=ram. At desktop I executed the following to access the save file and got the same error message for the save file:
Code: Select all
# losetup /dev/loop1 /mnt/sda5/LinuxBoots/Carolina/linasave-005_01.4fs
# e2fsck -b 8193 /dev/loop1
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Invalid argument while trying to open /dev/loop1
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Is there something wrong with Shutdown processing in Puppy Linux when it goes to create a save-session file from the running system to the Compressed NTFS?
Here to help