(Sorry for the belated response.) Am Mon, 23 Mar 2015 17:14:27 -0400 (EDT) schrieb Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>: > On Mon, 23 Mar 2015, Marc Joliet wrote: > > > OK, so obviously the drive is doing something wrong. I'm just confused about > > why one way works and not the other: > > > > - Boot up the computer with the drive attached: failure. > > > > - Boot up the computer without the drive attached, load the required kernel > > modules, and plug it in: success. > > > > I would think that, if it's solely the drive's fault, neither case would work, > > since in both cases I'm plugging the drive in for the first time and it has > > not spun up yet, and in both cases the uas and usb-storage modules are loaded > > beforehand (albeit with a larger delay in the second case). That is: what is > > the difference from the drive's perspective? > > Like Matt suggested, the most reasonable possibility is an interaction > with the BIOS. Like I said in my replay to Matt, the BIOS doesn't support booting via USB. The only thing I was able to try was to deactivate CD boot, which didn't change anything (except make boot faster, which is a nice side-effect, since I only very rarely boot from CD). I tried hooking it up to a borrowed laptop I have here (that only has USB 2 ports) to see how it behaves at boot. The BIOS was set to boot form its internal drive (followed by USB, but that would only trigger if the internal drive were missing, so it shouldn't have any influence, right?), and it behaved the same. > > (Also, why does Windows, without any manually installed drivers, work, then?) > > No way to know unless you can trace the communication between Windows > and the drive. There are a few USB sniffer programs available for > Windows, but I don't know if you'll be able to get them to start before > Windows has detected the drive. If I have the time and motivation to do this, I can certainly try. > > This, and all the other situations I described where the drive worked fine > > (such as turning the drive off for several hours), make me wonder whether you > > or anybody else on this list know of any drives/usb adapters that behave in > > strange ways when they are connected at boot up like this (for example, I read > > of older drives that would initially announce themselves as CD-ROM drives). > > There are plenty of devices which do that. The manufacturers store > drivers, manuals, and other information on the emulated CDs. > > No, I don't know of any devices with other crazy behaviors. But then I > don't try to keep track of such things. OK > > Of course, if the diagnosis is definitely "the drive did it", then I'm willing > > to resign myself to the notion that nothing can be done about it, however > > disappointing that would be. > > Well, it may be possible to replace the adapter. Or, if you can find > out what Windows does, it may be possible to make Linux do the same > thing. I like the latter option better, since I wouldn't be surprised if many (or at least several) external HDDs do things like this. All the more so since the links from my OP are several years old already (2013 and 2010, respectively). Regardless, thanks to you (and also to Matthew) for your help. I'll just have to accept the problem as it is, and maybe revisit it in the future as mentioned above. Of course, if I'm lucky, a developer here will obtain such a drive first and then get Linux to work well with it :) . Thanks again, -- Marc Joliet -- "People who think they know everything really annoy those of us who know we don't" - Bjarne Stroustrup
Attachment:
pgpb6LrM0RNeg.pgp
Description: Digitale Signatur von OpenPGP
