Solaris 10 SAN Boot issue

During Solaris 10 Installation on a SAN Based disk, SUN Fire V10 was not rebooting after the first CD installation. It does memory dump...

I really don't like san boot for operating system. You have too many points of failure for the basic operation.
Anyway, during installation, ensure that you access the disk using just one path (using zoning for example). After you enable and configure MPxIO, you could enable other paths.

Similar Messages

Solaris 10 booting issue

Hello,
Just liveupgraded solaris 8 to the latest solaris 10 on V440/sparc. After luactivate, trying to boot into Solaris 10 but system is throwing below messages on console,
Configuring devices.
WARNING: /pci@1f,700000/scsi@2,1 (mpt1):
hard reset failed
WARNING: /pci@1f,700000/scsi@2,1 (mpt1):
mpt_restart_ioc failed
WARNING: /pci@1f,700000/scsi@2 (mpt0):
hard reset failed
WARNING: /pci@1f,700000/scsi@2 (mpt0):
mpt restart ioc failed
WARNING: /pci@1f,700000/scsi@2 (mpt0):
firmware image bad or mpt ARM disabled. Cannot attempt to recover via firmware download because driver's stored firmware is incompatible with this adapter.
WARNING: /pci@1f,700000/scsi@2 (mpt0):
mpt restart ioc failed
WARNING: /pci@1f,700000/scsi@2 (mpt0):
firmware image bad or mpt ARM disabled. Cannot attempt to recover via firmware download because driver's stored firmware is incompatible with this adapter.
WARNING: /pci@1f,700000/scsi@2 (mpt0):
mpt restart ioc failed
WARNING: /pci@1f,700000/scsi@2 (mpt0):
firmware image bad or mpt ARM disabled. Cannot attempt to recover via firmware download because driver's stored firmware is incompatible with this adapter.
WARNING: /pci@1f,700000/scsi@2 (mpt0):
mpt restart ioc failed
WARNING: /pci@1f,700000/scsi@2 (mpt0):
firmware image bad or mpt ARM disabled. Cannot attempt to recover via firmware download because driver's stored firmware is incompatible with this adapter.
And, it continues to do so. Any idea on how this can be fixed?

OK, as I was booting into Solaris 8, that also gave me mpt errors and suddenly realized of one change that I had done recently and I had not rebooted Solaris 8 after that change. The change was connecting A1000 device to scsi port on the host(not external scsi adapter). I removed the A1000 cable from scsi port and there you go solaris 8 came up.
Thought I 'd try booting Solaris 10 again and now the earlier errors don't come but I see following warnings,
Loading smf(5) service descriptions: 1/187
WARNING: svccfg import /var/svc/manifest/application/management/wbem.xml failed
2/187
WARNING: svccfg import /var/svc/manifest/system/metainit.xml failed
172/187
WARNING: svccfg import /var/svc/manifest/system/power.xml failed
173/187
WARNING: svccfg import /var/svc/manifest/system/postrun.xml failed
174/187
WARNING: svccfg import /var/svc/manifest/system/resource-mgmt.xml failed
175/187
WARNING: svccfg import /var/svc/manifest/system/zones.xml failed
176/187
WARNING: svccfg import /var/svc/manifest/system/poold.xml failed
177/187
WARNING: svccfg import /var/svc/manifest/system/pools.xml failed
178/187
WARNING: svccfg import /var/svc/manifest/system/picl.xml failed
179/187
WARNING: svccfg import /var/svc/manifest/system/installupdates.xml failed
180/187
WARNING: svccfg import /var/svc/manifest/system/labeld.xml failed
181/187
WARNING: svccfg import /var/svc/manifest/system/tsol-zones.xml failed
182/187
WARNING: svccfg import /var/svc/manifest/system/iscsi_target.xml failed
183/187
WARNING: svccfg import /var/svc/manifest/system/cvc.xml failed
184/187
WARNING: svccfg import /var/svc/manifest/system/rcap.xml failed
185/187
WARNING: svccfg import /var/svc/manifest/system/fpsd.xml failed
186/187
WARNING: svccfg import /var/svc/manifest/system/br.xml failed
187/187
WARNING: svccfg import /var/svc/manifest/system/sar.xml failed
svccfg import warnings. See /var/svc/log/system-manifest-import:default.log .
WARNING: svccfg apply /var/svc/profile/generic.xml failed
WARNING: svccfg apply /var/svc/profile/platform.xml failed
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run
Reading ZFS config: *
Root password for system maintenance (control-d to bypass):done.
Login incorrect
Root password for system maintenance (control-d to bypass):
I can connect A1000 to other machine or external card and deal with it later however how to get system out of this state?

UCS 1.4(3M) BIOS Issue ? no network/san boot when diskless

Recreated faithfully on multiple blades and chassis with VIC cards. Have many SAN boot nodes in production and testing and after upgrading firmware this week anytime I apply my store policy of "diskless" to a blade I lose the ability to boot from network. After much effort to work around comes down to no matter what I do with diskless storeage policy, the configured boot order will never become the actual boot order. In the BIOS all network boot options/reference are invisible, cannot enable nor add to options. Upon removing diskless storeage profile and applying "any other that I have" I see in FST that it's powering up internal storage, starting up and updating pre-boot environments, and other things related that connected the dots. Returning to BIOS all reference and options have returned as I expected due to actual boot order screen updating to match configured order and hba's of course login the fabric right away, boot is fine. While I can faithfully replice across many, many blades, they are all the models with same mezz running 1.4.3 so curious if anyone else is seeing, particuaraly now with new version out, as I have done last few weeks without issues leading me towards the firmware.
In a nut shell I see that when going diskless this is actually shutting down the storage/raid controller. i can see that clearly but no bios access to it and not sure what else is or why it's affecting network and hba also since I cannot see, it's shutting more down than low powering drive side raid. I use different profiles due to some blades having disks removed, some retain them. moving a san boot service-profile dynamically around multiple chassis will fail to associate with errors on some due to disk setup and all that. some i have disks pulled and diskless based on documentation and best practices as this customer needed several san boot only blades in that pool. But yes if I use a storage profile allowing "any disk config" for association whether it has disks, no disks, raided drives, replaces the diskless policy in same service profile it faithfully follows my boot order and boots via hba's across multiple blades, up to about 8 or 10 as of today.....b200-m2's with vic's
thx
dave

My UCS manager firmware and Adapter is 1.3.1p,
the boot policy has been set to Boot to SAN,
I checked "Hardware and Software Interoperability Matrix for UCS System Release 1.3.1"
It seems the 1.3.1 only can support the "windows 2008 r2 x64 w/Hyper-v",
so, I updated the UCS manager Bios and the adpter firmware to 2.0, but the I/O module still is 1.3.1p
I can install the "windows 2008 r2 x64" successfuly...
Now, my concern is I have a mix component software versions on my ucs blade(I used the UCS manager 1.3.1, IO module 1.3.1, the UCS Bois 2.0.1 and the adapter 2.0.1)
will the mix component software versions cause some other issues? Dose anyone can give me some suggestion?
Thanks a lot

San Boot Win2K8 R2 SP1 x64 on UCS blades B with M81KR installation issue

I am trying to install a storage San Boot Win2K8 R2 SP1 x64 on UCS blades,(There are only 1 path to the OS installation drive during the installation.)
I loaded drivers for the M81K2 following the "UCS Windows Install Guide" , and I can see the LUN I mapped from XIV. I was able to create and format partitions, make it online, but when
I try to install, windows gives the error:"Windows cannot be installed to this disk. The computer's hardware may not support booting to this disk. Ensure that the disk's controller is enabled in the computer's BIOS menu."
any one know this issue?
Thanks

My UCS manager firmware and Adapter is 1.3.1p,
the boot policy has been set to Boot to SAN,
I checked "Hardware and Software Interoperability Matrix for UCS System Release 1.3.1"
It seems the 1.3.1 only can support the "windows 2008 r2 x64 w/Hyper-v",
so, I updated the UCS manager Bios and the adpter firmware to 2.0, but the I/O module still is 1.3.1p
I can install the "windows 2008 r2 x64" successfuly...
Now, my concern is I have a mix component software versions on my ucs blade(I used the UCS manager 1.3.1, IO module 1.3.1, the UCS Bois 2.0.1 and the adapter 2.0.1)
will the mix component software versions cause some other issues? Dose anyone can give me some suggestion?
Thanks a lot

Solaris Patching/SAN Boot

I have just created an ABE on a SAN device, upgraded it and then booted from it.
Its been a long journey, and involved a SR with oracle.
I was new to it and am astonished at how hard it has been. Not hard in the sense that anything was over complicated, but the tangle mess of patch levels and gathering information on server firmware, SAN boot, HBA firmware, patches etc has been a nightmare. Not sure whether its me just new to patching solaris 10 etc, but I have literally trawled through a couple of dozen documents, countless web browsing and a few grey hairs just to achieve this.
I will hold my hand up, some of it was of our own making - I was patching a system that had not been touched in a number of years.
Anyone had a similar experience or does it get easier?!?!?

I really don't like san boot for operating system. You have too many points of failure for the basic operation.
Anyway, during installation, ensure that you access the disk using just one path (using zoning for example). After you enable and configure MPxIO, you could enable other paths.

Dual OS system booting issue - Solaris with Windows XP Pro

Hi,
I have installed Windows XP Professional with SP2 on my laptop Dell Inspiron 6400 (Intel Core 2 Duo). I created partition as below,
C: 25GB (Primary : Active) Installed XP
D: 15GB (Primary) - Tried to install Solaris here
F: 10GB (Primary)
G: 20 GB (Logical)
H: 20 GB (Logical)
1. I tried to install Solaris 10, booted up system from DVD and selected Solaris. I got a message related to "License..." and it stopped right there, nothing showed up on screen after the message. I forced it to shutdown.
2. Next, I tried with Solaris Express Developer edition DVD. I was able to proceed until "Install" option. After clicking "Install" button, it reported some account name(no account name found) setting problem and quitted from installation. It asked to remove the DVD manually. But I was not able to eject it, got stuck. I switched off it and removed DVD.
When I bootup the system next time from HDD or CD or USB bootable backup, it showed blank screen and blinking cursor. I am not able to boot system with Win XP or USB Win Xp bootable. I am able to enter BIOS setup.
Please let me know how to boot up Win Xp and install Solaris with it.

with my little experience i find solaris 10 isn't able to install on sata hdd but with solaris express edition 5.11 i was able to install it on my lap top toshiba tecra and now i can boot with xp sp2 and solaris i hope this answer your question .

XenServer 6.1 SAN boot on B200M2

I'm new to XenServer. We have UCS with B200M2's with the M81KR CNA in them. We primarily use VMware ESXi and we SAN boot all of those machines. We have had no issue SAN booting ESXi servers. I've created a new serivce profile template for the XenServer's and brought up a couple machines. I've allocated the storage and when I got to install XenServer it doesn't see the boot LUNs. I know the storage is allocated properly. I can see the LUNs when the blade is booting and I can install ESXi onto the boot LUNs without issue. The issue is with XenServer seeing the LUN. I did the F2 > mulitpath option that it says to do in the Appendix of the install guide for XenServer but that makes no difference. What needs to be done to have XenServer see a boot LUN on a B200M2?

6.0
Please see the UCS Support Matrix tool for further info:
http://www.cisco.com/web/techdoc/ucs/interoperability/matrix/matrix.html
Support is coming in the upcoming UCSM 2.1 release before the end of the year (tentatively). I'm just confirming if support will be included in a future 2.0.x patch or not.
Regards,
Robert

V100 booting issue

I am using Hyperterminal from a Windows laptop to connect to the v100 server that's not on the network, but everytime I establish a connection I get the OK prompt.
Once at the OK prompt, I issue the boot comand, and solaris 8 boots up correctly from the disk.
How else can I make it skip the OpenBoot phase, so that I don't have to issue the boot comand everytime?
To rule out any potential causes for this issue, I have done the following:
setenv auto-boot true
setenv boot-device disk
setenv diag-switch false
Thanks
Ameen

Thank you both for your reply.
I'm sorry about the typo, but I did issue the right command, including the '?'. So the auto-boot? was set to true.
I have tried 3 different TERM emulators (HyperTerminal, Tera Term, and finally secureCRT, which is by the way a much better tool), and everytime I connect using COM1, I get the OK prompt. One work around I found is to type GO, which gets me right away to the Login prompt.
I think that will have to do for now, until I put this box on the LAN, and then I could telnet to it.
Thanks again for your input
Ameen

M5K SAN Boot Question.

If i have a 3rd domain on a m5k. and it is supposed to boot from SAN. how can I go about doing it?
If thats the case like if my storage got 2 controllers and each has a fc path to the domain 3,
wun there be 2 luns seem on system side?
how would I be able to do the stmsboot? Even if i do a stmsboot after OS, won't the system be unable to boot after?.
or do I map 2 individual luns to server, then raid @ server side? or do we only do mapping on switch side?
Thank you all for your kind attention.

Hi Tejas,
We are going to need some further details to help narrow down the problem.
1) Was this Boot from SAN working previously for the ESX blade, you then upgraded to 2.0(1s) and are now having the issue?
or
Is this a new Boot from SAN setup on 2.0(1s)?
2) You mentioned that you can see the WWPN of your blade in your Fiber Channel switch. Have you verified that the WWPN of the EMC VNX is also visible in your Fiber Channel switch?
3) Have you checked your zoning configuration on the Fiber Channel switch, ensuring that the WWPN of your blade is permitted to communicate with the EMC VNX storage array?
4) Have you also checked your LUN masking on the EMC storage array? Ensure that you have configured the storage group to allow the WWPN access to the LUN
5) Depending on if the array is active/active or active/passive, it is also important to verify which storage processor currently owns the LUN and ensure that the vHBA communication is hitting the appropriate storage processor
6) Generally most operating systems will boot from LUN ID 0. So you can compare the presented LUN ID in EMC to what you configured in your UCSM Boot policy
7) Also ensure that you have correctly configured the order of your Boot from SAN targets (primary vHBA - primary target, secondary vHBA - primary target, etc...)
Other tips available via the following:
Troubleshooting SAN Boot and SAN Connectivity Issues
Hope that helps. Let me know how you go.
Cheers,
Michael

SAN Boot Policy Clarification

I would like some clarification regarding the SAN Boot policy. I was always under the impression you were suppose to use the WWPN of the storage port. But what if you have many storage ports coming from the array (16 for example), this would not be possible.
Is the purpose of this policy to simply force the HBA to login into the SAN fabric?
If so, I can use one from my actual array or just make one up, correct?
Since all the zoning is being done by the SAN switch (Brocade/MDS/Nexus) and LUN masking at the array level, I would think putting the actual WWPN of a storage port is not necessary.
Thanks for any clarification.

My thought was you could just throw a valid wwpn in (any valid wwpn, doesn't have to be the array) again just to log in to the fabric. The it would scan the bus and off you go.
When I tried that with our try and buy setup and a NetApp array, doing windows 2008 r2 san boot, I could never get the luns to show up. We put in the arrays 4 wwpns and that got it to show up.
im not sure why it matters, and I think we had something else wrong. if you look at blogs online almost all of them show to just throw a wwpn in there to start flogi and that's it.
If you have 16 wwpns that could be an issue. As you probably know the boot policy only lets you put a primary and secondary for each HBA. I would try placing a random wwpn in and see if it works.

UCS Central - Making Boot Policy - SAN boot target Provisioning

Gents
Some objects is always related to the domains and need to be provisioned in global like
VLANs: but we can did it by Provisioning VLANs with UCS Central Using VLAN ID Aliasing.
VSANs: the same idea in VLAN ID Aliasing.
Boot Policy adding SAN boot target : what about this issue how can I provision it so I can configure it globally in abstract way then it will take targets depend on domain during associating the global service profile.

@Gmonroy
Thanks for support
But if I need to make a global Service profile temp so I can deploy SF from it in any domain, and if I referenced this service profile temp to one boot policy so i need to unbind each service profile created from this temp to associate a different boot policy in each domain ? " I will lose the benefit of updating service profile template "
Or I have to create different template per domain ? " I will lose the key benefit of centralizing Templates in UCS central"
Or there is any workaround to deply this senario.

SAN boot B440 blade

I've been booting my B200-M1 (and M2) blades from the SAN with no issues, but when I try it with the B440, it just hangs. I know it sees the LUN because when I boot from the install ISO I can select the lun as the install location. I'm also using the same boot policy as my B200 blades, so the targets are correct. The firmware on the system is 1.3.1n.
Anyone else having a problem SAN booting a B440?

Update and resolution:
Update: there was no problem with CentOS 5.5 or VMware 4.x - I just hadn't checked those when I posted this message.
Update: there is a problem with CentOS (or RHEL) < 5.5 - see fix below
Solution: during the install boot, use the following: 'boot: linux mpath'
The problem was that I wasn't using 'boot: linux mpath' during the install boot of CentOS. By not using mpath, something was messed up with the subsequent SAN boot.
Note: even with the Cisco drivers, this wasn't resolved until I used mpath
Note: despite the fact that Cisco doesn't have a driver for RHEL 5.3, it still works if you use mpath during install
Cheers!

The Mac HD has booting issues - how do I make a clone that is free of these?

I spilled water on my MacBook Air (10.6.8) and now it has booting issues.
When I shut it down, the power button doesn't work to boot it. But when I close the lid, it powers up. However even when I shut it down AND close the lid, it keeps booting up and staying on.
So I have to send it for repairs.
I cloned the Mac HD using Carbon Copy Cloner and put the clone using Migration Assistant onto the new machine (MacBook Pro - 10.7.2). Now the MacBook Pro won't boot at all. Before this, it was working fine.
So I want to know how to make a clone of the Mac HD of the MacBook Air that won't have booting issues when I migrate the clone to another machine.
I have to make a clone of the MacBook Air before I send it off for repairs as the last back up is quite old and out of date.
Also the fact that the Mac HD of the MBA has booting issues affects the ability to access the Boot Camp (Windows 7 partition) as now I can't even boot the new machine. (But I am asking about Boot Camp in another section.)
It seems like a catch-22 situation. I can't fix the booting problem until I send it off to the repair center to get the computer fixed. And yet the booting problem is preventing me from making a usable clone of the Mac HD.
I think the booting problem is a software problem because the MacBook Pro was working perfectly before I migrated the Mac HD of the MBA onto it, The MBP is only two days old. I migrated another Mac HD backup (one I made before the booting issues came up) onto the MBP on the first day I bought it and the MBP worked fine.
Do you think I will just have to clone things separately manually? I mean should I format an external hard drive, plug it in the USB port, and transfer the files I need to save? What files/folders should I save? Can I move folders or do I have to move files? I have many files in Desktop, Downloads, Documents. I also want to save my applications. I want to save the BookMarks of Opera, Firefox.
Will this take a long time? I have used about 200 GB of the MBA's hard drive.
Any advice? Thanks.
I don't use Time Machine and am not confident about using it. Will it be substantially different to CCC in the way it clones files? Will a Time Machine clone after migration contaminate the second computer with booting issues?
I am not so worried about the booting issues on the second computer. I know it's from the faulty clone and nothing to do with the machine itself. I can take it to Apple Genius Bar and they will probably be able to reinstall a new operating system on the machine and I can start from scratch, I think. I am more worried about how to save and restore my data from the old machine. Thanks for any advice.

applecore_eater wrote:
I cloned the Mac HD using Carbon Copy Cloner and put the clone using Migration Assistant onto the new machine (MacBook Pro - 10.7.2). Now the MacBook Pro won't boot at all. Before this, it was working fine.
Ok, you used Migraine Assistant to try to transfer the account from the clone drive to the MBP and it didn't work, that's ok, it can be fixed by command r booting into Lion Recovery and simply erasing and reinstalling Lion from Apple's servers. (AppleID)
I suggest you transfer the account data manually because the clone is a copy of a failing drive/corruption, use the same name in System Preferences >Accounts, drag and drop files transfer and hold option key, click on Purchases in crapStore to redownload to the new machine, install other programs from fresh sources. Cleaner machine that way. So that shoudl fix the MBP.
in the future, try to avoid Apple's "answers" like Migraine Assistant as much as possible, it's really not reliable in any sense in actuality.
So I want to know how to make a clone of the Mac HD of the MacBook Air that won't have booting issues when I migrate the clone to another machine.
You can't boot a clone of OS X from another type Mac on another type Mac, only the same exact machine model.
In your case the Migraine Assistant didn't work, so you'll have to manually install.
Also the fact that the Mac HD of the MBA has booting issues affects the ability to access the Boot Camp (Windows 7 partition) as now I can't even boot the new machine. (But I am asking about Boot Camp in another section.)
Well it's possible that Windows or something messed up the GUID partition map of the Mac, why it has booting issues. Likely why Migraine Assistant didn't work.
You'll have to set up BootCamp again on the new MBP machine, talk to Microsoft about validation on the new machine and return your Windows files, programs from fresh sources.
Likely you got malware and it was trying to write to the boot sector of the Mac, mistaking the MBR portion of the GPT for a full Windows one. This also happens when Mac users try to install Linux on their Mac's.
Unless you need full hardware performance, you really should look at virtualization software like VMFusion, Parallels Desktop or even VirtuaBox (might be outdated) and run Windows in a window on OS X instead. Much easier to recover from malware that way.
It seems like a catch-22 situation. I can't fix the booting problem until I send it off to the repair center to get the computer fixed. And yet the booting problem is preventing me from making a usable clone of the Mac HD.
Well if you make a clone, it's going to be junk any.
What you need to do is fix the new MBP machine first then use Firewire Target Disk Mode (firewire 800/400 cable and adpater if needed) and grab a copy of your files off the sick Mac or off the sick clone.
The drive is likely fine, it's just not booting and that could mean some sort of malware/drive/data corruption.
You'll have to install third party software on the new fixed MacBook Pro to read the NTFS drive format of the Windows 7 bootcamp parittion when the sick MacAir is in Firewire Target Disk Mode.
http://www.paragon-software.com/home/ntfs-mac/
https://support.apple.com/kb/HT1661

Boot issues

When I boot my computer (MacBook Pro, 15", Early 2010, 4GB RAM, 320GB HD, 2.4GHz Intel Core i5), it does nothing for quite awhile, and eventually gives me the folder with the question mark on it, signifying it can't find a startup volume. I think I know why, but this has not helped me fix the problem.
I used Disk Utility to partition the internal hard drive so I could install Linux (Ubuntu 10.10) and dual-boot. I used Linux to reformat the partition and used one of the 134MB spaces between partitions (the one at the end of the drive) as Swap space for Linux. I installed Ubuntu, and it worked fine. I could use the built in boot manager (holing down the option key at startup) to boot into either operating system.
That was last night. This afternoon, I booted up the computer, and it gave me the flashing question mark folder and wouldn't boot. I connected it to my iMac (20", Early 2009, 2GB RAM, 320GB HD, 2.66 GHz Intel Core 2 Duo) via a FireWire 800 cable and started the laptop up in Target Disk Mode. I started my iMac up holding down the option key to get it to look for the (possibly) bootable hard drive of the laptop. It did not find it, but displayed only the boot volumes normally available to it (Mac OS X 10.6.7, Windows 7 Ultimate, Mac OS X 10.5.8). I then shut down the laptop and proceeded to start it back up. Miraculously, it booted of its own accord into Mac OS X (10.6.7). I later booted the machine into Linux and began dinking around with some settings to get the illuminated keyboard to work. I did not entirely succeed, but the laptop was still working fine. I shut the clamshell to put it to sleep (while in Linux), and about an hour later, upon opening the clamshell, all I got was a black screen and the mouse pointer (as if it was stuck trying to get me to enter a password to unlock the screen). On rare occasions, this happens to me under Mac OS X as well, and I have usually been able to resolve it by shutting and opening the clamshell. After waiting a few minutes, I tried this, and when it failed, I decided to force shut down the machine, as I have had to do sometimes when this has happened under Mac OS X. Upon restarting the computer, I got the flashing question mark once again. I tried holding down the option key on startup, but only got a mouse pointer against a blank grey screen (like the boot loader screen, but without any icons). I tried zapping the PRAM, starting up in Safe Mode, starting in Verbose mode, holding down the x key, then Command-Option-O-F (then realized that wouldn't work since Apple doesn't use Open Firmware anymore), and also tried Command-Option-V-R, but that also appeared to do nothing. I just got the question mark folder each time (except for resetting the PRAM: that worked, but then I got the question mark folder).
I repeated the same steps as before (Target Disk Mode, etc) to see if they would miraculously fix the problem a second time (I still don't know how they did the first time), but to no avail. I fully booted my iMac with the laptop connected as a FireWire disk to attempt to use Disk Utility on it. Disk Utility did not recognize the drive. I checked System Profiler. It recognized that there was a Target Disk device attached to my iMac, but it did not list any hard drives under it. I proceeded to boot my laptop from its install DVD, which worked. However, Disk Utility on the pseudo-OS that is on the install DVD failed to recognize the internal hard drive. I checked under the Serial-ATA section of System Profiler. It showed two connections, one for the DVD drive, and I presume the other for the hard drive, but the hard drive one showed nothing connected to it. It simply listed a few specs on the SATA port.
I decided to boot my laptop from my iMac's internal drive. I reversed the roles of the machines, my iMac now being in Target Disk Mode, and the laptop trying to boot from its hard drive. I held down the option key at startup so I could choose what to boot from. I choose Mac OS X 10.6.7, and the machine started to boot. Just before it should have gotten to the brief blue screen before the login screen, it had a kernel panic, and the grey came down the screen and told me to restart the computer. I did, tried again, got the same kernel panic, so I decided to try Windows 7. When I selected Windows from the boot manager, it seemed to try to start up in Mac OS X (10.6.7, because 10.5.8 wasn't connected), but never got past the grey Apple icon. After a while, it started occasionally flashing a circle with a line through it, and sometimes the question mark folder, but always switched back to the Apple icon quickly. After at least 10 minutes, I decided to shut down the computer. I then tried booting Mac OS X 10.6.7 in Safe Mode. After showing the progress bar (it only got about half completed before it vanished, but it took a long time to get halfway) for awhile, it eventually successfully booted to the login screen. I signed in, and opened Disk Utility. Nothing. I checked System Profiler and got the same result I had from the install DVD. I shut down the computer, and tried to boot it normally one last time. Nothing.
Does anyone have a clue what's going on? I can understand why the computer would be having boot issues, with my shaky installation of Linux, and all, but I can't understand why nothing will recognize that the computer's internal hard drive exists.
I do have AppleCare for the laptop, unless I've voided the warranty by installing Linux. Should I send the computer in? (I'm over 250 miles from the nearest Apple Store). Is there anything I could do by opening up the computer (I know that would void the warranty if I haven't already). I do have a backup of most of the data, but the backup excludes some video files because of their size. Luckily, I do still have them on MiniDV tape if I have to reimport them.
I feel like I've tried everything, but I wouldn't be surprised if I've missed something obvious…
Thanks in advance for any ideas, suggestions or answers!

Update 2: That successful boot seems to have been one of about four flukes. For some strange reason, my computer will successfully boot into Mac OS X and Ubuntu, but only on rare occasions. There seems to be no pattern, but every once in a while, the computer will decide to recognize it has a hard drive.
Any thoughts?

Booting issue on a new installation on Acer Aspire 4752 laptop.

Hi All,
     I have done a new installation of OS on a Acer laptop stated above. However, due to some reason, during the booting up process, it will always stuck at screen right before it enter into the logon screen. I will have to press
Enter in order to move it, as if there is a "press Enter to continue...".
     After this "enter" key, everything else works normally. However, this is pretty annoying and I could not sent this laptop back to my enduser because of this trivial issue.
     Some other information as below:
This is a new OS and no other apps is installed. Though now it is patched (with Microsoft patches). But it happens since the first boot after install.
In according to Device Manager, all drivers are in place. No exclamation mark and error.
Event Viewer shows no error for the boot up.
Safemode (command prompt) shows that it is stuck at loading "classpnp.sys".
     My questions:
It will be good if there is already a resolution. :)
How to diagnose, or identify which apps actually waiting for that "enter" to move on?
     Thanks!
wsn

Hi,
For the boot issue, first I suggest you use startup repair if you have an installation disk, check if it can detect and fix some certain problems.
Or run sfc/scannow in command prompt in recovery console, check if it can make any difference.
If doesn’t work, then try “Enable boot logging”, then check the log called ntbtlog.txt, usually located in system drive\Windows.
Advanced startup options (including safe mode)
http://windows.microsoft.com/en-in/windows/advanced-startup-options-including-safe-mode#1TC=windows-7
You can also share a screen image with us about the “stuck” screen.
Regards
Yolanda
TechNet Community Support

Solaris 10 SAN Boot issue

Similar Messages

Maybe you are looking for