Prev: Sun SSH without a password (not OpenSSH)
Next: convert CPU load to CPU utilization in %
From: BertieBigBollox on 15 Dec 2009 09:34
OK. So from what I understand so far:-

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?
From: BertieBigBollox on 15 Dec 2009 09:44
On Dec 10, 6:39 pm, Ian Collins <ian-n...(a)hotmail.com> wrote:
> BertieBigBol...(a)gmail.com wrote:
> > 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- Hide quoted text -
>
> - Show quoted text -

OK. Got it to enter kmdb.

All I get is :-
Loading kmdb...

welcome to kmdb
[0]> ?

Any ideas what next?
From: BertieBigBollox on 15 Dec 2009 09:52
Ah. Got some info now.

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(a)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? ????

From: hume.spamfilter on 15 Dec 2009 13:29
In comp.unix.solaris BertieBigBollox(a)gmail.com <bertiebigbollox(a)gmail.com> wrote:
> Cannot mount root on /pci@0,0/pci-ide(a)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?

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.

--
Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/
From: BertieBigBollox on 16 Dec 2009 03:48
On Dec 15, 6:29 pm, hume.spamfil...(a)bofh.ca wrote:
> In comp.unix.solaris BertieBigBol...(a)gmail.com <bertiebigbol...(a)gmail.com> wrote:
>
> > Cannot mount root on /pci@0,0/pci-ide(a)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?
>
> 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.
>
> --
> Brandon Hume    - hume -> BOFH.Ca,http://WWW.BOFH.Ca/

Yes. root filesystem mount on /a and everything seems to be there.

Already tried reboot -- -r and reboot -- -ra with no luck.
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: Sun SSH without a password (not OpenSSH)
Next: convert CPU load to CPU utilization in %