Re: USB drives not recognized after reboot

[Patrick Mansfield <patmans@us.ibm.com>]

On Wed, Oct 25, 2006 at 05:04:00PM -0500, Steve Bergman wrote:
> I am running Fedora Core 6 with the vendor kernel which is 2.6.18.

You should try to reproduce it with a plain kernel (like 2.6.18) so we
know its not an FC6 specific problem.

> These drives work fine if I power them down and then backup up after the
> server is rebooted.

Compare or post your boot time logs (/var/log/messages or demsg output)
with output seen when the devices are properly detected.

Make sure all the correct modules are loaded, compare your lsmod output
for good and bad cases. You definitely need to have scsi_mod, sd_mod, and
usb_storage loaded.

Logs should show lines like:

Oct 23 11:39:36 sysa kernel: SCSI subsystem initialized
Oct 23 11:39:36 sysa kernel: Initializing USB Mass Storage driver...
Oct 23 11:39:36 sysa kernel: scsi0 : SCSI emulation for USB Mass Storage devices
Oct 23 11:39:36 sysa kernel: usbcore: registered new driver usb-storage
Oct 23 11:39:36 sysa kernel: USB Mass Storage support registered.
Oct 23 11:39:41 sysa kernel:   Vendor: Generic   Model: STORAGE DEVICE    Rev: 9
321
Oct 23 11:39:41 sysa kernel:   Type:   Direct-Access                      ANSI S
CSI revision: 00
Oct 23 11:39:41 sysa kernel: scsi 0:0:0:0: Attached scsi generic sg0 type 0
Oct 23 11:39:41 sysa kernel: SCSI device sda: 4061232 512-byte hdwr sectors (207
9 MB)
Oct 23 11:39:41 sysa kernel: sda: Write Protect is off
Oct 23 11:39:41 sysa kernel: sda: assuming drive cache: write through
Oct 23 11:39:41 sysa kernel: SCSI device sda: 4061232 512-byte hdwr sectors (207
9 MB)
Oct 23 11:39:41 sysa kernel: sda: Write Protect is off
Oct 23 11:39:41 sysa kernel: sda: assuming drive cache: write through
Oct 23 11:39:41 sysa kernel:  sda: sda1
Oct 23 11:39:41 sysa kernel: sd 0:0:0:0: Attached scsi removable disk sda

You can also ls /sys/block or ls /sys/bus/scsi/devices/ to see if the
block layer and scsi core are seeing the devices.

If devices aren't under /sys, it's not a udev issue.

> Actually, lsusb does show them as:
> 
> Bus 005 Device 005: ID 059f:0651 LaCie, Ltd
> Bus 005 Device 004: ID 059f:0651 LaCie, Ltd
> 
> However, udev does not notice them and no device files are created.
> 
> These are not partitioned, so the correct device file would be /dev/sda
> with a major of 8 and and minors of 0 and 16.
> 
> If I create the device files manually, 'mount' doesn't see them as  usb
> devices.  I believe it says it is not a valid block device, but I'm not
> certain of that and cannot test it right now as the server is currently
> live.
> 
> I need a way to force these drives to be detected at boot up even if I
> have to manually force it some way in rc.local.
> 
> I'm not certain that this is the proper list for this problem, but udev
> seems a reasonable place to start.

More likely a kernel usb mass storage or scsi problem, if all modules are
loaded and you can reproduce on mainline kernel post logs showing the
problem to linux-usb-devel@lists.sourceforge.net and
linux-scsi@vger.kernel.org

-- Patrick Mansfield

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel