Playbook won't boot after upgrade to v2

I did my OTA upgrade this morning, and it downloaded and appeared to apply successfully. I hit the "restart" button and the playbook has been stuck at the shiny lights splash screen since.
I've even done a hard reset - still stuck. I can't get it to boot up. Upgrade FAIL.
Anyone know how I should begin troubleshooting this? This is my one and only Blackberry device (not encouraging).
If I haven't backed up in a few days (I know, I know...), can I redownload recently purcahsed apps? How can I even find them? Will they show in App World if they aren't installed?
Thanks in advance,
A

Mine took over 15 min to reboot.
Click here to Backup the data on your BlackBerry Device! It's important, and FREE!
Click "Accept as Solution" if your problem is solved. To give thanks, click thumbs up
Click to search the Knowledge Base at BTSC and click to Read The Fabulous Manuals
BESAdmin's, please make a signature with your BES environment info.
SIM Free BlackBerry Unlocking FAQ
Follow me on Twitter @knottyrope
Want to thank me? Buy my KnottyRope App here
BES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V

Similar Messages

Imac won't boot after upgrade to latest Yosemite

After Upgrading to latest Yosemite version - my Imac will not start - it just hangs there or eventually comes with Crash window tellling it will restart.
However the Imac does launch in safe mode - holding down the shift key -but then there is no sound - so that no good.
Can you solve this you will be the christmas hero in Danish land.
NB sofar I have tried
reset PRAM- reinstalled Yosemite - Verified Disk is ok.
iMac (27”, ultimo 2009) - 2,66 GHz Intel Core i5
Yosemite 10.10.1 (14B25)
Latest crash log
nonymous UUID: 273AE997-AFAA-D71B-8080-9D38EA80ADEB
Sat Dec 27 19:52:13 2014
*** Panic Report ***
panic(cpu 1 caller 0xffffff800d01e80a): Kernel trap at 0xffffff800d1338c3, type 13=general protection, registers:
CR0: 0x0000000080010033, CR2: 0x000000010689fb25, CR3: 0x0000000124a97000, CR4: 0x0000000000002660
RAX: 0xffffff801aaa5df8, RBX: 0x00bfbfbf00bfbfbf, RCX: 0x0000000009000000, RDX: 0xffffff800d6f42d0
RSP: 0xffffff80a69bb460, RBP: 0xffffff80a69bb4b0, RSI: 0xffffff80a69bb507, RDI: 0xffffff800d6f42d0
R8: 0xffffffffffffffe9, R9: 0x000000000000003a, R10: 0xffffff8077cf3008, R11: 0x0000000000000000
R12: 0xffffff80a69bb4f0, R13: 0x0000000000000017, R14: 0x0000000000000017, R15: 0x000000000000031b
RFL: 0x0000000000010206, RIP: 0xffffff800d1338c3, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x000000010689fb25, Error code: 0x0000000000000000, Fault CPU: 0x1
Backtrace (CPU 1), Frame : Return Address
0xffffff80a00bde10 : 0xffffff800cf3a811
0xffffff80a00bde90 : 0xffffff800d01e80a
0xffffff80a00be050 : 0xffffff800d03a443
0xffffff80a00be070 : 0xffffff800d1338c3
0xffffff80a69bb4b0 : 0xffffff800d331348
0xffffff80a69bb5a0 : 0xffffff800d331d55
0xffffff80a69bb740 : 0xffffff800d32aab9
0xffffff80a69bb7d0 : 0xffffff800d340ccf
0xffffff80a69bb9a0 : 0xffffff800d13f2f8
0xffffff80a69bba80 : 0xffffff800d13ea95
0xffffff80a69bbbb0 : 0xffffff800d152005
0xffffff80a69bbc00 : 0xffffff800d15fcc7
0xffffff80a69bbf20 : 0xffffff800d154f0a
0xffffff80a69bbf50 : 0xffffff800d44dcb2
0xffffff80a69bbfb0 : 0xffffff800d03ac46
BSD process name corresponding to current thread: WindowServer
Mac OS version:
14B25
Kernel version:
Darwin Kernel Version 14.0.0: Fri Sep 19 00:26:44 PDT 2014; root:xnu-2782.1.97~2/RELEASE_X86_64
Kernel UUID: 89E10306-BC78-3A3B-955C-7C4922577E61
Kernel slide: 0x000000000cc00000
Kernel text base: 0xffffff800ce00000
__HIB text base: 0xffffff800cd00000
System model name: iMac11,1 (Mac-F2268DAE)
System uptime in nanoseconds: 88678398319
last loaded kext at 88213280354: com.apple.driver.AudioAUUC 1.70 (addr 0xffffff7f8f484000, size 28672)
loaded kexts:
com.apple.driver.AudioAUUC 1.70
com.apple.driver.AppleHDAHardwareConfigDriver 267.0
com.apple.driver.AGPM 100.14.37
com.apple.driver.AppleTyMCEDriver 1.0.2d2

Hello snake-apps,
Welcome to Apple Support Communities.
The article below provides troubleshooting tips that’ll help resolve kernel panic issues, like the one that you’re seeing with your iMac after upgrading to OS X Yosemite.
OS X: When your computer spontaneously restarts or displays "Your computer restarted because of a problem." - Apple Support
Ciao,
-Jason

IMac won't boot after upgrade to Maverick

First off, I have a Time Machine backup, so I'm not in really deep hot water yet, but...
Upgraded to Maverick from Lion 10.7.5 and let it run for ever and a day until it rebooted itself. Upon reboot, I got the grey screen with the Apple logo, then the little spinny thing beneath the logo disappeared...and nothing else happened. The iMac gets stuck like that and won't do anything else. I have only the keyboard and mouse connected to it — no external drives, no hubs, nothing else USB or FireWire. I can reboot to the recovery disk (which it now says is the 10.9 version). I have verified permissions, repaired permissions, verified disk (no problems) but repaired disk anyway, tried reinstalling Mavericks (and let it run overnight but got the exact same result) and even booted in single-user mode to run fsck. Nothing so far has worked.
I'm stuck with a grey screen and the pretty Apple logo, but can't get to the login screen or do anything else with it. Suggestions?

I spoke to Apple support and they've given me some suggestions to try when I get home tonight:
Mac OS X: Gray screen appears during startup
OS X Mavericks: Reset your computer's PRAM
Intel-based Macs: Resetting the System Management Controller (SMC)
Mac OS X: What is Safe Boot, Safe Mode?
Resolve startup issues and perform disk maintenance with Disk Utility and fsck
Mac OS X: Starting up in Safe Mode
Startup key combinations for Intel-based Macs

Arch 8.0 won't boot after upgrade :((( please help

OK guys, I've been running Arch for almost a year - switched from Ubuntu. The problem is that after a large update (around 520MB) I did a couple of days ago I can't boot into my system.
After "INIT version 2.86 booting" everything fails...
here's my syslog:
"Jun 26 00:02:02 endora syslog-ng[4434]: SIGHUP received, reloading configuration;
Jun 26 00:12:03 endora syslog-ng[4434]: Log statistics; processed='center(queued)=2', processed='center(received)=1', processed='destination(console)=0', processed='destination(mail)=0', processed='destination(user)=0', processed='destination(uucp)=0', processed='destination(messages)=0', processed='destination(news)=0', processed='destination(iptables)=0', processed='destination(everything)=1', processed='destination(lpr)=0', processed='destination(cron)=0', processed='destination(syslog)=1', processed='destination(authlog)=0', processed='destination(errors)=0', processed='destination(kernel)=0', processed='destination(daemon)=0', processed='source(src)=1'
Jun 26 00:22:03 endora syslog-ng[4434]: Log statistics; processed='center(queued)=20', processed='center(received)=10', processed='destination(console)=0', processed='destination(mail)=0', processed='destination(user)=0', processed='destination(uucp)=0', processed='destination(messages)=8', processed='destination(news)=0', processed='destination(iptables)=0', processed='destination(everything)=10', processed='destination(lpr)=0', processed='destination(cron)=0', processed='destination(syslog)=2', processed='destination(authlog)=0', processed='destination(errors)=0', processed='destination(kernel)=0', processed='destination(daemon)=0', processed='source(src)=10'
Jun 26 00:32:03 endora syslog-ng[4434]: Log statistics; processed='center(queued)=22', processed='center(received)=11', processed='destination(console)=0', processed='destination(mail)=0', processed='destination(user)=0', processed='destination(uucp)=0', processed='destination(messages)=8', processed='destination(news)=0', processed='destination(iptables)=0', processed='destination(everything)=11', processed='destination(lpr)=0', processed='destination(cron)=0', processed='destination(syslog)=3', processed='destination(authlog)=0', processed='destination(errors)=0', processed='destination(kernel)=0', processed='destination(daemon)=0', processed='source(src)=11'
Jun 26 00:42:03 endora syslog-ng[4434]: Log statistics; processed='center(queued)=24', processed='center(received)=12', processed='destination(console)=0', processed='destination(mail)=0', processed='destination(user)=0', processed='destination(uucp)=0', processed='destination(messages)=8', processed='destination(news)=0', processed='destination(iptables)=0', processed='destination(everything)=12', processed='destination(lpr)=0', processed='destination(cron)=0', processed='destination(syslog)=4', processed='destination(authlog)=0', processed='destination(errors)=0', processed='destination(kernel)=0', processed='destination(daemon)=0', processed='source(src)=12'
Jun 26 00:49:42 endora syslog-ng[4434]: SIGTERM received, terminating;
Jun 26 00:49:42 endora syslog-ng[4434]: syslog-ng shutting down; version='2.0.0'"
I tried to use the old rc.conf with no luck - exactly the same error. Also checked my menu.lst.
I get some strange errors saying /etc/rc.d/functions command not found etc.
Also I get some errors with /etc/rc.multi. Here's rc.multi:
"#!/bin/bash
# /etc/rc.multi
. /etc/rc.conf
. /etc/rc.d/functions
load_vars PROGRESS DELTA NUMBER
splash_setup
# Load sysctl variables if sysctl.conf is present
[ -r /etc/sysctl.conf ] && /sbin/sysctl -q -p &>/dev/null
# Start daemons
for daemon in "${DAEMONS[@]}"; do
if [ "$daemon" = "${daemon#!}" ]; then
if [ "$daemon" = "${daemon#@}" ]; then
export DAEMONSTATE=NORM
/etc/rc.d/$daemon start
if [[ ${SPLASH_MODE_REQ} == "silent" ]] ; then
update_progress
fi
else
export DAEMONSTATE=BKGD
stat_bkgd "Starting ${daemon:1}"
(/etc/rc.d/${daemon:1} start) &>/dev/null &
if [[ ${SPLASH_MODE_REQ} == "silent" ]] ; then
update_progress
fi
fi
fi
done
if [ -x /etc/rc.local ]; then
/etc/rc.local
fi
/sbin/splash exit
# vim: set ts=2 noet:"
I can only access the command line through the single mode.
If I won't get any help I will be forced to wipe everything out and do a fresh install. Please help.
I can provide you with other log files - just give me their exact localisation.
PS. I don't have access to the internet after I log in through the single mode. Lots of errors...eh.
Last edited by tempsanity (2007-06-27 14:12:34)

FIXED!
Well I'm not sure how exactly I managed to fix it, but I'll write it down for the people that may experience similar problems in the future.
I logged into my Linux using the 'single user mode' - by adding the 'single' word at the end of the kernel line in GRUB.
I gave myself write permissions by issuing the command 'mount -no remount, rw /'.
I removed the gensplash-initscripts, then installed normal initscripts, then installed gensplash-initscripts again and modified the rc.conf file.
Rebooted, fixed my network by modifying rc.conf file again.
I have to fix the local area settings like time, zone etc. and something is wrong with the xserver (the fonts are too big) but generally - it WORKS
Thanks for your help attempts
Cheers. Staying with Arch

MBP Won't Boot After Upgraded to EFI 2.2

Hi,
I upgraded to the latest EFI 2.2 firmware yesterday. After the reboot, the computer hangs on a black screen with a fan noisy. I have tried to reset SMC and PRAM & NVRAM, but there is no luck. I even couldn't hear the startup sound. Does anyone have experienced the same issue? Is my motherboard broken? It would be very appreciated if someone could help me out. I'm really frustrated now.
Thank you.
Kai.

alphaflight wrote:
I've got about 300 GB of space, so that shouldn't be the issue.
No, that certainly isn't the issue! Just had to make sure.
If it's not a hardware issue which happened to coincide with the update, the update may be corrupted or not completed. If either is the case, and you have another Mac available, you can try downloading the update from Apple Support Downloads, booting the MBP into FireWire Target Disk Mode (if it will cooperate), and trying to install the update that way. I have not tried this method, so cannot say if it will work or not, but I would try it prior to the alternative, which is to reinstall the OS (or, better yet, clone a backup to the MBP).

Playbook won't boot up after upgrade?

I upgraded to the new OS 2.0 today and now my playbook won't boot up? What's going on??

You need to follow these instructions to "debrick" your PlayBook:
You should have the Desktop Software version 7 installed on your PC, can be downloaded from http://us.blackberry.com/apps-software/desktop/
1. Make sure your PlayBook is powered off (sounds like yours might already be) press and hold down the power button until the unit forces the device off.
2. With the Desktop Software open on your computer and the PlayBook powered off, connect the PlayBook to your computer.
3. You should see an error screen from Desktop Software popup with the options to Retry, Update, or Cancel.
Very quickly choose the Update option.
4. Once this is complete your PlayBook will go back through the initial (as if new) setup wizard (entering the BlackBerryID, etc.), and then you can perform a restore using Desktop Software to return your personal data from the backup. Applications which you downloaded from AppWorld won't restore, but they can be easily reinstalled using AppWorld > My World section of AppWorld.
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you!
3. Install free BlackBerry Protect today for backups of contacts and data.
4. Guide to Unlocking your BlackBerry & Unlock Codes
Join our BBM Channels (Beta)
BlackBerry Support Forums Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

Mac mini won't boot after RAM upgrade.

Tried installing new RAM in my Mac Mini, 512MB stock to 2GB of Crucial. Followed the directions to a T, grounded myself the whole time.
Things I've tried so far:
1. Resetting the PRAM, no luck.
2. Holding option at start-up, shows no icon.
3. Holding shift, no luck.
4. Holding X, nothing.
How do I get it to accept a CD if it won't boot?

Welcome to Apple Discussions!
You clearly have a problem, but you don't describe exactly what that is other than that your mini won't boot after the upgrade. What happens when it starts up? Does it attempt to start and hang up on the grey or blue screens, or does it start beeping at you almost immediately after you try and start it up, and also flash the power light?
If the former, then you may have dislodged a connector while working inside the system, in which case opening it up and checking that everything is firmly connected would be the first thing to do. If the latter, then the beeping/light flashing is the system telling you it has failed the power-on self test and the pattern of beeps/lights indicates why. In your case likely the system can't find workable memory. In that instance, opening the system and ensuring that the RAM is firmly and fully seated would be a good step, and if the mini continues to fail, then replacing the new RAM with the original to test that the system will then start.
It is not likely that anything had damaged your MacOS install in the process of upgrading, thus normally no reason to need to boot to CD as a result of a RAM issue.

Mac OS won't boot after 2007-009 1.1 update

Hi all
Fairly major problem here. Mac OS X won't boot after the 2007-009 1.1 security update.
What I am left with is the mac boot screen, and not a lot happening. No rotating loading animation.
Any help would be really appreciated.
Thanks

I have been booting up for...2.45 hours now
Good grief!
Here are a few hints about what you should have done:
There are no guarantees, but following this procedure when installing updates and upgrades on your Mac will go a long way towards avoiding unpleasant after effects and ‘post-update stress disorder’.
It is also worth noting that it is an extreme rarity for updates to cause upsets to your system, but they may well reveal pre-existing ones, particularly those of which you may have been unaware. If you are actually aware of any glitches, make sure they are fixed before proceeding further.
So before you do anything else:
If you can, make a full backup first.
Turn off sleep mode for both screen and hard disk.
Disconnect all peripherals except your keyboard and mouse.
1. Repair Permissions (in Disk Utility)
2. Verify the state of your hard disk using Disk Utility. If any faults are reported, restart from your install disk (holding down the C key), go to Disk Utility, and repair your startup disk. Restart again to get back to your startup disk.
At least you can now be reasonably certain that your system does not contain any obvious faults that might cause an update/upgrade to fail.
3. Download the correct version of the COMBO update from the Apple download site. If your car runs on gasoline you would not want to fill the tank with diesel, so don’t try to install the PPC updater on an Intel Mac!
If you prefer to download updates via Software Update in the Apple menu (which would ensure that the correct version for your Mac was being downloaded), it is not recommended to allow SU to install major (or even minor) updates automatically. Set Software Update to just download the updater without immediately installing it. There is always the possibility that the combined download and install (which can be a lengthy process) might be interrupted by a power outage or your cat walking across the keyboard, and an interrupted install will almost certainly cause havoc. Once it is downloaded, you can install at a time that suits you. You should make a backup copy of the updater on a CD in case you ever need a reinstall.
Using the Combo updater ensures that all system files changed since the original 10.4.0 are included, and any that may have been missed out or subsequently damaged will be repaired. The Delta updater, although a temptingly smaller download, only takes you from the previous version to the new one, i.e. for example from 10.4.9 to 10.4.10. Software Update will generally download the Delta updater only. The preferable Combo updater needs to be downloaded from Apple's download site.
Now proceed as follows:
4. Close all applications.
5. Unplug all peripherals except your keyboard and mouse.
6. Install the update/upgrade. Do not under any circumstances interrupt this procedure. Do not do anything else on your computer while it is installing. Be patient.
7. When it ask for a restart to complete the installation, click restart. This can take longer than normal, there are probably thousands of files to overwrite and place in the correct location. Do nothing while this is going on.
8. Once your Mac is awake, repair permissions again, and you should be good to go!
If your Mac seems slightly sluggish or ‘different’, perform a second restart. It can’t hurt and is sometimes efficacious!
9. Open a few of your most used applications and check that all is OK. In this connection please remember that not all manufacturers of third party applications and plug-ins, add-ons, haxies etc, will have had time to do any necessary rewrites to their software to make them 10.4.10. compliant. Give them a weeks or two while you regularly check their websites for updates. This applies particularly to plug-ins for Safari 3.
N.B. Do not attempt to install two different updates at the same time as each may have different routines and requirements. Follow the above recommendations for each update in turn.
Lastly, Apple's own article on the subject of Software Update may also be useful reading:
http://docs.info.apple.com/article.html?artnum=106695
If you are updating Safari (or just have):
Input Managers from third parties can do as much harm as good. They use a security loophole to reach right into your applications' code and change that code as the application starts up. If you have installed 10.4.11 and Safari is crashing, the very first thing to do is clear out your InputManagers folders (both in your own Library and in the top-level /Library), log out and log back in, and try again.
So, disable all third party add-ons before updating Safari, as they may not have been updated yet for the new version. Add them back one by one. If something goes awry, remove it again and check on the software manufacturer's website for news of an update to match your version of Safari. Remember: Tiger up to 10.4.10 used Safari 2.0.4 or, if you downloaded it, Safari 3.0.3 beta. Safari 10.4.11 uses Safari 3.0.4 which is not a beta. If Safari 3.0.4 on 10.4.11 is not the fastest browser you have ever used, then something is wrong!
Moreover, trying to revert to Safari 2 when running 10.4.11 can have repercussions, as Safari 3.0.4 uses a completely different webkit on which other applications like iChat, Mail and Dashboard Widgets etc also rely.
Most errors reported here after an update are due to an unrepaired or undetected inherent fault in the system, and/or a third party ad-on. Two such add-on that have been frequently mentioned here for causing such problems are Piclens and Pithhelmet. If you have them, trash them.
Additional tips on software installation here:
http://docs.info.apple.com/article.html?artnum=106692

Mac pro cannot boot after upgrade to 10.8.3

My Mac Pro cannot boot after upgrade to 10.8.3. Anything firmware I can reset or how should I do.
I am using a early 2008 Mac Pro

Can you boot into safe mode? http://support.apple.com/kb/ht1455
If not, how about Recovery? http://support.apple.com/kb/ht4718
If you can, run Disk Utlity and repair the disk. You can try rebooting normally, but I would just reinstall after quitting Disk Utility.

Iphoto 8.1.2 won't open after upgrade to 10.8.2?

iphoto 8.1.2 won't open after upgrade to 10.8.2. I have tried to upgrade iphoto to 9.1 but it won't work.

To upgrade to iPhoto '11 (version 9.x.x) you musdt purchase the upgrade in the App store - that is not a free update.
what happens? What error messages do you get? if it crashes post the first 50 lines of the crash report
LN

Macbook pro won't boot after installing update 10.9.3

macbook pro won't boot after installing update 10.9.3

Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode.
Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

MacBook Pro won't boot after trying to install 10.7.3 update. Start up stalls at Apple logo and spinning gear.

MacBook Pro won't boot after trying to install 10.7.3 update. Start up stalls at Apple logo and spinning gear. Computer won't even start in safe mode.

My daughter's MacBook Pro was doing exactly the same thing. I don't know if it had anything to do with the latest update. She called me about a week ago saying that her MacBook began running slower by the day . She then called me Friday and told me that it wouldn't get past the gray screen and the gear just kept on spinning. I did everything I could over the phone including Safe mode which it wouldn't go into and thought maybe it was the hard drive. She took it to the Apple store. Originally, they also thought it was the hard drive. It ended up being a corrupted operating system (Lion). Apple genius simply re-installed Lion and she's back up and running. Good thing she backed up right before it crapped out. She'll be restoring everything tonight. Don't know if re-installing Lion will help your situation, but it did the trick for my daughter.

[SOLVED] Arch won't boot after I created a separate /var parition

Arch won't boot after I created a separate /var parition on an existing installation.And let me confess: it was maybe stupid trying to do it on an existing install.
I edited the fstab correctly, copied the files using rsync preserving permissions. Then I kept a backup of /var using tar. Then went on to delete everything under /var, ie /var/*, the /var folder is still there. All this I did from a live CD. After that I booted into my arch linux. Here I get messages about systemd successfully finishing fsck on each of my partitions, then the screen starts blinking. And there is no more output. Pressing Ctrl+Alt+Delete causes systemd to stop its services and reboot.
Having realized I had borked my system, I removed the /var line from fstab and restored /var from the tar file I made earlier. Again I did this from a live cd. Rebooted into my arch system, and again similar issues, namely that after fsck and messages informing a few services had started, the screen keeps blinking.
The live cd I used for reorganizing my partitions was elementary OS freya. They have GParted in there. I also have an arch install iso lying aroung from May 2013. If necessary, I can download the latest version. I am currently typing from a Windows installation I dual boot from.
I don't know how to extract any boot logs as I am locked out of the system. Here is my fstab in any case:
# Filesystem information
# /dev/sda5 LABEL=fs_root
UUID=b9d739cf-fd8c-46dd-a919-bd827dc47c66 / ext4 rw,noatime,data=ordered 0 1
# /dev/sda9 LABEL=fs_var
UUID=ec0f7a49-dccd-43ab-8651-9aa3fdb41cc7 /var ext4 rw,noatime,data=ordered 0 2
# /dev/sda2 LABEL=fs_boot
UUID=0e8ab31a-3bda-4b85-a901-a36f21b1583d /boot ext2 rw,noatime 0 2
# /dev/sda6 LABEL=fs_home
UUID=d9e63c47-274e-447f-ad01-0d97afe0fd34 /home ext4 rw,noatime,data=ordered 0 2
# /dev/sda7 LABEL=fs_swap
UUID=7301227c-e9f3-41b8-9d0f-4cf3c159491c none swap defaults 0 0
# /dev/sda3 LABEL=fs_win
UUID=12B639D1B639B5D7 /fs_win ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,nofail,noauto,x-systemd.automount 0 0
# /dev/sda3 LABEL=fs_share
UUID=D272269772268079 /fs_share ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,noauto,nofail,x-systemd.automount 0 0
I would greatly appreciate any help.
Last edited by richcocoa (2015-05-03 18:04:44)

Have you moved everything from /var to /new_var (i named it for learning purpose)? You shoud copy content from /var but not on the fly but booting from arch iso cd, and than you shoud mount your / into arch-chroot environement, mount all of your mount points and than copy content from default /var to new /var. The copying should be done with this
cp -rax
and you can add -v switch to verbose output. I have my own /var moved the same way.
The simples way is:
-boot the arch iso cd
-mount all of your mount point (i created here in this step /new_var to move /var to a new place, and this /new_var i put in /etc/fstab as /var later)
-copy /var to /new_var with -rax or -vrax (recursive, archive, this filesystem or verbose, recursive, archive, this filesystem switches)
-umount all of it
-reboot.
Last edited by firekage (2015-05-02 07:49:20)

IPhoto won't start after upgrade 1.1 for my new iMac. Now what do I do?

Had to upgrade according to screen. iPhoto won't start after upgrade 1.1 for my new iMac. Now what do I do?
I have restarted the computer. Brand new iMac intel. v 10.9.4

You need to upgrade iPhoto for Mavericks. Download the upgrade using App Store.

Mac won't boot after updating to OSX 10.6.4

I am on my 3rd Mac that won't boot after updating to OSX 10.6.4. One MacBook Pro and two iMacs. I fixed one but the last two are getting the better of me. HD is not fried. Have tried every keyboard shortcut on startup, Disk Warrior via. Target Disk, repairing permissions in single user mode. The machines will not boot off of a CD or DVD and it will not boot up in safe mode. Something in the startup files is preventing startup. I am suspecting Sophos antivirus. I tried to uninstall it and trash it but I think it's still blocking something. Any help would be appreciated.

Got it! Not sure if removing Sophos had anything to do with it but here's what I did.
1) boot dead machine in Target Disk Mode (iMac)
2) boot good machine off Snow Leopard disk (MacBook)
3) install OS to dead machine- I found this next part very curious. When the install was complete the MacBook restarted as the iMac.
4) ran software updates
5) shut down MacBook then shut down iMac
6) rebooted iMac- all was good
I actually did this twice because a co-worker had the exact same problem on her MacBook Pro. Got both fixed today.
Thanks everyone for your help!

Playbook won't boot after upgrade to v2

Similar Messages

Maybe you are looking for