Cannot make SS20 run with Seagate disk

Cannot make SS20 run with Seagate disk

Post by Erlend Legange » Mon, 16 Feb 2004 19:32:23



I have an SS20 which needed more disk space. I tried to install a Maxtor
Atlas 10K 36GB, Jumpstarted Solaris 8 02/02 onto it and all worked fine.
Then I tried the same with a Seagate ST318453LC (ie I used the same machine,
I only replaced the disk). The Jumpstart went fine as always, but on the
reboot at the end, the system went into perpetual panic (see below).

What could be wrong? The only strange thing I could see was probe-scsi (see
below) which gave a strange response, showing the same for all Units in
Target 3. Any tips?

- Erlend Leganger

Resetting ...

SPARCstation 20 MP (2 X 390Z50), No Keyboard
ROM Rev. 2.25, 192 MB memory installed, Serial #7745420.
Ethernet address 8:0:20:76:2f:8c, Host ID: 72762f8c.

Rebooting with command:
Boot device:

File and args:
WARNING: cannot open system file: etc/system
SunOS Release 5.8 Version Generic_108528-13 32-bit
Copyright 1983-2001 Sun Microsystems, Inc.  All rights reserved.

panic[cpu0]/thread=f0244020: read_binding_file: /etc/name_to_major file not
found

f02438a0 genunix:read_binding_file+40 (f026234c, f0275f9c, 5, 7530, 0, 0)
  %l0-7: 00000000 f0275f9c ffffffff 00000000 00000000 00000000 00000000
00000e00
f0243a08 genunix:mod_setup+1c (f0276000, f0253000, f0258000, bd, 1a000000,
0)
  %l0-7: f0253000 00001000 f0073f04 f0073f84 00000000 00000000 ffef0000
00000e00
f0243a68 unix:startup+5f0 (f024fc00, f0248800, fbd00000, f5900000, f0586000,
fbd00000)
  %l0-7: 00002000 f5904000 1ae1d000 00000023 f05c0000 000006f6 f027b000
f024f400
f0243b20 genunix:main+4 (40400fe0, 40400fe0, 2000, 404000e0, ffffffff,
f015bbd8)
  %l0-7: f5901000 f0243b88 f007fc00 f00c0000 00000000 00000000 ffef0000
00000e00

skipping system dump - no dump device configured
rebooting...
Resetting ...

 ~
Type  help  for more information
<#0> ok probe-scsi
Target 3
  Unit 0   Disk     SEAGATE ST318453LC      00033JY08TGK
                    Copyright (c) 2002 Seagate
                    All rights reserved
  Unit 1   Disk     SEAGATE ST318453LC      00033JY08TGK
                    Copyright (c) 2002 Seagate
                    All rights reserved
  Unit 2   Disk     SEAGATE ST318453LC      00033JY08TGK
                    Copyright (c) 2002 Seagate
                    All rights reserved
  Unit 3   Disk     SEAGATE ST318453LC      00033JY08TGK
                    Copyright (c) 2002 Seagate
                    All rights reserved
  Unit 4   Disk     SEAGATE ST318453LC      00033JY08TGK
                    Copyright (c) 2002 Seagate
                    All rights reserved
  Unit 5   Disk     SEAGATE ST318453LC      00033JY08TGK
                    Copyright (c) 2002 Seagate
                    All rights reserved
  Unit 6   Disk     SEAGATE ST318453LC      00033JY08TGK
                    Copyright (c) 2002 Seagate
                    All rights reserved
  Unit 7   Disk     SEAGATE ST318453LC      00033JY08TGK
                    Copyright (c) 2002 Seagate
                    All rights reserved
Target 6
  Unit 0   Removable Read Only device     TOSHIBA
XM-4101TASUNSLCD342412/08/94

<#0> ok

 
 
 

Cannot make SS20 run with Seagate disk

Post by Volker Borche » Mon, 16 Feb 2004 19:47:17


|> What could be wrong? The only strange thing I could see was probe-scsi (see
|> below) which gave a strange response, showing the same for all Units in
|> Target 3. Any tips?

|> <#0> ok probe-scsi
|> Target 3
|>   Unit 0   Disk     SEAGATE ST318453LC      00033JY08TGK
|>                     Copyright (c) 2002 Seagate
|>                     All rights reserved
|>   Unit 1   Disk     SEAGATE ST318453LC      00033JY08TGK
|>                     Copyright (c) 2002 Seagate
|>                     All rights reserved
|>   Unit 2   Disk     SEAGATE ST318453LC      00033JY08TGK
|>                     Copyright (c) 2002 Seagate
|>                     All rights reserved
|>   Unit 3   Disk     SEAGATE ST318453LC      00033JY08TGK
|>                     Copyright (c) 2002 Seagate
|>                     All rights reserved
|>   Unit 4   Disk     SEAGATE ST318453LC      00033JY08TGK
|>                     Copyright (c) 2002 Seagate
|>                     All rights reserved
|>   Unit 5   Disk     SEAGATE ST318453LC      00033JY08TGK
|>                     Copyright (c) 2002 Seagate
|>                     All rights reserved
|>   Unit 6   Disk     SEAGATE ST318453LC      00033JY08TGK
|>                     Copyright (c) 2002 Seagate
|>                     All rights reserved
|>   Unit 7   Disk     SEAGATE ST318453LC      00033JY08TGK
|>                     Copyright (c) 2002 Seagate
|>                     All rights reserved

I have an ST318417N inside a Sparc-LX that works perfectly.
It shows the same behavior, so I'd think it is OK for recent Seagate.

--




 
 
 

Cannot make SS20 run with Seagate disk

Post by Michael Laajane » Tue, 17 Feb 2004 09:25:02


HI,

> I have an SS20 which needed more disk space. I tried to install a Maxtor
> Atlas 10K 36GB, Jumpstarted Solaris 8 02/02 onto it and all worked fine.
> Then I tried the same with a Seagate ST318453LC (ie I used the same machine,
> I only replaced the disk). The Jumpstart went fine as always, but on the
> reboot at the end, the system went into perpetual panic (see below).

> What could be wrong? The only strange thing I could see was probe-scsi (see
> below) which gave a strange response, showing the same for all Units in
> Target 3. Any tips?

Could it be that the upper byte on the SCSI bus(disk) is not terminated
properly on the Seagate, this because SS20 does only have 8 bit SCSI and
what will happend with the upper 8 bits on the SS20 I don't know!

Check Maxtor and Seagates website!

/michael

 
 
 

Cannot make SS20 run with Seagate disk

Post by Casper H.S. Di » Tue, 17 Feb 2004 20:40:32



>I have an SS20 which needed more disk space. I tried to install a Maxtor
>Atlas 10K 36GB, Jumpstarted Solaris 8 02/02 onto it and all worked fine.
>Then I tried the same with a Seagate ST318453LC (ie I used the same machine,
>I only replaced the disk). The Jumpstart went fine as always, but on the
>reboot at the end, the system went into perpetual panic (see below).
>What could be wrong? The only strange thing I could see was probe-scsi (see
>below) which gave a strange response, showing the same for all Units in
>Target 3. Any tips?

Is your "/" (root) partition completly within the first 2GB of the disk?

Casper
--
Expressed in this posting are my opinions.  They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

 
 
 

Cannot make SS20 run with Seagate disk

Post by Erlend Legange » Wed, 18 Feb 2004 05:25:15





> >I have an SS20 which needed more disk space. I tried to install a Maxtor
> >Atlas 10K 36GB, Jumpstarted Solaris 8 02/02 onto it and all worked fine.
> >Then I tried the same with a Seagate ST318453LC (ie I used the same
machine,
> >I only replaced the disk). The Jumpstart went fine as always, but on the
> >reboot at the end, the system went into perpetual panic (see below).

> >What could be wrong? The only strange thing I could see was probe-scsi
(see
> >below) which gave a strange response, showing the same for all Units in
> >Target 3. Any tips?

> Is your "/" (root) partition completly within the first 2GB of the disk?

No, I went for a 4GB root partition in both cases. Is this significant?
Anyway, I will try again tomorrow with a 2000MB root partition and report
back here with the result.

- Erlend Leganger

No, I went for a 4GB root partition in both cases. I will try again tomorrow
with a 2000MB root partition and report the result back here.

- Erlend Legnager

 
 
 

Cannot make SS20 run with Seagate disk

Post by Michael Laajane » Wed, 18 Feb 2004 05:28:14


HI,





<snip>

Quote:> No, I went for a 4GB root partition in both cases. Is this significant?
> Anyway, I will try again tomorrow with a 2000MB root partition and report
> back here with the result.

> - Erlend Leganger

> No, I went for a 4GB root partition in both cases. I will try again tomorrow
> with a 2000MB root partition and report the result back here.

!!, if you have 4GB it should not work with any disk, or??

/michael

 
 
 

Cannot make SS20 run with Seagate disk

Post by Rich Tee » Wed, 18 Feb 2004 05:43:43



> No, I went for a 4GB root partition in both cases. Is this significant?

Yes.  All machines prior to the Ultras require the whole of
the root slice to be within the first 2 GB of the disk.

Quote:> Anyway, I will try again tomorrow with a 2000MB root partition and report
> back here with the result.

That should work, provided it starts at (or near) cylinder 0.

HTH,

--
Rich Teer, SCNA, SCSA

President,
Rite Online Inc.

Voice: +1 (250) 979-1638
URL: http://www.rite-online.net

 
 
 

Cannot make SS20 run with Seagate disk

Post by Volker Borche » Wed, 18 Feb 2004 06:49:01


|>> No, I went for a 4GB root partition in both cases. Is this significant?
|>> Anyway, I will try again tomorrow with a 2000MB root partition and report
|>> back here with the result.

|> !!, if you have 4GB it should not work with any disk, or??

If you're lucky, the criticial files (/boot, /kernel/genunix, ...) are
within the first 2 GB even if / is larger. Once the kernel takes over,
the 2 GB limit no longer applies.

--



 
 
 

Cannot make SS20 run with Seagate disk

Post by Erlend Legange » Thu, 19 Feb 2004 07:32:53



Quote:> > No, I went for a 4GB root partition in both cases. Is this significant?

> Yes.  All machines prior to the Ultras require the whole of
> the root slice to be within the first 2 GB of the disk.

> > Anyway, I will try again tomorrow with a 2000MB root partition and
report
> > back here with the result.

> That should work, provided it starts at (or near) cylinder 0.

And you guys were right again, of course. A 2000MB root partition did the
trick, now the machine boots without a problem. I guess I was just lucky
with the Maxtor disk and its 4GB root partition, that all the critical files
were within the first 2GB, as Michael wrote about.

Thanks again.

- Erlend Leganger