Mailinglist Archive: opensuse (2912 mails)

< Previous Next >
Re: 9.2 scsi install: no fstab found
  • From: Jim Osborn <jimo@xxxxxxxxxx>
  • Date: Sat, 5 Feb 2005 22:09:30 -0800
  • Message-id: <20050206060930.GA1820@xxxxxxxxxx>
On Sat, Feb 05, 2005 at 11:33:43AM -0500, Carl E. Hartung wrote:
> For some reason, your system is booting from one of the floppy
> images it found on the CD. This is ok -- that's why they're there
> -- but to proceed successfully you'll need to create and use the
> modules diskette's, too.

I created a diskette for Modules5, which has the sym53c8xx module,
and selected Manual Installation, then told linuxrc to load that
module. I was offered the opportunity to enter parameters for
"scsi_transport_spi" as well as "sym53c8xx" but since I've never
given any parameters to my boot process, I don't know what might
be useful.

Apparently the kernel is still not making contact with the SCSI
subsystem; no sda or sdb shows up in /proc/mounts, the installation
target still fails with "no fstab found," and the kernel messages
show SCSI errors. I copied by hand this much from VC #4:

Attached scsi generic sg1 at scsi0, channel 0, id 15, lun 0, type 0
sym0: scsi parity error detected: SCR1=132 DBC=50000000 SBCL=0
sym0:15: ERROR (81:0) (8-0-0) (1f/9f/0) @ (scripta 50:f31c0004).
sym0: script cmd = 90080000
sym0: regdump: da 00 00 9f 47 ... ff ff ff
sym0: SCSI BUS reset detected
sym0: SCSI BUS has been reset

Here's what the current SuSE 7.3/kernel 2.4.23 boot.msg shows:

<6>sym53c8xx: at PCI bus 0, device 13, function 0
<4>sym53c8xx: setting PCI_COMMAND_PARITY...(fix-up)
<6>sym53c8xx: 53c895 detected with Symbios NVRAM
<6>sym53c895-0: rev 0x1 on pci bus 0 device 13 function 0 irq 11
<6>sym53c895-0: Symbios format NVRAM, ID 7, Fast-40, Parity Checking
<6>sym53c895-0: on-chip RAM at 0xf4201000
<6>sym53c895-0: restart (scsi reset).
<4>sym53c895-0: Downloading SCSI SCRIPTS.
<6>scsi0 : sym53c8xx-1.7.3c-20010512
<4> Vendor: QUANTUM Model: QM39100TD-SW Rev: N1B0
<4> Type: Direct-Access ANSI SCSI revision: 02
<4> Vendor: IBM Model: IC35L018UCPR15-0 Rev: S80D
<4> Type: Direct-Access ANSI SCSI revision: 03
<6>sym53c895-0-<0,0>: tagged command queue depth set to 4
<6>sym53c895-0-<15,0>: tagged command queue depth set to 4
<4>Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
<4>Attached scsi disk sdb at scsi0, channel 0, id 15, lun 0
<6>sym53c895-0-<0,*>: FAST-40 WIDE SCSI 80.0 MB/s (25.0 ns, offset 31)
<4>SCSI device sda: 17783249 512-byte hdwr sectors (9105 MB)
<6>Partition check:
<6> sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >
<6>sym53c895-0-<15,*>: FAST-40 WIDE SCSI 80.0 MB/s (25.0 ns, offset 31)
<4>SCSI device sdb: 35592156 512-byte hdwr sectors (18223 MB)
<6> sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 >

I assume the fact that 9.2 says "sym0" instead of "sym53c895-0"
and "scsi generic sg1 at scsi0" instead of "scsi disk sda at scsi0"
is a sign of something really wrong, but I have no idea what to
do to try to fix it. Does anything in the 7.3 boot.msg give a hint?

The sym53c8xx module appeared in the list linuxrc offered me, and
when I asked linuxrc to "show loaded modules," there it was.

Fwiw, my /etc/fstab is actually a symlink to /etc/fstab.3, as a
result of the multi-step process involved in adding sdb a while back.
If you think Yast could be choking on that symlink, I could
restructure it, but given the driver errors, I suspect my problem is
not the symlink.

I'd really appreciate any suggestions...


< Previous Next >
Follow Ups