No boot from a new install of Lucid 528?
 

Hi all.

I have a strange problem with a brand new install of Lucid 528. I 'think' it has something to do with the personal details saved file - stuff like location and timezone etc.

This is what I have done. I got a brand new burn (done myself using K3b on Linux Mint16) of Lucid Puppy 528. I popped this into the DVD drive of a rather old desktop PC. The PC has two optical drives but no hard drives other than a 2gb Compact Flash drive in an IDE adaptor socket. The PC has 128mb of RAM, hence my wish to use Puppy with it. The disk fired up and booted to a very nice desktop. So far so good. I then opted to install Puppy to the Compact Flash drive. This appeared to work so I then went for a reboot.

Just before the reboot I took the original DVD with Puppy burned on it out of the DVD drive. The PC then went on to successfully boot from the Compact Flash drive. Great stuff! I then decided to customise the locale and time to Great Britain. Once I had done this I then went for a reboot to make sure everything was still ok. I was given the option to save the changes I had made to the Compact Flash drive which I accepted.

Upon reboot the problems started :( This is what I was presented with:

Loading drivers needed to access disk drives... done
Searching for Puppy files in computer disk drives... done
Loading the 'lupu_528.sfs' main file... done
Setting up the layered filesystem... failed

Fatal:Module pci:v0000109Ed00000878sv00000070sd000013EBbc04sc80i00 not found.
Cannot create regular file '/pup_ro1/var/local/etc_profile_at_shutdown'. No such file or directory.
mount:mounting unionfs on /pup_new failed
Dumping last lines of kernel log...
<6>EXT3-fs (sda1):using internal journal
<6>EXT3-fs (sda1):mounted filesystem with ordered data mode
<4>aufs test_add:248:mount[630]:uid/gid/perm /pup_r01 0/0/0755, 0/0/01777
<3>aufs test_add:233:mount[630]: /pup_ro2 is overlapped
Pausing for 60 seconds...
Performing a 'switch_root' to the layered filesystem... Kernel panic - not syncing: Attempted to kill init

So, from the above I 'think' it has something to do with that file that was (or should) have been made that holds the locale data. It did boot from the Compact Flash drive for it's first time after all.

I can boot from the DVD as I have done so again. I can also look into the contents of the Compact Flash drive (sda1). So, if there is anything I can do to edit a file then this should be possible. However, I did notice that all files were owned by root. Could this have any significance? If not then any suggestions on how to fix this are gratefully received :)

Thank you.

Kevan

Use the "puppy pfix=ram" boot cheat code to boot without the personal save file.

If me. I would boot the puppy cd though first as a live session and look at the cf card in gparted.
If it is full of yellow. Right click and pick umount if it is offered. Unmount it. Then pick check. Edit: even if not all yellow. It won't hurt to run a check on the drive.

Hit apply. Let it run.

If that does not fix the save file on that cf card. Then I would use the cheat code I suggested and delete my personal save file and start over.

If it works after that. Backup that sucker (persanl save file) to cd,usb, whatever.

That way if it corrupts again for whatever reason. You have a backup.

Hi 'rokytnji' and thank you for that suggestion. I shall go and give it a try and then report back with what happens...

'rokytnji' and others who read this.. I did as you suggested up to a point... I opened up Gparted, found the CF card/drive. It has about 1/6th used (yellow). I did try to unmount it (umount was not available as such so I tried the menu options). It would not allow me to unmount as it is of course using that localisation file that is stored on it. "Hmm, this could be problematical" I thought. So, I then tried another reboot. Once again I was asked if I wanted to save the changes to make a quicker boot next time. This I did. I also took the DVD out just to see what would happen. Would you believe it? It booted fine from that CF card. So, I can only imagine that it took along a file and renewed it on the CF card that allowed it to boot.

I do happen to have another 2gb CF card and adaptor. So, I shall be making a back up copy.

Thank you for helping.