Story: I was trying to block the e100 driver from loading since it was blocking Tigan's tg3 for our Broadcom cards. I removed both the e100 and tg3 with 'modprobe -r'. I tried to restart it once again, to see which modules load. In the boot process, the box hangs at the point where it says:
"Starting openntpd:"
Nothing else happens. I tried to restart it a couple of times and to load a different kernel, but no :|
Edit: The only ntp server runs on this machine.
Is there a way to "skip" the starting of openntpd at the boot process?
Problem with interfaces => problem with openntpd in this case?
Edit2: After some period of time (5-10 minutes), the following message is printed, and nothing else is happening:
Code:
3w-9xxx: scsi0: AEN: INFO (0x04:0x000C): Initialize started: unit=1.
Then I got another message:
3w-9xxx: scsi0: AEN: INFO (0x04: 0x0007) : Initializing completed:unit=0 subunit=0
Both of these messages come from the RAID, and mean "Initialize started" and "Initialize completed". Nothing happens afterwards though. I don't like these two messages... What happens with the raid? It is RAID5 type.
I can ping it from machines on the local net. But cannot access it via ssh (due to internal limitations, i.e., I do not have an access to the box from other boxes on the same net).
Previously I used to access it with a key from my laptop, but now that interface is down. I modified the /etc/network/interfaces to be set up for eth0 and eth1 before I reboot, so I lost eth2. (Before, eth0 and eth2 were running...and that was the reason to remove e100, which blocked eth1).
