Search results

  1. E

    Network setup.

    Thanks again, thats super helpful! I'm not doing anything crazy, so its definitely overkill, but I want to do it right if I'm going to do it, and maybe some day I will use it to full capacity. Right now one VM is a NAS and one is a docker server that I run plex on, and sometimes host a local...
  2. E

    Network setup.

    Thanks! that's the part I did not understand for some reason.
  3. E

    Network setup.

    ok, so just use the same bond for all vms? I only have it set the way I have it set now because I just thought each was going to have to use a physical nic. it sounds like once I create the bond, I will only need the one bridges, and all vm's will just use the same vmbr0, but have different ips?
  4. E

    Network setup.

    this is clearly the first time i've gone down this route, but I really want to make sure I break as little as possible tomorrow and Saturday. That's currently my proxmox network config. Proxmox maps to vmbr0. I have 2 more vm's that I map VM#1 to vmbr1 and VM#2 to vmbr2. then when i test a...
  5. E

    Wearout 99%

    I hope that's it, I'm not terribly worried as it's been like that for months, i'll just keep an eye out and see if anything starts changing. Thanks again!
  6. E

    Network setup.

    thanks! I'll have to make that change! I guess proxmox will have the bond and it will include all nics and get an ip, then i'll just create a virtual nic for each vm, give it an ip and the gateway will be the ip of the bond? Or am I over complicating it? throwing vlans on top of that probably...
  7. E

    Network setup.

    I'm about to upgrade my homelab with a proper router and switch. I feel like it will be a good time to make changes to my proxmox config during that time. Currently I have proxmox installed on an r720 that has a quad nic, which I will be upgrading as well. I will go from the quad 1gb, to...
  8. E

    Wearout 99%

    It's my boot drive, no vm's running on it or anything, just proxmox, I may have answered my own question WDS500G2B0B Does not seem to be in the database, from what I can tell, and perhaps it's getting an incorrect "media wearout idicator"?
  9. E

    Wearout 99%

    I've had proxmox installed on an m.2 ssd for a few months (~6). I don't know when the wearout started stating 99%, but it's been at least a month. Any ideas on if this can just be incorrect? I have updated the smart tools db and re ran smartctl, but still no luck. This is the drive i have...
  10. E

    device-mapper: thin: process_cell: dm_thin_find_block() failed: error = -5

    I would definitely make sure you update the firmware before you get going, just in case that fixes it. I've had no luck getting the firmware updated for any of my ssds.
  11. E

    Proxmox just died with: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10

    interesting, so yours may be related to power. I only have a p400 in my risers. dual 750w, dual xeon v2 2690's, only 6 drives loaded into my back plane, so I would think I'm not stressing it from a power perspective, i guess one/both power could be "bad" Thanks for the information.
  12. E

    Proxmox just died with: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10

    Any luck, I see this issue sporadically with my 870 EVO. I've seen someone say it was fixed after updating firmware on their drive, might be an option. I've suspected power problems in my device, no firmware for my device to update, so looking for any potential solution or location to...
  13. E

    device-mapper: thin: process_cell: dm_thin_find_block() failed: error = -5

    Thanks, I guess since there is no firmware for my SSD, I may be out of luck. going to have to figure out how to migrate to a new boot drive.
  14. E

    device-mapper: thin: process_cell: dm_thin_find_block() failed: error = -5

    thanks so the firmware update, did not wipe your drive? Did you have to download the firmware, or did it detect your device and tell you what firmware it was going to install? the 870 pro isnt listed, but thought maybe if I hook it up and it see's it, it will have an update for it :(
  15. E

    device-mapper: thin: process_cell: dm_thin_find_block() failed: error = -5

    I think I may have this same issue. Is it still working for you? I have a few questions if you get a chance. 1) is it still working? (mine seems to die randomly every few days) 2) It's going to wipe the drive I'm guessing? (how did you back up your VM's? 3) I have an 870 samsung pro, but I...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!