Stuck in Failsafe Bootloader. what now?

[GPL-DDay]

My PA-820 is stuck in failsafe bootloader mode.  what are my options now? I am no longer getting the option for MAINT mode either.  If I let the system boot on it's own I get the below and it just keeps rebooting.

Welcome to the PanOS Failsafe Bootloader.

U-Boot 8.0.6.0-29 (Build time: Oct 13 2017 - 12:13:40)

Octeon unique ID: 044000214719f31e00d5
N0.LMC0 Configuration Completed: 16384 MB
QLM 2: SGMII
QLM 3: SGMII
QLM 4: SATA
DLM 5: SGMII
SATA0: available
SATA1: not available
SATA BIST STATUS = 0x0
MILLENNIUM board revision major:1, minor:1, serial #: 012001004473
OCTEON CN7240-AAP pass 1.2, Core clock: 1500 MHz, IO clock: 1000 MHz, DDR clock: 800 MHz (1600 Mhz DDR)
Base DRAM address used by u-boot: 0x40f000000, size: 0x1000000
DRAM: 16 GiB
Clearing DRAM...... done
Flash: 64 MiB
WARNING: Failed to get lmac fdt node for -100
WARNING: Failed to get lmac fdt node for -101
0:PCIe: Port 0 in endpoint mode.
0:PCIe: Port 1 is unknown, skipping.
0:PCIe: Port 2 is unknown, skipping.
0:PCIe: Port 3 is unknown, skipping.
SATA#0
Model: Micron_5100_MTFDDAK240TCB Firm: D0MU027 Ser#: 171116A599A6
Type: Hard Disk
Capacity: 228936.5 MB = 223.5 GB (468862128 x 512)
Net: mdio-octeon0:18 is connected to octmgmt0. Reconnecting to octeth0
mdio-octeon0:17 is connected to octmgmt1. Reconnecting to octeth1
octmgmt0 [PRIME], octmgmt1, octeth0, octeth1, octeth2, octeth3, octeth4, octeth5, octeth6, octeth7, octeth8, octeth9
Type the command 'usb start' to scan for USB storage devices.

Hit any key to stop autoboot: 0
10052914 bytes read in 35 ms (273.9 MiB/s)
Allocating memory for ELF segment: addr: 0xffffffff80100000 (adjusted to: 0x100000), size 0x7c4aa0
Bootloader: Done loading app on coremask:
0xff
Starting cores:
0xff
Linux version 3.10.87-oct2-mp (build@61cfc5fe286c) (gcc version 4.7.0 (Cavium Inc. Version: SDK_BUILD build 49) ) #29 SMP Fri Nov 3 08:43:39 EDT 2017
CVMSEG size: 3 cache lines (384 bytes)
Cavium Inc. SDK-3.1.2
bootconsole [early0] enabled
CPU revision is: 000d9702 (Cavium Octeon III)
FPU revision is: 00739700
Checking for the multiply/shift bug... no.
Checking for the daddiu bug... no.
Determined physical RAM map:
memory: 0000000000702000 @ 0000000000100000 (kernel data and code)
memory: 000000000004e000 @ 0000000000802000 (usable after init)
memory: 0000000000075000 @ 0000000000850000 (kernel data and code)
memory: 0000000000100000 @ 00000000eff00000 (usable)
memory: 000000000feff000 @ 00000000f0001000 (usable)
memory: 00000000f0000000 @ 000000031f000000 (usable)
No power GPIO device tree entry
No power GPIO device tree entry
ata1.00: exception Emask 0x0 SAct 0x43800 SErr 0x0 action 0x0
ata1.00: irq_stat 0x40000000
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/08:90:5a:4c:3e/00:00:00:00:00/40 tag 18 ncq 4096 in
res 41/40:00:5a:4c:3e/00:00:00:00:00/40 Emask 0x409 (media error) <F>
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
end_request: I/O error, dev sda, sector 4082778
journal_bmap: journal block not found at offset 7180 on sda2
JBD: bad block at offset 7180
ata1.00: exception Emask 0x0 SAct 0x400000 SErr 0x0 action 0x0
ata1.00: irq_stat 0x40000000
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/08:b0:5a:4c:3e/00:00:00:00:00/40 tag 22 ncq 4096 in
res 41/40:00:5a:4c:3e/00:00:00:00:00/40 Emask 0x409 (media error) <F>
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
end_request: I/O error, dev sda, sector 4082778
journal_bmap: journal block not found at offset 7180 on sda2
JBD: bad block at offset 7180
EXT3-fs (sda2): error loading journal
EXT2-fs (sda2): error: couldn't mount because of unsupported optional features (4)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,2)

*** NMI Watchdog interrupt on Core 0x01 ***
$0 0x0000000000000000 at 0x0000000014009ce0
v0 0xffffffff80764018 v1 0x0000000000000001
a0 0xfffffffffffffffd a1 0x0000000000000000
a2 0x000000000000007a a3 0x000000000000000a
a4 0x0000000000000400 a5 0x800000040edd1280
a6 0x0000000000000000 a7 0x0000000000000000
t0 0x0000000014009ce0 t1 0x000000001000001f
t2 0xffffffff80880000 t3 0x800000040ece4000
s0 0x80000000f42ab430 s1 0x0000000000000001
s2 0x00000000ffffff01 s3 0x00000000ffffff02
s4 0xffffffff806a9988 s5 0x000000000000007a
s6 0x0000000000000000 s7 0x800000040f000000
t8 0x0000000000000005 t9 0xffffffff8016b9b0
k0 0x800000040ecbbe10 k1 0x800000040ecbbe10
gp 0x800000040ecb8000 sp 0x800000040ecbbb40
s8 0xffffffff806aa320 ra 0xffffffff80173144
err_epc 0xffffffff80173148 epc 0xffffffff80169f60
status 0x0000000014489ce4 cause 0x0000000040808400

Last 16 IRQs on this CPU:
7a 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08

Stack dump:
800000040ecbbb40: 00000000 9af8da00 ffffffff 801d67fc
800000040ecbbb50: 80000004 0ecbbb50 80000004 0ecbbb50
800000040ecbbb60: 80000004 0ec4fa00 00000000 00000000
800000040ecbbb70: 00000000 0000007a ffffffff 8073c500
800000040ecbbb80: ffffffff 80169f60 ffffffff 801731a8
800000040ecbbb90: 00000000 00000001 ffffffff 80162f10
800000040ecbbba0: ffffffff 80765008 ffffffff 801e0d88
800000040ecbbbb0: ffffffff 8073c500 ffffffff 807ca298
800000040ecbbbc0: ffffffff 80870000 ffffffff 8086d160
800000040ecbbbd0: ffffffff 806a9160 ffffffff 80800000
800000040ecbbbe0: 80000004 0ecb8000 80000004 0f000000

[Remo]

@GPL-DDay

Sounds like you definately should open a TAC case. Probably an important part on the drive is no longer readable...

[reaper]

looks like your root partition could have a bad block

you could try interrupting the boot process and going into maintenance mode and fsck the disks , to see if you can repair the damage

else you will need to get a replacement disk/device

[GPL-DDay]

I would live to go into maintenance mode ... but it never gives me the opportunity to. It only gives the option to interrupt autoboot which takes me to failsafe.

I feel like I need to reload the bootloader so I can get back to maintenance mode. But I guess I don't know how to do that.

[reaper]

if you're unable to interrupt and go into maintenance mode, the disk is lost and you need an RMA