Unable to Boot OVM Manager ISO from iLOM

Hi all,
I am trying to boot the OVM Manager ISO on a Fire X4150 using the console redirection but all that comes up is "Grub" and allows no further interaction. I've tried downloading the ISO multiple times, using an older version of the OVM installation ISO, and upgraded the iLOM firmware to the latest and greatest. When I use the OVM Server ISO, it boots up normally and starts the installation process. The machine that I am running the remote console from and has the ISO image is in the same rack as the server where I would want to install OVM Manager.
Getting physical access to pop a DVD in the drive is limited so really trying to figure out a way I can do this remotely.
Any one else have this issue and knows of a workaround?
Thanks,
Peter

FYI, update the FIRWARE on your Sun Fire X4150s. I was on a project a couple weeks ago and we where unable to use the ILOM to mount ISO files. After 10 hours of FUN, we discovered that its was a BUG! Update each server to the latest FIRMWARE, i.e. download the FIRWARE, and update each node from its web portal.
Sun x86 is FUN!
Roddy

Similar Messages

Cluster Not Available error when booting OVM server DOM0 from USB

Hi all,
I have been wanting to run OVM 2.2 from a USB stick for a while now. I ran through the install CD today and saw there was a 'minimal USB install' option on the installation screen. So I plugged in a 4GB USB stick, rebooted, and ran the USB install.
After a while, the install completed, OVM booted up perfectly it seemed, and I was happy.
The server had no local storage apart from this USB stick as we are going to be hooking it up to an iSCSI target for guest VM storage.
This was a new lab setup, so I got the VM Manager running on another system, connected to the USB booted OVM server, and went to create a pool.
Running the 'test connection' that worked fine.
Trying to add the pool - failed. I got the error 'Cluster Not Available'
On the OVM server I did a repos.py -l and nothing gets listed.
I understand that for HA you need a repository with shared storage. However, before I have used these same install CDs with a singe local hard disk, to get OVM server running, and it did so fine.
So what's different with the USB disk install that means you don't get a repository?
Do I have to create a special repository LUN, manually connect the OVM server to this, and then use repos.py to create it?
Cheers,
Jeff

Ok I have read, re-read related parts of the underground manual and have hit a brick wall with the 'simple' task of setting up a NIC for dedicated iSCSI traffic. The manual does not cover this task in the iSCSI SAN section.
So I'm in a catch 22.
My OVM server boots up, with it's single management NIC configured, but once booted - I don't want to connect to the iSCSI target via this network - I need it completely closed off.
I want to use another NIC (or bond of two) for dedicated iSCSI traffic to and from the OVM Server.
However, the underground manual strangely only seems to cover a single NIC configuration! It looks like he assumes you are going to be running iSCSI on your management NIC, which I can only think is incredibly bad practice.
I have installed OVM with the linux asknetwork - this did not give me the option to configure additional interfaces.
I then manually edited /etc/sysconfig/network-scripts/ifcfg-eth1 on the OVMServer, restarted network, restarted the entire box - I can ping my new NIC / IP locally from within the OVM server, but I can not connect to the iSCSI target, nor can I ping the iSCSI NIC on the OVM server from the target.
This is such a simple thing to try to achieve - super frustrating...
Jeff

Unable to boot Windows 7 Premium from an external harddrive

I recently gained an interest in playing microsoft based games, and just recently got my late 2013 macbook pro retina 15". I have been trying for several hours for the last two days to get bootcamp to boot Windows 7 Premium from a 500GB external harddrive without re-partiitioning my internal harddrive. I can get to the first screen of the Windows 7 Install asking about language, but neither my keyboard or mousepad respond with the windows installer. I assume this is because Windows 7 premium does not have USB 3.0 capability. Is there a workaround for this that doesn't involve partitioning my internal drive?

That's all fine and good, but I would strongly prefer not to have to use internal drive space for Windows. Even If I were to use the internal drive to install it, I would still run into the same problems of not having a keyboard or trackpad as I've seen other users having issues with. It stands to reason that if I had a working keyboard and mouse that I would be able to install it to an external hard drive, using a workaround method found here:
http://bleeptobleep.blogspot.fr/2013/02/mac-install-windows-7-or-8-on-external.h tml
If I had to partition my internal drive, what would be the absolute minimum amount of space I would need?

Unable to boot on Mac Mini from DVD burned from .iso image

I'm following the Beginner's Guide to try and install Arch on a Mac Mini "Late 2009".
I have downloaded archlinux-2014.10.01-dual.iso and associated .sig, and have verified it using the gpg2 command described in the guide (including the link to http://sparewotw.wordpress.com/2012/10/ … -sig-file/ which gave some assurance that the ambiguous answer produced by gpg2 was in fact legitimate).
I then used OSX's Disk Utility to burn the .iso file to a blank DVD. After verifying the burn, it ejected the disk.
When I re-inserted it, I received a message that the disk was unmountable, giving me the option to Ignore or Eject. I chose Ignore. Then I went to the System Preferences > Startup Disk, to see if it would at least appear there as an option, but it didn't.
(I should mention that I also burned the same file to another disk using a Windows machine, and when I inserted it into the Mac I got the same message, so I don't think it's corrupted media. (Bad reader, perhaps? eek.) )
That's where I stand. There are so many variables at play here (many of them Apple-induced, I think) that I've been unable to find a solution that fits my situation. Could someone please provide suggestions / pointers / answer?
Thanks,
Chap

Scimmia wrote:Ignore what OSX tells you, just try booting from it: http://support.apple.com/kb/ht1533
Exactly right. Holding the Option key caused a display of various bootable OSes, including the one I had just burned from the Mac using hdiutil (weirdly entitled "windows"). I selected it, and it booted. I now have a console. Problem solved. Thanks.
UPDATE: note that this boot disk *cannot* be seen or selected via the OSX System Preference > Startup Disk panel. Holding the Option key during startup seems to be the only way to select it.
Last edited by clh (2014-10-17 21:01:14)

[SOLVED]Unable to boot in UEFI mode from CD

Hello gents!
Here's the problem:
According to the beginner's guide I followed the instruction to test if I am in UEFI mode:
In case you have a UEFI motherboard, the CD/USB will launch UEFI Shell and display a message that
startup.nsh
script will be launched. Allow the shell to launch it. Then, to check whether you have booted into UEFI mode, load the efivars kernel module (before chrooting) and then check whether there are files in
/sys/firmware/efi/vars/
# modprobe efivars # before chrooting
# ls -1 /sys/firmware/efi/vars/
Well, the thing is that when I boot the CD no UEFI Shell is launched as well as no
startup.nsh
When I try to load the efivars I don't receive any message, so, I assume, the module is loaded; but the, when I invoke ls the message I receive is:
#ls: cannot access /sys/firmware/efi/vars/: No such file or directory
To me it looks that for some reason I am unable to access the UEFI mode when starting the CD iso.
Thank you guys for your courteous attention.
Have a wonderful day!!!
P.S. I've searched already in the following posts:
https://bbs.archlinux.org/viewtopic.php … 84#p148184
https://bbs.archlinux.org/viewtopic.php … 55#p148155
P.S.2
My mobo is an ASUS Maximus V Gene with i3770K on it.
Edit:
Ok guys! Thanks to all of you, but everything was brought about by my scarce knowledge of the mobo. Logging into the BIOS, in the boot section, you have to choose between normal DVD and UEFI DVD. When selecting the last, everything, I mean, the startup phase at least, went well.
Enjoy everybody
Any idea how to close/"solved" this forum tread?
Last edited by guidone (2012-09-11 20:34:21)

guidone wrote:Any idea how to close/"solved" this forum tread?
README: Forum Rules
Simply edit the original post by clicking on the 'edit' button at the lower right corner of it and prepend [SOLVED] to the title.

Boot arch netinstall iso from grub2

http://www.panticz.de/MultiBootUSB
I found this blog post and I successfully did it with linux mint but I couldn't do it with arch. what are the correct grub2 commands?
I tried with:
set root=(hd0,1)
loopback loop /arch.iso
linux (loop)/boot/vmlinuz26 iso-scan/filename=/arch.iso
initrd (loop)/boot/System.map26
I have no idea what System.map26 is and grub2 didn't choke when I offered it to him so I tried it. I couldn't find the normal initrd file.
Moreover, I know that there should be some boot=something parameter to the kernel in order for it to work but I couldn't guess the right one and I found no documentation about it.
If someone did it, I would appreciate your help
Thanks.

This is what I have:
menuentry "ArchLinux 2009-08 Core 64bit" {
set root=(hd0,1)
loopback loop /boot/iso/archlinux-2009.08-core-x86_64.iso
linux (loop)/boot/vmlinux26 iso-scan/filename=/boot/iso/archlinux-2009.08-core-x86_64.iso quiet
Get I get a "File not found" error.
*Edit*
I found /boot/grub/menu.lst (inside the iso) and found this:
title Boot Arch Linux Live CD
kernel /boot/vmlinuz26 lang=en locale=en_US.UTF-8 archisolabel=ARCHISO_KE1AECIE ramdisk_size=75%
initrd /boot/archiso_pata.img
There's the path for the initrd
*Edit #2*
"You need to load the kernel first." Well duh. You're supposed to do that grub.
Last edited by jordanwb (2009-11-10 19:37:19)

Unable to boot and install Windows 8.1 from a DVD

Hi, I have an ENVY 17 (3277nr) with windows 8.1 in it but I'm unable to update it since several months ago so I decided to reinstall the OS so I went to the windows site that lets you download an ISO image of windows 8.1 to burn it into a disc (right now I dont have a 4gb usb at hand but is also possible).
I already burned the disc by right clicking the ISO and selecting 'burn disc image' and changed the boot options but every time I turn on my computer all I see is a single underscore and then the regular windows 8 boot screen.
I already visited help wbesites in this regard and I've read things like the windows 8 UEFI thing (not on my laptop since I've upgraded from w7) and the security settings on the BIOS but none of them seem to fix the problem.
Additional details:
Oddly, when trying to open the burned dvd it only says 4.37gb out of 4.37gb, do you think my dvd drive might be damaged?
PLEASE, HELP ME OUT, BEEN 4 DAYS OF THIS HELL :/
This question was solved.
View Solution.

@killerpollo ,
Hello and thank you for posting on the HP support forum. The first thing I would try in this situation is to download and burn the ISO from another computer.
If you have already set your boot options to boot to CD/DVD and a new dvd is still not reading you may have a hardware issue with your dvd drive.
Does the DVD drive read dvds when you have booted up to windows?
As well I would try putting the image on a USB drive and try that.
I find on occasion when I use the windows software to make an ISO it is hit and miss. There are other software out there that you can try and some are free or what is known as share ware.
Now even if you burn a good image you started with a Windows 7 system. The actual image is more than a UEFI and you will not be able to read it if you system is set as a legacy system.
here are some things you will want to check out.
Boot UEFI or Legacy ---- tips
About UEFI and the Startup Menu
Free Image burn website.
Now if your system came with Windows 7 the product key that you have for your system will not work for Windows 8.1. This is one thing you will want to consider.
Let me know how things go.
Thank you again for posting and have a great day,
Please click the "Thumbs Up" on the bottom right of this post to say thank you if you appreciate the support I provide!
Also be sure to mark my post as “Accept as Solution" if you feel my post solved your issue, it will help others who face the same challenge find the same solution.
D5GR
I work on behalf of HP

[SOLVED] Unable to boot ISO on USB

Hello,
I'm unable to boot from USB. I have the following error : "Failed to install override security policy: (14) Not Found".
I tried the following solution : http://superuser.com/a/676059
But then my computer does not want to boot on the USB. I don't have any option for UEFI on my computer's BIOS (ASUS eeepc). Note that I don't want a dual boot with Windows and there is currently a broken archlinux installation on my hard drive.
Can anyone help me with this ?
Thanks. :-)
Last edited by filippo (2014-10-08 16:37:15)

Trilby wrote:How did you originally make the usb. Did you follow the wiki: https://wiki.archlinux.org/index.php/UE … B_from_ISO
Yes, I used :
dd bs=4M if=/path/to/archlinux.iso of=/dev/sdb && sync
And for creating the ISO (after copying the file for the workaround) :
genisoimage -iso-level 4 -o archlinux.iso archlinux
Mr.Elendig wrote:
This may be caused by buggy uefi firmware, check if there is a new one for your card.
Also in some cases it can be caused by fastboot/similar so check for that too in the bios.
I don't have an option for last boot. I'll check for a new uefi firmware !
EDIT: How do I check for that ?
I have an option on the BIOS "Launch EFIT Shell from filesystem" which search for Shellx64.efi on the available filesystem devices. However, it is calle shellx64_v1.efi and shellx64_v2.efi on the archlinux iso. May be this be a problem ?
Anyway, it's strange, the last time I installed Archlinux this eeepc (more than one year ago...) I didn't had any problem !
Last edited by filippo (2014-10-08 15:19:46)

Unable to start Managed servers from admin console

Hello!
We have a problem to start Managed Servers throw Node manager.
We get an error:
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Boot identity properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/boot.properties">
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Boot identity properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/boot.properties"
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Startup configuration properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/startup.properties">
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Startup configuration properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/startup.properties"
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server error log also redirected to server log>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
INFO: Server error log also redirected to server log
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Starting WebLogic server with command line: /software/psoft/pt851/webserv/peoplesoft/bin/startManagedWebLogic.sh >
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Starting WebLogic server with command line: /software/psoft/pt851/webserv/peoplesoft/bin/startManagedWebLogic.sh
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Working directory is '/software/psoft/pt851/webserv/peoplesoft'>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Working directory is '/software/psoft/pt851/webserv/peoplesoft'
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Rotated server output log to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out00001">
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
INFO: Rotated server output log to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out00001"
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server error log also redirected to server log>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
INFO: Server error log also redirected to server log
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server failed during startup so will not be restarted>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Server failed during startup so will not be restarted
<Jan 26, 2012 2:17:54 PM> <WARNING> <Exception while starting server 'PIA1'>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:662)
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'PIA1'
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:662)
Additional information:
weblogic 10.3.3
PT8.51.11
Linux x86_64 RH5
When we starting Manged servers manualy, it's works fine.
Thank you.

Hello!
The problem is found.
We tried to startup managed server by running startManagedServer.sh script, but this script expecting to get parameters.
The NodeManager unable to send parameters to script that appears in nodemanager.properties file (StartScriptName).
So, I created a new script startPIA.sh, that calls to startManagedServer.sh and sends it 2 parameters:
./startManagedWebLogic.sh $SERVER_NAME $ADMIN_URL
Now, we can start and stop managed servers from admin console, BUT we still have an error in NodeManager:
<Jan 29, 2012 11:15:39 AM> <INFO> <peoplesoft> <PIA1> <Server failed during startup so will not be restarted>
Jan 29, 2012 11:15:39 AM weblogic.nodemanager.server.ServerManager log
INFO: Server failed during startup so will not be restarted
<Jan 29, 2012 11:15:39 AM> <WARNING> <Exception while starting server 'PIA1'>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:662)
Jan 29, 2012 11:15:39 AM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'PIA1'
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:662)
There are no errors in managed servers logs.
PIA1.out:
<Jan 29, 2012 11:15:38 AM> <INFO> <NodeManager> <Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'>
Attempting to start WebLogic Server PIA1
No activity will be logged to this window.
Server activity will be logged to /software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1_*
PID for WebLogic Server PIA1 is: 27018
<Jan 29, 2012 11:15:39 AM> <FINEST> <NodeManager> <Waiting for the process to die: 26847>
<Jan 29, 2012 11:15:39 AM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Jan 29, 2012 11:15:39 AM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
The status of managed server in admin console is RUNNING, but "Status of Last Action" is FAILED.
What can be the reason?
Thank you.

How do I burn an .ISO from MSDN that Boot Camp will recognize?

Hello, I have a developers license that allows me to download the Windows 7 installers from the MSDN site in .ISO form. I can't seem to burn any of the installers to a disc that Boot Camp assistant will recognize as an installer DVD.
I have read and followed ALL of the solutions and still can not burn a recognizable disc. I have followed the IMGBURN instructions while in Parallels running Windows too.
Does anyone know how to create a compatible Boot Camp installer disc from the ISO's available on the MSDN network for Windows 7, preferably the 64-bit English Ultimate version?
I have tried the following instructions while in Windows 7 running in Parallels but they are either inaccurate or poorly written. If you have used these instructions with success, please translate into plain english because it just doesn't work in the VM I used.
1. Insert Windows Install disc into DVD drive
2. Using the build mode of imgburn, go to the advanced tab, then bootable disc and then select your DVD folder +--(saw that correction)+ in the extract boot image drop down list . Go ahead and extract the boot image and store it somewhere on your hard drive +(where is the extract button?)+
3. Go to the information tab and add your DVD drive as the source file
4. Options tab, check that file system is ISO9660 + IDF and UDF revision is 1.02 (should be anyway by default)
5. Go to Advanced tab, sub tab Restrictions and further sub tab ISO9660: Set Folder / File length to Level X and tick the four check boxes at the bottom (allow more than 8 directory levels, Allow more than 255 characters in path, Allow files without Extensions, Don’t Add ‘;1’ Version number to Files. (Note it’s this bit that actually solves the problem the rest is effectively just duplicating the existing disc)
6. Move to the bootable disc tab: Click the tick box to make the image bootable, emulation type to “none (custom)” and the browse and select the boot image you previously extracted from the windows disc. Finally set Sectors to load to 4.
7. Click the big create iso button to create the bootable iso. +(there is no big 'create' button, there is a build button though)+
8. And use that iso to burn a new install disc.
--THANKS, searching for the solution.

When I had boot issues with CDs, I would use BCD and create a bootable disc rather quickly. http://www.nu2.nu/bcd/ I can't verify that it works with Vista or Win 7, but you'd have to try it yourself. Very easy to use and hadn't failed me in the past.

[SOLVED] Unable to boot after downgrading from 2.6.38 to 2.6.37

After experiencing some issues with 2.6.38 and my Intel video card (external monitor support). I decided to go back to 2.6.37 for the time being.
I went into my /var/cache/pacman/pkg and typed in:
pacman -U kernel26-2.6.37-6-x86_64.pkg.tar.xz kernel26-headers-2.6.37-6-x86_64.pkg.tar.xz linux-api-headers-2.6.37-1-x86_64.pkg.tar.xz
warning: downgrading package kernel26 (2.6.38.2-1 => 2.6.37-6)
warning: downgrading package kernel26-headers (2.6.38.2-1 => 2.6.37-6)
warning: downgrading package linux-api-headers (2.6.38.1-1 => 2.6.37-1)
resolving dependencies...
looking for inter-conflicts...
Targets (3): kernel26-2.6.37-6 kernel26-headers-2.6.37-6 linux-api-headers-2.6.37-1
Total Download Size: 0.00 MB
Total Installed Size: 96.04 MB
Proceed with installation? [Y/n] y
(3/3) checking package integrity [#######################################################] 100%
(3/3) checking for file conflicts [#######################################################] 100%
(1/3) upgrading kernel26 [#######################################################] 100%
>>> Updating module dependencies. Please wait ...
>>> MKINITCPIO SETUP
>>> ----------------
>>> If you use LVM2, Encrypted root or software RAID,
>>> Ensure you enable support in /etc/mkinitcpio.conf .
>>> More information about mkinitcpio setup can be found here:
>>> http://wiki.archlinux.org/index.php/Mkinitcpio
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image "default"
==> Running command: /sbin/mkinitcpio -k 2.6.37-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [uresume]
:: Parsing hook [filesystems]
:: Parsing hook [keymap]
:: Generating module dependencies
:: Generating image '/boot/kernel26.img'...SUCCESS
==> SUCCESS
==> Building image "fallback"
==> Running command: /sbin/mkinitcpio -k 2.6.37-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [uresume]
:: Parsing hook [filesystems]
:: Parsing hook [keymap]
:: Generating module dependencies
:: Generating image '/boot/kernel26-fallback.img'...SUCCESS
==> SUCCESS
(2/3) upgrading kernel26-headers [#######################################################] 100%
(3/3) upgrading linux-api-headers [#######################################################] 100%
Then I rebooted and to my surprise I got stuck very early during the boot process.
sda: sda1 sda2 sda3
sd 0:0:0:0 [sda] Attached SCSI disk
Waiting 10 seconds for device /dev/sda3
mount: mounting /dev/sda3 on /new_root failed: No such device
ERROR: Failed to mount the real root device
Hopefully I had a 2.6.39rc3-mainline entry in my grub so I selected it and was able to boot as before. I then upgraded from 2.6.37 back to 2.6.38 and guess what... still unable to boot (same message).
What could be the root cause?
Thanks
Alphazo
Last edited by alphazo (2011-04-13 14:09:20)

Finally I got both 2.6.37 and 2.6.38 to boot again but boy it wasn't pretty. Before I start here is what I did before the boot issue.
- Running 2.6.38.2-1 from [Core]
- I also have 2.6.39rc3 from [miffe] repo with a dedicated entry in Grub (testing & recovery)
- Downgraded to 2.6.37 using from /var/cache/pacman/pkg:
pacman -U kernel26-2.6.37-6-x86_64.pkg.tar.xz kernel26-headers-2.6.37-6-x86_64.pkg.tar.xz linux-api-headers-2.6.37-1-x86_64.pkg.tar.xz
- Rebooted
- Boot would stop early during the process
- Booted 2.6.39rc3
- Upgraded to 2.6.38.2-1 via
pacman -U kernel26-2.6.38.2-1-x86_64.pkg.tar.xz kernel26-headers-2.6.38.2-1-x86_64.pkg.tar.xz linux-api-headers-2.6.38.1-1-x86_64.pkg.tar.xz
- Rebooted
- Boot would stop early during the process
- Booted 2.6.39rc3
- Downgraded to 2.6.37 using from /var/cache/pacman/pkg:
pacman -U kernel26-2.6.37-6-x86_64.pkg.tar.xz kernel26-headers-2.6.37-6-x86_64.pkg.tar.xz linux-api-headers-2.6.37-1-x86_64.pkg.tar.xz
- Rebooted
- Boot would stop early during the process
- Booted 2.6.39rc3
- Copied via USB kernel26.img and vmlinuz26 from a friend's PC (running same Arch configuration with 2.6.38 kernel)
- Rebooted
- This time, my friend's 2.6.38 would start
- Upgraded to 2.6.38.2-1 via
pacman -U kernel26-2.6.38.2-1-x86_64.pkg.tar.xz kernel26-headers-2.6.38.2-1-x86_64.pkg.tar.xz linux-api-headers-2.6.38.1-1-x86_64.pkg.tar.xz
- Rebooted
- This time, my 2.6.38 would start
- Downgraded to 2.6.37 using from /var/cache/pacman/pkg:
pacman -U kernel26-2.6.37-6-x86_64.pkg.tar.xz kernel26-headers-2.6.37-6-x86_64.pkg.tar.xz linux-api-headers-2.6.37-1-x86_64.pkg.tar.xz
- Rebooted
- Again I can boot from 2.6.37
So overall there have been two issues. One when dowgrading from 2.6.38 to 2.6.37 while running 2.6.38 and then when downgrading to 2.6.37 or 2.6.38 while running 2.6.39.
A bit confusing I admit but I think there is a glitch here that does bad thing when generating kernel26.img
Alphazo

Booting Arch-ISO from USB-Stick in UEFI mode fails

Hi there,
I'm running an Asrock H77M-ITX UEFI mobo. On this system I've already installed Arch on a Samsung 830 SSD (GPT formatted) - but in BIOS legacy mode because I've written the Arch-ISO image with "dd" to an USB-Stick (and UEFI boot mode wasn't even presented at boot).
Out of curiosity I've re-formatted the stick and copied Arch-ISO following https://wiki.archlinux.org/index.php/Un … B_from_ISO.
Now I could start the ISO in UEFI mode, but it failed to start gummiboot with the "No loader found. Configuration files in \loader\entries\*.conf are needed." error message, concerning a problem with gummiboot.
Following some advice on the forum, I did this:
- install refind-efi 0.4.7-2
- copy /usr/lib/refind/refindx64.efi to [USB]/EFI/boot and renaming it to bootx64.efi (i.e. replacing the original bootx64.efi from gummiboot)
- Create a new file in the same directory ([USB]/EFI/boot/) called refind.conf
- Add this to it:
textonly
scanfor manual
menuentry Arch {
loader /arch/boot/x86_64/vmlinuz
initrd /arch/boot/x86_64/archiso.img
options "gpt loglevel=7 add_efi_memmap none=UEFI_ARCH_x86_64"
With this I can launch Arch-ISO from the USB-Stick in UEFI mode and I can choose Arch from rEFIND. Then Arch-ISO starts booting but it always stops at the same point with this message:
sd 6:0:0:0: [sdb] No Caching mode page present
sd 6:0:0:0: [sdb] Assuming drive cache: write through
sd 6:0:0:0: [sdb] Attached SCSI removable disk
ERROR: '/dev/disk/by-label/' device did not show up after 30 seconds ...
Falling back to interactive prompt
You can try to fix the problem manually, log out when you are finished
sh: can't access tty: job control turned off
[rootfs /]#
sdb is the USB-Stick from which I start Arch-ISO. Again - I didn't use dd to write the ISO to the stick.
Maybe this is pretty easy to solve, but I have to admit that I'm somewhat stuck
Last edited by swordfish (2012-11-19 21:31:43)

WonderWoofy wrote:See what the difference is between archiso and archboot maybe? Seriously, have you made any effort whatsoever?
Of course. Read:
The "Main Page" ( https://www.archlinux.org/ ) states:
"You've reached the website for Arch Linux, a lightweight and flexible Linux® distribution that tries to Keep It Simple."
"Keep It Simple". Yeah!
In line with that, the "The Arch Way" page ( https://wiki.archlinux.org/index.php/The_Arch_Way ) states:
"The following five core principles comprise what is commonly referred to as the Arch Way, or the Arch Philosophy, perhaps best summarized by the acronym KISS for Keep It Simple, Stupid."
The ArchWiki ( https://wiki.archlinux.org/ ) links to several other pages, such as these:
The "Forum Etiquette" page ( https://wiki.archlinux.org/index.php/Forum_Etiquette ) states under "Ineffective Discussion":
"Arch is a Do It Yourself community" and "treat others as you would be treated; respect them and their views". I am very much a "do it yourself" person -- that's why I like The Arch Way. I also go by the Golden Rule stated here.
Now, everyone is a newbie at some time. I and other posters here are obviously newbies with respect to ArchLinux. Even experts were newbies at one time. Newbies, by definition, do not necessarily know what they're doing, or where to find information. Hence, Arch's "Beginners' Guide" and such. Hence, posts on this board from newbies asking for help.
As regards initial installation of ArchLinux, and consistent with the above, the FAQ ( https://wiki.archlinux.org/index.php/FAQ ), under "Q) Arch needs an installer. Maybe a GUI installer", states:
"A) Since installation doesn't occur often (read the rest of this article to know more about what rolling release means), it is not a high priority for developers or users. The Installation Guide and Beginners' Guide have been fully updated to use the command-line method. If you're still interested in using an installer, consider using Archboot."
So the basic installation instructions explicitly state that Archboot is not needed.
The "Installation Guide" ( https://wiki.archlinux.org/index.php/Installation_Guide ) says nothing about either Archboot or Archiso.
The "Beginners Guide" ( https://wiki.archlinux.org/index.php/Beginners%27_Guide ) says nothing about either Archboot or Archiso.
The "Archboot" page ( https://wiki.archlinux.org/index.php/Archboot ) is consistent with the above information, because it states:
"Archboot is a set of scripts to generate bootable media for CD/USB/PXE.
It is designed for installation or rescue operation."
The "Archiso" page ( https://wiki.archlinux.org/index.php/Archiso ) states:
"Archiso is a small set of bash scripts that is capable of building fully functional Arch Linux based live CD and USB images. It is a very generic tool, so it could potentially be used to generate anything from rescue systems, install disks, to special interest live CD/DVD/USB systems, and who knows what else."
So the pages describing both Archboot and Archiso clearly state that these tools are oriented towards already-existing installations -- even though it seems that they might be used, in certain circumstances, for initial installations.
I happen to be very new at playing around with installing Linux distros (although I've used Unix/Linux as a regular user for more than 30 years), and am brand new with respect to ArchLinux. I only began playing with it this past Saturday. So I would expect a bit of useful help as opposed to "RTFM!" I will soon get past the need to RTFM for basic tasks, but I have a way to go.
The fact is that for me and a number of other new ArchLinux users, the installation guides simply do not work. C.f. my post https://bbs.archlinux.org/viewtopic.php?id=153170 . I've done a lot of googling as well as searching the archives on this board, and others have come up against the same show-stopping installation problems that I have. I and others have posted to several recent threads on this board, trying to get past the problems, so far with no success.
Now, the.ridikulus.rat had written:
"You guys are using Archboot's kernel options for Archiso. Thats the issue in both the cases."
Given that neither of these sets of scripts were used by me or swordfish, this comment is not useful.
Given the above, can you or anyone else tell us what Archiso or Archboot might do to help us with our installation problems? Also, can you tell us how we, as newbies, ought to have found out how these might help?
Alan

Booting ISO from Grub2 without Loopback support

I am trying to boot an archlinux install ISO from grub2 menu, but I have no loopback support. I am not sure how I got to this point, but I installed Ubuntu first (just to test out the system and make sure that UEFI works fine. Then I booted the ISO file just fine, (I used grub-config to modify the bootup). During the install, I used cgdisk to redo my partition tables. After that, cgdisk said something about the partitions not taking effect until I rebooted... after reboot, I now get the grub console and nothing else. UEFI bios will not allow booting USB, so the only way I can do this is via this grub console.
The only things I did were; create a new partition at the end of the drive to store my ISO file and mkfs.ext4 /dev/sda2... The UEFI partition is still intact from ubuntu (i did not format that one).
I tried following this guide, http://wiki.grml.org/doku.php?id=rescueboot ,but it wasn't successful.
insmod part_msdos
insmod ext2
set root='(hd0,4)'
linux /arch/boot/x86_64/vmlinuz boot=live findiso=/archlinux-2014.01.05-dual.iso toram
initrd /arch/boot/x86_64/archiso.img
When I try to set the linux variables, i get an error that says /arch/boot/x86_64/vmlinuz cant be found.
I tried putting a livecd onto a usb drive, but when I get all of the parameters set and type boot, it just reboots the machine and goes right back to the grub console.
Any help would be greatly appreciated.

I really don't understand why you would go find some random guide and not check our wiki.

Unable to start Managed server from admin console using nodemanager

I changed the ip address and hostname of the server on which Weblogic Server 10.3.5 is running. After that I am unable to start the managed servers using Admin console. Is there any changes in the nodemanager configuration files which need to be done to start the managed servers from admin console.

Hi there,
Can you check the following configuration in Weblogic admin console ?
1- Check which listen address mentioned under the Machine configuration ( Environment > Machines > select appropriate nodemanager machine >Configuration > Node Manager ). If it is pointing to old host name, change it to new one.
2- Once you done with Step 1. Check whether the machine is reachable or not. ( Machine > [Your Machine] > Monitoring > status.
3- If still isuse persists.. Check the managed server startup log files ( for eg:- managedserver1.out under the path $DOMAIN_HOME\Servers\managedserver1\logs directory.
Thanks
Lakshman

Booting from iso from usb drive

I want to boot arch from iso from my thumb drive. Based on the wiki article on Grub, I've put this entry to my grub.cfg:
menuentry "Arch Linux x86_64" --class iso {
set isofile="/iso/archlinux-2014.05.01-dual.iso"
loopback loop $isofile
linux (loop)/arch/boot/x86_64/vmlinuz archisolabel=ARCH_201405 img_dev=/dev/disk/by-label/IKAROS img_loop=$isofile earlymodules=loop
initrd (loop)/arch/boot/x86_64/archiso.img
Grub seems to load the kernel fine, but the kernel then fails to mount the drive with the following message:
:: Setup a loop device from /iso/archlinux-2014.05.01-dual.iso located at device /dev/disk/by-label/IKAROS
:: Mounting '/dev/disk/by-label/IKAROS' to '/run/archiso/img_dev'
[ 9.556128] FAT-fs (sdb1): IO charset iso8859-1 not found
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
ERROR: Failed to mount '/dev/disk/by-label/IKAROS'
Falling back to interactive prompt
You can try to fix the problem manually, log out when you are finished
sh: can't acces tty: job control turned off
[rootfs /]#
I know I could dd the iso on the usb stick and probably avoid this, but I like my setup with several isos in a directory and appropriate grub entries. Does anybody know how to fix this?
Last edited by Remedan (2014-05-02 19:23:41)

elken wrote:I made it sometime last year and it has a load of ISOs on it but yes Arch was one of them. It was MultiCD sorry, not yumi. Like I said, it was a year ago. MultiCD was a piece of cake.
Well, with MultiCD I can create an image which can boot multiple isos and write it on the drive. The thing is, I want to be able to use the drive as a storage device also. So I'd like something that would allow me to have a FAT partition on the drive and boot from that.
But the core of my trouble is that the live arch doesn't seem to be able to handle the FAT partition.

Unable to Boot OVM Manager ISO from iLOM

Similar Messages

Maybe you are looking for