[ Follow up ] Unable to boot Ultra 60

From: Michael DeSimone (michael@desimone.net)
Date: Thu Jun 26 2003 - 18:32:15 EDT


First Thanks to Hichael Morton for suggesting to reinstall the boot block
with installboot. I tried that but it did not change the situation.

I have done some more digging and experimenting ...

I still get the same Can't invoke /etc/init, error 2 - which, according to
Sun, means that /etc/init is actually missing
(
http://docs.sun.com/db/doc/806-1075/6jacsnimi?q=Can%27t+invoke+%2fetc%2finit%2c+error+2&a=view )

I can boot off the CDROM and fsck all partitions, I can mount all
partitions. I can even reboot the system with /a/etc/init 6 (my mounted file
system). I still get the same error when the system tries to come back up. I
tried recreating the link from etc/init to ../sbin/init. I moved over the
sbin/init from my CD. I reinstalled the boot block but still no dice.

Is my system just gone? I just can't buy that with all partitions mountable
and able to read and write to them.

According to http://docs.sun.com/db/doc/802-2002/6i60dq869?a=view (which is
a nice diagram of the boot process)
I should be croaking on step 6 - the kernel starts the init process. Which
is after the root file system is mounted. Could something be happening that
prevents my root files system from mounting?

Any ideas as to what could be happening would me most appreciated.

Thanks,
Michael

> I have a U60 that dies on boot with the following error:
>
> ++++++++START ERROR+++++++++
> panic[cpu0]/thread=7091dd60: Can't invoke /etc/init, error 2
>
>
> 40067c20 genunix:icode+25c (ffbeffe8, 0, 0, 7091bd48, ffffffff, ffbefff4)
> %l0-7: ffbefff4 10031154 00000001 4008fe40 00000bb8 00000000 00000000
> 10410ec8
>
> syncing file systems... done
> skipping system dump - no dump device configured
> rebooting...
> Resetting ...
> ++++++++END ERROR+++++++++
>
> Archives/google point to the possibility of a corrupt boot disk, which
makes
> sense. The system does not have an internal CDROM so I attached an
external
> one. I booted off of it and ran an FSCK rebooted and got the same error.
>
> How can I confirm that this is in fact a corrupt boot disk?
> Is there anything I can do to fix it or do I need to rebuild and recover?
>
> Thanks in advance.
> I WILL summarize
> Michael DeSimone
> _______________________________________________
> sunmanagers mailing list
> sunmanagers@sunmanagers.org
> http://www.sunmanagers.org/mailman/listinfo/sunmanagers
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers



This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:26:39 EDT