From: Aaron Lauterer <a.lauterer@proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
Philippe Andersson <pan@iba-group.com>
Subject: Re: [PVE-User] Intel RST / VROC support in latest Proxmox?
Date: Tue, 27 Jun 2023 10:33:25 +0200 [thread overview]
Message-ID: <c03e690d-d6a6-9670-2e9e-b816a53d9c2f@proxmox.com> (raw)
In-Reply-To: <7b0bdc0d-fa2e-3a9b-00b4-7f177748af57@iba-group.com>
AFAIK, VROC has two variants, actual HW RAID and so-called fake RAID. If it is
the fake RAID variant, it will be ignored and the single disks should be shown
in the installer.
If it is an actual HW RAID, it should only show a single block device for each
RAID to the OS.
In consumer boards, the chances of VROC being the fake RAID variant are quite high.
But why not ZFS with mirrored (maybe even multiple mirrored disk, RAID 10 like)?
In case of a disk failure, the handling of it is much nicer and if you can
hotplug the disks, you don't even need to power down the machine.
Cheers,
Aaron
On 6/27/23 09:50, Philippe Andersson wrote:
> Hello List,
>
> Quick question. I'm currently looking into upgrading my home Proxmox
> server (using PC components meant for the home market, for cost
> reasons), and getting a "real" hardware RAID proposition under these
> conditions turns out to be quite an ordeal. Intel RST/VROC seems to be
> the only available option.
>
> Can anyone on this list please confirm whether these technologies are
> supported by the latest Proxmox VE installer/kernel ?
>
> Thanks in advance.
>
> Ph. A.
>
> --
>
> *Philippe Andersson*
> Unix System Administrator
> IBA Particle Therapy |
> Tel: +32-10-475.983
> Fax: +32-10-487.707
> eMail: pan@iba-group.com
> <http://www.iba-worldwide.com>
>
>
>
> Disclaimer | Use of IBA e-communication<https://iba-worldwide.com/disclaimer>
>
> The contents of this e-mail message and any attachments are intended solely for
> the recipient (s) named above. This communication is intended to be and to
> remain confidential and may be protected by intellectual property rights. Any
> use of the information contained herein (including but not limited to, total or
> partial reproduction, communication or distribution of any form) by persons
> other than the designated recipient(s) is prohibited. Please notify the sender
> immediately by e-mail if you have received this e-mail by mistake and delete
> this e-mail from your system. E-mail transmission cannot be guaranteed to be
> secure or error-free. Ion Beam Applications does not accept liability for any
> such errors. Thank you for your cooperation.
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
>
next prev parent reply other threads:[~2023-06-27 8:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 7:50 Philippe Andersson
2023-06-27 8:33 ` Aaron Lauterer [this message]
2023-06-27 10:03 ` Konold, Martin
2023-06-28 14:55 ` Philippe Andersson
2023-06-29 7:14 ` Aaron Lauterer
[not found] ` <mailman.127.1687943327.232.pve-user@lists.proxmox.com>
2023-06-28 15:13 ` Philippe Andersson
2023-06-28 15:16 ` Philippe Andersson
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=c03e690d-d6a6-9670-2e9e-b816a53d9c2f@proxmox.com \
--to=a.lauterer@proxmox.com \
--cc=pan@iba-group.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox