USB Stick Question

[Member Budgie]

I am working on an old 32 bit machine with antiX installed. I installed from USB stick and I assumed all was well but I have just inserted an USB 3 stick and it doesn’t work. Is there any way around this or is it just an incompatibility issue?
Budge

[Member PPC]

Helpful

Up

0

::

It’s very probable that “an old 32 bit machine”‘s USB port is not compatible with USB 3…

read here: https://en.wikipedia.org/wiki/USB_3.0#Adding_to_existing_equipment
It seems that an USB 3 port has different pins than those of previous versions…

P.

[Anonymous]

Helpful

Up

0

::

given only the vague “it doesn’t work” description, this is impossible to troubleshoot

Check the output of dmesg command (or lack of output) after attaching the usb device. Is the event logged? Any errors shown?

[Member PPC]

Helpful

Up

0

::

I’ve read a bit more, to give further support to my initial statament:

https://www.lifewire.com/usb-physical-compatibility-chart-2624585

States:

The biggest issue you’ll probably find is that some USB 3.0 devices may not communicate at all when used on a computer or other host device that supports only USB 1.1.

P.

[Member Budgie]

Helpful

Up

0

::

 26.854945] lib80211_crypt: registered algorithm 'CCMP'
[  252.742193] usb 1-7: new high-speed USB device number 3 using ehci-pci
[  252.871330] usb 1-7: New USB device found, idVendor=090c, idProduct=1000, bcdDevice=11.00
[  252.871335] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  252.871339] usb 1-7: Product: Flash Drive
[  252.871341] usb 1-7: Manufacturer: Samsung
[  252.871344] usb 1-7: SerialNumber: 0342120110012854
[  253.711289] usb-storage 1-7:1.0: USB Mass Storage device detected
[  253.714868] usb-storage 1-7:1.0: Quirks match for vid 090c pid 1000: 400
[  253.715946] scsi host2: usb-storage 1-7:1.0
[  253.717100] usbcore: registered new interface driver usb-storage
[  253.736214] usbcore: registered new interface driver uas
[  255.926942] scsi 2:0:0:0: Direct-Access     Samsung  Flash Drive      1100 PQ: 0 ANSI: 6
[  255.929499] sd 2:0:0:0: Attached scsi generic sg2 type 0
[  255.930166] sd 2:0:0:0: [sdb] 501253132 512-byte logical blocks: (257 GB/239 GiB)
[  255.930878] sd 2:0:0:0: [sdb] Write Protect is off
[  255.930883] sd 2:0:0:0: [sdb] Mode Sense: 43 00 00 00
[  255.931511] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[  255.936292]  sdb: sdb1
[  255.938876] sd 2:0:0:0: [sdb] Attached SCSI removable disk

So it seems the device is seen as a drive but not properly mounted.
fdisk -l tells me all is ok:-

$ sudo fdisk -l
Disk /dev/ram0: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram1: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram2: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram3: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram4: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram5: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram6: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram7: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram8: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram9: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram10: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram11: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram12: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram13: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram14: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram15: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/sda: 74.5 GiB, 80026361856 bytes, 156301488 sectors
Disk model: HTS548080M9AT00
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x41ab2316

Device Boot Start End Sectors Size Id Type
/dev/sda2 2048 31088639 31086592 14.8G 83 Linux
/dev/sda3 31088640 152104959 121016320 57.7G 83 Linux
/dev/sda4 152109056 156301487 4192432 2G 82 Linux swap / Solaris

Disk /dev/sdb: 239 GiB, 256641603584 bytes, 501253132 sectors
Disk model: Flash Drive
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device Boot Start End Sectors Size Id Type
/dev/sdb1 256 501253099 501252844 239G 7 HPFS/NTFS/exFAT
alastair@Dell-9300-antix1:~
$
`
Sorry my touchpadis driving me crazy.
Grateful for your advice please.

[Member Budgie]

Helpful

Up

0

::

 cat fstab
# Pluggable devices are handled by uDev, they are not in fstab
UUID=37407943-6191-4582-beca-681ecad4a2a9 / ext4 defaults,noatime 1 1
UUID=9e43a24f-37d5-4e02-a879-9faafe04026b /home ext4 defaults,noatime 1 2
UUID=7aad6124-af34-4f9a-92e0-0e0ab681428b swap swap defaults 0 0 
/dev/cdrom                                 /media/cdrom                                iso9660    noauto,exec,users,ro            0 0
/dev/cdrw                                  /media/cdrw                                 iso9660    noauto,exec,users,rw            0 0
/dev/dvd                                   /media/dvd                                  udf        noauto,exec,users,ro            0 0
/dev/dvdrw                                 /media/dvdrw                                udf        noauto,exec,users,rw            0 0
/dev/sr0                                   /media/sr0                                  auto       noauto,exec,users,ro            0 0
alastair@Dell-9300-antix1:/etc
$ 

I tried to mount the device as /dev/sdb1 but no.
This explains why I cannot mount but now I am stuck and need help.

[Member Budgie]

Helpful

Up

0

::

alastair@Dell-9300-antix1:~
$ udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[2147.351643] add      /devices/pci0000:00/0000:00:1d.7/usb1/1-7 (usb)
KERNEL[2147.353453] add      /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0 (usb)
KERNEL[2147.354710] add      /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2 (scsi)
KERNEL[2147.354750] add      /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/scsi_host/host2 (scsi_host)
KERNEL[2147.354790] bind     /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0 (usb)
KERNEL[2147.354837] bind     /devices/pci0000:00/0000:00:1d.7/usb1/1-7 (usb)
UDEV  [2147.933651] add      /devices/pci0000:00/0000:00:1d.7/usb1/1-7 (usb)
UDEV  [2147.936433] add      /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0 (usb)
UDEV  [2147.937733] add      /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2 (scsi)
UDEV  [2147.938599] add      /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/scsi_host/host2 (scsi_host)
UDEV  [2147.939676] bind     /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0 (usb)
UDEV  [2147.945614] bind     /devices/pci0000:00/0000:00:1d.7/usb1/1-7 (usb)
KERNEL[2149.648268] add      /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0 (scsi)
KERNEL[2149.648342] add      /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0/2:0:0:0 (scsi)
KERNEL[2149.648393] add      /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0/2:0:0:0/scsi_disk/2:0:0:0 (scsi_disk)
KERNEL[2149.648447] bind     /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0/2:0:0:0 (scsi)
KERNEL[2149.648495] add      /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0/2:0:0:0/scsi_device/2:0:0:0 (scsi_device)
KERNEL[2149.650611] add      /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0/2:0:0:0/scsi_generic/sg2 (scsi_generic)
KERNEL[2149.651211] add      /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0/2:0:0:0/bsg/2:0:0:0 (bsg)
UDEV  [2149.652631] add      /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0 (scsi)
KERNEL[2149.653440] add      /devices/virtual/bdi/8:16 (bdi)
UDEV  [2149.656822] add      /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0/2:0:0:0 (scsi)
KERNEL[2149.658442] add      /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0/2:0:0:0/block/sdb (block)
KERNEL[2149.658482] add      /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0/2:0:0:0/block/sdb/sdb1 (block)
UDEV  [2149.659164] add      /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0/2:0:0:0/scsi_disk/2:0:0:0 (scsi_disk)
UDEV  [2149.660186] bind     /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0/2:0:0:0 (scsi)
UDEV  [2149.667772] add      /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0/2:0:0:0/scsi_device/2:0:0:0 (scsi_device)
UDEV  [2149.670106] add      /devices/virtual/bdi/8:16 (bdi)
UDEV  [2149.674161] add      /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0/2:0:0:0/bsg/2:0:0:0 (bsg)
UDEV  [2149.675317] add      /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0/2:0:0:0/scsi_generic/sg2 (scsi_generic)
UDEV  [2149.757170] add      /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0/2:0:0:0/block/sdb (block)
UDEV  [2149.831046] add      /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0/2:0:0:0/block/sdb/sdb1 (block)
KERNEL[2150.252232] change   /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0/2:0:0:0/block/sdb/sdb1 (block)
UDEV  [2150.322502] change   /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host2/target2:0:0/2:0:0:0/block/sdb/sdb1 (block)

This is the result from monitoring udev using udevadm monitor and afterplugging in the problem device.
I hope this helps

[Member Budgie]

Helpful

Up

0

::

Further to this I succeeded in adding the device to udev using .rules but I may have made an error in my scripts because remvoving the device doesn’t show. This is waht I have now:

 cat /tmp/scripts.log
USB device added at Mon May 24 10:23:56 BST 2021
USB device added at Mon May 24 10:27:42 BST 2021
alastair@Dell-9300-antix1:~

But I still cannot mount it and am now well beyond my comfort zone!`

[Member Budgie]

Helpful

Up

0

::

Been round the houses with this one and missed the simple expedient of creating a mount point before trying to mount the device.
Now I can mount the device but even if I unmount it correctly I get a warning message that the volume was not unmounted cleanly.
Possibly true with all the udev work I did but this leaves me with two question:-

How can I get automount to work correctly and put the volume in my conky directory where I can see it?

What should I run to correct the exfat file system on my stick?

Is anybody able to help please?

Budge.

[Member PPC]

Helpful

Up

0

::

Budgie wrote:

What should I run to correct the exfat file system on my stick?

I’ve been in a similar spot… Try doing something similar to this (I could not find an application to correct exfat, only ntfs, you’ll have to serch the net for that, my quick search found nothing): https://www.antixforum.com/forums/topic/strange-error-when-trying-to-mount-lg-external-drive/

I’m glad that you partly solved your problem and can now mount the device (the 32 bits machine is not so old that’s USB 1.1 only, fortunately for you)
Stupid question- did you try unmounting it from Spacefm’s device’s list?

Edit: all I found on-line as this: https://forums.kali.org/showthread.php?50070-external-USB-drive-with-exFAT-not-mounting-(did-anything-be-changed-with-a-lately-update-)

P.

• This reply was modified 1 year, 11 months ago by PPC.
• This reply was modified 1 year, 11 months ago by PPC.

[Member Xecure]

Helpful

Up

0

::

Remove all changes you have already done to udev and mount it normally (af you have already done) and then
A. Add it manually to fstab (with auto to automount). If you don’t know how, mount it manually, as you already did, and then run
make-fstab
This will create a fstab file in your home folder (or wherever you have the terminal opened). Copy the line you want from the correct device to your /etc/fstab and change noauto to auto (so it automounts)

To add it to conky, see how it is done in ~/.conkyrc
Possible example:
${color}USB drive:${alignr}${fs_used /media/demo/my-drive/} ${color3} /${color} ${fs_size /media/demo/my-drive/}
Where you replace /media/demo/my-drive/ with the correct path to your drive. You may want to study how to do if statements in conky so that it only is displayed when the device is connected.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member Budgie]

Helpful

Up

0

::

Hi Xwcure,`
Many thanks for your advice. I have removed all my previous efforts and mounted the USB exfat stick manually.
I have used the make-fstab command to ensure I had it right and edited my /etc/fstab to include the line for the stick drive. I also added users and rw which seem right.
Here is my /etc/fstab now:-

alastair@Dell-9300-antix1:~
$ cat /etc/fstab
# Pluggable devices are handled by uDev, they are not in fstab
UUID=37407943-6191-4582-beca-681ecad4a2a9 / ext4 defaults,noatime 1 1
UUID=9e43a24f-37d5-4e02-a879-9faafe04026b /home ext4 defaults,noatime 1 2
UUID=7aad6124-af34-4f9a-92e0-0e0ab681428b swap swap defaults 0 0
UUID=64A5-F009 /media/alastair/big_stick exfat auto,exec,users,rw 0 0
/dev/cdrom /media/cdrom iso9660 noauto,exec,users,ro 0 0
/dev/cdrw /media/cdrw iso9660 noauto,exec,users,rw 0 0
/dev/dvd /media/dvd udf noauto,exec,users,ro 0 0
/dev/dvdrw /media/dvdrw udf noauto,exec,users,rw 0 0
/dev/sr0 /media/sr0 auto noauto,exec,users,ro 0 0
alastair@Dell-9300-antix1:~
`
Sadly this didn’t work. I can of course still mount it manually but sadly no auto function. I opted to put the mount point in /medai/alastair/ which is where other usb fat sticks are auto mounted.
You will have seen from the info in fstab about pluggable devices, which is why I went of on my earlier track. AFAIK the UUID for this stick is unique so another similar device will not work. Is that correct? Whatever the case, automount not yet working and I always get warning when I do mount the stick that it was not properly unmounted. UI assume this is just due to exfat.
Do you have any other edits I can try please?

[Member Xecure]

Helpful

Up

0

::

I remember that exfat automounted for me with automount enabled and fstab set up, but I also remember having to terminal mount often too. I will try to figure it out on the weekend if I can find a foolproof way. I have an unused small USB storage I will format to exfat and see what I can figure out.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member Budgie]

Helpful

Up

0

::

Xecure wrote:

I remember that exfat automounted for me with automount enabled and fstab set up, but I also remember having to terminal mount often too. I will try to figure it out on the weekend if I can find a foolproof way. I have an unused small USB storage I will format to exfat and see what I can figure out.

Hi and many thanks for looking into this but please, it is not critical so only if you have time.

It does appear there is a problem with exfat. I do not understand why a pluggable drive should be put in fstab, since fstab comment tells us it should be handled by uDev.

That said I did as you suggested and note that if I boot without the stick, as I would normally, I see that during boot there is an error immediately after loading the kernel module loop; I have

[....] Mounting local filesystems...mount: /media/alastair/big_stick: can't find UUID=64A5-F009
failed.

Which makes sense given the line I have added in fstab.

What is also interesting is that if I try and boot with the USB stick in, the boot fails and just stops.
I wonder how you get on with an exfat stick on your system.

Regards,
Budgie

[Author]

Posts