Update from 23.05.1 to 23.09 End's in Error
-
Hmm, that's a curious error. What are you installing on there? What hardware? What drive?
-
@stephenw10
Hardware
cpu: AMD G-T40E Processor (1000.03-MHz K8-class CPU)
Drive:
ada0: KingFast O1229A ACS-2ATA SATA 3.x device
Additionally…It also known as PC-Alix 2d (or so)…Hope, that helps and please let me know, if you need more info‘s.
Kindly regards
Diego -
It's an APU. The ALIX was their much older 32bit Via based device.
But that's an aside! That should be fine. I have exactly that combination here:
[23.09-RELEASE][admin@apu.stevew.lan]/root: sysctl hw.model hw.model: AMD G-T40E Processor [23.09-RELEASE][admin@apu.stevew.lan]/root: geom disk list ada0 Geom name: ada0 Providers: 1. Name: ada0 Mediasize: 30016659456 (28G) Sectorsize: 512 Mode: r2w2e7 descr: INTEL SSDMCEAC030B3 lunid: 55cd2e404be963ff ident: CVLI448600Z4030H rotationrate: 0 fwsectors: 63 fwheads: 16
For some reason it cannot write out the updated boot loader. It's not mounting the EFI partion as read write by the looks of it. But the APU is not a UEFI system....
Try looking at:
geom part list ada0
And:mount -p
Steve
-
@stephenw10 said in Update from 23.05.1 to 23.09 End's in Error:
geom part list ada0
Geom name: ada0 modified: false state: OK fwheads: 16 fwsectors: 63 last: 31277191 first: 40 entries: 128 scheme: GPT Providers: 1. Name: ada0p1 Mediasize: 524288 (512K) Sectorsize: 512 Stripesize: 0 Stripeoffset: 20480 Mode: r0w0e0 efimedia: HD(1,GPT,6375eedb-7afe-11e9-90c3-000db93411e4,0x28,0x400) rawuuid: 6375eedb-7afe-11e9-90c3-000db93411e4 rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f label: gptboot0 length: 524288 offset: 20480 type: freebsd-boot index: 1 end: 1063 start: 40 2. Name: ada0p2 Mediasize: 2147483648 (2.0G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 1048576 Mode: r1w1e0 efimedia: HD(2,GPT,63940663-7afe-11e9-90c3-000db93411e4,0x800,0x400000) rawuuid: 63940663-7afe-11e9-90c3-000db93411e4 rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b label: swap0 length: 2147483648 offset: 1048576 type: freebsd-swap index: 2 end: 4196351 start: 2048 3. Name: ada0p3 Mediasize: 13865320448 (13G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 2148532224 Mode: r1w1e1 efimedia: HD(3,GPT,63a69489-7afe-11e9-90c3-000db93411e4,0x400800,0x19d3800) rawuuid: 63a69489-7afe-11e9-90c3-000db93411e4 rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b label: zfs0 length: 13865320448 offset: 2148532224 type: freebsd-zfs index: 3 end: 31277055 start: 4196352 Consumers: 1. Name: ada0 Mediasize: 16013942784 (15G) Sectorsize: 512 Mode: r2w2e3
zroot/ROOT/default / zfs rw,noatime,nfsv4acls 0 0 devfs /dev devfs rw 0 0 zroot/tmp /tmp zfs rw,nosuid,noatime,nfsv4acls 0 0 zroot/var /var zfs rw,noatime,nfsv4acls 0 0 zroot /zroot zfs rw,noatime,nfsv4acls 0 0 zroot/reservation /zroot/reservation zfs rw,noatime,nfsv4acls 0 0 zroot/ROOT/default/var_cache_pkg /var/cache/pkg zfs rw,noexec,nosuid,noatime,nfsv4acls 0 0 zroot/ROOT/default/var_db_pkg /var/db/pkg zfs rw,noexec,nosuid,noatime,nfsv4acls 0 0 tmpfs /var/run tmpfs rw 0 0 /lib /var/unbound/lib nullfs ro,noatime,nfsv4acls 0 0 devfs /var/unbound/dev devfs rw 0 0 /var/log/pfblockerng /var/unbound/var/log/pfblockerng nullfs rw,noatime,nfsv4acls 0 0 /usr/local/share/GeoIP /var/unbound/usr/local/share/GeoIP nullfs ro,noatime,nfsv4acls 0 0 devfs /var/dhcpd/dev devfs rw 0 0 /usr/local/bin /var/unbound/usr/local/bin nullfs ro,noatime,nfsv4acls 0 0 /usr/local/lib /var/unbound/usr/local/lib nullfs ro,noatime,nfsv4acls 0 0
Until Today, I haven't some Problem for installing...
-
@stephenw10
Please excuse me for not answering properly (not with the necessary decorum) and allow me to ask one final question.
As I understand it now, this is the first time that such a "strange" error has occurred (I didn't find anything in the search).
If I interpret your answers correctly, the smartest thing to do would be to reinstall the Pfsense.
Is my assumption correct?
Thank you very much for your answer and thank you again for the answers already given.
Best wishes from (no longer) sunny Switzerland
Diego -
What do you see from:
sysctl machdep.bootmethod
Edit: also what do you see from:
geom part list
without restricting it to ada0. -
Hy Steve,
Response for sysctl machdep.bootmethod
machdep.bootmethod: BIOS
Response for geom part list
eom name: ada0 modified: false state: OK fwheads: 16 fwsectors: 63 last: 31277191 first: 40 entries: 128 scheme: GPT Providers: 1. Name: ada0p1 Mediasize: 524288 (512K) Sectorsize: 512 Stripesize: 0 Stripeoffset: 20480 Mode: r0w0e0 efimedia: HD(1,GPT,6375eedb-7afe-11e9-90c3-000db93411e4,0x28,0x400) rawuuid: 6375eedb-7afe-11e9-90c3-000db93411e4 rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f label: gptboot0 length: 524288 offset: 20480 type: freebsd-boot index: 1 end: 1063 start: 40 2. Name: ada0p2 Mediasize: 2147483648 (2.0G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 1048576 Mode: r1w1e0 efimedia: HD(2,GPT,63940663-7afe-11e9-90c3-000db93411e4,0x800,0x400000) rawuuid: 63940663-7afe-11e9-90c3-000db93411e4 rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b label: swap0 length: 2147483648 offset: 1048576 type: freebsd-swap index: 2 end: 4196351 start: 2048 3. Name: ada0p3 Mediasize: 13865320448 (13G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 2148532224 Mode: r1w1e1 efimedia: HD(3,GPT,63a69489-7afe-11e9-90c3-000db93411e4,0x400800,0x19d3800) rawuuid: 63a69489-7afe-11e9-90c3-000db93411e4 rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b label: zfs0 length: 13865320448 offset: 2148532224 type: freebsd-zfs index: 3 end: 31277055 start: 4196352 Consumers: 1. Name: ada0 Mediasize: 16013942784 (15G) Sectorsize: 512 Mode: r2w2e3 Geom name: da0 modified: false state: OK fwheads: 255 fwsectors: 63 last: 3970047 first: 1 entries: 4 scheme: MBR Providers: 1. Name: da0s1 Mediasize: 819200 (800K) Sectorsize: 512 Stripesize: 0 Stripeoffset: 512 Mode: r0w0e0 efimedia: HD(1,MBR,0x90909090,0x1,0x640) rawtype: 239 length: 819200 offset: 512 type: efi index: 1 end: 1600 start: 1 2. Name: da0s2 Mediasize: 755507200 (721M) Sectorsize: 512 Stripesize: 0 Stripeoffset: 819712 Mode: r0w0e0 efimedia: HD(2,MBR,0x90909090,0x641,0x168410) attrib: active rawtype: 165 length: 755507200 offset: 819712 type: freebsd index: 2 end: 1477200 start: 1601 3. Name: da0s3 Mediasize: 37748736 (36M) Sectorsize: 512 Stripesize: 0 Stripeoffset: 756326912 Mode: r0w0e0 efimedia: HD(3,MBR,0x90909090,0x168a51,0x12000) rawtype: 11 length: 37748736 offset: 756326912 type: fat32 index: 3 end: 1550928 start: 1477201 Consumers: 1. Name: da0 Mediasize: 2032664576 (1.9G) Sectorsize: 512 Mode: r0w0e0 Geom name: da0s2 modified: false state: OK fwheads: 255 fwsectors: 63 last: 1475599 first: 0 entries: 8 scheme: BSD Providers: 1. Name: da0s2a Mediasize: 755499008 (721M) Sectorsize: 512 Stripesize: 0 Stripeoffset: 827904 Mode: r0w0e0 rawtype: 7 length: 755499008 offset: 8192 type: freebsd-ufs index: 1 end: 1475599 start: 16 Consumers: 1. Name: da0s2 Mediasize: 755507200 (721M) Sectorsize: 512 Stripesize: 0 Stripeoffset: 819712 Mode: r0w0e0
The SD Card is/was for backup purposes.
Thanks and Kindly regards
Diego -
Ok, it's because you have that SD card in there and it has an EFI partition that is read-only. That's the installer image on that SD card I assume?
Remove the card and retest.
-
Hey Steve,
many thanks... That was the solution... I don't know why it has Yet a problem with the SD Card.
The Update is successfull done.Many thanks Steve, for your help.
Top...Greetings
Diego -
It's because the install image is multiboot, it has an EFI partition and loader, but the APU is not UEFI so the installed image on the SSD does not. The upgrade script looks for an EFI partition to update the loader and the only one on the system is on the SD card. It wouldn't happen on a UEFI system.
But that seems like a bug. It shouldn't really do that.Steve