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

Bug#441497: marked as done (linux-image-2.6.18-5-686: Detects raid controller in reverse order)

Your message dated Wed, 30 Jan 2008 19:27:15 +0100
with message-id <20080130182715.GL12407@stro.at>
and subject line linux-image-2.6.18-5-686: Detects raid controller in reverse order
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: linux-image-2.6.18-5-686
Version: 2.6.18.dfsg.1-13etch1
Severity: important

After upgrading from 2.6.18-4-686 to 2.6.18-5-686 the 2 3ware raid controllers in my system are detected in reverse order.

With 2.6.18-4 the 3ware 7506-4LP (3w_xxxx.ko) is the first controller and the 9500S-12 (3w_9xxx.ko) the second. After upgrading the 9500S-12 is the first controller and the 7506-4LP the second controller. This breaks my system because drives get mounted on the wrong mountpoints.

On systems with two identical raid controllers this doesn't happen. I suspect the modules get loaded in reverse order somehow.


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

--- End Message ---
--- Begin Message --- 
kernel *never* guaranted device ordering,
thus get over it and use UUID in fstab and grub menu.lst config.

stable device names are a userspace question not a kernel bug,
closing

-- 
maks

--- End Message ---
Reply to: