The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: Peter Teoh <htmldeveloper@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: /dev/sdb not detected anymore?
Date: Sat, 03 Oct 2009 19:02:09 -0600	[thread overview]
Message-ID: <4AC7F411.1090305@gmail.com> (raw)
In-Reply-To: <804dabb00910020707r9820d8bpe371baf1efb67c1@mail.gmail.com>

On 10/02/2009 08:07 AM, Peter Teoh wrote:
> I just built my 2.6.32-rc2 (from linus-git) yesterday, and repeated
> today again, starting from "make mrproper", and consistently both
> version cannot detect my /dev/sdb, which is the second SATA harddisk.
>   The first SATA is detected as follows in dmesg:
>
>      742 [    4.595949] scsi 2:0:0:0: Direct-Access     ATA
> ST3500630AS      3.AA PQ: 0 ANSI: 5
>      743 [    4.596116] sd 2:0:0:0: [sda] 976773168 512-byte logical
> blocks: (500 GB/465 GiB)
>      744 [    4.596213] sd 2:0:0:0: [sda] Write Protect is off
>      745 [    4.596216] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
>      746 [    4.596258] sd 2:0:0:0: [sda] Write cache: enabled, read
> cache: enabled, doesn't support DPO or FUA
>      747 [    4.596467]  sda: sda1 sda2 sda3 sda4<  sda5 sda6 sda7 sda8 sda9>
>      748 [    4.674607] sd 2:0:0:0: [sda] Attached SCSI disk
>
> And from sg_inq:
>
> standard INQUIRY:
>    PQual=0  Device_type=0  RMB=0  version=0x05  [SPC-3]
>    [AERC=0]  [TrmTsk=0]  NormACA=0  HiSUP=0  Resp_data_format=2
>    SCCS=0  ACC=0  TPGS=0  3PC=0  Protect=0  BQue=0
>    EncServ=0  MultiP=0  [MChngr=0]  [ACKREQQ=0]  Addr16=0
>    [RelAdr=0]  WBus16=0  Sync=0  Linked=0  [TranDis=0]  CmdQue=0
>    [SPI: Clocking=0x0  QAS=0  IUS=0]
>      length=96 (0x60)   Peripheral device type: disk
>   Vendor identification: ATA
>   Product identification: ST3500630AS
>   Product revision level: 3.AA
>   Unit serial number:             9QG14T5Z
>
> But the second SATA (identical in type/model) is not detectable.
> Upon rebooting to my previous 2.6.31 kernel version, it became
> detected and usable - absolutely nothing else is touch.   So what is
> it in the latest kernel which is giving the problem?

We need more details, can you post the full boot log including the 
actual libata messages from the working and non-working kernels?

  reply	other threads:[~2009-10-04  1:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02 14:07 /dev/sdb not detected anymore? Peter Teoh
2009-10-04  1:02 ` Robert Hancock [this message]
2009-10-04  2:08   ` Peter Teoh
2009-10-05 14:49     ` Peter Teoh

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=4AC7F411.1090305@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=htmldeveloper@gmail.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox