Well, I still cannot make a backup of my BE.
For now the system works. I think I’ll just have to do a fresh install and
reimport my storage pool when I really need to upgrade.
On 11/29/16, 7:30 PM, "Dan McDonald" wrote:
You may need to construct your menu.lst yourself, then. Here's a f
Install grub did not fix the issue. Its booting up with temp BE’s everytime.
This issue is really weird. I noticed that the zpool thinks that one of its
disks are c6t0d0s0 but its actually using c5t0d0s0 could this be related?
Thanks for your help this evening.
On 11/29/16, 7:30 PM, "Dan McD
You may need to construct your menu.lst yourself, then. Here's a few sample
entries. Note the up-front globals (like default entry), followed by specific
entries. HOPEFULLY that's all you have to do. Otherwise, you may need to
re-run installgrub(1M).
Dan
===
# default menu ent
So that’s the final caveat here lol…bootadm says that the menu file is at that
path but that file structure doesn’t actually exist.
Been racking my brain on this most of the afternoon.
ls /tmp
total 87
drwxrwxrwt 21 root sys1536 Nov 29 18:54 .
drwxr-xr-x 27 root root 31 Nov 2
Hmmm, try re-writing your rpool's menu.lst:
cp /tmp/bootadm_mnt_zfs_legacy.1603/boot/grub/menu.lst /rpool/boot/grub/.
See if that helps out.
Dan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/o
Thanks Dan,
One issue…I can’t backup my BE for a like reason.
beadm create omnios-backup2
Unable to create omnios-backup2.
Missing boot menu file.
On 11/29/16, 7:11 PM, "Dan McDonald" wrote:
> On Nov 29, 2016, at 8:06 PM, John Barfield
wrote:
>
> Hi Dan,
>
> I
> On Nov 29, 2016, at 8:06 PM, John Barfield wrote:
>
> Hi Dan,
>
> I hit a bad key combination and outlook sent me email prematurely.
>
> I’d like to update to the latest stable release. The old nfs lockd bug is on
> my last nerve.
Oh my... I also just realized something... you're REALLY
pkg
On 11/29/16, 7:00 PM, "Dan McDonald" wrote:
> On Nov 29, 2016, at 7:51 PM, John Barfield
wrote:
>
> Good evening,
>
> I’m trying to upgrade an omnios 151012 and I keep getting errors from pkg
src:
>
> WARNING: The boot environment being modified is n
Hi Dan,
I hit a bad key combination and outlook sent me email prematurely.
I’d like to update to the latest stable release. The old nfs lockd bug is on my
last nerve.
This box doesn’t have any active production zones any longer its only acting as
SAN/NAS.
Thanks for your help and quick re
> On Nov 29, 2016, at 7:51 PM, John Barfield wrote:
>
> Good evening,
>
> I’m trying to upgrade an omnios 151012 and I keep getting errors from pkg src:
>
> WARNING: The boot environment being modified is not the active one. Changes
> made will not be reflected on the next boot.
>
> If I
Good evening,
I’m trying to upgrade an omnios 151012 and I keep getting errors from pkg src:
WARNING: The boot environment being modified is not the active one. Changes
made will not be reflected on the next boot.
If I try to activate the “omnios” be it says:
Unable to activate omnios.
Missing
11 matches
Mail list logo
