GuixSD is missing /dev/disk/by-uuid

GuixSD is missing /dev/disk/by-uuid

[Chris Marusich]

Hi,

I've noticed that in GuixSD (version 0.9.0), the directory
/dev/disk/by-uuid is missing. Is that expected?

Because this directory is missing, cryptsetup cannot open a LUKS device
by UUID. For example, see the following:

--8<---------------cut here---------------start------------->8---
[0] marusich@garuda:~
$ sudo cryptsetup open --type luks UUID=c39bbc82-b70d-4e3d-a7dc-05f0b85dd84a backup
Device /dev/disk/by-uuid/c39bbc82-b70d-4e3d-a7dc-05f0b85dd84a doesn't exist or access denied.
[4] marusich@garuda:~
$ sudo cryptsetup open --type luks /dev/sdd1 backup
Enter passphrase for /dev/sdd1: 
[0] marusich@garuda:~
$ blkid
/dev/sdd1: UUID="c39bbc82-b70d-4e3d-a7dc-05f0b85dd84a" TYPE="crypto_LUKS" PARTUUID="00093e61-01"
[0] marusich@garuda:~
$ ls /dev/disk
by-id/
[0] marusich@garuda:~
$ ls /dev/disk/by-id/
dm-name-home  dm-uuid-CRYPT-LUKS1-2c7fc92e9e534bd08a178f15a89746bb-home
[0] marusich@garuda:~
$ 
--8<---------------cut here---------------end--------------->8---

As shown above, cryptsetup works fine if I specify /dev/sdd1, but it
would be nice to be able to specify the UUID instead. The
/dev/disk/by-id directory exists, but the purpose of that directory
appears to be different than the purpose of the /dev/disk/by-uuid
directory, and it does not contain an entry for the device in question.

Is it expected that GuixSD is missing the /dev/disk/by-uuid directory?

Thank you for your help,
Chris

Re: GuixSD is missing /dev/disk/by-uuid

[Ludovic Courtès]

Chris Marusich <cmmarusich@gmail.com> skribis:

> I've noticed that in GuixSD (version 0.9.0), the directory
> /dev/disk/by-uuid is missing. Is that expected?

It’s a bug that we noticed and fixed just recently, in commit 400ed6a.

You can get the fix by running, as root:

  guix pull
  guix system reconfigure your-config-file.scm

HTH!

Ludo’.

Re: GuixSD is missing /dev/disk/by-uuid

[Chris Marusich]

Hi,

I ran those commands, and it fixed the problem: /dev/disk/by-uuid now
exists and contains the links I expected to see.

However, it introduced a new problem. Now, my network interface eth0
does not show up like it did before. For example, when I run ifconfig,
"lo" shows up but "eth0" is missing. Nothing that relies on the network
works.

I've compared /var/log/messages before and after. Before the
reconfigure, it contained the following messages from "b44" (I think
this is my ethernet driver). This seems to show eth0 being successfully
set up:

--8<---------------cut here---------------start------------->8---
Feb 14 12:52:44 localhost vmunix: [    8.172311] b44: Broadcom 44xx/47xx 10/100 PCI ethernet driver version 2.0
Feb 14 12:52:44 localhost vmunix: [    8.192588] b44 ssb0:0 eth0: Broadcom 44xx/47xx 10/100 PCI ethernet driver 00:19:b9:7e:b4:cd
Feb 14 12:52:48 localhost vmunix: [   45.812218] b44 ssb0:0 eth0: Link is up at 100 Mbps, full duplex
Feb 14 12:52:48 localhost vmunix: [   45.812226] b44 ssb0:0 eth0: Flow control is off for TX and off for RX
Feb 14 12:52:48 localhost vmunix: [   55.223285] b44 ssb0:0 eth0: powering down PHY
Feb 14 12:52:48 localhost vmunix: [   55.252555] b44 ssb0:0 eth0: powering down PHY
Feb 14 12:52:52 localhost vmunix: [   61.812216] b44 ssb0:0 eth0: Link is up at 100 Mbps, full duplex
Feb 14 12:52:52 localhost vmunix: [   61.814593] b44 ssb0:0 eth0: Flow control is off for TX and off for RX
--8<---------------cut here---------------end--------------->8---

However, after the upgrade, I only see the following messages:

--8<---------------cut here---------------start------------->8---
Feb 14 12:12:16 localhost vmunix: [   10.820248] b44: Broadcom 44xx/47xx 10/100 PCI ethernet driver version 2.0
Feb 14 12:12:16 localhost vmunix: [   10.848595] b44 ssb0:0 eth0: Broadcom 44xx/47xx 10/100 PCI ethernet driver 00:19:b9:7e:b4:cd
--8<---------------cut here---------------end--------------->8---

I've checked messages, dmd.log, and shepherd.log in /var/log/, but I
can't figure out why networking isn't working. I found a similar problem
on the Guix bug tracker:

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=18483

However, I don't see messages like those in my logs, so I'm not sure
it's the same problem.

How can I proceed? My goal is to make networking work, like it did
before the reconfigure. I don't think I can use the new version of guix
until I get this networking problem fixed. Any advice would be
appreciated.

Thank you,
Chris

Re: GuixSD is missing /dev/disk/by-uuid

[Chris Marusich]

Chris Marusich <cmmarusich@gmail.com> writes:

> I ran those commands, and it fixed the problem: /dev/disk/by-uuid now
> exists and contains the links I expected to see.
>
> However, it introduced a new problem. Now, my network interface eth0
> does not show up like it did before. For example, when I run ifconfig,
> "lo" shows up but "eth0" is missing. Nothing that relies on the network
> works.
>

I think I'll start a new email threads to investigate this second issue,
which is decidedly separate from the /dev/disk/by-uuid problem. Thank
you, Ludo, for your help in resolving the original issue!

Chris