Stupid Hotplug....

[leech]

Ok, I have a 200GB harddrive in a USB 2.0 external enclosure... now if I mount it by hand, it works. But if I allow Hotplug to do it, for some reason it thinks that the device should be /dev/sda1 (it's actually /dev/sdc1) sda1 is my 73gb harddrive which is my Windows drive. And sdb1 is my linux drive (I have SCSI if you haven't figured that out yet.. ) usb-storage module always treats them as scsi devices, so of course since sda and sdb are already taken, the usb device has to be sdc, but hotplug keeps thinking it's sda.

Any ideas? I do have a script that was created off of a website...Unfortunately I can't find that site right now. I'll post the script after work today, when I've rebooted into linux again...

Leech

[The PIT]

Use winblows and it'll be correctly assigned.

[leech]

That's funny... since windows has a LOT more problems with it than linux ever will. In windows it takes an extra minute to load up if I have the drive connected and turned on when windows boots up. And it takes a full minute for it to be recognized by windows if I turn it on after windows is up and running. In linux, it's instantaneous. I actually had automounter working properly until I updated my hotplug package, then it fubar'd it.

This script that I found off the page that I can no longer find... works flawlessly. It creates a symbolic link in /mnt/usbdrive to /var/autofs/removable/usbdrive. But now hotplug decided it wanted to create a different usb-storage script (so I made a back up of the one I was using before I told debian to overwrite it with the hotplug installed one...) The script that works looks like this.
#!/bin/sh
set >> /tmp/settings
case "$PRODUCT" in
402/5621/103) #ByteCC
ln -s /var/autofs/removable/usbdrive /mnt/usbdrive
#set up what to do when remove the drive
echo -e '#!/bin/sh\nrm /mnt/usbdrive' > $REMOVER
chmod a+x $REMOVER
;;
esac


I probably just have to find that page again...

Oops, as I was constructing this post, I located a package that I apparently found somewhere on the net, but I don't know where!! It's a package called usb-storage version 2.0-1. I can't even find the actual debian package on my harddrive (it's not in apt's cache, and I didn't see it on apt-get.org.. ) I can see which files are in the debian package (due to synaptic) The mystery continues... this is what I get for messing around with something that worked before.....typical.

Leech

[Duty]

maybe here http://s1x.homelinux.net/

[Marshmallowman]

What's the scsi ID's of your drives, I would think the drive witht the lowest ID gets the "a" spot.

[leech]

/dev/sda1 is a 73gb 10krpm Quantum Atlas drive.

/dev/sdb1 is a 36gb 10krpm IBM drive.

/dev/sdc1 is the 200gb USB drive.

And yes, sda1 is ID 0, sdb1 is ID 1 and of course since linux uses the usb-storage device as a SCSI controller.. it doesn't really have an ID per se, but linux treats it as if it's on it's own controller..

Leech

P.S. Yes, Duty, that must be where I had found it... Thanks!

Edit: To quote from the page... "Supports systems with multiple SCSI hardisks and multiple usb storage devices." Figured I wouldn't have any issues.. It does create a nice little icon on my desktop in gnome... too bad it's the 'sda' icon, which I can already access...

[Marshmallowman]

Looks like it might be time to have some fun edting fstab

thats where all the device and mounting info is .

[leech]

Tried that... it seems to want it to be dynamic (because of devfs?) Debian, by default, sets up /cdrom as the first cdrom and /cdrom1 as the second cdrom. As well as /windows as any vfat or ntfs filesystem. But this usb-storage script must remove the /windows directory, because it's no longer there. And I even hand edited it back in there, and it removed it again....

Leech

[The PIT]

Well some os suck try another one.

[leech]

yeah, too bad x86 won't run Mac OS X

Leech

Edit: Or I could use that one (un)Operating System that takes 4 minutes just to install a security update that is only 416kb... And this was on a 2.7ghz Celeron with 256mb of Ram....