Still unable to create recovery image on Mac OS

Accelerated Computing DGX Spark / GB10 User Forum DGX Spark / GB10
1

I still can’t get it working with the latest recovery image upload: dgx-spark-recovery-image-1.91.51-1.tar.gz

For me, it seems like it’s not applying the partitions correctly, as my USB starts off with a NO NAME partition, and never gets the BOOTME partition, it’s as if it just doesn’t update it. Output below:

 /==================================\
 || _____         _    ___  ____   ||
 |||  ___|_ _ ___| |_ / _ \/ ___|  ||
 ||| |_ / _  / __| __| | | \___ \  ||
 |||  _| (_| \__ \ |_| |_| |___) | ||
 |||_|  \__,_|___/\__|\___/|____/  ||
 \==================================/
 For DGX Spark

FastOS Image Version:
NAME="DGX SPARK FASTOS"
DATE="2025-10-10T03:26:29+00:00"
VERSION="1.91.51"
BUILD_TYPE="customer"

Looking for external disks...
Select the USB disk to format (this will ERASE it):

  1) /dev/disk4 — 61.5 GB — SanDisk 3.2Gen1

Enter the number [1-1] and press Enter: 1

You selected: /dev/disk4 — 61.5 GB — SanDisk 3.2Gen1
WARNING: THIS OPERATION WILL ERASE ALL DATA ON THE DISK.
Type 'YES' (uppercase) to continue: YES

[1/5] Unmounting volumes of /dev/disk4...
[2/5] Creating partition map and FAT32 volume 'BOOTME'...
Started partitioning on disk4
Unmounting disk
Creating the partition map
Waiting for partitions to activate
Formatting disk4s1 as MS-DOS (FAT32) with name BOOTME
512 bytes per physical sector
/dev/rdisk4s1: 60517280 sectors in 1891165 FAT32 clusters (16384 bytes/cluster)
bps=512 spc=32 res=32 nft=2 mid=0xf8 spt=32 hds=255 hid=2048 drv=0x80 bsec=60546880 bspf=14775 rdcl=2 infs=1 bkbs=6
Mounting disk
Finished partitioning on disk4
/dev/disk4 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *61.5 GB    disk4
   1:                 DOS_FAT_32 NO NAME                 31.0 GB    disk4s1
                    (free space)                         30.5 GB    -
[3/5] Ensuring the BOOTME volume is mounted...
Error: Could not mount the BOOTME volume.
2

To follow up on this, it seems like it is creating a 32GB partition, but its name is always NO NAME. I’m going to try manually renaming it to BOOTME while it waits for the partition to mount and see what happens. ¯\(°_o)/¯

3

So I manually renamed it to BOOTME, and that seems to work as a workaround if anyone else runs into this… I did get a warning though, so I guess the verdict is out on whether this could affect the functionality:

[3/5] Ensuring the BOOTME volume is mounted...

[4/5] Copying files from:
  /Users/francois/Desktop/usbimg.customer/usb
to:
  /Volumes/BOOTME

Using rsync with progress...
rsync(2219): warning: /Volumes/BOOTME//./.Spotlight-V100: unreadable directory: Operation not permitted
./
efi.tar.xz
        1709972 100%   23.97MB/s   00:00:00 (xfer#1, to-check=1/261)
fastos-release.txt
             97 100%  261.05KB/s   00:00:00 (xfer#2, to-check=2/261)
fastos.partaa
     4089446400 100%   12.94MB/s   00:05:01 (xfer#3, to-check=3/261)
4

It boots with the workaround above, however, now running into the same issue others have run into where Mac wired keyboards do not function in the recovery environment, so there’s no way to proceed and actually do a recovery.

5

Do you have a mouse connected to the keyboard? Probably try unplug the mouse and it might work. It seems not all Linux system has support for Apple’s Keyboard and mouse special USB protocol.