Hot answers tagged usb
4
'live' watching can be done via udevadm:
udevadm monitor --subsystem-match=usb --property
or
udevadm monitor --subsystem-match=usb --property --udev
to filter only udev events. If you want to grep for a particular property you will have to un-buffer udevadm output (with tools like stdbuf, script, unbuffer...):
stdbuf -i 0 -o 0 -e 0 udevadm monitor ...
4
Writing to the device (/dev/sdX) instead of to a file system (/mount/point) deletes the file system on the device anyway so there's no need for mkfs before.
There is also no need to erase data in the non-written area. It is not visible anyway. Linux file systems can without problems be smaller than the block device they live on.
3
What I do is to store tarballs on the USB drive (formatted as VFAT). I'm wary of reformatting USB drives, they are build/optimized for VFAT so to level wear, and I'm afraid it will die much sooner with other filesystems. Besides, formatting another way will make it useless for ThatOtherSystem...
2
"It's not a bug, it's feature..."
It would be quite evil if every unprivileged user could write to every Linux file system just because he feels entitled to. You must explicitely allow him to. After creating a file system only root is allowed to.
# You (as root) can either give write write access to everyone:
chmod 777 /mount/point
# or you give the whole ...
2
All my USB hubs worked without a hitch, always. Yes, I've had broken(ish) USB ports that don't work right.
Make sure the devices don't draw too much power, the power a USB device is allowed to draw is limited (that's why many hubs have two connectors, as do USB disk drives), if you try to draw more from the hub than what it is able to get from the PC, ...
2
This information appears in the kernel logs — typically in /var/log/kern.log, or /var/log/syslog, or some other file (it depends on your syslog configuration, different distributions have different defaults).
If you'd like something pre-filtered, you can add an udev rule. Create a file /etc/udev/rules.d/tkk-log-usb.rules containing something like:
...
2
I found this answer to work great on my Gentoo system. Please also remember to re-enable your device if it's an important piece of your system (e.g. mouse or keyboard).
sudo sh -c 'AUTHFILE="/sys/bus/usb/devices/5-2/authorized" ; echo 0 > "$AUTHFILE" ; sleep 1 ; echo 1 > "$AUTHFILE"'
To see what you're disabling/re-enabling:
cat ...
2
You can use cmp for checking if everything was copied fine:
$ cmp -n `stat -c '%s' debian-X-netinst.iso` debian-X-netinst.iso /dev/sdX
This solution does not explicitly compute the checksum of your /dev/sdX - but you don't need to to that because you have already done this for the source of the comparison (i.e. debian-X-netinst.iso).
Doing just a dd ...
1
I realize this is a Unix & Linux site but if you have access to a PC I'd try out some of the tips from this site:
http://www.rmprepusb.com/tutorials/54---how-to-fix-write-protected-disks.
There is a tool listed on that site called RMPrepUSB, which has worked in past as well, YMMV. Here's a screenshot of that tool:
I've ...
1
The lack of the cp210x.ko and usbserial.ko kernel modules in the directory:
/lib/modules/`uname -r`/kernel/drivers/usb/serial/
would seem to indicate that the kernels provided with the ChrUbuntu releases were built not having these features enabled at compile time.
Comparing the output that's provided in the question by the OP against Ubuntu 12.10 would ...
1
This is the behavior I have on my Ubuntu Lucid system:
When I plug in my USB flash/thumbdrive which has two partitions, the system reports:
$ ls /dev/sdb*
/dev/sdb /dev/sdb1 /dev/sdb2
$ udisks --show-info /dev/sdb | grep -A2 'partition table\|by-id'
by-id: /dev/disk/by-id/usb-takeMS_USB_Mini_AA07013000010057-0:0
by-path: ...
Only top voted, non community-wiki answers of a minimum length are eligible
