Dgx spark just does boot loop.
Gets to this then after 19 to 20 minutes reboots.
No networking at all, wired or wireless.
Not sure what to do.
I can echo here, this is probably what’s going on with me as well. I logged onto the spark’s wifi and completed the software update. After it reported it was ready to run I started on the nvidia sync steps because I’m connecting by ssh. I tried the hotstpot ssid, hostname, ran arp -a to try the ip address – and got either a timeout or unable to find each time. Then I tried regular ssh from the terminal… and saw the device couldn’t be found. Then I checked the wifi again and saw it was gone. So I restarted the spark and waited 15 minutes… nothing. Restarted again waiting 30 minutes… and nothing again.
I’m hopeful I don’t have to burn a recovery stick, but this is not a great start. The machine itself starts: I can hear its fan, but that’s it.
I am facing the exact same issue. I started the network device setup and the update completed. After that, I no longer could see the Spark WiFi SSID.
So I hooked it up to a monitor and booting normally on GRUB takes me to a blank screen. If I try one of the recovery options in GRUB, it logs something that ends with “md: … autorun DONE” and stays stuck.
I made a recovery USB stick and tried booting into that. When I plug in the recovery USB and boot, there is no video output (I tried an HDMI cable and a USB-C to HDMI cable).
So I’m also stuck with a non-bootable machine.
Will restart after 10pm per notice just posted.
@wpolatkan & @rp_37716 We have an active issue we are working to resolve. The fix will be live at 7 PM PST. To recover your system you will need recover using the following steps. Please do not attempt to reflash your system until after 7 PM PST. Thank you for your patience.
Update: I recreated the recovery USB on a Mac and that fixed the above error.
We are actively working on the fix and will continue to keep you updated. Thank you for your patience.
The next update will be available at 8:30 PM PST.
We will provide the next update at ~11 PM PST.
** ACTIVE ISSUE - DO NOT ATTEMPT UPDATES OR SETUP **
This issue is now resolved, users can go ahead with the updates.
No joy on fixing the boot loop. I have created the USB recovery in both Windows and Linux and I get the same issue of not mounting /dev/sda1 on /mnt/usb. This entire escapade is rather ridiculous between immediately borking most folks new system, and having what seems to be a finicky recovery. Any one else find their way out of this? I have been able to boot to the original recovery image, even with networking, but manual efforts to run updates die because of conflicts with the problematic files from the original update.
I did the usb restore and finally got to enter timezone, keyboard, etc. Then said was done and rebooted , then rebooted again and appeared to power off. I captured boot process with my phone, but can’t tell what going on.
So at this time i have expensive brick…… :(
Is there anything special or different about your setup? What type of monitor, keyboard, network connection are you using? When did you try your latest restore, on October 17th? What region are you in?
No, usa, eastern tz keyboard works ok, is old USB with mouse attached to old unpowered USB hub via USBC to USB adapter I already had.
. Restore from image this morning the 17th. Could not reset keys (user mode) and it failed like this, then changed to custom and did restore keys and still fails.
What did you mean by “reset keys” and “custom mode”? I am also EST and have reimaged several times. After you did the TZ and user it should do some updates and reboot. It sounds like you are seeing the issue after the updates? You never get the login scren again?
No, never get logon screen. When doing restore it says (restore factory keys) from boot recovery document
Enable Secure Boot:
Use the Right Arrow key to select “Security”
Confirm that “Secure Boot” is set to “Enabled”
Select “Restore Factory Keys”
Use the arrow keys to select the “Save and Exit” BIOS screen, and select “Save Changes and Reset”
redid everything this morning and all is working fine. so no brick….. YEAH!!!.
p.s. I did it headless this time, which I also did yesterday…..