public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jorge Almeida <jalmeida@math.ist.utl.pt>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] confused udev?
Date: Wed, 23 Nov 2005 09:32:59 +0000 (WET)	[thread overview]
Message-ID: <Pine.LNX.4.63.0511230913580.1896@weber.math.ist.utl.pt> (raw)
In-Reply-To: <7573e9640511222010t546b19e1y2040f2cfc455973d@mail.gmail.com>

On Tue, 22 Nov 2005, Richard Fish wrote:
> 
> Ok, do dmesg and /proc/partitions agree that there is a partition
> there?  If not, then the problem is that the kernel is not recognizing
No...
> your partition table.  I would suggest:
> 
> <insert the key>
> dd if=/dev/zero of=/dev/sda bs=512 count=1
> <remove then re-insert the key>
> fdisk /dev/sdb
> <create single partition, type 'b'>
> mkfs.vfat -n MYKEY -F 32 /dev/sda1
> 
Done it. All well, apparently. But then I remove the key and insert it
again. No joy. (See dmesg). I remove it and insert it again. It works,
this time. This is just totally unreliable. I guess I'll boot from
KNOPPIX, to see whether it may be a kernel problem...
 
(...)
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x2a R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
Attached scsi removable disk sda at scsi4, channel 0, id 0, lun 0
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (1:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (2:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (3:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (4:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (5:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (6:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (7:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: device scan complete
ieee1394: Current remote IRM is not 1394a-2000 compliant, resetting...
ieee1394: Error parsing configrom for node 0-00:1023
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
ieee1394: Node resumed: ID:BUS[0-00:1023]  GUID[0050770e00071002]
scsi5 : SCSI emulation for IEEE-1394 SBP-2 Devices
ieee1394: sbp2: Logged into SBP-2 device
ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048]
  Vendor: Maxtor 6  Model: L250R0            Rev:     
  Type:   Direct-Access-RBC                  ANSI SCSI revision: 04
SCSI device sdb: 490234752 512-byte hdwr sectors (251000 MB)
sdb: asking for cache data failed
sdb: assuming drive cache: write through
SCSI device sdb: 490234752 512-byte hdwr sectors (251000 MB)
sdb: asking for cache data failed
sdb: assuming drive cache: write through
 sdb: sdb1
Attached scsi disk sdb at scsi5, channel 0, id 0, lun 0
 
Jorge 
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-11-23  9:38 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-17  9:26 [gentoo-user] confused udev? Jorge Almeida
2005-11-17  9:49 ` Dirk Heinrichs
2005-11-17 12:43   ` Jorge Almeida
2005-11-17 13:54     ` Dirk Heinrichs
2005-11-17 14:14       ` Jorge Almeida
2005-11-18 10:21         ` Dirk Heinrichs
2005-11-18 10:29           ` Neil Bothwick
2005-11-18 10:40             ` Dirk Heinrichs
2005-11-18 10:31           ` Jorge Almeida
2005-11-20  2:21             ` Richard Fish
2005-11-20 11:21               ` Jorge Almeida
2005-11-21 15:18                 ` Richard Fish
2005-11-22 11:46                   ` Jorge Almeida
2005-11-23  4:10                     ` Richard Fish
2005-11-23  9:32                       ` Jorge Almeida [this message]
2005-11-23 15:07                         ` Richard Fish
2005-11-23 21:13                           ` Jorge Almeida
2005-11-17 14:14     ` Richard Fish
2005-11-17 16:19       ` Jorge Almeida
2005-11-17 17:11         ` Richard Fish
2005-11-17 17:47           ` Jorge Almeida
2005-11-17 18:14             ` Richard Fish
2005-11-17 18:23               ` Jorge Almeida
2005-11-17 20:15                 ` Richard Fish
2005-11-17 20:49                   ` Jorge Almeida
2005-11-17 21:11                     ` Richard Fish
2005-11-17 22:04                       ` Jorge Almeida
2005-11-17 23:57                         ` Richard Fish
2005-11-18  8:33                           ` Jorge Almeida
2005-11-18  7:03                       ` Dirk Heinrichs
2005-11-18  6:56         ` Dirk Heinrichs
2005-11-18  8:36           ` Jorge Almeida

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=Pine.LNX.4.63.0511230913580.1896@weber.math.ist.utl.pt \
    --to=jalmeida@math.ist.utl.pt \
    --cc=gentoo-user@lists.gentoo.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