Re: [indiana-discuss] OpenSolaris package repository update, development build 130, x86/x64/SPARC (38 new packages)
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 neither luactivate or beadm activate recognize this device name. The workaround is: 1. Detach the secondary mirrored root pool device(s) 2. Run the activate operation 3. Re-attach the secondary root pool device(s) I have attempted to describe this problem, here: http://www.solarisinternals.com/wiki/index.php/ZFS_Troubleshooting_Guide#Live_Upgrade_and_beadm_Problem_.28Starting_in_Nevada.2C_build_125.29 I haven't been able to reproduce this scenario on my OpenSolaris laptop because I only have one disk. If someone else can confirm that CR 6894189 impacts beadm activate, then I will update this section with a better OpenSolaris error description and workaround. Thanks, Cindy On 01/04/10 13:53, Dave Miner wrote: On 12/25/09 12:30 PM, Bernd Schemmer wrote: Hi another issue with the upgrade to snv_130: The installation worked but the new BE could not be activated: ... Reading Existing Index ... Done Indexing Packages ... Done pkg: unable to activate OpenSolaris06.2009-6 A manual beadm activate for the new BE did also not work. But the beadm activate for one of the older BEs worked without problems. I could boot into the new BE by manual selecting the new BE in the GRUB menu without problems (except the ones documented in the message above) Doing a beadm activate manual with the environment variable PRINT_ERR set (after booting into the new BE) I got a much better error message: xtrn...@t61p:~$ BE_PRINT_ERR=true pfexec beadm activate OpenSolaris06.2009-6 be_do_installgrub: installgrub failed for device c8d0s0. Unable to activate OpenSolaris06.2009-6. Unknown external error. And that's a correct error message: xtrn...@t61p:~$ zpool status pool: rpool state: DEGRADED status: One or more devices could not be opened. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Attach the missing device and online it using 'zpool online'. see: http://www.sun.com/msg/ZFS-8000-2Q scrub: none requested config: NAME STATE READ WRITE CKSUM rpool DEGRADED 0 0 0 mirror-0DEGRADED 0 0 0 c9t0d0s0 ONLINE 0 0 0 c8d0s0OFFLINE 0 0 0 c1t0d0s0 UNAVAIL 0 0 0 cannot open errors: No known data errors xtrn...@t61p:~$ (c8d0s0 and c1t0d0s0 are my backup disks which I only connect one time a week to create a copy of the rpool) After detaching c8d0s0 and c1t0d0s0 from the pool the beadm activate worked fine: r...@t61p:~# beadm list BEActive Mountpoint Space Policy Created ---- -- - -- --- OpenSolaris06-2009-b121 - - 3.37G static 2009-09-02 21:55 OpenSolaris06.2009-1 - - 4.88M static 2009-04-22 21:46 OpenSolaris06.2009-2 - - 93.0K static 2009-04-30 23:50 OpenSolaris06.2009-3 - - 26.03M static 2009-05-23 14:15 OpenSolaris06.2009-4 - /a 95.83M static 2009-06-05 23:52 OpenSolaris06.2009-5 - - 2.82G static 2009-06-27 16:42 OpenSolaris06.2009-6 NR / 28.15G static 2009-12-25 13:42 OpenSolaris06.2009-6-b118 - - 2.93G static 2009-07-18 13:08 opensolaris - - 168.32M static 2009-04-22 21:27 *Conclusion* IMHO I think 1. the error messages from beadm should be more detailed in the default configuration Absolutely. They'll be getting better in the coming months. 2. In this case I think a warning about the missing disk is enough -- I don't think this should be an error. I disagree. Your use case is an exceptional one, and having a mirrored installation that can't boot from all sides of the mirror could be fairly damaging. Dave ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] zio_read_data failed in GRUB while trying to boot from compact flash (CF)
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 TB disk factor, is fixed in a later build. Someone more experienced will have to comment. Cindy James Lee wrote: cindy.swearin...@sun.com wrote: 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 boot off of a 2.2TB and zfs root The root cause seems to be that the that BIOS is not reporting correct capacity. This CR is fixed in Nevada, build 117. If someone can get you the stage2 binary from build 117, then we would know for sure that is bug is your issue. Thanks Cindy. I think we may be onto something with this. I grabbed c62013fcda99 from hg where this fix was committed and compiled GRUB. I installed the stages like: # installgrub stage1 stage2 /dev/rdsk/c7d0s0 And GRUB actually loaded menu.lst and the splash image! This is the furthest I've gotten so far. Unfortunately, it can't read the kernel now: loading '/platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS,console=graphics' ... cpu: 'GenuineIntel' family 6 model 7 step 7 [BIOS accepted mixed-mode target setting!] zio_read_data failed Error 15: File not found Press any key to continue... Back in GRUB: grub find /platform/i86pc/kernel/unix zio_read_data failed Error 15: File not found So what would cause GRUB to be able to load /rpool/boot/grub/menu.lst fine but not /platform/i86pc/kernel/unix? ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] zio_read_data failed in GRUB while trying to boot from compact flash (CF)
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 boot off of a 2.2TB and zfs root The root cause seems to be that the that BIOS is not reporting correct capacity. This CR is fixed in Nevada, build 117. If someone can get you the stage2 binary from build 117, then we would know for sure that is bug is your issue. Cindy James Lee wrote: Joseph J VLcek wrote: With rpool imported/mounted can you cat the contents of the GRUB menu.lst file? What does it contain? e.g.: % cat /rpool/boot/grub/menu.lst This question should probably be posted to install-disc...@opensolaris.org Joe Yes, I can cat the file just fine once booted into the livecd: # zpool import rpool # cat /rpool/boot/grub/menu.lst splashimage /boot/grub/splash.xpm.gz background 215ECA timeout 30 default 0 #-- ADDED BY BOOTADM - DO NOT EDIT -- title OpenSolaris 2009.06 findroot (pool_rpool,0,a) bootfs rpool/ROOT/opensolaris splashimage /boot/solaris.xpm foreground d25f00 background 115d93 kernel$ /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS,console=graphics module$ /platform/i86pc/$ISADIR/boot_archive #-END BOOTADM Unfortunately, GRUB never gets to a point where it can. ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] syslog broken in os2008.11?
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: %d, time);' and syslog.conf: *.err;kern.notice;auth.notice /dev/sysmsg *.err;kern.debug;daemon.notice;mail.crit/var/adm/messages *.alert;kern.err;daemon.err operator *.alert root *.emerg * mail.debug ifdef(`LOGHOST', /var/log/syslog, @loghost) ifdef(`LOGHOST', , user.err/dev/sysmsg user.err/var/adm/messages user.alert `root, operator' user.emerg * ) local6.debug/var/log/sipserver.log /var/log/syslog and /var/adm/messages aren't written! the same problem appears in a non global zone. Anybody has seen the problem? this is very important thanks in advance for help, gerard ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] Howto backup a rootpool on a Notebook?
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 what they are currently doing. We have some root pool recovery instructions, not specific to just OpenSolaris releases, described here: http://www.solarisinternals.com/wiki/index.php/ZFS_Troubleshooting_Guide#ZFS_Root_Pool_Recovery Currently, ZFS does not support breaking a mirror and then using that side of the mirror to recreate the pool. You could take the second disk (that you attached and detached) and import the root pool on another system (that includes the second disk). In any event, this RFE is already filed: http://bugs.opensolaris.org/view_bug.do?bug_id=5097228 provide 'zpool split' to create new pool by breaking all mirrors Cindy Bernd Schemmer wrote: Hi now that I've successfully installed OpenSolaris 06.2009 on my notebook I'm thinking about how to do a regular backup. Unfortunatley the notebook has only one internal drive so that I can not use a mirror to have data redundance. So my current approach is: Connect a second disk via USB ; attach the disk to the disk in the rootpool ; wait until the resilvering of the root pool is done; and detach the USB disk again. That works but Solaris always resilvers the complete pool so that it takes a long time (about 1 - 2 GB per minute; at this time 300 GB are in use so that it takes about 3 to 4 hours). Is there a better method to create a backup of the root pool? regards Bernd ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] problem with mirrored disk
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 /dev/rdsk/c6d0s0 I'm asking about the OpenSolaris release because I see a bug that is similar to these messages, but was fixed in build 106. Thanks, Cindy Seymour Krebs wrote: Two identical disks have identical partition tables: Current partition table (original): Total disk cylinders available: 30398 + 2 (reserved cylinders) Part TagFlag Cylinders SizeBlocks 0 rootwm 262 - 30397 230.85GB(30136/0/0) 484134840 1 swapwu 1 - 2612.00GB(261/0/0) 4192965 2 backupwu 0 - 30397 232.86GB(30398/0/0) 488343870 3 unassignedwm 00 (0/0/0) 0 4 unassignedwm 00 (0/0/0) 0 5 unassignedwm 00 (0/0/0) 0 6 unassignedwm 00 (0/0/0) 0 7 unassignedwm 00 (0/0/0) 0 8 bootwu 0 - 07.84MB(1/0/0) 16065 9 unassignedwm 00 (0/0/0) 0 the single primary disk boots, etc. when the second disk is added to the pool: ~# zpool attach rpool c7d0s0 c6d0s0 invalid vdev specification use '-f' to override the following errors: /dev/dsk/c6d0s0 overlaps with /dev/dsk/c6d0s2 when -f is added the second disk then resilvers and everything seems fine until a reboot occurs. Upon reboot, the original mirror member goes into grub2 menu, boots to build 110 of x64 Opensolaris, then refuses to continue an repeatedly throws errors concerning the second disk errors 0x03 and 0x07. Attempting to boot from the second disk give s a couple of very quick zio_read_data failed and drops to Grub. the second disk has been reformatted and tested and appears to be fine hardware-wise, so does the controller. Any suggestions would be appreciated. Otherwise I may have to back up and try reinstalling. ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] Time Slider broken in recent builds?
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 this when doing svcs -x : ggrav...@opensoltink:~$ svcs -xv svc:/system/filesystem/zfs/auto-snapshot:frequent (ZFS automatic snapshots) State: maintenance since 11 March 2009 09:53:45 CET Reason: Restarter svc:/system/svc/restarter:default gave no explanation. See: http://sun.com/msg/SMF-8000-9C See: /var/svc/log/system-filesystem-zfs-auto-snapshot:frequent.log Impact: 1 dependent service is not running: svc:/application/time-slider:default svc:/system/filesystem/zfs/auto-snapshot:hourly (ZFS automatic snapshots) State: maintenance since 11 March 2009 09:53:53 CET Reason: Restarter svc:/system/svc/restarter:default gave no explanation. See: http://sun.com/msg/SMF-8000-9C See: /var/svc/log/system-filesystem-zfs-auto-snapshot:hourly.log Impact: 1 dependent service is not running: svc:/application/time-slider:default svc:/system/filesystem/zfs/auto-snapshot:daily (ZFS automatic snapshots) State: maintenance since 11 March 2009 09:53:59 CET Reason: Restarter svc:/system/svc/restarter:default gave no explanation. See: http://sun.com/msg/SMF-8000-9C See: /var/svc/log/system-filesystem-zfs-auto-snapshot:daily.log Impact: 1 dependent service is not running: svc:/application/time-slider:default So I went to look at the log file... and I get this inside it : [ Mar 11 09:53:56 Enabled. ] [ Mar 11 09:53:56 Executing start method (/lib/svc/method/zfs-auto-snapshot start). ] Checking for non-recursive missed // snapshots rpool Last snapshot for svc:/system/filesystem/zfs/auto-snapshot:daily taken on Mon Mar 2 10:10 2009 which was greater than the 1 days schedule. Taking snapshot now. Checking for recursive missed // snapshots rpool/export rpool/ROOT Last snapshot for svc:/system/filesystem/zfs/auto-snapshot:daily taken on Mon Mar 2 10:10 2009 which was greater than the 1 days schedule. Taking snapshot now. cannot create snapshot 'rpool/ROOT/opensola...@zfs-auto-snap:daily-2009-03-11-09:53': dataset is busy no snapshots were created Error: Unable to take recursive snapshots of rpool/r...@zfs-auto-snap:daily-2009-03-11-09:53. Moving service svc:/system/filesystem/zfs/auto-snapshot:daily to maintenance mode. [ Mar 11 09:53:59 Method start exited with status 0. ] [ Mar 11 09:53:59 Stopping for maintenance due to administrative_request. ] [ Mar 11 09:53:59 Executing stop method (/lib/svc/method/zfs-auto-snapshot stop). ] [ Mar 11 09:53:59 Method stop exited with status 0. ] [ Mar 11 09:53:59 Stopping for maintenance due to administrative_request. ] Any idea? Cheers, Gilles. -- *Gilles Gravier, CISSP *Government Industry Solutions Architect mailto:gilles.grav...@sun.com Voice : +41 (22) 999 9051 Mobile : +41 (79) 472 8437 Fax : +41 (860) 79 472 8437 E-mail : gilles.grav...@sun.com mailto:gilles.grav...@sun.com *Sun Microsystems* 12 route des Avouillons CH-1196 Gland Switzerland http://www.sun.com/opensource/ SunIM : ggrav...@sun.com http://im-amer.sun.com/ ICQ : 77488526 http://www.icq.com/whitepages/about_me.php?Uin=77488526 AIM : gillesgravier aim:goim?screenname=gillesgravier Y! : ggravier http://profiles.yahoo.com/ggravier Jabber : ggrav...@jabber.org/Gaim http://www.jabber.org/ Skype : ggravier callto://ggravier MSN : gil...@gravier.org http://members.msn.com/gil...@gravier.org Google : gilles.grav...@gmail.com mailto://gilles.grav...@gmail.com Sent from a laptop running OpenSolaris 2008.11 snv_108 http://www.opensolaris.org/ using Mozilla Thunderbird http://www.mozilla.com/thunderbird/ (v2.0.0.18) ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] images, bootenv, clone, snapshot..
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: http://docs.sun.com/app/docs/doc/817-2271/ftyue?a=view Also, check out this section on creating and promoting clones in the purely ZFS context: http://docs.sun.com/app/docs/doc/817-2271/gbcxz?a=view Then, you could contrast how these terms are used in the OpenSolaris environment: http://dlc.sun.com/osol/docs/content/2008.11/snapupgrade/gentextid-173.html However, to work with bootable environments using the beadm commands that rely on these ZFS features, you must use the correct beadm command to add, remove, or clone them. For example, you wouldn't want to use zfs destroy to remove a BE. You would use beadm destroy. You wouldn't use zfs promote to activate a BE, you would use beadm activate, and so on. I hope this helps... Cindy Harry Putnam wrote: Harry Putnam rea...@newsguy.com writes: Create a clone of the current environment and never touch it. Thanks for that reference to `copy on write (COW)'. This is my first brush with those concepts which I am finding good discussion of with google. I'll admit I don't fully understand it yet. But correct me if I have this wrong. The miss-named `clone', is not stand alone (Something one would expect from a `clone'). That is, it relies still on the parent if called into duty. Is that right? Could you move(mv) the clone to a new disc and boot it up? Or does the COW kick in during mv... I'm not clear what happens. BZT = wrong: Similar with the `snapshot'. It sounds like an OS frozen in time when the shutter snapped. But can you move it to a new disc and boot up? On further consideration I need to drop this about snapshot.. After all, applying the term to real photographic snapshots, one would never expect a real snapshot to have the capabilities of the subject of the snap. So poor analagy... deeply flawed. But what about `clone'? It seems my reasoning stands on that. ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] Cannot Mirror RPOOL, Can't Label Disk to SMI
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 output, we could provide more guidance. Cindy Moinak Ghosh wrote: On Tue, Feb 3, 2009 at 2:21 PM, Handojo hando...@yahoo.com wrote: [...] hando...@opensolaris:~# zpool add rpool c4d0 cannot label 'c4d0': EFI labeled devices are not supported on root pools. hando...@opensolaris:~# Try: zpool add rpool c4d0p1 ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] Cannot activate BE
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 wiki relates to the OpenSolaris release, but provides some general ZFS troubleshooting scenarios. Cindy Sébastien Stormacq wrote: Hello Cindy, Looks like everything went fine this tile. Thanks for the detailed procedure. Just one last question : how to check the boot on the second disk (step 7) ? Is it as simple as removing my primary disk from the pool and reboot ? or a more complex procedure ? Thanks Seb --- Sébastien Stormacq Senior Software Architect GSS Software Practice, Sun Microsystems Luxembourg On 26 Jan 2009, at 19:18, cindy.swearin...@sun.com wrote: 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 recovery might be to just relabel the disk while it is still part of the root pool. I'm not sure how ZFS will react if the disk label is changing while the disk is still part of the pool. That's a test for another day... :-) Cindy 1. Make sure the system is currently bootable from c4t0d0s0. 2. Detach the second disk, c4t1d0s2, like this: # zpool detach rpool c4t1d0s2 3. Convert the existing EFI label on the disk to VTOC (SMI). # format -e c4t1d0s2 format label [0] SMI Label [1] EFI Label Specify Label type[1]: 0 Auto configuration via format.dat[no]? Auto configuration via generic SCSI-2[no]? format q Make sure all the disk space is in s2 or recreate it in s0. The relabeling process might go back to the default sizing so check to see that all the disk space is where you want it. (Write me offline if you need help with this step.) 4. Reattach the disk, c4t1d0s2, like this: # zpool attach rpool c4t0d0s0 c4t1d0s2 5. Wait for the newly attached disk to resilver completely by using zpool status to watch the progress. 6. Install the bootblock on the newly attached disk. # installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c4t1d0s2 7. Confirm that you can boot from c4t1d0s2. Sébastien Stormacq wrote: Hello, I tried that already format shows only a Solaris partition. I did label the disk too but r...@yajug:~# zpool attach rpool mirror c4t1d0 cannot label 'c4t1d0': EFI labeled devices are not supported on root pools. Seb --- Sébastien Stormacq Senior Software Architect GSS Software Practice, Sun Microsystems Luxembourg On 23 Jan 2009, at 23:42, Evan Layton wrote: Try running format, choose that disk, run fdisk and remove the EFI fdisk partition and create a Solaris partition. Then in format label the disk. -evan Sébastien Stormacq wrote: OK will try this Any suggestion to repartition ? I can't remind the exact errors but it seems that fdisk is not happy at all with the EFI partition :-( thanks --- Sébastien Stormacq Senior Software Architect GSS Software Practice, Sun Microsystems Luxembourg On 23 Jan 2009, at 23:26, Evan Layton wrote: On Jan 23, 2009, at 3:15 PM, Sébastien Stormacq sebastien.storm...@sun.com wrote: Evan, Using BE_PRINT_ERR=true (instead of 1 ;-) gives one more line that point to the error s...@yajug:~# beadm activate opensolaris-1 be_do_installgrub: installgrub failed for device c4t1d0s2. c4t1d0s2 is a mirror in my zpool s...@yajug:~# zpool status pool: rpool state: ONLINE scrub: resilver completed after 0h4m with 0 errors on Wed Jan 21 13:57:10 2009 config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 mirror ONLINE 0 0 0 c4t0d0s0 ONLINE 0 0 0 23.9M resilvered c4t1d0s2 ONLINE 0 0 0 4.16G resilvered errors: No known data errors I did not install grub (yet) on the second disk Actually, I had a whole bunch of issues to include that disk in the mirror because it is EFI partitioned Any suggestion ? EFI labeled disks are not supported for root pools. The only thing I can suggest is to remove that device from the pool and remove the EFI labeled partition, create a solaris fdisk partition (vtoc) and re-attach the device. -evan Thanks for your help --- Sébastien Stormacq Senior Software Architect GSS Software Practice, Sun Microsystems Luxembourg On 23 Jan 2009, at 23:11, Evan Layton wrote: Sébastien Stormacq wrote: Hello, I installed OpenSolaris 2008.11 on a Sun v40z machine. Unfortunately the build I use, although being 101b was not the latest one, i.e. it was a couple of hours before GA : Sun Microsystems Inc. SunOS 5.11 snv_101b
Re: [indiana-discuss] Keyboard mapping with different language
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: http://opensolaris.org/os/documentation/ 2. OpenSolaris administration information wiki is here: http://wikis.sun.com/display/OpenSolarisInfo/Home 3. The Solaris Express information on docs.sun.com is most similar to OpenSolaris features except for installation and packaging. If you search for information on docs.sun.com, then click on the links the Solaris Express collections. For example, the administration collection is here: http://docs.sun.com/app/docs/coll/47.23 Jasse Jansson wrote: On Jan 27, 2009, at 4:47 PM, Javier Acosta wrote: hi Jasse, well, it seems to me like a bug. Anyway, I believe that there is an easier workaround than letting your computer run 24/7: you can add the following line at the end of the file: /etc/ default/init LANG=en_US.UTF-8 Yay, that did it. Hmm, I can't find much info at all about this indiana distro at the opensolaris site, but I assume that most dox found at docs.sun.com still applies ? Kaiser Jasse -- Authorized Stealth Oracle The axioms of wisdom: 1. Go the SPARC way of life 2. You can't conquer the universe without the knowledge of FORTRAN 3. In the Unix realm, 10% of work fixes 90% of the problems ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] Cannot activate BE
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 recovery might be to just relabel the disk while it is still part of the root pool. I'm not sure how ZFS will react if the disk label is changing while the disk is still part of the pool. That's a test for another day... :-) Cindy 1. Make sure the system is currently bootable from c4t0d0s0. 2. Detach the second disk, c4t1d0s2, like this: # zpool detach rpool c4t1d0s2 3. Convert the existing EFI label on the disk to VTOC (SMI). # format -e c4t1d0s2 format label [0] SMI Label [1] EFI Label Specify Label type[1]: 0 Auto configuration via format.dat[no]? Auto configuration via generic SCSI-2[no]? format q Make sure all the disk space is in s2 or recreate it in s0. The relabeling process might go back to the default sizing so check to see that all the disk space is where you want it. (Write me offline if you need help with this step.) 4. Reattach the disk, c4t1d0s2, like this: # zpool attach rpool c4t0d0s0 c4t1d0s2 5. Wait for the newly attached disk to resilver completely by using zpool status to watch the progress. 6. Install the bootblock on the newly attached disk. # installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c4t1d0s2 7. Confirm that you can boot from c4t1d0s2. Sébastien Stormacq wrote: Hello, I tried that already format shows only a Solaris partition. I did label the disk too but r...@yajug:~# zpool attach rpool mirror c4t1d0 cannot label 'c4t1d0': EFI labeled devices are not supported on root pools. Seb --- Sébastien Stormacq Senior Software Architect GSS Software Practice, Sun Microsystems Luxembourg On 23 Jan 2009, at 23:42, Evan Layton wrote: Try running format, choose that disk, run fdisk and remove the EFI fdisk partition and create a Solaris partition. Then in format label the disk. -evan Sébastien Stormacq wrote: OK will try this Any suggestion to repartition ? I can't remind the exact errors but it seems that fdisk is not happy at all with the EFI partition :-( thanks --- Sébastien Stormacq Senior Software Architect GSS Software Practice, Sun Microsystems Luxembourg On 23 Jan 2009, at 23:26, Evan Layton wrote: On Jan 23, 2009, at 3:15 PM, Sébastien Stormacq sebastien.storm...@sun.com wrote: Evan, Using BE_PRINT_ERR=true (instead of 1 ;-) gives one more line that point to the error s...@yajug:~# beadm activate opensolaris-1 be_do_installgrub: installgrub failed for device c4t1d0s2. c4t1d0s2 is a mirror in my zpool s...@yajug:~# zpool status pool: rpool state: ONLINE scrub: resilver completed after 0h4m with 0 errors on Wed Jan 21 13:57:10 2009 config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 mirror ONLINE 0 0 0 c4t0d0s0 ONLINE 0 0 0 23.9M resilvered c4t1d0s2 ONLINE 0 0 0 4.16G resilvered errors: No known data errors I did not install grub (yet) on the second disk Actually, I had a whole bunch of issues to include that disk in the mirror because it is EFI partitioned Any suggestion ? EFI labeled disks are not supported for root pools. The only thing I can suggest is to remove that device from the pool and remove the EFI labeled partition, create a solaris fdisk partition (vtoc) and re-attach the device. -evan Thanks for your help --- Sébastien Stormacq Senior Software Architect GSS Software Practice, Sun Microsystems Luxembourg On 23 Jan 2009, at 23:11, Evan Layton wrote: Sébastien Stormacq wrote: Hello, I installed OpenSolaris 2008.11 on a Sun v40z machine. Unfortunately the build I use, although being 101b was not the latest one, i.e. it was a couple of hours before GA : Sun Microsystems Inc. SunOS 5.11 snv_101b November 2008 I tried to update to GA with image-update r...@yajug:~# pkg list -u NAME (AUTHORITY) VERSION STATE UFIX entire0.5.11-0.101 installed u--- r...@yajug:~# pkg image-update PHASEACTIONS Update Phase 1/1 PHASE ITEMS Reading Existing Index 9/9 Indexing Packages1/1 pkg: unable to activate opensolaris-1 r...@yajug:~# beadm activate opensolaris-1 Unable to activate opensolaris-1. Unknown external error. How can I further diagnose / solve this ?? Can you set export BE_PRINT_ERR=true before running beadm activate and send the debug output? That should help narrow down where the problem is. Thanks, -evan I followed the same procedure with the same image on a couple of VMs and it was always
Re: [indiana-discuss] unnessesary services?
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 computing roles/environments, doesn't exist. I think I'll look into writing something like that myself. ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] unnessesary services?
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 unsure whether all services are included in this section, but it should be close enough. Since we currently provide information for various Solaris releases, it is not always in the same location. I apologize for the confusion. Just ask if you can't find anything. Another venue for information questions is docs-disc...@opensolaris.org. Cindy Rand All wrote: I'm trying out OpenSolaris as a regular desktop OS, and it works fine, but it seems to be using a lot more memory than it probably ought to. svcs shows a ton of services running by default, and I'm sure I don't need all of them for everyday desktop stuff, so I want to disable services I don't need. The problem is that a lot of them have really cryptic names, and I can't find any good descriptions of what they all do. I've scoured Sun's Solaris docs, but they're not very well-organized. Can anyone point me to a simple list of service names, descriptions, functions, etc.? ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] BE not activate during update from svn_99 to latest (hopefully 08.11 RC1)
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 [1] EFI Label Specify Label type[1]: 0 Ready to label disk, continue? yes format quit 3. Attach the disk. # zpool attach rpool c9t4d0s0 c9t0d0s0 Tom Georgoulias wrote: Ethan Quach wrote: [EMAIL PROTECTED]:~# pfexec pkg refresh [EMAIL PROTECTED]:~# pfexec pkg install [EMAIL PROTECTED] No updates available for this image. [EMAIL PROTECTED]:~# pfexec pkg install [EMAIL PROTECTED] No updates available for this image. Since you're running b99, these should have been @0.5.11,0.5.11-0.99 Makes sense. Might be worth updating the notes here, they will have the 0.86 number in them: http://opensolaris.org/os/project/indiana/resources/relnotes/200811/x86/ If you get here, the new BE has been created and updated successfully, just not activated. Can you try to activate it from the command line and see what errors come out (you may need to turn on the BE debug to get more useful data): # BE_PRINT_ERR=true beadm activate opensolaris-3 Here you go, looks like it doesn't like the rpool setup or something. [EMAIL PROTECTED]:~# beadm list BEActive Mountpoint Space Policy Created ---- -- - -- --- opensolaris - - 12.25M static 2008-10-14 14:49 opensolaris-2 NR / 8.81G static 2008-10-15 10:35 opensolaris-3 - /tmp/tmp6tfVpN 1.51G static 2008-11-19 10:23 [EMAIL PROTECTED]:~# BE_PRINT_ERR=true beadm activate opensolaris-3 be_do_installgrub: installgrub failed for device c9t0d0s0. Unable to activate opensolaris-3. Unknown external error. [EMAIL PROTECTED]:~# zpool status rpool pool: rpool state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 mirror ONLINE 0 0 0 c9t4d0s0 ONLINE 0 0 0 c9t0d0s0 ONLINE 0 0 0 errors: No known data errors ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] [sysadmin-discuss] /dev/null disappeared and unable to recreate 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 installs. For some unknown reason, /dev/null disappeared. We tried to reboot but it didn't help. We're running SNV93. /devices/pseudo/[EMAIL PROTECTED]:null does exist and permissions are correct : # ls -l /devices/pseudo/[EMAIL PROTECTED]:null crw-rw-rw- 1 root sys 13, 2 août 21 15:59 /devices/pseudo/[EMAIL PROTECTED]:null devfsadm and devfsadm -P fail : # devfsadm -V chatty | grep null devfsadm: cannot create link: /dev/null - ../devices/pseudo/[EMAIL PROTECTED]:null. max attempts exceeded devfsadm[2456]: chatty: minor_process: node=mm, minor=null devfsadm[2456]: chatty: reset_node_permissions: phy_path=/devices/pseudo/[EMAIL PROTECTED]:null lphy_path=/pseudo/[EMAIL PROTECTED]:null /dev is writable by root and I can create files or symlinks into it, as long as they're not named, you guessed it, null. I didn't find any reference to that particular issue. Has anyone encountered that issue already ? This message posted from opensolaris.org ___ sysadmin-discuss mailing list [EMAIL PROTECTED] http://mail.opensolaris.org/mailman/listinfo/sysadmin-discuss ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] REVIEW System Admin. Guide for the Back to School Kit
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 student installing the Back to School Kit its probably best to create a personal user account for papers, etc. For the general comment: Please explain how pfexec is safer. :-) Thanks, Cindy (William) Brian Leonard wrote: Hi Kathy: Is the intent to keep this command line focused? In several cases there are GUIs you can work with for: * Managing services * Managing processes * Shutting down the system * Verifying device driver support Other notes: How to Stop a Program: In this case, look for the bash process for pts/2 which has a process ID of 689. For me it's pts/3 and the process id will always differ. Also, the ps command by itself is pretty useless. I generally use ps -ef | grep 'some string' I would also echo the sentiments of others to use pfexec instead of becoming superuser. It's much safer. Note that the Server type should be IMAP Mail Server Why are you assuming this is the case? You're probably better off just listing resources on how to configure Thunderbird to connect to popular mail servers, such as Yahoo!, gmail, etc. In addition to the system user account, you should create a user account and ZFS file system for your personal files that can be managed by delegating ZFS administration permissions, such as creating a file system snapshot. Interesting. Why do we recommend creating a 2nd user account? I'm new to OpenSolaris, but this is the first I've heard of this. http://blogs.sun.com/timf/resource/README.zfs-auto-backup.txt Consider pointing them to Tim's blog on this subject instead: http://blogs.sun.com/timf/entry/zfs_automatic_for_the_people mount -F smbfs //solarsystem/tmp /mnt Before you can mount a SMB client you need to first enable the service via the GUI or the command line (svcadm enable network/smb/client) Shut down the system. Shouldn't the first suggestion be the System Shutdown menu? And from the command line, shouldn't we recommend shutdown over init 5? Regards, Brian Kathy Slattery wrote: I have been leading a group of writers working on a companion to the Getting Started Guide. The idea is to document some useful procedures to help configure an OpenSolaris laptop after the OS is installed. Please take a look at a review draft of the OpenSolaris 2008.05 System Administration Guide (OSadminguide.pdf) at: http://www.opensolaris.org/os/project/indiana/files/ We have been working on this book for a couple of weeks, so we haven't had time to complete all sections or polish the content yet, but the current content should give you an idea of what we have decided to cover. In particular, the chapter about Useful Commands has not been worked on yet. Also, the links to docs.sun.com aren't working. I need to deliver this book for the Back To School Kit before August 8th, so please send me comments by COB on Wednesday 8/6. We will be developing this book further after the 8th for the 2008.11 release, so there will be more time for comments later. For now: 1) send any corrections to me or to the alias if discussion is needed 2) tell me about any procedures that we should add 3) please give me suggestions for a better book title Many thanks for your time and comments. -Kathy -- This message posted from opensolaris.org ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss -- (William) Brian Leonard Technology Evangelist 408.404.6884 http://weblogs.java.net/blog/bleonard ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] REVIEW System Admin. Guide for the Back to School Kit
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 creates a user account with a home dir as a directory not a ZFS file system. If I create a ZFS file system and feed it to user account manager, it doesn't setup the user home dir ownership correctly. In the meantime, I'll figure something else out. Thanks for feedback-- Cindy Dave Miner wrote: [EMAIL PROTECTED] wrote: 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 student installing the Back to School Kit its probably best to create a personal user account for papers, etc. I haven't reviewed the document, but this exchange caught my eye. The account can assume the role, but only does so when specifically requested by entering a profiled shell or using pfexec. There's no extra privilege when you're running in, say, bash or ksh. Please do not recommend a second user account, it makes OpenSolaris appear needlessly complex. At some point we may alter the RBAC privileges created by default to be somewhat less expansive than they are right now, but presently the behavior that results is what is expected for a single-user system, which is that the user can administer his own system. Dave ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] [docs-discuss] REVIEW System Admin. Guide for the Back to School Kit
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 aren't we using the roles? In previous Solaris versions, we recommended setting up roles and using them, and not using pfexec manually. Since I'm late to this party, please feel free set me straight. Regards, Cindy - Original Message - From: Glynn Foster [EMAIL PROTECTED] Date: Friday, August 1, 2008 4:57 pm Subject: Re: [docs-discuss] REVIEW System Admin. Guide for the Back to School Kit To: Kathy Slattery [EMAIL PROTECTED] Cc: indiana-discuss@opensolaris.org, [EMAIL PROTECTED] On 2/08/2008, at 10:17 AM, Kathy Slattery wrote: I have been leading a group of writers working on a companion to the Getting Started Guide. The idea is to document some useful procedures to help configure an OpenSolaris laptop after the OS is installed. Please take a look at a review draft of the OpenSolaris 2008.05 System Administration Guide (OSadminguide.pdf) at: http://www.opensolaris.org/os/project/indiana/files/ A couple of comments based on an initial read - - 'How to start a Program' The use of program seems a little strange, perhaps it should be 'how to start a service' - No mention of pfexec? Given that this is one of the major features of 2008.05, it seems a pity not to mention it. - It would be great to detail how to connect to an encrypted network (WEP/WPA) through use of the dladm create-secobj command. - No mention of IPS/packagemanager? Glynn ___ docs-discuss mailing list [EMAIL PROTECTED] ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
