Hi Glynn,
Sorry to be a dolt, but what's the strategy behind using pfexec if
the OpenSolaris installation goes through the trouble of setting
up root as a role?
I also noticed that the secondary user account that the OpenSolaris
install creates also has root privileges as a role.
So, why
Hi William,
Thanks for the comments...
For the ZFS comments:
1.
Good comment about pointing to Tim's blog instead of the script directly.
2. The user account that is created during the OpenSolaris
installation has root privileges. For example:
[EMAIL PROTECTED]:~/Desktop$ roles
root
So, for a
Hi Dave,
I see your point about the second user account so we'll drop it.
This issue also highlights a transition between managing user accounts
with home directories as a UFS directory and home directories as ZFS
file systems.
I need to file a bug against the user account manager because it
Francois,
I'm reposting this on indiana-discuss to see if anyone on that list
can provide some input.
Is this happening during a netinstall?
Can you provide the output of ls -l /dev/null?
Cindy
François Feugeas wrote:
Hello,
We're having a strange issue on one of our OpenSolaris 64bit
Hi Tom,
Can you confirm that c9t0d0s0 has a VTOC label rather than an EFI label?
If c9t0d0s0 has an EFI label, then you will need to do the procedure
described below.
Cindy
1. Detach the disk.
# zpool detach rpool c9t0d0s0
2. Relabel the disk.
# format -e c9t0d0s0
format label
[0] SMI Label
Hi Rand,
The Solaris admin guide identifies services, here:
http://docs.sun.com/app/docs/doc/819-2379/fddwm?a=view
You can use the service name identified in this section to
review the man page for the service or related function.
This doc isn't specific to the OpenSolaris release and I'm
Hi Rand,
Collecting some OSOL services information is a good idea.
We'll be in touch...
Thanks for your interest!
Cindy
Rand All wrote:
Cool, thanks, Cindy.
So it seems the doc I'm envisioning, a nice, succinct description of what
services do and which ones are needed for which
Hi Sebastien,
I've outlined steps below to help you recovery from the label problem.
Make sure you can boot from the primary disk, c4t0d0s0, before you
begin.
I've reproduced these steps correctly on my Nevada, build 104 system
because my OpenSolaris system doesn't have two disks.
An easier
Hi Jasse,
I included some pointers below that will help you navigate OpenSolaris
information. Since we are documenting several Solaris releases, we have
information in several locations.
Let me know if you can't find something that you need.
Cindy
1. OpenSolaris information starts here:
Hi Sebastien,
You can test booting from the second disk just by selecting the second
disk to boot at the BIOS level.
You can review this error scenario and other ZFS troubleshooting issues,
here:
http://www.solarisinternals.com/wiki/index.php/ZFS_Troubleshooting_Guide
Not everything in this
To create a mirrored root pool, you need to use the zpool attach
command. In addition, you need to specify the slice identifier.
For example:
# zpool attach rpool c1t0d0s0 c1t1d0s0
On an x86 system, you also must have a Solaris fdisk partition.
If you can provide your existing zpool status
Hi Harry,
I would recommend that you let the tasks guide you rather than
let the terminology confuse you, if that's possible. :-)
For example, the beadm commands in the OpenSolaris release are
built around some ZFS features such as snapshots and clones.
These ZFS terms are defined here:
Hi Gilles,
This looks like:
http://bugs.opensolaris.org/view_bug.do?bug_id=6462803
I can't find the matching OSOL bugzilla record but try the workaround
in this bug report.
Cindy
Gilles Gravier wrote:
Hi!
I get a strange message at boot since recent updates (b108, maybe before)...
I get
Hi Seymour,
Which OpenSolaris release is this?
I'm unclear of the root cause and because I don't know if you did this
step but because you are adding the second root pool disk manually, you
need to add a block block, like this:
x86# installgrub /boot/grub/stage1 /boot/grub/stage2
Hi Bernd,
You can take a recursive root pool snapshot and send it to a pool on the
second disk. If Time Slider is running, you could just send the root
pool related snapshots to the second disk.
I think the Time Slider team is working on a more robust approach, or
maybe some experts can share
Hi--
I generally restart syslog if I make modifications to syslog.conf,
like this:
# svcadm restart svc:/system/system-log:default
Cindy
solarg wrote:
hello all,
i'm unable to write with syslog from my apps:
# perl -MSys::Syslog -e 'Sys::Syslog::syslog(daemon|debug, this is a
better test:
Hi James,
No answers from me, just some information.
The ability to boot from a disk greater than 1 TB integrated last fall
and this support is in the OpenSolaris 2009.06 release.
I see the same zio_read_data error (boot from install okay, but not
from the disk) in this CR:
6843138 can not
Hi James,
It was as the zio error that caught my attention as I have a superficial
understanding of GRUB/x86-based booting.
I found only two bugs with the zio error message. One was fixed and then
6843138, which seems to describe your boot error scenario, although
without the greater than 1
Another issue that might be happening in this case is that the ZFS
device names have changed starting in build 125. This change impacts
luactivate and mostly likely beadm activate if you have a mirrored
root pool because the root pool mirror device becomes mirror-0 as in
Bernd's root pool and
19 matches
Mail list logo
