Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Set internal hard drives unaccessible to imager Post 302591816 by Corona688 on Friday 20th of January 2012 05:30:01 PM
Old 01-20-2012
I didn't suggest editing a rule, but adding a rule.

I don't think /dev/sda is generated by any rule -- it's a default. Kernel says this device is named 'sda', and no udev rules change that name, so it just ends up /dev/sda. (Yes, there's rules related to sda already, but none of them actually rename it. So the default name remains.)

My intent is to catch the devices you don't want to use and prevent them from appearing in their default locations by giving them different names.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Hard drives

Will some one tell me what this means. "warning: ida 0 <slot 6> : command timed out on dev 1/42 blk 4824290 logical unit=0 blocks=5512102, size 2, cmd=0x20." I'm running SCO 505 on a proliant 1600r. Thnank you in advance. (3 Replies)
Discussion started by: franruiz
3 Replies

2. Linux

No Hard Drives Have Been Found

I am using an Acer Aspire 4720Z with two partitions C and D. Windows is installed on C and I decided to install Red Hat Linux 9 in partition D. The two partitions are in NTFS file system. During my installation of the the Linux, a prompt was displayed on screen with the message: "No hard drives... (2 Replies)
Discussion started by: tamcomng
2 Replies

3. Filesystems, Disks and Memory

Opinions on Internal SCSI Tape Drives for FreeBSD home server?

Any recommend manufacturers for an internal SCSI tape drive in my FreeBSD 7.0 home server? Besides RAID-1, I'm not backing-up, but man, are they expensive! What makes a tape drive so darn pricy? There is no way I can afford a new drive so I'll start looking on eBay and craigslist to see if there... (3 Replies)
Discussion started by: Aaron Van
3 Replies

4. Solaris

formating and repartitioning an external hard drives

Version: solaris 10 x86 I just got a western digital external harddrive formated with fat 32. this drive came with some setup files which is meant for windows or mac. I want to reformat and partition this drive into two ( for solaris and windows) such that the setup files will still be there... (2 Replies)
Discussion started by: seyiisq
2 Replies

5. Filesystems, Disks and Memory

Help adding new hard drives

Folks; I just added 2 physical new hard drives to my SUSE server. My server is already running SUSE 10.3 version. Is there a command i can use to add the new space or even see if the system can sees them? (3 Replies)
Discussion started by: Katkota
3 Replies

6. UNIX for Dummies Questions & Answers

How to set server's ip address, router, network mask and set if it is an internal or external ip?

Hello, I need to write a program which sets server's ip address, router, network mask. Program also should set if it is an internal or external ip. Maybe someone can help me ? Any information from u is very useful :b: I stopped at .. :( #!/bin/sh A=`hostname -i` echo "server ip address is $A"... (4 Replies)
Discussion started by: zagaruika
4 Replies

7. Solaris

Reinstall old hard drives

I have a T2000 Sun-Fire server. I have 2 sets of drives in a raid 1. Lets call them Set A and Set B. I had Set A installed and working. I needed a new install so I so build up Set B. After some time I wanted to put Set A back in the server. Now the system will not boot off of Set A. I tried to boot... (7 Replies)
Discussion started by: stu1811
7 Replies

8. Hardware

Hard Drives and MBR

Hello everyone. I have a question which I may know the answer to, I'm just looking for a confirmation. When it comes to the MBR of a hard drive, i've read in multiple sources that it's always located in the first sector of the hard drive. Is the MBR there from the factory? When I buy a new blank... (3 Replies)
Discussion started by: Lost in Cyberia
3 Replies

9. Solaris

Solaris 8 - Accessing Hard Drives

Hi, I have two SCSI Hard Drives in a Sun Solaris 8 server as shown below. I would like to access Disk1 and look at its contents, directory structure and files. How do I change my default directory from Disk 0 to Disk 1 and vice versa? Thank you. (5 Replies)
Discussion started by: ssabet
5 Replies

10. UNIX for Beginners Questions & Answers

Understanding volumes and hard drives

Ok so i thought i was smart but i can tell I need some help. I am playing around with understanding lvm and adding disks to a linux box. I added a disk and then ran what i thought were commands to add this disk to the box but I think I messed up and would like some help. My question is did i... (5 Replies)
Discussion started by: cptkirkh
5 Replies
UDEVADM(8)							      udevadm								UDEVADM(8)

NAME
udevadm - udev management tool SYNOPSIS
udevadm [--debug] [--version] [--help] udevadm info [options] [devpath] udevadm trigger [options] [devpath] udevadm settle [options] udevadm control option udevadm monitor [options] udevadm test [options] devpath udevadm test-builtin [options] command devpath DESCRIPTION
udevadm expects a command and command specific options. It controls the runtime behavior of systemd-udevd, requests kernel events, manages the event queue, and provides simple debugging mechanisms. OPTIONS
-d, --debug Print debug messages to standard error. --version Print a short version string and exit. -h, --help Print a short help text and exit. udevadm info [options] [devpath|file] Queries the udev database for device information stored in the udev database. It can also query the properties of a device from its sysfs representation to help creating udev rules that match this device. -q, --query=TYPE Query the database for the specified type of device data. It needs the --path or --name to identify the specified device. Valid TYPEs are: name, symlink, path, property, all. -p, --path=DEVPATH The /sys path of the device to query, e.g. [/sys]/class/block/sda. Note that this option usually is not very useful, since udev can guess the type of the argument, so udevadm --devpath=/class/block/sda is equivalent to udevadm /sys/class/block/sda. -n, --name=FILE The name of the device node or a symlink to query, e.g. [/dev]/sda. Note that this option usually is not very useful, since udev can guess the type of the argument, so udevadm --name=sda is equivalent to udevadm /dev/sda. -r, --root Print absolute paths in name or symlink query. -a, --attribute-walk Print all sysfs properties of the specified device that can be used in udev rules to match the specified device. It prints all devices along the chain, up to the root of sysfs that can be used in udev rules. -x, --export Print output as key/value pairs. Values are enclosed in single quotes. -P, --export-prefix=NAME Add a prefix to the key name of exported values. -d, --device-id-of-file=FILE Print major/minor numbers of the underlying device, where the file lives on. -e, --export-db Export the content of the udev database. -c, --cleanup-db Cleanup the udev database. --version Print a short version string and exit. -h, --help Print a short help text and exit. In addition, an optional positional argument can be used to specify a device name or a sys path. It must start with /dev or /sys respectively. udevadm trigger [options] [devpath|file...] Request device events from the kernel. Primarily used to replay events at system coldplug time. -v, --verbose Print the list of devices which will be triggered. -n, --dry-run Do not actually trigger the event. -t, --type=TYPE Trigger a specific type of devices. Valid types are: devices, subsystems. The default value is devices. -c, --action=ACTION Type of event to be triggered. The default value is change. -s, --subsystem-match=SUBSYSTEM Trigger events for devices which belong to a matching subsystem. This option can be specified multiple times and supports shell style pattern matching. -S, --subsystem-nomatch=SUBSYSTEM Do not trigger events for devices which belong to a matching subsystem. This option can be specified multiple times and supports shell style pattern matching. -a, --attr-match=ATTRIBUTE=VALUE Trigger events for devices with a matching sysfs attribute. If a value is specified along with the attribute name, the content of the attribute is matched against the given value using shell style pattern matching. If no value is specified, the existence of the sysfs attribute is checked. This option can be specified multiple times. -A, --attr-nomatch=ATTRIBUTE=VALUE Do not trigger events for devices with a matching sysfs attribute. If a value is specified along with the attribute name, the content of the attribute is matched against the given value using shell style pattern matching. If no value is specified, the existence of the sysfs attribute is checked. This option can be specified multiple times. -p, --property-match=PROPERTY=VALUE Trigger events for devices with a matching property value. This option can be specified multiple times and supports shell style pattern matching. -g, --tag-match=PROPERTY Trigger events for devices with a matching tag. This option can be specified multiple times. -y, --sysname-match=PATH Trigger events for devices for which the last component (i.e. the filename) of the /sys path matches the specified PATH. This option can be specified multiple times and also supports shell style pattern matching. --name-match=NAME Trigger events for devices with a matching device path. This option can be specified multiple times. -b, --parent-match=SYSPATH Trigger events for all children of a given device. --version Print a short version string and exit. -h, --help Print a short help text and exit. In addition, optional positional arguments can be used to specify device names or sys paths. They must start with /dev or /sys respectively. udevadm settle [options] Watches the udev event queue, and exits if all current events are handled. -t, --timeout=SECONDS Maximum number of seconds to wait for the event queue to become empty. The default value is 120 seconds. A value of 0 will check if the queue is empty and always return immediately. -E, --exit-if-exists=FILE Stop waiting if file exists. --version Print a short version string and exit. -h, --help Print a short help text and exit. udevadm control option Modify the internal state of the running udev daemon. -e, --exit Signal and wait for systemd-udevd to exit. -l, --log-priority=value Set the internal log level of systemd-udevd. Valid values are the numerical syslog priorities or their textual representations: emerg, alert, crit, err, warning, notice, info, and debug. -s, --stop-exec-queue Signal systemd-udevd to stop executing new events. Incoming events will be queued. -S, --start-exec-queue Signal systemd-udevd to enable the execution of events. -R, --reload Signal systemd-udevd to reload the rules files and other databases like the kernel module index. Reloading rules and databases does not apply any changes to already existing devices; the new configuration will only be applied to new events. -p, --property=KEY=value Set a global property for all events. -m, --children-max=value Set the maximum number of events, systemd-udevd will handle at the same time. -t, --timeout=seconds The maximum number of seconds to wait for a reply from systemd-udevd. --version Print a short version string and exit. -h, --help Print a short help text and exit. udevadm monitor [options] Listens to the kernel uevents and events sent out by a udev rule and prints the devpath of the event to the console. It can be used to analyze the event timing, by comparing the timestamps of the kernel uevent and the udev event. -k, --kernel Print the kernel uevents. -u, --udev Print the udev event after the rule processing. -p, --property Also print the properties of the event. -s, --subsystem-match=string[/string] Filter kernel uevents and udev events by subsystem[/devtype]. Only events with a matching subsystem value will pass. -t, --tag-match=string Filter udev events by tag. Only udev events with a given tag attached will pass. --version Print a short version string and exit. -h, --help Print a short help text and exit. udevadm test [options] [devpath] Simulate a udev event run for the given device, and print debug output. -a, --action=string The action string. -N, --resolve-names=early|late|never Specify when udevadm should resolve names of users and groups. When set to early (the default), names will be resolved when the rules are parsed. When set to late, names will be resolved for every event. When set to never, names will never be resolved and all devices will be owned by root. --version Print a short version string and exit. -h, --help Print a short help text and exit. udevadm test-builtin [options] [command] [devpath] Run a built-in command COMMAND for device DEVPATH, and print debug output. --version Print a short version string and exit. -h, --help Print a short help text and exit. SEE ALSO
udev(7), systemd-udevd.service(8) systemd 237 UDEVADM(8)
All times are GMT -4. The time now is 04:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy