Search results

Though I'm wondering if it's my external SSD I've got passed through to a VM that I'm using for a cache drive for the moment. May need to stop that since I know that drive is old and had tons of data passed through it over the past 8 years

@leesteken I do want to make sure to mention that I'm running only LVMs and not ZFS. Would that potentially impact things and what I should look for or just continue with the long smart tests?

Thanks I'll do some checking into that and see what I find

My server is running hardware that's between 5-6 years old aside from the drives that's been running 24/7 and I'm starting to have outages/crashes roughly every 9 days it seems. It literally just happened and caused VMs to start slowly locking up and once I got them powered down I was getting...

I can confirm that this last reboot my LVMs came up immediately instead of me having to fight them. So this fixed that issue though now I'll be opening a new thread to see if I can get some help investigating to see if I have hardware problems in general. Thanks for the fix @fiona

Went ahead and added that fix and if nothing else I'll just revert back to my copy of the lvm.conf next time I reboot or it crashes

They're all thin pools built on top of standard LVMs. Assuming I'm using the terms correctly. All my LVM dealings/learnings have come from Proxmox. So to outline when I select LVM under Disks I get Then when selecting LVM-Thin I get So if this lines up with that fix then I'll get that added...

I'm slowly starting to lean towards hardware at this point. I had another crash just a moment ago. Though now I'm just trying to get things up and running since it's getting late-ish. I'll be curious to see if anything jumps out at you though

Currently working on getting it restored now since the LVMs are down

A random reboot got me the info much sooner than expected so here's the outputs that you asked for pvs root@proxmox:~# pvs PV VG Fmt Attr PSize PFree /dev/nvme0n1p3 pve lvm2 a-- <465.26g <16.00g /dev/sda Backup_Storage lvm2 a-- <3.64t...

Life got in the way and I completely forgot to do a reboot this weekend. My goal is to try and do it sometime throughout the week so that I can get you the info you're asking for.

After an initial read my first question is how is your Proxmox supposed to connect to the LAN of the network? Since it's using port 1 is it plugged into the LAN somewhere? Since ports 3 and 4 are dedicated to OPNsense those won't automatically give access to Proxmox. I used to run a similar...

I'm glad to hear that. I know on a previous install of Proxmox I started to experience this exact issue but it was with a multi-drive LVM that was running some ancient drives. All of the hardware minus the drives is the exact same since I had a boot drive die and replaced the others. So hoping...

I'll gather that information next time it occurs. I may try rebooting this weekend so I can gather the output of those LVM cmds for you. For the moment though I'll post the rest of the requested information. root@proxmox:~# pveversion -v proxmox-ve: 7.3-1 (running kernel: 5.15.83-1-pve)...

I have an install running 4 different LVMs across 4 different drives 2 are SSDs and 2 are spinning disks. Upon reboot my system will have my SSD LVMs loaded and ready to go but my spinning disk all show a ? mark and are unavailable. To get them back I typically have to run something like...

May possibly be having a drive with some upcoming issues. Manually deactivating the lvm with vgchange <lvm name> -an then vgchange <lvm name> -ay got it back online and the server seems happy again. SMART is showing PASSING on everything but the oldest drive is probably 6 years old now and the...

Looks like I'm having some LVM issues with my large data pool that I'm going to have to try and work through to recover from the looks of it. One disk isn't activating properly

Apparently I'm also unable to run any of the pvenode commands for this same reason. I'm guessing a reboot may be my best next step potentially.

Not sure when the issue actually started happening but I logged in to setup a new test VM and when I went to start it it immediately failed when I had a vNIC setup on it. After removing the vNIC to test further I was then unable to get a console to open up to it. I checked my 2 other running VMs...

I didn't even think to try that! That resolved the issue for me.