@gjacobse Try the source, ICANN.

https://lookup.icann.org/en

I found that the name has changed to UniGetUI recently. I've been using it recently since it does all the Windows repositories I know about.

@Oksana said in What is the Best Type-2 Hypervisor?:

Wondering what’s the difference between Oracle VirtualBox, VMware Workstation, and QEMU? Check out our latest comprehensive comparison by Dmytro Malynka, StarWind Product Manager, to choose the best Type 2 hypervisor for your virtualization projects. Read more here: https://starwind.com/s/9S

This graphic is very deceptive. The article never mentions using QEMU with VirtualBox, only KVM.

Going over a bunch of Scotts (now old) videos and documentation on SANs to do a brief overview with our sales team. They might be oldish now, but still the best refence material around.

I had another look at updating my Cloudflare domains using dynamic DNS, and found that it is very easy now compared to a few years back.... I think 2018 was the last thread I found on it.

Anyhow, super simple.

Start by creating a new API key with DNS update permission.
Using a current Ubuntu.
apt install ddclient
Follow the instructions.

One of the things I've been doing a lot of lately is adding drives to virtual machines. This can be done hassle free, but almost all instructions found online make you find the correct bus to use. There is no reason to spend the time to track down the proper bus to scan when you can scan them all in one shot.

for host in /sys/class/scsi_host/*; do echo "- - -" | sudo tee $host/scan; done

I can't find the original reference for where I first found this. It was one of those, why didn't I think of that moments.

@dbeato said in Anyone hosting your own S3 bucket?:

@travisdh1 Are you using a Scale Cluster or just a straight made up cluster of your own?

We'll be using a cluster of our own. Doubt it will make sense to use Scale in this scenario as it will be purely storage, no compute.

@dbeato said in Anyone hosting your own S3 bucket?:

@travisdh1 I haven't done so, It would be interesting to review that option.

Part of the issue is that I'm not sure how much total storage we're currently running via HDD. I happened to mention the SuperMicro 60 bay chassis filled with 20TB drive price point that made it to owners ears, and now I get to write a proper proposal up.

Honestly, I'm going to push for a 3node Ceph cluster as a starting point. The cost for the maintenance contract on that is ~$200,000.00/year, and the SuperMicro as described with a 5 year warranty would run ~170,000.00 for us.

Having to commute every day is a little bit of a pain, but the datacenter work is a nice change of pace!

So this question is purely because I'm not sure we're going to immediately scale to where we need a 3node storage cluster at work. If they decide to go that way, we'll just use the native Ceph S3.

Anyone hosting your own S3 bucket, and which of the S3 compatible software are you using?

Next up from the Docker site, how to actually enable the GPU in a Docker Compose file.

Example of a Compose file for running a service with access to 1 GPU device

services:
  test:
    image: nvidia/cuda:12.3.1-base-ubuntu20.04
    command: nvidia-smi
    deploy:
      resources:
        reservations:
          devices:
            - driver: nvidia
              count: 1
              capabilities: [gpu]

I've been working on a bunch of stuff lately, and I'm going to be recording some of the annoyances and fixes in the near future.

For now, it's Docker and getting access to Nvidia cards in containers.

For starters, just use Ubuntu Desktop. I know it sucks running a desktop for servers, but in this case the Desktop installer allows you to install the Nvidia proprietary drivers. I had no luck getting the proprietary drivers working on Ubuntu Server.

Step 1: Install Ubuntu Desktop and make sure to select the proprietary Nvidia driver.
Step 2: Verify nvidia-smi has the correct card(s) listed.
Step 3: Run the script below. Sourced from the Docker and Nvidia sites.

Edit: added nvidia-docker2 to the installed Nvidia software

# Add Docker's official GPG key:
sudo apt-get update
sudo apt-get install ca-certificates curl
sudo install -m 0755 -d /etc/apt/keyrings

sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc
sudo chmod a+r /etc/apt/keyrings/docker.asc

# Add the repository to Apt sources:
echo \
"deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/ubuntu \
 $(. /etc/os-release && echo "$VERSION_CODENAME") stable" | \
sudo tee /etc/apt/sources.list.d/docker.list > /dev/null

sudo apt-get update

sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

curl -fsSL https://nvidia.github.io/libnvidia-container/gpgkey | sudo gpg --dearmor -o /usr/share/keyrings/nvidia-container-toolkit-keyring.gpg \

  && curl -s -L https://nvidia.github.io/libnvidia-container/stable/deb/nvidia-container-toolkit.list | \

sed 's#deb https://#deb [signed-by=/usr/share/keyrings/nvidia-container-toolkit-keyring.gpg] https://#g' | \
sudo tee /etc/apt/sources.list.d/nvidia-container-toolkit.list

sudo apt-get update
sudo apt-get install -y nvidia-container-toolkit nvidia-docker2

@gjacobse Now that I think about it, you might want to try a bios reset on the iDRAC. I don't know if that will make a difference, but it's corrected issues with them for me in the past.

@gjacobse said in Dell r720 and Hitachi Drive:

iDRAC -

Ended up being short lived excitement when I came in last night to see that I could access the LifeCycle controller and was able to get the iDRAC connected.

Used the reboot option and that was it I suppose... Back to LifeCycle controller being disabled and the iDRAC being inaccessible.

Odd also is that it seems to only allow one of the four main NICs over the iDRAC NIC - Has it been so long since I worked on something at this level that I've misconstrued some information on how the iDRAC NIC is suppose to work/

iDRAC normally has a NIC separate from all the others. Some utilize the same NIC as the main system, but those are the jank version. My R620 iDRAC is a physically separate network port, and all the servers at work are as well.

@gjacobse said in Dell r720 and Hitachi Drive:

Specs:
Dell r720 surplused
Hitachi HUC106060css600 512 drives

I admit - I've realized that the last server I had to physically touch was likely back in 2009. While I have worked with systems, I've not had to build or rebuild an array in a very long time. So I am a tad rusty.

System does see these drives - I have a full complement of sixteen to fully populate the two bays. However I have run into a slight issue with these drives I hadn't had to work with previously as technology has changed.

These drives are per the details above 512/512e and the r720 doesn't want to 'accept' them. While the PERC does see them, they are all marked as BLOCKED.

Now, I understand that sector size is set and cannot be changed - I rather expected to find the correct firmware needed to update the PERC to allow these drives to be used...

I do see that Dell has the driver for this drive - but reading the details about it seems to point at an OS side issue and not the PERC.

I fully expect that I am simply overlooking the solution because I am looking at or for the wrong information.

Are you looking at the PERC bios screen? If it's in standard RAID mode, that's where you need to setup the array.

Hotkeys are always different. If you have access to the iDRAC, you should be able to boot directly into the RAID bios from that. I have an even older R620 still in use as my home lab box, and that's normally how I access the PERC bios when needed.

You're reminding me that I really should see about upgrading my home lab box.