I have a more current version of Dracut but still having issues. I expanded
the volume (got the BCACHE messages), ran "dracut -f" and rebooted and got a
disabled wait. From the other server here are some of the messages from the
rdsosreport file.
+ cat /lib/dracut/dracut-044-10.21.1
dracut-044-10.21.1
+ command -v lvm
+ lvm pvdisplay
Read-only locking type set. Write locks are prohibited.
Recovery of volume group "system-vg" failed.
Cannot process volume group system-vg
Read-only locking type set. Write locks are prohibited.
Recovery of standalone physical volumes failed.
Cannot process standalone physical volumes
+ lvm vgdisplay
Read-only locking type set. Write locks are prohibited.
Recovery of volume group "system-vg" failed.
Cannot process volume group system-vg
+ lvm lvdisplay
Read-only locking type set. Write locks are prohibited.
Recovery of volume group "system-vg" failed.
Cannot process volume group system-vg
+ command -v dmsetup
+ dmsetup ls --tree
No devices found
+ cat /proc/mdstat
cat: /proc/mdstat: No such file or directory
+ command -v ip
+ command -v journalctl
+ journalctl -ab --no-pager -o short-monotonic
[ 7.037687] nbxdv0392 kernel: sd 1:0:1:1074675735: [sdh] Attached SCSI disk
[ 7.103887] nbxdv0392 dracut-initqueue[358]: Scanning devices dasda2 dasdd1
sda1 sdb1 sdc1 sdd1 for LVM logical volumes system-vg/usr-lv
[ 7.151664] nbxdv0392 dracut-initqueue[358]: Read-only locking type set.
Write locks are prohibited.
[ 7.151770] nbxdv0392 dracut-initqueue[358]: Recovery of volume group
"system-vg" failed.
[ 7.151868] nbxdv0392 dracut-initqueue[358]: Cannot process volume group
system-vg
[ 7.314522] nbxdv0392 dracut-initqueue[358]: Read-only locking type set.
Write locks are prohibited.
[ 7.314639] nbxdv0392 dracut-initqueue[358]: Recovery of volume group
"system-vg" failed.
[ 7.314737] nbxdv0392 dracut-initqueue[358]: Cannot process volume group
system-vg
[ 8.096638] nbxdv0392 dracut-initqueue[358]: Scanning devices dasda2 dasdd1
sda1 sdb1 sdc1 sdd1 sde1 sdf1 sdg1 sdh1 for LVM logical volumes
system-vg/usr-lv
[ 8.115314] nbxdv0392 dracut-initqueue[358]: Read-only locking type set.
Write locks are prohibited.
[ 8.115462] nbxdv0392 dracut-initqueue[358]: Recovery of volume group
"system-vg" failed.
[ 8.115631] nbxdv0392 dracut-initqueue[358]: Cannot process volume group
system-vg
[ 8.229860] nbxdv0392 dracut-initqueue[358]: Read-only locking type set.
Write locks are prohibited.
[ 8.230011] nbxdv0392 dracut-initqueue[358]: Recovery of volume group
"system-vg" failed.
[ 8.230129] nbxdv0392 dracut-initqueue[358]: Cannot process volume group
system-vg
[ 147.100038] nbxdv0392 dracut-initqueue[358]: Warning: dracut-initqueue
timeout - starting timeout scripts
[ 147.136616] nbxdv0392 dracut-initqueue[358]: Scanning devices dasda2 dasdd1
sda1 sdb1 sdc1 sdd1 sde1 sdf1 sdg1 sdh1 for LVM logical volumes
system-vg/usr-lv
[ 147.182501] nbxdv0392 dracut-initqueue[358]: Read-only locking type set.
Write locks are prohibited.
[ 147.182674] nbxdv0392 dracut-initqueue[358]: Recovery of volume group
"system-vg" failed.
[ 147.182834] nbxdv0392 dracut-initqueue[358]: Cannot process volume group
system-vg
[ 147.495921] nbxdv0392 dracut-initqueue[358]: PARTIAL MODE. Incomplete
logical volumes will be processed.
[ 147.514583] nbxdv0392 dracut-initqueue[358]: Read-only locking type set.
Write locks are prohibited.
[ 147.514703] nbxdv0392 dracut-initqueue[358]: Recovery of volume group
"system-vg" failed.
[ 147.514797] nbxdv0392 dracut-initqueue[358]: Cannot process volume group
system-vg
[ 148.261379] nbxdv0392 dracut-initqueue[358]: Warning: dracut-initqueue
timeout - starting timeout scripts
Chris Will
Enterprise Linux/UNIX (ELU)
(313) 549-9729 Cell
cw...@bcbsm.com
-----Original Message-----
From: Linux on 390 Port <LINUX-390@VM.MARIST.EDU> On Behalf Of marcy cortes
Sent: Tuesday, April 21, 2020 5:57 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: BCACHE errors on lvextend, on reboot goes to dracut emergency mode
[External email]
Yes, we had this in two forms. Both fixed by the dracut fix (and
rerunning it)
Subject: SR101238520451 Re dracut timeout problems after
patching
Marcy,
We released this fix in maint
(dracut-044.2-10.15.2.s390x). The other issue related to this:
SR101237346921 Re: SLES Sp4 problem with lvm
and device names
On Tue, Apr 21, 2020 at 10:26 AM Mark Post <mp...@suse.com> wrote:
> On 4/21/20 12:11 PM, Will, Chris wrote:
> > Has anyone run into something like this? I would like to fix this
> proactively and not wait until the server dies and I have to go into
> emergency mode. This could be an issue with all our servers.
>
>
> Hi, Chris,
>
> I really thing the BCACHE messages are a red herring. I'm not at all
> sure what the real cause of the problem is, but I don't think it's that.
>
> Have you opened a problem with your support provider? I think a lot
> more information is going to be needed to help you with this.
>
> As far as being proactive, there are a number of things you can try. I
> don't know that any of them will actually prevent the problem, since
> we don't really know what's causing it. The "Inconsistent metadata
> found for VG system-vg - updating to use version 8 n 8" message is the
> most interesting data point from what I can tell.
>
> If you possibly can, I would try to clone the DASD volume(s) that make
> up one of your other existing SLES12 SP4 systems, and see if you can
> recreate the problem. If so, then re-clone the volume(s), and try
> doing something like this:
> pvscan
> vgscan
> pvck /dev/dasd?? (for each physical volume) lvscan
>
> Then try extending a logical volume again and see if the problem
> reoccurs or not. This is very much stabbing in the dark, but it might
> provide some relief.
>
>
> Mark Post
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions, send
> email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www2.marist.edu/htbin/wlvindex?LINUX-390
>
--
Marcy
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send email to
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390
The information contained in this communication is highly confidential and is
intended solely for the use of the individual(s) to whom this communication is
directed. If you are not the intended recipient, you are hereby notified that
any viewing, copying, disclosure or distribution of this information is
prohibited. Please notify the sender, by electronic mail or telephone, of any
unintended receipt and delete the original message without making any copies.
Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are
nonprofit corporations and independent licensees of the Blue Cross and Blue
Shield Association.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390
