Cant boot after upgrade with conflicts

hi
always when i install arch and do:
pacman -Syu
i have error:
failed to comit transaction (conflicting files)
without that upgrade i cant install desktop manager so i try:
pacman -Syuf
pacman -Sc
pacman -Syu
and it finish upgrade without errors but when i reboot it want boot:
Unable to find root device /dev/sda10
You are beign dropped to a recovery shell
and my keyboard doesnt work too, only i can i reinstall Arch and when i do that i have same problem next time with conflicting files.
i try many linux distros, gentoo, slackware and every of them works great only arch have stupit conflictioning, is this a bug ?
what can i do ?
thanx

For an explanation about those conflicting file errors (and how to fix them), take a look here.
As for the "unable to find root device" error, you probably borked something by running "pacman -Syuf" (never use the -f flag for a generic update). Take a look here at how to fix that.

Similar Messages

For Those Who Can't Boot After Upgrading To 10.5.6

For Those Who Can't Boot After Upgrading To 10.5.6
(and i am one of those)
how is Apple supposed to make them able to install future fixes and updates
once they finally acknowledge and address this horrible bug?
will they send free bootable CDs with the updates to 10.5.6?

What "Boot ROM version" do you have (check in the system profiler under "Hardware")? If it's not MBP31.0070.B07 or MBP21.00A5.B08, then you will need to update your MacBook Pro's firmware. To do this, you might need to connect an external display and mouse/keyboard, and then run the computer with the lid closed to bypass the laptop's monitor. Then apply the firmware patch and reboot the system. This might also be doable via "Screen Sharing" if you have that enabled and have another mac handy.
The firmware update is here: http://www.apple.com/downloads/macosx/apple/firmware_hardware/macbookproefifirmw areupdate151.html
Message was edited by: Topher Kessler

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.

My macbook pro retina 15'' cant boot after smc reset .

My macbook pro retina 15" cant boot after smc reset. Can someone find me a solution which does not require opening my laptop ? Thnx in advance .

Try Resetting the PRAM

Problem with dual boot after upgrade to Mountain lion

Hello Every One,
I have a Macbook pro from 2009 which had dual boot option Windows 7 + Snow Leopard.
The windows 7 had 2 partitions (C; and D: an extended partition).
I upgraded the OS X to Mountain lion. after upgrade the system showed 3 options at boot time. Mac, Windows and a recovery partition.
when i boot to windows the D: drive is gone...I mean even though i can see the partition in partition software, windows 7 stopped showing D: in "My computer".
So i used testdisk utility to get the D: drive back and now when i boot to mountain Lion i am able to access both C:(BOOTCAMP) and D: drives.
but now the problem is during boot time my Mac Book pro doesn't show the windows option.
Can some suggest a means to boot into windows 7? Also what is the purpose of recovery partition that Mountain lion adds to the system? I mean is it going to hurt if i get rid of it so that i can go back to my old configuration of 3 primary partitions (1 for windows 7 ...C: bootcamp + MountainLion) + 1 extended partition for D:
any help would be appreciated?
Regards

Ragu79 wrote:
Also what is the purpose of recovery partition that Mountain lion adds to the system? I mean is it going to hurt if i get rid of it
Leave it: http://support.apple.com/kb/HT4718

Can no longer dual boot after upgrade

Hi I used to run mac osx 10.7 dual booting with ubuntu 13.04. I used to press alt at startup to view the different partitions and select the appropriate OS. After upgrading to 10.9 I can no longer see the ubuntu partition when pressing alt. The disk is still there intact, but there is no way I can directly boot to it from startup. I tried creating another partition using disk utility and installing a fresh copy of linux and using the old linux partition as backup but whenever I select the ex-fat (or any other type for that matter) (for linux) I get:
File system resize support required, such as HFS+ with Journaling enabled.
I erased osx 10.9 and reset to factory settings back to 10.8 but the same problem continues.
I am not sure what to do to get dual booting working again. I do have an ubuntu backup on an external drive, but I would prefer not reformatting that partition.

I don't know why you couldn't repartition the disk using Disk Utility. You would have to provide more information about why you can't.
As for OPTION booting Ubuntu I'm not sure how that worked. Typically Ubuntu installs the GRUB bootloader/manager that provides a text menu from which you select which OS to start. GRUB replaces the OS X boot manager.

Hangs during boot after upgrading to Kernel 2.6.39

I have just installed Arch on a new computer. It works fine until I upgrade to Kernel 2.6.39. After that it hangs on boot.
The end of /var/log/everything.log is posted below.
Jul 26 23:52:06 localhost kernel: [ 6.036766] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table at offset 0x85F3
Jul 26 23:52:06 localhost kernel: [ 6.129046] adt7475 1-002e: ADT7473 device, revision 1
Jul 26 23:52:06 localhost kernel: [ 6.138997] [drm] nouveau 0000:04:00.0: Detected monitoring device: adt7473
Jul 26 23:52:06 localhost kernel: [ 6.139000] [drm] nouveau 0000:04:00.0: 1 available performance level(s)
Jul 26 23:52:06 localhost kernel: [ 6.139002] [drm] nouveau 0000:04:00.0: 0: memory 405MHz core 270MHz shader 540MHz
Jul 26 23:52:06 localhost kernel: [ 6.139233] [TTM] Zone kernel: Available graphics memory: 12371030 kiB.
Jul 26 23:52:06 localhost kernel: [ 6.139236] [TTM] Zone dma32: Available graphics memory: 2097152 kiB.
Jul 26 23:52:06 localhost kernel: [ 6.139238] [TTM] Initializing pool allocator.
Jul 26 23:52:06 localhost kernel: [ 6.139252] [drm] nouveau 0000:04:00.0: Detected 5376MiB VRAM
Jul 26 23:52:06 localhost kernel: [ 6.139260] mtrr: type mismatch for d0000000,8000000 old: write-back new: write-combining
Jul 26 23:52:06 localhost kernel: [ 6.150626] [drm] nouveau 0000:04:00.0: 512 MiB GART (aperture)
Jul 26 23:52:06 localhost kernel: [ 6.152371] [drm] nouveau 0000:04:00.0: failed to load fuc409d
Jul 26 23:52:06 localhost kernel: [ 6.176193] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
Jul 26 23:52:06 localhost kernel: [ 6.176195] [drm] No driver support for vblank timestamp query.
Jul 26 23:52:06 localhost kernel: [ 6.228800] No connectors reported connected with modes
Jul 26 23:52:06 localhost kernel: [ 6.228802] [drm] Cannot find any crtc or sizes - going 1024x768
Jul 26 23:52:06 localhost kernel: [ 6.231002] [drm] nouveau 0000:04:00.0: allocated 1024x768 fb: 0x8020000, bo ffff880608d97800
Jul 26 23:52:06 localhost kernel: [ 6.233786] Console: switching to colour frame buffer device 128x48
Jul 26 23:52:06 localhost kernel: [ 6.235094] fb0: nouveaufb frame buffer device
Jul 26 23:52:06 localhost kernel: [ 6.235094] drm: registered panic notifier
Jul 26 23:52:06 localhost kernel: [ 6.235098] [drm] Initialized nouveau 0.0.16 20090420 for 0000:04:00.0 on minor 0
Jul 26 23:52:06 localhost kernel: [ 6.255449] HDA Intel 0000:04:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
Jul 26 23:52:06 localhost kernel: [ 6.255451] hda_intel: Disable MSI for Nvidia chipset
Jul 26 23:52:06 localhost kernel: [ 6.255599] HDA Intel 0000:04:00.1: setting latency timer to 64
Jul 26 23:52:06 localhost kernel: [ 7.663482] EXT4-fs (sda3): re-mounted. Opts: (null)
Jul 26 23:52:06 localhost kernel: [ 7.807508] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
Jul 26 23:52:06 localhost kernel: [ 7.851401] Adding 265068k swap on /dev/sda2. Priority:-1 extents:1 across:265068k
Jul 26 23:52:06 localhost kernel: [ 8.569682] r8169 0000:08:00.0: eth0: link down
Jul 26 23:52:06 localhost kernel: [ 8.569687] r8169 0000:08:00.0: eth0: link down
Jul 26 23:52:06 localhost dhcpcd[747]: eth0: waiting for carrier
Jul 26 23:52:08 localhost dhcpcd[747]: eth0: carrier acquired
Jul 26 23:52:08 localhost kernel: [ 10.301736] r8169 0000:08:00.0: eth0: link up
Jul 26 23:52:08 localhost dhcpcd[747]: eth0: broadcasting for a lease
Jul 26 23:52:12 localhost dhcpcd[747]: eth0: offered 131.181.53.42 from 131.181.127.32
Jul 26 23:52:13 localhost dhcpcd[747]: eth0: acknowledged 131.181.53.42 from 131.181.59.48
Jul 26 23:52:13 localhost dhcpcd[747]: eth0: checking for 131.181.53.42
Jul 26 23:52:18 localhost dhcpcd[747]: eth0: leased 131.181.53.42 for 43200 seconds
Jul 26 23:52:18 localhost dhcpcd[747]: forked to background, child pid 774
Jul 26 23:52:18 localhost crond[823]: /usr/sbin/crond 4.5 dillon's cron daemon, started with loglevel info
Jul 26 23:53:01 localhost crond[823]: FILE /etc/cron.d/prune-cronstamps USER root PID 835 job prune-cronstamps
Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 836 job sys-hourly
Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 837 job sys-daily
Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 838 job sys-weekly
Any help fixing this would be greatly appreciated.

I have been trying to isolate the problem a little further. I re-installed (with just the base and sudo) and after upgrading pacman rebooted and it worked without fail. Then I installed libusb and libusb-compat which where required when I tried to upgrade just the kernel using
pacman -S kernel26
which initially failed because of the missing dependencies libusb and libusb-compat. I then re-booted and that worked without a problem.
I then upgraded to Kernel 2.6.39 using the above command and then it hung on rebooting. I saved the logs at each stage.
The additional logs in errors.log in the reboot that failed are as follows.
ul 26 16:28:39 O313 kernel: [ 5.120698] [drm] nouveau 0000:04:00.0: Pointer to BIT loadval table invalid
Jul 26 16:28:39 O313 kernel: [ 5.360508] [drm] nouveau 0000:04:00.0: failed to load fuc409d
Jul 26 16:28:39 O313 kernel: [ 5.808016] sd 20:0:0:0: [sdb] Assuming drive cache: write through
Jul 26 16:28:39 O313 kernel: [ 5.809960] sd 20:0:0:0: [sdb] Assuming drive cache: write through
Jul 26 16:28:39 O313 kernel: [ 5.812116] sd 20:0:0:0: [sdb] Assuming drive cache: write through
Jul 26 16:28:35 O313 udevd[369]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'
The end of kernel.log is as follows:
Sat Jul 9 14:57:41 CEST 2011
Jul 26 16:28:39 O313 kernel: [ 0.000000] Command line: root=/dev/disk/by-uuid/e4733c60-3e54-4001-a83e-415b690dfcb0 ro
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-provided physical RAM map:
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000000100000 - 00000000cfed0000 (usable)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfed0000 - 00000000cfed1000 (ACPI NVS)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfed1000 - 00000000cfee0000 (ACPI data)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfee0000 - 00000000cff00000 (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000100000000 - 0000000630000000 (usable)
Jul 26 16:28:39 O313 kernel: [ 0.000000] NX (Execute Disable) protection: active
Jul 26 16:28:39 O313 kernel: [ 0.000000] DMI 2.4 present.
Jul 26 16:28:39 O313 kernel: [ 0.000000] DMI: Gigabyte Technology Co., Ltd. X58A-UD5/X58A-UD5, BIOS FD 02/01/2011
Jul 26 16:28:39 O313 kernel: [ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
Jul 26 16:28:39 O313 kernel: [ 0.000000] No AGP bridge found
Jul 26 16:28:39 O313 kernel: [ 0.000000] last_pfn = 0x630000 max_arch_pfn = 0x400000000
And this is the end of daemon.log
Jul 26 16:27:49 O313 init: Switching to runlevel: 6
Jul 26 16:27:50 O313 dhcpcd: received SIGTERM, stopping
Jul 26 16:27:50 O313 dhcpcd: eth0: removing interface
Jul 26 16:28:39 O313 2.352592] udevd[87]: starting version 171
Jul 26 16:28:39 O313 4.531007] udevd[370]: starting version 171
Jul 26 16:28:39 O313 dhcpcd: version 5.2.2 starting
Jul 26 16:28:39 O313 dhcpcd: eth0: waiting for carrier
Jul 26 16:28:35 O313 udevd[369]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'
Jul 26 16:28:39 O313 init: Entering runlevel: 3
Please let me know if any further information would be useful in tracking down this problem. Also ignore any timings in my initial post they were incorrect.
Last edited by TheStatsMan (2011-07-26 07:40:48)

Hanging on boot after upgrading server.app

After upgrading to 10.9 Server.App my boot hangs at "/etc/rc.server: line 14: /etc/rc.server.firewall: No such file or directory" and won't boot into safe mode either. Anyone know how I can fix this without restoring from a backup?

Cameron, thanks for your feedback.
I'm on a 2011 iMac, with a DIY Fusion Drive (I added a SSD inside). I always had slow startups. I thought it was the custom Fusion Drive's fault, but now I know it was not.
Now I can't boot at all, just after applying the most recent 10.9.2 security update. This is a software issue. The iMac was running Mountain Lion Server, then I upgraded to Mavericks but did not upgrade to Mavericks Server. However there were remains of the old 10.8 Server app.
As I said, yesterday I deleted all those remains (booting from an external drive). However I forgot the most obvious thing: open that **** /etc/rc.server file and comment out line 14.
This morning I booted the iMac again, in verbose mode. The message about /etc/rc.server was not there, at last, but fsck was launched and took a long time. I had to go to work, where I am now, and I don't know if fsck finished its work. I'll let you know...

Mac Mini stuck at boot after upgrading to Yosimite

Hi All,
I am using mac Mini late 2012 model with 4 gb ram. I have recently upgraded to OSX Yosimite.
But now I am facing issue with it.
My Mac stops at boot. With Apple logo, grey/white screen and progree bar with 0% progress.
If I keep it as it is for some time, Mac mini temperature rises and i feel the heat while touching the mac mini. And still progress bar show 0% progress.
But when I switch it off with the help of power button and restart it, it works fine.
This happen every now and then. I have only monitor, Bluetooth mouse, wired keyboard and LAN cable attached to it. (WIFI stops working after upgrading to OSX now there is no wifi icon in system preferences or in task bar )
I have tried clean install also. But no success.
Please suggest why it stops at 0% progress bar. This is working fine before upgrading.
Regards
Siddharth

Hi Adding screenshot of the same. It stuck at 0 %

No Boot after install with

(for the 754 machine listed in my sig)
hey all - I cant boot into windows after a clean install of XP...will either hang on OS loading screen or on 'detecting IDE drives' after mem check. I''ve updated the bios to current and i've tried using all Nforce SATA drivers out (2.5, .2.6, 2.7) with no luck. The only way i seem to be able to boot into windows is not to install the SATA drivers. When i go that route my machine runs slow. Anyone help me out?

there have been some issues with the Maxtor 16Mb Cache HDDs & Neo2 Problems To a large extent these seem to have been solved.
There are also some beta bios about which may help , Just take care which one you use on which mobo
K8N NEO PLATINUM BIOS 1.51 beta

Iphone4 randomly chrashes and bootes after upgrade to ios7.1

Hello,
after upgrading from ios7.0 to ios7.1 my Iphone 4 chrashes and then bootes. Sometimes it does not happen during the whole day. Then again it crashes 5- 10 times a day.
I tried a few strategies, incl complete reset. Even loaded Ios7.1 with 2 different PCs. No success. It seems also to happen quite randomly, at least I couild not identify any logic behind it. Very frustrating experience.
Does anyone have the same experience? Any idea what to do?
Thanks / Thomas

As Texas Mac Man wrote in another post, the problem was fixed by repeated shut down of the iPad till GC started to work properly.

[Solved] Cant boot after editing fstab ( virtualbox )

what information do i need to post here to help, and how do i get it since i cant boot in ?
Last edited by Shockwave0 (2013-11-07 00:48:14)

im using openbox i opened up /etc/fstab with leafpad heres what it looks like
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda1
UUID=aff5b1d2-0452-467f-81e7-dc3b2298101e / ext4 rw,relatime,data=ordered 0 1
# /dev/sda3
# UUID=1519cef9-0d8d-4ea4-b9d5-cc94b09cd59a none swap defaults 0 0
Last edited by Shockwave0 (2013-11-07 00:05:54)

Helpp my itunes cant open after upgrading it !!

pls help me i cant open it after upgrading it and restarting the computer

You need to post more info after reading some of the topics here.
It could be any one of 50 solutions.

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

HT4623 We're sorry, we are unable to continue with your activation at this time. Please try again later, or contact customer care. What is this thing,i cant connect after upgrade my i phone 3gs to ios 6 from ios 5.1,auchhh,

We're sorry, we are unable to continue with your activation at this time.
Please try again later, or contact customer care. what is this thing?i try to upgrade my ios to 6.1 from 5.1.1,after i do this,i cant connect to iTunes although i had and have a internet connection

This message indicates that your phone was hacked or jailbroken to unlock it.
Then when you updated/restored your phone it locked back up to the original carrier.
Only the carrier that the phone is locked to can unlock it.

Cant boot after upgrade with conflicts

Similar Messages

Maybe you are looking for