PANIC: (CPU 0): pim_links: can't find xnts on next page

[Joao Rydin]

Hi,

I have a AS1200 with 4.0F.

It was working fine but after reboot started to give this message and restarts.

What can I do?

Thanks,

Rydin

[Ivan Ferreira]

Can you boot in single user?

boot -fl s

Can you boot with genvmunix kernel?

boot -fi genvmunix -fl s

You should call for a hardware verification.

[Han Pilmeyer]

This looks like an AdvFS disk corruption. I would boot from CD and try to run the AdvFS verification tool on all the domains.

It would be better if you also had the latest V5.1B CD and tried to run fixfdmn from that. But since you're still on V4.0F, that may not be an option.

BTW. Always make sure that the error messages are exactly as printed by the system. I had a hard time finding this message. It's pin_link, not pim_link.

[Joao Rydin]

Hi

I tried to boot with to single-user but it still reboot's.

I can start the server with the CDROM, but how can I mount the root filesystem to use the verify command (AdvFS).

Thank in advance.

Rydin

[Joao Rydin]

Hi again,

After booting from cdrom, I used the advscan -r command ro fix the domain and fset name.

Then I tried to mount the root filesystem, but the system reboots...

I think there is a problem with the advfs...

Thanks again

[Michael Schulte zur Sur]

Hi,

Han was talking about the verify command.
advscan does not correct inconsistencies.

greetings,

Michael

[Joao Rydin]

Hi,

I know that advscan does not fix the filesystem, but how can I use the verify command if I cant mount the root filesystem...

Thanks

[Michael Schulte zur Sur]

Hi,

filesets do not have to be mounted when using verify.
If machine also reboots when using verify then the domain is irreparably damaged.
The you can only recreate and restore the domain.

Michael

[Ivan Ferreira]

See the AdvFS Administration manual, section:

Recovering from Data Corruption of an AdvFS root Domain

For information about how to do that.

[Joao Rydin]

I have restored the root filesystem...