Problem doing full install of Slacko 6.9.9.9

[LeithR]

I set out to update Slacko6.3.0 on a Sony Vaio laptop to Slacko 6.9.9.9. I had expected that the laptop would notice that I was upgrading as this had happened on another machine. However, everything seemed to go as expected and I carried out a full installation of 6.9.9.9. When I switched the machine on again I noted in the GRUB4dos screen that there were entries for both 6.3.0 and 6.9.9.9. When I selected 6.9.9.9 it started to load as normal then failed with a number of error messages.

At this point I decided to re-partition the HD, this operation went well so I reloaded the full version of 6.9.9.9 sda1. I'm now getting this response on screen, not sure what its telling me.



Would this have something to do with having details of the earlier installation of 6.9.9.9 in the MBR? Before each installation of 6.9.9.9 I have repartitioned the HD I thought to ensure that my previous installation was overwritten.

Where to next?

[LeithR]

Sorry the image didn't come out, what I'm seeing on screen is
4: ONE_PART=sda1
4: ONE_PART=sda3
4: ONE_PART=sda4
6: ONE_PART=sda4 ONE_TRY_FN=/PUPPY_SLACKO_6.9.9.9.sfs PDRV=
Dumping last lines of kernel log...
EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
*** sda4 /puppy_slacko_6.9.9.9.sfs not found
*** Error is too critical, dropping out to console
*** To save debug info to a partition, type 'debugsave'
/#

Hope this helps.

[rcrsn51]

If this truly is a full install, the boot sequence shouldn't be looking for an sfs file.

[LeithR]

The HD is partitioned as follows
sda1 68.36G ext4 flagged as boot
sda2 linux-swap 1.95G
sda3 195.31G ext4
sda4 200.14G ext4

The full implementation was carried out on sda1.

I too do not understand why its looking for the .sfs file.

[rcrsn51]

Then you need to look at your GRUB menu.lst.

Does it have an entry for a full install or frugal?

[bigpup]

Hope you are trying to use Grub4dos boot loader.
You did run Grub4dos bootloader config, after the install, to setup the boot loader for the new install?

I know ext 4 is suppose to be newer and better for a format.
I am not so sure, when changing the format, has fixed the issues.
I suggest using ext 3 format.

[LeithR]

Where will I find menu.lst please?

[LeithR]

I'm relooking at this problem from a diferent perspective. I've just removed the HD and reformatted on another linux machine then re-inserted the HD back into the Sony machine. I've installed 6.9.9.9 again and requested GRUB4dos. I've now got the file open and I find that I have 2 entries (lines 9 - 12 & lines 14 - 17) saying the same thing.

title Slacko Puppy 6.9.9.9 (sda1/boot
uuid 125ebf9e- lef4- 40cd- 9586- 00b5ed0e4fe5
kernel /boot/vmlinuz root=/dev/sda1 ro
initrd /boot/initrd.gz

Is this correct?

[rcrsn51]

A traditional full install does NOT have the line "initrd /boot/initrd.gz".

But I am not going to second-guess Slacko or Grub4Dos on this.

This would be far simpler if you did a frugal install with a save folder.

[mikeslr]

Just following up on bigpup's suggestion. If you want to know why look here: http://murga-linux.com/puppy/viewtopic. ... 170#973170. Skip down to this paragraph:

"But the biggest part of the problem, the fourth part, is that unlike almost every other operating system -- Windows, Macs, Linuxes -- Puppy is NOT designed to be run as a FULL INSTALL. It was not designed to require an entire Partition. The ability to run it as a FULL install was developed in order to speed-up its operation if you are deploying it on a computer with 256 Mbs of RAM or less."

and read the next couple of paragraphs. Including "There is nothing you can do with a Full install that you can't also do with a Frugal Install. And there are a great many things which a Frugal install can do which a Full install can't."

The part of the post after those paragraphs explains how to go from a working Full install to a working Frugal Install.

mikesLr

[Sailor Enceladus]

I'll try a full install of Slacko 6.9.9.9 when I get home, I'm curious what my menu.lst will look like compared to yours. I don't remember my uuid having spaces in it, or maybe I just used root (hd0,0). The last time I tried full install with woof-CE it worked and the non-fatal warnings I originally had were fixed.

http://www.murga-linux.com/puppy/viewto ... &start=255

The menu.lst example by jlst on the previous page (17) doesn't have the initrd line either though like rcrsn51 mentioned.

[LeithR]

A traditional full install does NOT have the line "initrd /boot/initrd.gz".

But I am not going to second-guess Slacko or Grub4Dos on this.

This would be far simpler if you did a frugal install with a save folder.

Thanks I'll try that tomorrow.

[Sailor Enceladus]

Ok, it worked. I booted into a frugal Slacko 6.9.9.9, made a new partition on hard drive with GParted as ext4 that was 23GB, sda4, then clicked on the Install icon on desktop, selected Universal Installer -> Internal Hard Drive -> sda -> selected sda4 -> picked Directory -> chose my vmlinuz (I think) and picked Full install, then it extracted all the files, the zdrv, adrv and fdv, then it asked if I wanted a initrd.gz RAM drive to start for sanity, I selected Yes, and I added the line it gave me into my menu.lst:

Code: Select all

title Puppy Linux - Slacko Puppy 6.9.9.9 full install in sda4
#root (hd0,0) <-- GRUB legacy, ex: (hd1,0)
uuid 7c0d7b9d-71ea-4307-bd5b-8ffda9126624
kernel /boot/vmlinuz fullinstall root=UUID=7c0d7b9d-71ea-4307-bd5b-8ffda9126624 pmedia=atahd 
#                                root=/dev/sda4
initrd /boot/initrd.gz

And it booted (with the initrd.gz option selected). Attached is a screenshot of my working sda4 (slacko 6.9.9.9 full install).

[LeithR]

Thanks all for your assistance,

Taking rcrsn51's advice I did a frugal install and all now working as it should.