Succeeded for root on /dev/???

Hi - I'm running a Solaris 10 T4-1 server with non-global zones and just noticed the following in the logs:
Mar 11 21:12:29 zonewww su: [ID 366847 auth.info] 'su nagios' succeeded for root on /dev/???
Mar 11 21:12:33 zonewww su: [ID 366847 auth.info] 'su was' succeeded for root on /dev/???
Mar 11 21:18:00 zonewww su: [ID 366847 auth.info] 'su was' succeeded for root on /dev/???
Mar 14 05:00:34 zonewww su: [ID 366847 auth.notice] 'su root' succeeded for root on /dev/???
Mar 14 05:08:08 zonewww su: [ID 366847 auth.notice] 'su root' succeeded for root on /dev/???
Mar 14 10:22:40 zonewww su: [ID 366847 auth.info] 'su was' succeeded for root on /dev/???
Mar 20 10:57:17 zonewww su: [ID 366847 auth.info] 'su was' succeeded for root on /dev/???
I can see it's been going on for months, can be really random. I've seen a few threads about could be cron jobs running - but checked and it isn't or not that I can see. And also the times / dates are completely random. It's also for other users on this particular server. Has anyone seen this before and know what is causing it?
Thanks - J.

Ah right I've found part of the answer out - some of these entries tie in exactly with when the non-global zone was rebooted, eg.
grep "succeeded for root on /dev/???" /var/adm/authlog |grep "Mar 11"
Mar 11 20:03:28 zonewww su: [ID 366847 auth.info] 'su jhc' succeeded for root on /dev/???
Mar 11 20:03:30 zonewww su: [ID 366847 auth.info] 'su jhc2' succeeded for root on /dev/???
Mar 11 20:03:32 zonewww su: [ID 366847 auth.info] 'su jhcixx' succeeded for root on /dev/???
Mar 11 20:03:35 zonewww su: [ID 366847 auth.info] 'su was' succeeded for root on /dev/???
Mar 11 20:07:05 zonewww su: [ID 366847 auth.info] 'su was' succeeded for root on /dev/??? **** here ****
Mar 11 21:12:28 zonewww su: [ID 366847 auth.info] 'su jhc' succeeded for root on /dev/??? **** here ****
Mar 11 21:12:28 zonewww su: [ID 366847 auth.info] 'su jhc2' succeeded for root on /dev/??? **** here ****
Mar 11 21:12:29 zonewww su: [ID 366847 auth.info] 'su jhcixx' succeeded for root on /dev/??? **** here ****
Mar 11 21:12:29 zonewww su: [ID 366847 auth.info] 'su nagios' succeeded for root on /dev/??? **** here ****
Mar 11 21:12:33 zonewww su: [ID 366847 auth.info] 'su was' succeeded for root on /dev/??? **** here ****
Mar 11 21:18:00 zonewww su: [ID 366847 auth.info] 'su was' succeeded for root on /dev/???
last reboot |grep "Mar 11"
reboot system boot Mon Mar 11 21:12
reboot system down Mon Mar 11 20:07
There are still some other entries that I can't explain though.
Julian.

Similar Messages

[SOLVED] ERROR: Unable to find root device '/dev/sda3'

Earlier I updated the kernel to my arch system and found this error while trying to boot. I hate to post this because there are so many topics like it, but I've been looking for hours for a solution to this problem and can't find one.
Here is the output:
Booting 'Arch Linux'
root (hd0,1)
Filesystem type is ext2fs, partition type 0x83
kernet /vmlinuz-linux root=/dev/sda3 ro
[Linux-bzImage, setup=0x4200, size=0x2ff2d0]
initrd /initrd @ 0xfd17000, 0x2c878c bytes]
Probing EDD (edd=off to disable)... ok
Decompressing Linux... Parsing ELF... done.
Booting the kernel.
:: Starting udevd...
done.
Waiting 10 seconds for device /dev/sda3 ...
ERROR: device '/dev/sda3' not found. skipping fsck.
ERROR: Unable to find root device '/dev/sda3'.
You are being dropped to a recovery shell
type 'exit' to try and continue booting
sh: can't access tty; job control turned off
My partition layout is like this:
swap: /dev/sda1
boot: /dev/sda2
root: /dev/sda3
extended: /dev/sda4
home: /dev/sda5
I have two hard drives, but i'm sure /dev/sda is the one with my OS.
Here are some things I've tried:
This was at the very bottom of the pacman wiki
# mkdir /mnt/arch
# mount /dev/sdaX /mnt/arch (your root partition)
# cd /mnt/arch
# mount -t proc proc proc/
# mount -t sysfs sys sys/
# mount -o bind /dev dev/
# mount /dev/sdaX boot/ (your /boot partition) #This step is not needed if you do not have a separate boot partition
# chroot .
# pacman -Syu udev mkinitcpio
# mkinitcpio -p linux
I've also tried performing the above, downgrading the kernel, updating my mirrorlist, reinstalling the kernel, and rebooting as mentioned here.
I've alsa tried a few other things that I've read, but can no longer remember.
Any help would be greatly appreciated! Thanks.
Last edited by colton7909 (2012-05-25 02:09:36)

Thank colton
Same problem here, but on a mac book (not mine eyh )
So, for those how have the problem (or need a live usb for mac or uefi systems),
1) with a 32bits system
- download gparted live cd
- use it for the step 3
2) with a 64bits system:
- you need the gparted live cd too: mount it and copy the EFI directory somewhere; then umount it;
- download a 64bits system (system rescue cd, as colton said is enough, follow the instructions for installation on their website first);
- mount you live usb, install the 64bits system;
- copy EFI system on the key
- edit the grub.cfg in EFI/boot/ , add the following before the other entries:
menuentry "System Rescue" {
set gfxpayload=keep
linux /syslinux/altker64 nomodeset efi
initrd /syslinux/initram.igz
3) repairing...
- boot the broken computer with the live usb
- mount the partition on which your system is (e.g. /dev/sda1 on /mnt)
- chroot it, init the system as needed (mount /dev, /proc, etc. the easier way is using init scripts)
% chroot /mnt /bin/bash
% /etc/rc.sysinit
% mkinitcpio -p linux

Forbidden Screen - Error: "Still waiting for root device"

Greetings to all! I come to you with my boot troubles as a supplicant, in the hope that someone can help.
I have a PowerBook G4 15-inch, pre-Intel from late 2005. Until today it always worked and rarely hanged. All I've ever needed to do when in trouble was reboot. I've updated the Apple OSX software regularly and have never touched the hardware, except once 18 months ago to add memory. All I do with this machine is use it. It's been weeks since I installed any new software.
There were no warning signs before the problem started today.
FIRST SIGN OF TROUBLE: The machine was unusually slow, showing beach balls on every minor move. I powered down conventionally and later turned it on again. After a minute I got the "Forbidden Sign" grey screen, which I had never seen before. So I rebooted, and got that again.
+I turned to the only other available machine (very old PC, unfortunately) to browse for solutions, and have so far tried the following:+
1) BOOT FROM INSTALLATION DISK: Forbidden Screen. After a couple of attempts I removed the disk (by clicking trackpad on power up). At some point, in desperation, I even tried Disc 2.
2) RESET PRAM (Command-Option-P-R on power up) : I got three chimes, then the grey screen. It stayed on the apple and gear for many minutes. At least it never went to the Forbidden Screen.
3) FILE SYSTEM CHECK (Option-S on power up) : After a few steps it shows error messages (see below) and starts repeating, "Still waiting for root device," over and over.
4) RESET NVRAM (Command-Option-O-F on power up) : I got a blue screen with text and was able to input "reset-nvram" (response: OK) and then "boot." Result: Forbidden Screen.
5) SAFE START (Option on power up) : Forget it. Forbidden Screen. Same when I try it with "C" as some sites recommend. Same with or without the Install Disk in the DVD driver.
6) POWER MANAGEMENT UNIT RESET (Shift-Control-Option-Power): Subsequent boot still produces Forbidden Screen.
*THE ERROR MESSAGES*
Here are some of the messages when I start up with Option-S:
CSRHIDTransitionDriver::probe booting in single user .. do not match
Extension "com.apple.driver.AppleUSBTCKeyboard" has no kernel dependency.
Extension "com.apple.driver.AppleUSBTCKeyEventDriver" has no kernel dependency.
Apple PMU::CLOCK RESET! PMU WAS PROBABLY RESET SOMEHOW!! +(Yes, I did that, but it wasn't showing this before I did, and it WAS showing all of the following.)+
Security auditing service present
BSM auditing present
disabled
rooting via boot-uuid from /chosen: +(I think the long code that follows is the serial number?)+
Waiting on <dict ID="o"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
PMUMS::start ERROR: failed to find IOATABlockStorageDriver
Still waiting for root device
Still waiting for root device
Still waiting for root device
+(etc. ad infinitum)+
*So now I'm begging anyone for answers to these questions:*
Am I doomed?
Does anyone know what the problem is?
This seems to be happening prior to disk access, as it happens with or without the Install Disk. So do I still have the hard drive working? Is my data on it?!
Was resetting the Power Management Unit a bad idea?
What can I do next?
THANK YOU THANK YOU THANK YOU!
Nicholas from NYC

Thanks for your reply, Louie!
In the meantime I have succeeded in booting via the Install Disc using Option on power up. The Hardware test shows nada wrong. Disk Util repair goes up to "Rebuilding Category B-Tree" and then fails. Frustratingly, the HD is somehow visible, because the diagnostics correctly identify it and give correct values for empty space. Right now I'm running the Erase Free Space option and it's working - how is that possible? I've gotten into Single User mode and tried various FSCK commands. Sometimes it comes back with the superblock error and "Bad Magic Number" which I believe indicates a corrupted block within the boot sector. I can't figure out how to reassign without reformatting and losing the data. This will cost me a few weeks of data, but really not that much work - still set me back by days.
Next step will be to start taking it apart, as you suggest, starting with the easy matter of trying with just one DIMM or switching the DIMMs.
Thanks again, and if anyone knows how to help - how does one reassign a superblock from the Single User mode?

[SOLVED] ERROR: Can't find root device /dev/disk/by-uuid/...

Yesterday I upgraded my Lenovo X100e
# pacman -Syu
and rebooted. Upon reboot, I received the error
ERROR: Cannot find root device '/dev/disk/by-uuid/[...]'
just after kernel decompression. I got dropped into the recovery shell
and could not boot.
The problem persisted despite using different root device names (e.g. /dev/sda3, the actual root device). After reading the instructions at https://wiki.archlinux.org/index.php/Chroot I used a core installation image (on a usb stick) to boot the machine, then chrooted into my installation. I ran mkinitcpio and found that the udev hook was missing, i.e. not in /lib/initcpio/hooks. Nor was there a file called 'udev' in /lib/initcpio/install.
I copied these files from a friend's installation and then re-ran mkinitcpio:
# mkinitcpio -p linux
I was able to reboot successfully after that.
The weird thing: I don't know how the udev hook script was deleted from /lib/initcpio/hooks.
If someone else runs into this problem: try to run mkinitcpio (e.g. by using the chroot), and check for this problem. I think the problem was that the root device could not be found because the udev hook had not run, and therefore /dev was unpopulated.

Betwen udev-181-2 and udev-181-5, the hooks have moved from /lib/initcpio to /usr/lib/initcpio. But mkinitcpio -L should still list them.
I have a similar problem since the last update. The kernel doesn't seem to load my raid driver anymore. Upon boot it throws some cryptic udev messages at me and then crashes. Haven't found out what that is about yet.

"Unable to find root device /dev/sda2"

Hi!
After an update - seemingly unsuccessfull - I get dropped into a recovery shell. The messages are:
/usr/lib/suspend/resume: /usr/lib/libpng14: version `PNG14_0`not found (required by /usr/lib/libsplshrender.so.1)
ERROR: unable to find root device '/dev/sda2'
I read that now I'm supposed to run a LiveCD and chroot something... can someone please be a little more specific here? I don't want to lose that system and I have no idea why it doesn't find my disk anymore. I just performed a pacman4 uprade, but it seems pacman4 is rather immature, leaving a system unuseable like that.
There is no sdaX in /dev any more. And I have very little experience with recovering Arch Linux. Until now
Best,
wishi

I have some wild problems here
1.) I used an Arch Live CD, did the chroot trick from the wiki (https://wiki.archlinux.org/index.php/Ch … nging_Root) and rebuild my initcpio (https://wiki.archlinux.org/index.php/Mkinitcpio). That ends successfull, and says it adds hooks for sata etc.
-> But I had to remove the udev hook: http://bbs.archbang.org/viewtopic.php?pid=11304 - I guess that's the reason why it still doesn't find my /dev/sda2 - I'm not sure this is related though.
2.) I ran pacman -Qk to ensure everything is sane. No errors. I reinstalled linux and udev two minutes ago. No change.
But I don't see how I can fix this. What's that voodoo with some udev hooks wandering around? The new kernel is 3.2.5-1 ARCH.

Single User Mode: Still waiting for root device

iMac G4.
I reset the NVRAM, PRAM. It won't attempt to boot from anything but a OS 10.4 cd; booting from OS 9 cd just leaves me at the flashing question mark icon.
If I try to boot from OS X cd, it comes back with the prohibitory sign.
If I try to boot into single user mode, it gives me a bunch of "...."has no kernal dependency lines, then a 'still waiting for root device' line, and repeats that.
Something to the effect before the 'still waiting for root device' is "Waiting on <dict ID="0"><key>IOProvider-Class</key><string ID="1">IOResouces</string><key>IOResouceMatch></key><string ID="2">boot-uuid-media</string></dict>"
Any help please?

Nevermind...I found out that the hard drive was bad...still puzzles me why it wouldn't boot from CD though, as I thought they all should even if no drive is present.

Single User Mode: Searching for root...

My 2 year old unplugged my PowerMac iMac G5 (single) and now it won't start up.
I was finally able to boot up off of Disk Warrior and replace the directory, but it won't start up past the gray Apple screen. The fan comes on after about 45 seconds and blows hard. Then, I get the circle with a line through it, in gray. I've never seen that on a mac.. the international "no" sign.
When trying to start up in Single User Mode, I get a long list of stuff either disabled, not found, missing etc and then it starts writing to the screen every 30 seconds a line like:
Still searching for root.
I've tried pulling the back off, resetting the SMU, starting up in Safe Mode, etc.
This has happened with storms before and I can usually get it back.
I don't have original install discs.

When you say you have "OSX" but not the "original install disks" do you mean the mac originally came with an earlier version and you don't have those disks, but you have a retail copy of Tiger?
The circle with the slash means that Open Firmware cannot find BootX. Basically, I think this means that Open Firmware recognises the startup volume as such but cannot hand control to the operating system at all. BootX is what it uses to get the operating system going. Without this, as you've seen, you cannot make even single-user mode.
What is SMU?
*Is your data backed up? If not, prioritise that unless you can afford to loose it.*
Does DiskWarrior repair permissions? If not and you have the Tiger retail version, try running Disk Utility to do that. I don't think this will help, but it won't hurt.
Do you have another Mac? If so and you have the retail Tiger, you might be able to use Pacifist to replace BootX (in /System/Library/CoreServices). Alternatively, if the other Mac is running the same version of the OS and is also a PPC Mac, you could try copying the file from that machine.
Before you do any of this (with the exception of the permissions repair), try to backup any data you need if that's at all possible.
- cfr

10.6.8 Netboot - "Still waiting for root device"

Hi all,
I am having trouble with one particular 10.6.8 Netboot image that is hosted on a Mac Pro running 10.5.8 Server. (The main 10.5.8 Server is currently hosting about 15 other Netboot and Netrestore images that work with no problem.) I built the image on a 10.6.8 Server using System Image Utility from a fully updated 10.6.8 restore image on an external hard drive. The external drive was started up on MacBook, MacBook Pro, and iMac systems ranging from Late '06 to Early '11 revisions. Software update was run on every startup, but came back fully up-to-date every time and never encountered problems starting up each from the external drive.
I then ran Disk Utility permissions repair on the external drive from the 10.6.8 Server Mac Pro and built the Netboot image in System Image Utility. Although I am fairly new to this process, I have already successfully built several 10.6.8, 10.7.5, 10.8.5, and 10.9 Netrestore images as well as one 10.9 diagnostic Netboot that all work perfectly. I followed the same process when creating the 10.6.8 Netboot image.
The image I created, called 10.6.8 Diags 3.0, shows up in the Netboot list, but when I attempt to boot it shows the Apple logo for a bit before showing the "circle slash" symbol. Verbose mode shows that it hangs when starting and repeats "Still waiting for root device" over and over again and never does anything.
I have rebuilt the 10.6.8 Diags 3.0 Netboot image several times to rule out the possibility of corruption durring image creation. I have also tried to create the image from a Firewire attached external drive as well as building the data on the external drive into a .dmg on the 10.6.8 Server and then creating the image from that. All methods of creating the image yeild the same "Still waiting for root device" error when attempting to start up on any system supporting the 10.6.8 kernel.
Netboot settings in Server Admin are the same as other Netboot images that are functioning: enabled, diskless, Intel (grayed out), and NFS. I have verified that all enabled image index numbers are unique and even tried several different index numbers on the problem Neboot image.
Again, all other Netrestore images I created on the same 10.6.8 Server work just fine when added to the Netboot directory on the 10.5.8 Main Server, but the Netboot image of 10.6.8 Diags 3.0 does not. I'm not sure what else to try at this point, any ideas?

Ooooh. I've been reading similar pages on cidori.org and just assumed it was one of those. Remarkable how my google searches didn't find that one. Thanks for the pointer, and I'll go try it.
Thanks again, Dan.

Window Server communications from outside of session allowed for root

Hi ,
When I am running the following program, i got the exception as
49:wasp.corp.apple.com_kevinli:/ngs/app/giat/src/java/chart> java MyFrame
kCGErrorRangeCheck : Window Server communications from outside of session allowed for root and console user only
Exception in thread "main" java.lang.InternalError: Can't connect to window server - not enough permissions.
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1586)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1503)
at java.lang.Runtime.loadLibrary0(Runtime.java:788)
at java.lang.System.loadLibrary(System.java:834)
at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:50)
at java.security.AccessController.doPrivileged(Native Method)
at sun.awt.NativeLibLoader.loadLibraries(NativeLibLoader.java:38)
at sun.awt.DebugHelper.<clinit>(DebugHelper.java:29)
at java.awt.Component.<clinit>(Component.java:506)
at MyFrame.<clinit>(MyFrame.java:6)
import java.awt.*;
import javax.swing.*;
public class MyFrame
public static JFrame f = new JFrame();
public static void main(String[] args)
JFrame.setDefaultLookAndFeelDecorated(true);
f.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
//Add the ubiquitous "Hello World" label.
JLabel label = new JLabel("Hello World");
f.getContentPane().add(label);
//Display the window.
f.pack();
f.setVisible(true);
Please send a reply on this.
with regards,
Mohan

Seth,
you may also install the latest update (10.4.6) using the combo file from apple.com.
Mihalis.
Dual G5 @ 2GHz Mac OS X (10.4.6)

"Always Open In..." View Options for Root Level of a Disk Image File

I ran into a problem/bug tonight that I can't find listed anywhere and was wondering if anyone else has encountered it. I am using Snow Leopard (now 10.6.1), upgraded from the last revision of Leopard.
I create DVD-R sized disk images with Disk Utility (using "Mac OS Extended" only w/o Journaling) for saving downloaded files. Because of the number of files on this disk, I create single-letter folders (for alphabetical filing) and set up these disk images to "Always Open In List View". For the individual folders, I can set these to "Always Open In List View" without a problem. However, for the "root level" of these disk images, I can only access "Always Open In Icon View" no matter which view option is selected.
For previously created disk images that were already set to "Always Open In List View", these show the previously set "List View" at the disk image "root level" as expected. But if I uncheck the box, it immediately goes to "Always Open In Icon View". And like before, no matter which view option is selected, I can never get back to "Always Open In List View". Note also that I can set this option as expected for "root levels" of real disks - this only seems to be a problem with the disk image files.
I had no problems at all with this under Tiger or Leopard. I've only run into this now under Snow Leopard. The upgrade tonight to 10.6.1 hasn't seem to affect this problem.
So should I be doing something differently now to get this option to reappear, a possible conflict with something on my computer or is this a bug with Snow Leopard? Can anyone else duplicate this issue?

Additional info, in case anyone is running into this issue...
If I do the following with the "root level" of the disk image, I can set the "Always Open in List View" option.
1. Open the "root level" view of the disk image - for me, it always opens in icon view. Then, select "Show View Options" from the View menu.
2. Check the "Always Open in Icon View" box. While leaving this dialog open, select "as List" from the View menu.
3. Uncheck the "Always Open in Icon View" box. It will instantly turn into "Always Open In List View". Recheck this box immediately, then close dialog. This will make the setting stick.
I've been able to repeat this situation several times. I might be wrong, but it sure acts like a small bug to me. Hope this helps anyone else who might have encountered this issue.

RAID-1 for root/swap on Solaris 10 x86

OK, now that I have solved my problem with the update manager I am in the process of trying to create RAID-1 volumes for root and swap. I am working my way through the process by following the procedure in Solaris Volume Manager Administration Guide. I have run into a few errors in the doc, e.g. referent to using installboot as opposed to installgrub.
Now I am trying to create my new volume using the Enhanced Storage tool within the Solaris Management Console. I get as far as trying to create the new volume (RAID-0) with the root slice in it but it fails with metainit telling me that the slice is already mounted on /. (No kidding -- that is the whole idea.)
Does anyone have a working procedure to create RAID-1 for root and swap?
(BTW, I am trying to do this from the doc and admin guides without stealing time from folks on the list here but I just keep running into walls.)
(Once I get that done I hope to use zfs for the rest of the storage.)
Brian
Message was edited by: brian -- initial post was truncated.
brian.lloyd

I am attempting to set up RAID-1 (mirroring) for root and swap. I am attempting to work from "Solaris Volume Manager Administration Guide," Part No: 816�4520�12. (Same place you pointed me except I downloaded the pdf so I could page through it faster.) On page 105 you will find an entry for "Create a mirror from the root (/) filesystem," which directs you to page 122, "�x86: How to Create a RAID-1 Volume From the root (/) File System by Using DCA�.
I have two identical 300GB PATA drives with 20GB root/boot and swap partitions. The slices are all identical as to size and location, i.e. c0d0s0 is root and c1d0s0 will be the mirror for root. (I will use "mirror drive" to refer to c1d0.
Proceeding through the steps I have verified I can boot the mirror. I have created the slices. I have used fdisk to put the master boot block on the mirror drive. I have installed grub on the mirror drive.
At this point I am on step six which reads:
"Create a new RAID-0 volume on the slice from the previous step by using one of the following
methods. Only the single slice can be included in the RAID-0 volume. " At that point I decided to try to proceed using the Enhanced Storage Tool from smc.
As to RAID-0 vs. RAID-1, it is my understanding from the doc that one must first create the RAID-0 volumes, each containing just the single slice, one for each of the two volumes that will be combined to make the RAID-1 mirror, hence my comment about RAID-0.
I see your point about using the -f option to force the creation of the volume for the mounted root filesystem. One would think that, if they included the option of using the Enhanced Storage Tool that perhaps it might work. (I did not see a way to force the creation of the RAID-0 volume.) Certainly using metainit with the -f flag makes sense.
Next step will be to go back and punt EST in favor of using metainit from the command line.
I get the feeling that no one at sun is actually trying what is in the manuals to ensure correctness.
Brian

[SOLVED]Where is the place to set program path for root in arch?

The situation is that I use qingy (set up according to wiki) as login manager and kde as desktop. When I use tty6 (agetty) to login (how comes that I cannot login as root, have to login as user and then su) /usr/sbin is in the path for root, but in kde when I su in konsole it is not. That caused me some headache with the latest kernel upgrade, since in kde the kernel will not upgrade properly, I have to do it on tty6. what is the proper way to set paths in arch? I looked at /root/.bashrc and that is almost empty. What obvious things am I missing? Has qingy to do with that problems? Any docs on that for arch? Besides firefox doesn't see any installed plugins, opera does. Plain Centrino laptop here.
Thanks, signor_rossi
Last edited by signor_rossi (2007-08-24 15:12:31)

Thanks for the answers. Investigated a little more and it seems it is really qingy what messes things up. Deactivated it and used "startxfce4" to start xfce and "startx" with "exec startkde" in my .xinitrc to start kde (once I figured out that in Arch "startkde" on command prompt alone does not work ) and voila, the path weirdness is gone in both DEs. Will look again into qingy when I have more time, since it is really nice when using different X setups (laptop on the go or laptop on docking with second display), like the eye candy. I guess I will stick to console now and simply use bash aliases for that purpose.
Thanks, signor_rossi.

Can you create multiple connections in smartview? for PROD and DEV?

Hi,
We have a production and development hyperion planning. In Smartview, we have successfully connected to PROD but can we create another connection to DEV?
or do we keep replacing the URL?
thanks

I think from 11.1.2.2 onwards the ability to add servers in Shared Connection is removed and an enhancement is filed to have that ability.
You can use private connection to connect to different instances
http://DEV:19000/aps/APS for Essbase
http://DEV:19000/HyperionPlanning/SmartView HyperionPlanning
If you are on 11.1.2.3 you can create an XML file and use that as your Shared Connection
Essbase Labs: Smart View News
Regards
Celvin
http://www.orahyplabs.com

[SOLVED] - Arch Boot Error: Unable to find Root Device /dev/sdb1

I had Arch running perfectly using /dev/sdb1 (versus Disk Label or UUID) and decided to do a update. After the Update I can't boot
to a running system, and I get this error message:
ERROR: Unable to find root device /dev/sdb1
You are being dropped into a recovery shell.
Is there an easy way to convert to UUID or Disk Label since the latest Upgrade doesn't allow me to continue to use /dev/sdb1 ??
I'd prefer not to have to rebuild both USB Flash Drives to get functional systems.
Any Help is greatly appreciated.
Suggestions?
Larry
Last edited by lkraemer (2012-02-21 15:14:02)

Check your grub and read https://wiki.archlinux.org/index.php/UUID#By-uuid
Edit:
https://bbs.archlinux.org/viewtopic.php … 0#p1059160
https://bbs.archlinux.org/viewtopic.php?pid=1059338
https://bbs.archlinux.org/viewtopic.php?id=135288
Last edited by karol (2012-02-21 01:07:21)

IBook is not starting up - "still waiting for root device"

The 600 MHz / 640 MB / 20 GB iBook did not want to wake up and after forced shutdown would not start up. grey screen. With MacOS X CD - "prohibition sign", MacOs 9 - no start at all
I had 2 partitions on the HD one with Tiger and other with 9.2.2 - none of them appear in the list of startUp folders. would not go into the Target mode.
I know there are few threads here with similar problem - I went through them but nothing of the suggestions would help.
Did reset the PRAM (only once though) - when I still heard the startUp chime
Did reset PMU
Left the machine unplugged for about 12 hours
Now I managed to get into single user mode while attempting to start up from a Tiger DVD. Here is what I see on the screen:
"using 1638 buffer headers and 1638 cluster IO headers
Extension "com.apple.driver.AppleTexas2Audio" has no kernel dependency.
(then there are 14 extensions listed that has no kernel dependency)
Firewire (OHCI) Apple ID 30 built-in now active, GUID 000393ff fe6ce976; max speed s400.
ADB present: 8c
ApplePMU: CLOCK RESET! PMU WAS PROBABLY RESET SOMEHOW!!
Security auditing service present
BSM auditing present
disabled
rooting via boot-uuid from / chosen: 7FF85 (a lot of symbols)
Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1"><IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Still waiting for root device
still waiting for root device
and so on with "still waiting..." again and again
also I did not hear start up sound anymore. Yesterday it was still audible.... can someone please help?!
iBook dual USB Mac OS X (10.4.5)

thanx for replying. Last night I finally managed to start up the machine using a FireWire ext HD as a StartUp Disk. Disk Utility and TechTool Pro and Disk Warrior are not showing the internal HD at all.
Since I was not able to use any start CDs including original MacOs X and 9 Cds maybe it is a problem with Data Cable that connects both HD and optical drive with logic board? It is hard to imagine why it would come to something like that. Overheat? I did not have enough free space on Tiger partition - 1GB. Maybe that. I am starting to look for a replacement HD....
iBook dual USB Mac OS X (10.4.5)

Succeeded for root on /dev/???

Similar Messages

Maybe you are looking for