Start a Conversation

Unsolved

MD

1 Rookie

 • 

31 Posts

320

March 1st, 2024 21:04

Where can I find onie-installer-x86_64-dell_s6100_c2538-r0.bin ?

I have a Dell S6100-ON I want to upgrade. I've downloaded the bin files for FTOS and ONIE from the support site. I've upgraded FTOS, and now want to upgrade ONIE. However, to upgrade ONIE, I apparently need onie-installer-x86_64-dell_s6100_c2538-r0 (according to the release notes). I cannot find this file anywhere. Where can I get this file?

Alternatively, when I have downloaded ONIE-FTOS-S6100-ON-9.14.2.21.bin from the support site, how to I apply it to the switch (without the aforementioned installer)?

Moderator

 • 

3.9K Posts

March 4th, 2024 04:15

Hi,

 

I'm unsure of onie-installer-x86_64-dell_s6100_c2538-r0, you can find onie-updater-x86_64-dell_s6100_c2538-r0.3.25.1 in the zip file of https://dell.to/439fHKr. Would you mind sharing which release note that you mentioned. 

 

You can refer to the release note of Dell System S6100–ON 9.14(2.21) https://dell.to/4303pUu to install ONIE-FTOS-S6100-ON-9.14.2.21.bin

 

 

1 Rookie

 • 

31 Posts

March 22nd, 2024 12:41

Those were the release notes I was referring to.

If you refer page 8, you will see Step 7 states:

"Enter the following command to upgrade ONIE:ONIE:/ # onie-self-update tftp://<tftp-server–address>/ onie-updater-x86_64-s6100_c2538-r0."

where is the file "onie-updater-x86_64-s6100_c2538-r0" located? It isn't in the files for the S6100-ON. The only three files listed are the release notes PDF, a "FTOS-S6100-ON-9.14.2.21.bin" and "ONIE-FTOS-S6100-ON-9.14.2.21.bin"

Or, is this step unnecessary?

Where does one locate the latest ONIE and DIAG images? For example, the release notes indicate on page 11 there is an "diag-installer-x86_64-dell_s6100_c2538-r0.3.25.4.1.bin" file, but this file appears nowhere in the downloads for the S6100 that I can find.

Moderator

 • 

9.4K Posts

March 22nd, 2024 13:43

Mike Deignan,
 
The files you need for them are found below.

The diag is here

The image is here-

Now you will need to extract the files, but the updates needed are within. 
 
Let me know if this helps.
 
 

1 Rookie

 • 

5 Posts

June 4th, 2025 20:58

Hello !

All of the above links are broken.

https://dell.to/error?url=4apA7Bf
https://dell.to/error?url=498dSPa
https://dell.to/error?url=439fHKr

I have a Dell PowerSwitch S6010-ON, the sata drive went bad and now I put a blank one in. 

I need to first install onie on it, and then have onie install Dell NetworkOS9

I found the following document, but I'm not sure what exactly I need to get first

Dell Configuration Guide for the S6010–ON System 9.14.2.6 

https://www.dell.com/support/manuals/en-ca/dell-emc-os-9/s6010-on-9.14.2.6-config-pub/restoring-the-factory-default-settings?guid=guid-7026c4b6-93ce-4ad9-afde-a48761718bf5&lang=en-us

Dell PowerSwitch S6010-ON Release Notes

https://dl.dell.com/FOLDER08835877M/1/s6010_on_rn.pdf?uid=fbbb1e49-712c-4055-41c5-65e5354dfd7c&fn=s6010_on_rn.pdf

Dell PowerSwitch S6010-ON ONIE Firmware
Updater Release Notes

https://dl.dell.com/FOLDER08835876M/1/s6010_on_fw_updater.pdf?uid=abbbf5d7-7e23-40a7-a1a8-02e1b0ff684c&fn=s6010_on_fw_updater.pdf

Support for PowerSwitch S6010-ON
https://www.dell.com/support/product-details/en-ca/product/networking-s6010-on/drivers

I think for ONIE I need

Dell Networking Firmware Updater V3.26.5.0-8 for S6010-ON

https://dl.dell.com/FOLDER08835876M/1/s6010_on_fw_updater.pdf

View full driver details

https://www.dell.com/support/home/en-ca/drivers/driversdetails?driverid=5909h&oscode=naa&productcode=networking-s6010-on

ONIE Software V3.26.1.0-4 for Dell Networking S6010-ON Switch

https://dl.dell.com/FOLDER08835877M/1/s6010_on_rn.pdf

View full driver details

https://www.dell.com/support/home/en-ca/drivers/driversdetails?driverid=hf0fk&oscode=naa&productcode=networking-s6010-on

There is also 


Dell Networking Operating System, OS9, v9.14.1.14

https://dl.dell.com/FOLDER09244157M/1/ONIE-FTOS-S6010-9.14.1.14.bin

Dell Networking Operating System, OS9, V9.14.2.23

https://dl.dell.com/FOLDER11389344M/1/ONIE-FTOS-S6010-9.14.2.23.bin

There is also 

Dell OpenManage Enterprise Services, v3.0.1
Innodisk Solid-State Drive Firmware Update for 3IE3, v3.00.7.0-1
Dell Networking Diagnostic OS V3.26.3.3 for S6010 Open Networking Switch
Dell Networking Diagnostic Tools V3.26.4.2 for S6010 Open Networking 

I don't know if I need these or not 

1 Rookie

 • 

5 Posts

June 4th, 2025 21:05

Here are the files I have accumulated

The Dell S6010-ON switch appears to require an EFI boot drive ?

I also have a Dell S4048-ON, I tried to put its SATA drive into the S6010-ON but it failed to boot and went into the EFI shell (as opposed to hanging with the defective sata ssd)

I think I need to 

either flash a bin to the whole drive

of create ONIE partitions, then flash the bin to the ONIE partition

then usb boot something and with that chroot into the installed ONIE system and restore the boot loader

then boot the ONIE partition and then somehow serve the bin file to ONIE so it can install it

ONIE-FTOS-S6010-9.14.2.23.bin

or

ONIE-FTOS-S6010-9.14.1.14.bin

And lastly boot this newly created partition

1 Rookie

 • 

5 Posts

June 4th, 2025 21:08

Here is the partition table from the defective SATA SSD.

A hybrid GPT was detected. You have to sync the hybrid MBR manually (expert command 'M').

Command (m for help): p

Disk /dev/sdc: 14.91 GiB, 16013942784 bytes, 31277232 sectors
Disk model: USB 3.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Device       Start      End  Sectors  Size Type
/dev/sdc1     2048     6143     4096    2M BIOS boot
/dev/sdc2     6144   268287   262144  128M ONIE boot
/dev/sdc3   268288  2365439  2097152    1G Linux filesystem
/dev/sdc4  2365440  2430975    65536   32M Linux filesystem
/dev/sdc5  2430976  3454975  1024000  500M Linux filesystem
/dev/sdc6  3454976  4478975  1024000  500M Linux filesystem
/dev/sdc7  4478976 31277198 26798223 12.8G NetBSD FFS

There is also a protective MBR disklabel as follows

Command (m for help): M
Entering protective/hybrid MBR disklabel.

Command (m for help): p
Disk /dev/sdc: 14.91 GiB, 16013942784 bytes, 31277232 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x5c29bce1

Device     Boot   Start      End  Sectors  Size Id Type
/dev/sdc1             1  2365439  2365439  1.1G ee GPT
/dev/sdc2  *    2365440  2430975    65536   32M  6 FAT16
/dev/sdc3       2430976  3454975  1024000  500M  6 FAT16
/dev/sdc4       4478976 31277198 26798223 12.8G a9 NetBSD

Partition 1 does not start on physical sector boundary.

I don't know what or where the bootloader is supposed start from

1 Rookie

 • 

5 Posts

June 4th, 2025 23:23

Ok I think I have been able to re-create the partition table

root@proxmox:~# DEVICE=/dev/sdb
root@proxmox:~# parted $DEVICE --script mklabel gpt
root@proxmox:~# parted $DEVICE  --script unit s mkpart primary 2048 6143          # 2M BIOS boot
root@proxmox:~# parted $DEVICE --script set 1 bios_grub on
root@proxmox:~# parted $DEVICE --script unit s mkpart primary 6144 268287        # 128M ONIE boot
root@proxmox:~# parted $DEVICE --script name 2 "ONIE-BOOT"
root@proxmox:~# parted $DEVICE --script unit s mkpart primary 268288 2365439     # 1G Linux FS
root@proxmox:~# parted $DEVICE --script unit s mkpart primary 2365440 2430975    # 32M Linux FS
root@proxmox:~# parted $DEVICE --script unit s mkpart primary 2430976 3454975    # 500M Linux FS
root@proxmox:~# parted $DEVICE --script unit s mkpart primary 3454976 4478975    # 500M Linux FS
root@proxmox:~# parted $DEVICE --script unit s mkpart primary 4478976 31277198   # 12.8G NetBSD FFS

root@proxmox:~# sgdisk --typecode=2:7412f7d5-a156-4b13-81dc-867174929325 $DEVICE
The operation has completed successfully.
root@proxmox:~# sgdisk --typecode=7:49f48d5a-b10e-11dc-b99b-0019d1879648 $DEVICE
The operation has completed successfully.

Result


root@proxmox:~# fdisk /dev/sdb

Welcome to fdisk (util-linux 2.38.1).
Command (m for help): p
Disk /dev/sdb: 119.24 GiB, 128035676160 bytes, 250069680 sectors
Disk model: USB 3.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Device       Start      End  Sectors  Size Type
/dev/sdb1     2048     6143     4096    2M BIOS boot
/dev/sdb2     6144   268287   262144  128M ONIE boot
/dev/sdb3   268288  2365439  2097152    1G Linux filesystem
/dev/sdb4  2365440  2430975    65536   32M Linux filesystem
/dev/sdb5  2430976  3454975  1024000  500M Linux filesystem
/dev/sdb6  3454976  4478975  1024000  500M Linux filesystem
/dev/sdb7  4478976 31277198 26798223 12.8G NetBSD FFS

It remains to create the Hybrid GPT partition table

1 Rookie

 • 

5 Posts

June 4th, 2025 23:41

Here is how I created the Hybrid GPT partition table

root@proxmox:~# gdisk $DEVICE
GPT fdisk (gdisk) version 1.0.9

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): r

Recovery/transformation command (? for help): ?
b       use backup GPT header (rebuilding main)
c       load backup partition table from disk (rebuilding main)
d       use main GPT header (rebuilding backup)
e       load main partition table from disk (rebuilding backup)
f       load MBR and build fresh GPT from it
g       convert GPT into MBR and exit
h       make hybrid MBR
i       show detailed information on a partition
l       load partition data from a backup file
m       return to main menu
o       print protective MBR data
p       print the partition table
q       quit without saving changes
t       transform BSD disklabel partition
v       verify disk
w       write table to disk and exit
x       extra functionality (experts only)
?       print this menu

Recovery/transformation command (? for help): h

WARNING! Hybrid MBRs are flaky and dangerous! If you decide not to use one,
just hit the Enter key at the below prompt and your MBR partition table will
be untouched.

Type from one to three GPT partition numbers, separated by spaces, to be
added to the hybrid MBR, in sequence: 2 3 7
Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N): y

Creating entry for GPT partition #2 (MBR partition #2)
Enter an MBR hex code (default 30): 06
Set the bootable flag? (Y/N): y

Creating entry for GPT partition #3 (MBR partition #3)
Enter an MBR hex code (default 83): 83
Set the bootable flag? (Y/N): n

Creating entry for GPT partition #7 (MBR partition #4)
Enter an MBR hex code (default A9): A9
Set the bootable flag? (Y/N): n

Recovery/transformation command (? for help): w

Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/sdb.
The operation has completed successfully.

Moderator

 • 

3.9K Posts

June 5th, 2025 04:57

Hi,

 

The drive is not a replaceable hardware and there isn't a documented instruction on how to prepare the drive for ONIE and firmware installation. But here is a reference on how to install ONIE: https://infohub.delltechnologies.com/static/media/client/7phukh/57ae5efd-8700-40e4-a268-37a88b6763fc.pdf or if you have a spare switch, you can create a livedisk for restore: https://www.dell.com/support/kbdoc/en-my/000213926/creating-onie-recovery-livedisk

 

 

 

No Events found!

Top