headers
Lumpkin, Buddy | 1 Mar 2004 09:44

RE: SS1000 does random? hard lockups during Sol 8 install.

Any component could be at fault.

I would suggest removing all SBUS cards including your frame buffer, all CPUs
but one and all memory sticks but one and booting from serial port A. If it
still locks up swap the installed CPU and memory DIMM with one of your spares
and check again. If the hanging goes away, divide and conquer.

Regards,

--Buddy

-----Original Message-----
From: sunhelp-bounces <at> sunhelp.org [mailto:sunhelp-bounces <at> sunhelp.org]On
Behalf Of Jon
Sent: Thursday, February 26, 2004 9:35 PM
To: SunHELP <at> sunhelp.org
Subject: [SunHELP] SS1000 does random? hard lockups during Sol 8
install.

I've tried a few times to reinstall Sol 8 on my SS1000.  I just got a
Turbo GX and put it in last night, so I decided to reinstall Sol to get
the drivers and put all the  packages it wanted on. (I've got a single
4.5GB drive in it.  Anyone have the main quad drive bracket/rails or a
disk card for an SS1000?)  I thought it might be overheating, so I
checked and cleaned a layer of lint from the intake screen under the
side cover.  I also took out an MBUS module that has some physical
damage.  Still it locks up.  It seemed to be running fine as a headless
machine with just my Wyse 60 on the console with 6 CPUs installed.  For
now even removing the "bad" module seems to have no effect on these
seemingly random lockups.  Of course, now that I've got a borked Sol 8
(Continue reading)

Permalink | Reply | 0 comments |
headers
Francois Dion | 1 Mar 2004 16:10

Sun 3510fc SAN serial port

How do you talk to the box? What kind of cable? I have a serial cable, 
null modem adapter, gender changers, db9->rj45 Sun adapters and I tried 
all kinds of combos and I get nothing. I can access all my other Sun 
equipment with the serial console, but this unit uses a db9 instead of 
an rj45, so that might have something to do.

I have to get to the serial console to set the IP address, then I'll be 
able to manage it from my management network, but if I cant get on the 
console, I cant set that.

Any idea?

Thanks,
Francois
Permalink | Reply | 3 comments |
headers
Tom Jones | 1 Mar 2004 16:39
Favicon

Re: Sun 3510fc SAN serial port

Here's the port config from our Annex box which is connected to our 3510FC:

port asy4:

                        Port Generic Parameters

                mode: slave                        location: ""
                type: hardwired                    term_var: ""
              prompt: ""                      cli_interface: uci
               speed: 38400                        autobaud: N
           data_bits: 8                           stop_bits: 1
              parity: none                max_session_count: 3
     allow_broadcast: Y                 broadcast_direction: port
         imask_7bits: N                          cli_imask7: Y
   ps_history_buffer: 0                              banner: Y
       tcp_keepalive: 0                   dedicated_address: 0.0.0.0
      dedicated_port: 5004                    type_of_modem: ""
default_session_mode: interactive       dedicated_arguments: ""
    resolve_protocol: connect

Note the baud rate of 38400.  

Tom Jones

----- Original Message ----- 
From: "Francois Dion" <fdion <at> atriumwindows.com>
To: "The SunHELP List" <sunhelp <at> sunhelp.org>
Sent: Monday, March 01, 2004 9:10 AM
Subject: [SunHELP] Sun 3510fc SAN serial port
(Continue reading)

Permalink | Reply | 2 comments |
headers
Markham, Richard | 1 Mar 2004 17:09

RE: Root partition disk space requirement for upgrading O/S

seems like we got away with 400mb that was the /usr fs.

-----Original Message-----
From: Nguyen, David M [mailto:david.m.nguyen <at> xo.com]
Sent: Friday, February 27, 2004 12:58 PM
To: sunhelp <at> sunhelp.org
Subject: [SunHELP] Root partition disk space requirement for upgrading
O/S

We are running solaris 5.7 and we plan to upgrade them to solaris 8.
Based on documentation, it requires root partition to have at leaset
800Meg free disk spaces prior to upgrade.  The problem we have on all
our systems is the root partition only has 700Kbytes free disk spaces
left but we have plenty room on /export/home partition.  Is there a way
to solve disk space issue on root partition?  And does it really mean
root partition must have 800Meg free disk space left to successfully
upgrade the O/S?

Thanks,
David
_______________________________________________
SunHELP maillist  -  SunHELP <at> sunhelp.org
http://www.sunhelp.org/mailman/listinfo/sunhelp
Permalink | Reply | 0 comments |
headers
Francois Dion | 1 Mar 2004 17:30

Re: Sun 3510fc SAN serial port

Thanks! That worked. I assumed 9600. Wow, 38400 on Sun equipment, I 
guess I have to get with the program!

I was able to access the UI, set the IP etc. I used a regular db9 cable 
and connected straight to my laptop with no nullmodem or anything.

Francois

Tom Jones wrote:

>Here's the port config from our Annex box which is connected to our 3510FC:
>
>port asy4:
>
>                        Port Generic Parameters
>
>                mode: slave                        location: ""
>                type: hardwired                    term_var: ""
>              prompt: ""                      cli_interface: uci
>               speed: 38400                        autobaud: N
>           data_bits: 8                           stop_bits: 1
>              parity: none                max_session_count: 3
>     allow_broadcast: Y                 broadcast_direction: port
>         imask_7bits: N                          cli_imask7: Y
>   ps_history_buffer: 0                              banner: Y
>       tcp_keepalive: 0                   dedicated_address: 0.0.0.0
>      dedicated_port: 5004                    type_of_modem: ""
>default_session_mode: interactive       dedicated_arguments: ""
>    resolve_protocol: connect
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Tom Jones | 1 Mar 2004 18:30
Favicon

Re: Sun 3510fc SAN serial port

Sun OEMs the 3510FC from DotHill.  I guess DotHill uses 38400...

Tom
----- Original Message ----- 
From: "Francois Dion" <fdion <at> atriumwindows.com>
To: "The SunHELP List" <sunhelp <at> sunhelp.org>
Sent: Monday, March 01, 2004 10:30 AM
Subject: Re: [SunHELP] Sun 3510fc SAN serial port

> Thanks! That worked. I assumed 9600. Wow, 38400 on Sun equipment, I 
> guess I have to get with the program!
> 
> I was able to access the UI, set the IP etc. I used a regular db9 cable 
> and connected straight to my laptop with no nullmodem or anything.
> 
> Francois
> 
> Tom Jones wrote:
> 
> >Here's the port config from our Annex box which is connected to our 3510FC:
> >
> >port asy4:
> >
> >                        Port Generic Parameters
> >
> >                mode: slave                        location: ""
> >                type: hardwired                    term_var: ""
> >              prompt: ""                      cli_interface: uci
> >               speed: 38400                        autobaud: N
> >           data_bits: 8                           stop_bits: 1
(Continue reading)

Permalink | Reply | 0 comments |
headers
ymui | 1 Mar 2004 21:03
Picon

Mirroring Setup After a hardware error on Boot Disk

Hello Administrators,
There is a hardware problem with the Boot Disk (disk0, i.e. 
/dev/dsk/c0t0d0s2).  The disk is replaced.  metadb commands are executed 
to re-define the database.  After re-establishing the mirroring (metastat 
shows everything ok), metadb -i shows:

        flags           first blk       block count
     a        u         16              1034            /dev/dsk/c0t0d0s3
     a        u         1050            1034            /dev/dsk/c0t0d0s3
     a        u         2084            1034            /dev/dsk/c0t0d0s3
     a    p  luo        16              1034            /dev/dsk/c0t1d0s3
     a    p  luo        1050            1034            /dev/dsk/c0t1d0s3
     a    p  luo        2084            1034            /dev/dsk/c0t1d0s3
o - replica active prior to last mddb configuration change
 u - replica is up to date
 l - locator for this replica was read successfully
 c - replica's location was in /etc/lvm/mddb.cf
 p - replica's location was patched in kernel
 m - replica is master, this is replica selected as input
 W - replica has device write errors
 a - replica is active, commits are occurring to this replica
 M - replica had problem with master blocks
 D - replica had problem with data blocks
 F - replica had format problems
 S - replica is too small to hold current data base
 R - replica had device read errors

Before the hardware problem, it was  like :
   flags           first blk       block count
     a m  p  luo        16              1034            /dev/dsk/c0t0d0s3
(Continue reading)

Permalink | Reply | 2 comments |
headers
Markham, Richard | 1 Mar 2004 21:08

companion cd, vim 6.2 install

I installed vim (only) from the companion cd and it appears that
it still needs some other dependency met.

$ ./vim
ld.so.1: ./vim: fatal: libXm.so.2: open failed: No such file or directory
Killed

What do I need to install (minimally) to run vim?

---------
Solaris 8
Permalink | Reply | 0 comments |
headers
Michael Karl | 1 Mar 2004 21:48
Picon

Re: Mirroring Setup After a hardware error on Boot Disk

Hey,

I'm thinking, that you didn't clear with "metadb -d" the old replica-entries
for the fault old c0t0d0s3 and didn't create new on the actual c0t0d0s3.

1. metadb -d c0t0d0s3
2. metadb -a -c 3 -f c0t0d0s3

Maybe, this should help ... also with rebooting.

Michael

> Hello Administrators,
> There is a hardware problem with the Boot Disk (disk0, i.e.
> /dev/dsk/c0t0d0s2).  The disk is replaced.  metadb commands are executed
> to re-define the database.  After re-establishing the mirroring (metastat
> shows everything ok), metadb -i shows:
> 
>       flags           first blk       block count
>    a        u         16              1034            /dev/dsk/c0t0d0s3
>    a        u         1050            1034            /dev/dsk/c0t0d0s3
>    a        u         2084            1034            /dev/dsk/c0t0d0s3
>    a    p  luo        16              1034            /dev/dsk/c0t1d0s3
>    a    p  luo        1050            1034            /dev/dsk/c0t1d0s3
>    a    p  luo        2084            1034            /dev/dsk/c0t1d0s3
> o - replica active prior to last mddb configuration change
> u - replica is up to date
> l - locator for this replica was read successfully
> c - replica's location was in /etc/lvm/mddb.cf
> p - replica's location was patched in kernel
(Continue reading)

Permalink | Reply | 0 comments |
headers
Dale Ghent | 1 Mar 2004 22:24

Re: Mirroring Setup After a hardware error on Boot Disk

On Mon, 1 Mar 2004 ymui <at> royalsunalliance.ca wrote:

> Hello Administrators,
> There is a hardware problem with the Boot Disk (disk0, i.e.
> /dev/dsk/c0t0d0s2).  The disk is replaced.  metadb commands are executed
> to re-define the database.  After re-establishing the mirroring (metastat
> shows everything ok), metadb -i shows:

<snip>

there is no error there, your new metadbs are working fine.

You will only see the additional p, l and u flags if you reboot and the
kernel is configured from the information in /etc/system at start up.

/dale
Permalink | Reply | 0 comments |

Gmane