James writes:

> What part of the kernel install did it panic on? (if you even saw that 
> part) 

Sorry, I forgot to mention that.  Here is what was left on my remote screen
after the panic: 

root@ducky:/usr/src/sys/compile/DUCKY] # make install
chflags noschg /kernel
mv /kernel /kernel.old
install -c -m 555 -o root -g wheel -fschg  kernel /kernel
if [ -d /modules -a -n "`ls /modules`" ]; then  mkdir -p /modules.old;  cp 
 -p /modules/* /modules.old;  fi; 


> Have you tried booting the previous kernel? I'm not sure if it'll 
> even boot... but, you might want to try that.

I tried the old kernel, but it failed to get past the probing.  I can't
remember the messages, but it was something like "isa_?? cannot get ports
for le...... cannot get irq for le". 

> You might also wanna try installing the same /kernel and /modules that you 
> were when it panic'd, while you have the drive mounted on another box. 

There is no /kernel.old any more.  I have installed the new 4.2 kernel
when the drive was mounted in another box.  Its that kernel which produce
the messages below. 

Thanks. 

> Dan Langille writes:  
> 
>> I recently upgraded a box from 4.1-stable to 4.2-stable. An NFS mount was
>> used for the install world and install kernel.  During the kernel install
>> the box panic'd (sorry, didn't see the message).  Upon boot, the box give
>> these messages:   
>> 
>> Mounting root from ufs:/dev/ad0s1a
>> /: bad dir ino 2 at offset 0: mangled entry
>> panic: ufs_dirbad: bad dir   
>> 
>> syncing disks.... 1 1 1 1 1 1 1 1..etc
>> giving up on 1 buffers   
>> 
>> 
>> I did an fsck on the disk by moving it to another box. The above messages
>> appeared both before and after the fsck.   
>> 
>> Clues please!   
>> 
>> -- 
>> Dan Langille - novice in training
>> [my thanks to evilcode.com for the emergency email access]  
>> 
>> 
>> To Unsubscribe: send mail to [EMAIL PROTECTED]
>> with "unsubscribe freebsd-hackers" in the body of the message
> 
 


-- 
Dan Langille - novice in training 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Reply via email to