Search results

Just following up that while I had no *known* issues (been a few months since my last reboot), I ran apt dist-upgrade today and actually came across this message from your patch. I got the warning, which I first googled and came across this thread, and did the steps suggested. Rebooted my...

Just wanted to share that setting thin_check_options as suggested by Fabian_E worked for me. I have two identical 12TB disks, and for whatever reason one of them will not activate after a reboot of the Proxmox server. I used to have to do the lvchange -an/lvchange -ay method but...

Just as an update, I still have to do the same workaround as described by maxprox. After every reboot, one drive in particular I need to run lvchange -an on, but I need to wait about 5 minutes or so after Proxmox is done booting before it'll let me deactivate the volume. Then I can run lvchange...

I assume you don't really mean to install proxmox 5.2, but I can say I've had a (mostly) flawless experience with a R730xd and a PERC H730P. I'm on the latest 7.x version of Proxmox right now.

Apologies for not responding sooner. But for me, I often need to wait a good 5, maybe even 10 minutes after Proxmox is fully booted in order to run the lvchange -an command as I get the same error. But eventually, it does let me run it, which then allows me to enable the volume again, and I'm...

I am in the same camp. I have 2 identical 12TB HDD's. One loads up fine on every reboot, the other I need to manually deactivate/activate. Works great until I reboot the server.

I have the same issue. As for the workaround, just do: lvchange -an hgst_12tb *then* lvchange -ay hgst_12tb For me, this works. the 'lvchange -an hgst_12tb' command will take about 5 minutes, but it does eventually work, and then my VM's are functional again. Really weird. Downside is, I need...