Search results

i have also come across this issue today - fresh install of pve 8.1 inside a VM - zfs rootfs (rpool) - added a single disk and put zfs on that via pve gui (name testzfs) - reboot getting several of these on reboot Feb 13 21:48:27 pve systemd[1]: Starting zfs-import-cache.service - Import ZFS...

now, that's really really weird Feb 13 14:28:52 proxmox zpool[1275]: cannot import 'rpool': a pool with that name already exists Feb 13 14:28:52 proxmox zpool[1275]: use the form 'zpool import <pool | id> <newpool>' to give it a new name Feb 13 14:28:52 proxmox systemd[1]...

i'm curious how the problem can continue to exist ,when you have set volmode=dev on zd48 and zd96 (corresponding) zvols , as zpool import won't find any pool then i assume that you probably did not set volmode=dev on both !?

i just wanted to write that a typical problem with zfs boot problems is name clash with existing pool names. i had that some times when attaching old root disk via usb and the system then could not decide which rpool to import and apparently, that's your problem: Feb 12 15:09:53 proxmox...

> Of course I can ;-) Which GPT bootsector we're talking about? The one of the PVE host, or the one of the Solaris VM? the solaris VM one

i have searched a little bit in kernel code. whith my limited knowledge, it appears to me that there is no way to disable gpt scanning on blockdevices. i wonder that we can disable partition scan/device node creation. maybe missing feature in linux kernel !?

you may also try to boot with rEFInd

as installing solaris 11 is not trivial when there is no iso for download anywhere - can you perhaps make your gpt bootsector available for download? i would like to try to reproduce https://realtechtalk.com/Linux_how_to_copy_GPT_partition_table_with_dd-1898-articles

i have openend a RFE for this at https://bugzilla.proxmox.com/show_bug.cgi?id=5236

> The reason I ask is you dropped a reference in comment 8 [1] of the kernel.org BZ to self, I suspect you meant to refer to another bug report? ouch, indeed. sorry. that should have been : https://bugzilla.proxmox.com/show_bug.cgi?id=4573

https://bugzilla.kernel.org/show_bug.cgi?id=99171 https://forum.proxmox.com/threads/zfs-on-debian-or-mdadm-softraid-stability-and-reliability-of-zfs.116871/#post-505697

that's weird, as proxmox shouldn't care for the contents of the zvols there is a volmode setting for zfs zvols, maybe worth a closer look ? volmode=default|full|geom|dev|none This property specifies how volumes should be exposed to the OS. Setting it to full exposes volumes as...

du bist mit der frage leider im falschen forum

when it's a routing problem, why does ping work ?

that it's different on one node is weird indeed. please double check if you're not observing wrong i showed you how to investigate, i.e. how to determine what's the current working directory of a process, so you can analyze this

what does ' time (cp /path/file /dest;sync) vs time (cp /path/file /dest;) tell ?

i think this is as side effect on how console/shell is spawned internally. i don't think this can be changed. why is this a problem for you ? to explain what you see - the parent process (in both cases) has it's homedir set to "/" and sub-processes are inheriting that, as long they don't...

wrong forum. not related to proxmox. please ask docker or ubuntu community. if this is in a lxc container, please use docker in a VM.

"Their licensing model is too simple. I don’t feel alive unless I am reading a hyper-inflated PhD level contract with the threat of a compliance audit being held like a gun to my head." made my day :D

ok. seems there is some caching implemented so when a compiled keymap is there, it won't be that bad. will only happen to be ineffective when invoked directly via setupcon -k , but not at boot time from systemd/init root@pve8:/etc/init.d# strace -f /lib/console-setup/keyboard-setup.sh...