BookWormPUP64 problems with disk mount locations sdx...

[LANdpLAN]

When BWPUP64 10.09.9 boots to sdb1 everything works.
It won't boot to sdc or sdd
To make it boot to sdb1 i have to disconnect all other drives so that it's only the drive in the computer on sda and the puppy usb on sdb

I'm also saving my photos to an external hard drive and I have directed Shotwell to keep files in sdc1 which is where it was mounted the first time. Sometimes when I plug the drive in it mounts to sdd1 and i have to reconfigure shotwell.

Also, when puppy is booted to sdb and I plug in my drive, puppy gets remounted to sdc1 and my USBShotwell drive goes to sdd.

Is there a way to make puppy work no matter where it is mounted and a way to point shotwell to the name of the drive instead of it's mount point?

[Geek3579]

I use the UUID of the drive where the frugal Puppy OS is located. You can get this from the Partition--> Information menu in GParted.
For simplicity, I assign this to a variable in the Grub2 grub.conf file -
eg: MYUUID=1c48a2d8-bdbb-4cf5-a620-e43c95e51a05

Then I use the value of this variable in the Grub boot code, for example, with a frugal Jammypup64 OS :
menuentry " Jammypup64" {
insmod ext2
search --no-floppy --fs-uuid --set $MYUUID
linux /Jammypup64/vmlinuz intel_pstate=disable net.ifnames=0 pmedia=usbflash pdrv=$MYUUID psubdir=/Jammypup64 pfix=fsck,fsckp TZ=AEST-10 nousbwait=5
initrd /Jammypup64/initrd.gz
}

There are other how-to-boot-puppyOS sites on the forum which provide more detail.

[bigpup]

Give us some information.

BookwormPup64 10.0.9 is installed on a USB stick?

How did you install it?
Give specific full details????

Are you ever accessing the computers bios boot device screen to select what device to boot from?

you need to do that if multiple different boot-able drives are plugged in.

It won't boot to sdc or sdd

What are these drives?
Are these drives that have a boot loader on them and some operating system to boot?

Are you booting to a working desktop of BookwormPup64.
Plugging in different drives or are they already plugged in when you boot?

[Trapster]

Maybe this will help:

https://oldforum.puppylinux.com/viewtopic.php?t=112558

[LANdpLAN]

I think I did frugal install BWPUP64 on a USB with uefi boot

sda is the internal disk with linux Mint legacy boot

The first boot I had to change the boot priority from legacy to uefi to get BWPUP. As long as I boot with the BWPUP usb plugged in, and nothing else, it always boots BWPUP. If I boot without BWPUP if boots Mint and then to reboot BWPUP I have to change the bios again.

When I talked about "won't boot to sdc or sdd" I meant that if I have other drives plugged in and they get accessed first at boot then they will be sdb and BWPUP will be sdc or sdd in which case it will not boot or if it does boot, some programs (I think the ones in the save file) will not run. It says i/o error. For example when I try to run shotwell.

Give us some information.

BookwormPup64 10.0.9 is installed on a USB stick?

How did you install it?
Give specific full details????

Are you ever accessing the computers bios boot device screen to select what device to boot from?

you need to do that if multiple different boot-able drives are plugged in.

It won't boot to sdc or sdd

What are these drives?
Are these drives that have a boot loader on them and some operating system to boot?

Are you booting to a working desktop of BookwormPup64.
Plugging in different drives or are they already plugged in when you boot?

[LANdpLAN]

I'm struggling to understand this. I'll have to think about it.

Maybe this will help:

https://oldforum.puppylinux.com/viewtopic.php?t=112558

[LANdpLAN]

16gig usb with BWPUP uuid=960B-D2AF

Where is the grub.conf file?

menuentry " BWpup64" {
insmod ext2
search --no-floppy --fs-uuid --set $960B-D2AF
linux /BWpup64/vmlinuz intel_pstate=disable net.ifnames=0 pmedia=usbflash pdrv=$960B-D2AF psubdir=/BWpup64 pfix=fsck,fsckp TZ=AEST-10 nousbwait=5
initrd /BWpup64/initrd.gz
}

Above is my attempt at putting in the correct substitutions from your code below. Do I delete/replace something in grub.conf with this or do I paste this into grub.com?

I use the UUID of the drive where the frugal Puppy OS is located. You can get this from the Partition--> Information menu in GParted.
For simplicity, I assign this to a variable in the Grub2 grub.conf file -
eg: MYUUID=1c48a2d8-bdbb-4cf5-a620-e43c95e51a05

Then I use the value of this variable in the Grub boot code, for example, with a frugal Jammypup64 OS :
menuentry " Jammypup64" {
insmod ext2
search --no-floppy --fs-uuid --set $MYUUID
linux /Jammypup64/vmlinuz intel_pstate=disable net.ifnames=0 pmedia=usbflash pdrv=$MYUUID psubdir=/Jammypup64 pfix=fsck,fsckp TZ=AEST-10 nousbwait=5
initrd /Jammypup64/initrd.gz
}

There are other how-to-boot-puppyOS sites on the forum which provide more detail.

[d-pupp]

@LANdpLAN Bookworm has a boot code that should help with your problem
psave=uuid
To find the uuid open a terminal and type

Code: Select all

lsblk -f

You can copy from the terminal by highlighting it with the mouse and paste it into you grub config by clicking the center mouse button (usually the wheel)

I am assuming you are using grub2 to boot so just add psave=uuid to your grub config at the end of the linux line. (Don't forget to add the comma ,psave=your-uuid )

DO NOT change you grub config other then that or may not be able to boot at all.

The problem you are having is because linux renames drive depending what else is plugged in first.
The uuid of a drive doesn't change even if the drive letter does.
BTW Bookworm may also have another boot code that you may have to use pupsfs=uuid

[Trapster]

Get rid of the $ signs in your grub.conf.

[bigpup]

The first boot I had to change the boot priority from legacy to uefi to get BWPUP. As long as I boot with the BWPUP usb plugged in, and nothing else, it always boots BWPUP. If I boot without BWPUP if boots Mint and then to reboot BWPUP I have to change the bios again.

That is normal operation of selecting a boot device for the bios to use.

If going into bios settings ->Boot ->device boot order setting.
It is only going to show devices hooked up, at the time you access the bios settings.
The order setting is use this device first, if not there use this one, if it is not there use this one.

But if you unplug and plug in drives. This setting is going to be wrong for what is now plugged in.

So you have to go back into the bios setup and correct it.

The bios is only going to see what is connected to the computer at the time you boot it.
Next time you boot, if not all the same drives are plugged into the computer.
The bios boot device order is wrong and it goes into what to choose that is there.
It always will eventually boot what is on the internal drive.
Usually with USB drives selected to first boot. If drive is not there it will default to the internal drive.

Most computers have a key you can press just as it gets power. (F9, F10, F11, etc... (depends on computer manufacture which one)
This will open a boot device selection screen showing all the bootable devices it sees connected to the computer.
Go down this list and select the one to boot.

[bigpup]

first boot I had to change the boot priority from legacy to uefi to get BWPUP.

That is because you only have a UEFI boot loader on the BookwormPup64 USB.

I think I did frugal install BWPUP64 on a USB with uefi boot

[LANdpLAN]

@LANdpLAN Bookworm has a boot code that should help with your problem
psave=uuid
To find the uuid open a terminal and type

Code: Select all

lsblk -f

You can copy from the terminal by highlighting it with the mouse and paste it into you grub config by clicking the center mouse button (usually the wheel)

I am assuming you are using grub2 to boot so just add psave=uuid to your grub config at the end of the linux line. (Don't forget to add the comma ,psave=your-uuid )

DO NOT change you grub config other then that or may not be able to boot at all.

The problem you are having is because linux renames drive depending what else is plugged in first.
The uuid of a drive doesn't change even if the drive letter does.
BTW Bookworm may also have another boot code that you may have to use pupsfs=uuid

Thanks, I found the uuid d3fee9d3-f23c-456b-9ce6-1a3e26f9d1d5 for my BWPUP USB.

my grub file config-6.1.119 is 259594 characters so I can not post it all here. I searched the file for "psave" and nothing was found.

Can you be more specific about what I need to change/add and where?

[d-pupp]

Thanks, I found the uuid d3fee9d3-f23c-456b-9ce6-1a3e26f9d1d5 for my BWPUP USB.

my grub file config-6.1.119 is 259594 characters so I can not post it all here. I searched the file for "psave" and nothing was found.

Can you be more specific about what I need to change/add and where?

@LANdpLAN If you are using grub2 find the line that starts with Linux and add to it.

Code: Select all

 pupsfs=d3fee9d3-f23c-456b-9ce6-1a3e26f9d1d5 psave=d3fee9d3-f23c-456b-9ce6-1a3e26f9d1d5

This should allow grub to find your boot files even if the usb key has a different drive designation.

[LANdpLAN]

I wanted to make puppy on an ext4 and the only method that worked was using grub4DOS

[LANdpLAN]

I can't remember exactly how I made my usb. I think I used the Frugal pup installer e4StickPup

I don't know where is grub.conf
I found grub.cfg.
it says:

Code: Select all

#
set default=0
set timeout=5

set menu_color_normal='yellow/blue'
set menu_color_highlight='black/cyan'

if [ $grub_platform = 'efi' ]; then
  if [ -n "$shim_lock" ]; then
    loadfont (memdisk)/fonts/unicode.pf2
  else
    loadfont /boot/grub/fonts/DejaVuSansMono18.pf2
  fi
  set gfxmode=auto
  terminal_output gfxterm
fi

menuentry "Puppy dpupbw64 10.0.9" {
  insmod ext2
  set bootid=bd9ac4ab-168e-413d-ae78-0ccd3633f4b5
  search --no-floppy --fs-uuid --set=root ${bootid}
  echo "Loading vmlinuz"
  linux /pups/dpupbw64/vmlinuz net.ifnames=0 pmedia=usbhd pdrv=lin99448a7c psubdir=/pups/dpupbw64 pfix=fsck,fsckp TZ=PST8PDT,M3.2.0,M11.1.0
  if [ -e /pups/dpupbw64/local-initrd.gz ]; then
    set local_rd=/pups/dpupbw64/local-initrd.gz
  else
    set local_rd=
  fi
  if [ -e /pups/dpupbw64/ucode.cpio ]; then
    set ucode_rd=/pups/dpupbw64/ucode.cpio
    echo "Loading ucode.cpio and initrd.gz"
  else
    set ucode_rd=
    echo "Loading initrd.gz"
  fi
  initrd ${ucode_rd} /pups/dpupbw64/initrd.gz ${local_rd}
}
if [ $grub_platform = 'efi' ]; then
  menuentry "System BIOS setup" {
    fwsetup
  }
fi
menuentry "Shutdown computer" {
  halt
}
menuentry "Reboot computer" {
  reboot
}

The uuid for my external hard drive with shotwell is ca89e3f4-b0db-4b17-8714-2ece9eee672a

[esos]

I wanted to make puppy on an ext4 and the only method that worked was using grub4DOS

grub4DOS works only for legacy-bios computer.
grub2 works on both computers(efi and legacy bios).

I found grub.cfg.
The uuid for my external hard drive with shotwell is ca89e3f4-b0db-4b17-8714-2ece9eee672a

Just type blkid in your terminal.
It will show all partition-id(s) you have.

[LANdpLAN]

I use the UUID of the drive where the frugal Puppy OS is located. You can get this from the Partition--> Information menu in GParted.
For simplicity, I assign this to a variable in the Grub2 grub.conf file -
eg: MYUUID=1c48a2d8-bdbb-4cf5-a620-e43c95e51a05

Then I use the value of this variable in the Grub boot code, for example, with a frugal Jammypup64 OS :
menuentry " Jammypup64" {
insmod ext2
search --no-floppy --fs-uuid --set $MYUUID
linux /Jammypup64/vmlinuz intel_pstate=disable net.ifnames=0 pmedia=usbflash pdrv=$MYUUID psubdir=/Jammypup64 pfix=fsck,fsckp TZ=AEST-10 nousbwait=5
initrd /Jammypup64/initrd.gz
}

There are other how-to-boot-puppyOS sites on the forum which provide more detail.

where in the Grub2 grub.conf file located?

[LANdpLAN]

Some questions I can't post to this old forum.

Maybe this will help:

https://oldforum.puppylinux.com/viewtopic.php?t=112558

run "mkrule" from the console in
/root/udev: "./mkrule /dev/sdX DeviceName" (where 'X' is the USB drive you wish to use, and "DeviceName"
is the friendly name you give the disk)

My attempt:

Code: Select all

# ./mkrule /dev/sdd Shotwell
bash: ./mkrule: No such file or directory
# 

[bigpup]

When BWPUP64 10.09.9 boots to sdb1 everything works.
It won't boot to sdc or sdd
To make it boot to sdb1 i have to disconnect all other drives so that it's only the drive in the computer on sda and the puppy usb on sdb

I'm also saving my photos to an external hard drive and I have directed Shotwell to keep files in sdc1 which is where it was mounted the first time. Sometimes when I plug the drive in it mounts to sdd1 and i have to reconfigure shotwell.

Also, when puppy is booted to sdb and I plug in my drive, puppy gets remounted to sdc1 and my USBShotwell drive goes to sdd.

Is there a way to make puppy work no matter where it is mounted and a way to point shotwell to the name of the drive instead of it's mount point?

I am going back to your first post and try to give you some useful help.

But to do it you have to provide good information on what exactly you are doing. Details, Details, Details????

So here goes!

I am going to assume you can get the Puppy USB stick install to boot to a working desktop, and it seems to be running OK.

To make it boot to sdb1 I have to disconnect all other drives so that it's only the drive in the computer on sda and the puppy usb on sdb

Drive identifications are given based on what drives are found connected to computer.
With one internal drive and a Puppy on a USB stick, no other drives.
The internal drive is sda
The Puppy USB stick is sdb.
Then it breaks down by partitions on the drive.
If a single partition is on each drive it would be sda1 and sdb1.
More partitions on the drive would be identified as 2, 3, 4, etc.....

If there are more drives connected to the computer.
How they are identified is determined by how the computers bios sees them.
The computers bios will usually look for internal connected drives first then find external connected ones, but the order it finds them can affect what they are identified as.
With several other internal or external drives connected.
The Puppy USB stick could be found as the 3rd, 4th, or 5th, etc... drive the bios finds connected.
So it could be identified as sdc1, sdd1, sde1, etc...............

when using Puppy to run the computer.
If you can keep all external drives connected to the same connection points.

The drive identifiers should stay to being the same between boots.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Do you know about boot device order setting in the computers bios?

This setting is the order the bios uses the drives to boot the computer. (the drive does have to have a boot loader on it to be seen as a boot device)

What the drive is called in the listing of boot devices could be anything based on what the bios sees it as.
You have to look at what is listed for devices and figure out what the internal drive is, the Puppy USB stick is, etc.........

This boot device order setting is what device is tried to boot from first, 2nd, 3rd, 4th, etc.........
If the Puppy USB stick is listed first, then it will try to boot from it first.
If not there try the 2nd in the list etc.............
If you can keep the Puppy USB stick connected in the same connection this device order setting should only need set one time to correct order to use.

If you unplug the Puppy USB stick and reconnect it to a different connection point.
Next time you boot, the bios may see it as a device in a different location and throws off the device order you had setup.
To boot from it you would need to correct the bios boot device order setting.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------

Also, when puppy is booted to sdb and I plug in my drive, puppy gets remounted to sdc1 and my USBShotwell drive goes to sdd.

This is when the computer is running from the Puppy USB stick and Puppy is in control of the computer?
You are not unplugging the Puppy USB stick while it is controlling the computer?

If yes.

This is not normal operation.

Maybe the computers connection controller is doing this. Maybe switching to a different controller.

Maybe have the Puppy USB stick plugged into a different USB connection point.
Boot the computer using this setup.

I need to know.

Is the Puppy save file/folder also located on the Puppy USB stick?

[esos]

@LANdpLAN
where in the Grub2 grub.conf file located?

If you installed Grub2, the file location is in /boot/grub/grub.cfg (by default) Not grub.conf.

[mikewalsh]

@LANdpLAN :-

Sounds to me as though what you need is "udev-rules". Jafadmin's wee mount-point utility worked brilliantly for me some years ago on the old Compaq Presario desktop rig, in the days before it eventually shuffled off its mortal coil.....

https://oldforum.puppylinux.com/viewtopic.php?t=112558

I was using a permanently plugged-in Seagate 'Expansion' USB 3.0 external hard drive at the time, and when experimenting with "suspend" discovered that Puppy WOULD insist on re-mounting the Seagate at the next mount-point up, i.e., sdb1 would become sdc1.....and then sdd1, sde1, sdf1, etc, through repeated suspend cycles. Which was no good at all if you were trying to script for stuff in a 'fixed' location!

(I don't have the issue with this HP Pavilion rig, as I ripped the guts out of the afore-mentioned external USB HDD, and it's now installed as a secondary internal 'data' drive via SATA cable direct to the mobo.)

=============================

This originally came as a collection of small files that needed to be manually put into the correct locations. I think jafadmin must have thrown the "ReadMe" file together in rather a hurry; it was a bit 'hacky', and didn't read all that smoothly.....so I edited the "ReadMe" file to make it more comprehensible, and assembled everything into a .pet package. One click, BANG! all installed, and ready to go.

I've attached the .pet below.

It places a text file called "README_Udev-Rules" in /root. Please read this BEFORE you do anything else, as it explains exactly what you need to do in order to create your "friendly", permanent mount-points(s). Apart from this, jafa's scripts still work as well as they ever did.

If you decide to give this a try, please let us know if it helps at all. I may have gotten hold of the wrong end of the stick here..!

Mike.

[dimkr]

A drive that disappears and re-appears can happen if voltage is too low and you have multiple USB devices connected at the same time. If this is the case, you should consider a powered USB hub.

[LANdpLAN]

Success! Thank you.

@LANdpLAN :-

Sounds to me as though what you need is "udev-rules". Jafadmin's wee mount-point utility worked brilliantly for me some years ago on the old Compaq Presario desktop rig, in the days before it eventually shuffled off its mortal coil.....

https://oldforum.puppylinux.com/viewtopic.php?t=112558

I was using a permanently plugged-in Seagate 'Expansion' USB 3.0 external hard drive at the time, and when experimenting with "suspend" discovered that Puppy WOULD insist on re-mounting the Seagate at the next mount-point up, i.e., sdb1 would become sdc1.....and then sdd1, sde1, sdf1, etc, through repeated suspend cycles. Which was no good at all if you were trying to script for stuff in a 'fixed' location!

(I don't have the issue with this HP Pavilion rig, as I ripped the guts out of the afore-mentioned external USB HDD, and it's now installed as a secondary internal 'data' drive via SATA cable direct to the mobo.)

=============================

This originally came as a collection of small files that needed to be manually put into the correct locations. I think jafadmin must have thrown the "ReadMe" file together in rather a hurry; it was a bit 'hacky', and didn't read all that smoothly.....so I edited the "ReadMe" file to make it more comprehensible, and assembled everything into a .pet package. One click, BANG! all installed, and ready to go.

I've attached the .pet below.

It places a text file called "README_Udev-Rules" in /root. Please read this BEFORE you do anything else, as it explains exactly what you need to do in order to create your "friendly", permanent mount-points(s). Apart from this, jafa's scripts still work as well as they ever did.

If you decide to give this a try, please let us know if it helps at all. I may have gotten hold of the wrong end of the stick here..!

Mike.