Boot ISCSI LUN from LDOM

Hi,
We are exporting bootable LUNS from a 7110 array to LDOM's on our Blades. The array was rebooted today. Since the reboot we are unable to connect to the hosts booted from the array.
I did not configure this but have the task of fixing it.....
We are running LDOM 1.2,REV=2009.06.25.09.48
So, does the LDOM boot directly from the LUN from the LDOM OBP?
The syntax in this link causes the below failure;
http://wikis.sun.com/display/OpenSolarisInfo/Configuring+iSCSI+Boot+for+SPARC+Systems
Unknown key 'iscsi-target-ip'
Unknown key 'iscsi-target-name'
Unknown key 'iscsi-lun'The ISCSI LUNS are seen by the host.
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 273>
/pci@0/pci@0/pci@2/LSILogic,sas@0/sd@0,0
1. c1t2d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 32 sec 279>
/pci@0/pci@0/pci@2/LSILogic,sas@0/sd@2,0
2. c3t600144F04B73EB660000000000000000d0 <SUN-SOLARIS-1 cyl 32766 alt 2 hd 4 sec 736>
/scsi_vhci/ssd@g600144f04b73eb660000000000000000
3. c3t600144F04B713A260000000000000000d0 <SUN-SOLARIS-1 cyl 32766 alt 2 hd 4 sec 736>
/scsi_vhci/ssd@g600144f04b713a260000000000000000
4. c3t600144F04B9910370000000000000000d0 <SUN-SOLARIS-1 cyl 32766 alt 2 hd 4 sec 1200>
/scsi_vhci/ssd@g600144f04b9910370000000000000000Nothing has changed on the LDOM controller domain.
I'm really stuck so any input would be appreciated.

Im getting the following error as well.. Was there any solution to this please ?
Im not using any LDOM. Just on the h/w platform on T5140
{0} ok boot net Boot device: /pci@500/pci@0/pci@8/network@0 File and args:
Unknown key 'iscsi-target-ip'
Unknown key 'iscsi-target-name'
Manual Configuration: Host IP, boot server and filename must be specified
ERROR: boot-read fail
Can't open boot device
{0} ok
Edited by: 836793 on Feb 15, 2011 12:36 AM

Similar Messages

LDOM in iSCSI LUN - iSCSI logging in too early

Hi there,
I am having a very strange problem. I'll describe my setup first.
The hardware hosting the LDOM environment does not have enough local disk space to support the number of required domains so to get around this problem the disks used by the configuration are, in fact, iSCSI LUNS mounted from a Netapp.
This works fine once they are up and running, but I am having problems when the host server is rebooted because the services do not seem to be starting in a sensible order. If you look at the dmesg output at [http://www.joshberry.plus.com/dmesg.txt|http://www.joshberry.plus.com/dmesg.txt] this is the boot up sequence for the server.
You can see the iSCSI failing to log in first, with the associated errors where disks are unavailable:
Apr 30 14:55:21 fhw-dataarchive02 iscsi: [ID 286457 kern.notice] NOTICE: iscsi connection(7) unable to
connect to target iqn.1992-08.com.netapp:sn.101204418:vf.c254e0d0-1836-11dd-a621-00a0980aec76 (errno:128)Lower down in the boot sequence the reason for this becomes obvious:
Apr 30 14:55:26 fhw-dataarchive02 mac: [ID 469746 kern.info] NOTICE: e1000g1 registered
Apr 30 14:55:26 fhw-dataarchive02 e1000g: [ID 766679 kern.info] Intel(R) PRO/1000 Network Connection, Driver Ver. 5.1.8
Apr 30 14:55:26 fhw-dataarchive02 e1000g: [ID 801725 kern.info] NOTICE: pciex8086,105e - e1000g[1] : Adapter copper link is down.
Apr 30 14:55:29 fhw-dataarchive02 e1000g: [ID 801725 kern.info] NOTICE: pciex8086,105e - e1000g[1] : Adapter 1000Mbps full duplex copper link is up.Here, as far as I can see, the network is down when the LDOM is initiated and tries to get access to the iSCSI, which is never going to work.
So, firstly, have I got the right end of the stick here?
If I am on the right track my question is: can you change the order that the system initialises everything so that the network will be brought up before the guest domains are initialised.
Thanks
Josh

Don't use CHAP for discovery.
Enable CHAP afterwards.
Andy

Using iscsi luns as vdiskserverdevices

Hi
I am new to LDoms and was wondering if anyone has any experience of using iscsi luns (presented by zfs volumes on an X4500) as vdiskserverdevices . In my case the iscsi luns were presented to the service domain (in this case the control domain) and were correctly visible and accessible from it. However when presented as vdisks to the guest domains, for use as the root disk, the guest domains could not access/see the disks. When the guest domain was booted for a jumpstart install one of the first messages was that it couldn't access the vdisks and this was confirmed during the install process when a boot disk couldn't be found. AFAIK solaris can't boot of iscsi luns (without iscsi HBA's) but I figured that hiding the iscsi lun behind the vdiskserver would work -but no such luck. Any advice on whether this is possible would be most welcome.
As an unwanted work-around I created a couple of large files (aprox 420 Gb and 920Gb) and presented these instead as the vdsdevs. This time the smaller 420Gb couldn't be seen at all by the guest domain while the larger file showed up as a SUN 920Gb type disk though while partitioning it, it only showed about 100Gb as the disk size. Any pointers as to what I'm doing wrong here is also most welcome.
My hardware consists of 2* T5220 running Sol10 08/07 with latest recommended patches and firmware and an X4500 which is being used to provide all (root and data) storage for the guest domains.
Thanks
Saurav

Hi there,
I am setting up a platform when the guest domains are installed into iSCSI LUNS and it is working fine.
I am using LUN's expported from a NetApp rather than using ZFS but that shouldn't matter. They appear like this on my test platform:
root@solarisvh # iscsiadm list target -S
Target: iqn.1992-08.com.netapp:sn.********
        Alias: -
        TPGT: 2000
        ISID: 4000002a0000
        Connections: 1
        LUN: 0
             Vendor: NETAPP
             Product: LUN
             OS Device Name: /dev/rdsk/c4t0d0s2And I can add it into a guest domain by running:
ldm add-vdsdev /dev/rdsk/c4t0d0s2 examplevol1@primary-vds0I found that I had to pop in an label the disk (using format) on the first use for it to be picked up but after that it worked fine and I could boot up and install an OS into the LUN.
Josh

Install OVM server 3.2.1 on iSCSI LUN

Hello friends,
I have a Cisco Blade and would like to boot OVM server from an iSCSI lun. I create a LUN from a SAN and presented the lun to the blade. When the server boots up, it sees the iSCSI lun just fine but when I tried to install OVM server 3.2.1, it did not detect that LUN. I tried to install Oracle Linux 6.3 and it sees the LUN ok. Is there a way to make OVM server to see that LUN.
thanks,
TD

I have done to many oel and ovs install lately such that they are blurring together...
On the OVM 3.2.1 install watch closely for a place to add support for non local storage. I remember seeing a small prompt in some of the installs but it may have been from some of the OEL installs (I have also been doing OEL 4, 5, & 6) & not OVM.
Sorry I can't remember right now. If I get a moment and try to run the install process I will and report back if no one else does.

[VHD][BOOT][UEFI] Boot Windows 8 From a VHD Drive On a GPT Disk Using UEFI BIOS

I had been dual booting two copies of Windows 8 prior to getting a new rig without any issues. Once I installed Windows 8.1 I can no longer boot a VHD from the GPT partitioned drive.
My PC specifications
Intel i7-4770k
ASUS SABERTOOTH Z87
16GB KINGSTON HYPERX BEAST DUAL-DDR3 2400MHz
2GB NVIDIA GEFORCE GTX 660 Ti
120GB INTEL 520 SSD
4TB WD CAVIAR BLACK WD2002FAEX
4TB WD CAVIAR BLACK WD2002FAEX (two way mirror = storage spaces)
15x BLU-RAY Writer Drive
CORSAIR 750W PRO HX750-80
Corsair H60 Hydro Series High Performance CPU Cooler
10/100/1000 GIGABIT LAN PORT
Windows 8.1 Pro x64
So I basically copied my existing VHD to the new data drive and created the relevant BCD entry, when I chose to boot from the VHD I am presented with an error saying Windows cannot boot and to choose another OS or the troubleshooting options (I’ll post the
exact error later as I am at work at the moment).
I can boot the VHD inside Hyper-V without any issues, it just wont boot natively. I also created a brand new Windows 8.1 VHD and still the same thing happens. Once I created a new VHD I used “bcdboot j:\windows /s j:” to insert the attached VHD into the BCD
store.
So existing or brand new VHD’s don’t seem to work for me, any advice would be appreciated.
Mike Park

I posted this issue on Neowin and someone kindly pointed out the answer, it's to do with storage spaces:
http://www.neowin.net/forum/topic/1191873-native-boot-vhdx-from-second-drive/#entry596152197
Quote
What types of drives can I use with Storage Spaces?
You can use commodity drives attached via Serial-Attached SCSI (SAS), Serial ATA (SATA), or USB. Storage layers that abstract the physical disks are not compatible with Storage Spaces. This includes VHDs and pass-through disks in a virtual machine, and storage
subsystems that layer a RAID implementation on top of the physical disks. iSCSI and Fibre Channel controllers are not supported by Storage Spaces.
From: http://social.techne...stions-faq.aspx
Mike Park

Two native iSCSI LUNs in a 2012 storage pool

I have a Windows Server 2012 storage pool connected to a single SAN VIA iSCSI. I'd like to add a second SAN and present the virtual disks as part of the same pool to extend my total storage. Is this possible?

Hi,
I do not have the environment to test if add LUNs from different SAN will work or not but personally I believe it will work as SAN (LUN) is supported to be added into a storage pool.
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Patches needed to see extra luns from HDS SAN

Hi,
I hope you can help, i am having problems at the moment getting two solaris 9 servers to see more than one lun from the attached SAN on both machines. Nothing is being shown in cfgadm -al.
The hardware is
TWO Qlogic 2300 FC HBA Cards attached to a tagnastore AMS200 Hitachi SAN. This is connected through a silkworm brocade switch. At present i can only see the first lun assigned and nothing else.
Any ideas ?
Cheers,
Mike

wdey,
The link you supplied in your response is the answer.
You can look at the devices on the FC boot paths, but not while the OS is running.
I have a test server I could reeboot to try what you have in your document, and it does work.
Too bad Cisco could not create a linux util rpm that would allow looking down the fabric while running. Im quit sure emulex has this kind of util, called HBAanywhere...at least for solaris.
In any case, thanks for the link to your article, it was VERY good!
My problem with seeing a shorter list of luns on 2 of my FC paths may get solved this afternoon by a change my SAN admin is going to make.. If it does I will post the fix.

Oracle VM 3.1.1: Using iSCSI LUN's as Device-Backed Virtual Machine Disks?

Will Oracle VM Manager 3.1.1 support the use of iSCSI LUN's as device-backed virtual machine disks? i.e., Can iSCSI LUN's be treated like directly-attached storage (DAS) and used as virtual machine disks?
Eric Pretorious
Truckee, CA

user12273962 wrote:
I don't personally use ISCSI. BUT, I don't see why you can't create physical pass through attachments to virtual guests using ISCSI LUNS. It is no different than FC or direct attach storage. Worst case scenerio... you can create a repo on the ISCSI LUN and then create virtual disks.
Oracle VM Getting Started Guide for Release 3.1.1Chapter 7. Create a Storage Repository
A storage repository is where Oracle VM resources may reside... Resources include virtual machines, templates for virtual machine creation, virtual machine assemblies, ISO files (DVD image files), shared virtual disks, and so on. This would have the effect of using file-backed virtual machine disks but at least they'd be centrally-located on shared storage (and, therefore, the virtual machine could run as an HA guest)
budachst wrote:
I have kicked this idea around as well, but I decided do it slightly different, by providing the storage repo via multipathed iSCSI and use iSCSI within my guests if needed for better speed or lower disk latency.
If you want to use iSCSI as the virtual devices for your guests in a clustered server pool, you'd have to grant access to all of your iSCSI targets to any VM server and I was not feeling comfortable with that. I rather grant only the guest directly access to "its" iSCSI target. So I will keep all of my guests system images on the clustered server pool - and additionally also the virtual disks that don't need a high performance and have the really heavy-duty vdisks as separate iSCSI targets.That seems logical, Budy:
<ul>
<li>Use a multipathed iSCSI repository for hosting the virtual machine's disk image, and then;
<li>Utilize iSCSI LUN's for "more performant" parts of the guest's file system (e.g., /var).
</ul>
I'm still puzzled about that image, though. +i.e., the fourth image from the bottom of Chapter 7.7, "Creating a Virtual Machine" ("To add a physical disk:...") where it's clear that the exising "physical" disks are actually iSCSI LUN's that are attached to the OVM server.+
I suppose that I'll have to configure some iSCSI LUN's and try it out to be certain. Just another tool that I don't have +but will need to add to my toolbox+.

P2v conversion of sap ecc6 host w/ ISCSI Lun

Hello, I am looking for some feedback here please.
Background:
We have an Physical SAP Host that has ISCSI LUNs (volumes) attached with are formatted as NTFS file system. These are then presented to the OS as drive letters L:\ (Logs) and D:\ (Database) and M:\ (Backups).
We want to virtualize the entire machine and create a virtual machine on ESX Virtual Infrastructure 3. We have an EMC AX4 SAN.
The question is how to do it?
There appear to be two ways:
1. The first way and perhaps the easier way would be to stop SAP, stop the Database and log off the ISCSI adapters from the OS. Then virtualize the physical machine (P2V) with only the C:\ drive. When the machine comes up as a virtual host, it should reattach directly to the existing LUNs through its internal configuration and attach to the existing LUN. We may have to fiddle around with the drive letters to get them to be as previously L:\ D:\ and M:\ but essentially there is not really anything else to do. The internal EMC Powerpath should still be working properly. The ESX Host is already connected and configured to have one physical adapter on the iSCSI VLAN; thus, there should be no additional configuration as long as the VM sees the same network.
2. The second way would be to perform the entire P2V migration and create a brand new gigantic LUN on the SAN and virtualize the entire physical host including all the attached drives. The disadvantages here would be that the entire machine would be on one gigantic LUN and each Drive Letter would be a different file. (I believe).
To complicate things we also have a Cluster with three ESX Hosts. VMotion between Hosts would be no issue under either solution.
I would like to get feedback on how to proceed and hear about any pros/cons and or any success or failure stories.
Thank you,
Pete

Hi Nadeem
Save your init<SID>.ora.
You can try to set processes and sessions parameters in the init<sid>.ora to the following value :
processes = 800
sessions =1600
- Stop your instance
- Stop your DB
- Recreate the spfile
- Start your DB
- Start your instance
If the issue does not solve the problem, you return back.
Otherwise, when you start your instance is that the processes dw.sap <SID> _DVEBMGSXX starts then dies or they do not start?
Best regards.

Add iSCSI LUN to Multiple Hyper-V Cluster Hosts?

Is there a way to connect multiple Hyper-V hosts to a CSV LUN without manually logging into each and opening the iSCSI Initiator GUI?

Is there a way to connect multiple Hyper-V hosts to a CSV LUN without manually logging into each and opening the iSCSI Initiator GUI?
Here's a good step-by-step guide on how to do everything you want using just PowerShell. Please see:
Configuring iSCSI storage for a Hyper-V Cluster
http://www.hypervrockstar.com/qs-buildingahypervcluster_part3/
This part is should be of a particular interest of yours. See:
Connect Nodes to iSCSI Target
Once the target is created and configured, we need to attach the iSCSI initiator in each node to the storage. We will use MPIO to
ensure best performance and availability of storage. When we enable the MS
DSM to claim all iSCSI LUNs we must reboot the node for the setting to take affect. MPIO is utilized by creating a persistent connection to the target for each data NIC on the target server and from all iSCSI initiator NICs on our hyper-v
server. Because our hyper-v servers are using converged networking, we only have 1 iSCSI NIC. In our example resiliency is provided by the LBFO team we created in the last video.
PowerShell Commands
1
2
3
4
5
6
7
8
9
Set-Service -Name
msiscsi -StartupType Automatic
Start-Service msiscsi
#reboot requres after claim
Enable-MSDSMAutomaticClaim -BusType
iSCSI
Set-MSDSMGlobalDefaultLoadBalancePolicy
-Policy RR
New-IscsiTargetPortal –TargetPortalAddress 192.168.1.107
$target = Get-IscsiTarget
-NodeAddress *HyperVCluster*
$target| Connect-IscsiTarget
-IsPersistent $true -IsMultipathEnabled
$true -InitiatorPortalAddress
192.168.1.21 -TargetPortalAddress 10.0.1.10
$target| Connect-IscsiTarget-IsPersistent$true-IsMultipathEnabled$
You'll find a reference to "Connect-IscsiTarget" PowerShell cmdlet here:
Connect-IscsiTarget
https://technet.microsoft.com/en-us/library/hh826098.aspx
Set of samples on how to control MSFT iSCSI initiator with PowerShell could be found here:
Managing iSCSI Initiator with PowerShell
http://blogs.msdn.com/b/san/archive/2012/07/31/managing-iscsi-initiator-connections-with-windows-powershell-on-windows-server-2012.aspx
Good luck and happy clustering :)
StarWind Virtual SAN clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

ISCSI LUN doesn reconnect if CHAP authentication is enabled on 7410

I have a Windows 2008 R2 server as an iSCSI initiator connecting to the Sun storage 7410 NAS. Everything appeared to be working except the iSCSI LUN is unable to reconnect to the initiator as long as I have CHAP enabled (initiator authentication only). I tested the same initiator configuration with another iSCSI target using StarWind and it didn't have the same problem. Any ideas? Thanks

I have the same issue. Unable to connect from 2008r2 until i disabled CHAP. We are running 2010Q3p1.

Booting two Macs from one external drive: 10.8 and App Store?

I boot two Macs from one external harddrive. Does this mean that when 10.8 is sold exclusively via the App Store and thereby linked to a unique hardware identifier, I am going to have issues with activation/authentification each time I switch machines? I have avoided the App Store since I discovered that an app I bought there, and which I really needed to open automatically on log-in, had to be manually re-activated with my Apple ID after every switch (so that I eventually deleted it and reverted to an earlier, non-App Store version).

Welcome to the forum!
There are a couple of "solutions" to your problem. The easiest, and possibly the best for you (although it is a bit slower) is to copy your catalog onto the external drive as well.
Then when you plug in the drive, you will always have your latest catalog for access.
The other way is to keep a local copy of your catalog, and copy it onto the local drive as a way to transfer it from one computer to the other.
This has the problem of possibly not being in sync, that is, you forgot to copy it over once and did some editing. Then you would end up with essentually two different catalogs, instead of one in two places.
You can copy the catalog either with your OS, or you can "export as catalog" and specify the external drive as the destination. Then, on your other computer, "import from catalog" and only take the meta-data settings (it's on the import dialog box).
Personally, when I'm traveling, I have my catalog on my external drive as well. It just makes life easier, and I don't have to worry about it being out of sync, or losing it (and not the images).
So, I would go with the first method, at least to start. To get your catalog over there, you can either export as catalog or copy it, either one will work.
You can find the location of your catalog file (if you don't know where it is) in the catalog settings menu prompt. Both the location and the name will be displayed.
Cheers!

Can't boot G5 even from OS install disk. Help?

I've trolled the message boards 25 pages deep and searched all the "Can't boot my G5" threads and still haven't found anyone describing what my machine is doing so thought I'd start a new thread in the hopes someone can help me out.
Ok I have a G5 dual processor machine. (Power PC chip, not Intel) Things went bad when I tried to do an Archive and Install of Leopard (OS 10.5) The install looked as normal until I got to one minute left on the install. At that point the install never progressed. I thought maybe it was doing some behind the scenes processing and decided to leave it over night. The next day my machine was still hung on that One minute left. So obviously it was a failure. Of course now the problem is I have an install that never completed of the OS and so that partition is, I assume, unbootable. Wiped away the Tiger OS and did a 99% install of Leopard. So I had to shut down by holding the power button.
I think to myself, "No worries I can just boot from my 2nd partition holding down the Option key to select it on the boot up screen". I always keep a partition with an OS on it for times like these. So I reboot, hold option key, select my other partition, things look OK. I get the grey screen with the Apple logo and I get the wheel animation turning. (Not beachball of death but the typical circular, almost sun ray configuration thing) At this point, usually the screen will go black for a moment before the desktop loads. However, in my case once the screen goes black after the load screen, it stays black. Now let me say the monitor does NOT turn off. There is a definite difference when I manually turn the monitor off. When off it's truly black. But this is like a power on black, not true black. (If you need me to explain this better feel free to ask me to clarify)
So the untouched, pristine Tiger partition boot is a No Go. I figured I'd then give up on trying to put Leopard on my desktop machine (I use it on my laptop) and reinstall the original OS and system software from the system disk that came with my G5. I boot machine holding down eject button, place the disk in, close the drive door and shut down again by holding power button. Reboot holding C key and the same routine happens with booting from the disk. Gray Apple logo screen, sun ray circle moving, screen goes black on the attempted transition to desktop .. but stays black. I also tried booting with my Disk Warrior disk to no avail. Same thing happens. (Also tried booting from disks by selecting them manually from booting with Option key down) At first I wondered if it was a monitor issue. That maybe my desktop was up but there was an issue with the signal being passed to the monitor on the resolution jump. Thought perhaps hitting the Eject key on the keyboard when I had attempted to boot from the partition (not from disk on this test) would tell me if it was a monitor issue. If it was a monitor issue, the disk tray should open. But alas, no.
So since I cannot boot normally from any partition or disk I decided to boot into single-user mode.
I did the fsck -fy thing and it told me everything was ok. I had also previously installed applejack and I ran that and short of correcting a few permissions and dumping some unneeded caches it came back with a system OK.
At my wits end I booted into target disk mode and ran Disk Warrior on both the original half installed OS partition and the back up emergency boot up partition from my laptop. Again, everything OK. Hoped against hope that I could actually install an OS onto my G5 from my laptop but I was only given the option of being able to do it from my laptop with the Leopard disk and it would only allow me to do it if I used Disk Utility to completely format that drive first. No, thanks.
Re-attempt to boot G5. Failure. So now I turn to hardware. Disconnected everything beside the keyboard and mouse. Try again. Fail. Pulled a couple sticks of Crucial memory out of the machine and left the stock RAM. No dice. Pressed the small power unit reset button under the RAM slots. No change. Zapped the PRAM. Still nothing. Try to boot in Safe mode holding down shift key. Doesn't work.
It seems to me if I can't even get the machine to boot from the Install disk that there is something going on that is much more major than software issues.
Bad motherboard? Any ideas? Because I'm all out of ideas.

Brother, Sound74, I thought I was the only one pulling the hair out of my chest one by one the past two days. Your situation is very similar to mine, and I'm just as clueless as you are. I started getting kernel panic screens, then nothing on boot, until finally I brought it to the local genius bar. They ran all the usual software/hardware tests, updated Tiger to 10.4.11, recommended I buy Leopard and do an erase-install. My computer, of course, was working absolutely fine by this point. I bought Leopard, came home, backed everything up, then tried to install the new OS. Like in your case, it just up and quit half-way through. Screen went black and a "No DVI Signal" message came on my display (it does this when I turn it on without first turning on the computer).
So I thought, well, maybe it takes a really long time to erase-install, and the monitor is just waiting for things to kick back in. I've always upgrade-installed before, so I couldn't tell if this was normal or not. But about half an hour later, my fans kicked in so fast I thought I had a P-51 Mustang taking off in my studio. I waited a bit more and finally force-shut-down my system. Not knowing what to expect, I nervously tried to re-boot.
Nothing. Zip. I can't safe boot, I can't boot from the installer disc, etc. The only thing I can do is the option-key thing whereby you choose the startup disc. And of course, it only gives the Leopard install disc as an option, because now the entire HD has been erased! But when I choose the Leopard disc, of course it doesn't work.
So I have a nice $3000 paperweight sitting in my studio. I guess I'll have to bring it back to the Mac store, where if it costs more than $300 to fix, I'm going to say screw it and put that dough toward a new iMac.
Sorry I couldn't provide any helpful info, but I just wanted you to know you're not alone in suffering the slings and arrows of outrageous technology.
Keep me posted on any solutions you discover, and I'll do the same.
Noochy1
PS My applecare expired a month ago! AAAAARRRRGGGHHHH!!! **** Murphy and his stupid laws.

2012 iMac 27" fails to boot AND wake from sleep

Hi all,
My 2012 iMac has recently started giving my trouble when booting and waking from sleep.
When booting - A normal power up results in the apple logo screen being stuck, then I have to hold down the power button for a few seconds until power off, then i power it back up and the computer boots up normally. NOTE: only at the second time does the computer succeed in getting past the apple logo screen to the sign in screen.
Waking from Sleep - When ever the mac goes to sleep he doesn’t seem to be able to wake up. Usually stuck on a black screen with just the spinning wheel shown. At times i waited more then an hour to see if he can get passed the black screen but in vain.
Other then that the mac works fine.
Both issues started roughly two weeks ago and roughly at the same time.
My mac is mostly used for work, I'm familiar with computers so I am trying to be extra careful with installing weird applications but you could never know..
SPEC:
Late 2012 iMac 27'' - 3.4 Ghz i7.
16GB RAM.
1TB Fusion drive.
2GB NVIDIA GTX 680MX
Wired keyboard and a Magic mouse.
Mountain Lion 10.8.5 (Updated and backed up on a regular basis)
Things I've tried:
Boot to Recovery and Repair Disk/Permissions.
Safe Boot.
SMC reset.
PRAM reset.
* The first two produced a single case of a normal start up, but after a shut down the problem remains.
Any ideas/thoughts/help would be much appriciated,
Thanks in advance,
Idan.

Bump.

[SOLVED] Unable to Boot Windows 7 from GRUB

I recently reinstalled Arch onto my laptop (Lenovo Thinkpad t520) and have been having problems with Grub. For the last week I've been having trouble getting it to run grub at boot at all, only being able to run windows 7 by flagging it as the bootable drive. The other day I finally got it to boot into grub, and from grub I can boot into Arch. However, I can not boot into windows 7 through grub. When I attempt to, it throws an error:
Invalid EFI file path
I'm somewhat new to arch, and especially new to efi bootloading and such. Right now the only way I can get into windows is either booting from the arch install disk > boot other os and specifying partition 2 (where I have windows installed) or by pressing f12 at boot. When I do this (not sure what the term is, if anyone knows please tell me), it brings up a menu asking where I want to boot with "arch_efi" "cd drive" "Hard drive" etc. I choose hard drive and it will then boot to windows by default. Booting normally takes me to grub where I can boot into arch but not windows. If there's any more info you need please let me know and I'll try to provide it. Thanks in advance.
Also, here is my current partition setup
/dev/sda1 /boot/efi
/dev/sda2 Windows7
/dev/sda3 Extended partition containing sda 5,6, & 7
/dev/sda4 swap
/dev/sda5 /boot
/dev/sda6 /
/dev/sda7 /home
UPDATE
Terminator seems to be right (still on a roll!), so I wiped the partition I had grub on, removed grub, and installed syslinux. Now I have another problem that I'm hoping can be solved in the same thread to avoid another. It boots to syslinux no problem, and I can boot to windows from there all good, but when I select arch I get:
Root device mounted successfully but /sbin/init does not exist
I haven't been able to look for solutions too much on my own, but any help would be appreciated, thank you.
Last edited by IamFuzzles (2012-08-22 04:20:56)

Terminator wrote:If I understand it correctly, what you are trying is impossible: you are trying to boot windows using UEFI on a disk with MBR partitioning. Windows 7 only supports UEFI on discs with GPT partitioning but AFAIK, extended partitions only exist in MBR partitioning.
i also saw this in the arch wiki, but i have a brand new lenovo ideapad y570 running windows 7 64-bit that i'm in the process of setting up for someone, and it has what i think is an efi system partition but the disk uses mbr partitioning. does anyone know why this might be, or is there a way i can verify that the system is actually being booted via bios-mbr?
Last edited by e_tank (2012-08-21 11:56:15)

Boot ISCSI LUN from LDOM

Similar Messages

Maybe you are looking for