I thought I had it!!??


HELP!

After reading a thread on this issue I did the following :

modprobe usb_storage and was able to mount /dev/sda1 /mnt/usbhd
just fine.

After rebooting I cannot mount this device any more??

Is this telling me to mounr /dev/sg1?

If so I get the same error:

mount -t ext3 /dev/sg1 /mnt/usbhd
mount: /dev/sg1 is not a block device!!

Geeze It mounted yesterday. I only rebooted?
______________________________________________________________


I get : dmesg snips
drivers/usb/core/usb.c: registered new driver usbfs
drivers/usb/core/usb.c: registered new driver hub

drivers/usb/host/uhci-hcd.c: USB Universal Host Controller Interface driver v2.1
uhci_hcd 0000:00:1f.2: UHCI Host Controller
PCI: Setting latency timer of device 0000:00:1f.2 to 64
uhci_hcd 0000:00:1f.2: irq 5, io base 0000ef40
uhci_hcd 0000:00:1f.2: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
uhci_hcd 0000:00:1f.4: UHCI Host Controller
PCI: Setting latency timer of device 0000:00:1f.4 to 64
uhci_hcd 0000:00:1f.4: irq 9, io base 0000ef80
uhci_hcd 0000:00:1f.4: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
drivers/usb/core/usb.c: registered new driver usbkbd
drivers/usb/input/usbkbd.c: :USB HID Boot Protocol keyboard driver
drivers/usb/core/usb.c: registered new driver usbmouse
usb 1-2: new full speed USB device using address 2
usb 2-2: new full speed USB device using address 2
SCSI subsystem initialized
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: SONY Model: DVD RW DRU-510A Rev: 1.0c
Type: CD-ROM ANSI SCSI revision: 02
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
scsi1 : SCSI emulation for USB Mass Storage devices
Vendor: IC35L090 Model: AVV207-0 Rev: V23O
Type: Direct-Access ANSI SCSI revision: 02
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
drivers/usb/core/usb.c: registered new driver usb-storage
USB Mass Storage support registered.

Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 5
Attached scsi generic sg1 at scsi1, channel 0, id 0, lun 0, type 0
_______________________________________________________

mount /dev/sda1 /mnt/usbhd
mount: you must specify the filesystem type.

mount -t ext3 /dev/sda1 /mnt/usbhd
mount: /dev/sda1 is not a valid block device.

lsmod:
usb_storage 65472 0
scsi_mod 115512 2 sg,usb_storage

lspci
0000:00:00.0 Host bridge: Intel Corp. 82850 850 (Tehama) Chipset Host Bridge (MCH) (rev 02)
0000:00:01.0 PCI bridge: Intel Corp. 82850 850 (Tehama) Chipset AGP Bridge (rev 02)
0000:00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB PCI Bridge (rev 02)
0000:00:1f.0 ISA bridge: Intel Corp. 82801BA ISA Bridge (LPC) (rev 02)
0000:00:1f.1 IDE interface: Intel Corp. 82801BA IDE U100 (rev 02)
0000:00:1f.2 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #1) (rev 02)
0000:00:1f.3 SMBus: Intel Corp. 82801BA/BAM SMBus (rev 02)
0000:00:1f.4 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #2) (rev 02)
0000:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon VE QY
0000:02:0a.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07)
0000:02:0a.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 07)
0000:02:0c.0 Communication controller: Conexant HCF 56k Data/Fax/Voice/Spkp Modem (rev 08)
0000:02:0d.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)

uname -r
2.6.2-48932cl

scsibus1:
1,0,0 100) 'IC35L090' 'AVV207-0 ' 'V23O' Disk
lsusb
Bus 002 Device 002: ID 0c0b:b001 Dura Micro, Inc. (Acomdata)

I've had this happen before too and I don't know why. I guess when your computer starts, it assigns a device name to your devices depending on the order in which they were plugged in. For example, if you have another usb device plugged in, it might have become sda1 during the reboot, so now your device might be sdb1. There are only two ways that I have found to solve this problem:
1. Mount as root, including the fs type.
or
2. Using the 2.6.3 kernel, I wrote udev rules so that the device is always named /dev/usbhd. Here's a good tutorial on how to do that.

still I get /dev/sda1 not a valid block device when I use as root mount -t ext3 /dev/sda1 /mnt/usbhd.

Like I said it worked before I re-booted ??

Thanks for trying though

PC

For some reason, your usb drive isn't being assigned a device address. It looks like the kernel can see it, it just doesn't label it. WHat kernel are you using--2.4.x or 2.6.x?

uname -r
2.6.2-48932cl

When I run cdrecord -scanbus I get:

scsibus1:

1,0,0 100) ' IC35L090 ' 'AVV207-0 ' 'V230' DISK


I assumed this was a valid address is it Not ?

See the end of my first post for more details

have you installed udev or are you still using devfs?

not sure how do I tell ?? I did not install anything after installing the distro with 2.61 and using apt to upgrade to 2.6.2

what distro are you using?

Conectiva 10

Login as su or root and type fdisk -l /dev/sda. If /dev/sda1 doesn't show then the kernel doesn't recoqnize your USB device. You have to add a few lines of code to a certain file or add a line in the usb-distmap in the hotplug directory.

I don't know how kernel 2.6.x is setup. I'm still using kernel version 2.4.x. Probably between March and August I'll try to compile 2.6.x but it depends on VMware if they can revise their modules for 2.6.x kernel.

we may be getting some where as fdisk -l /dev/sda returns nothing?

Weird as this WAS WORKING until I rebooted!

Note I also need to use VMware and found it will not install.

I may have found the problem. I plugged the USB-STORAGE device into another system running 2.6.1 kernel
and it mounted ok.

Then I ran lsmod and compared with the 2.6.2 kernel system.

Seems the 2.6.2 kernel is missing usbcore module ? which is weird as my printer is usb and works?

hmm try updating to 2.6.3 and see if that fixes it.

NO need to install 2.6.3 Here is what makes it work.

1) turn off USB-Storage device
2) re-boot system
3) turn on USB-Storage device
4) mount /dev/sda1 /mnt/usbhd

Not sure why this works? Perhaps a hot-plug feature/bug?


Philip