- This topic has 12 replies, 5 voices, and was last updated Sep 12-9:24 am by ModdIt.
-
Posts
-
Anonymous
Hello again. Third thread…
I have an old 32 Gb Kingston USB 2.0 stick formatted with FAT32, which, despite old, still works well in other systems.
But here on Antix live, I plug it, and only after half a minute (yes, *30 freaking seconds*) the device is recognized and mounted. During those whole 30 seconds CPU monitor also goes crazy high.
I have never seen this issue in other Linux distros or even Windows, unless rig is clearly broken in hardware. And I really don’t think my rig is broken because if I boot into Windows the USB device works like normal, immediately recognized and opened.
Could anyone help please?
Thanks beforehand.
sybok
Hi, not an answer but it seems the issue was already observed by someone else in Ubuntu though the USB was slow in Win 7 as well.
antiX live = running from live USB, which version of antiX?
I would (naively) suspect that it has something to do with running live (in RAM) and loading/making-available rather large USB on top of that.
However, the above Ubuntu-related link suggests that it may not be related to size of USB because an SD of comparable size did mount faster (in an installed [!] Ubuntu; but I cannot tell about the difference SD vs. USB in general…).Could you please repeat the procedure (inserting the USB) and post e.g.
1) lsusb; lsusb -t
2) inxi -Fxz
3) copy-paste/screenshot of ‘top’ (‘htop’ or some other system monitor) indicating what processes heavily use your CPU when mounting/accessing the USB?I may not be able to provide the answer but someone else might be able to help using the additional information.
ModdIt
Hi ctcx, a week ago I had similar issues with a Transcend stick.
Please try another stick and see if it has similar behaviour.
That will point us in direction of stick or computer/system. Also pls answer sybok.
My stick was accepted by windows which I used to test and later repair, but it was definitely
not ok. It would also write but at snail pace.Other USB Sticks worked fine with antiX so issue not driven by hardware or my installation
of antiX. I used same computer, just swapped in a drive with Windoze to help fault find.Finally I found out that the stick was defective, maybe due code design windows was not
detecting the issues.In my case I was able to update the USB stick controller software using
a tool provided by transcend, the stick is now in use and works fine.During those whole 30 seconds CPU monitor also goes crazy high.
I have never seen this issue in other Linux distros
During such “incidents”, utilizing the “dmesg” command would probably be enlightening
https://en.wikipedia.org/wiki/Dmesg
dmesg (diagnostic message) is a command on most Unix-like operating systems that prints the message buffer of the kernel. The output includes messages produced by the device drivers.
[..]
It is also common to manually consult the current dmesg buffer after hot-plugging devices, particularly USB devices (especially thumb drives), to determine whether the device has been recognized, the data rate of the port involved (USB 2 and USB 3.0 plugs sit side by side and are hard to distinguish on many systems), what driver has been assigned, and where the device is made visible in the file system.Thanks everyone.
demo@antix1:~ $ inxi -Fxz System: Host: antix1 Kernel: 4.9.0-264-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: IceWM 2.3.4 Distro: antiX-19.4_x64-base Grup Yorum 20 May 2021 base: Debian GNU/Linux 10 (buster) Machine: Type: Laptop System: Gateway product: NE-522 v: V2.02 serial: <filter> Mobo: Gateway model: NE-522 v: V2.02 serial: <filter> UEFI: Insyde v: 2.02 date: 05/03/2013 Battery: ID-1: BAT0 charge: 1.6 Wh condition: 23.4/37.0 Wh (63%) model: SANYO AL12A32 status: Charging CPU: Topology: Dual Core model: AMD E1-2500 APU with Radeon HD Graphics bits: 64 type: MCP arch: Jaguar rev: 1 L2 cache: 1024 KiB flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 5589 Speed: 1200 MHz min/max: 800/1400 MHz Core speeds (MHz): 1: 800 2: 1000 Graphics: Device-1: AMD Kabini [Radeon HD 8240 / R3 Series] vendor: Acer Incorporated ALI driver: radeon v: kernel bus ID: 00:01.0 Display: server: X.Org 1.20.4 driver: ati,radeon unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz OpenGL: renderer: AMD KABINI (DRM 2.49.0 4.9.0-264-antix.1-amd64-smp LLVM 7.0.1) v: 4.5 Mesa 18.3.6 direct render: Yes Audio: Device-1: AMD Kabini HDMI/DP Audio vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel bus ID: 00:01.1 Device-2: AMD FCH Azalia vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel bus ID: 00:14.2 Sound Server: ALSA v: k4.9.0-264-antix.1-amd64-smp Network: Device-1: Qualcomm Atheros QCA8171 Gigabit Ethernet vendor: Acer Incorporated ALI driver: alx v: kernel port: 2000 bus ID: 01:00.0 IF: eth0 state: down mac: <filter> Device-2: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter vendor: Lite-On driver: ath9k v: kernel port: 2000 bus ID: 05:00.0 IF: wlan0 state: up mac: <filter> Device-3: Lite-On Atheros AR3012 Bluetooth type: USB driver: btusb bus ID: 4-2:5 Drives: Local Storage: total: 223.57 GiB used: 591.6 MiB (0.3%) ID-1: /dev/sda vendor: A-Data model: SU650 size: 223.57 GiB Partition: ID-1: / size: 3.63 GiB used: 591.6 MiB (15.9%) fs: overlay source: ERR-102 Sensors: System Temperatures: cpu: 53.5 C mobo: 37.0 C gpu: radeon temp: 53 C Fan Speeds (RPM): N/A Info: Processes: 125 Uptime: 3h 19m Memory: 5.28 GiB used: 336.0 MiB (6.2%) Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.36 demo@antix1:~ $demo@antix1:~ $ lsusb; lsusb -t Bus 002 Device 002: ID 064e:e330 Suyin Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 005: ID 04ca:300b Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 003: ID 0951:1665 Kingston Technology Digital DataTraveler SE9 64GB #When USB stick plugged Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/4p, 12M |__ Port 2: Dev 5, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 2: Dev 5, If 1, Class=Wireless, Driver=btusb, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/4p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/4p, 480M |__ Port 1: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 1: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/4p, 480M |__ Port 1: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 480M #When USB stick plugged demo@antix1:~ $Only posted last 20 lines of dmesg because those are the only ones related to the USB stick.
demo@antix1:~ $ dmesg | tail -n 20 [13125.322129] usb 1-1: new high-speed USB device number 3 using ehci-pci [13125.448261] usb 1-1: New USB device found, idVendor=0951, idProduct=1665 [13125.448270] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [13125.448276] usb 1-1: Product: DataTraveler 2.0 [13125.448281] usb 1-1: Manufacturer: Kingston [13125.448286] usb 1-1: SerialNumber: 60A44C413DF8B070698C0043 [13125.449485] usb-storage 1-1:1.0: USB Mass Storage device detected [13125.451574] scsi host2: usb-storage 1-1:1.0 [13126.118565] usbcore: registered new interface driver uas #This line only the first time USB was plugged [13126.470345] scsi 2:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 4 [13126.472248] sd 2:0:0:0: Attached scsi generic sg2 type 0 [13129.730778] sd 2:0:0:0: [sdb] 60466944 512-byte logical blocks: (31.0 GB/28.8 GiB) [13129.732100] sd 2:0:0:0: [sdb] Write Protect is off [13129.732141] sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00 [13129.733506] sd 2:0:0:0: [sdb] No Caching mode page found #highlighted in red [13129.733512] sd 2:0:0:0: [sdb] Assuming drive cache: write through #highlighted in red [13129.743873] sdb: sdb1 [13129.748485] sd 2:0:0:0: [sdb] Attached SCSI removable disk [13135.058927] FAT-fs (sdb1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! #highlighted in bold [14009.175728] usb 1-1: USB disconnect, device number 3 #unmounted and disconnected USB stick demo@antix1:~ $Command “top” while the USB stick struggles to be recognized:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 50255 root 20 0 0 0 0 D 6.0 0.0 0:00.42 usb-storage 50368 demo 20 0 389020 50060 35800 D 3.7 0.9 0:01.02 spacefm 12872 root 20 0 597516 87608 50968 S 2.7 1.6 13:32.39 XorgIssue happening on all laptops’s USB ports equally.
The USB stick works quite normal on same laptop when on Windows 10; also with other Linux distros and other different rigs.However, on other rigs (e.g. an old Toshiba Satellite L955 from circa 2012), but with this Antix 19 live system, this issue still happens.
First, I find it not good that lsusb output thinks the USB stick is 64 Gb size, when it’s actually 32 Gb as a whole, i.e., it’s not weirdly partitioned nor the like.
Second, I did a desperate test:
sudo dd if=/dev/zero of=/dev/sdb bs=4M status=progress
and in the meanwhile (it took 2.5 hours in total, for 32 Gb…) I went to get some few new USB sticks.Then worked on the used USB stick with Gparted. First tried creating a new FAT32 partition, and tested. Still takes long time to be mounted, though now less: from 30 seconds to 20.
Tested with other file systems: ext4 took 10 seconds, NTFS curiously took 8 seconds.
I tried with exFAT, but Gparted only threw an error, like “invalid option -L”. And yes, Gparted tries to use this option with the command. Is this a bug?Then tested the totally new USB stick, which is also a Kingston DT USB2, albeit 16 Gb. Also formated with FAT32 out of the box.
This one took 14 seconds to be mounted…sybok
Hi, interesting that NTFS was faster than FAT32. The link I mentioned in my post claimed otherwise and even provided an explanation (NTFS journaling).
BTW, few dummy questions related to HW (better late than never):
1) Did you try to clean contacts of (both) the USB drive (and the socket)?
2) Is it possible that some of the internal connecting cables got loose? Can you examine that? (With the PC switched off, disconnected from power and you grounded/discharged e.g. by touching a water-tap.)
This could be relatively easy if you have a desktop and it would be an opportunity to clean some dust that might have collected.First, I find it not good that lsusb output thinks the USB stick is 64 Gb size, when it’s actually 32 Gb as a whole
Not good to blame the OS for what the USB stick controller reports. The OS can not check the actual size of a plugged
in stick.Maybe you should search the forum for how and run F3 over your stick or sticks. You may have fake or defective sticks.
Only way to find out is to test them. There are differences in the way different OS work with sticks, windows believes
anything the stick tells it, and loads virus or trojan from stick immediaetly. Some linux distros are probably very tolant
too.You may well have an answer for some of your purported issues if the stick is fake or has a controller defect.
None of my myriad usb sticks have the kind of problem you report.
One did, until a short time ago, a 64 GB Transcend stick which I was able to repair using an online tool from
the manufacturer. The controller software was defective.My experience with Kingston sticks was that many were not real.
Regarding I tried with exFAT, but Gparted only threw an error, like “invalid option -L”. And yes, Gparted tries to
use this option with the command. Is this a bug?. Exfat support on debian based systems is now in the kernel, not an
external tool. I can use it without any isssue with a very recent kernel. You may need to update your system Kernel.Hell, old USB stick just suddenly went back to take 30 seconds to be mounted out of the blue…
Though new one still takes same 14 seconds until now.Hell, old USB stick just suddenly went back to take 30 seconds to be mounted out of the blue…
Which points toward it being defective. Will no longer bother to answer you as blaming os
will never give a solution….
rokytnji
Usb 1.1 speeds is like watching paint dry, sometimes.
Put some usb 2.0 addon gear on the ancient gear if wanting more speed. If the MOBO accepts it.
I run USB PCMCIA 2.0 speeds when needed. Older laptops all have pcmcia slots, usually.Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problems@ModdIt, @Xecure, everyone else:
I apologize for all the inconveniences. In the end you all may be right: maybe it’s a thing with the sticks themselves, and probably even with the brand itself.I just couldn’t “digest” the fact that they behaved differently in different systems, and with different file formats on top of that. But I think it was my ignorance.
Thanks everyone for your help. No more bothers in this topic.
@ctcx. even when you buy new sticks they can be defective or fake, best way is to install and use F3 to
check sticks before use. It is a very good tool set. Fake sticks can and do inject virus or trojans, or
try to do so. As you have found Issues can be very puzzling and frustrating.
sudo apt install f3
For usage look in net, it can not detect every error but is a good pointer.I wrote about my Stick from Transcend, a good brand. It showed
weirdest errors, slow to be recognized, loss of data, refused to boot an image.When I researched I found Transcend had admitted to a controller software defect and offered a tool to
fix the issue. I had to plug in a windoze disk to my laptop to do the fix. I could also have used a fresh
download and install from ms, that runs for 30 days and IS LEGAL.What I like is Transcend admitted a problem and provided a fix. I am using that stick now as it hosts antiX
Beta2 runit. I have many sticks from that company, the higher priced ones with silver case, to date all have
been reliable.
- You must be logged in to reply to this topic.
