Search results

https://forum.proxmox.com/threads/proxmox-7-0-failed-to-prepare-efi.95466/

make sure that only the node that actually has this store is in this box: also, you need a third node or qdevice in your cluster or you can have issues if any node is down.

pvesm remove SATAPool out of curiosity- why do you keep bringing up the other node? are they clustered? if clustered, dont delete the store; you need to go to datacenter-storage and make sure you EXCLUDE the node that doesnt have that pool in it from the store definition or unmark shared.

delete the store.

lets only discuss the node in question, since the other one is working. I assume that the end result here is a zpool named saspool? if so, zpool create SASPool [raidtype] [device list] If something else, please note what your desired end result is.

I am completely confused. If the drives that host saspool are NOT PRESENT, then its a foregone conclusion that a defined store looking for the filesystem is going to error... what are you asking? lets start over. do you have the drives plugged in, and can you see them in lsblk?

dont worry about attaching/detaching it. simply remove and replace it. edit- DONT PULL IT YET. there's a resilver in progress; even though the disk is bad, the vdev partner is not in a "complete" state. let it finish resilver, and THEN replace the bad drive.

so I assume you have a data store defined looking for saspool... remember to delete that too.

what does zpool list and zpool import show?

the likely culprit is a pre-existing filesystem on your local drive. The installer is usually pretty good at dealing with it, but in your case clearly it isnt. use a linux livecd like https://gparted.org/download.php and completely wipe the drive; retry installation.

actual errors would be useful- this can refer to the zfs pool or the storage pool in pve. No. each pool must have a different name on the same host. same goes for pve stores.

Ignore it. its just informing you what the default behavior for a ceph install is, which is not aware of how ceph interacts in a pve environment.

I feel so inadequate.... for years, I just run a postinstall script that sits on a nfs mount. yes, I could have done more automation but in the end it seemed the better part of valor to just type mount followed by /path/to/mount/postinstall.sh maybe if I was doing 100 installs a day I'd look...

This package is necessary to prevent race condition issues at boot; what could happen without it is that VGs get trapped ahead of multipath by the operating system. If you dont have any entries in fstab for your iscsi mounts you dont need it. edit- to clarify, if you're not issuing iscsi...

As long as your PVE box sees the drives (eg, /dev/sdb and /dev/sdc) you can do whatever you want insofar as deployment. You can make them individual VGs, or Single VG on both, or as a zpool, btrfs mirror, or passthrough to guest if you really want OMV. Understand that USB as a disk transport...

well since the cluster is still up, not all is lost (or at least there is still a chance of recovery.) start with logging into a node containing a working monitor: ceph config dump | tee -a /etc/pve/ceph.conf.rebuild alternatively, if it doesnt work: ceph config show-with-defaults...

https://forum.proxmox.com/threads/full-disk-on-vm-but-cant-find-files-taking-up-space.75084/post-336530

I'd say that the question is too broad for a reasonable answer; most "software" doesnt care about direct access to hardware. application that need DO need access (eg, GPU) have these methods to accomplish: 1. for exclusive access, a gpu can be passed directly to a guest 2. for shared access, it...

the syntax is qm disk import <vmid> <source> <storage> [OPTIONS] in your case, source would be /path/to/my/recovered.raw

1. try proxmox-kernel 2. says who? while the DRIVERS arent provided in the package, mst should work just fine. if it doesnt, you can always uninstall :) 3. that is one way; another would be to make a persistent live usb so you dont have to mess with your install at all.