System disruption occurs after temporarily unable to read or write to boot device on FAS80x0 or AFF80x0
Applies to
- FAS80x0
- FAS8020
- FAS8040
- FAS8060
- FAS8080
- AFF80x0
- AFF8020
- AFF8040
- AFF8060
- AFF8080
Issue
- Node panics with string similar to:
Panic string: thread (g_up) on cpu 7 hung for 4001 milliseconds in process g_up on release 9.7P14 (C)
Panic_Message: g_vfs_done(): rootfs.uzip read error - suspect boot device in process g_up on release 9.8P4 (C)
- Prior to panic, g_vfs_done errors logged:
g_vfs_done():md0.uzip[WRITE(offset=535388160, length=8192)]error = 1
md0.uzip: UZIP(zlib) inflate() failed
g_vfs_done():md0.uzip[READ(offset=40071168, length=4096)]error = 86
vnode_pager_generic_getpages_done: I/O read error 5
md0.uzip: UZIP(zlib) inflate() failed
vm_fault: pager read error, pid 52511 (cat) [retry 9]
md0.uzip[READ(offset=690434048, length=8192)]vm_fault: pager read error, pid 2729 (ucoreman) [retry 9]
- During AUTOBOOT process, node may experience the following:
Starting AUTOBOOT press Ctrl-C to abort...
Could not load fat://boot0/X86_64/freebsd/image1/kernel:Device not found
ERROR: Error booting OS on: 'boot0' file: fat://boot0/X86_64/freebsd/image1/kernel (boot0,fat)
Autoboot of PRIMARY image failed. Device not found (-6)