drive name change sdb3>sde3, cant boot to puppy now

[deepforest]

Puppy installed at hdd - /dev/sde3
Before, when hdd name was - /dev/sdb3 all worked good.

Code: Select all

root@devuan:/home/freeartist-devuan# lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
fd0      2:0    1     4K  0 disk 
sda      8:0    0 186.3G  0 disk 
├─sda1   8:1    0  10.5G  0 part 
├─sda2   8:2    0     1K  0 part 
├─sda5   8:5    0  29.3G  0 part 
├─sda6   8:6    0  48.8G  0 part 
├─sda7   8:7    0  48.8G  0 part 
└─sda8   8:8    0  48.8G  0 part 
sdb      8:16   0   149G  0 disk 
├─sdb1   8:17   0  70.3G  0 part 
├─sdb2   8:18   0     4G  0 part 
└─sdb3   8:19   0  74.7G  0 part 
sdc      8:32   0 223.6G  0 disk 
├─sdc1   8:33   0  72.3G  0 part /
├─sdc2   8:34   0  72.3G  0 part 
├─sdc3   8:35   0    75G  0 part 
├─sdc4   8:36   0     1K  0 part 
└─sdc5   8:37   0     4G  0 part [SWAP]
sdd      8:48   0 149.1G  0 disk 
├─sdd1   8:49   0  70.3G  0 part 
├─sdd2   8:50   0   4.5G  0 part 
├─sdd3   8:51   0    50M  0 part 
└─sdd4   8:52   0  74.2G  0 part 
sde      8:64   0 931.5G  0 disk 
├─sde1   8:65   0  75.7G  0 part 
├─sde2   8:66   0     4G  0 part 
├─sde3   8:67   0 345.7G  0 part /home
├─sde4   8:68   0     1K  0 part 
└─sde5   8:69   0 506.1G  0 part 
sr0     11:0    1  1024M  0 rom  

Code: Select all

root@devuan:/home/freeartist-devuan# blkid
/dev/sdd2: UUID="b6b16d67-2aab-43c1-bfc4-d948e4a270b5" TYPE="swap" PARTUUID="6296eae2-02"
/dev/sdd3: LABEL="System Reserved" BLOCK_SIZE="512" UUID="A0D6B4C7D6B49ECA" TYPE="ntfs" PARTUUID="6296eae2-03"
/dev/sdd1: LABEL="NEW4" BLOCK_SIZE="512" UUID="4E9E2ABD9E2A9E09" TYPE="ntfs" PARTUUID="6296eae2-01"
/dev/sdd4: LABEL="NEW_10" BLOCK_SIZE="512" UUID="A414D1AC14D1822A" TYPE="ntfs" PARTUUID="6296eae2-04"
/dev/sdb2: UUID="a5633ead-0ebc-4f5b-b0fd-cd036aeb94f6" TYPE="swap" PARTUUID="0002426d-02"
/dev/sdb3: UUID="c266328b-3853-45d6-b1e5-5e795370f40e" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="0002426d-03"
/dev/sdb1: UUID="86bd6cdd-1f9b-4b57-942e-c7ebbf42c0e4" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="0002426d-01"
/dev/sde2: UUID="34d1ae4c-5d37-4bb7-bdd4-ae5a95060504" TYPE="swap" PARTUUID="907085ae-02"
/dev/sde5: LABEL="NEW5" BLOCK_SIZE="512" UUID="3232708532704FB9" TYPE="ntfs" PARTUUID="907085ae-05"
/dev/sde3: UUID="24c316e7-38e1-4db4-a0aa-ade09eea7782" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="907085ae-03"
/dev/sde1: UUID="5720e815-c048-427f-b2f8-c5bd6d68665b" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="907085ae-01"
/dev/sdc2: UUID="e4470a2b-7a42-4eee-9051-2f0ce31da08c" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="1f909dee-02"
/dev/sdc5: UUID="207cec6a-4917-4837-ae55-8c96f473d2f4" TYPE="swap" PARTUUID="1f909dee-05"
/dev/sdc3: LABEL="10" BLOCK_SIZE="512" UUID="B842FF8142FF42A4" TYPE="ntfs" PARTUUID="1f909dee-03"
/dev/sdc1: UUID="db80be11-947e-4bc9-9eb0-278894b401a4" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="1f909dee-01"
/dev/sda7: LABEL="NEW_7" BLOCK_SIZE="512" UUID="0EAC29DEAC29C157" TYPE="ntfs" PARTUUID="3dd23dd1-07"
/dev/sda5: LABEL="NEW1" BLOCK_SIZE="512" UUID="E498D01C98CFEADE" TYPE="ntfs" PARTUUID="3dd23dd1-05"
/dev/sda1: LABEL="M-PM-^]M-PM->M-PM-2M-QM-^KM-PM-9 M-QM-^BM-PM->M-PM-<" BLOCK_SIZE="512" UUID="064C49404C492BAD" TYPE="ntfs" PARTUUID="3dd23dd1-01"
/dev/sda8: LABEL="NEW3" BLOCK_SIZE="512" UUID="B8E45713E456D2EC" TYPE="ntfs" PARTUUID="3dd23dd1-08"
/dev/sda6: LABEL="NEW2" BLOCK_SIZE="512" UUID="E8802A87802A5C76" TYPE="ntfs" PARTUUID="3dd23dd1-06"
root@devuan:/home/freeartist-devuan# 

[rockedge]

@deepforest

I've seen from time to time that the USB drive name will change dependent on where it's plugged in.

How was this Puppy Linux installed? And you are sure it is on the correct partition?

Might be able to fix this by editing the boot stanza to use the partition UUID like:
/mnt/sde3 is UUID=24c316e7-38e1-4db4-a0aa-ade09eea7782

Using the UUID will eliminate the problem of the drive/partition changing it's mount point like /mnt/sba3 changing to mnt/sde3. The UUID will always remain the same.

[bigpup]

I assume HDD is indicating the install is on a partition on a internal drive.

You did try to boot from a completely powered off and powered on condition?
This was not a reboot.

[Jafadmin]

'sdX' type drive designations are transitory. They are re-provisioned every time you boot the machine. There is NO guarantee they will stay consistent between boots.

It is ALWAYS recommended to use UUID's instead of 'sdX' designators. UUID's WILL remain consistent between boots. They will remain consistent between machines.

The problem you are experiencing is exactly why UUID booting was created.

[fredx181]

Besides UUID's, IF the partition has a label, then using LABEL=... is fine also.