Hi all, new install. Migrating from existing pfsense installation. Install media is an old Kingston 2GB USB 2.0 stick. Checksum download was verified. Installation is on a Dell Optiplex 5050 with Intel i3-7100. I saw this forum post https://forum.opnsense.org/index.php?topic=23893.0 (https://forum.opnsense.org/index.php?topic=23893.0), and did try moving the USB stick to a USB 2.0 port. Maybe I didn't format and install correctly to USB 2.0 stick?
Errors while formatting and copying to the flash drive, I did unmount the disk:
(base) iMac-2019:Downloads XXX$ bzip2 -dc OPNsense-24.1-vga-amd64.img.bz2 | sudo dd of=/dev/disk5 bs=64k
Password:
dd: /dev/disk5: Resource busy
(base) iMac-2019:Downloads XXX$ bzip2 -dc OPNsense-24.1-vga-amd64.img.bz2 | sudo dd of=/dev/disk5 bs=64k
dd: /dev/disk5: Resource busy
(base) iMac-2019:Downloads XXX$ bzip2 -dc OPNsense-24.1-vga-amd64.img.bz2 | sudo dd of=/dev/disk5 bs=64k
dd: /dev/disk5: end of device
15304+997 records in
15639+1 records out
1024970752 bytes transferred in 277.000384 secs (3700250 bytes/sec)
Error on install:
dal: Serial Number 208411811113ec539406 dad: 48.800MB/s transfers
dal: 977MB (2001888 512 byte sectors)
dad: quirks=Bx2<NO_6_BYTE>
GEOM: daB: corrupt or invalid GPT detected.
GEOM: dad: GPT rejected - may not be recoverable.
GEOM: diskid/DISK-200411011113ec53940b: corrupt or invalid GPT detected.
GEOM: diskid/DISK-208411011113ec53940b: GPT rejected - may not be recoverable. mountroot: waiting for device /dev/ufs/OPNsense_Install...
Mounting from ufs:/dev/ufs/OPNsense_Install failed with error 19.
Loader variables:
vfs.root.mountfrom-ufs:/dev/ufs/OPNsense_Install
vfs.root.mountfrom.options-ro.noatime
Manual root filesystem specification:
<fstype>: <device> Coptions)
Mount <device> using filesysten <fstupe> and with the specified (optional) option list.
eg. ufs: /dev/daBsla
zfs:zroot/ROOT/default cd9660:/dev/cd@ ro
(which is equivalent to: mount - cd9660 -0 ro /dev/cd /)
? List valld disk boot devices
• Yield 1 second (for background tasks)
(empty line> Abort manual input
mountroot>
Haven't written an image using dd on macOS for ages, but you may have to use rdisk5 instead of disk5 (see here (https://osxdaily.com/2018/04/18/write-image-file-sd-card-dd-command-line/)).
But even more important: 2GB USB stick is not big enough, the image is 2.39G unpacked.
Quote from: patient0 on May 19, 2024, 07:31:33 PM
Haven't written an image using dd on macOS for ages, but you may have to use rdisk5 instead of disk5 (see here (https://osxdaily.com/2018/04/18/write-image-file-sd-card-dd-command-line/)).
But even more important: 2GB USB stick is not big enough, the image is 2.39G unpacked.
1. /dev/disk5 is fine.
2. Yes, the drive is too small as clearly shown by the "dd: /dev/disk5: end of device" message.
3. To get around the "device busy" problem use the GUI disk utility and deactivate (not eject!) the volume that is already present. Also the easiest way to get the disk device path. Click on the device, press Cmd-I for "information".
4. Use 1m blocksize for better performance.
I use dd exclusively to write images to devices - what else? ;)
Thanks Patrick and patient0. I reimaged to a larger USB stick, used rdisk, and the installation proceeded without issue. Interface autodetect didn't work which required pulling the cards to identify each specific interface and manually configure them, and zfs mirror didn't work, but those are separate issues.