I love hacks which make your life easier, but I also love an evolving OS. It used to be to do ssh-agent management, I had the following in my .dtprofile (and I think dt is no longer being invoked):
###
if whence ssh-agent > /dev/null && [[ ${SSH_AGENT_PID:-0} -eq 0 ]]
then
eval $(ssh-agent) > /dev/null
trap "kill $SSH_AGENT_PID" EXIT
fi
(xterm -e ssh-add &)
###
I'd get a little X window and have to manually enter my pass phrases every time I rebooted.
I don't know when it was introduced, but we now have a proper keychain manager and I'm loving it.
Reinstall with a graphical install option appears to have configured X for me, I'm now able to login to the headed console. I'll fix that later.
Now to reinstall everything.
Note that I kept the second zpool, so it was easy to import it and quicker to reinstall my stuff.
And sweet, the Sun Ray software just installs and runs! The crowds go wild!
Hmm, the fonts for the icons on the screen look sharp. Those in my terminal window look like they are from the 80s. Yuck!
At last, a bright spot:
[root@warlock archives]> cdrw -l
Looking for CD devices...
Node Connected Device Device type
----------------------+--------------------------------+-----------------
cdrom0 | AOPEN COM5232/AAH PRO 1.04 | CD Reader/Writer
cdrom1 | AOPEN DUW1608/ARR A04b | CD Reader/Writer
instead of ... ahh, I don't have a capture of it
Much easier to remember which is which now for me...
So my w2100z is fully installed, but not fully functional. I learned some valuable lessons along the way, and I'm not yet done. Things brought back to the surface:
And the big one, sometimes it is better to go to bed than futz with things just a bit longer.
I've tried both Sun Ray Software 4 Update 3 Beta for Solaris 10 5/08 X86 and Sun Ray Software 4 09/07. In both cases I've got the 26D error. I know that the firmware on the DTU is being changed between releases and the server software knows about the DTU.
I've tried the following things to get this working:
And I left it there with the last one. I'm about to restart. I think that perhaps fixing my menu.lst has caused this issue or I have to face the fact that I upgraded to too modern a build. But since I never had this problem before and I don't have my hands on the prior configurations, I'll try to get it working.
Strike part of that, I do have /etc/dt/config archived off and it shows I never did the Xserver thing:
[th199096@warlock config]> ls -la total 26 drwxr-xr-x 2 root other 6 Sep 25 12:41 . drwxr-xr-x 3 root other 3 Mar 29 2008 .. -r--r--r-- 1 root sys 1577 Aug 1 2007 README.SUNWut lrwxrwxrwx 1 root root 34 Sep 29 02:58 Xconfig -> /tmp/SUNWut/config/xconfig/Xconfig -r--r--r-- 1 root root 5868 Mar 29 2008 Xconfig.SUNWut.prototype lrwxrwxrwx 1 root root 35 Sep 29 02:58 Xservers -> /tmp/SUNWut/config/xconfig/Xservers
Okay, I fixed that back out and I told grub not to boot to the console. But I didn't tell eeprom(1M):
[root@warlock ~]> eeprom ata-dma-enabled=1 atapi-cd-dma-enabled=1 ttyb-rts-dtr-off=false ttyb-ignore-cd=true ttya-rts-dtr-off=false ttya-ignore-cd=true ttyb-mode=9600,8,n,1,- ttya-mode=9600,8,n,1,- lba-access-ok=1 prealloc-chunk-size=0x2000 keyboard-layout=US-English console=ttya boot-file=bootadm: kernel command on line 64 not recognized. boot-args=bootadm: kernel command on line 64 not recognized. [root@warlock ~]> eeprom console=text [root@warlock ~]>
By the way, if this is horked, so am I. :->
Okay, I'm horked. I have to come up in failsafe mode. Now how do I fix my eeprom? Luckily, is it?, I've had to do this in the past - eeprom hosed on an x86. And it has the sed command I will need because I refuse to learn how to configure my terminal! And I've saved above what the real value should be!
# pwd /a/boot/solaris # sed 's/text/ttya/' bootenv.rc > xxx # diff bootenv.rc xxx 39c39 < setprop console 'text' --- > setprop console 'ttya' # cp xxx bootenv.rc # reboot Creating boot_archive for /a
So I'm not getting X on the headed headless server (i.e., I've attached a monitor). I get output there until the OS takes over.
What is in my /var/dt/Xerrors?
Fatal server error:
could not open default font 'fixed'
XIO: fatal IO error 146 (Connection refused) on X server ":2.0"^M
after 0 requests (0 known processed) with 0 events remaining.^M
failed to set default font path '/usr/openwin/lib/X11/fonts/Type1/,/usr/openwin/lib/X11/fonts/Type1/sun/,/usr/openwin/lib/X11/fonts/F3bitmaps/,/
usr/openwin/lib/X11/fonts/Speedo/,/usr/openwin/lib/X11/fonts/misc/,/usr/openwin/lib/X11/fonts/75dpi/,/usr/openwin/lib/X11/fonts/100dpi/,/usr/ope
nwin/lib/X11/fonts/TrueType'
One of the directories in the list above does not exist
or it does not contain a valid 'fonts.dir' file
Okay, lets take care of that! All of them existed and none had a valid 'fonts.dir' file. And now:
Fatal server error:
could not open default font 'fixed'
XIO: fatal IO error 146 (Connection refused) on X server ":2.0"^M
after 0 requests (0 known processed) with 0 events remaining.^M
I'm really coming to suspect X is the thing horked on this system.
It looks like something, perhaps eeprom touched my menu.lst and added a new and default setting for me:
title Diagnostic Partition
rootnoverify (hd0,0)
chainloader +1
#---------- ADDED BY BOOTADM - DO NOT EDIT ----------
title Solaris bootenv rc
findroot pool_rpool
kernel$ /platform/i86pc/kernel/$ISADIR/unix -B console=ttya bootadm: kernel command on line 64 not recognized.
-B bootadm: kernel command on line 64 not recognized.
module$ /platform/i86pc/$ISADIR/boot_archive
#---------------------END BOOTADM--------------------
#BOOTADM RC SAVED DEFAULT: 0
Which yields:
krtld: Unused kernel arguments: `bootadm: kernel command on line 64 not recognized.'. SunOS Release 5.11 Version snv_99 64-bit Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. NOTICE: mount: not a UFS magic number (0x0) Cannot mount root on /ramdisk:a fstype ufs panic[cpu0]/thread=fffffffffbc293a0: vfs_mountroot: cannot mount root fffffffffbc48dc0 genunix:vfs_mountroot+356 () fffffffffbc48df0 genunix:main+e6 () fffffffffbc48e00 unix:_locore_start+92 () skipping system dump - no dump device configured SunOS Release 5.11 Version snv_99 64-bit Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Hostname: warlock Reading ZFS config: done. Mounting ZFS filesystems: (8/8)
I've got the head on it, so I'm going to reinstall and see if I can at least get X working on it.
While I'm waiting on my installs to finish, I thought I would tinker with the Western Digital My Passport Essential WDMENG1600TN 160GB USB 2.0 I thought I was using for my Time Machine Backup for my Mac Book Air. It had stopped working one day.
I've hooked the USB drive up to several computers and I haven't even seen it appear. I tried another WD USB drive and it was working. Anyway, tonight I finally tried changing out the USB cables from the two and it started working. And the "bad" cable worked with the other drive.
I used the WD tools to reformat it back to factory spec and then I couldn't see it on my MBA. I pulled the unpowered Belkin mini-USB hub and plugged it straight in. Joy!
Speaking of which the 4 port mini-USB hub from Belkin tricked me with the packaging. It looked like it had an external power supply tucked in it, but it was only folded paper. This is the hub which rotates. It is called a Swivel Hub. I won't be taking it on trips now.
Anyway, my Time Machine backup is now proceeding from scratch.
Okay, so I got this configuration:
# zpool list
NAME SIZE USED AVAIL CAP HEALTH ALTROOT
rpool 68G 7.18G 60.8G 10% ONLINE -
# zpool iostat -v
capacity operations bandwidth
pool used avail read write read write
------------ ----- ----- ----- ----- ----- -----
rpool 7.18G 60.8G 31 14 814K 528K
mirror 7.18G 60.8G 31 14 814K 528K
c1t0d0s0 - - 12 8 509K 530K
c1t1d0s0 - - 13 8 510K 530K
------------ ----- ----- ----- ----- ----- -----
But I don't want a mirror, I want space!
This should work, but it doesn't:
# zpool detach rpool c1t1d0s0
# zpool iostat -v
capacity operations bandwidth
pool used avail read write read write
---------- ----- ----- ----- ----- ----- -----
rpool 7.18G 60.8G 8 6 367K 383K
c1t0d0s0 7.18G 60.8G 8 6 367K 383K
---------- ----- ----- ----- ----- ----- -----
# zpool add rpool c1t1d0s0
invalid vdev specification
use '-f' to override the following errors:
/dev/dsk/c1t1d0s0 overlaps with /dev/dsk/c1t1d0s2
# zpool add -f rpool c1t1d0s0
cannot add to 'rpool': root pool can not have multiple vdevs or separate logs
Ahh, I should have done some light reading, from ZFS Troubleshooting Guide:
You cannot use a RAID-Z configuration for a root pool. Only single-disk pools or pools with mirrored disks are supported.
I was thinking of reinstalling, but no, I'll go with two different pools. By the way, I understand the need for redundancy, but I'd prefer more spindles here.
# zpool create tank c1t1d0s0
invalid vdev specification
use '-f' to override the following errors:
/dev/dsk/c1t1d0s0 overlaps with /dev/dsk/c1t1d0s2
# zpool create -f tank c1t1d0s0
# zpool iostat -v
capacity operations bandwidth
pool used avail read write read write
---------- ----- ----- ----- ----- ----- -----
rpool 7.18G 60.8G 5 4 246K 255K
c1t0d0s0 7.18G 60.8G 5 4 246K 255K
---------- ----- ----- ----- ----- ----- -----
tank 73.5K 68.0G 0 9 18.3K 165K
c1t1d0s0 73.5K 68.0G 0 9 18.3K 165K
---------- ----- ----- ----- ----- ----- -----
When I last configured my w2100z, it wasn't possible to have a ZFS root. And I did some funky stuff playing around with it. My current configuration (I have 2 drives, which I think should be 72G):
0. c1t0d0
/pci@5,0/pci1022,7450@4/pci108e,534d@4,1/sd@0,0
Part Tag Flag Cylinders Size Blocks
0 root wm 524 - 3134 20.00GB (2611/0/0) 41945715
1 swap wu 1 - 523 4.01GB (523/0/0) 8401995
2 backup wm 0 - 8913 68.28GB (8914/0/0) 143203410
3 unassigned wm 3135 - 5745 20.00GB (2611/0/0) 41945715
4 unassigned wm 5746 - 8356 20.00GB (2611/0/0) 41945715
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 0 0 (0/0/0) 0
7 home wm 8357 - 8913 4.27GB (557/0/0) 8948205
8 boot wu 0 - 0 7.84MB (1/0/0) 16065
9 unassigned wm 0 0 (0/0/0) 0
1. c1t1d0
/pci@5,0/pci1022,7450@4/pci108e,534d@4,1/sd@1,0
Part Tag Flag Cylinders Size Blocks
0 stand wm 1 - 4466 34.21GB (4466/0/0) 71746290
1 stand wm 4467 - 8932 34.21GB (4466/0/0) 71746290
2 backup wu 0 - 8932 68.43GB (8933/0/0) 143508645
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0
8 boot wu 0 - 0 7.84MB (1/0/0) 16065
9 unassigned wm 0 0 (0/0/0) 0
I've shamelessly munged together output from different format commands. Anyway, the first drive has several available partitions for Live Update and grabbing in case of need. The second drive has two partitions used for ZFS.
This configuration is very flexible for doing updates. I can have several boot partitions on the root drive and I never have to worry about the data on my ZFS pool:
[root@warlock snv99]> zpool list zoo
NAME SIZE USED AVAIL CAP HEALTH ALTROOT
zoo 68G 51.5G 16.5G 75% ONLINE -
[root@warlock snv99]> zpool iostat -v
capacity operations bandwidth
pool used avail read write read write
---------- ----- ----- ----- ----- ----- -----
zoo 51.5G 16.5G 0 1 21.9K 60.8K
c1t1d0s0 33.6G 381M 0 0 7.31K 12.0K
c1t1d0s1 17.9G 16.1G 0 1 14.6K 48.8K
---------- ----- ----- ----- ----- ----- -----
But I think I want to live more on the edge. I'm looking to get a more modern build on warlock:
[root@warlock snv99]> uname -a SunOS warlock 5.11 snv_85 i86pc i386 i86pc
So, I'm going to back everything up onto an attached USB drive, and nuke the entire system.
Back in a bit
Since warlock is headless, the first task is to build an install DVD which has a modified menu.lst for grub - see Getting a Solaris bootable DVD for headless x86es.
While I'm doing that, I'm going to back up my system. I need the contents of /etc, my punchin configuration (a Sun VPN tool), my Sun Ray server configuration, and my homedirs. The rest I could probably care less about or already have saved off.
Also, I'm pretty ruthless, once I decide I don't need something, I will delete it. That gives me a better idea of how how much I still have to backup. And no, I'm not talking system stuff. Take for example here where I delete some ISO images:
[th199096@warlock isos]> df -h . Filesystem size used avail capacity Mounted on zoo/isos 67G 29G 16G 65% /zoo/isos [th199096@warlock x86]> rm -rf snv7* snv8* snv90/ snv97 [th199096@warlock x86]> df -h . Filesystem size used avail capacity Mounted on zoo/isos 67G 12G 33G 27% /zoo/isos
You may not be comfortable with this approach, but once you reinstall it is gone anyway.
Cleaned out, the ISO is booting in a VirtualBox on my WinXP desktop, so I'm signing off here....