Bug#412837: marked as done (jumbles scsi devices on sun x4100)
Your message dated Mon, 5 Mar 2007 18:57:26 -0700
with message-id <[🔎] 20070306015726.GR17252@krebs.dannf>
and subject line use udev aliases
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 ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: jumbles scsi devices on sun x4100
- From: Sebastian Langenhorst <schlupp-debbug@balda7-3.de>
- Date: Wed, 28 Feb 2007 14:47:04 +0100
- Message-id: <20070228134704.17560.93752.reportbug@cannibalon.uni-paderborn.de>
Package: linux-image-2.6.18-4-686-bigmem
Version: 2.6.18.dfsg.1-11
Severity: critical
The X4100 comes with an AMI Bios which brings virtual usb floppy and virtual usb cdrom devices.
>From kernel 2.6.18-4 on theses devices are sometimes recongnized before the raid controller
is and scatter the sd names resulting in an non-booting machine.
So the bootdevice is now most times sdj but sometimes sdb.
In 2.6.18-3 the problem never occured and sdb was the bootdevice.
Below theres a extract from dmesg:
scsi1 : SCSI emulation for USB Mass Storage devices
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
Vendor: <5> Vendor: AMI Model: Virtual Floppy Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 00
Vendor: AMI Model: Virtual Floppy Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 00
Vendor: AMI Model: Virtual Floppy Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 00
Vendor: AMI Model: Virtual Floppy Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 00
Vendor: AMI Model: Virtual Floppy Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 00
Vendor: AMI Model: Virtual Floppy Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 00
Vendor: AMI Model: Virtual Floppy Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 00
Vendor: AMI Model: Virtual Floppy Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 00
usb-storage: device scan complete
AMI Model: Virtual CDROM Rev: 1.00
Type: CD-ROM ANSI SCSI revision: 00
usb-storage: device scan complete
scsi2 : ioc0: LSISAS1064, FwRev=010a0000h, Ports=1, MaxQ=511, IRQ=209
Vendor: SEAGATE Model: ST973401LSUN72G Rev: 0556
Type: Direct-Access ANSI SCSI revision: 03
Vendor: SEAGATE Model: ST973401LSUN72G Rev: 0556
Type: Direct-Access ANSI SCSI revision: 03
Vendor: FUJITSU Model: MAY2036RCSUN36G Rev: 0401
Type: Direct-Access ANSI SCSI revision: 04
Vendor: FUJITSU Model: MAY2036RCSUN36G Rev: 0401
Type: Direct-Access ANSI SCSI revision: 04
Vendor: LSILOGIC Model: Logical Volume Rev: 3000
Type: Direct-Access ANSI SCSI revision: 02
Vendor: LSILOGIC Model: Logical Volume Rev: 3000
Type: Direct-Access ANSI SCSI revision: 02
AMD8111: IDE controller at PCI slot 0000:00:07.1
AMD8111: chipset revision 3
AMD8111: not 100% native mode: will probe irqs later
AMD8111: 0000:00:07.1 (rev 03) UDMA133 controller
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:pio, hdb:pio
Probing IDE interface ide0...
sd 1:0:0:0: Attached scsi removable disk sda
sd 1:0:0:1: Attached scsi removable disk sdb
sd 1:0:0:2: Attached scsi removable disk sdc
sd 1:0:0:3: Attached scsi removable disk sdd
sd 1:0:0:4: Attached scsi removable disk sde
sd 1:0:0:5: Attached scsi removable disk sdf
sd 1:0:0:6: Attached scsi removable disk sdg
sd 1:0:0:7: Attached scsi removable disk sdh
SCSI device sdi: 70311936 512-byte hdwr sectors (36000 MB)
sdi: Write Protect is off
sdi: Mode Sense: 03 00 00 08
SCSI device sdi: drive cache: write through
SCSI device sdi: 70311936 512-byte hdwr sectors (36000 MB)
sdi: Write Protect is off
sdi: Mode Sense: 03 00 00 08
SCSI device sdi: drive cache: write through
sdi: sdi1
sd 2:1:2:0: Attached scsi disk sdi
SCSI device sdj: 142577664 512-byte hdwr sectors (73000 MB)
sdj: Write Protect is off
sdj: Mode Sense: 03 00 00 08
SCSI device sdj: drive cache: write through
SCSI device sdj: 142577664 512-byte hdwr sectors (73000 MB)
sdj: Write Protect is off
sdj: Mode Sense: 03 00 00 08
SCSI device sdj: drive cache: write through
sdj: sdj1 sdj2 sdj3 sdj4
sd 2:1:0:0: Attached scsi disk sdj
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686-bigmem
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages linux-image-2.6.18-4-686-bigmem depends on:
ii coreutils 5.97-5.3 The GNU core utilities
ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii initramfs-tools [linux-initra 0.85e tools for generating an initramfs
ii module-init-tools 3.3-pre4-1 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.18-4-686-bigmem recommends:
ii libc6-i686 2.3.6.ds1-11 GNU C Library: Shared libraries [i
-- debconf information excluded
--- End Message ---
--- Begin Message ---
hey Sebastian,
When you accessing devices using the /dev/sd* names, you are
counting on the same ordering each time. If you want to use a name
that won't change, try one of the aliases under /dev/disk. For
example, I use the following line in my /etc/fstab to mount my usb stick:
/dev/disk/by-id/usb-PNY_USB_2.0_FD_6E59150036E6 /media/usb vfat noauto,defaults 0 0
Linux does not guarantee ordering of /dev/sd* devices, so this is not
a kernel bug.
[1] and really cannot, since driver loading is a userspace thing
--
dann frazier | HP Open Source and Linux Organization
--- End Message ---
Reply to: