Re: Too many levels of symbolic links
Hi,
Le 21-01-2021, à 20:41:05 -0600, David Wright a écrit :
On Thu 21 Jan 2021 at 08:34:34 (+0100), steve wrote:
I have rebooted with udev_log=debug in /etc/udev/udev.conf. I see
Jan 21 08:15:28 box systemd-udevd[607]: sdc6: Failed to update device symlinks: Too many levels of symbolic links
Jan 21 08:15:28 box systemd-udevd[607]: sdc6: Preserve already existing symlink '/dev/disk/by-path/pci-0000:00:17.0-ata-2.0-part6' to '../../sdc6'
Jan 21 08:15:28 box systemd-udevd[607]: sdc6: Preserve already existing symlink '/dev/disk/by-partuuid/7acd2c90-b372-4bfb-a517-e14d2a17e342' to '../../sdc6'
Jan 21 08:15:28 box systemd-udevd[607]: sdc6: Preserve already existing symlink '/dev/disk/by-path/pci-0000:00:17.0-ata-2-part6' to '../../sdc6'
And the same for other partitions which are all part of a Raid1 array.
Other partitions are not impacted. So I guess this is related.
But I'm blocked now.
You said it's working, so that's a good thing. But I can't help
wondering whether there's some mistake in the way your raid is
configured—a part that perhaps aids monitoring it rather than
being essential to its assembly.
Not that it would help me at all (I haven't used raid), but
perhaps you could show how your raid is configured, for others
to cast an eye over. Experienced raiders might spot something.
cat /proc/mdstat
Personalities : [raid1] [linear] [multipath]
md1 : active raid1 sdg5[3] sdc5[5] sdd5[4]
117120896 blocks super 1.2 [3/3] [UUU]
md0 : active raid1 sdg1[3] sdc1[5] sdd1[4]
19514240 blocks super 1.2 [3/3] [UUU]
md2 : active raid1 sdg6[3] sdc6[5] sdd6[4]
97589120 blocks super 1.2 [3/3] [UUU]
unused devices: <none>
and
cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wildcards if desired.
#DEVICE partitions containers
# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# instruct the monitoring daemon where to send mail alerts
MAILADDR root
# definitions of existing MD arrays
ARRAY /dev/md/0 metadata=1.2 name=paros:0 UUID=9bb7d2a7:e96b5e9e:54c12ef1:4e8992fc
ARRAY /dev/md/1 metadata=1.2 name=paros:1 UUID=be24cc5a:5a29d2b8:10385878:4ae00056
ARRAY /dev/md/2 metadata=1.2 name=paros:2 UUID=78920a51:c8858cf6:a6027ee6:a016643e
I always archive the output of udevadm for my disks (actually
I just copy the /run/udev/data/b8\:* files).
I don't understand.
Thanks.
Reply to: