Update to 14.3 does not boot anymore

[Matthias Fechner]

Dear all,

I tried to upgrade today one of my servers from 14.2 to 14.3 using
freebsd-update.
I just fetch the update, installed new kernel and rebooted:
freebsd-update upgrade -r 14.3-RELEASE
freebsd-update install
reboot

Now I see on the screen:
(ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 e0 48 04 04 40 00 00 00
00 00 00
(ada1:ahcich1:0:0:0): CAM status: Auto-Sense Retrieval Failed
(ada1:ahcich1:0:0:0): Error 5, Unretryable error

this is repeated and server refused to boot.
Maybe the disc is broken, but it worked fine till before the reboot into
the new kernel, so this can also be related to the upgrade.

These are Exos Enterprise Seagate harddiscs.

Does anyone have an idea?

Gruß
Matthias

--

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

[Arnold Greyling]

On 10 Jun 2025, at 10:14, Matthias Fechner <mfec...@freebsd.org> wrote:

I tried to upgrade today one of my servers from 14.2 to 14.3 using freebsd-update.
I just fetch the update, installed new kernel and rebooted:
freebsd-update upgrade -r 14.3-RELEASE
freebsd-update install
reboot

Now I see on the screen:
(ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 e0 48 04 04 40 00 00 00 00 00 00
(ada1:ahcich1:0:0:0): CAM status: Auto-Sense Retrieval Failed
(ada1:ahcich1:0:0:0): Error 5, Unretryable error

this is repeated and server refused to boot.
Maybe the disc is broken, but it worked fine till before the reboot into the new kernel, so this can also be related to the upgrade.

If you are using ZFS with the standard layout from the installer freebsd-update should have created a boot environment for 14.2 when you started the upgrade.

When you boot, select the option “Select boot environment …” from the boot menu, and then select the 14.2 environment

You will at least see if it is hardware or if it is caused by the upgrade.

If you don’t even get the boot menu it is probably hardware.

Regards

Arnold Greyling

[Paul Macdonald]

FWIW  an upgrade i just performed worked fine

-- 
-------------------------
Paul Macdonald (he/him)
IFDNRG Ltd
Web and video hosting
-------------------------
t: 0131 5548070
m: 07970339546
e: pa...@ifdnrg.com
w: https://www.ifdnrg.com
-------------------------
IFDNRG
40 Maritime Street
Edinburgh
EH6 6SA
----------------------------------------------------

Virtual Servers from £50.00pm
High specification Dedicated Servers from £150.00pm

----------------------------------------------------

[Matthias Fechner]

Am 10.06.2025 um 16:08 schrieb Paul Macdonald:

On 10/06/2025 09:47, Arnold Greyling wrote:

On 10 Jun 2025, at 10:14, Matthias Fechner <mfec...@freebsd.org> wrote:

I tried to upgrade today one of my servers from 14.2 to 14.3 using freebsd-update.
I just fetch the update, installed new kernel and rebooted:
freebsd-update upgrade -r 14.3-RELEASE
freebsd-update install
reboot

Now I see on the screen:
(ada1:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 e0 48 04 04 40 00 00 00 00 00 00
(ada1:ahcich1:0:0:0): CAM status: Auto-Sense Retrieval Failed
(ada1:ahcich1:0:0:0): Error 5, Unretryable error

this is repeated and server refused to boot.
Maybe the disc is broken, but it worked fine till before the reboot into the new kernel, so this can also be related to the upgrade.

If you are using ZFS with the standard layout from the installer freebsd-update should have created a boot environment for 14.2 when you started the upgrade.

When you boot, select the option “Select boot environment …” from the boot menu, and then select the 14.2 environment

You will at least see if it is hardware or if it is caused by the upgrade.

If you don’t even get the boot menu it is probably hardware.

Regards

Arnold Greyling

FWIW  an upgrade i just performed worked fine

at first thank you all for your feedback.
These problems always happen if you do not have physical access too the hardware.

We tried to boot an old ZFS snapshot (before the kernel update) which showed the same error message.
FreeBSD tries to boot, it failed and automatically rebooted after some time.

So we tried next to remove ada1 which is a SATA harddisc and it booted fine with FreeBSD 14.3 kernel (the pool is now degraded as is it a mirror).
So I completed the upgrade to 14.3 successfully.

Just to make another test, after the upgrade was done, we inserted the disc with the problem again and the system even hang up.
I was able to see in messages this (I redacted the serial of the drive):
Jun 11 12:59:05 server kernel: ada4 at ahcich1 bus 0 scbus1 target 0 lun 0
Jun 11 12:59:05 server kernel: ada4: <ST16000NM000J-2TW103 SB40> ACS-4 ATA SATA 3.x device
Jun 11 12:59:05 server kernel: ada4: Serial Number ZxxxxxxxQ
Jun 11 12:59:05 server kernel: ada4: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
Jun 11 12:59:05 server kernel: ada4: Command Queueing enabled
Jun 11 12:59:05 server kernel: ada4: 15259648MB (31251759104 512 byte sectors)
Jun 11 12:59:08 server kernel: (ada4:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 e0 20 fc bf 40 46 07 00 00 00 00
Jun 11 12:59:08 server kernel: (ada4:ahcich1:0:0:0): CAM status: Auto-Sense Retrieval Failed
Jun 11 12:59:08 server kernel: (ada4:ahcich1:0:0:0): Error 5, Unretryable error
Jun 11 12:59:08 server kernel: (ada4:ahcich1:0:0:0): READ_FPDMA_QUEUED. ACB: 60 e0 20 fe bf 40 46 07 00 00 00 00
Jun 11 12:59:08 server kernel: (ada4:ahcich1:0:0:0): CAM status: Auto-Sense Retrieval Failed
Jun 11 12:59:08 server kernel: (ada4:ahcich1:0:0:0): Error 5, Unretryable error

and then my ssh terminal disconnected.

So I will replace that harddisc. It is a new one and maybe half a year old but it seems somehow broken.
I will test a new one if I see a similar problem, maybe it is also a cable issue, but that I need to check in some month if I have physical access to the server again.

Best regards
Matthias

[Matthias Fechner]

Hi Juan,

Am 12.06.2025 um 22:03 schrieb Juan Manuel Palacios:

Not sure if this could be related, but just came across it and thought it might be of interested to you:

Are you by any chance using ZFS on MRB?

no, I use only GPT from the beginning it was available.
I never got warm with these slices on MBR ;)

[Matthias Fechner]

Am 11.06.2025 um 15:17 schrieb Matthias Fechner:
> So I will replace that harddisc. It is a new one and maybe half a year
> old but it seems somehow broken.
> I will test a new one if I see a similar problem, maybe it is also a
> cable issue, but that I need to check in some month if I have physical
> access to the server again.

I can confirm that the disc was dying and the upgrade made that finally
visible.
After the disc was now replaced by a new one, all is fine again and 14.3
is running fine.

Thanks
Matthias