[solved}Permanent USB boot and new udev?

I'm always booting from an usb stick on my netbook and the new udev seems to create problems in some cases. A real problem in my case would be that udev makes my usb stick not to be found and the netbook unbootable. However, the stick is fully represented in fstab;
UUID=52523bb8-e3fb-40c7-93a5-afe47fb62a91 /boot ext2 defaults,noatime,nodiratime 0 1
UUID=827d9502-aa52-4989-ba55-2afd2a0ed377 /home ext4 defaults,noatime,nodiratime,commit=60 0 1
UUID=b0ab0cc0-9ab9-4b8b-967d-871788b9f4ab / ext4 defaults,nodiratime,noatime,commit=55 0 1
UUID=cd38656a-f2bb-45c3-a23d-6e0d7c09bbb3 swap swap defaults 0 0
I suspect it's ok to update udev but if it's not i'd like some advice to make a fix beforehand.
EDIT: update worked out OK.
Last edited by swanson (2011-10-26 07:06:30)

Yeah, classic error. "LiLi" was mentioned in the wiki, except that someone decided to remove the information...
https://wiki.archlinux.org/index.php?ti … did=251979
The complete version can be found on the History page, just before the lines were removed:
https://wiki.archlinux.org/index.php?ti … SB_Creator
LiLi changes the label of the USB to MYLINUXLIVE by default but the file archiso-x86_64.conf tell linux to look for installation media named with the month and release date of the file, eg: ARCH_201302 Hence the famous 30 second error.
Anyway, welcome to the forum! Don't forget to mark the topic as solved (by editing the first post) so that other people (including yourself sometimes) may find useful.
Last edited by DSpider (2013-06-25 19:28:59)

Similar Messages

P35 Neo Questions about USB boot speed (New query)

i see it's an old topic but i have the same problem with slow USB Boot on a MSI P35 Neo2-FR mainboard.
i have tried something like 5 different USB drives and all are the same. the problem is when it's tring to boot from USB. there is some missing support for USB booting from BIOS , i don't know.
i had a BIOS from 2008 and i have updated to the latest version but nothing solved my problem.
i have tried to boot from USB with a linux live environment, windows live CD or i have tried to install windows from USB drive. all of them with very slow reading (instead of max 2-3 min loading time it takes almost 20-25min at least..).
when the system (windows) loads up the speed of reading the USB drives increse dramatically and all things gets back to normal.
with the same USB drive on several computers all the above works without any delay or very slow reading. so this i think it's the motherboard or the motherboard BIOS but i don't have a clue on how to fix this issue.
any help will be more than appreciated. thank you.

AngelTudorache please read the Forum Rules and don't resurrect nearly 4 year old threads. >>Please read and comply with the Forum Rules.<<
Please post your full system specs >>Posting Guide<<
Do you use the case USB ports or the MB USB ports ? Have you tested the MB USB ports by disconnecting the case USB headers ?
Suggest you transfer a large file from the HDD to a USB device or from a USB device to the HDD and monitor the transfer speeds. Anything between 15 and 30mb/s is normal for USB2.

I have new hard drive in macbook pro(08) and have SATA cable with external power source to old hard drive (10.5.8)via. USB port and newer drive(10.6.8) will not recognize older drive..Do I need to partition newer drive with older disk to recover data?

I have new HD 750GB Hybrid in 2008 Macbook Pro 17" w/ Snow Leopard 10.6.8 connected to old Hard drive(250GB that had 10.5.8 on it at time of failure) via SATA cable to USB port with external power source.. Computer not acknowledging old HD at all in Disk Utility or otherwise (that I'm aware of)..Do I need to partition New HD and load old(10.5.8) onto partition to recognize older drive for data recovery? Thanks Wayno08

You do not need to load 10.5.8 onto your new drive in order for a 10.6.8 system to see the contents of a 10.5.8 system.
You might want to check out the hard drive troubleshooting bootk in the downloads section of this web site:
http://scsc-online.com
They also sell a product named Phoenix that can do OS extraction and volume copying/cloning, but to be honest I don't know if it's appropriate in this case.
I would suggest the following:
Open up Terminal.app (under utilities) and type "diskutil list" without the quotes. This is the command line version of Disk Utility. If the external drive doesn't show up at all, then it's likely not connected properly, not getting power, or just plain dead. If it shows up with only a devce name like disk0s16 but no volume it means the drive is seen, the OS just can't make sense of it.
Assuming the drive shows up, I would try to boot off the original installl disks for the system and run Disk Utility from that. I'm assuming the drive will show up. You'll want to select the option to repair the drive and then perform the option to repair the permissions.
If the unit isn't showing up, as per step 1, try a different USB port. More importantly with your unit, try it on another side of the unit if possible. If you read the book I referenced above, some of those units have I/O boards that are separated from the logic board. If the cable from the logic board to the I/O card goes bad or has problems, which isn't all that uncommon, some or all of the ports on the I/O card may appear to be bad as well. If you use a USB port on another side, it would be routing out of a completely different I/O path, so that's a potential problem.
If the drive is only seen with a device name such as disk0s16, it's likely either the index files are corrupt beyond Disk Utility's ability to see them. The only thing that I think would help would be a product named DIsk Warrior, but I can't guarantee that.
Disk Warrior can be found at:
http://www.alsoft.com/diskwarrior/
The company that I linked in the first link above also makes a product named Scannerz that does HD and system testing. The Scannerz/Disk Warrior combination make a good pair because the complement each other....Scannerz does what Disk Warriror can't and Disk Warrior does what Scannerz can't. However, at this point I'm not too sure getting a tool like Scannerz would be of much use because it sounds like the damage has already been done.
Let us know what happens.

Problem with USB speakers and new Mac Mini

I have a USB sound system consisting of a pair of Harman Kardon soundsticks and a woofer from probably 10 years ago (bought and used originally with a Mac). I have tried driving it my new Mac Mini. It works fine for about a minute; then the music stops. Here's what I've tried to diagnose the problem:
1. The problem does not occur when these speakers are driven from my Macbook Air (about 3 years old).
2. The OS and iTunes software is up to date on both machines (10.9.5 and 12.0.1.26).
3. It does not depend on which USB port I use on the Mac Mini.
4. Using a port on a USB extender on the Mac Mini does not solve the problem.
5. The iTunes Preference settings are the same on both machines.

Sorry, no actual experience with USB Audio devices.
I found this in the Pro forum, but the outlook doesn't seem good:
http://discussions.apple.com/thread.jspa?messageID=1739084&#1739084

USB Drive and new Macbook Pro Retina

I have an early 2006 MBP. When I use my optical drive, I have to pump my smcFanControl up to 6000 plus point a table fan at the computer so I can load cd software without the computer overheating and shutting off. I've had both fans replaced, but it still runs as hot as August in Atlanta.
I've ordered a new MBP with Retina Display and I've bought a USB SuperDrive. My question is with the drive being external to the computer, will that make the computer cooler when I'm using the drive? Or is it the processor that makes the machine run hot and an external drive will make little difference.
I'm anticipating that my new MBP will be a lot cooler running to begin with, but I can't tell you how many applications I've loaded that have been buggy because I've had to reload them when the computer shut down midway through.
Should I install smcFanControl or is that a waste of space?

Your external drive will have no affect on the heat, it comes mostly from the CPU and GPU, but from other components as well.
Some older models of Macs it was good to use SMCFanControl because Apple thought it was perfectly fine for the CPU to get over 100º C before even starting to spin the fans up...
I've found on my Retina model, not only is the cooling designed much better, the fans react much quicker, and I don't really think SMCFanControl is needed.
I hope the creator updates it though, just cause... I've been glancing through the source code, but I haven't figured out the root of the problem yet for finding the Temp.

[solved] my usb flash and my camera can't be mounted.

hello, i have a problem i actually solved once with my optical drive which didn't work either, but how do i fix this? should i use fstab again? which directories should i create in /media for this to work?
thanks in advance for your help.
Last edited by 1lj4z1 (2011-04-01 18:55:17)

I'm improved the messaging from my udsks script, so you'll know now why an unmount fails.
Also, I've dropped notify-send in favour of zenity, though you can easily change it to use another notification program like dzen2 (which I prefer). This last change came about to avoid the problems caused by the implementation of Gnome3 and GTK3.

[SOLVED] Cloning boot and var partitions to a new drive for booting

Ok first of all here's my setup:
fakeraid (dmraid) / and home on an OCZ Revodrive
boot with GRUB on a flash drive (since fakeraid doesn't support grub)
var and downloads/media folder on a 500GB WD Caviar drive
When I originally installed Arch I had the Caviar drive in my home server in a RAID5 array, so that's why I opted to install boot and grub on a flash drive simply for booting. Now that I have the drive in my desktop I've cloned the flash drive's partitions and MBR using dd:
#dd if=/dev/sde of=~/MBR.img bs=512 count=1
#dd if=/dev/sde1 of=~/boot.img
#dd if=/dev/sdc1 of=~/var.img
I then backed up my downloads/media partition, then removed the partition table, then used dd to put the img files on the Caviar drive.
#dd if=~/MBR.img of=/dev/sdc bs=512 count=1
#dd of=~/boot.img of=/dev/sdc1
#dd of=~/var.img of=/dev/sdc2
I also created labels for the filesystems and put those in fstab.
I'm able to mount both partitions, however I can't boot from the drive. I get a 'grub hard disk error' (no error number) when I put it as my first drive in the BIOS.
I can still use the flash drive as the first hard drive in the BIOS and boot from it, then it mounts the dmraid root partition and boots successfully. It is also able to mount the var and boot partitions in fstab.
Basically the only problem is that the MBR is somehow wrong. I then tried booting back into an Arch live USB and installing GRUB from the prompt:
grub
grub>setup (hd4,0) (in this case the Caviar drive's boot partition was /dev/sde1
So essentially what I'm asking is how GRUB handles the MBR. Is it specific to the partition table of the drive in which it resides when it's originally installed? For instance, since I had an 8GB flash drive with 2 partitions when I installed GRUB, is the backed up MBR no good for a 500GB drive with 3 partitions?
I have everything backed up so I can start with a fresh /boot and /var if need be....I'm just not sure where to start.
Thanks in advance.
Last edited by DarksideEE7 (2011-02-13 23:25:31)

Sorry, I forgot to mention that I tried to install GRUB from the GRUB shell in a live Arch USB. It failed on a few non-critical parts, and succeeded on the last part. I'm going to try again shortly, possibly I did something wrong. GRUB is able to find the stage files using:
#grub
grub>find /grub/stage1
grub> find /grub/stage1
(hd0,0)
(hd5,0)
grub>
(hd0,0) is the desired boot drive, while (hd5,0) is the current bootable flash drive with /boot and GRUB installed.
Here is the output of fdisk -l:
WARNING: GPT (GUID Partition Table) detected on '/dev/sde'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sde: 2000.4 GB, 2000398934016 bytes
256 heads, 63 sectors/track, 242251 cylinders, total 3907029168 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 identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sde1 1 3907029167 1953514583+ ee GPT
Disk /dev/sdb: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders, total 117231408 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 identifier: 0xedb72db9
Device Boot Start End Blocks Id System
/dev/sdb1 * 2048 206847 102400 7 HPFS/NTFS
/dev/sdb2 206848 117227519 58510336 7 HPFS/NTFS
Disk /dev/sdd: 40.0 GB, 40018599936 bytes
255 heads, 63 sectors/track, 4865 cylinders, total 78161328 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 identifier: 0x00000000
Disk /dev/sdd doesn't contain a valid partition table
Disk /dev/sdc: 40.0 GB, 40018599936 bytes
32 heads, 32 sectors/track, 76329 cylinders, total 78161328 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 identifier: 0xb8372fcd
Device Boot Start End Blocks Id System
/dev/sdc1 32 21484543 10742256 83 Linux
/dev/sdc2 21484544 156317695 67416576 83 Linux
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 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 identifier: 0x8497e059
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 206847 102400 83 Linux
/dev/sda2 206848 42149887 20971520 83 Linux
/dev/sda3 42149888 976773167 467311640 83 Linux
Disk /dev/dm-0: 80.0 GB, 80035053568 bytes
32 heads, 32 sectors/track, 152654 cylinders, total 156318464 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 131072 bytes
Disk identifier: 0xb8372fcd
Device Boot Start End Blocks Id System
/dev/dm-0p1 32 21484543 10742256 83 Linux
Partition 1 does not start on physical sector boundary.
/dev/dm-0p2 21484544 156317695 67416576 83 Linux
Disk /dev/dm-1: 11.0 GB, 11000070144 bytes
255 heads, 63 sectors/track, 1337 cylinders, total 21484512 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 131072 bytes
Alignment offset: 49152 bytes
Disk identifier: 0x00000000
Disk /dev/dm-1 doesn't contain a valid partition table
Disk /dev/dm-2: 69.0 GB, 69034573824 bytes
255 heads, 63 sectors/track, 8392 cylinders, total 134833152 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 131072 bytes
Disk identifier: 0x00000000
Disk /dev/dm-2 doesn't contain a valid partition table
Disk /dev/sdf: 8086 MB, 8086618112 bytes
249 heads, 62 sectors/track, 1023 cylinders, total 15794176 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 identifier: 0x8497e059
Device Boot Start End Blocks Id System
/dev/sdf1 * 62 200693 100316 83 Linux
/dev/sdf2 200694 15794175 7796741 83 Linux
I'm using dmraid, so just to be clear I've configured the raid using:
#modprobe dm_mod
#dmraid -ay
Then I saw the array stored in /dev/mapper/silXXXXX. I then created partitions for /boot, /, and home. At that time I was hoping to get GRUB working with the AUR package grub2-dmraid. I wasn't able to get it working for some time, so I just went ahead and installed boot and GRUB to a separate USB flash drive.
Here is the output of df -h:
Filesystem Size Used Avail Use% Mounted on
udev 10M 268K 9.8M 3% /dev
/dev/mapper/sil_bgbgdjaddicbp1
11G 5.3G 4.3G 56% /
shm 6.0G 584K 6.0G 1% /dev/shm
/dev/mapper/sil_bgbgdjaddicbp2
64G 38G 23G 63% /home
/dev/sda1 95M 16M 75M 18% /boot
/dev/sda2 19G 142M 19G 1% /var
/dev/sda3 439G 148G 269G 36% /home/l33/Torrents
none 1000M 132K 1000M 1% /tmp
shm 6.0G 584K 6.0G 1% /dev/shm
/dev/sde1 1.8T 1.1T 665G 62% /mnt/Green
and cat /etc/mtab
proc /proc proc rw,nosuid,nodev,noexec,relatime
sys /sys sysfs rw,nosuid,nodev,noexec,relatime
udev /dev devtmpfs rw,nosuid,relatime,size=10240k,nr_inodes=1022975,mode=755
/dev/mapper/sil_bgbgdjaddicbp1 / ext4 rw,noatime,barrier=1,stripe=32,data=ordered
devpts /dev/pts devpts rw 0 0
shm /dev/shm tmpfs rw,nosuid,nodev 0 0
/dev/mapper/sil_bgbgdjaddicbp2 /home ext4 rw,noatime 0 0
/dev/sda1 /boot ext2 rw 0 0
/dev/sda2 /var reiserfs rw,noatime 0 0
/dev/sda3 /home/l33/Torrents ext4 rw,noatime 0 0
none /tmp tmpfs rw,nosuid,nodev,noatime,size=1000M,mode=1777 0 0
shm /dev/shm tmpfs rw,nosuid,nodev,size=6G 0 0
rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0
nfsd /proc/fs/nfsd nfsd rw,noexec,nosuid,nodev 0 0
/dev/sde1 /mnt/Green ext4 rw 0 0
Also I don't have a /proc/mdstat. That's only for mdadm RAID setups, right? It's been quite some time since I've used mdadm so I can't remember.
EDIT:
So I booted into a live Arch USB and entered the grub shell. I ran:
#grub
grub> root (hd3,0)
Filesystem type is ext2fs, partition type 0x83
grub> setup (hd3)
Checking if "/boot/grub/stage1" exists.....no
Checking if "/grub/stage1 exists.......yes
Checking if "/grub/stage2 exists.......yes
Checking if "/grub/e2fs_stage1_5 exists....yes
Running "embed /grub/e2fs_stage1_5 (hd3)".....25 sectors are embedded.
succeeded
Running "install /grub/stage1 (hd3) (hd3))1+25 p (hd3,0)/grub/stage2 /grub/menu.lst".......succeeded
Done.
Last time I recall more errors than this, then it reporting that one was a non-critical error, so I think the problem may be solved. More to come.
Last edited by DarksideEE7 (2011-02-13 23:18:44)

Can I switch out a hard drive for an SSD without having to clone the existing hard drive, and then install Yosemite from an USB Boot Drive onto the new SSD?

Can I simply replace a hard drive with a new SSD and just install Yosemite from a USB boot drive onto the SSD? I recently bought a used MBP and it has absolutely no files on it except for the OS, and so I'm assuming I don't need to clone the current hard drive as I can just reinstall the OS onto the new SSD.

Honey_Revenge wrote:
Thanks.
Just a quick follow up question, is formatting the SSD with HFS+ done in Disk Utility?...
It's possible that the SSD will be set up for use on a PC, which means it will have a Master Boot Record partition table rather than a GUID Partition Table, which is what Yosemite needs. In Disk Utility, select the SSD and click the Partition button. Create a new Partition Layout and click the Options... button at the bottom. You'll likely see MBR is selected. Choose GUID instead and Mac OS Extended (Journaled) for the Format.

[SOLVED]system fails to boot since adding udev rules for automounting

Hello
I have recently been trying to use udev rules to automount, and putting together stuff from the wiki, forums and general googling around have produced the following set of rules:
# automounts usb hdd and pendrives as usbhd-sdx; no messing around with
# volume labels or other confusing stuff
# matches all sdx devices except the internal hdd, sda
KERNEL=="sd[b-z]", NAME="%k", SYMLINK+="usbhd-%k", GROUP="users", OPTIONS="last_rule"
# imports filesystem information
ACTION=="add", IMPORT{program}="/sbin/blkid -o udev -p %N"
# creates mount points and sets up symlinks
ACTION=="add", KERNEL=="sd[b-z][0-9]", SYMLINK+="usbhd-%k", GROUP="users", NAME="%k"
ACTION=="add", KERNEL=="sd[b-z][0-9]", RUN+="/bin/mkdir -p /media/usbhd-%k"
ACTION=="add", KERNEL=="sd[b-z][0-9]", RUN+="/bin/ln -s /media/usbhd-%k /mnt/usbhd-%k"
# global mount options
ACTION=="add", ENV{mount_options}="relatime"
# filesystem-specific mount options (777/666 dir/file perms for ntfs/vfat)
ACTION=="add", ENV{ID_FS_TYPE}=="vfat|ntfs", ENV{mount_options}="$env{mount_options},gid=100,dmask=000,fmask=111,utf8"
# automount ntfs filesystem with ntfs-3g driver
ACTION=="add", KERNEL=="sd[b-z][0-9]", ENV{ID_FS_TYPE}=="ntfs", RUN+="/bin/mount -t ntfs-3g -o %E{mount_options} /dev/%k /media/usbhd-%k", OPTIONS="last_r$
# automount all other file systems
ACTION=="add", KERNEL=="sd[b-z][0-9]", ENV{ID_FS_TYPE}!="ntfs", RUN+="/bin/mount -t auto -o %E{mount_options} /dev/%k /media/usbhd-%k", OPTIONS="last_rule"
# unmounts and removes the mount points
ACTION=="remove", KERNEL=="sd[b-z][0-9]", RUN+="/bin/rm -f /mnt/usbhd-%k"
ACTION=="remove", KERNEL=="sd[b-z][0-9]", RUN+="/bin/umount -l /media/usbhd-%k"
ACTION=="remove", KERNEL=="sd[b-z][0-9]", RUN+="/bin/rmdir /media/usbhd-%k", OPTIONS="last_rule"
This seemed to be working very well unitl I tried to boot this morning and the boot process stopped at "processing UDev events" with the following message:
iTCO_wdt: Unexpected close, not stopping watchdog!
It pauses at this point for 10-15 seconds and then reboots.
Having searched a bit, I found the following similar post on the forums: http://bbs.archlinux.org/viewtopic.php?pid=459375
Which suggests that the problem might lie with this line:
ACTION=="add", IMPORT{program}="/sbin/blkid -o udev -p %N"
I have renamed the file so that it no longer has the udev .rules extension and now the system boots fine. Does anyone have any suggestions as to why the above rules might be causing this behaviour and how I might go about fixing it?
Thanks
Last edited by useradded (2010-07-02 22:58:14)

Hey falconindy
That was the final kick up the logical a$$ that I needed to get some kind of grip on udev rules. I now have a fully functional rule that applies only to /dev/sdxy and not to everything else as well, so no more boot trauma, THANK YOU.
I will mark this thread as solved and post my new rule for the benefit of anyone who might read this.
New rule (no boot problems):
# automounts usb hdd and pendrives as label or as usbhd-sdxy if no label present
# ensures the following is _only_ run for sdxy devices excluding internal hdd, sda
KERNEL!="sd[b-z][0-9]", GOTO="personal_usb_automount_settings_end"
# imports filesystem information
# provides access to following variables:
# ID_FS_UUID; ID_FS_UUID_ENC; ID_FS_VERSION; ID_FS_TYPE; ID_FS_VERSION; ID_FS_LABEL
# accessible via ENV{variable}; $env{variable}|%E{variable}
IMPORT{program}="/sbin/blkid -o udev -p %N"
# Get a label if present, otherwise name usbhd-%k
ENV{ID_FS_LABEL}!="", ENV{dir_name}="%E{ID_FS_LABEL}"
ENV{ID_FS_LABEL}=="", ENV{dir_name}="usbhd-%k"
# creates mount points and sets up symlinks
ACTION=="add", SYMLINK+="%E{dir_name}", GROUP="users", NAME="%k"
ACTION=="add", RUN+="/bin/mkdir -p /media/%E{dir_name}"
ACTION=="add", RUN+="/bin/ln -s /media/%E{dir_name} /mnt/%E{dir_name}"
# global mount options
ACTION=="add", ENV{mount_options}="relatime"
# filesystem-specific mount options (777/666 dir/file perms for ntfs/vfat)
ACTION=="add", ENV{ID_FS_TYPE}=="vfat|ntfs", ENV{mount_options}="$env{mount_options},gid=100,dmask=000,fmask=111,utf8"
# automount ntfs filesystem with ntfs-3g driver
ACTION=="add", ENV{ID_FS_TYPE}=="ntfs", RUN+="/bin/mount -t ntfs-3g -o %E{mount_options} /dev/%k /media/%E{dir_name}", OPTIONS="last_rule"
# automount all other file systems
ACTION=="add",ENV{ID_FS_TYPE}!="ntfs", RUN+="/bin/mount -t auto -o %E{mount_options} /dev/%k /media/%E{dir_name}", OPTIONS="last_rule"
# unmounts and removes the mount points
ACTION=="remove", RUN+="/bin/rm -f /mnt/%E{dir_name}"
ACTION=="remove", RUN+="/bin/umount -l /media/%E{dir_name}"
ACTION=="remove", RUN+="/bin/rmdir /media/%E{dir_name}", OPTIONS="last_rule"
# exit
LABEL=="personal_usb_automount_settings_end"
Last edited by useradded (2010-07-02 22:59:20)

New udev version and required changes

As described here.
I think that deserves an Announcement.

phrakture wrote:Ok, to all the nay-sayers out there. Yes, udev requires module autoloading activated. This is intentional. If it forces you to auto load on boot, then so be it. That is the way it is intended.
From what you are saying, and from what I've gathered from dabbling in /lib/udev and the initscripts, is that you decided that only if MOD_AUTOLOAD is set to yes, udev will autoload the modules. This seems arbitrary to me. Technically I don't see the reason for this (especially because you _can_ control which modules are loaded at boot time, via the blacklist). So, effectively, I don't see how this brought a new feature, except for breaking MODULES.
Arguably one of the coolest and most unique features of Arch, is thereby made practically obsolete. And users who are still using MODULES are forced to mess around with the blacklists, wrong hardware detected, etc... This is even more difficult for people like me, because if something goes wrong with the boot-up of my laptop, I am unable to repair it, since it's one of those tiny laptops without CD or floppy drives. Maybe I should change to a distribution where I am not afraid of screwing up my bootup after every update?
And by the way, adding usb-storage to MODULES doesn't really solve the problem. What is the point of hotplugging then, anyways?
Normally, I am open to fixing up my computers after updates that bring something cool and new to Arch. But I am flabbergasted when we are made to do redundant work to maintain our systems. I see Arch Linux as a distribution for WORKstations, not a playground, and thus I believe Arch developers should have a more careful approach when dealing with init scripts, kernels and such.
Maksim Sipos

[SOLVED] Problem with modules and udev

Hi everybody,
I've been configuring Arch on my new laptop the last few days and today as I was going to perform the first backup, I noticed that my external HDD does not show up in /dev/ when I plug it in. I figured it could be a problem with udev and the fact that in my /etc/rc.conf I use MOD_AUTOLOAD="no" with an explicit list of MODULES generated with hwdetect (as suggested in the wiki).
To "solve" this I just changed MOD_AUTOLOAD to "yes" and after a reboot everything worked fine.
My questions are:
1) Is it possible to keep that feature (udev detects usb drives and creates the corresponding /dev/sdX) while having MOD_AUTOLOAD="no" ? What is/are the appropriate module(s) I have to put in my MODULES array ?
2) What other such "basic" MODULES could be very useful that hwdetect does not tell about.
Sorry for any English mistakes (I'm not a native speaker) and thank you in advance for your help,
yms
Last edited by yms (2010-01-06 12:48:20)

1) Thank you, it works perfectly.
2) Yes I know the question is weird. The thing is I have no precise idea at the moment and I just wanted to know if there are other very widely used features such as the one described in 1) that hwdetect ommits and that has to be loaded in MODULES.
Anyway, thank you very much, I consider this matter [solved]

Boot and NO USB

Hi,
It's the second time that I power-off my book and, when I reboot no keyboard no touchpad no bluetooth and no USB.
With desktop remote I can check the system management hardware that does show nothing under USB controller.
The first time I've tried every kind of mac reset, NVRAM PRAM SMC Safeboot ecc...NOTHING...
I have solved it with Command+C and new macosx instalation...
Finally I think that was a software problem not hardware....
After a month, today, again the same problem...any idea?

more details,
I have a IOMEGA 1T Ultramax and a USB mouse always connected...
Here the exactly sequence to have a NO USB boot:
- Macbook magsafe, ultramax and mouse connected.
- Ejectetd ultramax and magsafe disconnected.
- Macbook moved to battery working time...and powered off.
- After one night, PowerOn and Keyboard, touchpad and every USB Death in OSX.
PS: USB works in new macosx installations, every kind of reset tried.
Thanks for your time

[SOLVED] Encrypted root, /boot on USB, cryptkey issue

Well to the topic. Followed this guide.
Usb flash drive with GRUB and a keyfile on it. Encrypted root.
grub.cfg
linux /vmlinuz-linux root=UUID=<uuid> ro cryptdevice=/dev/disk/by-id/<id>:luks cryptkey=/dev/disk/by-uuid/<uuid>:ext2:/key ipv6.disable=1 quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
mkinitcpio.conf
MODULES="ata_generic ata_piix nls_cp437 ext2 i915"
HOOKS="base udev autodetect modconf block encrypt filesystems keyboard fsck consolefont"
Result: "Meh can't read a keyfile. Please input a passphrase om nom nom."
Tried:
1. Quadruple-checked UUID's, used /dev/sdX instead of them.
2. Using different modules, like nls_utf8, removing ata_* stuff.
3. Playing with <path> and <keyfile> strings, slashes, e t c.
4. A barrel roll.
Is it actually possible to make that filesystem key reading work? If not, how can I get physical offset of keyfile in a filesystem?
UPDATE:
Trouble in device detection speed. Any other usb media get's recognized instantly, while the one I booted from is slow like hell.
Last edited by wfoojjaec (2013-08-14 14:37:11)

Marked as solved.
It seems that origin of a bug was somewhere in a kernel. After a recent update, done today of a 'linux' package a /boot usb device is properly recognized after about 5 seconds passed from poweron (instead of a full initialization at ~270 sec and hanging udev before).
A hack with fstab & noauto is not required now. <_<

[SOLVED] Seriously, Arch? Recovery shell, USB boot won't work

So I made the mistake of updating my system without painstakingly checking the news/updates and possible error logs. I rebooted my computer this morning and:
Decompressing Linux...Parsing ELF...done.
Booting the kernel.
:: Running Hook [resume]
ERROR: Unable to find root device '/dev/sda3'.
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty; job control turned off
[rootfs /]#
This appears to be a pretty widespread problem today, as I've googled and searched the forums extensively and everyone is complaining about some udev to mkinitcpio movement or something.
I know what I need to do: either copy my files off my hard drive and reinstall, or chroot and downgrade my kernel, or chroot and reinstall udev, something like that.
Cool, so I need a liveCD. Unfortunately, my laptop lacks a CD drive (lenovo tablet). So I set out to make a USB bootable drive.
I tried it from Windows: my laptop didn't detect anything and kept kicking me back to the recovery shell. (Tried PartedMagic, Ubuntu, and Arch.)
I tried it from my school's Linux computers: Can't do *anything* without root. I tried sudo and for the first time in my life, the incident was reported and I got an email telling me not to try sudo again. Sweet.
I just tried it from my friend's Mac (the Arch x64 iso via Unetbootin): Now I get a blinking cursor when I boot from the USB.
What would you do? I'm at my wit's end here, and after using Archlinux for two years, this is giving me a MAJORLY bad taste in my mouth for the distro.
Last edited by tacostick (2012-02-15 23:33:13)

karol,
I can only change parameters from the grub menu, as far as I can tell, and I tried (hd0,{0,1,2,3,4}) and none of them worked. Only (hd0,0) gets me even as far as the recovery shell.
fsckd,
I'm using Unetbootin, which offers Core, Core_x64, Netinstall, and Netinstall_x64. Because I intend to chroot an x64 system, I tried core_x64.
willbprog127,
Yeah, you're right - sorry for being snarky. Thanks, please do let me know if you find that parameter.
I booted from the usb stick on one of my school's RHEL computers, and it says "no operating system detected". I'm...so...sad...why didn't unetbootin work...going to try to burn ubuntu again.

HT6437 My itunes cannot locate my ipod. All the sync option are grayed out and diagnostics says that itunes cannot find usb ports and that no device is connected when it is. What should I do to solve this issue?

So itunes is giving me problems. Since around Christmas time, itunes decided to stop reading my ipod. I connect it to my computer with the usb cable and my computer will recognize that a device is connected but itunes will not. If I go to file->devices and try to sync, all of my sync options are grayed out, while before it would just automatically sync.
When I run diagnostics it tells me that under ports that it cannot find usb ports (it has a green circle?), a type of cable isn't found, and that no device is connected with the usb cable (which my ipod is). I have been trying to fix this issue but nothing is working. I've tried restarting my ipod, itunes, and my computer, i've also tried resetting my ipod and uninstalling itunes then reinstalling itunes but nothing seems to be working.
Does anyone know how to solve this issue?

Do the USB ports work for other devices?
Does the iPod charge?
See
iOS: Device not recognized in iTunes for Windows
- I would start with
Removing and reinstalling iTunes and other software components for Windows Vista, Windows 7, or Windows 8
However, after your remove the Apple software components also remove the iCloud Control Panel via Windows Programs and Features app in the Window Control Panel. Then reinstall all the Apple software components
- Then do the other actions of:
iOS: Device not recognized in iTunes for Windows
paying special attention to item #5
- New cable and different USB port
- Run this and see if the results help with determine the cause
iTunes for Windows: Device Sync Tests
Also see:
iPod not recognised by windows iTunes
Troubleshooting issues with iTunes for Windows updates
- Try on another computer to help determine if computer or iPod problem

[solved}Permanent USB boot and new udev?

Similar Messages

Maybe you are looking for