6100 Max running 24.03 RC unable to update firmware

stephenw10

Hmm, interesting. Can I assume you didn't try updating it from 21.09.1? Are you able to roll back to a 23.09.1 BE and test that?

jonathan.rupp

@stephenw10

Correct this is a lab system and ran 24.03-Beta since it was released.

Rollback is not an option, unfortunately.

The unit was just recently reinstalled using the Netgate Install package, as it was not on ZFS.

stephenw10

Can we see the output from gpart list there?

jonathan.rupp

@stephenw10

Geom name: nda0
modified: false
state: OK
fwheads: 255
fwsectors: 63
last: 234441607
first: 40
entries: 128
scheme: GPT
Providers:
1. Name: nda0p1
   Mediasize: 272629760 (260M)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 20480
   Mode: r0w0e0
   efimedia: HD(1,GPT,0e2c316b-f072-11ee-8d18-90ec772121fe,0x28,0x82000)
   rawuuid: 0e2c316b-f072-11ee-8d18-90ec772121fe
   rawtype: c12a7328-f81f-11d2-ba4b-00a0c93ec93b
   label: efiboot1
   length: 272629760
   offset: 20480
   type: efi
   index: 1
   end: 532519
   start: 40
2. Name: nda0p2
   Mediasize: 524288 (512K)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 272650240
   Mode: r0w0e0
   efimedia: HD(2,GPT,0e34e1db-f072-11ee-8d18-90ec772121fe,0x82028,0x400)
   rawuuid: 0e34e1db-f072-11ee-8d18-90ec772121fe
   rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f
   label: (null)
   length: 524288
   offset: 272650240
   type: freebsd-boot
   index: 2
   end: 533543
   start: 532520
3. Name: nda0p3
   Mediasize: 1073741824 (1.0G)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 276824064
   Mode: r1w1e1
   efimedia: HD(3,GPT,0e3be6bd-f072-11ee-8d18-90ec772121fe,0x84000,0x200000)
   rawuuid: 0e3be6bd-f072-11ee-8d18-90ec772121fe
   rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b
   label: swap1
   length: 1073741824
   offset: 276824064
   type: freebsd-swap
   index: 3
   end: 2637823
   start: 540672
4. Name: nda0p4
   Mediasize: 118682025984 (111G)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 1350565888
   Mode: r1w1e1
   efimedia: HD(4,GPT,0e40924c-f072-11ee-8d18-90ec772121fe,0x284000,0xdd10000)
   rawuuid: 0e40924c-f072-11ee-8d18-90ec772121fe
   rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b
   label: (null)
   length: 118682025984
   offset: 1350565888
   type: freebsd-zfs
   index: 4
   end: 234438655
   start: 2637824
Consumers:
1. Name: nda0
   Mediasize: 120034123776 (112G)
   Sectorsize: 512
   Mode: r2w2e4

Geom name: da0
modified: false
state: OK
fwheads: 255
fwsectors: 63
last: 60628991
first: 1
entries: 4
scheme: MBR
Providers:
1. Name: da0s1
   Mediasize: 34091008 (33M)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 512
   Mode: r0w0e0
   efimedia: HD(1,MBR,0x90909090,0x1,0x10418)
   rawtype: 239
   length: 34091008
   offset: 512
   type: efi
   index: 1
   end: 66584
   start: 1
2. Name: da0s2
   Mediasize: 1667604480 (1.6G)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 34091520
   Mode: r0w0e0
   efimedia: HD(2,MBR,0x90909090,0x10419,0x31b2d0)
   attrib: active
   rawtype: 165
   length: 1667604480
   offset: 34091520
   type: freebsd
   index: 2
   end: 3323624
   start: 66585
3. Name: da0s3
   Mediasize: 67108864 (64M)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 1701696000
   Mode: r0w0e0
   efimedia: HD(3,MBR,0x90909090,0x32b6e9,0x20000)
   rawtype: 11
   length: 67108864
   offset: 1701696000
   type: fat32
   index: 3
   end: 3454696
   start: 3323625
Consumers:
1. Name: da0
   Mediasize: 31042043904 (29G)
   Sectorsize: 512
   Mode: r0w0e0

Geom name: da0s2
modified: false
state: OK
fwheads: 255
fwsectors: 63
last: 3257039
first: 0
entries: 8
scheme: BSD
Providers:
1. Name: da0s2a
   Mediasize: 1667596288 (1.6G)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 34099712
   Mode: r0w0e0
   rawtype: 7
   length: 1667596288
   offset: 8192
   type: freebsd-ufs
   index: 1
   end: 3257039
   start: 16
Consumers:
1. Name: da0s2
   Mediasize: 1667604480 (1.6G)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 34091520
   Mode: r0w0e0

stephenw10

Hmm, do you have a USB drive attached to it?

A 6100-MAX would normally have disks nda0 and mmcsd0. Your's appears to not have the eMMC but does have a da0 device.

jonathan.rupp

@stephenw10

That’s the strange thing. There’s nothing but stock drives and no attachments.

stephenw10

Hmm. Well that's odd!

Do you see the mmcsd device in the boot log?

[24.03-RC][admin@6100-3.stevew.lan]/root: dmesg | grep mmc
mmc0: <MMC/SD bus> on sdhci_pci0
mmcsd0: 16GB <MMCHC TB2916 9.0 SN 28E9728E MFG 09/2020 by 112 0x0000> at mmc0 50.0MHz/8bit/65535-block
mmcsd0boot0: 4MB partition 1 at mmcsd0
mmcsd0boot1: 4MB partition 2 at mmcsd0
mmcsd0rpmb: 4MB partition 3 at mmcsd0

jonathan.rupp

@stephenw10

mmc0: <MMC/SD bus> on sdhci_pci0
mmcsd0: 16GB <MMCHC TB2916 9.0 SN 5A5A608C MFG 08/2021 by 112 0x0000> at mmc0 50.0MHz/8bit/65535-block
mmcsd0boot0: 4MB partition 1 at mmcsd0
mmcsd0boot1: 4MB partition 2 at mmcsd0
mmcsd0rpmb: 4MB partition 3 at mmcsd0

Tried rebooting and reinstalling, same error.

stephenw10

And still no mmcsd0 device in the geom output?

stephenw10

Hmm, what does: dmesg | grep da0 show?

jonathan.rupp

@stephenw10

nda0 at nvme0 bus 0 scbus0 target 0 lun 1
nda0: <M.2 (P80) 3TE6 V20B09 YCA12109270110123>
nda0: Serial Number YCA12109270110123
nda0: nvme version 1.3
nda0: 114473MB (234441648 512 byte sectors)
da0 at umass-sim0 bus 0 scbus1 target 0 lun 0
da0: <PNY USB 3.2.1 FD PMAP> Removable Direct Access SPC-4 SCSI device
da0: Serial Number 071828D6D5486E38
da0: 400.000MB/s transfers
da0: 29604MB (60628992 512 byte sectors)
da0: quirks=0x2<NO_6_BYTE>

jonathan.rupp

@stephenw10

Geom Class Provider
mmcsd0 DISK mmcsd0
mmcsd0 DEV
mmcsd0boot0 DISK mmcsd0boot0
mmcsd0boot0 DEV
mmcsd0boot1 DISK mmcsd0boot1
mmcsd0boot1 DEV
nda0 DISK nda0
nda0 DEV
nda0 PART nda0p1
nda0p1 DEV
nda0p1 LABEL gpt/efiboot1
gpt/efiboot1 DEV
nda0p1 LABEL msdosfs/EFISYS
msdosfs/EFISYS DEV
nda0 PART nda0p2
nda0p2 DEV
nda0 PART nda0p3
nda0p3 DEV
nda0p3 LABEL gpt/swap1
gpt/swap1 DEV
swap SWAP
nda0 PART nda0p4
nda0p4 DEV
zfs::vdev ZFS::VDEV
da0 DISK da0
da0 DEV
da0 PART da0s1
da0s1 DEV
da0 PART da0s2
da0s2 DEV
da0s2 PART da0s2a
da0s2a DEV
da0s2a LABEL ufsid/65f0033358586c91
ufsid/65f0033358586c91 DEV
da0s2a LABEL ufs/pfSense_Install
ufs/pfSense_Install DEV
da0 PART da0s3
da0s3 DEV
da0s3 LABEL msdosfs/PFSENSE
msdosfs/PFSENSE DEV

stephenw10

Ok that da0 device is non-standard. It's USB attached. If it's not an actual USB drive is it perhaps a card in the SIM slot?

It's somehow booting from that though and confusing the firmware updater. You should remove it. You may need to reinstall though if the nvme drive doesn't contain a valid install.

jonathan.rupp

@stephenw10

No USBs and nothing in the SIM slot.

stephenw10

Ok check the output of: usbconfig dump_device_desc

On a 6100-MAX with nothing connected that should look like:

[24.03-RC][admin@6100-3.stevew.lan]/root: usbconfig dump_device_desc
ugen0.1: <Intel XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA)

  bLength = 0x0012 
  bDescriptorType = 0x0001 
  bcdUSB = 0x0300 
  bDeviceClass = 0x0009  <HUB>
  bDeviceSubClass = 0x0000 
  bDeviceProtocol = 0x0003 
  bMaxPacketSize0 = 0x0009 
  idVendor = 0x0000 
  idProduct = 0x0000 
  bcdDevice = 0x0100 
  iManufacturer = 0x0001  <Intel>
  iProduct = 0x0002  <XHCI root HUB>
  iSerialNumber = 0x0000  <no string>
  bNumConfigurations = 0x0001

stephenw10

Were you able to resolve this?