aha!
So installgrub was the final culpret but I did add etc/zfs/zpool.cache
into the filelist.ramdisk file first. For reference, I did boot into a
safemode miniroot to ensure that installgrub or any other boot related
updates didn't happen from the old nmu environments. I think that
installgr
One thing I forgot to mention is to
modify /mnt/boot/solaris/filelist.ramdisk and add /boot/grub line there
- then update archive and reboot.
Also, GRUB/ZFS update (i.e. installgrub) is fairly safe operation and
should not interfere with older checkpoints.
And - ensure that you installgrub on all
Re-running installgrub was the other thing I did and forgot to mention.
If zpool.cache is missing then it will not know how to import your root
pool. This is problematic because it's sometimes necessary to remove that
file when recovering from problems/importing other pools. I guess the
sol
They versions are 10/3 respectively. I have booted into an older
checkpoint and tried to rebuild the boot_archive with no luck. My
process looks like:
# mount -F zfs syspool/rootfs-nmu-002 /mnt
# mount | awk '!/^\/mnt/ {print "mount " $1 " /mnt" $1}' > /tmp/mount.sh
# source /tmp/mount.sh
# c
This been fixed in b104 I believe
On Tue, 2008-12-16 at 17:28 -0500, Thomas Garner wrote:
> I wasn't seeing them at boot, but after upgrading to b102, I saw
> spontaneous reboots, often several times a day. It was bad enough
> that I reverted to b85.
>
> Dec 2 04:00:11 filer0 ^Mpanic[cpu2]/thre
you might need to verify that zpool / zfs versions of your checkpoint(s)
are all the latest:
zpool get version syspool >= v10
zfs get -r version syspool >= v3
However, keep in mind that if you upgrade to > v10, you will not be able
to load previous checkpoint with b85.
Another possible reason is
I wasn't seeing them at boot, but after upgrading to b102, I saw
spontaneous reboots, often several times a day. It was bad enough
that I reverted to b85.
Dec 2 04:00:11 filer0 ^Mpanic[cpu2]/thread=868b8dc0:
Dec 2 04:00:11 filer0 genunix: [ID 335743 kern.notice] BAD TRAP:
type=e (#pf Page fault
On Tue, 16 Dec 2008, Tim Spriggs wrote:
This is the second host with b104 I am getting this on. Has anyone else seen
this:
Yes, I got this the other day after doing a forced b85 -> 2.0 alpha1
upgrade. It can't import the root pool, and I had to rebuild the boot
archive (boot from cd and
This is the second host with b104 I am getting this on. Has anyone else
seen this:
module /platform/i86pc/kernel/amd64/unix: text at [0xfb80,
0xfb91fcc3] data at 0xfbc0
module /kernel/amd64/genunix: text at [0xfb91fcd0,
0xfbb6c1c7] data at 0x
