/ filesystem crash

[Jagadesh_2]

Hi,

root filesystem crashed on rp3440. When i tried recovering from HPUX core OS DVD it gave an error / filesystem full. It is not able to load the required files for recovering / filesystem.

Please let me know the possibilities for recovering / fixing this issue.

Thanks

[Jeeshan]

HPUX servers contains 2 HDD with mirrored.

Is both disk fails or 1 HDD crashed?

You can boot the system from alternate disk.

[MarkSyder]

I've never known a single filesystem to crash. What error message are you getting?

Mark Syder (like the drink but spelt different)

[Shahul]

HI,

When you say crashed, is it crashed on it's own, if it's crashed on it's own it's highly likely caused by a hardware fault. Try through alternate boot disk, or try booting to single user mode ,etc.

If it's crashed while you were doing some software config, like kernel rebuild, etc, then you can try booting from old kernel.

Good luck
Shahul

[Pete Randall]

What do you mean, "crashed"? I've never heard of a file system crashing. Can you give an exact error message or a better description of what actually occurred?


Pete

[Pete Randall]

Perhaps this document could help:

http://docs.hp.com/en/5991-1236/When_Good_Disks_Go_Bad.pdf


Pete

[Jagadesh_2]

/ filesystem is corrupted and while booting we are getting the below error. Iam not able to boot in to single user more or lvm maintenance mode. I am attaching the log along with this.

While trying to recover the filesystem from DVD i am getting error / filesystem is full. Unable to load files.

error details.
**************
ISL booting hpux -lq

Boot
: disk(0/1/1/0.0.0.0.0.0.0;0)/stand/vmunix

10850304 + 2080768 + 4885480 start 0x1f9868



alloc_pdc_pages: Relocating PDC from 0xfffffff0f0c00000 to 0x3f900000.

gate64: sysvec_vaddr = 0xc0002000 for 2 pages
NOTICE: autofs_link(): File system was registered at index 3.
NOTICE: cachefs_link(): File system was registered at index 5.
NOTICE: nfs3_link(): File system was registered at index 6.
probe: port 2 overcurrent 0x0
probe: port 3 overcurrent 0x0
igelan0: INITIALIZING HP PCI 1000Base-T Core at hardware path 0/1/2/0
igelan1: INITIALIZING HP AB465-60001 PCI/PCI-X 1000Base-T 2-port 2Gb FC/2-port 1000B-T Combo Adapter at hardware path 0/3/1/0/6/0
igelan2: INITIALIZING HP AB465-60001 PCI/PCI-X 1000Base-T 2-port 2Gb FC/2-port 1000B-T Combo Adapter at hardware path 0/3/1/0/6/1
igelan3: INITIALIZING HP AB465-60001 PCI/PCI-X 1000Base-T 2-port 2Gb FC/2-port 1000B-T Combo Adapter at hardware path 0/4/1/0/6/0
igelan4: INITIALIZING HP AB465-60001 PCI/PCI-X 1000Base-T 2-port 2Gb FC/2-port 1000B-T Combo Adapter at hardware path 0/4/1/0/6/1

System Console is on the Built-In Serial Interface
Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 16777216
Starting the STREAMS daemons-phase 1
The device file /dev/rroot does not exist or is not correct.
Automatic checks of the root file system not performed.
msgcnt 1 vxfs: mesg 017: vx_dirlook - / file system inode 2748 marked bad ?vxfs msgcnt 1 offset 0x00000000 0 0 0 0 ?vxfs msgcnt 1 offset 0x00000010 0 0 0 0 ?vxfs msgcnt 1 offset 0x00000020 0 0 0 0 ?vxfs msgcnt 1 offset 0x00000030 0 0 0 0 ?vxfs msgcnt 1 offset 0x00000040 0 0 0 0 ?vxfs msgcnt 1 offset 0x00000050 0 0 0 0 ?vxfs msgcnt 1 offset 0x00000060 0 0 0 0 ?vxfs msgcnt 1 offset 0x00000070 0 0 0 0 ?vxfs msgcnt 1 offset 0x00000080 0 0 0 0 ?vxfs msgcnt 1 offset 0x00000090 0 0 0 0 ?vxfs msgcnt 1 offset 0x000000a0 0 0 0 0 ?vxfs msgcnt 1 offset 0x000000b0 0 0

[Matt Hearn]

Eek. Corrupted root filesystem usually means you need to restore from an ignite image and hope the image is from before the corruption started. If that doesn't work, you may have to completely rebuild the box and restore your data to new filesystems.