Hi folks (mods can move this if I put it in the wrong topic)
I was going through the storage boxes of my old consulting company and found a Deciso DEC695.
I have no documnetation for it.
I plugged it in, thinking it would issue a 192.168.1.x address - but it did not.
Manually setting my laptop's address to the 192.168.1.x range, I cannot connect to the DEC695's webserver at 192.168.1.1
I'm not a complete novice with networking, but I kind of baffled by this basic no-do situation.
Any tips or advice?
Kind thanks in advance!
Was the box sealed or was it set up and just put back? Normally it has a quickstart guide. First port (may be "0") is LAN and DHCP is offered there for GUI access. Should be 192.168.1.1 indeed to reach it.
Your best bet is a serial cable and see what it reports at boot (and test standard credentials).
Cheers,
Franco
Hi Franco and kind thanks for your reply.
I'm pretty technical and good with instructions and research.
The unit was sealed and is un-used, never deployed.
I followed the Quick Start Guide (LAN to Port 0, WAN to Port 1).
No response on 192.168.1.1 and no response to pinging that IP from LAN.
Connecting to console, I see no opportunity to login.
Boot from power-on shows this:
[NOTE ] coreboot-v4.16.5-Deciso Mon May 16 13:20:57 UTC 2022 bootblock starting (log level: 6)...
[INFO ] CBFS: mcache @0x00034e00 built for 21 files, used 0x43c of 0x4000 bytes
[INFO ] CBFS: Found 'fallback/romstage' @0x80 size 0x62d0 in mcache @0x00034e2c
[NOTE ] coreboot-v4.16.5-Deciso Mon May 16 13:20:57 UTC 2022 romstage starting (log level: 6)...
[INFO ] done.
[INFO ] Initializing devices...
[INFO ] CPU: AMD GX-420MC SOC .
[INFO ] LAPIC 0x0 in XAPIC mode.
[INFO ] LAPIC 0x2 in XAPIC mode.
[INFO ] LAPIC 0x1 in XAPIC mode.
[INFO ] LAPIC 0x3 in XAPIC mode.
[INFO ] AP: slot 1 apic_id 2
[INFO ] AP: slot 3 apic_id 1
[INFO ] AP: slot 2 apic_id 3
[INFO ] Initializing CPU #0
[INFO ] CBFS: Found 'cpu_microcode_blob.bin' @0x6400 size 0xb5 in mcache @0xcfffd0ac
[INFO ] CPU #0 initialized
[INFO ] Initializing CPU #2
[INFO ] Initializing CPU #3
[INFO ] Initializing CPU #1
[INFO ] CBFS: Found 'cpu_microcode_blob.bin' @0x6400 size 0xb5 in mcache @0xcfffd0ac
[INFO ] CBFS: Found 'cpu_microcode_blob.bin' @0x6400 size 0xb5 in mcache @0xcfffd0ac
[INFO ] CBFS: Found 'cpu_microcode_blob.bin' @0x6400 size 0xb5 in mcache @0xcfffd0ac
[INFO ] CPU #2 initialized
[INFO ] CPU #3 initialized
[INFO ] CPU #1 initialized
[INFO ] bsp_do_flight_plan done after 40 msecs.
[INFO ] Devices initialized
[INFO ] Finalize devices...
[INFO ] Devices finalized
[INFO ] Writing IRQ routing tables to 0xf0000...write_pirq_routing_table done.
[INFO ] Writing IRQ routing tables to 0xcfee7000...write_pirq_routing_table done.
[INFO ] CBFS: Found 'fallback/dsdt.aml' @0x168c0 size 0x1760 in mcache @0xcfffd198
[WARN ] CBFS: 'fallback/slic' not found.
[INFO ] ACPI: Writing ACPI tables at cfec3000.
[INFO ] ACPI: done.
[INFO ] CBFS: Found 'fallback/payload' @0x26bc0 size 0x9949 in mcache @0xcfffd230
SeaBIOS (version rel-1.16.0-0-gd239552)
iPXE (https://ipxe.org) 02:00.0 C000 PCI2.10 PnP PMM+CFE64320+CFDA4320 C000
iPXE (https://ipxe.org) 03:00.0 C100 PCI2.10 PnP PMM CFE64320 CFDA4320 C100
iPXE (https://ipxe.org) 04:00.0 C200 PCI2.10 PnP PMM CFE64320 CFDA4320 C200
iPXE (https://ipxe.org) 05:00.0 C300 PCI2.10 PnP PMM CFE64320 CFDA4320 C300
xc
\
/boot/config: -S115200 -h
Booting from Hard Disk...
Consoles: serial port
BIOS drive C: is disk0s) from 500117600 to 0x27818 (0x31818): 00
disk0: Read 32 sector(s) from 500117600 to 0x74650 (0x7e650): 0xc
BIOS 639kB/3405536kB available memory
FreeBSD/x86 bootstrap loader, Revision 1.1
Loading /boot/defaults/loader.conf
Loading /boot/defaults/loader.conf
Loading /boot/device.hints
Loading /boot/loader.conf
Loading /boot/loader.conf.local
/
\
disk0: Read 5 sector(s) from 16282275 to 0x74650 (0x7e650): 0xc
zio_read error: 5
ZFS: i/o error - all block copies unavailable
disk0: Read 5 sector(s) from 16282275 to 0x74650 (0x7e650): 0xc
zio_read error: 5
ZFS: i/o error - all block copies unavailable
ERROR: /boot/lua/logo-hourglass.lua:1: unexpected symbol near '<\193>'.
Type '?' for a list of commands, 'help' for more detailed help.
OK
I am not familiar with this console (but I'm reading/learning).
It seems to me that my DEC 695 has faulty storage, and so cannot boot the OPNsense image - is this correct or close?
Many thanks,
Trevor
Quote from: TTownsend on August 08, 2025, 06:46:17 PM[...]
It seems to me that my DEC 695 has faulty storage, and so cannot boot the OPNsense image - is this correct or close?
Looks correct to me.
The device attempts network boot off all four ports (the "iPXE" messages), but that's not something I've done.
From here (https://wiki.junicast.de/en/junicast/review/opnsense_dec695), it has an M.2 2280 NVME SSD (I'd verify that, as all I can see for certain is the M key slot, which could be SATA). It may be bad, or it may have simply aged out due to being powered off - that is, it might function if re-written.
Quote... it has an M.2 2280 NVME SSD (I'd verify that, as all I can see for certain is the M key slot, which could be SATA). It may be bad, or it may have simply aged out due to being powered off - that is, it might function if re-written.
Pretty sure my warranty is over, so I'll open it and see what's in it for storage.
Then, I intend to try this: https://docs.opnsense.org/manual/install.html#installation-instructions (https://docs.opnsense.org/manual/install.html#installation-instructions), choosing the serial installer, and re-load an image.
If that doesn't work it's likely the SSD is bad and I'll replace it and try serial installation again.
Does that sound reasonable?
Many thanks!
Quote from: TTownsend on August 09, 2025, 12:00:12 AM[...]
Does that sound reasonable? [...]
Heh. I didn't even think of the serial installer.
I was thinking "swap those two activities", but thinking about it, I'd also take it apart first.
Quote from: pfry on August 09, 2025, 03:50:24 AMHeh. I didn't even think of the serial installer.
I've never done this method before, and I may try to image the SSD in a dock with a known utility DD(linux) or Rufus/DD(Windows).
We'll see how it goes - this DEC 695 is a nice piece of hardware, so I want to try everything reasonable to recover it as a usable appliance.
...fingers crossed!
And how do you think you get an image you can dd? ;-)
Boot from USB and run the installer while connected to the serial console. You cannot dd the installer image to a runtime SSD - the installer image is "installer" only.
Quote from: Patrick M. Hausen on August 09, 2025, 08:43:25 PMAnd how do you think you get an image you can dd? ;-)
From the OPNsense manual. (https://docs.opnsense.org/manual/install.html#installation-media)
QuoteYou cannot dd the installer image to a runtime SSD - the installer image is "installer" only.
Yeah, I meant DD to a USB.
So, I opened my DEC695 device and discovered ... a really nice piece of hardware. The PCB layout is neat and tidy.
There's the NVMe SSD, a Transcend 110s 256GB model (2000/1200 sequential read/write speeds), so I replaced that with a WB Black SN7100 1 TB model (7250/6900 MB/s read/write). Should make a snappy little box a wee bit snappier, perhaps?
8GB DDR3 SODIMM will stay.
On to re-installing OPNsense....
Quote from: TTownsend on August 09, 2025, 10:59:49 PMQuote from: Patrick M. Hausen on August 09, 2025, 08:43:25 PMFrom the OPNsense manual. (https://docs.opnsense.org/manual/install.html#installation-media)
That will create an installer medium.
I got from your previous post to which I replied that you intended to somehow dd OPNsense to an SSD and place that one into your appliance. Like one would do with e.g. a Raspberry Pi. That does not work.
Good luck installing!
Kind regards,
Patrick