Dell Nautilus firmware update utilitiy on non-dell systems?

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

111alan

Active Member
Mar 11, 2019
343
135
43
Haerbing Institution of Technology
I have a Dell DC S3610 1.6TB with firmware DL2B. I noticed that there are DL2D and DL2E firmwares which both featured critical fixes that could prevent the drive from bricking so I went to update. First, the stand-alone update utility didn't work, so I did some research and found this post:

@JediGhost talked about the Dell Nautilus utility, which he said could run on non-dell systems without a RAID card(including HBA?). So I went to try it, then encountered two kinds of errors. One EPYC3 platform the error code is 8903 while on Xeon 8100 and Z97 platform the error code is 0151.

Wondering what went wrong here? And has anyone successfully updated the drives using Nautilus? Want to know on what platforms have the update been successful, or whether it's hardware-dependant or not, if anyone has the experience.

Thank you.
S3610-2.JPGS3610-1.JPG
 
  • Like
Reactions: Aluminat

Propaganda

Active Member
Dec 6, 2017
154
62
28
46
I don't have those specific systems at my house but I could try running nautilus on the same drives on a non dell system tonight. I updated my dell 1.6tb s3610 using nautilus in an r720 modded with hba330 card.
 

111alan

Active Member
Mar 11, 2019
343
135
43
Haerbing Institution of Technology
I don't have those specific systems at my house but I could try running nautilus on the same drives on a non dell system tonight. I updated my dell 1.6tb s3610 using nautilus in an r720 modded with hba330 card.
It would be so kind of you if you could try this for me :) Also someone liked this topic, perhaps he encountered the same problem too? @Aluminat
 
Last edited:

Propaganda

Active Member
Dec 6, 2017
154
62
28
46
I was able to run the "Nautilus SAS-SATA EFI A22.iso" which I flashed on to a usb drive with Etcher. Etcher did complain about no boot partition found but I flashed anyway and it seemed to work fine. Found and evaluated both my 200GB Intel/HP S3710 and the 1.6TB Intel/Dell S3610. Test system was a x399 Asrock Taichi with 1950x utilizing the onboard sata ports in ahci mode.
I did originally try this on my HP G8 Microserver, in hindsight I should have remembered it can't boot uefi so it obviously didn't boot at all there. Most of the older Nautilus releases that aren't uefi don't appear to contain most of the firmware of the newer releases.
Proof:

dn.jpg
 
  • Like
Reactions: 111alan

111alan

Active Member
Mar 11, 2019
343
135
43
Haerbing Institution of Technology
I was able to run the "Nautilus SAS-SATA EFI A22.iso" which I flashed on to a usb drive with Etcher. Etcher did complain about no boot partition found but I flashed anyway and it seemed to work fine. Found and evaluated both my 200GB Intel/HP S3710 and the 1.6TB Intel/Dell S3610. Test system was a x399 Asrock Taichi with 1950x utilizing the onboard sata ports in ahci mode.
I did originally try this on my HP G8 Microserver, in hindsight I should have remembered it can't boot uefi so it obviously didn't boot at all there. Most of the older Nautilus releases that aren't uefi don't appear to contain most of the firmware of the newer releases.
Proof:

View attachment 26557
Thank you very much for trying! I was using the UsbMake.exe in the package to create the boot disk. I'll try if Etcher could make any difference.
 

111alan

Active Member
Mar 11, 2019
343
135
43
Haerbing Institution of Technology
I was able to run the "Nautilus SAS-SATA EFI A22.iso" which I flashed on to a usb drive with Etcher. Etcher did complain about no boot partition found but I flashed anyway and it seemed to work fine. Found and evaluated both my 200GB Intel/HP S3710 and the 1.6TB Intel/Dell S3610. Test system was a x399 Asrock Taichi with 1950x utilizing the onboard sata ports in ahci mode.
I did originally try this on my HP G8 Microserver, in hindsight I should have remembered it can't boot uefi so it obviously didn't boot at all there. Most of the older Nautilus releases that aren't uefi don't appear to contain most of the firmware of the newer releases.
Proof:

View attachment 26557
Still a no go. Exactly the same error I got before. I'll see if I can get some other motherboards to try on.
 

name stolen

Active Member
Feb 20, 2018
135
40
28
Use Rufus to write the update ISO to a bootable USB. This just worked for me on a self built Asus X370 Ryzen system. Updating Dell SATA drives on a non_Dell system. Rufus complained but it worked anyway.