I am doing a cross install from my current Debian daedalus systm to a target disk /dev/nvme1n1.

I enter chroot, and create /etc/festab on the target. I use the UUIDs repored by # blkid for
the target disk,

Then I attemt to mount these partitions

/:# mount -a

Mount cann't find the UIIDs. For eample:

mount: /tmp: can't find UUID="0753d3bf-15eb-40a3-bdbd-bea054fc4f60".

What am I doint wrong?

--

Haines Brown

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, 21 Apr 2025 15:38:45 -0400
Haines Brown <haines@histomat.net> wrote:

I enter chroot, and create /etc/festab on the target. I use the UUIDs
repored by # blkid for the target disk,

Then I attemt to mount these partitions

/:# mount -a

Mount cann't find the UIIDs. For eample:

mount: /tmp: can't find UUID="0753d3bf-15eb-40a3-bdbd-bea054fc4f60".

What am I doint wrong?

Possibly misspelling the name of the file?

--
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon 21 Apr 2025 at 15:38:45 (-0400), Haines Brown wrote:

I am doing a cross install from my current Debian daedalus systm to a target disk /dev/nvme1n1.

I enter chroot, and create /etc/festab on the target. I use the UUIDs repored by # blkid for
the target disk,

Then I attemt to mount these partitions

/:# mount -a

Mount cann't find the UIIDs. For eample:

mount: /tmp: can't find UUID="0753d3bf-15eb-40a3-bdbd-bea054fc4f60".

What am I doint wrong?

Have you considered using LABELs? You can make them short and easy
to type. I give each disk a four-letter name, written on the case¹
in marker ink (eg kirk), and I PARTLABEL the partitions with names
like Kirk-……, and LABEL the filesystems kirk…….

The prefixes avoid name collisions, particularly if you want to use
meaningful names, like Kirk-swap and Kirk-home.

You then write PARTLABEL=whatever or LABEL=whatever in your fstab
file, instead of error-prone UUIDs.

¹ Not easy, I realise, when there's no case.

Cheers,
David.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, Apr 21, 2025 at 09:30:39PM -0500, David Wright wrote:

On Mon 21 Apr 2025 at 15:38:45 (-0400), Haines Brown wrote:

I am doing a cross install from my current Debian daedalus systm to a target disk /dev/nvme1n1.

I enter chroot, and create /etc/festab on the target. I use the UUIDs repored by # blkid for
the target disk,

Then I attemt to mount these partitions

/:# mount -a

Mount cann't find the UIIDs. For eample:

mount: /tmp: can't find UUID="0753d3bf-15eb-40a3-bdbd-bea054fc4f60".

What am I doint wrong?

Have you considered using LABELs? You can make them short and easy
to type. I give each disk a four-letter name, written on the case¹
in marker ink (eg kirk), and I PARTLABEL the partitions with names
like Kirk-……, and LABEL the filesystems kirk…….

The prefixes avoid name collisions, particularly if you want to use meaningful names, like Kirk-swap and Kirk-home.

You then write PARTLABEL=whatever or LABEL=whatever in your fstab
file, instead of error-prone UUIDs.

¹ Not easy, I realise, when there's no case.

While labels a possibllity, the UUIDs are copied and pasted from # blkid and so should be without error.

I did the chroot command again (while in chroot) nd it reported an error:

# LANG=C.UTF-8 chroot /mnt/debinst /bin/bash
chroot: cannot change root directory to '/mnt/debinst': No
such file or directory

$ ls /mnt | grep debinst
debinst

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, 21 Apr 2025, Haines Brown wrote:

I am doing a cross install from my current Debian daedalus systm to a target disk /dev/nvme1n1.

I enter chroot, and create /etc/festab on the target. I use the UUIDs repored by # blkid for
the target disk,

Then I attemt to mount these partitions

/:# mount -a

Mount cann't find the UIIDs. For eample:

mount: /tmp: can't find UUID="0753d3bf-15eb-40a3-bdbd-bea054fc4f60".

What am I doint wrong?

Probably need to bind mount /dev, /sys and /proc in the chroot.

Tim.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

On Tue, Apr 22, 2025 at 06:23:05AM -0400, Haines Brown wrote:

the UUIDs are copied and pasted from # blkid and so should be without
error.

Can you show us the output of blkid?

I did the chroot command again (while in chroot) nd it reported an error:

chroot from inside a chroot is obviously not going to work if the target directory doesn't exist inside the upper chroot.

# LANG=C.UTF-8 chroot /mnt/debinst /bin/bash
chroot: cannot change root directory to '/mnt/debinst': No
such file or directory

$ ls /mnt | grep debinst
debinst

One of these was done as root, the other not (# vs $ prompts). Are they actually from the same shell session or are you saying you did a chroot
and then tried to do the same chroot again and then when that failed
exited out and proved to us that your /mnt/debinst does exist?

If the latter than this is not very interesting as we would expect that
to exist for your first chroot to work, and we would not expect the
second chroot to work. After all, you probably do not have a directory structure like /mnt/debinst/mnt/debinst, right?

After showing us the output of blkid from outside the chroot I suggest
that you paste a full session of you:

- bind mounting relevant directories into your chroot
- entering that chroot
- showing content of etc/fstab from inside chroot
- proving that block devices exist by UUID by showing content of
/dev/block/by-uuid/ from inside chroot.

So far we have only have drip drip drip of little information and some
of that not relevant.

Also Debian Daedalus is not a Debian release code name so you are
probably running something else like Devuan, and should really seek
support at their support venues.

Thanks,
Andy

--
https://bitfolk.com/ -- No-nonsense VPS hosting

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)