Arch Linux

olsman037

Member

Registered: 2011-06-17

Posts: 27

bad LUN and bad target number startup problem

Hello

Since few time, when my laptop boots I have some strange lines just after uevent :

bad LUN
bad target number (1:0)
....
bad target number (7:0)

They are in the everything.log and dmesg. Here you have the relevant part of the dmesg output, lspci and lsusb (it seems to be related with some SCSI removable disk...):

[   16.185536] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[   16.369346] scsi 6:0:0:0: Direct-Access     Generic- SD/MMC           1.00 PQ: 0 ANSI: 0 CCS
[   16.369521] sd 6:0:0:0: Attached scsi generic sg2 type 0
[   16.369638] scsi 6:0:0:1: Direct-Access     Generic- MemoryStick      1.00 PQ: 0 ANSI: 0 CCS
[   16.369648] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[   16.369757] sd 6:0:0:1: Attached scsi generic sg3 type 0
[   16.369825] Bad LUN (0:2)
[   16.369873] sd 6:0:0:1: [sdc] Attached SCSI removable disk
[   16.392657] Bad target number (1:0)
[   16.405941] Bad target number (2:0)
[   16.419294] Bad target number (3:0)
[   16.469295] Bad target number (4:0)
[   16.522611] Bad target number (5:0)
[   16.575913] Bad target number (6:0)
[   16.629228] Bad target number (7:0)

lspci :

00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation 2nd Generation Core Processor Family PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB Controller: Intel Corporation 6 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 6 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 1 (rev b4)
00:1c.1 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 2 (rev b4)
00:1c.2 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 3 (rev b4)
00:1c.3 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 4 (rev b4)
00:1d.0 USB Controller: Intel Corporation 6 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 6 Series Chipset Family 6 port SATA AHCI Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 6 Series Chipset Family SMBus Controller (rev 04)
01:00.0 VGA compatible controller: ATI Technologies Inc NI Seymour [AMD Radeon HD 6470M] (rev ff)
02:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5209 (rev 01)
04:00.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)

lsusb

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 0c45:64b5 Microdia 
Bus 002 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 002 Device 004: ID 0b38:0010 Gear Head 107-Key Keyboard

I can boot, but something seems to be broken or at least not very clean (and it seems that my boot is a bit longer). Is there a way to reset/reconfigure target numbers ? (no idea of what is that... I googled without success).

All my usb seem to work with keyboard, mouse and usb key... as the SD card reader. I also have something called HG duo (sony vaio laptop) but I don't have this kind of card so I can't test it.

The problem occured with the kernel26_mainline (3.0), but also with 2.6.39 and now with linux3.0 in core...

Does anybody has an idea on what's going on ? (and how to fix it...)

Merci!!

3Dman

Member

Registered: 2011-06-14

Posts: 13

Re: bad LUN and bad target number startup problem

I have the same problem also...

alphaniner

Member

From: Ancapistan

Registered: 2010-07-12

Posts: 2,810

Re: bad LUN and bad target number startup problem

LUN stands for Logical Unit Number.  In dmesg lines like

sd 6:0:0:0 ...

the first number is Host, the second number is Channel, the third number is ID (aka Target), and the fourth number is LUN.

AFAIK LUN is only used in SCSI protocol.  For example, in my box with two SATA drives attached to onboard SATA ports, the drives show up as 0:0:0:0 and 1:0:0:0.  My IDE CD-ROM shows up as 2:0:1:0 (the Target # is 1 because it's slave). So I find it odd that you are seeing 6:0:0:0 and 6:0:0:1.  I think it's likely that you've got some bad (or badly acting) hardware.

For starters a 'plain-language' description of the storage devices attached to your machine (type and connection) would be helpful.

In addition, post the output of fdisk -l and cat /proc/scsi/scsi and the contents of /etc/fstab.

Last edited by alphaniner (2011-08-10 16:59:00)

---

But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner

olsman037

Member

Registered: 2011-06-17

Posts: 27

Re: bad LUN and bad target number startup problem

Thank you for these informations..

My laptop is a Sony Vaio VPC-SB1C5E with intel i7-2620M, 8Go RAM, GPU AMD 6470M.

My storages are (according to gnome disk utility, I hope it helps...) :

SATA 6 series chipset family 6 port AHCI controller
      hard drive 500G ATA toshiba MK5061GSY
      optical drive optiarc DVD RW AD-7930V

peripheral
       Generic SD - MMC
       Generic Memory stick

fdisk -l : no output

cat /proc/scsi/scsi

Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: TOSHIBA MK5061GS Rev: MC00
  Type:   Direct-Access                    ANSI  SCSI revision: 05
Host: scsi4 Channel: 00 Id: 00 Lun: 00
  Vendor: Optiarc  Model: DVD RW AD-7930V  Rev: 1.70
  Type:   CD-ROM                           ANSI  SCSI revision: 05
Host: scsi6 Channel: 00 Id: 00 Lun: 00
  Vendor: Generic- Model: SD/MMC           Rev: 1.00
  Type:   Direct-Access                    ANSI  SCSI revision: 02
Host: scsi6 Channel: 00 Id: 00 Lun: 01
  Vendor: Generic- Model: MemoryStick      Rev: 1.00
  Type:   Direct-Access                    ANSI  SCSI revision: 02

/etc/fstab

# /etc/fstab: static file system information
#
# <file system>        <dir>         <type>    <options>          <dump> <pass>
devpts                 /dev/pts      devpts    defaults            0      0
shm                    /dev/shm      tmpfs     nodev,nosuid        0      0
debugfs            /sys/kernel/debug debugfs                      0      0
# DEVICE DETAILS: /dev/sda10 UUID=b1c83852-9009-43aa-a079-14b56c0f8e13 LABEL=ar$
# DEVICE DETAILS: /dev/sda5 UUID=3bb61900-3bc8-4340-99eb-b8608493f47b LABEL=
# DEVICE DETAILS: /dev/sda8 UUID=a7ca72d5-f5a9-4a69-9157-a356b8b4956f LABEL=arc$
# DEVICE DETAILS: /dev/sda9 UUID=80e4178f-2768-4174-99f0-8de49e34b350 LABEL=arc$
UUID=3bb61900-3bc8-4340-99eb-b8608493f47b swap swap defaults 0 0
UUID=80e4178f-2768-4174-99f0-8de49e34b350 /home ext4 defaults 0 1
UUID=a7ca72d5-f5a9-4a69-9157-a356b8b4956f /boot ext2 defaults 0 1
UUID=b1c83852-9009-43aa-a079-14b56c0f8e13 / ext4 defaults 0 1

alphaniner

Member

From: Ancapistan

Registered: 2010-07-12

Posts: 2,810

Re: bad LUN and bad target number startup problem

The problem is related to the 'Generic SD - MMC' and/or 'Generic Memory stick'. At first I thought they might be one device acting strangely, but now that doesn't seem to be the case.  The best I can suggest is to try with just one of them connected, and see if the errors persist.  When you're up, run cat /proc/scsi/scsi again, and fdisk -l, this time as root or using sudo.  Then do the same with the other device.

---

But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner

olsman037

Member

Registered: 2011-06-17

Posts: 27

Re: bad LUN and bad target number startup problem

The best I can suggest is to try with just one of them connected, and see if the errors persist.

My laptop only has few weeks.... If it is possible to not destroy it.... (I'm not very comfortable with the hardware part, and I think that I will lost the warranty if I open this part).
But I found an option in the bios to disable the memory card reader (both I guess... or maybe there are 2 slots but only one thing to plug), and the bad target number message disappear.

With memory cards disabled :

fdisk -l

Périphérique Amorce  Début        Fin      Blocs     Id  Système
/dev/sda1            2048    25927679    12962816   27  TFS WinRE masquée
/dev/sda2   *    25927680    26132479      102400    7  HPFS/NTFS/exFAT
/dev/sda3        26132480   226701359   100284440    7  HPFS/NTFS/exFAT
/dev/sda4       226705406   976771071   375032833    5  Étendue
/dev/sda5       960688128   976771071     8041472   82  partition d'échange Linux / Solaris
/dev/sda6       960163840   960686079      261120   83  Linux
/dev/sda7       226705408   929204223   351249408   83  Linux
/dev/sda8       929206272   960161791    15477760   83  Linux

cat /proc/scsi/scsi

Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: TOSHIBA MK5061GS Rev: MC00
  Type:   Direct-Access                    ANSI  SCSI revision: 05
Host: scsi4 Channel: 00 Id: 00 Lun: 00
  Vendor: Optiarc  Model: DVD RW AD-7930V  Rev: 1.70
  Type:   CD-ROM                           ANSI  SCSI revision: 05

With memory card enabled (but I don't have any sd card right now to give you the output with one plugged) :
fdisk -l

Périphérique Amorce  Début        Fin      Blocs     Id  Système
/dev/sda1            2048    25927679    12962816   27  TFS WinRE masquée
/dev/sda2   *    25927680    26132479      102400    7  HPFS/NTFS/exFAT
/dev/sda3        26132480   226701359   100284440    7  HPFS/NTFS/exFAT
/dev/sda4       226705406   976771071   375032833    5  Étendue
/dev/sda5       960688128   976771071     8041472   82  partition d'échange Linux / Solaris
/dev/sda6       960163840   960686079      261120   83  Linux
/dev/sda7       226705408   929204223   351249408   83  Linux
/dev/sda8       929206272   960161791    15477760   83  Linux

cat /proc/scsi/scsi

Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: TOSHIBA MK5061GS Rev: MC00
  Type:   Direct-Access                    ANSI  SCSI revision: 05
Host: scsi4 Channel: 00 Id: 00 Lun: 00
  Vendor: Optiarc  Model: DVD RW AD-7930V  Rev: 1.70
  Type:   CD-ROM                           ANSI  SCSI revision: 05
Host: scsi6 Channel: 00 Id: 00 Lun: 00
  Vendor: Generic- Model: SD/MMC           Rev: 1.00
  Type:   Direct-Access                    ANSI  SCSI revision: 02
Host: scsi6 Channel: 00 Id: 00 Lun: 01
  Vendor: Generic- Model: MemoryStick      Rev: 1.00
  Type:   Direct-Access                    ANSI  SCSI revision: 02

Any idea ? I will try to boot on windows to see if there is any problem...

[edit]: no problem with windows : no strange messages, no strange icon in device manager.. It may be a software problem and not a hardware one ?

Last edited by olsman037 (2011-08-12 08:00:04)

danielstrong52

Member

Registered: 2010-08-12

Posts: 6

Re: bad LUN and bad target number startup problem

I also have a very similar problem to olsman037, and I can confirm that it seems to be a problem with the SD card reader: my /proc/scsi/scsi:

Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: TOSHIBA MK7575GS Rev: GT00
  Type:   Direct-Access                    ANSI  SCSI revision: 05
Host: scsi5 Channel: 00 Id: 00 Lun: 00
  Vendor: hp       Model: DVD A  DS8A5LH   Rev: 1H68
  Type:   CD-ROM                           ANSI  SCSI revision: 05
Host: scsi6 Channel: 00 Id: 00 Lun: 00
  Vendor: Generic- Model: xD/SD/M.S.       Rev: 1.00
  Type:   Direct-Access                    ANSI  SCSI revision: 02

and the relevant portion of dmesg:

[    5.681887] sd 6:0:0:0: Attached scsi generic sg2 type 0
[    5.681996] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[    5.682017] Bad LUN (0:1)
[    5.701535] Bad target number (1:0)
[    5.711514] Bad target number (2:0)
[    5.724863] Bad target number (3:0)
[    5.778133] Bad target number (4:0)
[    5.831471] Bad target number (5:0)
[    5.851481] Bad target number (6:0)
[    5.928092] Bad target number (7:0)

I have no prior experience of SD card readers under linux, but it seems quite odd that it thinks it's "removable disk" sdb, doesn't it?
Also, it seems that lscpi fails to recognise the device, returning it as

13:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5209 (rev 01)

again very similar to olsman037's lspci

It would be great if someone who understands to some extent the problem could help on this one. Is it a bug? Should it be reported?

---

"A knowledge of the existence of something we cannot penetrate, of the manifestations of the profoundest reason and the most radiant beauty, which are only accessible to our reason in their most elementary forms—it is this knowledge and this emotion that constitute the truly religious attitude; in this sense, and in this alone, I am a deeply religious man."
-- Albert Einstein

r0b0t

Member

From: /tmp

Registered: 2009-05-24

Posts: 505

Re: bad LUN and bad target number startup problem

[    6.150737] scsi 6:0:0:0: Direct-Access     Generic- xD/SD/M.S.       1.00 PQ: 0 ANSI: 0 CCS
[    6.151010] Bad LUN (0:1)
[    6.151041] scsi: killing requests for dead queue
[    6.151075] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[    6.151088] Bad target number (1:0)
[    6.151157] scsi: killing requests for dead queue
[    6.151212] Bad target number (2:0)
[    6.151249] scsi: killing requests for dead queue
[    6.151292] Bad target number (3:0)
[    6.151317] scsi: killing requests for dead queue
[    6.151360] Bad target number (4:0)
[    6.151398] scsi: killing requests for dead queue
[    6.151439] Bad target number (5:0)
[    6.151466] scsi: killing requests for dead queue
[    6.151502] Bad target number (6:0)
[    6.151525] scsi: killing requests for dead queue
[    6.151563] Bad target number (7:0)
[    6.151587] scsi: killing requests for dead queue
[    6.151600] rts_pstor: device scan complete
[    6.723449] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'

Same here, any idea?

karlyzo

Member

From: Germany

Registered: 2009-01-24

Posts: 7

Re: bad LUN and bad target number startup problem

Same here on Lenovo x121e

jason_ca

Member

Registered: 2011-12-09

Posts: 3

Re: bad LUN and bad target number startup problem

Same here on Lenovo x121e

Same here.

Cows

Member

From: Brooklyn, NY

Registered: 2007-05-20

Posts: 101

Re: bad LUN and bad target number startup problem

I also have the same problem on my Dell XPS 14z.

http://paste.pocoo.org/show/539057/

christopher72

Member

Registered: 2010-09-07

Posts: 24

Re: bad LUN and bad target number startup problem

Filed a bug in Kernel Bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=42640

Btw, blacklisting the rts_pstor kernel module gets rid of the errors but also disables the card reader of course. Might be a workaround for those who don't use the reader anyway.

Triston J. Taylor

Banned

Registered: 2011-10-20

Posts: 41

Re: bad LUN and bad target number startup problem

Well, since no one could 'fix' this, can anyone suggest a way to keep this error from posting to the terminal on boot? It looks critical and its quite tacky imho. Perhaps we can simply report [in red lettering] that no removable media is present instead of some random LUN message? I don't use the card reader but I plan to, and blacklisting the kmod seems like something I might forget!

If you know of a way to recompile kmods feel free to post link to the TUT! I really don't have time to wait for some kdev to get off his t-ass-k list to do something he should have done right the first time (in other words I'm not holding my breath for the second coming.)

---

systemd has its advantages; of these the most damaging are: corporatization, security bottlenecks, control obfuscation, and micro-managed forward compatibility pitfalls. Free Software meets Dictatorship. What a maroon.

christopher72

Member

Registered: 2010-09-07

Posts: 24

Re: bad LUN and bad target number startup problem

From the developer: "We will fix the issue to printing "bad lun" or "bad target number" during boot, in our next submission to the kernel staging tree.".

It is also possible to download the source code from the Realtek site, comment out the lines printing the 'bad lun' and 'bad target number' messages, and then compile the driver yourself.  The file with the source code is "rtsx.c".  Lines 530,531 en 536,537 in the version I downloaded.  Compilation instructions are in the README after extracting the driver.

Last edited by christopher72 (2012-03-23 19:32:49)