Solaris 10 x86 boot problem
bertieb...@gmail.com
attempts to boot, displays sun copyright lines and then reboots and
loops around.
Grub entries are:-
findroot (rootfs0,0,a)
kernel /platform/i86pc/multiboot
module /platform/i86pc/boot-archive
Also, got an entry in grub for failsafe solaris boot and this boots up
ok:-
findroot (rootfs0,0,a)
kernel /boot/multiboot kernel/unix -s
module /boot/x86.miniroot-safe
Its on a laptop and I've got a feeling the user may have been powering
off without shutting down properly and that this has corrupt
something.
Anyway, is there a command to fixboot or something?
Or would I be better off booting from sol10 cd and doing an inplace
upgrade?
Richard B. Gilbert
Have you tried booting from CD/DVD and running fsck on your disk? All
partitions, of course; If the boot partition is fsck'ed up you have to
expect that the rest of the disk may be in less than perfect shape.
bertieb...@gmail.com
wrote:
>
> - Show quoted text -
No. I'll try that.
bertieb...@gmail.com
as the first choice). Would this affect anything that grub was trying
to do?
hume.sp...@bofh.ca
> Also, I recently changed the boot order in the BIOS (to remove CD boot
> as the first choice). Would this affect anything that grub was trying
That shouldn't matter.
Also, if your failsafe boot option works okay, it shouldn't be necessary to
boot from DVD/CD. Just boot from failsafe, and do your checks from
maintenance mode.
--
Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/
Ian Collins
> Had a working system. Booted up fine but now it goes into grub,
> attempts to boot, displays sun copyright lines and then reboots and
> loops around.
>
> Grub entries are:-
> findroot (rootfs0,0,a)
> kernel /platform/i86pc/multiboot
> module /platform/i86pc/boot-archive
>
> Also, got an entry in grub for failsafe solaris boot and this boots up
> ok:-
> findroot (rootfs0,0,a)
> kernel /boot/multiboot kernel/unix -s
> module /boot/x86.miniroot-safe
>
> Its on a laptop and I've got a feeling the user may have been powering
> off without shutting down properly and that this has corrupt
> something.
>
> Anyway, is there a command to fixboot or something?
Edit the grub entry to enter kmdb on boot. See
http://blogs.sun.com/dmick/entry/diagnosing_kernel_hangs_panics_with
--
Ian Collins
cindy
Which Solaris release is this? Sounds to me like your boot archives
need to be updated, depending on the Solaris release. You might
review the bootadm update-archive command, described here:
http://docs.sun.com/app/docs/doc/817-1985/gglaj?a=view
Or, do a google search of bootadm update to see other examples
that might apply to your scenario.
Cindy
Cindy
bertieb...@gmail.com
>
> - Show quoted text -
Cindy,
Thanks. Already tried that.
bertieb...@gmail.com
>
> - Show quoted text -
I'll give this a try...
bertieb...@gmail.com
>
> - Show quoted text -
sol 10 x86
Chris Ridd
> sol 10 x86
Which update? It makes a difference.
--
Chris
bertieb...@gmail.com
> On 2009-12-11 09:39:11 +0000, BertieBigBol...@gmail.com said:
>
> > sol 10 x86
>
> Which update? It makes a difference.
> --
> Chris
solaris 10 5/09 x86
Paul Floyd
<bertieb...@gmail.com> wrote:
>
> sol 10 x86
And precisely which version of Solaris 10? The first release was almost
5 years ago, and the 'current' version is the 8th update. Update 1 added
grub, and update 6 added ZFS boot. Both of these change significantly
booting.
A bientot
Paul
--
Paul Floyd http://paulf.free.fr
cindy
Bertie,
If this is a Solaris 10 10/08 system with a UFS root, for example,
then your grub entries
look reasonable to me.
Maybe the problem is with the disk. I would boot from an s10 CD and
use format to
review the disk label to see if it is still intact.
Cindy
bertieb...@gmail.com
> If this is a Solaris 10 10/08 system with a UFS root, for example,
> then your grub entries
> look reasonable to me.
>
> Maybe the problem is with the disk. I would boot from an s10 CD and
> use format to
> review the disk label to see if it is still intact.
>
>
> - Show quoted text -
Its Sol 10 05/09. I still seem to be able to access all my files if I
boot from failsafe.
Its just if I try to boot normally, it does the SunOs release 5
banner, then resets the machine and goes back into grub.
bertieb...@gmail.com
1. findroot (rootfs0,0,a) command is fine because failsafe boot uses
the same command and this works. So it can find the disk.
2. module /platform/i86pc/boot_archive must be OK because I've rebuilt
the boot archive with the bootadm command.
Therefore, this leaves the actual kernel? kernel /platform/i86pc/
multiboot
Could this be corrupt or something? Is there any way to rebuild this?
bertieb...@gmail.com
>
> - Show quoted text -
OK. Got it to enter kmdb.
All I get is :-
Loading kmdb...
welcome to kmdb
[0]> ?
Any ideas what next?
bertieb...@gmail.com
Got into kmdb and ran :-
prom_debug/W 1
:c
and this seems to attempt to boot.
At the end, there was a message which seems to be pertinent:-
Cannot mount root on /pci@0,0/pci-ide@1f,2/ide@0/cmdk@0,0:a fstype ufs
panic[cpu0]/thread=fffffffffbc26480: vfs_mountroot: cannot mount root
Hmmm. So for some reason the kernel cant see the root disk. I know its
there because failsafe can see it?
Any ideas?
Rebuild the kernel? ????
hume.sp...@bofh.ca
> panic[cpu0]/thread=fffffffffbc26480: vfs_mountroot: cannot mount root
>
> Hmmm. So for some reason the kernel cant see the root disk. I know its
> there because failsafe can see it?
I wouldn't assume that. When the failsafe boots, it runs off the ramdisk.
Does it offer to mount the hard disk root on /a?
If you boot failsafe, and then pop into a shell, is /a mounted? What
device is it attached to?
What happens if you do a regular boot, adding '-r' to the grub flags? It's
possible your /dev tree is damaged.
Nicolas GIMMILLARO
See my post on 12/10/09 18:11
Have to try to see if bootpath in bootenv.rc (it is actually be set to
/pci@0,0/pci-ide@1f,2/ide@0/cmdk@0,0:a ) matchs the hardware path on
which the failsafe os has booted ?
bertieb...@gmail.com
wrote:
>
> - Show quoted text -
Which post was that?