From: Ralf Storm <ralf.storm@konzept-is.de>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Question about best way to replace boot disk of a proxmox + ceph node
Date: Fri, 9 Jul 2021 12:16:38 +0200 [thread overview]
Message-ID: <e46839dd-b7f4-7d22-f596-d9c0edf5e615@konzept-is.de> (raw)
In-Reply-To: <17e68a3840a9442d8f0e845493964dca@xpecto.com>
Hello Christoph,
please read the documentation about removing/replacing a Node carefully
- you may not reinstall it with the same IP and/or Name as this will
crash your whole cluster!
I would use the node6 to move the ceph-part and then reinstall the node
with new ip and name.
For the boot disks we use 2 or 3 mirrored zfs disks to be sure...
Best regards
Ralf
Am 09.07.2021 um 11:43 schrieb Christoph Weber:
> Hi everybody,
>
> we have one proxmox node (node3) with ceph where the boot disk is beginning to fail (In fact we already experienced some defective system libraries which led to kernel panic on boot until we were able to determine the affected library to be replaced with a working copy).
>
> We see two possible ways:
> a) clone the partially defective disk to a new ssd which would keep all configuration, but might also copy defective files
> b) install a fresh copy of proxmox 6.4 with two subvariants:
> b1) only configure the same network interface address and name and join the proxmox and ceph cluster when the node has booted up
> b2) copy network configuration and /etc/ceph folder from defective node to the new disk before booting - and then join the proxmox cluster. In this case the question is, if there are more files to be copied like /etc/corosync?
>
> Method b1 seems to be the most safe to me, but I'm not 100% sure if it might be a problem when we cluster join the node3 again with the same name and ip address as it was.
> Would we have to prepare ceph or proxmox for this? Remove the node3 from ceph and/or proxmox before we re-join it?
>
> Additional Bonus: We have a fresh node (node6) without disks set up - we might move the ceph disks from the node3 to the new node6 before we replace the bootdisk.
>
> Any opinions/suggestions would be greatly appreciated
>
prev parent reply other threads:[~2021-07-09 10:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 9:43 Christoph Weber
2021-07-09 10:16 ` Ralf Storm [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e46839dd-b7f4-7d22-f596-d9c0edf5e615@konzept-is.de \
--to=ralf.storm@konzept-is.de \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.