Re: 2.2.1 boot problem - missing scsi disk
More details - it does the same thing in version 2.2.5. It does not
affect the problem to remove the target 4 disk, or to change the SCSI
id of the target 3 disk. Thus it seems to be connected physically to
a particular disk. Both disks are the same model of Seagate disk
(this is from the 2.0.35 boot):
scsi : 1 host.
Vendor: SEAGATE Model: ST52160N Rev: 0418
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 3, lun 0
Vendor: SEAGATE Model: ST52160N Rev: 0344
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdb at scsi0, channel 0, id 4, lun 0
The only difference is that the first disk was formated with
"sformat" version 3.4, the second was not.
>
> I have a system with a Cycle 5 board (Sparc 5 clone) that has two SCSI disks -
> targets 3 & 4 with slink installed on both disks. When I boot kernel 2.0.35,
> all works fine. But when I install the 2.2.1 kernel on my main disk (target 3)
> and then boot, the boot goes fine until where it is scanning the SCSI bus for
> disks - and all it sees is target 4, which it then treats as /dev/sda and the
> boot sequence fails. When I go back to 2.0.35, all is fine (target 3 is sda,
> target 4 is sdb).
>
> Is this a known problem that is fixed in a later version of the 2.2 kernel?
>
--
Dr. Harry Edmon E-MAIL: harry@atmos.washington.edu
(206) 543-0547 FAX: (206) 543-0308
Dept of Atmospheric Sciences
University of Washington, Box 351640, Seattle, WA 98195-1640
Reply to: