Diskless client NFS boot fails. cannot create /dev/nfs

Hi
I've set up a diskless laptop to boot off my server, both running Arch. I followed the wiki article: https://wiki.archlinux.org/index.php/Di … t_NFS_root
PXE on the laptop connects with the tftpd server just fine, gets the kernel and begins booting up. At some point it begins looking for /dev/nfs, declares it does not exist, attempts to create it and and fails with the following error (from memory as I'm not at the computer now).
"ERROR: Unable to determine major/minor number of root device root=/dev/nfs"
my kernel param line in pxelinux.cfg/default is just like the one in the wiki article i.e
default linux
label linux
kernel vmlinuz26
append initrd=kernel26.img rootfstype=nfs root=/dev/nfs nfsroot=10.0.0.1:/disklessroot,v3,rsize=16384,wsize=16384 ip=::::::dhcp
any help will be greatly appreciated.
emk

I'm assuming youve entered your own IP addresses instead of just copy&pasting from the howto, correct?
Also, did you install all the nfs packages, and do the mkinitcpio-nfs-utils procedure?

Similar Messages

  • Zones not booting - failed to create devlinks: Interrupted system call

    I just installed the latest 10_Recommended cluster with 118833-36 kernel patch and now my zones won't boot. I get the error:
    (root)Yes Master?> zoneadm list -iv
    ID NAME STATUS PATH
    0 global running /
    - samba installed /export/home/zones/samba
    - web installed /export/home/zones/web
    - dhcp installed /export/home/zones/dhcp
    - dns installed /export/home/zones/dns
    - vs1 installed /zdata/zones/vs1
    - dss installed /zdata/zones/dss
    - test installed /zdata/zones/test
    (root)Yes Master?> zoneadm -z test boot
    failed to create devlinks: Interrupted system call
    console setup: device initialization failed
    zoneadm: zone 'test': could not start zoneadmd
    zoneadm: zone 'test': call to zoneadmd failed
    Also, running devfsadm or drvconfig;devlinks from the global zone will core dump.
    Any ideas..??
    tia..

    First, you gotta change your prompt to something less embarrassing when you post to a public forum :)
    I'd forget about the zones problem and focus on why devfsadm core dumps -- that's the core of the problem (no pun intended...no, really!).
    First, review the install logs of all the patches installed during the recent service (/var/sadm/patch/*/log). Even if they all show a good completion, check the messages they generated, sometimes they have errors that aren't bad enough to cause a complete failure of the patch. The KJP (118833-36) is probably a good one to start with.
    Next I'd "truss" the devfsadm command while it core dumps then get a stack trace of the core (run "adb <corefile>" and type "$C" -- that's old school, I'm sure mdb is much cooler...).
    Throw some of the strings from those against sunsolve and see if something sticks.
    Good luck!

  • Incomplete Client Install OSD - Failed to create instance if Software Execution Request Managerr. 0x80070005

    I am using an imaging task sequence and getting a
    0x80070005 error.  IT seems that the SCCM client
    doesn’t complete correctly and actions are missing from the client.
    Below is the log information.  I am not sure if a reboot is causing the issue?
    <![LOG[Path variable _SMSTSBootStagePath converted from C:\_SMSTaskSequence\WinPE to F05092C70000100000000000:\_SMSTaskSequence\WinPE]LOG]!><time="09:40:56.205+300" date="04-07-2014" component="TSManager" context=""
    type="1" thread="2244" file="resolvesource.cpp:1597">
    <![LOG[Updated security on object C:\_SMSTaskSequence.]LOG]!><time="09:40:56.237+300" date="04-07-2014" component="TSManager" context="" type="1" thread="2244" file="utils.cpp:1704">
    <![LOG[Set a global environment variable _SMSTSNextInstructionPointer=12]LOG]!><time="09:40:56.237+300" date="04-07-2014" component="TSManager" context="" type="0" thread="2244" file="executionenv.cxx:668">
    <![LOG[Set a TS execution environment variable _SMSTSNextInstructionPointer=12]LOG]!><time="09:40:56.237+300" date="04-07-2014" component="TSManager" context="" type="0" thread="2244"
    file="executionenv.cxx:386">
    <![LOG[Set a global environment variable _SMSTSInstructionStackString=8]LOG]!><time="09:40:56.237+300" date="04-07-2014" component="TSManager" context="" type="0" thread="2244" file="executionenv.cxx:668">
    <![LOG[Set a TS execution environment variable _SMSTSInstructionStackString=8]LOG]!><time="09:40:56.237+300" date="04-07-2014" component="TSManager" context="" type="0" thread="2244" file="executionenv.cxx:414">
    <![LOG[Save the current environment block]LOG]!><time="09:40:56.237+300" date="04-07-2014" component="TSManager" context="" type="0" thread="2244" file="executionenv.cxx:833">
    <![LOG[Expand a string: %_SMSTSMDataPath%\Logs]LOG]!><time="09:40:56.268+300" date="04-07-2014" component="TSManager" context="" type="0" thread="2244" file="executionenv.cxx:782">
    <![LOG[_SMSTSReturnToGINA variable set to true]LOG]!><time="09:41:56.381+300" date="04-07-2014" component="TSManager" context="" type="1" thread="2244" file="engine.cxx:936">
    <![LOG[Skipped Reboot System]LOG]!><time="09:41:56.381+300" date="04-07-2014" component="TSManager" context="" type="1" thread="2244" file="engine.cxx:940">
    <![LOG[The action (Restart Computer) initiated a reboot request]LOG]!><time="09:41:56.381+300" date="04-07-2014" component="TSManager" context="" type="1" thread="2244" file="engine.cxx:277">
    <![LOG[MP server http://XXXXXXXXXXX. Ports 80,443. CRL=false.]LOG]!><time="09:41:56.381+300" date="04-07-2014" component="TSManager" context="" type="1" thread="2244"
    file="utils.cpp:5881">
    <![LOG[Setting authenticator]LOG]!><time="09:41:56.396+300" date="04-07-2014" component="TSManager" context="" type="1" thread="2244" file="utils.cpp:5903">
    <![LOG[Set authenticator in transport]LOG]!><time="09:41:56.396+300" date="04-07-2014" component="TSManager" context="" type="0" thread="2244" file="libsmsmessaging.cpp:7734">
    <![LOG[Sending StatusMessage]LOG]!><time="09:41:56.428+300" date="04-07-2014" component="TSManager" context="" type="1" thread="2244" file="libsmsmessaging.cpp:4023">
    <![LOG[Setting message signatures.]LOG]!><time="09:41:56.443+300" date="04-07-2014" component="TSManager" context="" type="0" thread="2244" file="libsmsmessaging.cpp:1295">
    <![LOG[Setting the authenticator.]LOG]!><time="09:41:56.443+300" date="04-07-2014" component="TSManager" context="" type="0" thread="2244" file="libsmsmessaging.cpp:1325">
    <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: XXXXXXXXXX:80  CCM_POST /ccm_system/request]LOG]!><time="09:41:56.443+300" date="04-07-2014" component="TSManager" context="" type="1" thread="2244"
    file="libsmsmessaging.cpp:8604">
    <![LOG[Request was successful.]LOG]!><time="09:41:56.474+300" date="04-07-2014" component="TSManager" context="" type="0" thread="2244" file="libsmsmessaging.cpp:8939">
    <![LOG[****************************************************************************]LOG]!><time="09:41:56.490+300" date="04-07-2014" component="TSManager" context="" type="1" thread="2244"
    file="tsmanager.cpp:925">
    <![LOG[Execution engine result code: Reboot (2)]LOG]!><time="09:41:56.490+300" date="04-07-2014" component="TSManager" context="" type="2" thread="2244" file="tsmanager.cpp:931">
    <![LOG[Process completed with exit code 2147945410]LOG]!><time="09:41:56.521+300" date="04-07-2014" component="TSMBootstrap" context="" type="1" thread="2352" file="commandline.cpp:1123">
    <![LOG[Exiting with return code 0x80070BC2]LOG]!><time="09:41:56.521+300" date="04-07-2014" component="TSMBootstrap" context="" type="1" thread="2352" file="tsmbootstrap.cpp:1238">
    <![LOG[Process completed with exit code 2147945410]LOG]!><time="09:41:56.537+300" date="04-07-2014" component="OSDSetupHook" context="" type="1" thread="2144" file="commandline.cpp:1123">
    <![LOG[Task sequence requested a reboot]LOG]!><time="09:41:56.537+300" date="04-07-2014" component="OSDSetupHook" context="" type="1" thread="2144" file="basesetuphook.cpp:1580">
    <![LOG[Terminating system message loop.]LOG]!><time="09:41:56.553+300" date="04-07-2014" component="OSDSetupHook" context="" type="0" thread="2168" file="debugwindow.cpp:222">
    <![LOG[Restoring original desktop wallpaper.]LOG]!><time="09:41:56.568+300" date="04-07-2014" component="OSDSetupHook" context="" type="0" thread="2144" file="wallpaperselector.cpp:139">
    <![LOG[::SystemParametersInfoW( 0x0014, 0, (LPVOID)m_sOriginalWallpaper.c_str(), 0x0002 | 0x0001 ), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\osdgina\wallpaperselector.cpp,162)]LOG]!><time="09:41:56.568+300" date="04-07-2014"
    component="OSDSetupHook" context="" type="0" thread="2144" file="wallpaperselector.cpp:162">
    <![LOG[Failed to set log directory. Some execution history may be lost.
    The system cannot find the file specified. (Error: 80070002; Source: Windows)]LOG]!><time="09:43:40.359+300" date="04-07-2014" component="OSDSetupHook" context="" type="3" thread="840" file="osdsetuphook.cpp:192">
    <![LOG[Executing task sequence]LOG]!><time="09:43:40.375+300" date="04-07-2014" component="OSDSetupHook" context="" type="1" thread="840" file="osdsetuphook.cpp:279">
    <![LOG[Task Sequence environment not found.]LOG]!><time="09:43:40.390+300" date="04-07-2014" component="OSDSetupHook" context="" type="1" thread="840" file="basesetuphook.cpp:1450">
    <![LOG[Attempting to get active request.]LOG]!><time="09:43:40.390+300" date="04-07-2014" component="OSDSetupHook" context="" type="1" thread="840" file="basesetuphook.cpp:48">
    <![LOG[Failed to create instance if Software Execution Request Managerr. 0x80070005]LOG]!><time="09:43:40.437+300" date="04-07-2014" component="OSDSetupHook" context="" type="1" thread="840"
    file="basesetuphook.cpp:57">
    <![LOG[Waiting for ccmexec process to start.]LOG]!><time="09:43:40.437+300" date="04-07-2014" component="OSDSetupHook" context="" type="1" thread="840" file="basesetuphook.cpp:58">
    <![LOG[Failed to create instance if Software Execution Request Managerr. 0x80070005]LOG]!><time="09:43:46.257+300" date="04-07-2014" component="OSDSetupHook" context="" type="1" thread="840"
    file="basesetuphook.cpp:57">
    <![LOG[Waiting for ccmexec process to start.]LOG]!><time="09:43:46.257+300" date="04-07-2014" component="OSDSetupHook" context="" type="1" thread="840" file="basesetuphook.cpp:58">
    <![LOG[Failed to create instance if Software Execution Request Managerr. 0x80070005]LOG]!><time="09:43:51.257+300" date="04-07-2014" component="OSDSetupHook" context="" type="1" thread="840"
    file="basesetuphook.cpp:57">
    <![LOG[Waiting for ccmexec process to start.]LOG]!><time="09:43:51.257+300" date="04-07-2014" component="OSDSetupHook" context="" type="1" thread="840" file="basesetuphook.cpp:58">
    <![LOG[Failed to create instance if Software Execution Request Managerr. 0x80070005]LOG]!><time="09:43:56.257+300" date="04-07-2014" component="OSDSetupHook" context="" type="1" thread="840"
    file="basesetuphook.cpp:57">
    <![LOG[Waiting for ccmexec process to start.]LOG]!><time="09:43:56.257+300" date="04-07-2014" component="OSDSetupHook" context="" type="1" thread="840" file="basesetuphook.cpp:58">
    <![LOG[Failed to create instance if Software Execution Request Managerr. 0x80070005]LOG]!><time="09:44:01.257+300" date="04-07-2014" component="OSDSetupHook" context="" type="1" thread="840"
    file="basesetuphook.cpp:57">
    <![LOG[Waiting for ccmexec process to start.]LOG]!><time="09:44:01.257+300" date="04-07-2014" component="OSDSetupHook" context="" type="1" thread="840" file="basesetuphook.cpp:58">
    <![LOG[GetActiveRequest failed with error code 0x87d01012]LOG]!><time="09:44:07.804+300" date="04-07-2014" component="OSDSetupHook" context="" type="3" thread="840" file="basesetuphook.cpp:66">
    <![LOG[GetActiveRequest failed. 0x87D01012.]LOG]!><time="09:44:07.804+300" date="04-07-2014" component="OSDSetupHook" context="" type="3" thread="840" file="basesetuphook.cpp:83">
    <![LOG[ReleaseActiveRequest failed. 0x87d01012.]LOG]!><time="09:44:07.804+300" date="04-07-2014" component="OSDSetupHook" context="" type="3" thread="840" file="basesetuphook.cpp:122">
    <![LOG[Deleting SMS_MaintenanceTaskRequests istance: SMS_MaintenanceTaskRequests.TaskID="{11EB4952-7CDD-45D5-BD6F-DA65E193E04F}".]LOG]!><time="09:44:07.835+300" date="04-07-2014" component="OSDSetupHook"
    context="" type="1" thread="840" file="basesetuphook.cpp:144">
    <![LOG[Removed 1 instance of SMS_MaintenanceTaskRequests for tasksequence.]LOG]!><time="09:44:07.835+300" date="04-07-2014" component="OSDSetupHook" context="" type="1" thread="840" file="basesetuphook.cpp:155">
    <![LOG[Uninstalling Setup Hook]LOG]!><time="09:44:07.835+300" date="04-07-2014" component="OSDSetupHook" context="" type="1" thread="840" file="basesetuphook.cpp:1628">
    <![LOG[Removing setup hook from registry.]LOG]!><time="09:44:07.835+300" date="04-07-2014" component="OSDSetupHook" context="" type="0" thread="840" file="vistasetuphook.cpp:143">
    <![LOG[Successfully removed C:\WINDOWS\system32\OSDGINA.DLL]LOG]!><time="09:44:07.835+300" date="04-07-2014" component="OSDSetupHook" context="" type="1" thread="840" file="basesetuphook.cpp:1321">
    <![LOG[Successfully removed C:\WINDOWS\system32\OSDSETUPHOOK.EXE]LOG]!><time="09:44:07.835+300" date="04-07-2014" component="OSDSetupHook" context="" type="1" thread="840" file="basesetuphook.cpp:1321">
    <![LOG[Successfully removed C:\WINDOWS\system32\_SMSOSDSetup]LOG]!><time="09:44:07.835+300" date="04-07-2014" component="OSDSetupHook" context="" type="1" thread="840" file="basesetuphook.cpp:1358">

    You are starting the OSD from Full OS? Is there Bitlocker enabled on the machine you're trying to re-install? Could you post a screenshot of your Task Sequence?

  • Import fails (cannot create initial extent)

    I am running an import (using the interactive screen, and importing 1 user only)
    After creating a couple of tables, the import starts failing with "cannot create initial extent" errors.
    When I look at the free space, the tablespace I am importing into, has no free space left.
    What I don't understand, is that - I created this tablespace exactly the same size, as the tablespace I exported from (on a remote system). Source=4Gb, Target=4Gb
    Why is this happening ?

    I was never faced with that issue before so I am just guessing...
    Did you create the tablespace with the same initial/next extent values?
    Also, have you tried setting the tablespace to autoextend? It will not answer the "why", but it will at least allow you to see how much larger that tablespace needs to be and let the import finish.

  • [Solved] Can't boot; udev not creating /dev/disk/

    After doing a system upgrade I can no longer boot.  I get the message that /dev/disk/by-uuid/{device id} cannot be found.  (There is no /dev/disk/ path at all).  I tried changing the grub boot path to dev/sdaX, but /dev/sda?? are also not created.
    I have a Fedora rescue CD lying around, and if I boot from that I can see and mount the boot device (/dev/disk/by-uuid/ is created), so I don't think it's a hardware issue.
    Last edited by rhodie (2012-03-20 18:26:53)

    Booting from a NetInstaller CD worked.
    A couple of notes in case others have the same issue.
    I had to turn on networking before I could run pacman.  I turned on networking by issuing these commands (not sure of the proper order for them or if they're all necessary, but it worked):
    /etc/rc.d/networking start
    ip link set eth0 up
    dhcpd
    I then ran through the steps listed at https://wiki.archlinux.org/index.php/Pa … nger_boot.  , but I got errors on "mkinitcpio -p linux" so I added "pacman -S linux," which seemed to include mkinitcpio, but I ran mkinitcpio again afterwards just to be sure and got no errors.
    Last edited by rhodie (2012-03-20 16:09:20)

  • [SOLVED] Cannot create /dev/loop0

    I am trying to create an encrypted loopback device.
    Firstly, I created a file using
    dd if=/dev/urandom of=./bigsecret bs=1M count=200
    Then, created a /dev/loop0 using
    losetup /dev/loop0 ./bigsecret
    Then these two commands:
    cryptsetup luksFormat /dev/loop0
    cryptsetup luksOpen /dev/loop0 secret
    After that the expected behavior is to see a new file secret in /dev/mapper but I am not getting that. I am following the wiki https://wiki.archlinux.org/index.php/Sy … filesystem
    EDIT: It seems like the loop0 was not being created and the losetup command was failing silently. Fixed now.
    Last edited by shadyabhi (2012-06-15 14:20:59)

    Something really bizarre is happening, when I run strace ln ../file file then it creates a hard link, but when I just run ln ../file file then it creates a soft link.
    Perhaps there is an alias somewhere? I think that is the case.
    Yes, that is correct.
    I feel dumb now
    But there's the answer to anyone who ever wants to know!

  • Boot fails due to /dev/sdb not showing up after update

    For some reason, my secondary hard disk has stopped being detected after I updated my Arch Linux machine today.  This machine has not been updated for about a year (I have been away).  Basically, /dev/sdb* is not in /dev/.  There is only /dev/sda*.
    The current kernel installed is 2.6.39.
    The error I get on boot is when it tries to detect the hard drives.  I would try to provide a log file, however every time I try to plug in a USB stick, it says that it is disabling IRQ #10, and it won't start the network so I can't ssh the information to any other computer.  I can log in by removing sdb from the fstab, so I will try to get /var/log/messages on here later.
    I am using udev to detect my hard drives on startup.
    Anybody know how to fix this problem?
    I can log in perfectly fine if I remove any mention of sdb from my /etc/fstab.
    Thank-you in advance for your help,
    kev717.
    Last edited by kev717 (2011-07-17 01:49:12)

    Assuming you have a BIOS based computer, have you tried the BIOS configuration program to see if the drive is detected by the BIOS ?

  • Cannot create tape device

    Hi, maybe someone can help me?
    My tape device /dev/rmt/0n was 20Gb in size even though it had no tape in it, after a failed backup.
    This was after filling up my hard-drive to 100% capacity, so I decided to delete /dev/rmt/0n and recreate using "devfsadm" or "boot -r" but neither of these commands worked!
    Now I cannot connect the tape drive at all as I cannot create /dev/rmt/0n.
    Does anybody know how this can be fixed?
    Thanks

    My tape device /dev/rmt/0n was 20Gb in size even
    though it had no tape in it, after a failed backup.Sound like you mis-specified the destination of your backup and it literally went to a file "/dev/rmt/0n" (overwriting your device file) instead of to tape.
    Please run 'drvconfig' then 'tapes'. (Or do a reconfiguration reboot.) This should recreate your device name.

  • JNI : cannot create JVM

    Hello everybody, sorry to bother all of you.
    I got problem with the JNI.
    I'm creating a Windows service that invoking a Java-based server via JNI.
    I'm copying the source from the JNI tutorial (from sun), and the problem is:
    res = JNI_CreateJavaVM(&jvm, (void **)&env, &vm_args);
    res will result < 0, means it failed/cannot create Java VM.
    I read on JNI tutorial that said the problem is because it cannot locate the JVM, or in other words, it cannot found the java library.
    I'm using JDK 1.4.1_01 now, and Microsoft Visual C++.
    I'm installing the JDK under "C:\Java\J2SE"
    and I'm compile the c program inside "C:\Program Files\Microsoft Visual Studio\VC98\Bin", and I'm also copied the JVM.DLL into this directory, since it's needed when i'm running the exe file.
    I already set the vm_args.version into JNI_VERSION_1_4 (0x00010004)
    Does anybody know the workaround about this problem?
    what directory should I put into vm_args.classpath? is it ".;C:\Java\J2SE\lib" ?
    Thanks anyway.
    Regards,
    Loekito

    Here's some stuff I can tell you.
    1. dont copy the JVM.dll anywhere. Use the registry to find out where it is installed and then load it dynamically.
    2. look at the laucnher directory in the src.zip file in the j2sdk. there are some examples in there you should find handy.

  • S10u 7 - smpatch in BE fails - patchadd: /dev/null: cannot create

    Solaris 10 5/09 s10x_u7wos_08 X86 with ZFS Root + Zones
    smpatch on non active BE with Zones fails:
    # smpatch update -b s10x_u7wos_08p1
    Ckecking the currently running boot enviornment ...
    Currently running boot enviornment name is [s10x_u7wos_08p].
    Checking the destination boot environment [s10x_u7wos_08p1] ...
    Installing patches from /var/sadm/spool...
    Copying the currently running BE into inactive BE [s10x_u7wos_08p1] ...
    (This process will take some time, please wait a moment.)
    Installing update(s) onto the inactive boot environment [s10x_u7wos_08p1] ...
    Failed to install patch 119901-07.
    Utility used to install the update failed with exit code 1.
    System has findroot enabled GRUBNo entry for BE <s10x_u7wos_08p1> in GRUB menuValidating the contents of the media </var/sadm/spool/119901-07.jar.dir>.The media contains
    1 software patches that can be added.All 1 patches will be added because you did not specify any specific patches to add.Mounting the BE <s10x_u7wos_08p1>.Adding patche
    s to the BE <s10x_u7wos_08p1>.Validating patches...Loading patches installed on the system...Done!Loading patches requested to install.Done!Checking patches that you spe
    cified for installation.Done!Approved patches will be installed in this order:119901-07 Preparing checklist for non-global zone check...Checking non-global zones...This
    patch passes the non-global zone check.119901-07 Summary for zones:Zone master-templateRejected patches:None.Patches that passed the dependency check:119901-07 Zone mast
    er-template-cloneRejected patches:None.Patches that passed the dependency check:119901-07 Patching global zoneAdding patches...Checking installed patches...Verifying suf
    ficient filesystem capacity (dry run method)...Installing patch packages...Patch 119901-07 has been successfully installed.See /a/var/sadm/patch/119901-07/log for detail
    sPatch packages installed: SUNWPython SUNWTiff SUNWTiff-devel SUNWgnome-img-viewer-shareDone!Patching non-global zones...Patching zone master-templateAdding patches.
    ..Checking installed patches...Patchadd is terminating.Done!Unmounting the BE <s10x_u7wos_08p1>.The patch add to the BE <s10x_u7wos_08p1> failed (with result code <8>).
    /usr/lib/patch/patchadd[4]: /dev/null: cannot create/usr/lib/patch/patchadd[6]: /dev/null: cannot createsort: insufficient available file descriptorsPatch 119901-07 fail
    ed in non-global zone SUNWlu-master-template.Patch 119901-07 wasn't installed in zones:master-template-clone
    Failed to install patch 119901-07.
    ALERT: Failed to install patch 119901-07.
    Any ideas?
    TIA.
    /phs
    Peter H. Seybold

    Post your question in the Developer Forums:
    http://discussions.apple.com/category.jspa?categoryID=164

  • After boot can't mount SDS file systems on 3300 mount: cannot mount /dev/md

    Hi
    I have a SUNW,Netra-440 with two SE 3300 SCSI each with two controllers. The server was working fine but after a boot, it can not see the metadevices stored in the 3300.
    I have tried restarting the SE3300 and a boot -r from ok prompt but I still can see those disks or partitions.
    Metaset Import
    metaset: log01: setname "appvol": no such set
    mount all SVM filesystems for group appvol
    mount: No such device
    mount: cannot mount /dev/md/appvol/dsk/d101
    mount: No such device
    mount: cannot mount /dev/md/appvol/dsk/d102
    mount: No such device
    mount: cannot mount /dev/md/appvol/dsk/d103
    mount: No such device
    mount: cannot mount /dev/md/appvol/dsk/d104
    mount: No such device
    mount: cannot mount /dev/md/appvol/dsk/d105
    mount: No such device
    mount: cannot mount /dev/md/appvol/dsk/d106
    metaset: log01: setname "dbvol": no such set
    mount all SVM filesystems for group dbvol
    mount: No such device
    mount: cannot mount /dev/md/dbvol/dsk/d107
    mount: No such device
    mount: cannot mount /dev/md/dbvol/dsk/d108
    i can see the devices in /dev/md/appvol but i can't mount them.
    Any ideas what this could be? using metaset shows nothing, metastat -s dbvol hangs.
    Am I missing some patch or am I missing something here? is the SE3300 damaged? or is it a problem with SDS (solstice). I have solaris 9.
    The system was working fine until we had to boot and power off to perform power tests in the rack.
    thanks
    Ryck
    this is the output of prtdiag
    root@log01 >prtdiag
    System Configuration: Sun Microsystems sun4u Netra 440
    System clock frequency: 177 MHZ
    Memory size: 8GB
    ==================================== CPUs ====================================
    E$ CPU CPU Temperature
    CPU Freq Size Implementation Mask Die Amb. Status Location
    0 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4 - - online -
    1 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4 - - online -
    2 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4 - - online -
    3 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4 - - online -
    ================================= IO Devices =================================
    Bus Freq Slot + Name +
    Type MHz Status Path Model
    pci 66 PCI5 scsi-pci1000,30 (scsi-2) LSI,1030
    okay /pci@1c,600000/scsi@1
    pci 66 PCI5 scsi-pci1000,30 (scsi-2) LSI,1030
    okay /pci@1c,600000/scsi@1,1
    pci 66 MB pci108e,abba (network) SUNW,pci-ce
    okay /pci@1c,600000/network@2
    pci 66 PCI4 scsi-pci1000,30 (scsi-2) LSI,1030
    okay /pci@1d,700000/scsi@1
    pci 66 PCI4 scsi-pci1000,30 (scsi-2) LSI,1030
    okay /pci@1d,700000/scsi@1,1
    pci 66 PCI2 pci100b,35 (network) SUNW,pci-x-qge
    okay /pci@1d,700000/pci@2/network@0
    pci 66 PCI2 pci100b,35 (network) SUNW,pci-x-qge
    okay /pci@1d,700000/pci@2/network@1
    pci 66 PCI2 pci100b,35 (network) SUNW,pci-x-qge
    okay /pci@1d,700000/pci@2/network@2
    pci 66 PCI2 pci100b,35 (network) SUNW,pci-x-qge
    okay /pci@1d,700000/pci@2/network@3
    pci 33 MB isa/su (serial)
    okay /pci@1e,600000/isa@7/serial@0,3f8
    pci 33 MB isa/su (serial)
    okay /pci@1e,600000/isa@7/serial@0,2e8
    pci 33 MB isa/rmc-comm-rmc_comm (seria+
    okay /pci@1e,600000/isa@7/rmc-comm@0,3e8
    pci 33 PCI0 SUNW,XVR-100 (display) SUNW,375-3290
    okay /pci@1e,600000/SUNW,XVR-100
    pci 33 MB pciclass,0c0310 (usb)
    okay /pci@1e,600000/usb@a
    pci 33 MB pciclass,0c0310 (usb)
    okay /pci@1e,600000/usb@b
    pci 33 MB pci10b9,5229 (ide)
    okay /pci@1e,600000/ide@d
    pci 66 MB pci108e,abba (network) SUNW,pci-ce
    okay /pci@1f,700000/network@1
    pci 66 MB scsi-pci1000,30 (scsi-2) LSI,1030
    okay /pci@1f,700000/scsi@2
    pci 66 MB scsi-pci1000,30 (scsi-2) LSI,1030
    okay /pci@1f,700000/scsi@2,1
    ============================ Memory Configuration ============================
    Segment Table:
    Base Address Size Interleave Factor Contains
    0x0 2GB 4 BankIDs 0,1,2,3
    0x1000000000 2GB 4 BankIDs 16,17,18,19
    0x2000000000 2GB 4 BankIDs 32,33,34,35
    0x3000000000 2GB 4 BankIDs 48,49,50,51
    Bank Table:
    Physical Location
    ID ControllerID GroupID Size Interleave Way
    0 0 0 512MB 0,1,2,3
    1 0 1 512MB
    2 0 1 512MB
    3 0 0 512MB
    16 1 0 512MB 0,1,2,3
    17 1 1 512MB
    18 1 1 512MB
    19 1 0 512MB
    32 2 0 512MB 0,1,2,3
    33 2 1 512MB
    34 2 1 512MB
    35 2 0 512MB
    48 3 0 512MB 0,1,2,3
    49 3 1 512MB
    50 3 1 512MB
    51 3 0 512MB
    Memory Module Groups:
    ControllerID GroupID Labels Status
    0 0 C0/P0/B0/D0
    0 0 C0/P0/B0/D1
    0 1 C0/P0/B1/D0
    0 1 C0/P0/B1/D1
    1 0 C1/P0/B0/D0
    1 0 C1/P0/B0/D1
    1 1 C1/P0/B1/D0
    1 1 C1/P0/B1/D1
    2 0 C2/P0/B0/D0
    2 0 C2/P0/B0/D1
    2 1 C2/P0/B1/D0
    2 1 C2/P0/B1/D1
    3 0 C3/P0/B0/D0
    3 0 C3/P0/B0/D1
    3 1 C3/P0/B1/D0
    3 1 C3/P0/B1/D1
    root@log01 >

    Hi,
    thanks for your answer.
    Yes format displays the physical devices, but metadb -i only shows the internal disks of the netra 440, not the ones in the 3320. metadb -s dbvol -i doesnt show anything.
    metaset which is supposed to show me the metadevices, says the program is not registered.
    cat /etc/lvm/md.tab has the configuration but since the scsi can be seen, the devices aren't mounted.
    Any suggestions?
    Cheers
    Oscar
    Searching for disks...done
    AVAILABLE DISK SELECTIONS:
    0. c1t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> bootdisk
    /pci@1f,700000/scsi@2/sd@0,0
    1. c1t1d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> bootmirr
    /pci@1f,700000/scsi@2/sd@1,0
    2. c1t2d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> spare1
    /pci@1f,700000/scsi@2/sd@2,0
    3. c1t3d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> spare2
    /pci@1f,700000/scsi@2/sd@3,0
    4. c2t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> appvol
    /pci@1c,600000/scsi@1/sd@8,0
    5. c2t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol01
    /pci@1c,600000/scsi@1/sd@9,0
    6. c2t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol02
    /pci@1c,600000/scsi@1/sd@a,0
    7. c2t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol03
    /pci@1c,600000/scsi@1/sd@b,0
    8. c2t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol04
    /pci@1c,600000/scsi@1/sd@c,0
    9. c2t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol05
    /pci@1c,600000/scsi@1/sd@d,0
    10. c3t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol06
    /pci@1c,600000/scsi@1,1/sd@8,0
    11. c3t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free1
    /pci@1c,600000/scsi@1,1/sd@9,0
    12. c3t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free2
    /pci@1c,600000/scsi@1,1/sd@a,0
    13. c3t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free3
    /pci@1c,600000/scsi@1,1/sd@b,0
    14. c3t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> hotAPP
    /pci@1c,600000/scsi@1,1/sd@c,0
    15. c3t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> hotDB
    /pci@1c,600000/scsi@1,1/sd@d,0
    16. c4t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> APPVOLm
    /pci@1d,700000/scsi@1/sd@8,0
    17. c4t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
    /pci@1d,700000/scsi@1/sd@9,0
    18. c4t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
    /pci@1d,700000/scsi@1/sd@a,0
    19. c4t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
    /pci@1d,700000/scsi@1/sd@b,0
    20. c4t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
    /pci@1d,700000/scsi@1/sd@c,0
    21. c4t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
    /pci@1d,700000/scsi@1/sd@d,0
    22. c5t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> d6Mirr
    /pci@1d,700000/scsi@1,1/sd@8,0
    23. c5t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free1M
    /pci@1d,700000/scsi@1,1/sd@9,0
    24. c5t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free2M
    /pci@1d,700000/scsi@1,1/sd@a,0
    25. c5t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free3M
    /pci@1d,700000/scsi@1,1/sd@b,0
    26. c5t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
    /pci@1d,700000/scsi@1,1/sd@c,0
    27. c5t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> hotDBm
    /pci@1d,700000/scsi@1,1/sd@d,0
    root@log01 >metadb -i
    flags first blk block count
    a m p luo 16 8192 /dev/dsk/c1t0d0s7
    a p luo 8208 8192 /dev/dsk/c1t0d0s7
    a p luo 16400 8192 /dev/dsk/c1t0d0s7
    a p luo 16 8192 /dev/dsk/c1t1d0s7
    a p luo 8208 8192 /dev/dsk/c1t1d0s7
    a p luo 16400 8192 /dev/dsk/c1t1d0s7
    r - replica does not have device relocation information
    o - replica active prior to last mddb configuration change
    u - replica is up to date
    l - locator for this replica was read successfully
    c - replica's location was in /etc/lvm/mddb.cf
    p - replica's location was patched in kernel
    m - replica is master, this is replica selected as input
    W - replica has device write errors
    a - replica is active, commits are occurring to this replica
    M - replica had problem with master blocks
    D - replica had problem with data blocks
    F - replica had format problems
    S - replica is too small to hold current data base
    R - replica had device read errors
    root@log01 >
    root@log01 >metadb -i
    flags first blk block count
    a m p luo 16 8192 /dev/dsk/c1t0d0s7
    a p luo 8208 8192 /dev/dsk/c1t0d0s7
    a p luo 16400 8192 /dev/dsk/c1t0d0s7
    a p luo 16 8192 /dev/dsk/c1t1d0s7
    a p luo 8208 8192 /dev/dsk/c1t1d0s7
    a p luo 16400 8192 /dev/dsk/c1t1d0s7
    r - replica does not have device relocation information
    o - replica active prior to last mddb configuration change
    u - replica is up to date
    l - locator for this replica was read successfully
    c - replica's location was in /etc/lvm/mddb.cf
    p - replica's location was patched in kernel
    m - replica is master, this is replica selected as input
    W - replica has device write errors
    a - replica is active, commits are occurring to this replica
    M - replica had problem with master blocks
    D - replica had problem with data blocks
    F - replica had format problems
    S - replica is too small to hold current data base
    R - replica had device read errors
    root@log01 >metadb -s appvol -i
    metadb: log01: setname "appvol": no such set
    root@log01 >metaset
    metaset: log01: metad client create: RPC: Program not registered
    root@log01 >cat /etc/lvm/md.tab
    # Copyright 2002 Sun Microsystems, Inc. All rights reserved.
    # Use is subject to license terms.
    # ident "@(#)md.tab 2.4 02/01/29 SMI"
    # md.tab
    # metainit utility input file.
    dbvol/d57 1 1 c2t12d0s0
    dbvol/d58 1 1 c4t12d0s0
    dbvol/d4 -m dbvol/d57 dbvol/d58 1
    dbvol/d55 1 1 c2t11d0s0
    dbvol/d56 1 1 c4t11d0s0
    dbvol/d3 -m dbvol/d55 dbvol/d56 1
    dbvol/d61 1 1 c3t8d0s0
    dbvol/d62 1 1 c5t8d0s0
    dbvol/d6 -m dbvol/d61 dbvol/d62 1
    dbvol/d59 1 1 c2t13d0s0
    dbvol/d60 1 1 c4t13d0s0
    dbvol/d5 -m dbvol/d59 dbvol/d60 1
    dbvol/d53 1 1 c2t10d0s0
    dbvol/d54 1 1 c4t10d0s0
    dbvol/d2 -m dbvol/d53 dbvol/d54 1
    ###dbvol/d51 1 1 c2t9d0s0
    dbvol/d52 1 1 c4t9d0s0
    #dbvol/d1 -m dbvol/d51 dbvol/d52 1
    dbvol/d1 -m dbvol/d52 1
    # SOFT Partitions
    dbvol/d129 -p dbvol/d5 -o 19933376 -b 526336
    dbvol/d128 -p dbvol/d5 -o 19407008 -b 526336
    dbvol/d127 -p dbvol/d5 -o 18880640 -b 526336
    dbvol/d126 -p dbvol/d5 -o 10489952 -b 8390656
    dbvol/d125 -p dbvol/d5 -o 2099264 -b 8390656
    dbvol/d123 -p dbvol/d4 -o 4724864 -b 133120
    dbvol/d122 -p dbvol/d4 -o 4460640 -b 264192
    dbvol/d121 -p dbvol/d4 -o 4196416 -b 264192
    dbvol/d120 -p dbvol/d4 -o 32 -b 4196352
    dbvol/d119 -p dbvol/d3 -o 30972032 -b 526336
    dbvol/d118 -p dbvol/d3 -o 10489952 -b 20482048
    dbvol/d117 -p dbvol/d3 -o 4196416 -b 6293504
    dbvol/d116 -p dbvol/d3 -o 32 -b 4196352
    dbvol/d115 -p dbvol/d2 -o 8925408 -b 526336
    dbvol/d114 -p dbvol/d2 -o 8399040 -b 526336
    dbvol/d113 -p dbvol/d2 -o 7872672 -b 526336
    dbvol/d112 -p dbvol/d2 -o 7346304 -b 526336
    dbvol/d111 -p dbvol/d2 -o 5247072 -b 2099200
    dbvol/d110 -p dbvol/d2 -o 1050688 -b 4196352
    dbvol/d109 -p dbvol/d2 -o 32 -b 1050624
    dbvol/d108 -p dbvol/d1 -o 33554496 -b 1572864
    dbvol/d107 -p dbvol/d1 -o 32 -b 33554432
    dbvol/d124 -p dbvol/d5 -o 32 -b 2099200
    dbvol/d138 -p dbvol/d4 -o 38416608 -b 133120
    dbvol/d137 -p dbvol/d3 -o 31498400 -b 264192
    dbvol/d136 -p dbvol/d4 -o 21637312 -b 16779264
    dbvol/d135 -p dbvol/d4 -o 4858016 -b 16779264
    dbvol/d134 -p dbvol/d6 -o 69212288 -b 23070720
    dbvol/d133 -p dbvol/d6 -o 46141536 -b 23070720
    dbvol/d132 -p dbvol/d6 -o 23070784 -b 23070720
    dbvol/d131 -p dbvol/d6 -o 32 -b 23070720
    dbvol/d130 -p dbvol/d5 -o 20459744 -b 526336
    root@log01 >metadb -s dbvol -i
    metadb: log01: setname "dbvol": no such set
    root@log01 >\

  • Diskless client boot on a blade farm

    We have a possible blade-centric architecture we are looking at whereby the chassis provides for F/C connection to a SAN and standard Ethernet (x 2) for network.
    As we are looking to use RHEL as the OS I'd be interested to know whether people think that the blades can be booted as a diskless client (is this supported by Oracle?) from a single boot image on the SAN or the network. All Oracle datafiles would be maintained on the SAN. Has anyone experience or comments on this kind of setup?
    The possible advantages of this would be the reduced admin for RHEL: When patches are applied one blade can be taken out of the cluster and booted from a secondary image against which the patches are applied. When completed, the remaining blades can be rebooted one at a time to pick up the revised image. The first boot image can be left hanging about as a fall back option before the next round of upgrades. Also, expanding the number of blades can be done (near as damn it) with zero configuration and there is little chance of version mismatches in the OS.
    I am concerned about database upgrades, the Oracle home in a shared everything environment, impact on Grid Control, so I welcome any comments/criticism/abuse.
    Best regards to all,
    Jon Mercer

    I haven't tried RAC on diskless boots, but I have used diskless boots with RHAS3. Once the system is running, you can't really tell except that all mount points are NFS based.
    But in regards to having the oracle homes shared, I would recommend against it. If you follow the normal guidelines for the diskless boots, you'll find that each node already have it's own "home" on the array; in particular paritions like /var and /tmp cannot be shared between hosts. The same goes for Oracle, as (unforunately) it puts most of it's log files in the oracle home. These would have to be different.
    I would look at OCFS2 - it has support for shared Oracle Homes - in which it can be TOLD to keep seperate copies of "common" log files - meaning seperate files for each host. This way, executables that are the same, stays as one copy but host specific data are separated out. I would be very careful before going that route and do a lot of testing; but that seems to be what the good linux guys thought of when they did the OCFS2.

  • [SOLVED]C compiler cannot create executables DUE TO MISSING DEV. PACKS

    Hi there, I was trying to build "lib32-libpcap" from AUR using yaourt when the gcc(?) reported an error as following:
    ==> Starting build()...
    checking build system type... x86_64-unknown-linux-gnu
    checking host system type... x86_64-unknown-linux-gnu
    checking target system type... x86_64-unknown-linux-gnu
    checking for gcc... gcc -m32
    checking for C compiler default output file name...
    configure: error: C compiler cannot create executables
    See `config.log' for more details.
    ==> ERROR: A failure occurred in build().
    Aborting...
    The content of the "config.log" file:
    This file contains any messages produced by compilers while
    running configure, to aid debugging if configure makes a mistake.
    It was created by configure, which was
    generated by GNU Autoconf 2.61. Invocation command line was
    $ ./configure --prefix=/usr --libdir=/usr/lib32 --enable-ipv6
    ## Platform. ##
    hostname = mzws
    uname -m = x86_64
    uname -r = 3.2.8-1-ARCH
    uname -s = Linux
    uname -v = #1 SMP PREEMPT Mon Feb 27 21:51:46 CET 2012
    /usr/bin/uname -p = unknown
    /bin/uname -X = unknown
    /bin/arch = x86_64
    /usr/bin/arch -k = unknown
    /usr/convex/getsysinfo = unknown
    /usr/bin/hostinfo = unknown
    /bin/machine = unknown
    /usr/bin/oslevel = unknown
    /bin/universe = unknown
    PATH: /usr/local/bin
    PATH: /usr/bin
    PATH: /bin
    PATH: /usr/local/sbin
    PATH: /usr/sbin
    PATH: /sbin
    PATH: /usr/bin/core_perl
    ## Core tests. ##
    configure:1794: checking build system type
    configure:1812: result: x86_64-unknown-linux-gnu
    configure:1834: checking host system type
    configure:1849: result: x86_64-unknown-linux-gnu
    configure:1871: checking target system type
    configure:1886: result: x86_64-unknown-linux-gnu
    configure:2036: checking for gcc
    configure:2063: result: gcc -m32
    configure:2301: checking for C compiler version
    configure:2308: gcc -m32 --version >&5
    gcc (GCC) 4.6.2 20120120 (prerelease)
    Copyright (C) 2011 Free Software Foundation, Inc.
    This is free software; see the source for copying conditions. There is NO
    warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
    configure:2311: $? = 0
    configure:2318: gcc -m32 -v >&5
    Using built-in specs.
    COLLECT_GCC=gcc
    COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.2/lto-wrapper
    Target: x86_64-unknown-linux-gnu
    Configured with: /build/src/gcc-4.6-20120120/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch --enable-libstdcxx-time --enable-gnu-unique-object --enable-linker-build-id --with-ppl --enable-cloog-backend=isl --enable-lto --enable-gold --enable-ld=default --enable-plugin --with-plugin-ld=ld.gold --disable-multilib --disable-libssp --enable-checking=release
    Thread model: posix
    gcc version 4.6.2 20120120 (prerelease) (GCC)
    configure:2321: $? = 0
    configure:2328: gcc -m32 -V >&5
    gcc: error: unrecognized option '-V'
    gcc: fatal error: no input files
    compilation terminated.
    configure:2331: $? = 1
    configure:2354: checking for C compiler default output file name
    configure:2381: gcc -m32 -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu conftest.c >&5
    /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.2/libgcc.a when searching for -lgcc
    /usr/bin/ld: cannot find -lgcc
    /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.2/../../../libgcc_s.so when searching for -lgcc_s
    /usr/bin/ld: skipping incompatible /usr/lib/libgcc_s.so when searching for -lgcc_s
    /usr/bin/ld: cannot find -lgcc_s
    collect2: ld returned 1 exit status
    configure:2384: $? = 1
    configure:2422: result:
    configure: failed program was:
    | /* confdefs.h. */
    | #define PACKAGE_NAME ""
    | #define PACKAGE_TARNAME ""
    | #define PACKAGE_VERSION ""
    | #define PACKAGE_STRING ""
    | #define PACKAGE_BUGREPORT ""
    | /* end confdefs.h. */
    |
    | int
    | main ()
    | {
    |
    | ;
    | return 0;
    | }
    configure:2429: error: C compiler cannot create executables
    See `config.log' for more details.
    ## Cache variables. ##
    ac_cv_build=x86_64-unknown-linux-gnu
    ac_cv_env_CC_set=set
    ac_cv_env_CC_value='gcc -m32'
    ac_cv_env_CFLAGS_set=set
    ac_cv_env_CFLAGS_value='-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2'
    ac_cv_env_CPPFLAGS_set=
    ac_cv_env_CPPFLAGS_value=
    ac_cv_env_CPP_set=
    ac_cv_env_CPP_value=
    ac_cv_env_LDFLAGS_set=set
    ac_cv_env_LDFLAGS_value=-Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu
    ac_cv_env_LIBS_set=
    ac_cv_env_LIBS_value=
    ac_cv_env_build_alias_set=
    ac_cv_env_build_alias_value=
    ac_cv_env_host_alias_set=
    ac_cv_env_host_alias_value=
    ac_cv_env_target_alias_set=
    ac_cv_env_target_alias_value=
    ac_cv_host=x86_64-unknown-linux-gnu
    ac_cv_prog_ac_ct_CC='gcc -m32'
    ac_cv_target=x86_64-unknown-linux-gnu
    ## Output variables. ##
    ADDLARCHIVEOBJS=''
    ADDLOBJS=''
    BT_SRC=''
    CAN_SRC=''
    CC='gcc -m32'
    CFLAGS='-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2'
    CPP=''
    CPPFLAGS=''
    DEFS=''
    DYEXT=''
    ECHO_C=''
    ECHO_N='-n'
    ECHO_T=''
    EGREP=''
    EXEEXT=''
    GREP=''
    HAVE_LINUX_TPACKET_AUXDATA=''
    INSTALL_DATA=''
    INSTALL_PROGRAM=''
    INSTALL_SCRIPT=''
    LDFLAGS='-Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu'
    LIBOBJS=''
    LIBS=''
    LTLIBOBJS=''
    MAN_FILE_FORMATS=''
    MAN_MISC_INFO=''
    OBJEXT=''
    PACKAGE_BUGREPORT=''
    PACKAGE_NAME=''
    PACKAGE_STRING=''
    PACKAGE_TARNAME=''
    PACKAGE_VERSION=''
    PATH_SEPARATOR=':'
    PCAP_SUPPORT_BT=''
    PCAP_SUPPORT_CAN=''
    PCAP_SUPPORT_USB=''
    RANLIB=''
    SHELL='/bin/sh'
    SHLICC2=''
    SSRC=''
    USB_SRC=''
    V_CCOPT='-O'
    V_DEFS=''
    V_FINDALLDEVS=''
    V_INCLS=''
    V_LEX=''
    V_PCAP=''
    V_RPATH_OPT=''
    V_SHLIB_CMD=''
    V_SHLIB_OPT=''
    V_SONAME_OPT=''
    V_YACC=''
    ac_ct_CC='gcc -m32'
    bindir='${exec_prefix}/bin'
    build='x86_64-unknown-linux-gnu'
    build_alias=''
    build_cpu='x86_64'
    build_os='linux-gnu'
    build_vendor='unknown'
    datadir='${datarootdir}'
    datarootdir='${prefix}/share'
    docdir='${datarootdir}/doc/${PACKAGE}'
    dvidir='${docdir}'
    exec_prefix='NONE'
    host='x86_64-unknown-linux-gnu'
    host_alias=''
    host_cpu='x86_64'
    host_os='linux-gnu'
    host_vendor='unknown'
    htmldir='${docdir}'
    includedir='${prefix}/include'
    infodir='${datarootdir}/info'
    libdir='/usr/lib32'
    libexecdir='${exec_prefix}/libexec'
    localedir='${datarootdir}/locale'
    localstatedir='${prefix}/var'
    mandir='${datarootdir}/man'
    oldincludedir='/usr/include'
    pdfdir='${docdir}'
    prefix='/usr'
    program_transform_name='s,x,x,'
    psdir='${docdir}'
    sbindir='${exec_prefix}/sbin'
    sharedstatedir='${prefix}/com'
    sysconfdir='${prefix}/etc'
    target='x86_64-unknown-linux-gnu'
    target_alias=''
    target_cpu='x86_64'
    target_os='linux-gnu'
    target_vendor='unknown'
    ## confdefs.h. ##
    #define PACKAGE_NAME ""
    #define PACKAGE_TARNAME ""
    #define PACKAGE_VERSION ""
    #define PACKAGE_STRING ""
    #define PACKAGE_BUGREPORT ""
    configure: exit 77
    and the makepkg.conf:
    # /etc/makepkg.conf
    # SOURCE ACQUISITION
    #-- The download utilities that makepkg should use to acquire sources
    # Format: 'protocol::agent'
    DLAGENTS=('ftp::/usr/bin/curl -fC - --ftp-pasv --retry 3 --retry-delay 3 -o %o %u'
    'http::/usr/bin/curl -fLC - --retry 3 --retry-delay 3 -o %o %u'
    'https::/usr/bin/curl -fLC - --retry 3 --retry-delay 3 -o %o %u'
    'rsync::/usr/bin/rsync -z %u %o'
    'scp::/usr/bin/scp -C %u %o')
    # Other common tools:
    # /usr/bin/snarf
    # /usr/bin/lftpget -c
    # /usr/bin/wget
    # ARCHITECTURE, COMPILE FLAGS
    CARCH="x86_64"
    CHOST="x86_64-unknown-linux-gnu"
    #-- Compiler and Linker Flags
    # -march (or -mcpu) builds exclusively for an architecture
    # -mtune optimizes for an architecture, but builds for whole processor family
    CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2"
    CXXFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2"
    LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu"
    #-- Make Flags: change this for DistCC/SMP systems
    #MAKEFLAGS="-j2"
    # BUILD ENVIRONMENT
    # Defaults: BUILDENV=(fakeroot !distcc color !ccache check !sign)
    # A negated environment option will do the opposite of the comments below.
    #-- fakeroot: Allow building packages as a non-root user
    #-- distcc: Use the Distributed C/C++/ObjC compiler
    #-- color: Colorize output messages
    #-- ccache: Use ccache to cache compilation
    #-- check: Run the check() function if present in the PKGBUILD
    #-- sign: Generate PGP signature file
    BUILDENV=(fakeroot !distcc color !ccache check !sign)
    #-- If using DistCC, your MAKEFLAGS will also need modification. In addition,
    #-- specify a space-delimited list of hosts running in the DistCC cluster.
    #DISTCC_HOSTS=""
    #-- Specify a directory for package building.
    #BUILDDIR=/tmp/makepkg
    # GLOBAL PACKAGE OPTIONS
    # These are default values for the options=() settings
    # Default: OPTIONS=(strip docs libtool emptydirs zipman purge !upx)
    # A negated option will do the opposite of the comments below.
    #-- strip: Strip symbols from binaries/libraries
    #-- docs: Save doc directories specified by DOC_DIRS
    #-- libtool: Leave libtool (.la) files in packages
    #-- emptydirs: Leave empty directories in packages
    #-- zipman: Compress manual (man and info) pages in MAN_DIRS with gzip
    #-- purge: Remove files specified by PURGE_TARGETS
    #-- upx: Compress binary executable files using UPX
    OPTIONS=(strip docs libtool emptydirs zipman purge !upx)
    #-- File integrity checks to use. Valid: md5, sha1, sha256, sha384, sha512
    INTEGRITY_CHECK=(md5)
    #-- Options to be used when stripping binaries. See `man strip' for details.
    STRIP_BINARIES="--strip-all"
    #-- Options to be used when stripping shared libraries. See `man strip' for details.
    STRIP_SHARED="--strip-unneeded"
    #-- Options to be used when stripping static libraries. See `man strip' for details.
    STRIP_STATIC="--strip-debug"
    #-- Manual (man and info) directories to compress (if zipman is specified)
    MAN_DIRS=({usr{,/local}{,/share},opt/*}/{man,info})
    #-- Doc directories to remove (if !docs is specified)
    DOC_DIRS=(usr/{,local/}{,share/}{doc,gtk-doc} opt/*/{doc,gtk-doc})
    #-- Files to be removed from all packages (if purge is specified)
    PURGE_TARGETS=(usr/{,share}/info/dir .packlist *.pod)
    # PACKAGE OUTPUT
    # Default: put built package and cached source in build directory
    #-- Destination: specify a fixed directory where all packages will be placed
    #PKGDEST=/home/packages
    #-- Source cache: specify a fixed directory where source files will be cached
    #SRCDEST=/home/sources
    #-- Source packages: specify a fixed directory where all src packages will be placed
    #SRCPKGDEST=/home/srcpackages
    #-- Packager: name/email of the person or organization building packages
    #PACKAGER="John Doe <[email protected]>"
    #-- Specify a key to use for package signing
    #GPGKEY=""
    # EXTENSION DEFAULTS
    # WARNING: Do NOT modify these variables unless you know what you are
    # doing.
    PKGEXT='.pkg.tar.xz'
    SRCEXT='.src.tar.gz'
    # vim: set ft=sh ts=2 sw=2 et:
    Am running a up-to-date x64 Arch with [multilib] enabled; perhaps it's a silly mistake I made somewhere but I'm no dev and so cannot figure out what went wrong in the config.log....please help with your kindness and thanks in advance!
    Last edited by karbon (2012-03-10 04:28:58)

    Thanks for your replies:)
    Allan wrote:Are you really up-to-date?   gcc-4.6.3 was put in [core] four days ago but you still seem to have 4.6.2.
    Well...at least as up-to-date as on March 2nd(when I did last system-wide upgrade); trying to update system tonight to see whether this works.
    stronnag wrote:If you have multilib and testing enabled, you also need  multilib-testing, otherwise (as I know from bitter experience), you get these hard to track down errors.
    Nope I didn't enable [testing]; I've discovered some packages in [multilib], namely gcc-multilib or something similar(with the -multilib subfix) and some of these packages belong to the group "multilib-devel". Is installing these packages a must for compiling 32-bit packages?

  • Failing to create HA nfs storage on a shared 3310 HW Raid cluster 3.2

    Hi,
    I'm working on testing clustering on a couple v240s, running identitcal Sol10 10/08 and Sun Cluster 3.2. In trying things, I may have messed up the cluster. I may want to backout the cluster and start over. Is that possible, or do I need to install Solaris fresh.
    But first, the problem. I have the array connect to both machines and working. I mount 1 LUN on /global/nfs using the device /dev/did/dsk/d4s0. Then I ran the commands:
    # clrt register SUNW.nfs
    # clrt register SUNW.HAStoragePlus
    # clrt list -v
    Resource Type Node List
    SUNW.LogicalHostname:2 <All>
    SUNW.SharedAddress:2 <All>
    SUNW.nfs:3.2 <All>
    SUNW.HAStoragePlus:6 <All>
    # clrg create -n stnv240a,stnv240b -p PathPrefix=/global/nfs/admin nfs-rg
    I enabled them just now so:
    # clrg status
    Cluster Resource Groups ===
    Group Name Node Name Suspended Status
    nfs-rg stnv240a No Online
    stnv240b No Offline
    Then:
    # clrslh create -g nfs-rg cluster
    # clrslh status
    Cluster Resources ===
    Resource Name Node Name State Status Message
    cluster stnv240a Online Online - LogicalHostname online.
    stnv240b Offline Offline
    I'm guessing that 'b' is offline because it's the backup.
    Finally, I get:
    # clrs create -t HAStoragePlus -g nfs-rg -p AffinityOn=true -p FilesystemMountPoints=/global/nfs nfs-stor
    clrs: stnv240b - Invalid global device path /dev/did/dsk/d4s0 detected.
    clrs: (C189917) VALIDATE on resource nfs-stor, resource group nfs-rg, exited with non-zero exit status.
    clrs: (C720144) Validation of resource nfs-stor in resource group nfs-rg on node stnv240b failed.
    clrs: (C891200) Failed to create resource "nfs-stor".
    On stnv240a:
    # df -h /global/nfs
    Filesystem size used avail capacity Mounted on
    /dev/did/dsk/d4s0 49G 20G 29G 41% /global/nfs
    and on stnv240b:
    # df -h /global/nfs
    Filesystem size used avail capacity Mounted on
    /dev/did/dsk/d4s0 49G 20G 29G 41% /global/nfs
    Any help? Like I said, this is a test setup. I've started over once. So I can start over if I did something irreversible.

    I still have the issue. I reinstalled from scratch and installed the cluster. Then I did the following:
    $ vi /etc/default/nfs
    GRACE_PERIOD=10
    $ ls /global//nfs
    $ mount /global/nfs
    $ df -h
    Filesystem size used avail capacity Mounted on
    /dev/global/dsk/d4s0 49G 20G 29G 41% /global/nfs
    $ clrt register SUNW.nfs
    $ clrt register SUNW.HAStoragePlus
    $ clrt list -v
    Resource Type Node List
    SUNW.LogicalHostname:2 <All>
    SUNW.SharedAddress:2 <All>
    SUNW.nfs:3.2 <All>
    SUNW.HAStoragePlus:6 <All>
    $ clrg create -n stnv240a,stnv240b -p PathPrefix=/global/nfs/admin nfs-rg
    $ clrslh create -g nfs-rg patience
    clrslh: IP Address 204.155.141.146 is already plumbed at host: stnv240b
    $ grep cluster /etc/hosts
    204.155.141.140 stnv240a stnv240a.mns.qintra.com # global - cluster
    204.155.141.141 cluster cluster.mns.qintra.com # cluster virtual address
    204.155.141.146 stnv240b stnv240b.mns.qintra.com patience patience.mns.qintra.com # global v240 - cluster test
    $ clrslh create -g nfs-rg cluster
    $ clrs create -t HAStoragePlus -g nfs-rg -p AffinityOn=true -p FilesystemMountPoints=/global/nfs nfs-stor
    clrs: stnv240b - Failed to analyze the device special file associated with file system mount point /global/nfs: No such file or directory.
    clrs: (C189917) VALIDATE on resource nfs-stor, resource group nfs-rg, exited with non-zero exit status.
    clrs: (C720144) Validation of resource nfs-stor in resource group nfs-rg on node stnv240b failed.
    clrs: (C891200) Failed to create resource "nfs-stor".
    Now, on the second machine (stnv240b), /dev/global does not exist, but the file system mounts anyway. I guess that's cluster magic?
    $ cat /etc/vfstab
    /dev/global/dsk/d4s0 /dev/global/dsk/d4s0 /global/nfs ufs 1 yes global
    $ df -h /global/nfs
    Filesystem size used avail capacity Mounted on
    /dev/global/dsk/d4s0 49G 20G 29G 41% /global/nfs
    $ ls -l /dev/global
    /dev/global: No such file or directory
    I followed the other thread. devfsadm and scgdevs
    One other thing I notice. Both nodes mount my global on node@1
    /dev/md/dsk/d6 723M 3.5M 662M 1% /global/.devices/node@1
    /dev/md/dsk/d6 723M 3.5M 662M 1% /global/.devices/node@1

  • JCo client connection Failed to create new JCO client connection

    hi All
    I am trying to create a new JCO destination ion CE7.1 webdynpro content Admin. but I am getting following error.
    Exception while creating JCo client connection Failed to create new JCO client connection weter: com.sap.lcr.api.cimclient.LcrException: CIM_ERR_ACCESS_DENIED: User is not in role LcrInstanceWriterLD at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.raiseExceptionOnError(SimpleResponseAnalyser.java:120) at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.getIResult(SimpleResponseAnalyser.java:53) at com.sap.lcr.api.cimclient.CIMOMClient.sendImpl(CIMOMClient.java:220) at com.sap.lcr.api.cimclient.CIMOMClient.send(CIMOMClient.java:148) at com.sap.lcr.api.cimclient.CIMOMClient.createInstanceImpl(CIMOMClient.java:669) at ......
    SLD is Up and running
    CIM data is imported
    Solution tried :
    1) As no role wtih name LcrInstanceWriterLD was existing in the server ,hence created a new role with same name and assigned the LCR related action . Assigned the role to the user through which we are creating JCOs.
    But we still getting the same error.
    regards
    Poonam

    Hi Poonam!
    Got to dig in the past a bit, I remember Users being able to create SLD object have to have certain permissions set in the J2EE UME. Simple Admin rights do not suffer, if I recall right.
    Unfortunately I cannot go further in detail because this issue has been solved by a long gone collegue of mine.
    Good luck anyway!
    Jürgen

Maybe you are looking for