Project

General

Profile

Actions

Bug #15364

closed

Netgate XG-7100-1U OS drive timeout / system hang / no access to WebUI nor SSH

Added by Pf Sensitive about 1 month ago. Updated about 1 month ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
Upgrade
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Release Notes:
Default
Affected Plus Version:
23.09.1
Affected Architecture:
7100

Description

Bug seems to be similar as #14181 and #14300.

Contexte : Upgrade PfSense+ from 23.05.1 to 23.09.1 on Netgate XG-7100-1U. Two hours after, everything crashed. OS drive use ZFS filesystem.

Bug : Network features (WAN/Firewall/routing/etc.) works, FreeBSD operating system and services (DHPC/OpenVPN/WebUI/SSH/etc.) down.

Relevant log : In a serial console, at during reboot, we get :

@mmcsd0: Issuing erase command failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Setting erase start position failed Timeout
mmcsd0: Error indicated: 1 Timeout
mmcsd0: Error indicated: 1 Timeout
mmcsd0: Error indicated: 1 Timeout
mmcsd0: Error indicated: 1 Timeout
mmcsd0: Error indicated: 1 Timeout
sdhci_pci0-slot0: ============== REGISTER DUMP ==============
sdhci_pci0-slot0: Sys addr: 0x07080000 | Version: 0x00001002
sdhci_pci0-slot0: Blk size: 0x00007200 | Blk cnt: 0x00000010
sdhci_pci0-slot0: Argument: 0x00200a10 | Trn mode: 0x00000037
sdhci_pci0-slot0: Present: 0x1fef0000 | Host ctl: 0x00000025
sdhci_pci0-slot0: Power: 0x0000000b | Blk gap: 0x00000080
sdhci_pci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000207
sdhci_pci0-slot0: Timeout: 0x0000000d | Int stat: 0x00000000
sdhci_pci0-slot0: Int enab: 0x01ff003b | Sig enab: 0x01ff003b
sdhci_pci0-slot0: AC12 err: 0x00000000 | Host ctl2:0x0000000c
sdhci_pci0-slot0: Caps: 0x546ec8b2 | Caps2: 0x80000007
sdhci_pci0-slot0: Max curr: 0x00000000 | ADMA err: 0x00000000
sdhci_pci0-slot0: ADMA addr:0x00000000 | Slot int: 0x00000000
sdhci_pci0-slot0: ===========================================
Solaris: WARNING: Pool 'pfSense' has encountered an uncorrectable I/O failure and has been suspended.

Solaris: WARNING: Pool 'pfSense' has encountered an uncorrectable I/O failure and has been suspended.

Solaris: WARNING: Pool 'pfSense' has encountered an uncorrectable I/O failure and has been suspended.@

Actions #1

Updated by Jim Pingle about 1 month ago

  • Status changed from New to Not a Bug
  • Priority changed from Very High to Normal

There are no issues of that nature with the 7100 hardware on 23.09.1. Most likely that is a hardware problem. Contact TAC for assistance.

Actions

Also available in: Atom PDF