Unable to get into maintenance mode

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Unable to get into maintenance mode

L0 Member

Hello All,

I was in the process of upgrading our firmware of our PA500 to 8.1 and when the device rebooted, it did not want to come back online.  Checked the startup and noticed I was getting this error message.  I did read online that it might be an issue with the hard drive?  Is there a way I can resolve this?  I cannot even get into maintenance mode to run a hard drive repair.

 

Entry: maint8935587 bytes read in 217 ms (39.3 MiB/s)
Allocating memory for ELF segment: addr: 0xffffffff80100000 (adjusted to: 0x100000), size 0x74b2a0
Bootloader: Done loading app on coremask: 0x3
Starting cores:
0x3
Linux version 3.10.20-mp-7.1.0.0.22 (build@eng-bf0-1.paloaltonetworks.local) (gcc version 4.7.0 (Cav ium Inc. Version: SDK_BUILD build 41) ) #2 SMP Fri Feb 5 14:19:56 PST 2016
CVMSEG size: 2 cache lines (256 bytes)
Cavium Inc. SDK-3.1
bootconsole [early0] enabled
CPU revision is: 000d0708 (Cavium Octeon+)
Checking for the multiply/shift bug... no.
Checking for the daddiu bug... no.
Determined physical RAM map:
memory: 000000000b400000 @ 0000000000900000 (usable)
memory: 0000000003c00000 @ 000000000c200000 (usable)
memory: 0000000060000000 @ 0000000020000000 (usable)
memory: 000000000f000000 @ 0000000410000000 (usable)
memory: 0000000000615000 @ 0000000000100000 (usable)
memory: 000000000005b000 @ 0000000000715000 (usable after init)
ata1.00: exception Emask 0x0 SAct 0x7f000001 SErr 0x0 action 0x6
ata1.00: irq_stat 0x00020002, device error via SDB FIS
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/08:00:6d:20:b9/00:00:00:00:00/40 tag 0 ncq 4096 in
res 6c/1e:00:00:00:00/00:00:00:00:6c/00 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DF DRQ }
ata1.00: error: { IDNF ABRT }
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/08:c0:35:20:b9/00:00:00:00:00/40 tag 24 ncq 4096 in
res 41/40:00:35:20:b9/00:00:00:00:00/40 Emask 0x409 (media error) <F>
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/08:c8:3d:20:b9/00:00:00:00:00/40 tag 25 ncq 4096 in
res 6d/1e:00:00:00:00/00:00:00:90:6d/00 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DF DRQ ERR }
ata1.00: error: { IDNF ABRT }
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/08:d0:45:20:b9/00:00:00:00:00/40 tag 26 ncq 4096 in
res 6d/1e:00:00:00:00/00:00:00:a0:6d/00 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DF DRQ ERR }
ata1.00: error: { IDNF ABRT }
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/08:d8:4d:20:b9/00:00:00:00:00/40 tag 27 ncq 4096 in
res 6d/1e:00:00:00:00/00:00:00:b0:6d/00 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DF DRQ ERR }
ata1.00: error: { IDNF ABRT }
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/08:e0:55:20:b9/00:00:00:00:00/40 tag 28 ncq 4096 in
res 6d/1e:00:00:00:00/00:00:00:c0:6d/00 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DF DRQ ERR }
ata1.00: error: { IDNF ABRT }
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/08:e8:5d:20:b9/00:00:00:00:00/40 tag 29 ncq 4096 in
res 6d/1e:00:00:00:00/00:00:00:d0:6d/00 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DF DRQ ERR }
ata1.00: error: { IDNF ABRT }
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/08:f0:65:20:b9/00:00:00:00:00/40 tag 30 ncq 4096 in
res 6d/1e:00:00:00:00/00:00:00:e0:6d/00 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DF DRQ ERR }
ata1.00: error: { IDNF ABRT }
end_request: I/O error, dev sda, sector 12132405
JBD: Failed to read block at offset 11692
EXT3-fs (sda3): error loading journal
EXT2-fs (sda3): error: couldn't mount because of unsupported optional features (4)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,3)

 

 

 

3 REPLIES 3

Cyber Elite
Cyber Elite

Hello,

That is a support call and possible RMA.

 

Regards,

Unfortunately the warranty has expired on this unit.   Is there anything else I might be able to do?

Hello,

I would place it back under warranty, if its something you need asap, buy a new one :(.

 

Sorry.

  • 3998 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!