Boot critical Error after modifying grub (Bionicpup3) [Solved]

[pupco]

here config part of my grub.cfg for my multiboot installation ( without details ) ; I do not install grub from puppy as nothing was working in that case ( my ohers linux & windows xp not found )
Then I have modified my grub file as per some postsans according my expereince , and the system start but stop on a such error :
"sda6 / puppy_upupbb_19.03.sfs , error too critical , dropping out to console"
I dont understand as this file 'puppy_upupbb_19.03.sfs' exist in 'upupbb19.03frugal' folder ?

Code: Select all

### BEGIN PUPPY
menuentry "Puppy Bionic (sda6)" {
  search --no-floppy --fs-uuid --set=root UUID of partition
  linux /upupbb19.03frugal/vmlinuz
  initrd /upupbb19.03frugal/initrd.gz 
}
### END PUPPY

Waiting for suggestions / corrections

[mikeslr]

@pupco, to the Forum. Please read viewtopic.php?p=816#p816 before editing your request for help. There are over 6,000 Puppys, only google knows how many combinations of hardware exist as personal computers, and --this being Linux-- usually a half dozen ways to do anything. Only my late Mother could read minds. As for the rest of us, one of bigpup's parting adages in the above referenced post always read true:
"The things you do not tell us, are usually the clue to fixing the problem."

@moderators, please move this post to the 'Beginners' Section. This Section is for providing Tips and Instructions, not asking for them.

[williwaw]

pupco,
your boot stanza would actually like the UUID of partition in the numerical format.
it can be found by running the command blkid

[HerrBert]

pupco,
your boot stanza would actually like the UUID of partition in the numerical format.
it can be found by running the command blkid

I don't know much about grub2, but at first sight i'm also missing a psubdir=upupbb19.03frugal on the linux/kernel command line...
Am i wrong with this

[d-pupp]

linux /upupbb19.03frugal/vmlinuz
initrd /upupbb19.03frugal/initrd.gz

I think this needs to be changed to your path on your system

[Geek3579]

Here is an example of the typical boot config I use where the frugal files are located in a folder LX_Bionicpup64(2),
the time zone is for QLD, Australia,
and the UUID for an ext4 partition is 1c48a2d8-bdbb-4cf5-a620-e43c95e51a05.

menuentry "LX_Bionicpup64(2)" {
search --no-floppy --fs-uuid --set 1c48a2d8-bdbb-4cf5-a620-e43c95e51a05
linux /LX_Bionicpup64(2)/vmlinuz pmedia=usbflash pdrv=1c48a2d8-bdbb-4cf5-a620-e43c95e51a05 psubdir=/LX_Bionicpup64(2) pfix=fsck,fsckp TZ=AEST-10
initrd /LX_Bionicpup64(2)/initrd.gz
}

For simplicity one could instead do this:
menuentry "LX_Bionicpup64(2)" {
MYUUID=1c48a2d8-bdbb-4cf5-a620-e43c95e51a05
search --no-floppy --fs-uuid --set $MYUUID
linux /LX_Bionicpup64(2)/vmlinuz pmedia=usbflash pdrv=$MYUUID psubdir=/LX_Bionicpup64(2) pfix=fsck,fsckp TZ=AEST-10
initrd /LX_Bionicpup64(2)/initrd.gz
}

[pupco]

please note :
1)in the extract of my grub file : of course it's the nber proper of uuid which is in the file and the boot operates (up to the error)
2)my grub file is compliant with all posts and subfolder are well indicated such : linux /upupbb19.03frugal/vmlinuz
and initrd /upupbb19.03frugal/initrd.gz ( except there are no options but ? )
3) the two lines calling linux & initrd are OK as the boot operates up to the file "puppy_upupbb_19.03.sfs" noted as " not found " ( but it's in the subfolder upupbb19.03frugal ); have anyone an idea of this file purpose?
this file has been generated during the exit whan I select "save" ,I suppose?
here attached a picture of my boot screen

[bigpup]

file "puppy_upupbb_19.03.sfs" noted as " not found " ( but it's in the subfolder upupbb19.03frugal ); have anyone an idea of this file purpose?

That is the main SFS file that has most of the operating system(OS) in it.

That file has to load for the OS to even run.

The Grub entry you posted in the beginning has no UUID number in it for the UUID of the partition the install is on.

It needs to have this information in the entry.

The UUID is a specific identifying number that is only for that specific partition.

As this example entry that was shown to you.

Code: Select all

menuentry "LX_Bionicpup64(2)" {
search --no-floppy --fs-uuid --set 1c48a2d8-bdbb-4cf5-a620-e43c95e51a05
linux /LX_Bionicpup64(2)/vmlinuz pmedia=usbflash pdrv=1c48a2d8-bdbb-4cf5-a620-e43c95e51a05 psubdir=/LX_Bionicpup64(2) pfix=fsck,fsckp TZ=AEST-10
initrd /LX_Bionicpup64(2)/initrd.gz

Those added commands are used by the boot process to help it find stuff to use, load, and also what type running setup to have, for using the save.
So you need to have a pdrv= with the partition UUID number, a psubdir=, and pfix=fsck,fsckp TZ=AEST-10 on the linux line.

Use the info given in earlier posts about how to find the exact UUID number for the partition the install is on.
It is not going to be the number in this example entry.

[pupco]

hello
the solution is : I added psubdir , pdrv & pfix options and the boot is OK now
thanks to all attendants
here the line modified

Code: Select all

linux /upupbb19.03frugal/vmlinuz [b] psubdir=/upupbb19.03frugal  pdrv=$uuid  pfix=fsck,fskp[/b]

[bigpup]

What is the complete entry that is now working?

You seem to be using some commands in ways I have never seen.

The complete entry, may be helpful for others to see, as a good example of what works.

[pupco]

Here the entire grub.cfg

Code: Select all

menuentry "..Puppy Bionic sur sda6" {
insmod part_msdos
buid=c9ba1c98-c611-4dae-ae77-daac7850b6a8
set root='hd0,msdos6'
echo "root:" $root
insmod ext2
#search --no-floppy --fs-uuid --set c9ba1c98-c611-4dae-ae77-daac7850b6a8
search --no-floppy --fs-uuid --set $buid
linux /upupbb19.03frugal/vmlinuz psubdir=/upupbb19.03frugal pdrv=$buid pfix=fsck,fskp
initrd /upupbb19.03frugal/initrd.gz
}