#proliant — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #proliant, aggregated by home.social.
-
Qui veut des galères de démarrage ?
Saleté de #proxmox qui ne laisse pas choisir le partitionnement des disques (et le serveur ridiculement stricte). -
Qui veut des galères de démarrage ?
Saleté de #proxmox qui ne laisse pas choisir le partitionnement des disques (et le serveur ridiculement stricte). -
Two #HP #ProLiant DL380 Gen10. Used. In working condition. No OS loaded
1. #Intel #Xeon Bronze 3006 CPU @1.70GHz, 64 GB RAM, 24x 2TB SAS drives, 2 power supplies
2. Intel Xeon Silver 4110 CPU @2.1GHz, 64 GB RAM, 3x 480GB SATA SSD, 5x 2TB SAS drives, 2 power supplies
-
Two #HP #ProLiant DL380 Gen10. Used. In working condition. No OS loaded
1. #Intel #Xeon Bronze 3006 CPU @1.70GHz, 64 GB RAM, 24x 2TB SAS drives, 2 power supplies
2. Intel Xeon Silver 4110 CPU @2.1GHz, 64 GB RAM, 3x 480GB SATA SSD, 5x 2TB SAS drives, 2 power supplies
-
Two #HP #ProLiant DL380 Gen10. Used. In working condition. No OS loaded
1. #Intel #Xeon Bronze 3006 CPU @1.70GHz, 64 GB RAM, 24x 2TB SAS drives, 2 power supplies
2. Intel Xeon Silver 4110 CPU @2.1GHz, 64 GB RAM, 3x 480GB SATA SSD, 5x 2TB SAS drives, 2 power supplies
-
Two #HP #ProLiant DL380 Gen10. Used. In working condition. No OS loaded
1. #Intel #Xeon Bronze 3006 CPU @1.70GHz, 64 GB RAM, 24x 2TB SAS drives, 2 power supplies
2. Intel Xeon Silver 4110 CPU @2.1GHz, 64 GB RAM, 3x 480GB SATA SSD, 5x 2TB SAS drives, 2 power supplies
-
Two #HP #ProLiant DL380 Gen10. Used. In working condition. No OS loaded
1. #Intel #Xeon Bronze 3006 CPU @1.70GHz, 64 GB RAM, 24x 2TB SAS drives, 2 power supplies
2. Intel Xeon Silver 4110 CPU @2.1GHz, 64 GB RAM, 3x 480GB SATA SSD, 5x 2TB SAS drives, 2 power supplies
-
Me parece impresionante lo fácil que es mover todo el sistema #UnRAID físicamente de un servidor a otro totalmente distinto. En mi caso de un HP #ProLiant ML110 G7 con 3 discos mecánicos y un SSD a un Dell #PowerEdge T330. Sólo he tenido que llevarme el "pincho" USB (que lo puedo "esconder" dentro del servidor gracias al conector USB que tiene en la placa base) y los discos y conectarlo todo en el T330. Arrancar y listo. (1/3)
-
Me parece impresionante lo fácil que es mover todo el sistema #UnRAID físicamente de un servidor a otro totalmente distinto. En mi caso de un HP #ProLiant ML110 G7 con 3 discos mecánicos y un SSD a un Dell #PowerEdge T330. Sólo he tenido que llevarme el "pincho" USB (que lo puedo "esconder" dentro del servidor gracias al conector USB que tiene en la placa base) y los discos y conectarlo todo en el T330. Arrancar y listo. (1/3)
-
Me parece impresionante lo fácil que es mover todo el sistema #UnRAID físicamente de un servidor a otro totalmente distinto. En mi caso de un HP #ProLiant ML110 G7 con 3 discos mecánicos y un SSD a un Dell #PowerEdge T330. Sólo he tenido que llevarme el "pincho" USB (que lo puedo "esconder" dentro del servidor gracias al conector USB que tiene en la placa base) y los discos y conectarlo todo en el T330. Arrancar y listo. (1/3)
-
Me parece impresionante lo fácil que es mover todo el sistema #UnRAID físicamente de un servidor a otro totalmente distinto. En mi caso de un HP #ProLiant ML110 G7 con 3 discos mecánicos y un SSD a un Dell #PowerEdge T330. Sólo he tenido que llevarme el "pincho" USB (que lo puedo "esconder" dentro del servidor gracias al conector USB que tiene en la placa base) y los discos y conectarlo todo en el T330. Arrancar y listo. (1/3)
-
Me parece impresionante lo fácil que es mover todo el sistema #UnRAID físicamente de un servidor a otro totalmente distinto. En mi caso de un HP #ProLiant ML110 G7 con 3 discos mecánicos y un SSD a un Dell #PowerEdge T330. Sólo he tenido que llevarme el "pincho" USB (que lo puedo "esconder" dentro del servidor gracias al conector USB que tiene en la placa base) y los discos y conectarlo todo en el T330. Arrancar y listo. (1/3)
-
Was setting up the new router yesterday and also upgraded the #Proxmox 7 (EoL) install on our old HP #ProLiant (DL360p G8) to latest 8.2. Worked like a charm ♥️
Hoping the connection issues are fixed now. This is the self hosting part that sucks but realistically.. who cares if my mailserver or the blog is offline for a few hours? The whole 24/7 idea is kinda nuts. Whatever happened to Hold The Line, Please.
-
Was setting up the new router yesterday and also upgraded the #Proxmox 7 (EoL) install on our old HP #ProLiant (DL360p G8) to latest 8.2. Worked like a charm ♥️
Hoping the connection issues are fixed now. This is the self hosting part that sucks but realistically.. who cares if my mailserver or the blog is offline for a few hours? The whole 24/7 idea is kinda nuts. Whatever happened to Hold The Line, Please.
-
Was setting up the new router yesterday and also upgraded the #Proxmox 7 (EoL) install on our old HP #ProLiant (DL360p G8) to latest 8.2. Worked like a charm ♥️
Hoping the connection issues are fixed now. This is the self hosting part that sucks but realistically.. who cares if my mailserver or the blog is offline for a few hours? The whole 24/7 idea is kinda nuts. Whatever happened to Hold The Line, Please.
-
Was setting up the new router yesterday and also upgraded the #Proxmox 7 (EoL) install on our old HP #ProLiant (DL360p G8) to latest 8.2. Worked like a charm ♥️
Hoping the connection issues are fixed now. This is the self hosting part that sucks but realistically.. who cares if my mailserver or the blog is offline for a few hours? The whole 24/7 idea is kinda nuts. Whatever happened to Hold The Line, Please.
-
In light of a failed hard drive on my refurbished #proliant (one of four drives in the array), I'm doing a deep backup of media files and databases before doing my first hot-swap.
When I first started this digital madness c. 2010, it was a few directories I manually created on a 500GB portable drive. Today's backup of 90,000+ files is going to a spare 4TB external drive.
-
In light of a failed hard drive on my refurbished #proliant (one of four drives in the array), I'm doing a deep backup of media files and databases before doing my first hot-swap.
When I first started this digital madness c. 2010, it was a few directories I manually created on a 500GB portable drive. Today's backup of 90,000+ files is going to a spare 4TB external drive.
-
In light of a failed hard drive on my refurbished #proliant (one of four drives in the array), I'm doing a deep backup of media files and databases before doing my first hot-swap.
When I first started this digital madness c. 2010, it was a few directories I manually created on a 500GB portable drive. Today's backup of 90,000+ files is going to a spare 4TB external drive.
-
In light of a failed hard drive on my refurbished #proliant (one of four drives in the array), I'm doing a deep backup of media files and databases before doing my first hot-swap.
When I first started this digital madness c. 2010, it was a few directories I manually created on a 500GB portable drive. Today's backup of 90,000+ files is going to a spare 4TB external drive.
-
In light of a failed hard drive on my refurbished #proliant (one of four drives in the array), I'm doing a deep backup of media files and databases before doing my first hot-swap.
When I first started this digital madness c. 2010, it was a few directories I manually created on a 500GB portable drive. Today's backup of 90,000+ files is going to a spare 4TB external drive.
-
The Integrated Lights-Out (ILO) Management on HPE #ProLiant servers support the #Redfish DMTF API since ILO4.
To make the communication to the API easier, #HPE created the #opensource ilorest command in 2016.
However, depending on your #Linux server setup, you might run into an error when executing ilorest - a misleading error pointing to a library issue.
In my latest #blog post I share how #ilorest can be debugged and find out the real reason.
-
The Integrated Lights-Out (ILO) Management on HPE #ProLiant servers support the #Redfish DMTF API since ILO4.
To make the communication to the API easier, #HPE created the #opensource ilorest command in 2016.
However, depending on your #Linux server setup, you might run into an error when executing ilorest - a misleading error pointing to a library issue.
In my latest #blog post I share how #ilorest can be debugged and find out the real reason.
-
The Integrated Lights-Out (ILO) Management on HPE #ProLiant servers support the #Redfish DMTF API since ILO4.
To make the communication to the API easier, #HPE created the #opensource ilorest command in 2016.
However, depending on your #Linux server setup, you might run into an error when executing ilorest - a misleading error pointing to a library issue.
In my latest #blog post I share how #ilorest can be debugged and find out the real reason.
-
The Integrated Lights-Out (ILO) Management on HPE #ProLiant servers support the #Redfish DMTF API since ILO4.
To make the communication to the API easier, #HPE created the #opensource ilorest command in 2016.
However, depending on your #Linux server setup, you might run into an error when executing ilorest - a misleading error pointing to a library issue.
In my latest #blog post I share how #ilorest can be debugged and find out the real reason.
-
Are you running #ProLiant DX with Nutanix AOS and do you get a warning about incorrect SAS cabling after installing the last patches? You might want to take a look at this. #Nutanix #HPE
https://vcloudnine.de/hpe-hba-cabling-check-falsely-issues-a-warning/
-
Are you running #ProLiant DX with Nutanix AOS and do you get a warning about incorrect SAS cabling after installing the last patches? You might want to take a look at this. #Nutanix #HPE
https://vcloudnine.de/hpe-hba-cabling-check-falsely-issues-a-warning/
-
Just published a blog post on how I power up my home lab with Ansible and some neat features of Ansible that make this process easy.
https://medium.com/@a.j.longchamps/how-i-power-on-my-home-lab-with-ansible-dd608e7357a2
-
Just published a blog post on how I power up my home lab with Ansible and some neat features of Ansible that make this process easy.
https://medium.com/@a.j.longchamps/how-i-power-on-my-home-lab-with-ansible-dd608e7357a2
-
Just published a blog post on how I power up my home lab with Ansible and some neat features of Ansible that make this process easy.
https://medium.com/@a.j.longchamps/how-i-power-on-my-home-lab-with-ansible-dd608e7357a2
-
Just published a blog post on how I power up my home lab with Ansible and some neat features of Ansible that make this process easy.
https://medium.com/@a.j.longchamps/how-i-power-on-my-home-lab-with-ansible-dd608e7357a2
-
Just published a blog post on how I power up my home lab with Ansible and some neat features of Ansible that make this process easy.
https://medium.com/@a.j.longchamps/how-i-power-on-my-home-lab-with-ansible-dd608e7357a2
-
CW: What can you actually boot from an HPE ProLiant iLO 5?
While debugging the problem with FreeBSD not booting on HPE #ProLiant DL385 Gen10 "Plus" v2 and HPE #ProLiant DL345 Gen11 via virtual disks on iLO 5 (version 3.01 from January 2024) we went through a plethora of bootable images.
Here are the results:
* #FreeBSD 11.3, 12.4, 13.2, 14.0 all exhibit the same problem booting any of the ISO or IMG files where the first bootloader is fine but then when it boots the kernel the USB emulation is "lost" and it is unable to mount the root fs,
* #OpenBSD 7.4 - neither the ISO nor the IMG file is even recognised as bootable
* #Linux (Ubuntu 22.04 LTS "server") boots fine and into the installer.We did not try Windows or MS-DOS because we couldn't care less about them working and we presumed the former would be the standard QA test.
An additional data point is the the emulated USB is UHCI and that, on previous machines which were installed (via USB stick) you completely lose the USB keyboard and mouse on the virtual console which becomes, in effect useless.
For those interested in spelunking the iLO5 3.01 manual has a couple of curious entries around power-saving such as this one talking about "persistence" of the USB mouse and keyboard¹ which we're looking into to see if that fixes at least the console post-install.
There is a case open with HPE (not public, sadly), not that it will ever get any attention, and there is a FreeBSD bug open where you can see all the work which went into it².
:flan_greybeard: will have to set up a PXE infrastructure to install machines.
__
¹ https://support.hpe.com/hpesc/public/docDisplay?docId=a00105236en_us&page=GUID-6099A408-6792-431B-B947-A3BB73E49F1B.html
² https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277062 -
CW: What can you actually boot from an HPE ProLiant iLO 5?
While debugging the problem with FreeBSD not booting on HPE #ProLiant DL385 Gen10 "Plus" v2 and HPE #ProLiant DL345 Gen11 via virtual disks on iLO 5 (version 3.01 from January 2024) we went through a plethora of bootable images.
Here are the results:
* #FreeBSD 11.3, 12.4, 13.2, 14.0 all exhibit the same problem booting any of the ISO or IMG files where the first bootloader is fine but then when it boots the kernel the USB emulation is "lost" and it is unable to mount the root fs,
* #OpenBSD 7.4 - neither the ISO nor the IMG file is even recognised as bootable
* #Linux (Ubuntu 22.04 LTS "server") boots fine and into the installer.We did not try Windows or MS-DOS because we couldn't care less about them working and we presumed the former would be the standard QA test.
An additional data point is the the emulated USB is UHCI and that, on previous machines which were installed (via USB stick) you completely lose the USB keyboard and mouse on the virtual console which becomes, in effect useless.
For those interested in spelunking the iLO5 3.01 manual has a couple of curious entries around power-saving such as this one talking about "persistence" of the USB mouse and keyboard¹ which we're looking into to see if that fixes at least the console post-install.
There is a case open with HPE (not public, sadly), not that it will ever get any attention, and there is a FreeBSD bug open where you can see all the work which went into it².
:flan_greybeard: will have to set up a PXE infrastructure to install machines.
__
¹ https://support.hpe.com/hpesc/public/docDisplay?docId=a00105236en_us&page=GUID-6099A408-6792-431B-B947-A3BB73E49F1B.html
² https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277062 -
CW: What can you actually boot from an HPE ProLiant iLO 5?
While debugging the problem with FreeBSD not booting on HPE #ProLiant DL385 Gen10 "Plus" v2 and HPE #ProLiant DL345 Gen11 via virtual disks on iLO 5 (version 3.01 from January 2024) we went through a plethora of bootable images.
Here are the results:
* #FreeBSD 11.3, 12.4, 13.2, 14.0 all exhibit the same problem booting any of the ISO or IMG files where the first bootloader is fine but then when it boots the kernel the USB emulation is "lost" and it is unable to mount the root fs,
* #OpenBSD 7.4 - neither the ISO nor the IMG file is even recognised as bootable
* #Linux (Ubuntu 22.04 LTS "server") boots fine and into the installer.We did not try Windows or MS-DOS because we couldn't care less about them working and we presumed the former would be the standard QA test.
An additional data point is the the emulated USB is UHCI and that, on previous machines which were installed (via USB stick) you completely lose the USB keyboard and mouse on the virtual console which becomes, in effect useless.
For those interested in spelunking the iLO5 3.01 manual has a couple of curious entries around power-saving such as this one talking about "persistence" of the USB mouse and keyboard¹ which we're looking into to see if that fixes at least the console post-install.
There is a case open with HPE (not public, sadly), not that it will ever get any attention, and there is a FreeBSD bug open where you can see all the work which went into it².
:flan_greybeard: will have to set up a PXE infrastructure to install machines.
__
¹ https://support.hpe.com/hpesc/public/docDisplay?docId=a00105236en_us&page=GUID-6099A408-6792-431B-B947-A3BB73E49F1B.html
² https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277062 -
CW: What can you actually boot from an HPE ProLiant iLO 5?
While debugging the problem with FreeBSD not booting on HPE #ProLiant DL385 Gen10 "Plus" v2 and HPE #ProLiant DL345 Gen11 via virtual disks on iLO 5 (version 3.01 from January 2024) we went through a plethora of bootable images.
Here are the results:
* #FreeBSD 11.3, 12.4, 13.2, 14.0 all exhibit the same problem booting any of the ISO or IMG files where the first bootloader is fine but then when it boots the kernel the USB emulation is "lost" and it is unable to mount the root fs,
* #OpenBSD 7.4 - neither the ISO nor the IMG file is even recognised as bootable
* #Linux (Ubuntu 22.04 LTS "server") boots fine and into the installer.We did not try Windows or MS-DOS because we couldn't care less about them working and we presumed the former would be the standard QA test.
An additional data point is the the emulated USB is UHCI and that, on previous machines which were installed (via USB stick) you completely lose the USB keyboard and mouse on the virtual console which becomes, in effect useless.
For those interested in spelunking the iLO5 3.01 manual has a couple of curious entries around power-saving such as this one talking about "persistence" of the USB mouse and keyboard¹ which we're looking into to see if that fixes at least the console post-install.
There is a case open with HPE (not public, sadly), not that it will ever get any attention, and there is a FreeBSD bug open where you can see all the work which went into it².
:flan_greybeard: will have to set up a PXE infrastructure to install machines.
__
¹ https://support.hpe.com/hpesc/public/docDisplay?docId=a00105236en_us&page=GUID-6099A408-6792-431B-B947-A3BB73E49F1B.html
² https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277062 -
CW: What can you actually boot from an HPE ProLiant iLO 5?
While debugging the problem with FreeBSD not booting on HPE #ProLiant DL385 Gen10 "Plus" v2 and HPE #ProLiant DL345 Gen11 via virtual disks on iLO 5 (version 3.01 from January 2024) we went through a plethora of bootable images.
Here are the results:
* #FreeBSD 11.3, 12.4, 13.2, 14.0 all exhibit the same problem booting any of the ISO or IMG files where the first bootloader is fine but then when it boots the kernel the USB emulation is "lost" and it is unable to mount the root fs,
* #OpenBSD 7.4 - neither the ISO nor the IMG file is even recognised as bootable
* #Linux (Ubuntu 22.04 LTS "server") boots fine and into the installer.We did not try Windows or MS-DOS because we couldn't care less about them working and we presumed the former would be the standard QA test.
An additional data point is the the emulated USB is UHCI and that, on previous machines which were installed (via USB stick) you completely lose the USB keyboard and mouse on the virtual console which becomes, in effect useless.
For those interested in spelunking the iLO5 3.01 manual has a couple of curious entries around power-saving such as this one talking about "persistence" of the USB mouse and keyboard¹ which we're looking into to see if that fixes at least the console post-install.
There is a case open with HPE (not public, sadly), not that it will ever get any attention, and there is a FreeBSD bug open where you can see all the work which went into it².
:flan_greybeard: will have to set up a PXE infrastructure to install machines.
__
¹ https://support.hpe.com/hpesc/public/docDisplay?docId=a00105236en_us&page=GUID-6099A408-6792-431B-B947-A3BB73E49F1B.html
² https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277062
