Problem mounting usb stick with ISO installed on it [SOLVED]

I'm experiencing a weird problem regarding mounting usb sticks. Archlinux stopped auto-mounting usb sticks on my machine, but only those that contains an operating system. Empty or data usb sticks mount without problem.
A few weeks or month ago, I don't remember exactly, still everything was all right, but due to updates(?) usb sticks won't auto mount any more.
I have two arch partitions none of them mount usb sticks anymore with operating systems on them.
Today, I wanted to test a new operating system and write it on my usb stick, and of course I couldn't because arch didn't mount it. Luckily, on my other partitions a few old distos are still installed – I don't use them anymore for years- I booted them up and they mounted the usb stick without problem; it seems only the up-to-date system have problem handling the usb sticks. I have two Arch system installed on two different partitions, Gnome 3 and Enlightenment, both system are up to date.
Here are some info:
[mak@myhost ~]$ dmesg | grep -E "sd[a-z]"
[ 1.369732] sd 2:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/111 GiB)
[ 1.369819] sd 2:0:0:0: [sda] Write Protect is off
[ 1.369821] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1.369872] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.369924] sd 3:0:0:0: [sdb] 625142448 512-byte logical blocks: (320 GB/298 GiB)
[ 1.369982] sd 3:0:0:0: [sdb] Write Protect is off
[ 1.369985] sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 1.370070] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.371642] sda: sda1 sda2 sda3 sda4 sda5 sda6
[ 1.372298] sd 2:0:0:0: [sda] Attached SCSI disk
[ 1.429438] sdb: sdb1 sdb2 sdb3 sdb4 sdb5 sdb6 sdb7 sdb8 sdb9
[ 1.430159] sd 3:0:0:0: [sdb] Attached SCSI disk
[ 2.244580] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
[ 2.348031] systemd[1]: Expecting device dev-sdb8.device...
[ 2.362842] EXT4-fs (sda5): re-mounted. Opts: discard,data=ordered
[ 3.358252] Adding 2097148k swap on /dev/sdb8. Priority:-1 extents:1 across:2097148k FS
[ 5.458907] EXT4-fs (sda5): re-mounted. Opts: discard,data=ordered,commit=0
[ 52.120360] sd 6:0:0:0: [sdc] 15679488 512-byte logical blocks: (8.02 GB/7.47 GiB)
[ 52.121310] sd 6:0:0:0: [sdc] Write Protect is off
[ 52.121319] sd 6:0:0:0: [sdc] Mode Sense: 43 00 00 00
[ 52.122191] sd 6:0:0:0: [sdc] No Caching mode page present
[ 52.122199] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[ 52.125825] sd 6:0:0:0: [sdc] No Caching mode page present
[ 52.125838] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[ 52.126999] sdc: sdc1 sdc2
[ 52.131071] sd 6:0:0:0: [sdc] No Caching mode page present
[ 52.131084] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[ 52.131093] sd 6:0:0:0: [sdc] Attached SCSI removable disk
[mak@myhost ~]$
[root@myhost mak]# fdisk -l
WARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion.
Disk /dev/sda: 120.0 GB, 120034123776 bytes, 234441648 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: gpt
# Start End Size Type Name
1 2048 18431 8M BIOS boot parti BIOS boot
2 18432 56641478 27G Linux filesyste sda2
3 56641536 113264582 27G Linux filesyste sda3
4 113264640 169887686 27G Linux filesyste sda4
5 169887744 226510790 27G Linux filesyste sda5
6 226510848 234441614 3.8G Linux filesyste Spare
WARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion.
Disk /dev/sdb: 320.1 GB, 320072933376 bytes, 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: gpt
# Start End Size Type Name
1 2048 18431 8M BIOS boot parti Bios boot
2 18432 54544383 26G Microsoft basic Partition 2
3 54544384 109070335 26G Linux filesyste Partition 3
4 109070336 163596287 26G Microsoft basic
5 163596288 218122239 26G EFI System Partition 5
6 218122240 272647630 26G Microsoft basic Partition 6
7 272648192 327174143 26G Linux filesyste Partition 7
8 327174144 331368447 2G Linux swap Swap
9 331368448 625142414 140.1G Linux filesyste Storage
Disk /dev/sdc: 8027 MB, 8027897856 bytes, 15679488 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x5fadc669
Device Boot Start End Blocks Id System
/dev/sdc1 * 0 4040703 2020352 0 Empty
/dev/sdc2 4036 38595 17280 ef EFI (FAT-12/16/32)
Disk /dev/sdc1: 2068 MB, 2068840448 bytes, 4040704 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x5fadc669
Device Boot Start End Blocks Id System
/dev/sdc1p1 * 0 4040703 2020352 0 Empty
/dev/sdc1p2 4036 38595 17280 ef EFI (FAT-12/16/32)
[root@myhost mak]#
[root@myhost mak]# blkid -o list -c /dev/null
device fs_type label mount point UUID
/dev/sda1 (not mounted)
/dev/sda2 ext4 (not mounted) 0a76a275-1798-495b-aa27-732626029de2
/dev/sda3 ext4 (not mounted) 0e9363ef-3791-409c-8db9-393385007689
/dev/sda4 ext4 (not mounted) 8f043c02-8b56-4689-a0ee-ed34ccc6f21f
/dev/sda5 ext4 / 82699b0e-8fe9-41e2-be13-65c798ed8a73
/dev/sda6 ext4 (not mounted) 3eaab6bf-2d05-4a7b-a6f7-8675e5f18723
/dev/sdb1 (not mounted)
/dev/sdb2 ext4 (not mounted) 17069311-9f14-4430-8298-be48194eb874
/dev/sdb3 ext4 (not mounted) 2e3b383d-3fa7-40df-b52d-c5d07caf252e
/dev/sdb4 ext4 (not mounted) 9d9b0656-d4ca-4efa-b6f8-1797bd4ead1f
/dev/sdb5 ext4 (not mounted) 05abf58a-ae6e-4377-9b3d-d6bacd92226d
/dev/sdb6 ext4 (not mounted) 8d7c6d55-dc47-471f-84f6-aae8864dfdd7
/dev/sdb7 ext4 (not mounted) b2155741-8f88-4063-bd1b-39b210004b17
/dev/sdb8 swap <swap> 97cf7cdf-299c-4e0d-a438-c8b79766699c
/dev/sdb9 ext4 (not mounted) 426648fd-98f5-4fb0-9114-bdbdfea9047c
/dev/sdc1 udf Sabayon GNOME (not mounted) 2013-07-29-13-08-13-27
/dev/sdc2 vfat (not mounted) CF68-C2B6
[root@myhost mak]#
Thanks for the help.
jmak
Last edited by jmak (2013-08-14 00:12:54)

cfr wrote:
What is sdc1p? Is that another USB stick? It seems to have an equally weird partition map.
By the way, you can't create an Arch USB bootable in EFI mode with dd. Obviously don't know about sabayon.
EDIT: Did you dd to the disk or to a partition? What command exactly did you use? Because it almost looks as if you did something like dd once and create one thing and then dd over the top of one of the partition so you've got a partition which itself has a partition map. Not sure that's possible but it sure looks weird.
I would wipe the key and start over.
I don't know what is that. It is a partition on the same usb stick, it was the “dd” that made that partition automatically, I guess. When I burn images into usb, I always use this command:
# dd bs=4M if=/path/to/archlinux.iso of=/dev/sdx && sync
I used this when burned Sabayon and it works perfectly.
The problem is that Arch can't auto-mount its own installation usb either. I put the arch install usb in and I get the following output:
[root@myhost mak]# blkid -o list -c /dev/null
device fs_type label mount point UUID
/dev/sda1 (not mounted)
/dev/sda2 ext4 (not mounted) 0a76a275-1798-495b-aa27-732626029de2
/dev/sda3 ext4 (not mounted) 0e9363ef-3791-409c-8db9-393385007689
/dev/sda4 ext4 (not mounted) 8f043c02-8b56-4689-a0ee-ed34ccc6f21f
/dev/sda5 ext4 / 82699b0e-8fe9-41e2-be13-65c798ed8a73
/dev/sda6 ext4 (not mounted) 3eaab6bf-2d05-4a7b-a6f7-8675e5f18723
/dev/sdb1 (not mounted)
/dev/sdb2 ext4 (not mounted) 17069311-9f14-4430-8298-be48194eb874
/dev/sdb3 ext4 (not mounted) 2e3b383d-3fa7-40df-b52d-c5d07caf252e
/dev/sdb4 ext4 (not mounted) 9d9b0656-d4ca-4efa-b6f8-1797bd4ead1f
/dev/sdb5 ext4 (not mounted) 05abf58a-ae6e-4377-9b3d-d6bacd92226d
/dev/sdb6 ext4 (not mounted) 8d7c6d55-dc47-471f-84f6-aae8864dfdd7
/dev/sdb7 ext4 (not mounted) b2155741-8f88-4063-bd1b-39b210004b17
/dev/sdb8 swap <swap> 97cf7cdf-299c-4e0d-a438-c8b79766699c
/dev/sdb9 ext4 /run/media/mak/426648fd-98f5-4fb0-9114-bdbdfea9047c 426648fd-98f5-4fb0-9114-bdbdfea9047c
/dev/sdc1 iso9660 ARCH_201305 (not mounted) 2013-05-01-07-12-33-00
[root@myhost mak]#
It doesn't appear in nautilus side panel.
Last edited by jmak (2013-08-13 02:44:45)

Similar Messages

Hi i bought a new 500gb hard drive on my 2011 macbook pro, it is a blank hardrive and i forgot to save my other files on an external hard drive , i have a usb stick with mavericks installed on it. can i just go ahead and do a straight install by using it?

hi i have a macbook pro 2011 model, i decided to upgrade my hardrive and bought a 500gb blank hardrive, my query is because i wasnt able to save most of my files and my operating system to an external hard drive, i have a usb stick with a mavericks os installed on it. will i be able to do a straight install by just doing this method? i will be grateful for any tips or help u might offer, thanks.

Is it just bootable or does it have the Mavericks installation files on it? If so, yes. If not, no. You might consider getting an external enclosure. Put your old drive in it and boot to its Recovery partition. You can install from there. As a matter of fact, you can run Migration Assistant and get all your stuff over too.
http://www.amazon.com/Sabrent-2-5-Inch-Aluminum-Enclosure-EC-TB4P/dp/B005EIGUD4/ ref=sr_1_3?ie=UTF8&qid=1396656137&sr=8-3&keywords=2.5+enclosure

Cant mount usb sticks with fat32 ISO-8859-1 2.6.31-ARCH

when trying to mount my usb sticks from xfce4 desktop(halmount).
Following error occurs (as told by dmesg).
FAT: IO charset ISO-8859-1 not found
First i suspected hal being the culprit but now im not so sure anymore.
im using stock 2.6.31-ARCH.
when i checked the .config for the stock kernel CONFIG_NLS_ISO8859_1=y is enabled in the kernelconfig, and also everything below to support fat32.
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_NTFS_FS=m
but when i list the modules nls_iso8859-1.ko is missing.
#~ls -a /lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso*
/lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-13.ko
/lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-14.ko
/lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-15.ko
/lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-2.ko
/lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-3.ko
/lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-4.ko
/lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-5.ko
/lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-6.ko
/lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-7.ko
/lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-9.ko
So i suspect the newest kernel broke mounting with hal.
Last edited by nichlas.johansson (2009-10-17 14:25:56)

Based on the information given in http://bbs.archlinux.org/viewtopic.php?id=82176, I changed in /etc/rc.conf from LOCALE=en_GB.iso88591 to LOCALE=en_GB.utf8, uncommented en_GB.UTF-8 UTF-8 in /etc/locale.gen, issued # locale-gen and after a reboot, I was able to mount my usb sticks again.
However, now I get "FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!" in dmesg. Is this something, I need to worry about...?
Last edited by smurf (2009-10-19 08:29:15)

Problems mounting USB drives

I am having some problems getting USB flash drives to (auto) mount on my system.
In the past, when I plugged in the device (a simple USB flash drive), it showed up in Thunar and I could click on it to mount it. Now nothing shows up in thunar when I plug in the device. dmesg shows the following, so I know the device is being recognized:
usb 2-2: new high speed USB device using ehci_hcd and address 14
but it isn't being assigned to /dev/sd*. fdisk -l also doesn't show the device. lsusb shows the following for the device:
Bus 002 Device 014: ID 0781:b6b7 SanDisk Corp.
I added a udev rule to automount in /media, as per the udev wiki instructions, but that didn't do anything. Installing udisks and udiskie was similarly unhelpful. I tried this with multiple USB drives (which I both confirmed were working on other machines) so it doesn't seem to be a HW problem.
Thanks in advance.

You might try reformatting the usb drive using Disk Utility. Use MacOS Extended(Journaled). That might help.
lenn

Auto Mounting USB sticks

So, I've looked around a lot, but I can't find much at all about mounting my usb sticks whenever they're plugged in. It'd be nice to not have to # mount /dev/sde1 /home/droid/usb
I've set it up as the wiki says to do so with Thunar, but it's still not working. Any help?

As jasonwryan mentioned the wiki is your friend. If you are trying to automount volumes with thunar make sure to install thunar-volman:
pacman -S thunar thunar-volman
Then you must configure thunar to automount your thumbdrive(s):
From the wiki https://wiki.archlinux.org/index.php/Th … tomounting
Configuration
It can also be configured to execute certain actions when cameras and audio players are connected. After installing the plugin:
1. Launch Thunar and go to Edit -> Preferences
2. Under the 'Advanced' tab, check 'Enable Volume Management'
3. Click configure and check the following items:
Mount removable drives when hot-plugged.
Mount removable media when inserted.
also add dbus-launch to your .xinitrc making sure it comes before your windows manager/desktop environment
for example my .xinitrc contains:
exec dbus-launch openbox-session
Granted there are numerous different ways to automount usb drives, but based on your post I assume that this is the method you are trying to use.
Last edited by Gr0t92 (2013-05-16 05:20:36)

No GRUB menu when booting from USB stick with new archlinux

Hi,
I want to try archlinux but I do not have a full backup of my current system right now, such that I do not dare to install archlinux on it. I decided to install it on a USB drive and followed the Beginners Guide considering the hints for installations on USB sticks.
The first issue that I had was that I was not able to to install gurb and it complained that no boot partition was available. I started from scratch again but this time choose the partition type EF02 (bios boot partition) instead of the default 0700 (I only have one partition on the stick). This time everything went fine until I rebooted from the USB stick. Instead of a grub menu I got:
GRUB GRUB GRUB GRUB GRUB GRUB
and nothing happened.
I booted again from the boot cd with archlinux and did the following to examine the grub installation again:
mount /dev/sdb1 /mnt
arch-chroot /mnt /bin/bash
grub-install --recheck --boot-directory=/boot /dev/sdb
>Installation finished. No error reported.
grub-mkconfig -o /boot/grub/grub.cfg
>Generating grub.cfg
>Found linux image: /boot/vmlinux-linux
>Found linux image: /boot/initramfs-linux.img
> WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning.
> No volume groups found
>Found LMDE MATE Edition (1) on /dev/sda1
>done
I don't know what the grub-mkconfig output should look like...
Do you have any idea how I can fix this?
Thanks in advance!

Welcome to Arch!
EF02 is definitely not the type code you want. That is used for a small partition with no file system which grub needs on GPT disks because it cannot fit into the space on disk. You don't install anything into it and it is 1-2MB.
Perhaps https://wiki.archlinux.org/index.php/Usb_installation would help?

[SOLVED] xfce4 automounting problem on usb dev with utf8 encoded files

I have problem of auto mounting usb external drive contains utf8 encoded files under xfce4.
Using hal and dbus for usb device detection.
Heard that I need to add iocharset=utf8 under fstab or hal fdi configure files and tried them all but didn't work
usb devices with vfat always got mounted with default charset.
I found out that exo-mount is the one doing the actual mounting and that it is the one that cannot take all extra mounting options such as iocharset etc.
Have tried gnome to mount this hard drive and works find with nautilus option that let me set various mount options for each harddrive.
Is there any way to replace exo-mount with some other alternative mounting tools that work with thunar?
Any workaround will be helpful as long as I can mount my usb drives with prefer charset so that I don't have to guess all ???marked files.
Heard that xubuntu replaced that exo-mount with gnome-mount to handle drives with extra mount options such as iocharset.
but I am pretty new to configuring things and couldn't find the step by step instruction for this so please provide the complete solution.
Link to the pages that explain workaround would be nice as well.
Thanks in advance!
Last edited by axca (2007-10-17 18:24:50)

Found the patch for exo-mount so that it takes additional mount options HAL suggests.
https://bugzilla.altlinux.org/attachmen … ction=diff
Now my usb drive can be mounted with the proper charset.
Hope this patch helps others with similar situation as well!
Last edited by axca (2007-10-15 15:41:47)

[SOLVED] How to automatically mount USB drives with custom mount point

edit:
Original title was : 'Unable to mount USB disk via /etc/rc.local', but got changed since the /etc/rc.local problem isn't relevant for me anymore.
Hello,
Since I am new to this forum, I'll start off with this :
Thanks to archlinux, its founder and all its contributors, cause this is the operating system (flavour) that annoys me the least.
The root problem :
I want to automount USB storage devices to other places than /media/ and without the need for programs that depend on gnome and the like. As I tried some stuff with hald and such, I didn't really get to a nice and easy to configure solution. Any hints in that direction are always welcome.
For now, automount of known USB storages devices during boot, will do.
So the things I tried and didnt work :
1.
Provide the disk info to /etc/fstab (via the disks UUID and 'auto' filesystem)
Add 'mount /mountpoint' to /etc/rc.local
Result : the mount command in rc.local says '... specify filesystem'
However, after boot, running /etc/rc.local mounts the USB disks correctly.
2.
Provide the disk info to /etc/fstab (via the disks UUID and the correct filesystem)
Add 'mount /mountpoint' to /etc/rc.local
Result : pc doesn't get through boot process and gives me the 'ctrl-d to reboot or root passwd for maintenance'
3.
Provide no disk info in /etc/fstab
Add the full mount line to /etc/rc.local (mount -t fs /dev/disks/by-uuid/MyUUID /MyMountpoint )
Result : don't remember the output of the mount execution, but well, it didn't mount
However, after boot, running /etc/rc.local mounts the USB disks correctly.
Is there something that isn't loaded at the time of rc.local execution that I need for mounting of USB devices ? Or why else is this failing ?
Regards,
BasiK
Last edited by BasiK (2009-08-28 07:22:50)

Thanks for the hint hunterthomson, but the pc I will be using it on, is an own-built HTPC/home file server, so there is no way I want to use a graphical file manager to get the usb disks mounted.
I tried to figure out a little about udev rules, and I got to do what I wanted to do, so thx for pointing me in that direction Mr.Elendig.
Btw, I am indeed also using auto-sleep/park disks, but this udev way works perfectly.
I added two rules files to /etc/udev/rules.d/ :
The first for a known usb disk (with its volume uuid), with a named mountpoint under my media dir /symbiosis/ :
[basik@plox ~]$ cat /etc/udev/rules.d/80-usb-utopia.rules
ACTION=="add", KERNEL=="sd[b-z][0-9]", ENV{ID_FS_UUID}=="a59332c2-07ba-4c52-afb5-20e361bdf71a",SYMLINK+="usb-%n", GROUP="storage", NAME="%k"
ACTION=="add", KERNEL=="sd[b-z][0-9]", ENV{ID_FS_UUID}=="a59332c2-07ba-4c52-afb5-20e361bdf71a",RUN+="/bin/mkdir -p /symbiosis/utopia"
ACTION=="add", KERNEL=="sd[b-z][0-9]", ENV{ID_FS_UUID}=="a59332c2-07ba-4c52-afb5-20e361bdf71a", RUN+="/bin/mount -t auto -o rw,noauto,sync,dirsync,noexec,nodev,noatime /dev/%k /symbiosis/utopia", OPTIONS="last_rule"
ACTION=="remove", KERNEL=="sd[b-z][0-9]", ENV{ID_FS_UUID}=="a59332c2-07ba-4c52-afb5-20e361bdf71a", RUN+="/bin/umount -l /symbiosis/utopia", OPTIONS="last_rule"
The second for unknown usb disks, to mount under the same dir. This is simply taken from the archwiki http://wiki.archlinux.org/index.php/Ude … .26_Tricks
Make sure these rules are executed after the ones for specific usb disks.
[basik@plox ~]$ cat /etc/udev/rules.d/usb-disks.rules
KERNEL=="sd[a-z]", NAME="%k", SYMLINK+="usb%m", GROUP="storage", OPTIONS="last_rule"
ACTION=="add", KERNEL=="sd[a-z][0-9]", SYMLINK+="usb%n", GROUP="storage", NAME="%k"
ACTION=="add", KERNEL=="sd[a-z][0-9]", RUN+="/bin/mkdir -p /symbiosis/usb%n"
ACTION=="add", KERNEL=="sd[a-z][0-9]", RUN+="/bin/mount -t auto -o rw,noauto,sync,dirsync,noexec,nodev,noatime /dev/%k /symbiosis/usb%n", OPTIONS="last_rule"
ACTION=="remove", KERNEL=="sd[a-z][0-9]", RUN+="/bin/umount -l /symbiosis/usb%n"
ACTION=="remove", KERNEL=="sd[a-z][0-9]", RUN+="/bin/rmdir /symbiosis/usb%n", OPTIONS="last_rule"
These may not be the nicest looking udev rules, but it works for what I wanted to do with it.

HAL won't mount USB storage with "flush" option.

Trying to mount a 8G vfat USB stick automatically with HAL that using "flush" option to decrease the flushing time when unmounting it.
And I've consulted the wiki HAL entry and wrote this:
<match key="block.is_volume" bool="true">
<match key="@block.storage_device:storage.hotpluggable" bool="true">
<merge key="volume.policy.mount_option.flush" type="bool">true</merge>
</match>
<match key="@block.storage_device:storage.removable" bool="true">
<merge key="volume.policy.mount_option.flush" type="bool">true</merge>
</match>
</match>
put it in /usr/PolicyKit/PolicyKit.conf, and restart HAL.
But it's still not working. Can anyone tell me where I do wrong?

ok, thank you.
I've been putting my setting into /etc/hal/fdi/policy/20-usbvfat.fdi
Here's its content:
<?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2">
<device>

<match key="volume.fstype" string="vfat">
<merge key="volume.policy.mount_option.utf8" type="bool">true</merge>
</match>
<match key="storage.hotpluggable" bool="true">
<merge key="volume.policy.mount_option.flush" type="bool">true</merge>
</match>
<match key="storage.removable" bool="true">
<merge key="volume.policy.mount_option.flush" type="bool">true</merge>
</match>
<match key="@block.storage_device:storage.hotpluggable" bool="true">
<merge key="volume.policy.mount_option.flush" type="bool">true</merge>
</match>
<match key="@block.storage_device:storage.removable" bool="true">
<merge key="volume.policy.mount_option.flush" type="bool">true</merge>
</match>
</device>
</deviceinfo>
(with every possible syntaxs i can find)
The fact is that I've tried putting them under /etc/hal/... and /usr/share/hal...
But none of them really work, I doubt if HAL is really reading this file or it has changed its variable names (idk...)

Booting from an USB stick with an old BIOS using a boot CD

Hi
I use larch to build a customized live-usb system, and I'm pretty happy with it.
The problem is that I can't boot it on some old computers, with a BIOS that :
Doesn't support booting from USB devices
Doesn't support accessing USB devices
This mean, that, when using a CD with GRUB, the USB stick cannot be seen by GRUB.
That issue is discussed in the Ubuntu help : https://help.ubuntu.com/community/BootFromUSB
As you can see, I have problem #2, so my option is to use Linux USB drivers to boot from the stick.
kernel /boot/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper noprompt cdrom-detect/try-usb=true persistent
The only problem is that, this seems to be Ubuntu-specific, and I don't know how to do that in Arch Linux : do I need a custom kernel or something ?
I tried searching for "cdrom-detect" in the Linux Kernel Documentation, without success.
Thanks
Last edited by mickael9 (2010-09-29 20:08:53)

I use Plop bootmanager to boot from usb cause my PC cant boot from usb because of BIOS
http://www.plop.at/en/bootmanager.html
I actually use a older version that seems to work better than newer one
link to mine> http://multidistro.com/downloads/plpbt
grub legacy entry
title Plop
root (hdx,x)
kernel /boot/plpbt
grub2
menuentry "Plop" {
set root='(hd0,1)'
search --no-floppy --fs-uuid --set e6adb195-3201-42f0-b6d6-f175abe1912c
linux16 /boot/plpbt
see if that works

I want to put photos on my ipad from a usb stick (with a connector)

When I put the 8GB usb stick into the ipad (through a connector) I get the message
Cannot use device.
The connected USB device requires too much power.
I am trying to load some photos on the ipad.
Thanks

I have 3 USB thumb drives. One, the oldest, causes the too much power msg. Buy a new one.
Plug the USB flash drive into your computer & create a new folder titled DCIM. Then put your movie/photo files into the folder. The files must have a filename with exactly 8 characters long (no spaces) plus the file extension (i.e., my-movie.mov; DSCN0164.jpg).
Now plug the flash drive into the iPad using the camera connection kit. Open the Photos app, the movie/photo files should appear & you can import. (You can not export using the camera connection kit.)
Secrets of the iPad Camera Connection Kit
http://howto.cnet.com/8301-11310_39-57401068-285/secrets-of-the-ipad-camera-conn ection-kit/
 Cheers, Tom

Mount USB stick on an ASA 5505?

Hello,
I have an ASA 5505 and the built in flash is pretty small and I need to put 3 .pkg on it for Anyconnect 4.
I formated an USB Stick (4GB) to FAT32 and put in the USB Port 2 on the back and rebooted the firewall.
But in the filemanager I see disk0 and disk1, but disk1 does not work, doesn't list anything and I can't create folders on it.
Can I mount the USB stick manually or something?
Kind Regards.

The USB port on the 5505 is not a supported file storage location.
On the newer 5500-X series (including the 5506-X) you can do that.

Can I download FF to a USB stick, and then install it on another computer that is NOT connected to the Internet?

I want to download FF at home where I have a broadband internet connection, then take the required data on a USB stick to a friend who uses an old computer (w2k OS) and only a 56 k modem and install FF on his computer. Is it possible?

That shouldn't be an issue. You could test it if you like by killing your internet connection and installing it locally.

Download Adobe Reader to a USB stick and then install it to a computer

HOW CAN I DO THAT????

Hi william george dunbar,
Please download the installation file of Adobe Reader XI from the link below:
http://get.adobe.com/reader/enterprise/
Once you download the installation file, you can copy the file to USB stick and install it on any computer.

[SOLVED] Mounted USB stick immediately unmounts itself - why?

Hi all,
I thought I was unable to mount a USB stick, however it does actually mount but then it gets immediately unmounted by something:
# mount /dev/sdd1 /mnt
# ls /mnt
<empty folder>
# umount /mnt
umount: /mnt: not mounted
# mount /dev/sdd1 /mnt && ls /mnt
<contents of USB stick>
# ls /mnt
<empty folder>
Somehow the USB stick is getting automatically *unmounted* almost immediately after I mount it!
I don't have any automounts enabled, so I'm not sure why this would happen. If I make a different folder (e.g. /root/test) and mount it there then it sticks, it is only the /mnt folder that gets automatically unmounted.
Any idea what's going on? I've never seen this happen before, and last time I tried this (a week or two ago) it worked fine.
Last edited by Malvineous (2015-03-15 01:15:16)

brebs wrote:Use "mount -v" (i.e. "verbose") to get some feedback - it's most likely not being mounted.
Like I said in my first post, if you run "ls" immediately after the mount then you can see the contents of the USB stick, so it's definitely getting mounted, but waiting only a few hundred milliseconds after the mount reveals it has been unmounted again. What is causing the unmount is unknown.
brebs wrote:
Immediately after running that mount command, run:
echo $?
To see the return code. It should be 0.
Yes it is zero, because the mount command succeeds. "ls" wouldn't be able to list the files on the USB stick if the mount failed. It is something else that is unmounting the folder mere milliseconds after it is successfully mounted, but I don't know where else to look to find out what it could be.
brebs wrote:Also, mounting to /mnt is very weird - you should be mounting a directory *inside* /mnt.
I am mounting inside /mnt, I just used /mnt as an example to keep things simple.
Vain wrote:
I made the same “mistake”. Try running “systemctl status mnt.mount” and see which device the output refers to. For me, it still listed the old device name. Hence, when you mount it, systemd tries to find the (old) device—which it can’t—and thus unmounts your device immediately.
I was too lazy/annoyed to find out how to solve this properly. I rebooted my system.
Interesting idea! Unfortunately I have nothing listed for this particular mount point. The only *.mount services on my system are the ones that are mounted at boot (e.g. srv.mount for /srv). I have the "noauto" option against this mount point in fstab (as USB sticks aren't normally attached to my system when I boot) so sensibly enough I don't seem to have a mount service running for this particular mount point.

Problem mounting usb stick with ISO installed on it [SOLVED]

Similar Messages

Maybe you are looking for