Ja sicher. Du trägst das Medium in die fstab ein und setzt für diesen Eintrag die Option 'noauto'. Das Medium wird erst gemountet, wenn der Backupjob loslaufen soll. Ich nehme mal an, dass Du das wie ich mit Festplatten in einer Dockingstation machen möchtest. Ich nehme weiterhin an, dass Du die...
May it be possible to somehow slightly level up the priority of this task at the TODO? I'm facing the same problem: Created a NFS Storage at the host to use it as VitIO SCSI inside a VM (differential backups of windows servers needs dedicated volumes - impossible with NFS). These NFS Storage...
... and to add another device to one of the PCI-X Slots, it's possible, the numbering changes - breaking 'persistant' naming again.
Replacing an Intel with something else (Maybe Broadcom) would fall back to the "slot path", breaking 'persistant' naming. The idea is, to have names for network...
Can you please look for /etc/udev/rules.d/70-persistent-net.rules in stretch? As far as I understand, this file does the same like the .link-files of systemd but reporting the resulting names to systemd as kernel - names.
Proxmox 6 (Buster) have no such a file.
The rules at /lib/udev/rules.d...
Digging deeper, collecting knowledge, getting upset ...
It seems there is a combination of changes in Debian (namely udev) and Systemd and maybe the PVE custom kernel. All this is only visible if there are notwork cards like the Intels installed.
Your list of changes in 99-default.link gives a...
Debian can't imagine, there are more than one MAC per Port ... these Intels do exactly this. It seems like Intel simply put two network adaptors on one PCI-X Card, each of them got two network ports. The following is the view to such a device from ILO4. Formerly all the port had a name...
https://forum.proxmox.com/threads/4-15-based-test-kernel-for-pve-5-x-available.42097/page-4#post-208348
provided the information, it's a bug in kernel, fixed in 4.15.0-19.20 ... so maybe there will be an other kernel-update soon.
https://forum.proxmox.com/threads/4-15-based-test-kernel-for-pve-5-x-available.42097/page-4
Someone seems to running mad ... They choose to set the new default kernel to 4.15.15.1
They say "having a kernel that never shows any issues on all possible hardware is an illusion" ... because there...
Me too, HP ML350p G8 with P420i.
This happens with both of the two machines I'm running.
The screen looks exactly like the one attached by timota to #62.
Additionally, the first message after power on was
error parsing pcc subspaces from pcct
Couldn't get size: [...]
reading all physical...
Just to confirm: you are not the only one. I got the exact same behavior at two identical machines ... including the successful boot to the previous kernel.
These are Proliant ML350p G8 equipped with two E5-2680 v2 and the onboard Smart Array P420i (Firmware 8.32; 2G Cache installed; 6...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.