DGX Spark System Recovery completes with errors, then boots to grub>

Hello,
I have a DGX Spark that initially failed during first boot setup with the Wi-Fi error:

“Error searching for nearby networks. Reason: 500”

I then tried to restore the system using the official DGX Spark System Recovery procedure.

What I tried:

  1. Downloaded the official DGX Spark System Recovery Image.
  2. Created the recovery USB on macOS using CreateUSBKeyMacOS.sh.
  3. Ran System Recovery.
  4. Recovery Environment appeared to complete, but after reboot the system dropped to the `grub>` prompt.
  5. Re-created the recovery USB on Windows using CreateUSBKey.cmd.
  6. Downloaded the recovery .tar.gz again directly on the Windows PC and recreated the USB.
  7. Restored UEFI defaults.
  8. Confirmed Secure Boot is enabled.
  9. Restored Factory Keys.
  10. Booted the recovery USB through UEFI Boot Override.
  11. Recovery still ends with filesystem/GRUB-related errors.
  12. After reboot, UEFI shows an `ubuntu` boot entry, but selecting it still drops to `grub>`.

During recovery, I saw the following errors:

  • `e2fsck: aborted`
  • `resize2fs: inode bitmap checksum does not match bitmap while trying to resize /dev/nvme0n1p2`
  • `mount: mounting /dev/nvme0n1p2 on /mnt/disk/data failed: Invalid argument`
  • `can’t create /mnt/disk/data/etc/fstab: nonexistent directory`
  • `can’t cd to /mnt/disk/data/boot/grub: No such file or directory`
  • `Error: grub.cfg file not found`

Although the screen eventually says “Recovery command completed”, it looks like the recovery fails before the root filesystem is mounted and before grub.cfg is generated.

My questions:

  1. Is this a known issue with the DGX Spark recovery image?
  2. Does the `resize2fs` / inode bitmap checksum error indicate an internal NVMe/storage issue?
  3. Is there a way to manually repair the EFI/GRUB configuration?
  4. Should this unit be treated as defective and sent for RMA/replacement?

I can provide a photo of the recovery log showing the errors.

Thanks.

Sorry you are experiencing this. A photo of the errors would be greatly appreciated. I will confer with our engineering team if there is a way to recover your system, in the meantime, please run a NVMe self test in the UEFI menu to see if there is an issue there, as seen here: Advanced Tab — DGX Spark UEFI User Guide

Here is the recovery failure log.

Also, I ran the NVMe Extended Self Test, and the result was Pass. I have also contacted the supplier and am waiting for their response.

Thank you for the screenshot. A couple questions from engineering:

  1. Do the same errors appear when using both the MacOS script and the Windows script?
  2. Did you attempt to modify the NVMe somehow, maybe with a 4k sector one?
  1. I initially ran the macOS script. At the end, I only saw the “Completed” message, so I assumed it had finished successfully. However, after rebooting, the system showed the grub> prompt.

    While investigating, I found that there seem to be many issues with the macOS script. So I recreated the recovery USB on Windows and ran the recovery again. On the second attempt, I checked the logs more carefully and noticed those errors. After that, the grub> prompt still appeared in the same way.

  2. I do not even know how to modify the NVMe, and I have never modified it.

For now, the supplier’s technical support team said they will collect the device and inspect it. If needed, I will also share this information with their technical support team.