Opened 15 years ago
Closed 15 years ago
#4937 closed bug (invalid)
USB stick not recognized when plugged before boot
Reported by: | skfir | Owned by: | mmlr |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Drivers/USB | Version: | R1/alpha1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
If I insert a thumb drive before the systems is loaded, the drive is not recognized, I have to take it off and insert again. If I don't remove it and reboot the machine, drive is not recognized after rebooting as well. And after reading from the drive, when I unpluged it, the system fell into debug mode.
Attachments (3)
Change History (12)
comment:1 by , 15 years ago
comment:2 by , 15 years ago
Component: | - General → Drivers/USB |
---|---|
Owner: | changed from | to
comment:3 by , 15 years ago
What revision are you testing with? The alpha release or something more current?
by , 15 years ago
Attachment: | IMG_0016.JPG added |
---|
by , 15 years ago
Attachment: | syslog.zip added |
---|
comment:6 by , 15 years ago
One more problem: when attempted to delete a folder from a flash drive system crashed to KDL. Please look at img_0015
by , 15 years ago
Attachment: | IMG_0015.jpg added |
---|
comment:8 by , 15 years ago
Summary: | USB Bug → USB stick not recognized when plugged before boot |
---|
Replying to skfir:
If I insert a thumb drive before the systems is loaded, the drive is not recognized, I have to take it off and insert again.
And by "not recognized" you mean not auto-mounted or not available to mount from the mount menu? From the syslog, the drive and the FAT filesystem on it are detected just fine.
If I don't remove it and reboot the machine, drive is not recognized after rebooting as well.
Again, what exactly do you mean by "not recognized"? Does it not show up in the mount menu?
And after reading from the drive, when I unpluged it, the system fell into debug mode.
If you unplug it without unmounting this is perfectly expected and indicates that you just lost and/or corrupted some data. From the screenshot it looks like a read-write mounted filesystem wasn't able to write back changes when it was unmounted because of the unplug provoked media change event.
The second screenshot is very hard to read, but doesn't look related. It indeed looks like a FAT problem where a block was modified where no modification was expected. Might be a race condition and might be related to the cluster != 0 assert.
comment:9 by , 15 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
I'm going to close this one. Without further feedback all seems perfectly fine as explained in comment 8 above. I can only guess that by "not recognized" actually "not automounted" was meant as the syslog indicates the device and filesystem were detected fine.
this is possibly related to #2344