All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eddie <stunnel@attglobal.net>
To: linux-scsi@vger.kernel.org
Subject: LSI MegaRAID not recognised correctly in 64-bit.  2.6.29.6
Date: Wed, 16 Sep 2009 09:18:10 -0700	[thread overview]
Message-ID: <4AB10FC2.1080900@attglobal.net> (raw)

I've done a quick search of the archives, and didn't find anything 
relevant, or I missed it.  :(

I've just installed the latest Slackware release, 13.0, in 64-bit mode, 
that uses kernel 2.6.29.6.  Previously, I was running 12.2, in 32-bit, 
which used kernel 2.6.27.31.  After booting, I noticed that the drives 
on the raid had not been mounted.  Checking through dmesg, I noticed 
that the "drive" attached to the card had not been correctly 
recognised.  Here's the relevant messages, about the card, and the 
drive, from dmesg:

megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006)

megaraid: 2.20.5.1 (Release Date: Thu Nov 16 15:32:35 EST 2006)
megaraid: probe new device 0x101e:0x1960:0x101e:0x0511: bus 1:slot 4:func 0

megaraid 0000:01:04.0: PCI INT A -> Link[LNK1] -> GSI 19 (level, high) 
-> IRQ 19
megaraid: fw version:[N661] bios version:[1.01]
scsi4 : LSI Logic MegaRAID driver
scsi[4]: scanning scsi channel 0 [Phy 0] for non-raid devices

scsi[4]: scanning scsi channel 1 [Phy 1] for non-raid devices
scsi[4]: scanning scsi channel 2 [Phy 2] for non-raid devices
scsi[4]: scanning scsi channel 3 [Phy 3] for non-raid devices
scsi[4]: scanning scsi channel 4 [virtual] for logical drives
scsi scan: INQUIRY result too short (5), using 36
scsi 4:4:0:0: Direct-Access                                    PQ: 0 ANSI: 0
sd 4:4:0:0: [sda] Sector size 0 reported, assuming 512.
sd 4:4:0:0: [sda] 1 512-byte hardware sectors: (512 B/512 B)
sd 4:4:0:0: [sda] Write Protect is off
sd 4:4:0:0: [sda] Mode Sense: 00 00 00 00
sd 4:4:0:0: [sda] Asking for cache data failed
sd 4:4:0:0: [sda] Assuming drive cache: write through
sd 4:4:0:0: [sda] Sector size 0 reported, assuming 512.
sd 4:4:0:0: [sda] 1 512-byte hardware sectors: (512 B/512 B)
sd 4:4:0:0: [sda] Write Protect is off
sd 4:4:0:0: [sda] Mode Sense: 00 00 00 00
sd 4:4:0:0: [sda] Asking for cache data failed
sd 4:4:0:0: [sda] Assuming drive cache: write through
 sda: unknown partition table
sd 4:4:0:0: [sda] Attached SCSI disk
sd 4:4:0:0: Attached scsi generic sg1 type 0


Obviously, it's this "scsi scan: INQUIRY result too short (5), using 
36", causing the drive not to be correctly recognised.  Normally, I'd 
expect to get:

scsi 4:4:0:0: Direct-Access     MegaRAID LD 0 RAID5 1430G N661 PQ: 0 ANSI: 2
sd 4:4:0:0: [sda] 2930307072 512-byte hardware sectors (1500317 MB)

In order to eliminate either the change in kernel version, or the change 
in architecture, as the culprit, I booted the machine, from both the 
32-bit, and 64-bit, DVDs from Slack.  With the 32-bit kernel, the drive 
was correctly recognised, but not with the 64-bit.  So, it's definitely 
the change in architecture causing this, not the change in kernel version.

The full dmesg can be found here:  ftp.BogoLinux.net/pub together with 
the dmesg from the 32-bit system, with kernel 2.6.27.31.

Cheers,
Eddie

             reply	other threads:[~2009-09-16 16:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16 16:18 Eddie [this message]
2009-09-16 16:31 ` LSI MegaRAID not recognised correctly in 64-bit. 2.6.29.6 James Bottomley
2009-09-16 16:54   ` Eddie
2009-09-17  2:58     ` Eddie
2009-09-17  2:59     ` Eddie
2009-09-17 15:59       ` James Bottomley
2009-09-17 16:09         ` Eddie
2009-09-17 18:39           ` James Bottomley
2009-09-17 20:28             ` James Bottomley
2009-09-18 13:00               ` FUJITA Tomonori
2009-09-18 14:11                 ` Matthew Wilcox
2009-09-18 14:18                   ` FUJITA Tomonori
2009-09-19  7:03                     ` Eddie
2009-09-19  7:55                       ` FUJITA Tomonori
2009-09-19 15:24                         ` Eddie
2009-09-21 13:51                           ` FUJITA Tomonori
2009-09-21 15:34                             ` James Bottomley
2009-09-21 15:37                               ` Yang, Bo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AB10FC2.1080900@attglobal.net \
    --to=stunnel@attglobal.net \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.