All,
I am no UNIX guru and all of them on my project have been unable to figure out the situation regarding the "waiting for ARP/RARP packet" issue we are experiencing. Hopefull, someone here will have some much needed insight....
The workstation is crashing while no one is around, the screen indicates a scrolling "Timeout waiting for ARP/RARP packet" error. The machine is locked up. We reboot via the power switch and run fsck and this usually gets the machine back to an operational state. The most recent time when we rebooted we had to run fsck 3 times and each time a particular block on the c0t0d0s7 disk was
unreadable and three INODEs were partially allocated. After the third
iteration we rebooted again without issue.
The machine normally boots off of its own disk and there is no ability to boot off of a network drive. I have seen the Timeout waiting for ARP/RARP packet issue stated as being inability to boot off of the network drive mentioned but this is not the case in our situation as we have no ability to boot off the network. Also, we have replaced the hard drive but are still experiencing the same issue.
Can anyone provide any insight regarding this problem. I would greatly appreciate it....So far our UNIX guys have spent a lot of man hours on this and have gotten nowhere.
I am no UNIX guru and all of them on my project have been unable to figure out the situation regarding the "waiting for ARP/RARP packet" issue we are experiencing. Hopefull, someone here will have some much needed insight....
The workstation is crashing while no one is around, the screen indicates a scrolling "Timeout waiting for ARP/RARP packet" error. The machine is locked up. We reboot via the power switch and run fsck and this usually gets the machine back to an operational state. The most recent time when we rebooted we had to run fsck 3 times and each time a particular block on the c0t0d0s7 disk was
unreadable and three INODEs were partially allocated. After the third
iteration we rebooted again without issue.
The machine normally boots off of its own disk and there is no ability to boot off of a network drive. I have seen the Timeout waiting for ARP/RARP packet issue stated as being inability to boot off of the network drive mentioned but this is not the case in our situation as we have no ability to boot off the network. Also, we have replaced the hard drive but are still experiencing the same issue.
Can anyone provide any insight regarding this problem. I would greatly appreciate it....So far our UNIX guys have spent a lot of man hours on this and have gotten nowhere.