i had the same problem, tried installgrub updategrub bootadm-updatearchive.. nothing helps. i made a clean install
On Mon, Oct 27, 2008 at 5:57 PM, gerard at free <gerard.henry at free.fr> wrote: > hello all, > my laptop contains os2008.05, upgraded to snv_b99 with pkg image-update, > and after a shutdown, it is now totally broken, the error at boot is: > > ********************************************************************************* > bootfs rpool/ROOT/opensolaris-4 > kernel$ /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS > loading 'kernel$ /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS' ... > cpu: 'GenuineIntel' family 6 model 13 step 8 > amd64: CPU does NOT support long mode > amd64: CPU does NOT support PSE > amd64: CPU does NOT support amd64 executables. > [Multiboot-elf, <0xc000000:0xfa54:0x0>, <0x400000:0xbc248:0x0>, > <0x800000:0x7a18:0x3867c>, shtab=0xc10370, entry=0xc00000] > '/platform/i86pc/kernel//unix -B > zfs-bootfs=rpool/440,bootpath="/pci at 0,0/pci-ide > @1f,2/ide at 0/cmdk at 0,0:a",diskdevid="id1,cmdk at > AWDC_WD400VE-75HDT1=_____WD-WXE40600 > 3777/a"' is loaded > module$ /platform/i86pc/$ISADIR/boot_archive > loading '/platform/i86pc/$ISADIR/boot_archive' ... > > Error 16: Inconsistent filesystem structure > ********************************************************************************* > > The laptop is x86, not amd64, and i followed all the docs i founded in > archives's list: > - boot from milax, zpool -f import rpool, and update_grub > but it seems that something is incorrect yet: > > ********************************************************************************* > bootadm: get_bootgrub(): cannot get (hd?,?,?) for menu. menu not on > bootdisk: /dev/rdsk/c5d0s0 > Installing grub > ********************************************************************************* > > THe laptop had 2 BE, one with b97 and other with b99, and unfortunately, > the problem occured with the two ones... > > How can i repair it? Why grub said that: > "16 : Inconsistent filesystem structure > This error is returned by the filesystem code to denote an internal > error caused by the sanity checks of the filesystem structure on disk > not matching what it expects. This is usually caused by a corrupt > filesystem or bugs in the code handling it in GRUB. " > > i can mount the filesystem without problem when i boot from cd, and the > datas are still there. I also re-installed grub into the mbr, without > positive change. > > Thanks for help, > > gerard > > > > -- > _______________________________________________ > indiana-discuss mailing list > indiana-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/indiana-discuss > _______________________________________________ > install-discuss mailing list > install-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/install-discuss > -- Andy http://blog.sartek.net
