Persistent device naming

hi, I have two network adapters. one is internal and one is a pci card. I used this https://wiki.archlinux.org/index.php/Ud … ork_device and added udev rules to make sure the correct one is always eth0 and the other one is eth1. but they still occasionally switch after a reboot,
my /etc/udev/rules.d/10-network.rules looks like this:
SUBSYSTEM=="net", ATTR{address}=="74:ea:3a:83:86:5e", NAME="eth0"
SUBSYSTEM=="net", ATTR{address}=="00:1c:c0:88:0b:3f", NAME="eth1"
I am using a full systemd environment. no classic initscripts or sysvinit installed (just in case that affects things).
Any idea how I can tell why this is happening?

Try with NAME:= rather than NAME=
From "man udev":
Assign a value to a key finally; disallow any later changes.
However, I always saw the recommended method as being to assign a SYMLINK, and not change the name. E.g.:
SUBSYSTEM=="net", ATTR{address}=="00:c3:d1:a5:e4:09", SYMLINK+="eth-router"

Similar Messages

  • Persistent device naming - cannot mount root as rw

    hello people,
    i started using persistent block device naming but quickly realized i can only use it for non-root (/) partitions in fstab otherwise it will only get mounted as readonly and my system (arch current) will cease to boot.
    # this line only mounts fs as ro
    #/dev/disk/by-uuid/d02a0ef4-8cb3-460c-a48a-471f2798e4ad / ext3 default 0 1
    # i get stuck while mounting fs as ro when using this line
    #UUID=d02a0ef4-8cb3-460c-a48a-471f2798e4ad / ext3 default 0 1
    # so i have to use the old format (non persistent device naming)
    /dev/sda6 / ext3 defaults 0 1
    # the other partitions (same disk) work just fine
    /dev/disk/by-uuid/cc295f7d-3927-433d-bcc0-2d2267e0d672 /home ext3 defaults 0 1
    /dev/disk/by-uuid/936823be-b9bb-4a9d-a4e4-b4d62972f0af swap swap defaults 0 0
    /dev/disk/by-uuid/E8A04533A0450A10 /mnt/win-c ntfs-3g locale=sk_SK.utf8,nls=utf8,users 0 0
    snippet from menu.lst:
    kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/d02a0ef4-8cb3-460c-a48a-471f2798e4ad ro
    initrd /boot/kernel26.img
    does anyone have an idea what may be causing this?
    thanks.
    jozef

    Both of the UUID fstab lines for your root filesystem have 'default' instead of 'defaults'. Is that intentional, or is it a typo in your post?.
    I don't know offhand whether 'default' is even a valid option, or what effect it would have if it is.

  • [Solved] Persistent Device Naming for Full Disk Encryption & USB Boot

    Using the following boot option does not work while using FDE (dm-crypt plain) due to the filesystem being unreachable until decryption.
    cryptdevuce=UUID=xxxx-xxxx:root
    sda
    └   root   /
    sdb
    └  sdb1   /boot
    This forces the use of /dev/sda for booting, but occasionally a USB device is mapped to sda instead.
    Is there a way to use Persistent Block Device Naming for this type of FDE?
    Last edited by easton741 (2015-02-05 01:42:57)

    MSC wrote:What exactly is not working? It shouldn't matter if the USB device maps to /dev/sda because the partition with that UUID still resides on the same disk.
    I guess I should be more clear. The entire sda device is encrypted. This meas that during the initialization there is no UUID is read from the disk because the filesystem cannot be read until it is unencrypted.
    This leaves me in a catch 22 where I cannot use UUID until the device is unencrypted, but I need UUID to boot & decrypt the device properly. Here is an example of what the computer sees in the Arch Install.
    NAME            FSTYPE   LABEL                UUID                                 MOUNTPOINT
    sda                                                                       
    sdb                iso9660     ARCH_201501    2015-01-01-09-54-22-00               
    ├─sdb1          iso9660    ARCH_201501     2015-01-01-09-54-22-00       /run/archiso/bootmnt
    └─sdb2          vfat           ARCHISO_EFI    9051-9287                           
    sdc                                                                       
    └─sdc1          vfat                                     4EC5-5B7D                        (normally /boot)
    As you can see, sda has no uuid.
    So I guess what I'm asking is if there is any alternative method because it does not look like I can use anything in the wiki.

  • [Solved] udev rules: serial for persistent device naming disappeared

    Hello,
    since the latest upgrade of udev and kmod I cant't mount my external e-SATA hard disk with my working udev rules.
    This is my udev rule:
    $ cat /etc/udev/rules.d/66-persistent_esata.rules
    KERNEL=="sd?1", SUBSYSTEMS=="block", ENV{ID_SERIAL_SHORT}=="S1VSJ1LS301247", NAME="aluguard"
    When plugged in, I could decrypt and mount it with "sudo cryptsetup luksOpen /dev/aluguard aluguard && mount /mnt/aluguard".
    Since the update above I get "Device /dev/aluguard doesn't exist or access denied."
    While I re-checked https://wiki.archlinux.org/index.php/Ma … _with_udev, I discovered, that the serial entry in the output of udevadm has vanished:
    $ udevadm info -a -p $(udevadm info -q path -n /dev/sdg)
    Udevadm info starts with the device specified by the devpath and then
    walks up the chain of parent devices. It prints for every device
    found, all possible attributes in the udev rules key format.
    A rule to match, can be composed by the attributes of the device
    and the attributes from one single parent device.
    looking at device '/devices/pci0000:00/0000:00:09.0/host3/target3:0:0/3:0:0:0/block/sdg':
    KERNEL=="sdg"
    SUBSYSTEM=="block"
    DRIVER==""
    ATTR{range}=="16"
    ATTR{ext_range}=="256"
    ATTR{removable}=="0"
    ATTR{ro}=="0"
    ATTR{size}=="1953525168"
    ATTR{alignment_offset}=="0"
    ATTR{discard_alignment}=="0"
    ATTR{capability}=="50"
    ATTR{stat}==" 96 24 762 780 0 0 0 0 0 780 780"
    ATTR{inflight}==" 0 0"
    ATTR{events}==""
    ATTR{events_async}==""
    ATTR{events_poll_msecs}=="-1"
    looking at parent device '/devices/pci0000:00/0000:00:09.0/host3/target3:0:0/3:0:0:0':
    KERNELS=="3:0:0:0"
    SUBSYSTEMS=="scsi"
    DRIVERS=="sd"
    ATTRS{device_blocked}=="0"
    ATTRS{type}=="0"
    ATTRS{scsi_level}=="6"
    ATTRS{vendor}=="ATA "
    ATTRS{model}=="SAMSUNG HD103SI "
    ATTRS{rev}=="1AG0"
    ATTRS{state}=="running"
    ATTRS{timeout}=="30"
    ATTRS{iocounterbits}=="32"
    ATTRS{iorequest_cnt}=="0xa2"
    ATTRS{iodone_cnt}=="0x98"
    ATTRS{ioerr_cnt}=="0xc"
    ATTRS{evt_media_change}=="0"
    ATTRS{queue_depth}=="31"
    ATTRS{queue_ramp_up_period}=="120000"
    ATTRS{queue_type}=="simple"
    looking at parent device '/devices/pci0000:00/0000:00:09.0/host3/target3:0:0':
    KERNELS=="target3:0:0"
    SUBSYSTEMS=="scsi"
    DRIVERS==""
    looking at parent device '/devices/pci0000:00/0000:00:09.0/host3':
    KERNELS=="host3"
    SUBSYSTEMS=="scsi"
    DRIVERS==""
    looking at parent device '/devices/pci0000:00/0000:00:09.0':
    KERNELS=="0000:00:09.0"
    SUBSYSTEMS=="pci"
    DRIVERS=="ahci"
    ATTRS{vendor}=="0x10de"
    ATTRS{device}=="0x0554"
    ATTRS{subsystem_vendor}=="0x1849"
    ATTRS{subsystem_device}=="0x0554"
    ATTRS{class}=="0x010601"
    ATTRS{irq}=="23"
    ATTRS{local_cpus}=="00000000,00000003"
    ATTRS{local_cpulist}=="0-1"
    ATTRS{numa_node}=="0"
    ATTRS{dma_mask_bits}=="64"
    ATTRS{consistent_dma_mask_bits}=="64"
    ATTRS{enable}=="1"
    ATTRS{broken_parity_status}=="0"
    ATTRS{msi_bus}==""
    looking at parent device '/devices/pci0000:00':
    KERNELS=="pci0000:00"
    SUBSYSTEMS==""
    DRIVERS==""
    What is the reason for this strange behaviour, and how can I get back the serial entry?
    Thank in advance!
    Last edited by indianahorst (2012-01-31 13:03:20)

    $ udevadm info -q all -n /dev/sdg1
    P: /devices/pci0000:00/0000:00:09.0/host3/target3:0:0/3:0:0:0/block/sdg/sdg1
    N: sdg1
    S: disk/by-id/ata-SAMSUNG_HD103SI_S1VSJ1LS301247-part1
    S: disk/by-id/scsi-SATA_SAMSUNG_HD103SIS1VSJ1LS301247-part1
    S: disk/by-id/wwn-0x50024e900136a03e-part1
    S: disk/by-path/pci-0000:00:09.0-scsi-3:0:0:0-part1
    S: disk/by-uuid/bb024e1b-78a5-4ed0-9e80-aaa7633aa493
    E: DEVLINKS=/dev/disk/by-id/ata-SAMSUNG_HD103SI_S1VSJ1LS301247-part1 /dev/disk/by-id/scsi-SATA_SAMSUNG_HD103SIS1VSJ1LS301247-part1 /dev/disk/by-id/wwn-0x50024e900136a03e-part1 /dev/disk/by-path/pci-0000:00:09.0-scsi-3:0:0:0-part1 /dev/disk/by-uuid/bb024e1b-78a5-4ed0-9e80-aaa7633aa493
    E: DEVNAME=/dev/sdg1
    E: DEVPATH=/devices/pci0000:00/0000:00:09.0/host3/target3:0:0/3:0:0:0/block/sdg/sdg1
    E: DEVTYPE=partition
    E: ID_ATA=1
    E: ID_ATA_DOWNLOAD_MICROCODE=1
    E: ID_ATA_FEATURE_SET_AAM=1
    E: ID_ATA_FEATURE_SET_AAM_CURRENT_VALUE=254
    E: ID_ATA_FEATURE_SET_AAM_ENABLED=1
    E: ID_ATA_FEATURE_SET_AAM_VENDOR_RECOMMENDED_VALUE=254
    E: ID_ATA_FEATURE_SET_APM=1
    E: ID_ATA_FEATURE_SET_APM_ENABLED=0
    E: ID_ATA_FEATURE_SET_HPA=1
    E: ID_ATA_FEATURE_SET_HPA_ENABLED=1
    E: ID_ATA_FEATURE_SET_PM=1
    E: ID_ATA_FEATURE_SET_PM_ENABLED=1
    E: ID_ATA_FEATURE_SET_PUIS=1
    E: ID_ATA_FEATURE_SET_PUIS_ENABLED=0
    E: ID_ATA_FEATURE_SET_SECURITY=1
    E: ID_ATA_FEATURE_SET_SECURITY_ENABLED=0
    E: ID_ATA_FEATURE_SET_SECURITY_ENHANCED_ERASE_UNIT_MIN=194
    E: ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=194
    E: ID_ATA_FEATURE_SET_SMART=1
    E: ID_ATA_FEATURE_SET_SMART_ENABLED=1
    E: ID_ATA_SATA=1
    E: ID_ATA_SATA_SIGNAL_RATE_GEN1=1
    E: ID_ATA_SATA_SIGNAL_RATE_GEN2=1
    E: ID_ATA_WRITE_CACHE=1
    E: ID_ATA_WRITE_CACHE_ENABLED=1
    E: ID_BUS=ata
    E: ID_FS_TYPE=crypto_LUKS
    E: ID_FS_USAGE=crypto
    E: ID_FS_UUID=bb024e1b-78a5-4ed0-9e80-aaa7633aa493
    E: ID_FS_UUID_ENC=bb024e1b-78a5-4ed0-9e80-aaa7633aa493
    E: ID_FS_VERSION=1
    E: ID_MODEL=SAMSUNG_HD103SI
    E: ID_MODEL_ENC=SAMSUNG\x20HD103SI\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
    E: ID_PART_ENTRY_TYPE=0x83
    E: ID_PART_TABLE_TYPE=dos
    E: ID_PATH=pci-0000:00:09.0-scsi-3:0:0:0
    E: ID_PATH_TAG=pci-0000_00_09_0-scsi-3_0_0_0
    E: ID_REVISION=1AG01131
    E: ID_SCSI_COMPAT=SATA_SAMSUNG_HD103SIS1VSJ1LS301247
    E: ID_SERIAL=SAMSUNG_HD103SI_S1VSJ1LS301247
    E: ID_SERIAL_SHORT=S1VSJ1LS301247
    E: ID_TYPE=disk
    E: ID_WWN=0x50024e900136a03e
    E: ID_WWN_WITH_EXTENSION=0x50024e900136a03e
    E: MAJOR=8
    E: MINOR=97
    E: PART_ENTRY_DISK=8:96
    E: PART_ENTRY_NUMBER=1
    E: PART_ENTRY_OFFSET=63
    E: PART_ENTRY_SCHEME=dos
    E: PART_ENTRY_SIZE=1953520002
    E: SUBSYSTEM=block
    E: UDEV_LOG=3
    E: UDISKS_PARTITION=1
    E: UDISKS_PARTITION_ALIGNMENT_OFFSET=0
    E: UDISKS_PARTITION_NUMBER=1
    E: UDISKS_PARTITION_OFFSET=32256
    E: UDISKS_PARTITION_SCHEME=mbr
    E: UDISKS_PARTITION_SIZE=1000202241024
    E: UDISKS_PARTITION_SLAVE=/sys/devices/pci0000:00/0000:00:09.0/host3/target3:0:0/3:0:0:0/block/sdg
    E: UDISKS_PARTITION_TYPE=0x83
    E: UDISKS_PRESENTATION_NOPOLICY=0
    E: USEC_INITIALIZED=6897248001
    OK, there is the serial.... but the problem persists - udev doesn't execute the rule and doesn't create /dev/aluguard.

  • Kernel 2.6.20 - device naming - all hdx devices are now sdx/srx?

    I just upgraded my Arch system (Voodoo 0.8), including the kernel to kernel26  (2.6.20.1-1)  from 2.6.17.
    I'm noticing now that all devices that used to be hdx devices (hda, hdb etc) are now either sdx or srx.
    Here's the contents of /sys/block, first for the old 2.6.17 kernel, and then with the new 2.6.20 kernel. I removed
    ramx and loopx devices from the output below for brevity and clarity.
    ls -l  /sys/block  (2.6.17)
    drwxr-xr-x  5 root root 0 Feb 28 10:38 hda
    drwxr-xr-x  5 root root 0 Feb 28 10:38 hdb
    drwxr-xr-x 15 root root 0 Feb 28 10:38 sda
    drwxr-xr-x  9 root root 0 Feb 28 15:38 sdb
    drwxr-xr-x  5 root root 0 Feb 28 15:38 sdc
    ls -l /sys/block  (2.6.20)
    drwxr-xr-x 15 root root 0 Feb 28 10:30 sda
    drwxr-xr-x  9 root root 0 Feb 28 10:31 sdb
    drwxr-xr-x  5 root root 0 Feb 28 10:31 sdc
    drwxr-xr-x  5 root root 0 Feb 28 10:30 sr0
    drwxr-xr-x  5 root root 0 Feb 28 10:30 sr1
    sda, sdb,sdc are correct - they are USB devices and shoud be sdx
    Edit:  correction: sda is a SATA hard drive (not USB)
    However hda became sr0, and hdb became sr1 (these are ATAPI CD/DVD burners)
    On another system, an IDE hard drive (normally hda) became sda.
    Since this data is taken right from /sys/block, the device naming is coming directly from the kernel and is not related to udev etc. Is everyone seeing this with 2.6.20? In other words, is this normal for the newer kernels, or is there something in the Arch config that causes this.
    All installed packages are up to date as of today (standard Voodoo 0.8 system )
    Last edited by tomp (2007-02-28 21:11:41)

    lucke wrote:http://www.archlinux.org/news/272/
    Thanks for the replies everyone....and the links
    I guess I skipped over the kernel where this change kicked in (2.6.19) so it took me by surprise.
    At least I know it's not just me having one of those days. I'm working on s special purpose live-cd (and using a modified Arch kernel on it), where the naming changes will confuse some people (not to mention me). Guess i'll have to read up on this and see what I can work out...
    Tom

  • SAN device naming conventions with EMC symmetrix

    Hi,
    How CTD are named using Solaris 8 ssd drivers ?
    Regards

    I've gotten around this by either using a symbolic link to the device or just doing a mknod to recreate the device special files so the names match across the cluster. You only need to do this for the OCR and Voting devices, you don't need consistent names for ASM.
    If you use EMC's PowerPath software the name should be synced across the nodes, if not copy the PowerPath device data files (/etc/emcp_devicesDB.dat and .idx) from 1 nod to the other nodes and reboot. This will sync up the EMC device names too...

  • [Solved] Inconsistency in device naming concerning mount/fstab

    This is not a problem that needs to be solved, but rather a gap in my understanding of a mechanism.
    I have several partitions mounted in my fstab, they are identified by UUID.
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump><pass>
    devpts /dev/pts devpts defaults 0 0
    shm /dev/shm tmpfs nodev,nosuid 0 0
    UUID=0767c51a-0ba8-405e-ac98-106182fe4d83 /tmp ext4 noexec,rw,noatime,nodiratime 0 2
    UUID=0ba14b78-1b36-4857-92ae-8b1ca41264b6 /boot ext2 defaults 0 1
    UUID=4eb07abb-25b0-4683-badf-8d556b536d9c / ext4 defaults 0 1
    UUID=e3fe5429-379b-4b6d-a01e-e30aa85784e2 /home ext4 defaults 0 1
    UUID=e7fda340-ca00-4c4c-b42e-cfba13a3abbe swap swap defaults 0 0
    UUID=e3ae11a4-b602-4ea2-bbf7-8c8c9dea52a6 /mnt/Esther ext4 defaults,rw,noatime,nodiratime 0 2
    UUID=55525a1b-386b-4390-8f47-b078b0b2c06e /mnt/Ballamb ext4 defaults,rw,noatime,nodiratime 0 2
    UUID=b71cfb8d-a4eb-4ded-a65b-fbc2db102332 /mnt/Galbadia ext4 defaults,rw,noatime,nodiratime 0 2
    When all drives are mounted, they show up as mounted by device name (/dev/sd*), only / is displayed as mounted by UUID.
    $ mount
    proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
    sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
    udev on /dev type devtmpfs (rw,nosuid,relatime,size=10240k,nr_inodes=386283,mode=755)
    run on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=10240k,mode=755)
    /dev/disk/by-uuid/4eb07abb-25b0-4683-badf-8d556b536d9c on / type ext4 (rw,relatime,barrier=1,data=ordered)
    devpts on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)
    shm on /dev/shm type tmpfs (rw,nosuid,nodev,relatime)
    /dev/sdc2 on /tmp type ext4 (rw,noexec,noatime,nodiratime)
    /dev/sda1 on /boot type ext2 (rw)
    /dev/sda4 on /home type ext4 (rw)
    /dev/sdb1 on /mnt/Esther type ext4 (rw,noatime,nodiratime)
    /dev/sdc1 on /mnt/Ballamb type ext4 (rw,noatime,nodiratime)
    /dev/sdd1 on /mnt/Galbadia type ext4 (rw,noatime,nodiratime)
    fusectl on /sys/fs/fuse/connections type fusectl (rw)
    gvfs-fuse-daemon on /home/xy/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=xy)
    $ df -h
    Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf
    udev 10M 0 10M 0% /dev
    run 10M 192K 9,9M 2% /run
    /dev/disk/by-uuid/4eb07abb-25b0-4683-badf-8d556b536d9c 68G 8,5G 56G 14% /
    shm 1,5G 4,0K 1,5G 1% /dev/shm
    /dev/sdc2 289G 194M 274G 1% /tmp
    /dev/sda1 251M 17M 222M 7% /boot
    /dev/sda4 849G 62G 745G 8% /home
    /dev/sdb1 1,8T 1,5T 223G 88% /mnt/Esther
    /dev/sdc1 1,1T 223G 810G 22% /mnt/Ballamb
    /dev/sdd1 1,8T 390G 1,4T 23% /mnt/Galbadia
    Now I feel the urge to know why. Neither the mount nor the fstab manfile gave me insight on this one. So, what's behind this?
    Last edited by Awebb (2011-10-08 17:51:26)

    Now I feel stupid for not searching properly. Solved. Thanks, karol.
    EDIT: So, in other words, if the UUID is passed by Grub, it shows as UUID in the system,
    http://projects.archlinux.org/mkinitcpi … 3afd7e0001
    So it was solved about a year ago? Well...
    Last edited by Awebb (2011-05-29 14:12:06)

  • Persistant Block Naming for USB?

    I once seen a topic on this forum about something similar to an issue I am having, evertime I reboot and put my usb in the drive letter chages thus making my fstab line useless. How would I goo about making a udev rule for usb block naming?

    tomk wrote:
    http://wiki.archlinux.org/index.php/Udev
    That's the one I had in mind.
    Ah thanks worked the way I needed it to.

  • Device naming convention for san disks

    Hi,
    Is there a way I can force a san disk to obtain a certain device name? for example if a hitachi device shows up as c6t5000000000, can make it c5t5000000000. Is there some option in /kernel/drv/fp.conf or sd.conf? Is there a way to disable one port on the Qlogic HBA? Thanks for your assistance.

    The controller number (c) in ctdt notation is assigned by the OS when it is buillt, and additional controllers added on after are added in numerical order.
    Some SANs allow you to specify the "scsi-id" (at the end of the wwpn on FC).
    This behavior can be a real pain if you move a SCSI card from slot to slot, each time it gets a new c#, also can be amusing on larger systems (e.g. F-6800) with an OS installed on a domain, that is then expanded to include more I/O devices, the c#s will not necessarily match when the expanded domain is booted from "CD".
    In the brave new world of LDOMs there is a fix ! I assign the volumes normally (resulting in different ctdt) on each server, then use DiskSuite to give each LUN the same md### , when presenting the VDIsk you can specify disk ID.
    e.g.
    server..... ctdt...................... ....... SDS ......... VDSdev.......... VDisk ...Guest sees
    primary01 c2t500000ab13t0d5 --> md21 ---> dbdev_u21 --> disk21 c0d21sx
    primary02 c3t510000ab13t0da --> md21 ---> dbdev_u21 --> disk21 c0d21sx
    Edited by: HarryC on Dec 30, 2009 10:44 AM

  • ICloud Tabs - device named Macintosh.local for MacBook Air

    When I look at iCloud Tabs I see my MacBook Air named Macintosh.local.Everything else is correct.  Where do I change how iCloud names the MacBook Air?

    Welcome to Apple Support Communities
    The name you see in iCloud Tabs is your MacBook Air's name. To change it, open System Preferences > Sharing, and type the name you want next to "Computer name"

  • Device naming and movie questions.

    I got a 80 GB video ipod for Christmas, and am still learning everything. How do I change the "name" of my ipod? I also can't figure out how to download my movies to my ipod. I would greatly appreciate any help, especially with the movies, as I am going out of town this weekend, and would like to have something to watch. Thank you for your help.

    Select your iPod in the iTunes Source list.
    Click on it's its name again.
    The text box will open for editing.
    Type a new name.
    Have a look here for more: How To Rename your iPod

  • Fixing iSight Device Naming (e.g., iSight #2, iSight #3)

    I just wanted to provide some information to follow up on an old post that has been archived, so I can't reply to it. The OP of this thread http://discussions.apple.com/thread.jspa?messageID=1432144 was complaining about swapping in and out a few different iSight cameras, resulting in his new camera being referred to as 'iSight #3' or whatever in OS X.
    I had the same problem, having purchased a bunch of iSights for family members, testing them et cetera, I was left with my own camera being referred to as 'iSight #3' in iChat AV and Skype. It still works but it's uneccessary and ugly and gnaws at my soul.
    So, I just reset the NVRAM and PRAM:
    1. Restart, hold down Command-Option-O-F before the start tone, which gets you into the Open Firmware.
    2. Type 'reset-nvram' then 'shut-down' at the prompt.
    3. Start up again, holding down Command-Option-P-R before the grey screen comes up. You should hear the tone sound, keep holding down, it's going to reboot again. After the second tone sounds, you should be all good.
    Hopefully that works for everyone else for whom this is annoying.
    Powerbook G4 15"   Mac OS X (10.4.10)  

    Welcome to  Discussions, dropbear
    Thanks for taking the time to share your solution.
    Nice find!
    Jim

  • How to create device IDs with same name

    i am using SE 3310 and its creating different device ids for each node sharing it . since I will be building a RAC enviornment I need these IDs/name to be same .
    for example  on one node the lun id is /dev/rdsk/c3t0d0s6  but the same lun id on node 2 is /dev/rdsk/c2t0d0s6.
    In past with an old storage array I fixed this issue by creating links  in /dev/rdsk for  c3t0d0s6 --->  c2t0d0s6.
    my question is : is there a way in SE3310 that device ids get created with same name or do i still have to rely on creating these soft links ?
    thanks
    Note: since i need the answer to this quickly i will wait a while and then post this question in other forums and i will update the question here with the answer .

    This could be a Solaris (I presumed) O.S. question rather than SE3310 or storage question.  
    The logical device (/dev/[r]dsk/*) is the work of the O.S. when it first configures the device,  in this case the LUN from your SE3310.   I can go in depth on how the cX number happens (due to device probe order, driver differences, history of device discovery due to need of persistent device naming, etc...) but ... it's a really long story and is really quite irrelevant and most people should not be interested...
    If you have COMPLETELY identical servers, i.e. identical hardware down to specific HBA in specific slot are the same,   and if you make sure that luns are presented to all servers exactly the same way, same order, and any changes are seen by all servers in the same sequence,  in theory,  all /dev/rdsk/* devices will be consistent across servers.
    But that's still rather irrelevant.    Application that is designed to work in a redundant environment should not be dependent on logical devices like /dev/rdsk being the same.
    So ... in effect this is also not a question for the Solaris forum,  but rather a question for those familiar with RAC,  how to configure such that device access is done "safely" through actually identifying the lun rather than assuming /dev/rdsk are consistent.

  • Raw devices problem

    Hello, I made a model on Vmware ESX for testing Oracle RAC, so it's two Centos 5.10 machines with shared disks. I'm using raw devices for ocr, voting disks and data, and without ASMLib library.
    After installing clusterware and Oracle (10gR2), everything was OK until now, when after reboot of one node, no more shared disks exist anymore. For every raw disk related comand I got an error:
    #raw -qa
    Cannot open raw device '/dev/rawctl' (No such file or directory)
    #service rawdevices restart
    Assigning raw devices:
    /dev/raw/raw1 --> /dev/sdb1
    Cannot open raw device '/dev/rawctl' (No such file or directory)
    Didn't find anything related to this in /var/log's. Could be glad if someone could explain how to fix it.

    Yes, but keep in mind that the device tree is not only rebuild after a system restart, but also the order of devices can be different, so for instance /dev/sdc1 may not be the same after a system restart if you attach or remove another device or plug in any USB. That's why UDEV should be configured to use the unique device identifier to map storage devices which require persistent device naming.
    For instance you could use the following entry to map e.g. current /dev/sdc1 to /dev/vote1
    KERNEL=="sd*", BUS=="scsi", PROGRAM=="/sbin/scsi_id", RESULT=="361a98001686f6959614a453133524171", NAME="vote1", OWNER="oracle", GROUP="oinstall", MODE="0640"
    Using raw devices is no longer necessary, not for Oracle, which uses the O_DIRECT flag when opening a device and it does not matter if it is a device or partition. But if you really want to map to raw device names, you could use the following:
    ACTION=="add", KERNEL=="sd*", PROGRAM=="/sbin/scsi_id", RESULT=="361a98001686f6959614a453133524171", RUN+="/bin/raw /dev/raw/raw1 %N"

  • Arch won't boot, FS not detected, Kernel Panic.

    Ok so here is the situation. I have arch linux installed on sda1, which is a sata drive, samsung. Seems lately I been having problems getting arch to boot because it doesn't know what type filesystem my root device has. It goes on and tells me that I can use the kernel parameter rootfstype= to solve the issue, but yet when I try this, it does nothing. I stop getting the error, about unknown FS type, but arch still won't boot. Init fails...
    I have tried everything on these forums to fix the problem and not one thing in general has solved the issue. What seems to be most consistent about this problem, is it takes me at least 20 - 30 times of rebooting before it will finally go through and boot. But, even then this is not foolproof. Last night I tried at least 30+ times of rebooting, powering off and still it would not boot.
    So after reading the forums some more I found an article somewhat related to my problem and it was suggested that I add my root FS type as a module and then remove the filesystem hook in mkinitcpio.conf. I tried this approach and at the same time downgraded to 2.6.24.2-1 kernel26 so mkinitcpio would generate the new image. Then I rebooted and arch loaded just fine. So then I rebooted and again, unknown fs type on root device error.
    So I retraced my steps and tried the same process again, only this time when I rebooted I got same problem. So as it seems, nothing I did to mkinitcpio.conf did anything to alleviate my problem.
    As of right now, I managed to get the fallback image to work(but fallback does not load all the time, just this last time I tried it it worked), but I am scared to death to turn off my machine because I know it's not gonna reboot without a lot of hassle.
    So can anyone help me diagnose this problem? What can I do to get the kernel to boot and mount the root device with ext3 and pass init on boot up? I am completely lost when it comes to this...
    here is my mkinitcpio.conf
    # vim:set ft=sh
    # MODULES
    # The following modules are loaded before any boot hooks are
    # run. Advanced users may wish to specify all system modules
    # in this array. For instance:
    # MODULES="piix ide_disk reiserfs"
    MODULES="ext3 pata_amd ata_generic sata_nv"
    # BINARIES
    # This setting includes, into the CPIO image, and additional
    # binaries a given user may wish. This is run first, so may
    # be used to override the actual binaries used in a given hook.
    # (Existing files are NOT overwritten is already added)
    # BINARIES are dependancy parsed, so you may safely ignore libraries
    BINARIES=""
    # FILES
    # This setting is similar to BINARIES above, however, files are added
    # as-is and are not parsed in anyway. This is useful for config files.
    # Some users may wish to include modprobe.conf for custom module options,
    # like so:
    # FILES="/etc/modprobe.conf"
    FILES=""
    # HOOKS
    # This is the most important setting in this file. The HOOKS control the
    # modules and scripts added to the image, and what happens at boot time.
    # Order is important, and it is recommended that you do not change the
    # order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
    # help on a given hook.
    # 'base' is _required_ unless you know precisely what you are doing.
    # 'udev' is _required_ in order to automatically load modules
    # 'modload' may be used in place of 'udev', but is not recommended
    # 'filesystems' is _required_ unless you specify your fs modules in MODULES
    # Examples:
    # This setup specifies all modules in the MODULES setting above.
    # No raid, lvm2, or encrypted root is needed.
    # HOOKS="base"
    # This setup will autodetect all modules for your system and should
    # work as a sane default
    # HOOKS="base udev autodetect pata scsi sata filesystems"
    # This is identical to the above, except the old ide subsystem is
    # used for IDE devices instead of the new pata subsystem.
    # HOOKS="base udev autodetect ide scsi sata filesystems"
    # This setup will generate a 'full' image which supports most systems.
    # No autodetection is done.
    # HOOKS="base udev pata scsi sata usb filesystems"
    # This setup assembles an pata raid array with an encrypted root FS.
    # Note: See 'mkinitcpio -H raid' for more information on raid devices.
    # HOOKS="base udev pata raid encrypt filesystems"
    # This setup loads an lvm2 volume group on a usb device.
    # HOOKS="base udev usb lvm2 filesystems"
    HOOKS="base udev autodetect pata sata"
    here is my fallback.conf
    # vim:set ft=sh
    # MODULES
    # The following modules are loaded before any boot hooks are
    # run. Advanced users may wish to specify all system modules
    # in this array. For instance:
    # MODULES="piix ide_disk reiserfs"
    # BusLogic is added to support VMWARE arch booting in fallback image
    MODULES="BusLogic"
    # BINARIES
    # This setting includes, into the CPIO image, and additional
    # binaries a given user may wish. This is run first, so may
    # be used to override the actual binaries used in a given hook.
    # (Existing files are NOT overwritten is already added)
    # BINARIES are dependancy parsed, so you may safely ignore libraries
    #BINARIES=""
    # FILES
    # This setting is similar to BINARIES above, however, files are added
    # as-is and are not parsed in anyway. This is useful for config files.
    # Some users may wish to include modprobe.conf for custom module options,
    # like so:
    # FILES="/etc/modprobe.conf"
    FILES=""
    # HOOKS
    # This is the most important setting in this file. The HOOKS control the
    # modules and scripts added to the image, and what happens at boot time.
    # Order is important, and it is recommended that you do not change the
    # order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
    # help on a given hook.
    # 'base' is _required_ unless you know precisely what you are doing.
    # 'udev' is _required_ in order to automatically load modules
    # 'modload' may be used in place of 'udev', but is not recommended
    # 'filesystems' is _required_ unless you specify your fs modules in MODULES
    # Examples:
    # This setup specifies all modules in the MODULES setting above.
    # No raid, lvm, or encrypted root is needed.
    # HOOKS="base"
    # This setup will autodetect all modules for your system and should
    # work as a sane default
    # HOOKS="base udev autodetect ide scsi sata filesystems"
    # This setup will generate a 'full' image which supports most systems.
    # No autodetection is done.
    # HOOKS="base udev ide scsi sata usb filesystems"
    # This setup assembles an ide raid array with an encrypted root FS.
    # Note: See 'mkinitcpio -H raid' for more information on raid devices.
    # HOOKS="base udev ide filesystems raid encrypt"
    # This setup loads an LVM volume group on a usb device.
    # HOOKS="base udev usb filesystems lvm"
    HOOKS="base udev ide pata scsi sata usbinput raid filesystems"
    modules I need
    sudo mkinitcpio -M
    Password:
    Modules autodetected:
    ata_generic
    libata
    pata_acpi
    pata_amd
    sata_nv
    cdrom
    ide-core
    amd74xx
    generic
    forcedeth
    sd_mod
    sr_mod
    usbcore
    ehci-hcd
    ohci-hcd
    jbd
    ext3
    Last edited by jacko (2008-04-15 19:53:35)

    I had a similar issue (I think, can you post the exact error the kernel panics with to check?) and it seemed grub or the kernel had difficulties with finding my root device which was specified as a device node in /dev. The solution for me was to change the root parameter in my kernel line in grub's menu.lst to root=/dev/disk/by-label/<label>, I'm sure UUID and such will work fine too. After doing that I haven't encountered a single such kernel panic. More info about persistent device naming can be found here.

Maybe you are looking for