Zfs boot issues

Hi,
I've got next issues: when I try to boot my server I'm getting following message:
Executing last command: boot disk11
Boot device: /pci@8f,2000/scsi@1/disk@1,0 File and args:
SunOS Release 5.10 Version Generic_147440-26 64-bit
Copyright (c) 1983, 2012, Oracle and/or its affiliates. All rights reserved.
NOTICE: Can not read the pool label from '/pci@8f,2000/scsi@1/disk@1,0:a'
NOTICE: spa_import_rootpool: error 5
Cannot mount root on /pci@8f,2000/scsi@1/disk@1,0:a fstype zfs
panic[cpu0]/thread=1810000: vfs_mountroot: cannot mount root
000000000180d950 genunix:vfs_mountroot+370 (1898400, 18c2000, 0, 1295400, 1299000, 1)
%l0-3: 00000300038a6008 000000000188f9e8 000000000113a400 00000000018f8c00
%l4-7: 0000000000000600 0000000000000200 0000000000000800 0000000000000200
000000000180da10 genunix:main+120 (189c400, 18eb000, 184ee40, 0, 1, 18f5800)
%l0-3: 0000000000000001 0000000070002000 0000000070002000 0000000000000000
%l4-7: 0000000000000000 000000000181d400 000000000181d6a8 0000000001297c00
skipping system dump - no dump device configured
rebooting...
Resetting ...
I'm able to boot server in failsafe mode and successfuly import zfs-pool. The pool is fine.
Here is zfs pool configuration:
# zpool status
pool: zfsroot
state: ONLINE
scan: scrub repaired 0 in 0h35m with 0 errors on Thu Jan 30 13:10:36 2014
config:
        NAME          STATE     READ WRITE CKSUM
        zfsroot       ONLINE       0     0     0
          mirror-0    ONLINE       0     0     0
            c2t0d0s2 ONLINE       0     0     0
            c2t1d0s2 ONLINE       0     0     0
errors: No known data errors
Could somebody help?
Thanks in advance.
PS:
SunOS Release 5.10 Version Generic_147440-01 64-bit
Server: Fujitsu PRIMEPOWER850 2-slot 12x SPARC64 V
OBP: 3.21.9-1

Here are
format output
AVAILABLE DISK SELECTIONS:
       0. c0t1d0 <FUJITSU-MAP3735NC-3701 cyl 24345 alt 2 hd 8 sec 737>
          /pci@87,2000/scsi@1/sd@1,0
       1. c2t0d0 <COMPAQ-BD14689BB9-HPB1 cyl 65533 alt 2 hd 5 sec 875>
          /pci@8f,2000/scsi@1/sd@0,0
       2. c2t1d0 <COMPAQ-BD14689BB9-HPB1 cyl 65533 alt 2 hd 5 sec 875>
          /pci@8f,2000/scsi@1/sd@1,0
show-disks in OBP:
{0} ok show-disks
a) /pci@8d,4000/scsi@3,1/disk
b) /pci@8d,4000/scsi@3/disk
c) /pci@8f,2000/scsi@1,1/disk
d) /pci@8f,2000/scsi@1/disk
e) /pci@85,4000/scsi@3,1/disk
f) /pci@85,4000/scsi@3/disk
g) /pci@87,2000/scsi@1,1/disk
h) /pci@87,2000/scsi@1/disk
q) NO SELECTION
Enter Selection, q to quit:
boot-device value is "disk1:c" but I switch off autoboot (for debug purposes) and boot server manualy with command "boot disk11..."
Here is devalias output:
{0} ok devalias
tape                     /pci@87,2000/scsi@1,1/tape@5,0
cdrom                    /pci@87,2000/scsi@1,1/disk@4,0:f
disk11                   /pci@8f,2000/scsi@1/disk@1,0
disk10                   /pci@8f,2000/scsi@1/disk@0,0
disk1                    /pci@87,2000/scsi@1/disk@1,0
disk0                    /pci@87,2000/scsi@1/disk@0,0
disk                     /pci@87,2000/scsi@1/disk@0,0
scsi                     /pci@87,2000/scsi@1
obp-net                  /pci@87,4000/network@1,1
net                      /pci@87,4000/network@1,1
ttyb                     /pci@87,4000/ebus@1/FJSV,se@14,400000:b
ttya                     /pci@87,4000/ebus@1/FJSV,se@14,400000:a
scf                      /pci@87,4000/ebus@1/FJSV,scfc@14,200000

Similar Messages

ZFS boot partition?

Hi All,
I'm currently being asked to look creating a number of servers with mirroring. Ideally the whole server will use ZFS which would mean it would also need to boot from ZFS.
Looking at the OpenSolaris website:
http://www.opensolaris.org/os/community/zfs/boot/zfsboot-manual/
It looks like it's possible to do this. My problem is that I need to use vanilla Solaris on SPARC, and some bits and pieces from those instructions don't work.
Is this even possible? If it's not, what's the best I can hope for?
I'm currently testing on x86 (in VMWare), I'll be deploying on SPARC.
Thanks for any help.....

Darren_Dunham wrote:
Boot procedures on x86 and SPARC are still quite different. So your testing on one doesn't necessarily help on the other. You'll note that the link you show is only for x86.
A new boot method for SPARC is being developed that will work with ZFS, but it hasn't been released the way the x86 side has. So you can't boot from ZFS on SPARC just yet.
DarrenI've also had issues with ZFS root in the X86 world. I won't go into the details as I'm not 100% certain whether it was the Nevada Build I was using (76) or if it was user error.
The current roadmap has ZFS boot for mainline Solaris as coming in either U5 or U6 according to a briefing we had recently. That puts it out anywhere from mid to very late 2008.
Dev Express will likely have it sooner, but we're back to "Is this production"? If it is, I would wait for it to be solid and stable and in main-line Solaris.
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

Windows 8 Laptop Boot Issue (and other related problems)

My Toshiba Satellite S855D-S5148 laptop was bought about a month ago, but it's been giving me issues for the last week.
The most significant one was a boot issue, where out of nowhere, the PC would not start, and after a hard restart, I received an error message saying Windows was not able to start. So I called tech support and they guided me through a PC refresh. That seemed to have solved the issue until twenty minutes later, when my system froze and I could not move the cursor let alone use any applications. So I did a hard restart again, and tried to do another PC refresh until the laptop 'clicked' and shut off. I restarted again, and my system seemed to be working normally until two days later (I did not shut it off or restarted it during this period, only kept it in hibernate when not in use).
Upon trying to use my laptop, it said Windows was reconfiguring. Afterwards, I received an error message saying that Windows had to restart due to 'this problem,' though the problem was not specified. The error message included a list of file addresses that presumably contained a description of the problem, but I can't access the files because they don't show up when I search their addresses. They are .dmp and .xml files, respectively.
Is anyone familiar with this problem? I wish I could return the laptop but it's a couple of weeks shy of the return period (Staples has a measely 14-day return period, but I didn't think I'd have to use it). I don't want to go through the hassle of shipping it off to Toshiba for repairs. Would reformatting the laptop solve the problem? I wish I could attach the .dmp and .xml files to this post but I can't locate them. I'd try using the recovery disks, but they were recently destroyed in a flood.
Any comments, advice, and/or suggestions are very much welcome!

Happy to learn the hardware is fixed.
I was told they could not do so without the product key. ... Any ideas as to how I can get my product key?
Everybody should know by now that there is no product key for preinstalled Windows. The OEM has it locked into the motherboard.
As I've said over and over, recovery media will restore the hard disk to its original out-of-the-box contents. Windows will be activated.
Windows is not installed during this process. Everything on the hard drive is restored. It's an important distinction.
-Jerry

Safe boot issues tried everything

Howdy From NZ
I have a MBP with a bad case of safe Boot Issues
Things I have tried:
Disk Repair
Checked S.M.A.R.T status of HDD under linux and run a full surface scan to check HDD is fine
Replaced SATA Cable
Reloaded OSX (upto yosimite)
tried another hdd just in case
replaced top panel (thought maybe it was holding down the shift button)
and a few others I cannot remember at the moment
i'm Thinkin' it's motherboard related but would like a second opinion from the forum guru's
Also I've taken it to the closest apple authorised repair store, and they said it was the HDD, but clearly it isnt as I have replaced it with a brand new one and the sata cable
interestingly enough, If i 6 second death it, upon reboot it works fine, but if i restart normally it hits this problem, I'm thinking maybe its doing some sort of start up check thats causing it?, it seems to work fine if you boot with verbose mode every time without fail, so is verbose mode disabling something upon startup?
I run a repair store here, but im not apple authorized, but as stated before, have gotten further than the people that are.... any help will be greatly appreciated

Good Timing,
I was heading to Christchurch (the only town in the south island with an "apple genius store")
they told me it was the HDD again, even after telling them I have put a new HDD in and also changed the Sata cable!!!
Clearly this isn't going anywhere fast, and although I appreciate the help you have given me, I'm going to nut this one out by myself.
***update***
I borrowed a mates mac that was the exact same model and swapped the Motherboards over, worked straight from the get-go
Thank for the help, it was appreciated in making me think I'm not crazy.
Scott

Mac Pro Boot Issue

Mac Pro - "Quad", 2 X 2.66Ghz; 5GB RAM; OS X 10.5.6
Mac Pro will not boot. It powers up to the grey Apple logo screen. The progress circle spins for about 3 seconds, then powers itself off.
This past week I came back from two weeks off. The first morning back I noticed my Mac was sluggish at times and freezing for a few seconds here and there. When Time Machine backups would kick in, the whole system would be unresponsive for minutes at a time. After turning off all other equipment in my office, I could detect a tell-tale "click click, spin" type noise coming from one of my two internal drives (one for OS and a second for backups).
I tracked the noise to the boot drive and guessing it was about to go out, I ordered a replacement Samsung Spinpoint 750GB. Good thing, because the next day when I came in to work my machine was having worse problems. IF it would boot, it would hang after a few minutes of use. If it would not boot, it would power up to the grey Apple logo, the progress circle would spin a few seconds, the power itself off.
I waited another day and the new drive arrived. I pulled the old OS drive, installed the new one, then dumped our standardized clone image on the drive (using CCC). After the clone was complete, I booted up on the drive, tested it out for a couple of hours and verified that it was working as expected. Next I copied data over to my drive from my backup drive. Everything looked fine.
Three days later, I come in to find my Mac will no longer boot. Grey Apple logo, spinning, etc.. I power off and boot from my external diagnostic drive (OS X 10.5.5). It will not boot. I remove both internal drives and try another boot from the external diagnostic drive. It boots up fine. Shutdown. Remove the backup drive (drive bay 2) and try to reboot from the diag drive once again. It will not boot. Remove the OS drive (drive bay 1) and it boots to the diagnostic drive fine (note: no internal drives are installed at this point). Shutdown. Install the OS drive into drive bay 2 and it then boots to the diagnostic drive just fine.
So now I have booted to my external diag drive and can see that the OS drive is showing on the Desktop; however a pop-up error stating there is a problem has appeared. I try to verify the OS drive using Disk Utility and it stops about 2 seconds into the process with a "Filesystem verify or repair failed" error. The OS drive will then not mount.
I restart booting back to the external diag drive. The OS drive shows up on the Desktop with the same pop-up error message as before.
I run Tech Tool Pro from the diag drive and it comes back with a File Structure error of "Type List Offset Is Invalid" and "No method for Tech Tool Pro to repair a corrupt file". I have a surface scan and drive hardware test running now, but on a 750GB it will be a WHILE.
So here is my predicament... I can understand my original OS drive having problems. It was at least 3 yrs old and has been run quite hard. But what are the odds that I would replace it with a brand new drive running a verified to be good cloned disk image AND have almost the exact same boot issues on the new drive that I had on the old one?
I have taken my original OS drive and hooked it up to external cases and sata-to-usb adapters to make sure that it was actually dead and it is. It will not spin up properly and makes lots of clicking noises. However, having a similar boot issue with a brand new drive has me worried something may be wrong with the Mac Pro hardware also. The new OS drive ran fine for a few days and only had these problems today.
Any guesses?

Here is my own "cookie cutter" template to this type of problem.
Insure your UPS is working properly and that you have 1300VA to start with.
Run Apple Hardware Test of course.
CCC has been updated so make sure latest (it auto checks probably already).
Do you have Windows? run diagnostics from there, much better.
I settled on WD drives and use WD Diagnostic and has saved a drive.
Avoid Barracudas, seems even their 1TB is also suffering early failures (the 1.5TB was suffering from firmware problem).
Check for reviews and drive upgrade DB on AccelerateYourMac.
http://www.xlr8yourmac.com/
I know the F1 got a lot of early praise but they aren't compatible with Apple Pro RAID card and may have other issues.
If you want a fast low-cost drive, WD Cavair 640GB $69.
http://www.barefeats.com/harper14.html
Hitachi E7K1000: http://techreport.com/articles.x/16130/10
http://www.tomshardware.com/reviews/hdd-terabyte-1tb,2077-8.html
I have seen more than a couple of similar stories from people going away for 1-2 weeks and coming home to system that won't work properly. Hopefully people shutdown and unplug, or shutdown and have UPS, but it is strange to say the least.
Resetting SMC is a good idea but best done with 2008 model by leaving it unplugged for a full night 8-12 hrs. and not just 5 minutes. contrary to Apple tech article. For yours, there is a small physical button accessed by pulling drive tray #4 (easier to see if it is on its side and you have flashlight!)
http://support.apple.com/kb/HT1806
http://www.apple.com/support/macpro/

Satellite L50D - Boot issues after Hard Drive replacement

I have just upgraded my hard drive from the pathetic 5400 crod they supply to an SSHD@7200rpm but now have a major issue.
I initially imaged the os from the old hard drive back to the new drive and have had chronic boot issues (1 in 3-4 boot attempts succeed else it fails at any point (often at the Toshiba startup screen)).
I've reinstalled from a plain clean Win 8.1 ENT disc (trying to avoid the bloatware) and this has the exact same issue and was what I used to format the laptop fine with previously and worked previously.
I've tried reformatting and reinstalling (deleting ALL partitions each attempt) in CSM, UEFI non secure and UEFI secure. CSM is a straight never works no go and both UEFI methods have the exact same outcome.
I've tried with the original restore discs and it seems to work (haven't had time to fully test) but I don't want the bloatware and this should not matter since if I were a customer who forgot to make the restore discs (happens too often) and just had to have a failed or killed hard drive replaced the laptop would now be a door stop.
This seems as bad as Apple for locking people in :/.
So I'd appreciate ideas from people please, I'm not sure if there is a prep program that is supposed to be run over a new drive like PS3's etc (I doubt it) but this is driving me up the wall and will be the last time I consider Toshiba as anything other than a joke if there is no fix.
I've had to replace hard drives a few times in my previous Toshiba laptops and had none of this crod, it has something to do with the UEFI which seems more of a nuisance than assistance at the moment.
TIA.

Hi
In my opinion you should check firstly if this booting issue is related to the new installed HDD or new installed system.
You said that the notebook fails to boot often at the Toshiba splash screen.
The splash screen appears while POST (power on self test) procedure. During this test, the hardware will be checked.
Im wondering if the hybrid SSD/HDD isnt recognized by BIOS during this particular step.
From my point of few this might be the reason why the system cannot be booted up.
Another important note:
The Win 8.1 requires enable secure boot as well as the UEFI boot mode.
Therefore you should enable both options in BIOS.
Last but not least check if you are using latest BIOS version as well as latest firmware for hybrid SSD/HDD

Anyone see an ios 7.1.2 boot issue AFTER updating?

From everything I read, I wonder if iOS 7.1.2 has a general boot issue. I have 4 devices, one of which locked on update. When i reset it and checked the crash log, my reset counter was zero and it said there was a boot failure. There was no indication of any application crash for the time in question.
I never reboot any of my devices, so I don't know, but it crossed my mind that perhaps the lockups on boot or booting into recovery mode has nothing to do with the update process, but is related to rebooting 7.1.2 in general. In other words, just because the devices are working fine now, is there still a chance that any of them can lockup or go into recovery mode the next time they are reset?

There appears to be a plethora of similar reports out there (I've been looking around). So we wait for Apple to provide a fix for this problem.
What I am most unhappy about is the inability to downgrade to, at least, the last known working firmware; in this case, 7.1.1. In situations like this, newly introduced problems become a corporate liability, more so on the part of end users that experience limited use of these expensive devices due to these newly-introduced problems. Then, there is the added liability of support calls, feedback/bug reports, etc.
I do not see any logic in the decision to disable downgrading firmware -- in this case, it's seems more paranoia (ie: jailbreak prevention) than a solid engineering decision, in my opnion.

How to back up a ZFS boot disk ?

Hello all,
I have just installed Solaris 10 update 6 (10/08) on a Sparc machine (an Ultra 45 workstation) using ZFS for the boot disk.
Now I want to port a custom UFS boot disk backup script to ZFS.
Basically, this script copies the boot disk to a secondary disk and makes the secondary disk bootable.
With UFS, I had to play with the vfstab a bit to allow booting off the secondary disk, but this is not necessary with ZFS.
How can I perform such a backup of my ZFS boot disk ?
I tried the following (source disk: c1t0d0, target disk: c1t1d0):
# zfs list
NAME USED AVAIL REFER MOUNTPOINT
rpool 110G 118G 94K /rpool
rpool/ROOT 4.58G 118G 18K legacy
rpool/ROOT/root 4.58G 25.4G 4.50G /
rpool/ROOT/root/var 79.2M 4.92G 79.2M /var
rpool/dump 16.0G 118G 16.0G -
rpool/export 73.3G 63.7G 73.3G /export
rpool/homelocal 21.9M 20.0G 21.9M /homelocal
rpool/swap 16G 134G 16K -
# zfs snapshot -r rpool@today
# zpool create -f -R /mnt rbackup c1t1d0
# zfs send -R rpool@today | zfs receive -F -d rbackup               <- This one fails (see below)
# installboot /usr/platform/`uname -i`/lib/fs/zfs/bootblk /dev/rdsk/c1t1d0s0
The send/receive command fails after transfering the "/" filesystem (4.5 GB) with the following error message:
cannot mount '/mnt': directory is not empty
There may be some kind of unwanted recursion here (trying to back up the backup or something) but I cannot figure it out.
I tried a workaround: creating the mount point outside the snapshot:
zfs snapshot -r rpool@today
mkdir /var/tmp/mnt
zpool create -f -R /var/tmp/mnt rbackup c1t1d0
zfs send -R rpool@today | zfs receive -F -d rbackup
But it still fails, this time with mounting "/var/tmp/mnt".
So how does one back up the ZFS boot disk to a secondary disk in a live environment ?

OK, this post requires some clarification.
First, thanks to robert.cohen and rogerfujii for giving some elements.
The objective is to make a backup of the boot disk on another disk of the same machine. The backup must be bootable just like the original disk.
The reason for doing this instead of (or, even better, in addition to) mirroring the boot disk is to be able to quickly recover a stable operating system in case anything gets corrupted on the boot disk. Corruption includes hardware failures, but also any software corruption which could be caused by a virus, an attacker or an operator mistake (rm -rf ...).
After doing lots of experiments, I found two potential solutions to this need.
Solution 1 looks like what rogerfujii suggested, albeit with a few practical additions.
It consists in using ZFS mirroring and breaking up the mirror after resilvering:
     - Configure the backup disk as a mirror of the boot disk :
     zpool attach -f rpool <boot disk>s0 <backup disk>s0
     - Copy the boot block to the backup disk:
     installboot -F zfs /usr/platform/`uname -i`/lib/fs/zfs/bootblk /dev/rdsk/<backup disk>s0
     - Monitor the mirror resilvering:
     zpool status rpool
     - Wait until the "action" field disappears (this can be scripted).
     - Prevent any further resilvering:
     zpool offline rpool <backup disk>s0
     Note: this step is mandatory because detaching the disk without offlining it first results in a non bootable backup disk.
     - Detach the backup disk from the mirror:
     zpool detach rpool <backup disk>s0
     POST-OPERATIONS:
     After booting on the backup disk, assuming the main boot disk is unreachable:
     - Log in as super-user.
     - Detach the main boot disk from the mirror
     zpool detach rpool <boot disk>s0
This solution has many advantages, including simplicity and using no dirty tricks. However, it has two major drawbacks:
- When booting on the backup disk, if the main boot disk is online, it will be resilvered with the old data.
- There is no easy way to access the backup disk data without rebooting.
So if you accidentally lose one file on the boot disk, you cannot easily recover it from the backup.
This is because the pool name is the same on both disks, therefore effectively preventing any pool import.
Here is now solution 2, which I favor.
It is more complex and dependent on the disk layout and ZFS implementation changes, but overall offers more flexibility.
It may need some additions if there are other disks than the boot disk with ZFS pools (I have not tested that case yet).
***** HOW TO BACKUP A ZFS BOOT DISK TO ANOTHER DISK *****
1. Backup disk partitioning
- Clean up ZFS information from the backup disk:
The first and last megabyte of the backup disk, which hold ZFS information (plus other stuff) are erased:
dd if=/dev/zero seek=<backup disk #blocks minus 2048> count=2048 of=/dev/rdsk/<backup disk>s2
dd if=/dev/zero count=2048 of=/dev/rdsk/<backup disk>s2
- Label and partition the backup disk in SMI :
format -e <backup disk>
     label
     0          -> SMI label
     y
     (If more questions asked: press Enter 3 times.)
     partition
     (Create a single parition, number 0, filling the whole disk)
     label
     0
     y
     quit
     quit
2. Data copy
- Create the target ZFS pool:
zpool create -f -o failmode=continue -R /mnt -m legacy rbackup <backup disk>s0
Note: the chosen pool name is here "rbackup".
- Create a snapshot of the source pool :
zfs snapshot -r rpool@today
- Copy the data :
zfs send -R rpool@today | zfs receive -F -d rbackup
- Remove the snapshot, plus its copy on the backup disk :
zfs destroy -r rbackup@today
zfs destroy -r rpool@today
3. Backup pool reconfiguration
- Edit the following files:
/mnt/etc/vfstab
/mnt/etc/power.conf
/mnt/etc/dumpadm.conf
In these files, replace the source pool name "rpool" with the backup pool name "rbackup".
- Remove the ZFS mount list:
rm /mnt/etc/zfs/zpool.cache
4. Making the backup disk bootable
- Note the name of the current boot filesystem:
df -k /
E.g.:
# df -k /
Filesystem kbytes used avail capacity Mounted on
rpool/ROOT/root 31457280 4726390 26646966 16% /
- Configure the boot filesystem on the backup pool:
zpool set bootfs=rbackup/ROOT/root rbackup
Note: "rbackup/ROOT/root" is derived from the main boot filesystem name "rpool/ROOT/root".
- Copy the ZFS boot block to the backup disk:
installboot -F zfs /usr/platform/`uname -i`/lib/fs/zfs/bootblk /dev/rdsk/<backup disk>s0
5. Cleaning up
- Detach the target pool:
zpool export rbackup
I hope this howto will be useful to those like me who need to change all their habits while migrating to ZFS.
Regards.
HL

ZFS boot and other goodies

Hi everyone,
With the new funky OS-features in Solaris 10/08, does anyone know if such features are going to get support in the OSP/SUNWjet/N1SPS? ZFS boot would be nice, for a change :)
I haven't seen any updated versions of the OSP plugin for N1SPS for quite a while now, is it still under development?
Cheers,
Ino!~

Hi Ino,
as far as I know (and I might be mistaken) OSP is not under any active development and all bare metal OS provisioning activities are now domain of xVM Ops Center, which is built on top of Jet, which does support ZFS root/boot installation already.
If you want to get hacky, you can replace the SUNWjet package on your Jet server by hand (pkgrm/pkgadd), put there the fresh one and SPS/OSP should happily work with it (read: I have not tested it myself)...
If you want to get supported, then go the xVM OC 2.0 way...
HTH,
Martin

Zfs boot block size and ufs boot block size

Hi,
In Solaris UFS file system , boot block resides in 1 to 15 sectors, and each sector is 512 bytes total makes 7680 bytes
bash-3.2# pwd
/usr/platform/SUNW,SPARC-Enterprise-T5220/lib/fs/ufs
bash-3.2# ls -ltr
total 16
-r--r--r-- 1 root sys 7680 Sep 21 2008 bootblk
for zfs file system the boot block size is
bash-3.2# pwd
/usr/platform/SUNW,SPARC-Enterprise-T5220/lib/fs/zfs
bash-3.2# ls -ltr
total 32
-r--r--r-- 1 root sys 15872 Jan 11 2013 bootblk
when we install zfs bootblk on disk using the install boot command ,how many sectors it will use to write the bootblk?
Thanks,
SriKanth Muvva

Thanks for your reply.
my query is when zfs boot block size is 16K, and on disk 1 to 15 sectors(here boot block going to be installed) make around 8K,
it mean in the 16K,it writes only 8K on the disk
if you don't mid will you please explain me in depth
I m referring the doc for UFS, page no 108 ,kernel bootstrap and initialization (its old and its for Solaris 8)
http://books.google.co.in/books?id=r_cecYD4AKkC&printsec=frontcover&source=gbs_ge_summary_r&cad=0#v=onepage&q&f=false
please help me to find a doc for kernel bootstrap and initialization for Solaris 10 with zfs and boot archive
Thanks in advance .
Srikanth

ZFS boot device - UFS external storage - Solaris volume manger

Hi All,
If a system is running ZFS boot can one use Solaris Volume Manager on external UFS storage devices? If so, where do you store the metadb?

Should work, even though you need to have a slice somewhere where you can store the metadb's.
Perhaps you can store them on the external storage? Unless they are frequently removed.
.7/M.

Trouble shooting BOOT issue in SCCM 2012 but I cant find SMSPXE.log in the logfolder

Hi,
Is there an change in PXE troubleshooting PXE PE boot issue, in 2012?
I cant find wat I am used to...
/SaiTech

Hi,
One of our PXE point get some issue, I could not set my finger on it.
I could not find any log file and I expect an smspxe.log in D:\Program Files\SMS_CCM\Logs (Primary site server) so I think something is wrong. The PXE worked after I put .Net 4 on the server.
Is it a secret what you're missing? How should we help you if you don't tell the exact problem?
No secret but I am not sure by my self what state the DP server have.
/SaiTech

Zfs boot issues

Similar Messages

Maybe you are looking for