![](https://seccdn.libravatar.org/avatar/9435667f7160374bc34a8600b686aecd.jpg?s=120&d=mm&r=g)
06.09.2019 17:17, Ralph пишет:
Andrei, thanks for the response and excuse the delay. My replies inline below...
On Mon, 2 Sep 2019 20:53:08 +0300 Andrei Borzenkov
wrote: 02.09.2019 16:13, Ralph пишет:
[Leap 15.1, xfce, kernel 5.2.11-1.g6385110-default]
I have a machine with 2 nvme drives, 1 in the built-in motherboard m.2 slot (grub2 boots 15.1,"SX8200NP"), other in an m.2 slot on a pci-e expansion card (boots 15.0,"SX7000NP"). The dev names of the 2 nvmes seem to keep changing within the same boot. Here's an example from the logs
Show full logs from boot (journalctl -b).
Original journal under discussion is gone because apparently the default of a new 15.1 install is to not write journals to permanent storage. Bad idea, imho. Anyway, fixed now. Current log is at: https://paste.opensuse.org/9a901053 with same nvme device number problem as before. Note that journal is truncated at point of first user info as I log some file accesses and etc and I would need to edit it for privacy before posting beyond this point. If you need anything beyond this point in the journal, advise.
Unfortunately this does not really allows to identify nvme at various point in times. I'm still not sure what the actual problem is.
Note that yast2 info on the nvme devices is the same now as given below.
with the mb nvme first called nvme0 by the kernel, then nvme1 by btrfs, then nvme0 by both smart and btrfs. But the device according to yast is still nvme1. Confusing, to say the least. I need someone
Try showing output of lspci -nn ls -l /sys/block blkid nvme list nvme list-ns /dev/nvme0 nvme list-ns /dev/nvme1 -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org