Re: Unable to Access a Foreign Volume Group

2019-01-14 Thread Jens Holzhäuser
On Sun, Jan 13, 2019 at 05:39:20PM +0100, Martin wrote: > Hi Jens, > > my first shot would be setting the actual system id to > 'zaphod1105820973' like described in the lvmsystemid man page. I'm not > sure, how this uname or lvmlocal work, so I would try setting > system_id_source to machineid or

Re: Unable to Access a Foreign Volume Group

2019-01-13 Thread Martin
Hi Jens, my first shot would be setting the actual system id to 'zaphod1105820973' like described in the lvmsystemid man page. I'm not sure, how this uname or lvmlocal work, so I would try setting system_id_source to machineid or file. First, look if /etc/machine-id matches. If not, put is may b

Unable to Access a Foreign Volume Group

2019-01-13 Thread Jens Holzhäuser
Hello, I have a buster/sid system with two volume groups that have made no issue for years. vg00 has not been actively used for a longer time, I migrated off of it, but keep it up and around. vg01 is holding most of the data for the system and works with no issues. Both are on two separate raid1'