[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: remove me from this list



Dear Bryant,

If you have subscribed to this list in error (or somebody else has subscribed
you as a prank or whatever) -
You need to send a mail to 

debian-user-REQUEST@lists.debian.org

with the subject

unsubscribe

Note the -REQUEST part of the list address is crucial: the mailing list software will then picl this up. 
This needs to be from the same account that's getting mail from the list.

Note: We will not normally be able to remove all trace of you from the list: 
the lists are archived in various locations around the 'Net so "please remove my name" 
will be ineffective and may be counter-productive.

With every good wish,

Andy Cater

On Fri, Jan 22, 2021 at 08:02:29AM -0500, J B Martin wrote:
> I do not use this product.
> 
> Please remove my name.
> 
> Thank you.
> 
> Bryant Martin
> 
> On 1/22/2021 7:59 AM, Andrei POPESCU wrote:
> > On Vi, 22 ian 21, 08:08:57, steve wrote:
> > > Le 21-01-2021, à 09:45:18 +0200, Andrei POPESCU a écrit :
> > > 
> > > > On Jo, 21 ian 21, 08:34:34, 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.
> > > > Could you inspect the /dev directory from a live image or similar (i.e.
> > > > with the affected system not running)?
> > > Yes I can do that. What should I look for?
> > I'm guessing it should be empty ;)
> > 
> > At least in buster /dev is a 'devtmpfs' mounted over /dev (is this the
> > same for you?).
> > > > Do you have any custom udev rules or any other custom scripts, services,
> > > > etc. plugged into the early startup?
> > > Don't know:
> > > 
> > > tree /etc/udev
> > > /etc/udev
> > > ├── hwdb.d
> > > ├── rules.d
> > > │   ├── 51-android.rules
> > > │   ├── 55-Argyll.rules
> > > │   ├── 69-libmtp.rules
> > > │   ├── 70-persistent-cd.rules
> > > │   └── 70-persistent-net.rules.old
> > > └── udev.conf
> > Maybe the output of 'udevadm test /sys/block/sdc/sdc6' can provide some
> > interesting information, as well as 'ls -l /dev/disk/by-*', otherwise
> > I'm out of ideas.
> > 
> > Kind regards,
> > Andrei
> 
> -- 
> Joseph Bryant Martin
> USA 804 223-0325
> Info Voice
> 804 334-4309
> 


Reply to: