6100 Max running 24.03 RC unable to update firmware
-
That’s the strange thing. There’s nothing but stock drives and no attachments.
-
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
-
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 mmcsd0Tried rebooting and reinstalling, same error.
-
And still no mmcsd0 device in the geom output?
-
Hmm, what does:
dmesg | grep da0
show? -
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> -
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 -
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.
-
No USBs and nothing in the SIM slot.
-
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
-
Were you able to resolve this?