From: hume.spamfilter on
BertieBigBollox(a)gmail.com <bertiebigbollox(a)gmail.com> wrote:
> Yes. root filesystem mount on /a and everything seems to be there.
>
> Already tried reboot -- -r and reboot -- -ra with no luck.

That's interesting. When you boot failsafe, and drop to a shell, try
chrooting to the mounted broken root. Use the command:

chroot /a /sbin/sh

When it's done, you'll be running /sbin/sh inside the root. / will refer
to /a and so on.

Check /etc/vfstab and make sure it refers to the proper devices. You can
also try "fsck -n -m /" and see how it behaves (keep in mind that you're
running fsck on a mounted, live filesystem...)

Are you using ZFS at all?

--
Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/
From: Nicolas GIMMILLARO on
BertieBigBollox(a)gmail.com wrote:
> 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? ????
>


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(a)1f,2/ide@0/cmdk@0,0:a ) matchs the hardware path on
which the failsafe os has booted ?
From: BertieBigBollox on
On Dec 17, 8:38 am, Nicolas GIMMILLARO <nicolas.gimmill...(a)wmi.fr>
wrote:
> BertieBigBol...(a)gmail.com wrote:
> > 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? ????
>
> 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(a)1f,2/ide@0/cmdk@0,0:a ) matchs the hardware path on
> which the failsafe os has booted ?- Hide quoted text -
>
> - Show quoted text -

Which post was that?