WilliamLam.com

Heads Up - 24GB & 48GB DDR5 SODIMM memory now available

by // 2 Comments

For small or ultra small form factor (SFF/USFF) systems like the popular Intel NUC, SODIMM (Small-Outline Dual Inline Memory Module) memory is commonly used, which has been limited to a maximum of 64GB (2 x 32GB module) memory since 2019, which I had first shared that the Intel NUC could used the new 32GB modules. While 64GB might have been plentiful back in 2019, it certainly no longer cuts it, especially for any serious VMware Homelab.

Like many, I assumed the SODIMM format has simply hit its limit and with the new proposed CAMM standard looking to replace SODIMM format in the near future, I was honestly not expecting that we could reach higher density modules for SODIMM.

UPDATE (05/18/23) - Officially confirmed Mushkin 48GB DDR5 SODIMM works with DDR5 compatible system with ESXi

UPDATE (05/10/23) - Mushkin has released 48GB modules for three different frequencies (5600, 5200 & 4800 Mhz). For more details, please see below with initial pricing of $349 USD

UPDATE (02/21/23) - Apologies, it looks like Corsair has only released the Desktop memory and NOT Laptop memory (SODIMM) for the new DDR5 capacity modules. I assume those will come shortly, but these are currently only for desktop systems.

Fast forward to 2023, news broke that a new 24GB and 48GB DDR5 SODIMM modules were in the works and today, they just started showing up online for purchase! Currently, only the Corsair Vengeance Desktop (non-SODIMM) with heatsinks are available:

Desktop Memory:

Laptop Memory (SO-DIMM):

This is great news for homelabbers, but before you rush out and make a purchase. These new memory modules are only for DDR5 and there are currently not many SFF/USFF kits that actually support DDR5 and might benefit those in the near term with DIY system. In addition, to get the full benefit, you will also need a system that can support DDR5 5200MHz. 

Create Windows 11 Virtual Appliance using Tiny 11 with only 2GB memory

by // Leave a Comment

I recently came to learn about a really cool project called Tiny 11 which is a stripped down version of Windows 11 Pro 22H2 that can run with just 2GB of memory and 8GB of storage. While you would probably not use this for production workloads, it could be interesting for those with homelabs and can even for demo purposes.

Disclaimer: Tiny 11 is not an official project from Microsoft, use at your own risk. If you are interested in creating an optimized Windows 10 or 11 image, you can also check out these VMware resources here and here to produce a similiar size image using official Microsoft tools and images.

UPDATE (02/16/23) - There is now an Arm version for Tiny 11, which is great for anyone using the ESXi-Arm Fling and the technique in this blog post would also apply.

After performing a manual installation of Tiny 11, I thought it would be neat if I could build a Virtual Appliance (OVA) for Tiny 11 and also add custom OVF properties, which would allow anyone to customize the OS further without having to rely on any external tooling.

In fact, I had demonstrated this concept back in 2019 using Windows Server 2016 in this blog post and I figure it should be easy enough to also do the same for Tiny 11 or even standard Windows 11! With a bit of trial/error, I was indeed able to create a simple Tiny 11 OVA that includes the following OVF properties as shown in the screenshot below.


My initial goal was to fully automate the building of a Tiny 11 OVA with custom OVF properties using Packer. However, after many attempts, I was not able to figure out the correct autoattended.xml configuration and decided on a semi-manual approach which is detailed in the instructions below. If anyone is able to figure out how to get Tiny 11 installed via Packer, then I may revisit this topic and automate the remainder of the setup.

Note: The instructions below are not specific to Tiny 11 in any way and is also applicable to standard Windows 10 or 11 image.

[Read more...]

Quick Tip - Additional NVMe vendors (SK Hynix & Sabrent) for ESXi homelab

by // 12 Comments

The Samsung 980 Pro NVMe is a pretty popular SSD model that is used by many within the VMware Homelab Community. However, in recent months, there have been an alarming amount of reports from owners that their 980 Pro NVMe devices have been failing prematurely due to firmware issues.

Samsung has finally acknowledge the problem with a firmware fix and it looks like a simliar fix is also planned for the Samsung 990 Pro NVMe.

While I can not comment on the specific issues with the Samsung 980/990 Pro NVMe devices, I have had my own failures with cheaper Samsung M.2 NVMe devices where I lost my vSAN setup since I only had a single vSAN diskgroup comprised of single cache and capacity SSD for my homelab. While not ideal, this is to be expected since I had no redundancy and consumer hardware can and will fail over time. I ended upgrading both of my SSDs to a Samsung 970 Plus, which luckily is not affected by the firmware issues.

I typically recommend Samsung, Intel and Western Digital NVMe devices as they typically just work with ESXi, especially for homelab purposes where cost is one of the factors. From some of the online posts that I have read about the current Samsung 980/990 Pro issues, it seems that many have lost faith in Samsung and some have even stated that they will no longer consider Samsung for storage purchases.

This was also a simliar sentiment when I recently spoke with a fellow VMware colleague who was also impacted by the firmware issues. As part of our discussion, he had shared a couple of alternative vendors that he has is now using and recommending for his VMware Homelab setup which also includes vSAN. I thought this was good information that could also benefit folks in the community looking for other storage options.

[Read more...]