Hot answers tagged usb-drive
11
Suppose your usb drive is mounted to /media/usb then it would be sufficient to do
sudo umount /media/usb
Suppose the your usb is /dev/sdb1 then you could also do
sudo umount /dev/sdb1
You may also have a look at the anwers of one of my questions, how to umount all attached usb devices with a single command: Umount all attached usb disks with a single ...
9
It is sometimes possible to do a power cycle on branch of the USB bus where the device is plugged :
# echo suspend > /sys/bus/usb/devices/1-1/power/level
# echo auto > /sys/bus/usb/devices/1-1/power/level
The 1-1 should be adjusted to your configuration. You can see to which part of the USB tree your device is plugged by running lsusb -t before ...
9
Yes, this can occur if your device is formatted with a filesystem that does not support that kind of permission setting, such as VFAT. In those cases, the umask is made up on the fly from a setting in the fstab (or the hotplugging equivalent).
See, most probably, man mount for details. For example, for VFAT, we find:
Mount options for fat
...
6
qemu-kvm -hdb <device>, where <device> is the USB stick (e.g. /dev/sdb), should do it (tested with Ubuntu 12.04 on an USB stick and it works).
You will need write permission to the device (i.e. be root or change its permissions).
5
Following method works with CentOS 6.2:
Requirements: USB flash drive (at least 4 GB, I used a 16 GB one)
Download an ISO image from a mirror - I chose the full 1st DVD image to avoid a network install (because it is not clear if the cryptographic package signatures are checked by the installer or not), e.g.:
$ wget ...
5
When you mount a partition, it will show in df -h, and if you umount it, then it will no longer show in df -h
fdisk -l uses /proc/partitions and prints out all partitions which are physically connected, but your USB drive is still connected to your PC. When you unplug it, then it will not show in fdisk -l anymore, and you can also check cat ...
4
I would suggest that your drive experienced some kind of hardware failure. The problem isn't the partitions, the problem was encountered when the drive decided to die on you. The original errors you saw during install were probably it failing to write because the disk failed to respond correctly to commands.
You can try putting it in a different machine ...
4
Unfortunately it seems that you've just killed your pendrive while trying to install a normal* distro onto it. (See wikipedia on why this is a bad idea.)
If there is any chance of bringing your pendrive back to life, it would involve destroying current partitioning. You can try doing that using dd. dd if=/dev/zero of=/dev/sdc bs=4096 count=100 should be ...
3
The mount command has two related options:
sync All I/O to the filesystem should be done synchronously.
dirsync All directory updates within the filesystem should be done synchronously.
You can specify them in the mount command's -o option:
mount -o sync /mnt/flashdrive
Or in your /etc/fstab's fourth column:
/dev/sdb1 /mnt/flashdrive ...
3
You seem to forget to unmount the pen drive before unplugging. The data is being written at hte time when you're physically detaching the drive; this results in a corruption.
In Nautilus, locate the drive in the left panel, click the eject button near its name. Alternatively, find it on the desktop, right-click, choose 'Eject'.
This is the same thing as ...
3
There are several possible causes and things that you might do. The dmesg excerpt suggests a few things:
The kernel tries several times to access the device. It seems that each time it does not finish for some reason.
There are notices saying not ready after error recovery which indicate that the drive either failed to undergo filesystem checks (although ...
3
Ok, so if it satisfies you to have the old pendrive work as the second one, here's how you can do it:
Back-up the contents of the old pendrive.
Once you have both pendrives attached and your system running, re-partition the old pendrive in similar manner to how the second one is partition - that is to say, make the /boot partition on the old one have the ...
3
Well you can connect up to 127 devices (including hubs) to each USB controller so the answer will partly depend on whether those two USB 2.0 ports are on the same controller or on different controllers.
Overall the answer is probably several hundred anyway, not that I would recommend that as you'll be sharing the limited amount of I/O that is available ...
3
Reset the device, or the hub it is connected to, and the device should reappear. Here is a small program to do that:
http://marc.info/?l=linux-usb-users&m=116827193506484
It works for most USB drives I've tried, but there are exceptions, like my Kingston DT 101 II 4GB, which fails INQUIRY and READ CAPACITY commands after reset, and remains unusable ...
3
USB drives have a chipset that converts USB mass-storage-device commands to IDE or SATA commands, which the drive then receives. Cheap chipsets (which are the majority, I imagine) don't pass on commands correctly to the drive that aren't directly related to reading or writing data from the drive. You are kind of at the mercy of that hardware with USB ...
3
From my experience in Ubuntu, when you "eject" a USB stick from within Nautilus, the device actually disappears from the system. I'm not sure why this is, but neither Nautilus nor the command line can get it back. I guess the logic is that once you eject a USB stick you don't want it back, but are going to disconnect it.
The way I work around this (when ...
3
There is also the possibility, that any malware install itself in the MBR/VBR boot sectors of the drive. From there it could be executed automatically if booting from USB storage devices is enabled.
As soon as the malware runs, it could install nasty root/bootkits.
To clean the MBR of the usb drive from any malware, install a new one.
And remove any ...
3
Was the name of the device U167CONTROLLER before?
It may be that the microcontroller on the device has encountered some abnormal condition (totally possible with less than totally reputable manufacturers) and needs to be reprogrammed. This is a bit of a black art and it's likely you will only find Windows programs that can reprogram the microcontroller.
...
3
Before you do anything to the USB-stick, you should make an image of it:
dd bs=4k of=stick.img if=/dev/disk/by-id/usb-JetFlash_Transcend_4GB_QTMFKJQQ-0\:0
Then you put your stick safely away and use the stick.img file to do your fiddling, instead of destroying more data.
Are there important files on it? Check http://www.cgsecurity.org/wiki/PhotoRec for ...
3
It's very doubtful that Ubuntu's beta status has anything to do with your drive issues.
Your drive is having difficulties, but there's no way to know for sure if the problems are fatal based on your log output. These are the relevant lines indicating trouble:
Mar 31 22:26:06 talk kernel: [13354.939177] end_request: I/O error, dev sdb, sector 488459069
Mar ...
3
I don't know why exactly, but Renan's answer didn't quite work for me. KVM said to me it couldn't find a bootable drive (despite the usb partition being marked as such).
However I've found another solution. Get the USB device VendorID:ProductID with lsusb. Example:
$ lsusb
...
Bus 002 Device 007: ID 0781:5406 SanDisk Corp. Cruzer Micro U3
Pass that to ...
3
Try adding -d sat, -d usbcypress, -d usbjmicron, -d usbsunplus to your smartctl command line, to use a transfer format that can pass through the USB-SATA bridge chip.
You can also try connecting it to a USB 2.0 hub / port, which may cause the bridge to behave differently in regards to ATA passthrough.
If none of those work, you can always just remove the ...
3
You can use chainloading, altough you have to specify the boot record (ie. partition or drive) to boot to.
menuentry "Another bootloader" {
set root=(hd1,0)
chainloader +1
}
Should work for (hd1) too, if you want to use MBR. I hope you know how are the devices enumerated in GRUB, that's the only trouble here. If you want to test it first, you can ...
3
As others have commented I don't believe this is possible in runlevel3. The application in question under GNOME 2.x is called gnome-volume-manager. You can reconfigure it a bit using gnome-volume-properties.
screenshot
Given you're in runlevel 3 I don't believe this is an option. You ...
2
Do you have an image file for the suse install you want? Usually the process is:
Get install disk image, from http://en.opensuse.org/
Extract that image onto a USB drive (Izarc/7-zip wll do (in windows), or double click on the file in linux/unix. Or mount as a loopback and copypaste.)
Use a tool such as unetbootin or mkboot.bat (windows only) to make the ...
2
If your BIOS supports 'boot from usb' as an option in the boot loader (cd, hdd, net, floppy etc).
You can create an bootable image on a usb drive. I've done so with Debian, but here is a howto for OpenSUSE I pulled from a search result that should apply to you.
http://en.opensuse.org/SDB:Live_USB_stick
Once you have your image on the usb (note that it ...
2
Per Aki's comment, check the boot priority set in your BIOS. Note that there may be various USB boot options, but likely you need USB HDD or similar.
A better overall alternative, assuming you have space on your internal hard disk, might be to setup your Windows XP as a Virtual machine host running VirtualBox.
2
Check your BIOS settings, make the boot priority look like this:
CDROM
USB
Internal drive
Then if your USB is not connected it will boot from the internal drive. It's then up to your system to detect both drives, the only problem you can run into is the filesystem compatibility: accessing ext3 or whatever FS Fedora uses from Windows. Accessing Windows ...
2
Open a terminal
steve@mcr-pc-29334:~$ sudo fdisk /dev/sdb
WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
switch off the mode (command 'c') and change display units to
sectors (command 'u').
Command (m for help): d
Selected partition 1
Command (m for help): w
The partition table has been ...
2
I've fixed this now.
Firstly, I didn't install squeeze with the default GNOME desktop environment. I mis-remembered. What I did was install the base system, and then install the gnome-desktop-environment package, aiming for a lighter/closer-to-upstream set of packages.
Now, completely unscientifically, I did two things in one go to fix this, so I don't ...
Only top voted, non community-wiki answers of a minimum length are eligible
