Device () available / removed

[Sven Semmler]

Hi,

I just downloaded the latest updates (incl. dom0 updates)... shortly
after installing them I saw a notification "Device () available" twice
and then maybe 2-3 minutes later "Device () removed" twice.

Any idea what this was? ... is this connected to the update? How would I
investigate?

/Sven

--
public key: https://www.svensemmler.org/0x8F541FB6.asc
fingerprint: D7CA F2DB 658D 89BC 08D6 A7AA DA6E 167B 8F54 1FB6

[awokd]

Sven Semmler:

> Hi,
>
> I just downloaded the latest updates (incl. dom0 updates)... shortly
> after installing them I saw a notification "Device () available" twice
> and then maybe 2-3 minutes later "Device () removed" twice.
>
> Any idea what this was? ... is this connected to the update? How would I
> investigate?
>
> /Sven
>

Response might be too late, but was it updating dom0 or a template at
the time? Cross-reference dom0 or the template's journalctl device
messages with /var/log/dnf.log (or apt if it was a Debian template) to
find out what package was being updated when the device change happened,
then dig into details of that package to see what it would impact.

--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

[Sven Semmler]

On Fri, Mar 06, 2020 at 08:38:39PM +0000, 'awokd' via qubes-users wrote:
> > I just downloaded the latest updates (incl. dom0 updates)... shortly
> > after installing them I saw a notification "Device () available" twice
> > and then maybe 2-3 minutes later "Device () removed" twice.

> Response might be too late, but was it updating dom0 or a template at
> the time? Cross-reference dom0 or the template's journalctl device
> messages with /var/log/dnf.log (or apt if it was a Debian template) to
> find out what package was being updated when the device change happened,
> then dig into details of that package to see what it would impact.

Hi awokd,

I'm afraid my linux skills are not sufficient to explain this with
confidence. What I can see in the logs you pointed my to is:

-> major updates in dom0 including kernel, linux-firmware, salt
management stack

-> right around the time I've seen the notifications I see lots and lots
of dracut output aparently building a initramfs (seems to be a file
system image)

-> apparently at the same time I also had a VM with qubes-builder
running

-> Qubes memory management was busy reshuffleing RAM

-> the Qubes OS daemon was restarted

-> qubesd also reports: permission denied for call
b'admin.vm.device.block.Available'+b'' (b'dom0' -> b'disp213') with
payload of 0 bytes

I don't expect you or anyone else on this list to solve this for me, but
if the above gives you any ideas I'd be thankful to hear them.

[awokd]

Sven Semmler:

> -> apparently at the same time I also had a VM with qubes-builder
> running

That would do it. It frequently sets up loop devices while doing a
build, so you'd see those messages.

[Sven Semmler]

On Fri, Mar 06, 2020 at 11:01:56PM +0000, 'awokd' via qubes-users wrote:
> > -> apparently at the same time I also had a VM with qubes-builder
> > running
>
> That would do it. It frequently sets up loop devices while doing a
> build, so you'd see those messages.

:-) Thank you!