[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#586029: marked as done (udev: 3ware 8006 RAID controller gets a new controller ID on each reboot)

Your message dated Thu, 17 Jun 2010 01:31:15 +0100
with message-id <1276734675.14011.683.camel@localhost>
and subject line Re: udev: 3ware 8006 RAID controller gets a new controller ID on each reboot
has caused the Debian Bug report #586029,
regarding udev: 3ware 8006 RAID controller gets a new controller ID on each reboot
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
586029: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586029
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: udev
Version: 157-1
Severity: important

Hello,

I have got a 8006-2LP RAID controller, which is mounted to /home (so not root).

In the past the controller worked on a stable server system (Debian etch 4.0 AND
Debian lenny 5.0) without any problems.

Now I have installed this controller on my desktop (debian sid) and on each reboot
I have got another controller name, like c0, c1, c2, etc...

exez:~# tw_cli info

Ctl   Model        (V)Ports  Drives   Units   NotOpt  RRate   VRate  BBU
------------------------------------------------------------------------
c2    8006-2LP     2         2        1       0       2       -      -


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.34-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages udev depends on:
ii  debconf [debconf-2.0]        1.5.32      Debian configuration management sy
ii  libc6                        2.11.2-1    Embedded GNU C Library: Shared lib
ii  libselinux1                  2.0.94-1    SELinux runtime shared libraries
ii  libusb-0.1-4                 2:0.1.12-15 userspace USB programming library
ii  lsb-base                     3.2-23.1    Linux Standard Base 3.2 init scrip
ii  util-linux                   2.17.2-3    Miscellaneous system utilities

Versions of packages udev recommends:
ii  pciutils                      1:3.1.7-3  Linux PCI Utilities
ii  usbutils                      0.87-3     Linux USB utilities

udev suggests no packages.

-- debconf information:
  udev/new_kernel_needed: false
  udev/title/upgrade:
  udev/reboot_needed:

--- End Message ---
--- Begin Message --- 
On Tue, 2010-06-15 at 22:39 +0200, Patrick Matthäi wrote:
> Package: udev
> Version: 157-1
> Severity: important
> 
> Hello,
> 
> I have got a 8006-2LP RAID controller, which is mounted to /home (so not root).
> 
> In the past the controller worked on a stable server system (Debian etch 4.0 AND
> Debian lenny 5.0) without any problems.
> 
> Now I have installed this controller on my desktop (debian sid) and on each reboot
> I have got another controller name, like c0, c1, c2, etc...
> 
> exez:~# tw_cli info
> 
> Ctl   Model        (V)Ports  Drives   Units   NotOpt  RRate   VRate  BBU
> ------------------------------------------------------------------------
> c2    8006-2LP     2         2        1       0       2       -      -
[...]

It looks like this number corresponds to the kernel's controller
numbering, since you later wrote:

> exez:~# dmesg|grep 3ware
> [    0.637640] 3ware Storage Controller device driver for Linux 
> v1.26.02.002.
> [    7.076015] scsi2 : 3ware Storage Controller
> [    7.076071] 3w-xxxx: scsi2: Found a 3ware Storage Controller at 
> 0xdc00, IRQ: 19.
> [    7.076797] scsi 2:0:0:0: Direct-Access     3ware    Logical Disk 0 
>  1.2  PQ: 0 ANSI: 0

You should also see scsi0 and scsi1 in the kernel log, which are
probably ATA controllers or USB storage devices.

The enumeration order of SCSI controllers is *not* stable.  This is
*not* a bug in the kernel.  If tw_cli assumes that, it is a bug in
tw_cli.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: