SCSI disk detection aborts randomly

Subject: SCSI disk detection aborts randomly
From: Richard Blocker (r-blocker@uchicago.edu)
Date: Mon Oct 18 1999 - 08:06:46 MDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
• Next message: Graham Leggett: "v2.2.12 and a bronze Powerbook G3"
• Previous message: Dennis Murphy: "Re: Can You Prevent Some Users From Telneting to their Accounts?"

I'm having a problem with random scsi disk detection failures. I have CS
1.1 inbstalled on a PowerMac 7600 with two internal 1.2GB SCSI HDs. The
first HD (SCSI ID 0) is HFS with MacOS 8.6 installed. The second HD (SCSI
ID 1) has Yellowdog CS 1.1.

During installation, I noticed that the installer was identifying the only
Linux HD listed as sda (not sdb as I expected -- i'd previoulsy had
LinuxPPC on this disk, so it was already formated for linux). This caused
me some concern about using fdisk to format the disk. I bailed out of the
installation, but after I'd finally determined that it actually was the
disk I wanted, I went ahead.

After installation, the machine booted fine, but the following showed up in
the boot diagnostics:

        scsi0: MESH
        scsi1: S3C94
        scsi: 2 hosts
        mesh: target 0 aborted
        mesh: target 1 synchronous at 10. MB/s
                vendor: Quantum Model: FIREBALL_TM1280s Revision:300z

As you can see, target 0 (SCSI ID 0) is quietly being aborted, and target 1
is detected as the primary (sda) HD. When this happens, everything works
fine.

When it does not happen, as occurs randomly, the diagnostics show this:

        scsi0: MESH
        scsi1: S3C94
        scsi: 2 hosts
        mesh: target 0 synchronous at 10.0 MB/s
                vendor: Quantum Model: FIREBALL1280s Revision: 630g
        [.....]
        mesh: target 1 synchronous at 10.0 MB/s
                vendor: Quantum Model: FIREBALL_TM1280s Revision:300z
        [.....]
        Kernel Panic: VFS Unable to mount root fs on 08:05

Here, the first disk (SCSI ID 0) is not being aborted. It is being detected
as primary (sda), which then causes a kernel panic because there's no linux
installed there.

I have no idea why target 0 gets aborted most of the time. As I said, I
had LinuxPPC installed on this second disk originally (with the same MacOS
on the first disk), and there were no problems like this. Can anyone help
identify the cause of this problem? Could it be a bug in BootX (v. 1.1.3)
is what I'm using)?

Thanks for any help.

Rick

• Next message: Graham Leggett: "v2.2.12 and a bronze Powerbook G3"
• Previous message: Dennis Murphy: "Re: Can You Prevent Some Users From Telneting to their Accounts?"

This archive was generated by hypermail 2a24 : Tue Nov 02 1999 - 16:20:58 MST