2009 Xserve no boot after configuring LOM

Got a used 2009 Xserve 2 x 2.26 Quad that i just purchased. Fresh install of OS X 10.10. Running off internal SSD.
Currently no drives loaded in the bays.
Installed "Server" app, configured an working like a champ, running for 2-3 days.
Earlier today i configured LOM, the system remained to work as per normal as it has for the past couple days.
Had to reboot the machine before, after that it is absolutely useless, on startup it gets about 1/3 of the way along
the loading bar (on yosemite boot screen), and hangs there, have reset SMC, tried to reset NVRAM via the front buttons but
i cant tell if it was successful - see below.
Ive also tried to boot via a USB with Yosemite install on it - no go.
Disconnected and SSD and fitted HDD to a bay with a fresh working volume on it - no go.
Unsure about the function of Startup Method selection and operation though, I've selected the modes i want, then held the system identifier
button until the top row it lit up, let go of the button and then nothing happens, system doesn't turn off/restart in to that mode, it just appears to hang
after that selection. Is this right?

Eventually it booted from a USB drive and allowed me to reinstall OSX.

Similar Messages

Mac Pro 2009 won't boot after airport installation

Hey everyone, looking for some insight here.
I recently bought a Mac Pro 2009 running Mavericks (at time of receipt). It didn't come with an airport card so I purchased one to install myself. The Mac was running fine until this evening when I finally got around to installing the card, however since then it won't get past the grey boot screen with apple logo. I've tried disconnecting the airport card to see if that reverted it, but no change. I also can't boot into safe mode, so that's no good. The only thing I can do is bring up the giant padlock with the option key held, which I saw elsewhere was connected with a firmware password (my admin doesn't work).
Any advice here would be greatly appreciated. Thanks!

It wouldn't be much of a lock if you could circumvent it with advice from a forum.
Obviously a valid point, although possibly somewhat niaive where forums are concerned (no disrespect intended).
It was more an expression of frustration than anything else, to be honest, though. It's kind of absurd that this happened following a simple hardware upgrade. Most people I know aren't even aware they can set a firmware password, so basically what it means is don't upgrade a machine that's intented to be upgraded (I'm aware of the hyperbole here).
Looks like it will be a Mac store trip, though, yes. A pain in the arse since even my nearest authorised technician is miles away.

Mac Mini Early 2009 Won't Boot After Mavericks Update

I had Mavericks installed on my Mac for a while now and recently, it did a software update... Since then, I rebooted the system when it asked me to and it has not been able to boot up since then. It reaches the Apple Screen, tries to load the OS and my Mac shuts off Completely...
I recently upgraded the Hard Drive on the system, so I am currently using my old hard drive running OS X 10.5.8... I plugged in my Hard Drive that has OS X Mavericks on it and I tried to verify the disk. When I do so in Disk Utility, I get this message:
I went on a couple of websites where people had this same issue, and I followed the instructions where someone said to open Disk Utility, select the Partition and Press "CMD + i". I got the name of my drive from Disk Identifier. I opened Terminal and typed in "sudo /sbin/fsck_hfs -yprf /dev/disk1s2"
It ran the code and this is the output...
Last login: Sat Mar 15 10:05:40 on console
fadil-shamir-khans-mac-mini:~ silentarts$ sudo /sbin/fsck_hfs -yprd /dev/disk1s2
WARNING: Improper use of the sudo command could lead to data loss
or the deletion of important system files. Please double-check your
typing when using sudo. Type "man sudo" for more information.
To proceed, enter your password, or type Ctrl-C to abort.
Password:
/dev/rdisk1s2: starting
          Using cacheBlockSize=32K cacheTotalBlock=1024 cacheSize=32768K.
          Journal replay returned error = 22
** Checking Journaled HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
** Rebuilding Catalog B-tree.
hfs_UNswap_BTNode: invalid node height (1)
hfs_swap_BTNode: record #57 invalid offset (0x0003)
   Invalid node structure
(4, 6913)
hfs_swap_BTNode: record #-1 invalid offset (0x004D)
   Invalid node structure
(4, 6915)
hfs_swap_BTNode: invalid forward link (0x0065006E)
hfs_swap_BTNode: invalid backward link (0x0075002E)
hfs_swap_BTNode: invalid node height (110)
hfs_swap_BTNode: offsets 103 and 104 out of order (0x0000, 0x0000)
   Invalid node structure
(4, 6916)
hfs_swap_BTNode: record #-1 invalid offset (0x0075)
   Invalid node structure
(4, 6917)
hfs_swap_BTNode: invalid forward link (0x002E006E)
hfs_swap_BTNode: invalid backward link (0x00690062)
hfs_swap_BTNode: offsets 132 and 133 out of order (0x0000, 0x0000)
   Invalid node structure
(4, 6918)
hfs_swap_BTNode: record #-1 invalid offset (0x0065)
   Invalid node structure
(4, 6921)
hfs_swap_BTNode: invalid forward link (0x006D0065)
hfs_swap_BTNode: invalid backward link (0x006E0074)
hfs_swap_BTNode: invalid node height (80)
hfs_swap_BTNode: record #113 invalid offset (0x0075)
   Invalid node structure
(4, 6922)
hfs_swap_BTNode: record #-1 invalid offset (0xA26E)
   Invalid node structure
(4, 6923)
hfs_swap_BTNode: invalid forward link (0xCE4D961D)
hfs_swap_BTNode: record #-1 invalid offset (0x0065)
   Invalid node structure
(4, 6924)
hfs_swap_BTNode: invalid forward link (0x006E0067)
hfs_swap_BTNode: invalid backward link (0x0065004C)
hfs_swap_BTNode: invalid node height (105)
hfs_swap_BTNode: offsets 113 and 114 out of order (0x0078, 0x0032)
   Invalid node structure
(4, 6925)
hfs_swap_BTNode: invalid forward link (0x00650073)
hfs_swap_BTNode: invalid backward link (0x00730061)
hfs_swap_BTNode: invalid node height (103)
hfs_swap_BTNode: offsets 99 and 100 out of order (0x0000, 0x0000)
   Invalid node structure
(4, 6926)
hfs_swap_BTNode: invalid forward link (0x0078002E)
hfs_swap_BTNode: invalid backward link (0x0070006E)
hfs_swap_BTNode: invalid node height (103)
hfs_swap_BTNode: offsets 4 and 5 out of order (0x0000, 0x0000)
   Invalid node structure
(4, 6932)
hfs_swap_BTNode: invalid forward link (0x0047004B)
hfs_swap_BTNode: invalid backward link (0x00500061)
hfs_swap_BTNode: invalid node height (110)
hfs_swap_BTNode: record #99 invalid offset (0x5277)
   Invalid node structure
(4, 6937)
hfs_swap_BTNode: invalid forward link (0x00460072)
hfs_swap_BTNode: invalid backward link (0x0061006D)
hfs_swap_BTNode: invalid node height (101)
hfs_swap_BTNode: offsets 80 and 81 out of order (0x0000, 0x0000)
   Invalid node structure
(4, 6938)
hfs_swap_BTNode: invalid backward link (0x07110000)
hfs_swap_BTNode: invalid forward link (0x00610074)
hfs_swap_BTNode: invalid backward link (0x00650032)
hfs_swap_BTNode: invalid node height (64)
hfs_swap_BTNode: record #49 invalid offset (0x525E)
   Invalid node structure
(4, 6940)
hfs_swap_BTNode: record #-1 invalid offset (0x006F)
   Invalid node structure
(4, 6941)
hfs_swap_BTNode: invalid forward link (0x00770040)
hfs_swap_BTNode: invalid backward link (0x00320078)
hfs_swap_BTNode: invalid node height (46)
hfs_swap_BTNode: record #111 invalid offset (0x006D)
   Invalid node structure
(4, 6942)
hfs_swap_BTNode: invalid backward link (0x0056000F)
hfs_swap_BTNode: invalid node kind (62)
hfs_swap_BTNode: invalid node height (233)
hfs_swap_BTNode: record #39 invalid offset (0x0067)
   Invalid node structure
(4, 6944)
hfs_swap_BTNode: invalid forward link (0x00650064)
hfs_swap_BTNode: invalid backward link (0x00400032)
hfs_swap_BTNode: invalid node height (120)
hfs_swap_BTNode: record #45 invalid offset (0xCE4D)
   Invalid node structure
(4, 6945)
hfs_swap_BTNode: record #-1 invalid offset (0x0047)
   Invalid node structure
(4, 6946)
hfs_swap_BTNode: invalid forward link (0x004B0054)
hfs_swap_BTNode: invalid backward link (0x00610062)
hfs_swap_BTNode: invalid node height (98)
hfs_swap_BTNode: record #96 invalid offset (0x0065)
   Invalid node structure
(4, 6947)
hfs_swap_BTNode: invalid forward link (0x00720061)
hfs_swap_BTNode: invalid backward link (0x006D0065)
hfs_swap_BTNode: invalid node height (83)
hfs_swap_BTNode: offsets 102 and 103 out of order (0x0000, 0x0000)
   Invalid node structure
(4, 6948)
hfs_swap_BTNode: record #-1 invalid offset (0x0065)
   Invalid node structure
(4, 6951)
hfs_swap_BTNode: invalid forward link (0x006C0063)
hfs_swap_BTNode: invalid backward link (0x006F006D)
hfs_swap_BTNode: invalid node height (101)
hfs_swap_BTNode: offsets 69 and 70 out of order (0x0040, 0x0032)
   Invalid node structure
(4, 6952)
hfs_swap_BTNode: invalid forward link (0x0073006B)
hfs_swap_BTNode: invalid backward link (0x00370030)
hfs_swap_BTNode: invalid node height (64)
hfs_swap_BTNode: offsets 48 and 49 out of order (0x0000, 0x0000)
   Invalid node structure
(4, 6953)
hfs_swap_BTNode: invalid forward link (0x000A0184)
hfs_swap_BTNode: invalid backward link (0x7A7D0000)
hfs_swap_BTNode: invalid node height (10)
hfs_swap_BTNode: record #-1 invalid offset (0x000D)
   Invalid node structure
(4, 6957)
hfs_swap_BTNode: invalid forward link (0x0043006F)
hfs_swap_BTNode: invalid backward link (0x00640065)
hfs_swap_BTNode: invalid node height (82)
hfs_swap_BTNode: offsets 99 and 100 out of order (0x0000, 0x0000)
   Invalid node structure
(4, 6958)
hfs_swap_BTNode: invalid forward link (0x004C0065)
hfs_swap_BTNode: invalid backward link (0x00610064)
hfs_swap_BTNode: invalid node height (101)
hfs_swap_BTNode: offsets 112 and 113 out of order (0x0000, 0x0000)
   Invalid node structure
(4, 6959)
hfs_swap_BTNode: invalid forward link (0x002E0073)
hfs_swap_BTNode: invalid backward link (0x00740072)
hfs_swap_BTNode: invalid node height (105)
hfs_swap_BTNode: record #106 invalid offset (0x0065)
   Invalid node structure
(4, 6962)
hfs_swap_BTNode: invalid forward link (0x006C006C)
hfs_swap_BTNode: invalid backward link (0x00650072)
hfs_swap_BTNode: invalid node height (46)
hfs_swap_BTNode: record #114 invalid offset (0xA273)
   Invalid node structure
(4, 6963)
hfs_swap_BTNode: invalid forward link (0x001C0047)
hfs_swap_BTNode: invalid backward link (0x004B004E)
hfs_swap_BTNode: invalid node height (111)
hfs_swap_BTNode: record #115 invalid offset (0x5277)
   Invalid node structure
(4, 6964)
hfs_swap_BTNode: invalid forward link (0x00700061)
hfs_swap_BTNode: invalid backward link (0x00720065)
hfs_swap_BTNode: invalid node height (86)
hfs_swap_BTNode: offsets 103 and 104 out of order (0x0000, 0x0000)
   Invalid node structure
(4, 6965)
hfs_swap_BTNode: invalid forward link (0x00740072)
hfs_swap_BTNode: invalid backward link (0x0069006E)
hfs_swap_BTNode: invalid node height (103)
hfs_swap_BTNode: record #112 invalid offset (0x0067)
   Invalid node structure
(4, 6966)
hfs_swap_BTNode: invalid backward link (0xF1F30000)
hfs_swap_BTNode: record #-1 invalid offset (0x0069)
   Invalid node structure
(4, 6968)
hfs_swap_BTNode: invalid forward link (0x006E0067)
hfs_swap_BTNode: invalid backward link (0x00730002)
hfs_swap_BTNode: invalid node height (134)
hfs_swap_BTNode: invalid node height (11)
hfs_swap_BTNode: invalid record count (0x5431)
   Invalid record count
(4, 6971)
hfs_swap_BTNode: record #-1 invalid offset (0x0073)
   Invalid node structure
(4, 6975)
hfs_swap_BTNode: invalid forward link (0x00020086)
hfs_swap_BTNode: invalid node height (11)
hfs_swap_BTNode: invalid record count (0x548C)
   Invalid record count
(4, 6976)
hfs_swap_BTNode: invalid forward link (0x00610072)
hfs_swap_BTNode: invalid backward link (0x00640044)
hfs_swap_BTNode: invalid node height (101)
hfs_swap_BTNode: offsets 114 and 115 out of order (0x0000, 0x0000)
   Invalid node structure
(4, 6977)
hfs_swap_BTNode: invalid forward link (0x0072006F)
hfs_swap_BTNode: invalid backward link (0x006C006C)
hfs_swap_BTNode: invalid node height (101)
hfs_swap_BTNode: offsets 112 and 113 out of order (0x0072, 0x0046)
   Invalid node structure
(4, 6981)
hfs_swap_BTNode: invalid forward link (0x006C006C)
hfs_swap_BTNode: invalid backward link (0x00650072)
hfs_swap_BTNode: invalid node height (46)
hfs_swap_BTNode: offsets 113 and 114 out of order (0x0000, 0x0000)
   Invalid node structure
(4, 6982)
hfs_swap_BTNode: invalid forward link (0x00690066)
hfs_swap_BTNode: invalid backward link (0x00690063)
hfs_swap_BTNode: invalid node height (97)
hfs_swap_BTNode: record #115 invalid offset (0x5277)
   Invalid node structure
(4, 6983)
hfs_swap_BTNode: invalid forward link (0x00700061)
hfs_swap_BTNode: invalid backward link (0x00720065)
hfs_swap_BTNode: invalid node height (86)
hfs_swap_BTNode: offsets 103 and 104 out of order (0x0000, 0x0000)
   Invalid node structure
(4, 6984)
hfs_swap_BTNode: invalid forward link (0x00740072)
hfs_swap_BTNode: invalid backward link (0x0069006E)
hfs_swap_BTNode: invalid node height (103)
hfs_swap_BTNode: record #112 invalid offset (0x0067)
   Invalid node structure
(4, 6985)
hfs_swap_BTNode: invalid backward link (0x00020000)
hfs_swap_BTNode: record #-1 invalid offset (0x0073)
   Invalid node structure
(4, 6987)
hfs_swap_BTNode: invalid forward link (0x00740072)
hfs_swap_BTNode: invalid backward link (0x0069006E)
hfs_swap_BTNode: invalid node height (103)
hfs_swap_BTNode: offsets 113 and 114 out of order (0x0000, 0x0000)
   Invalid node structure
(4, 6988)
hfs_swap_BTNode: invalid node height (11)
hfs_swap_BTNode: invalid record count (0x5581)
   Invalid record count
(4, 6990)
hfs_swap_BTNode: record #-1 invalid offset (0x0073)
   Invalid node structure
(4, 6995)
hfs_swap_BTNode: invalid forward link (0x00020086)
hfs_swap_BTNode: invalid node height (11)
hfs_swap_BTNode: invalid record count (0x55DC)
   Invalid record count
(4, 6996)
hfs_swap_BTNode: invalid forward link (0x00610072)
hfs_swap_BTNode: invalid backward link (0x00640044)
hfs_swap_BTNode: invalid node height (101)
hfs_swap_BTNode: offsets 114 and 115 out of order (0x0000, 0x0000)
   Invalid node structure
(4, 6997)
hfs_swap_BTNode: invalid forward link (0x006F006C)
hfs_swap_BTNode: invalid backward link (0x006C0065)
hfs_swap_BTNode: invalid node height (114)
hfs_swap_BTNode: record #45 invalid offset (0x0069)
   Invalid node structure
(4, 7001)
hfs_swap_BTNode: invalid forward link (0x002E0073)
hfs_swap_BTNode: invalid backward link (0x00740072)
hfs_swap_BTNode: invalid node height (105)
hfs_swap_BTNode: offsets 108 and 109 out of order (0x0000, 0x0000)
   Invalid node structure
(4, 7002)
hfs_swap_BTNode: invalid node kind (-127)
hfs_swap_BTNode: invalid node height (164)
hfs_swap_BTNode: record #-1 invalid offset (0x006D)
   Invalid node structure
(4, 7003)
hfs_swap_BTNode: invalid forward link (0x00700061)
hfs_swap_BTNode: invalid backward link (0x00720065)
hfs_swap_BTNode: invalid node height (86)
hfs_swap_BTNode: offsets 103 and 104 out of order (0x0000, 0x0000)
   Invalid node structure
(4, 7004)
hfs_swap_BTNode: invalid forward link (0x00740072)
hfs_swap_BTNode: invalid backward link (0x0069006E)
hfs_swap_BTNode: invalid node height (103)
hfs_swap_BTNode: offsets 112 and 113 out of order (0x0000, 0x0000)
   Invalid node structure
(4, 7005)
hfs_swap_BTNode: invalid backward link (0x00020000)
hfs_swap_BTNode: record #-1 invalid offset (0x0069)
   Invalid node structure
(4, 7007)
hfs_swap_BTNode: invalid forward link (0x006E0067)
hfs_swap_BTNode: invalid backward link (0x00730002)
hfs_swap_BTNode: invalid node height (134)
hfs_swap_BTNode: record #-1 invalid offset (0x0067)
   Invalid node structure
(4, 7008)
hfs_swap_BTNode: invalid forward link (0x00730006)
hfs_swap_BTNode: invalid backward link (0x000B56C5)
hfs_swap_BTNode: offsets 2 and 3 out of order (0x0000, 0x0000)
   Invalid node structure
(4, 7009)
hfs_swap_BTNode: record #-1 invalid offset (0x0061)
   Invalid node structure
(4, 7016)
hfs_swap_BTNode: invalid forward link (0x006C0069)
hfs_swap_BTNode: invalid backward link (0x007A0061)
hfs_swap_BTNode: invalid node height (98)
hfs_swap_BTNode: offsets 106 and 107 out of order (0x0000, 0x0000)
   Invalid node structure
(4, 7017)
hfs_swap_BTNode: invalid forward link (0x00790050)
hfs_swap_BTNode: invalid backward link (0x00690063)
hfs_swap_BTNode: invalid node height (107)
hfs_swap_BTNode: offsets 98 and 99 out of order (0x0072, 0x0050)
   Invalid node structure
(4, 7018)
hfs_swap_BTNode: invalid forward link (0x00720069)
hfs_swap_BTNode: invalid backward link (0x00760056)
hfs_swap_BTNode: invalid node height (105)
hfs_swap_BTNode: offsets 99 and 100 out of order (0x0000, 0x0000)
   Invalid node structure
(4, 7019)
hfs_swap_BTNode: invalid forward link (0x00690063)
hfs_swap_BTNode: invalid backward link (0x0061002D)
hfs_swap_BTNode: invalid node height (115)
hfs_swap_BTNode: offsets 102 and 103 out of order (0x0000, 0x0000)
   Invalid node structure
(4, 7021)
hfs_swap_BTNode: invalid forward link (0x00860000)
hfs_swap_BTNode: invalid node kind (87)
hfs_swap_BTNode: invalid node height (225)
hfs_swap_BTNode: invalid record count (0xCE58)
   Invalid record count
(4, 7022)
hfs_swap_BTNode: record #-1 invalid offset (0x0069)
   Invalid node structure
(4, 7023)
hfs_swap_BTNode: invalid forward link (0x0065006C)
hfs_swap_BTNode: invalid backward link (0x00640070)
hfs_swap_BTNode: invalid node height (97)
hfs_swap_BTNode: record #97 invalid offset (0x006F)
   Invalid node structure
(4, 7024)
hfs_swap_BTNode: invalid backward link (0x00120184)
hfs_swap_BTNode: invalid node kind (-102)
hfs_swap_BTNode: invalid node height (18)
hfs_swap_BTNode: invalid forward link (0x002D0032)
hfs_swap_BTNode: invalid backward link (0x002D006F)
hfs_swap_BTNode: invalid node height (99)
hfs_swap_BTNode: record #99 invalid offset (0x0065)
   Invalid node structure
(4, 7027)
hfs_swap_BTNode: invalid forward link (0x006E0069)
hfs_swap_BTNode: invalid backward link (0x0061002D)
hfs_swap_BTNode: invalid node height (115)
hfs_swap_BTNode: record #102 invalid offset (0x0069)
   Invalid node structure
(4, 7028)
hfs_swap_BTNode: invalid backward link (0x0184A0B1)
hfs_swap_BTNode: record #21 invalid offset (0x81A4)
   Invalid node structure
(4, 7030)
hfs_swap_BTNode: record #-1 invalid offset (0x0075)
   Invalid node structure
(4, 7031)
hfs_swap_BTNode: invalid forward link (0x00740068)
hfs_swap_BTNode: invalid backward link (0x002D0073)
hfs_swap_BTNode: invalid node height (104)
hfs_swap_BTNode: record #102 invalid offset (0x0073)
   Invalid node structure
(4, 7032)
** Rechecking volume.
** Checking Journaled HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
   Missing thread record (id = 691885)
   Missing thread record (id = 691919)
   Incorrect number of thread records
(4, 23903)
          CheckCatalogBTree: dirCount = 140937, dirThread = 140885
   Incorrect number of thread records
(4, 23903)
          CheckCatalogBTree: fileCount = 701678, fileThread = 701730
** Checking multi-linked files.
** Checking Catalog hierarchy.
   Missing thread record (id = 741414)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741420)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741429)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741435)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741432)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741444)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741438)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741459)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741441)
   Invalid directory item count
   (It should be 0 instead of 2)
   Invalid directory item count
   (It should be 9 instead of 13)
   Missing thread record (id = 741450)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741426)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741465)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741453)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741492)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741456)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741462)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741468)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741471)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741447)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741474)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741417)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741477)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741480)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741483)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741489)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741486)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741498)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741504)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741507)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741423)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 741495)
   Invalid directory item count
   (It should be 0 instead of 2)
   Invalid directory item count
   (It should be 201 instead of 227)
   Missing thread record (id = 741510)
   Invalid directory item count
   (It should be 0 instead of 1)
   Missing thread record (id = 691884)
   Invalid directory item count
   (It should be 0 instead of 4)
   Missing thread record (id = 691911)
   Invalid directory item count
   (It should be 0 instead of 1)
   Missing thread record (id = 691913)
   Invalid directory item count
   (It should be 0 instead of 1)
   Missing thread record (id = 691915)
   Invalid directory item count
   (It should be 0 instead of 1)
   Missing thread record (id = 691917)
   Invalid directory item count
   (It should be 0 instead of 1)
   Missing thread record (id = 691919)
   Invalid directory item count
   (It should be 2 instead of 5)
   Missing thread record (id = 691904)
   Invalid directory item count
   (It should be 0 instead of 1)
   Missing thread record (id = 691906)
   Invalid directory item count
   (It should be 0 instead of 2)
   Missing thread record (id = 691909)
   Invalid directory item count
   (It should be 0 instead of 1)
   Missing thread record (id = 743122)
   Invalid directory item count
   (It should be 0 instead of 3)
   Invalid directory item count
   (It should be 165 instead of 417)
   Invalid volume directory count
   (It should be 140922 instead of 140936)
   Invalid volume file count
   (It should be 701648 instead of 701678)
** Checking Extended Attributes file.
   Incorrect number of Extended Attributes
   (It should be 347482 instead of 346415)
** Checking volume bitmap.
   Volume Bit Map needs minor repair
** Checking volume information.
   Invalid volume free block count
   (It should be 59615838 instead of 50477719)
          invalid VHB nextCatalogID
          invalid VHB attributesFile.clumpSize
   Volume Header needs minor repair
(2, 0)
   Verify Status: VIStat = 0xa000, ABTStat = 0x0040 EBTStat = 0x0000
                  CBTStat = 0x0800 CatStat = 0x00004200
** Repairing volume.
   Missing directory record (id = 691885)
** Look for missing items in lost+found directory.
          FixOrphanedFiles: Created thread record for id=743119 (err=0)
          FixOrphanedFiles: Created thread record for id=743121 (err=0)
          FixOrphanedFiles: Created thread record for id=742222 (err=0)
          FixOrphanedFiles: Created thread record for id=743122 (err=0)
          FixOrphanedFiles: Created thread record for id=691904 (err=0)
          FixOrphanedFiles: Created thread record for id=691906 (err=0)
          FixOrphanedFiles: Created thread record for id=691909 (err=0)
          FixOrphanedFiles: Created thread record for id=691911 (err=0)
          FixOrphanedFiles: Created thread record for id=691913 (err=0)
          FixOrphanedFiles: Created thread record for id=691915 (err=0)
          FixOrphanedFiles: Created thread record for id=691917 (err=0)
          FixOrphanedFiles: Created thread record for id=743120 (err=0)
          FixOrphanedFiles: Created thread record for id=743357 (err=0)
          FixOrphanedFiles: Created thread record for id=743358 (err=0)
          FixOrphanedFiles: Created thread record for id=743359 (err=0)
          FixOrphanedFiles: Created thread record for id=743360 (err=0)
          FixOrphanedFiles: Created thread record for id=743361 (err=0)
          FixOrphanedFiles: Created thread record for id=743362 (err=0)
          FixOrphanedFiles: Created thread record for id=743363 (err=0)
          FixOrphanedFiles: Created thread record for id=741510 (err=0)
          FixOrphanedFiles: Created thread record for id=741522 (err=0)
          FixOrphanedFiles: Created thread record for id=741523 (err=0)
          FixOrphanedFiles: Created thread record for id=691884 (err=0)
          FixOrphanedFiles: Created thread record for id=742221 (err=0)
          FixOrphanedFiles: Created thread record for id=742785 (err=0)
          FixOrphanedFiles: Created thread record for id=742253 (err=0)
          FixOrphanedFiles: Created thread record for id=742813 (err=0)
          FixOrphanedFiles: Created thread record for id=742213 (err=0)
          FixOrphanedFiles: Created thread record for id=742214 (err=0)
          FixOrphanedFiles: Created thread record for id=742215 (err=0)
          FixOrphanedFiles: Created thread record for id=742216 (err=0)
          FixOrphanedFiles: Created thread record for id=742841 (err=0)
          FixOrphanedFiles: Created thread record for id=742869 (err=0)
          FixOrphanedFiles: Created thread record for id=742925 (err=0)
          FixOrphanedFiles: Created thread record for id=742449 (err=0)
          FixOrphanedFiles: Created thread record for id=742897 (err=0)
          FixOrphanedFiles: Created thread record for id=743009 (err=0)
          FixOrphanedFiles: Created thread record for id=743037 (err=0)
          FixOrphanedFiles: Created thread record for id=743065 (err=0)
          FixOrphanedFiles: Created thread record for id=742218 (err=0)
          FixOrphanedFiles: Created thread record for id=743093 (err=0)
          FixOrphanedFiles: Created thread record for id=742309 (err=0)
          FixOrphanedFiles: Created thread record for id=742981 (err=0)
          FixOrphanedFiles: Deleted thread record for id=691886 (err=0)
          FixOrphanedFiles: Created thread record for id=691903 (err=0)
          FixOrphanedFiles: Created thread record for id=741414 (err=0)
          FixOrphanedFiles: Created thread record for id=741420 (err=0)
          FixOrphanedFiles: Created thread record for id=741429 (err=0)
          FixOrphanedFiles: Created thread record for id=741435 (err=0)
          FixOrphanedFiles: Created thread record for id=741432 (err=0)
          FixOrphanedFiles: Created thread record for id=741444 (err=0)
          FixOrphanedFiles: Created thread record for id=741438 (err=0)
          FixOrphanedFiles: Created thread record for id=741459 (err=0)
          FixOrphanedFiles: Created thread record for id=741441 (err=0)
          FixOrphanedFiles: Created thread record for id=741450 (err=0)
          FixOrphanedFiles: Created thread record for id=741426 (err=0)
          FixOrphanedFiles: Created thread record for id=741465 (err=0)
          FixOrphanedFiles: Created thread record for id=741453 (err=0)
          FixOrphanedFiles: Created thread record for id=741492 (err=0)
          FixOrphanedFiles: Created thread record for id=741456 (err=0)
          FixOrphanedFiles: Created thread record for id=741462 (err=0)
          FixOrphanedFiles: Created thread record for id=741468 (err=0)
          FixOrphanedFiles: Created thread record for id=741471 (err=0)
          FixOrphanedFiles: Created thread record for id=741447 (err=0)
          FixOrphanedFiles: Created thread record for id=741474 (err=0)
          FixOrphanedFiles: Created thread record for id=741417 (err=0)
          FixOrphanedFiles: Created thread record for id=741477 (err=0)
          FixOrphanedFiles: Created thread record for id=741480 (err=0)
          FixOrphanedFiles: Created thread record for id=741483 (err=0)
          FixOrphanedFiles: Created thread record for id=741489 (err=0)
          FixOrphanedFiles: Created thread record for id=741486 (err=0)
          FixOrphanedFiles: Created thread record for id=741498 (err=0)
          FixOrphanedFiles: Created thread record for id=741504 (err=0)
          FixOrphanedFiles: Created thread record for id=741507 (err=0)
          FixOrphanedFiles: Created thread record for id=741423 (err=0)
          FixOrphanedFiles: Created thread record for id=741495 (err=0)
          FixOrphanedFiles: Deleted thread record for id=740809 (err=0)
          FixOrphanedFiles: Deleted thread record for id=740810 (err=0)
          FixOrphanedFiles: Deleted thread record for id=740811 (err=0)
          FixOrphanedFiles: Deleted thread record for id=740812 (err=0)
          FixOrphanedFiles: Deleted thread record for id=740813 (err=0)
          FixOrphanedFiles: Deleted thread record for id=740814 (err=0)
          FixOrphanedFiles: Deleted thread record for id=740815 (err=0)
          FixOrphanedFiles: Deleted thread record for id=740816 (err=0)
          FixOrphanedFiles: Deleted thread record for id=740817 (err=0)
          FixOrphanedFiles: Deleted thread record for id=740826 (err=0)
          FixOrphanedFiles: Deleted thread record for id=740827 (err=0)
          FixOrphanedFiles: Deleted thread record for id=740828 (err=0)
          FixOrphanedFiles: Deleted thread record for id=740829 (err=0)
          FixOrphanedFiles: Deleted thread record for id=740830 (err=0)
          FixOrphanedFiles: Deleted thread record for id=740925 (err=0)
          FixOrphanedFiles: Deleted thread record for id=740926 (err=0)
          FixOrphanedFiles: Deleted thread record for id=740927 (err=0)
          FixOrphanedFiles: Deleted thread record for id=740928 (err=0)
          FixOrphanedFiles: Deleted thread record for id=740929 (err=0)
          FixOrphanedFiles: Deleted thread record for id=740930 (err=0)
          FixOrphanedFiles: Deleted thread record for id=740931 (err=0)
          FixOrphanedFiles: Deleted thread record for id=740932 (err=0)
          FixOrphanedFiles: Deleted thread record for id=740933 (err=0)
          FixOrphanedFiles: Deleted thread record for id=740934 (err=0)
          FixOrphanedFiles: Deleted thread record for id=740935 (err=0)
          FixOrphanedFiles: Created thread record for id=741405 (err=0)
          FixOrphanedFiles: Created thread record for id=741406 (err=0)
          FixOrphanedFiles: Created thread record for id=741402 (err=0)
          FixOrphanedFiles: Created thread record for id=741403 (err=0)
          FixOrphanedFiles: Created thread record for id=741401 (err=0)
          FixOrphanedFiles: Created thread record for id=741407 (err=0)
          FixOrphanedFiles: Created thread record for id=741404 (err=0)
          FixOrphanedFiles: Created thread record for id=741408 (err=0)
          FixOrphanedFiles: Created thread record for id=741409 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743563 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743564 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743565 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743566 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743567 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743568 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743569 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743570 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743571 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743572 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743573 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743574 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743575 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743576 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743577 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743578 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743579 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743580 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743581 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743582 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743583 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743584 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743585 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743586 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743587 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743588 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743589 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743590 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743591 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743592 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743593 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743594 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743595 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743596 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743597 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743598 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743599 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743600 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743601 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743602 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743603 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743604 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743605 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743606 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743607 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743608 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743609 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743610 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743611 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743612 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743613 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743614 (err=0)
          FixOrphanedFiles: Deleted thread record for id=743615 (err=0)
          FixOrphanedFiles: Deleted thread record for id=756412 (err=0)
          FixOrphanedFiles: Deleted thread record for id=782888 (err=0)
          FixOrphanedFiles: Deleted thread record for id=2049005 (err=0)
          FixOrphanedFiles: Deleted thread record for id=8863256 (err=0)
** Rechecking volume.
** Checking Journaled HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
   Missing thread record (id = 691886)
   Missing thread record (id = 2049005)
   Incorrect number of thread records
(4, 23903)
          CheckCatalogBTree: dirCount = 140939, dirThread = 140941
** Checking multi-linked files.
** Checking Catalog hierarchy.
   Invalid directory item count
   (It should be 0 instead of 25)
   Invalid directory item count
   (It should be 0 instead of 25)
   Invalid directory item count
   (It should be 0 instead of 25)
   Invalid directory item count
   (It should be 0 instead of 25)
   Invalid directory item count
   (It should be 0 instead of 25)
   Invalid directory item count
   (It should be 0 instead of 25)
   Invalid directory item count
   (It should be 0 instead of 25)
   Invalid directory item count
   (It should be 0 instead of 25)
   Invalid directory item count
   (It should be 0 instead of 25)
   Invalid directory item count
   (It should be 0 instead of 25)
   Invalid directory item count
   (It should be 0 instead of 25)
   Invalid directory item count
   (It should be 0 instead of 25)
   Invalid directory item count
   (It should be 0 instead of 25)
   Invalid directory item count
   (It should be 0 instead of 25)
   Invalid volume file count
   (It should be 701653 instead of 701678)
** Checking Extended Attributes file.
   Invalid map node
(8, 0)
** Checking volume bitmap.
** Checking volume information.
   Verify Status: VIStat = 0x0000, ABTStat = 0x4000 EBTStat = 0x0000
                  CBTStat = 0x0800 CatStat = 0x00004200
** Repairing volume.
   Missing directory record (id = 2049005)
   Missing directory record (id = 691886)
** Look for missing items in lost+found directory.
** Rechecking volume.
** Checking Journaled HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
** Checking multi-linked files.
** Checking Catalog hierarchy.
** Checking Extended Attributes file.
** Checking volume bitmap.
** Checking volume information.
   Invalid volume file count
   (It should be 701678 instead of 701653)
   Verify Status: VIStat = 0x8000, ABTStat = 0x0000 EBTStat = 0x0000
                  CBTStat = 0x0000 CatStat = 0x00000000
** The volume MACINTOSH HD could not be repaired after 3 attempts.
          volume type is pure HFS+
          primary MDB is at block 0 0x00
          alternate MDB is at block 0 0x00
          primary VHB is at block 2 0x02
          alternate VHB is at block 975093950 0x3a1ec0be
          sector size = 512 0x200
          VolumeObject flags = 0x07
          total sectors for volume = 975093952 0x3a1ec0c0
          total sectors for embedded volume = 0 0x00
fadil-shamir-khans-mac-mini:~ silentarts$
After all of that was done, I am now able to go back to Disk Utility and Completely Verify My Disk.
What should my next step be? Should I try booting to Mavericks from that hard drive or should I try to Repair the Disk?

I upgraded to Mavericks, and had a "grey screen of death" when re-booting for the first time. Re-setting the PRAM fixed it for me. Worth a try:
http://support.apple.com/kb/ph14222

Mac Pro early 2009 won't boot after running 1.8.2 update

It even does not get into recovery mode. A grey screen with dots appear.

Hold down the Option key at Startup. This invokes the Startup Manager, whose code is all in ROM. It will then draw an Icon for each potentially bootable drive.
If there are defects on the screen during this process, you probably have a Hardware problem.

Xserve early 2009 won't Boot

My Xserve early 2009 won’t Boot , No Video , Activity LEDs Flashing :
Xserve begins to power up but does not boot
Fan array and hard drive are spinning
Power LED is illuminated
Top row of activity lights flash
No video on external display
My server was stored in the original box for 12 months now, when I reuse it, he presented the above problems
Anyone know how to fix this?

Thank you, Khashoggi. Reseating the ADM's did generate a different result in Disk Utility. The mirror had a state of "degraded" after reseating because one of the drives had an error. I began a rebuild but it was set to take 4 hours so I just re-built the mirror and re-installed the OS. I would have let it rebuild but it was a brand new instal; no configuration done at all so it was much quicker to just reinstall.
I've got the machine back to the state it was in before the issue and I've created both a Time Machine and Carbon Copy Clone backup of the System in case of further issues.
Thanks again!

Will not boot after moving Journal

I did this on a test system so the fact that it didn't work isn't so big of a deal, but I'd like to get it working.
I ran through the steps outlined in Apple's own KB as well as the article on AFP548 to move the journal of my boot volume to the ssd in our new late-2009 xserve
http://support.apple.com/kb/HT3790
When rebooting the system hangs for many minutes at the apple log with spinning gear. Eventually it just throws up the ? folder and sits there. I've been able to undo the journal move back to the boot volume which makes for some good recovery practice, but as I said I'd like to know what I'm doing wrong.
I have my raid0 volume and the ssd called just that, ssd. I give the following commands;
diskutil moveJournal external /Volumes/ssd /Volumes/raid0
It unmounts the ssd drive to copy it over and succeeds, but after rebooting it does nothing.
Thanks

I did this on a test system so the fact that it didn't work isn't so big of a deal, but I'd like to get it working.
I ran through the steps outlined in Apple's own KB as well as the article on AFP548 to move the journal of my boot volume to the ssd in our new late-2009 xserve
http://support.apple.com/kb/HT3790
When rebooting the system hangs for many minutes at the apple log with spinning gear. Eventually it just throws up the ? folder and sits there. I've been able to undo the journal move back to the boot volume which makes for some good recovery practice, but as I said I'd like to know what I'm doing wrong.
I have my raid0 volume and the ssd called just that, ssd. I give the following commands;
diskutil moveJournal external /Volumes/ssd /Volumes/raid0
It unmounts the ssd drive to copy it over and succeeds, but after rebooting it does nothing.
Thanks

IMac 27' i5 late 2009 don't boot.

My iMac 27' late 2009 don't boot, the screen become grey with only the Apple's logo.
He can boot on the USB Lion installer but not on installed system.
When I want to re-install the system, the screen become black after some minutes.
I've tried to reset the SMS, the PRAM/NVRAM, to change the HDD, to make fsck, to repair the disk with disk warrior and disk utility, to change the RAM memory...
HELP !
Max.
PS : I've made an AHT but all is OK.

iCoppa wrote:
I'm having the same problem. What software do you have installed (Aside from ilife and OSX) ?
Hello, basically my software are:
Aperture 2
Fusion 3
Microsoft Office 2004 (and most of the time word crashes as soon as it's started)
Firefox 3.6
Qpict 7.1
Adium 1.3.6
plus other software that I use sporadically (muCommander, Filezilla).
I connect to several external hard drives, I use cisco vpn client and >Microsoft RDP client often. If I can't find any helpful information I'm going >to start removing things 1 by one until I figure this crap out.
Well, during the past weekend, the possibility that the bug maybe caused by Firewire devices is dramatically increased. If it's true, the problem effect Snow Leopard in general and not only the iMac.
Yesterday I connect my MacBookPro 2.2 (3GB RAM 10.6.2) to the external devices (one Packard Bell 250GB FW-400 connected to one Lacie 1TB FW-800) because I had to move several files from one disk to the other (procedure that I've started with the iMac and never completed).... well the 4 year old MBP that never had a problem, crashed completely three times!! :O
The first time the spinning ball appeared (same bug behavior as on the iMac), the second time the mouse stopped to move and the last one (I had the screen dimmed) the screen remained black.
I'm really starting to think that something at kernel level that handle firewire devices has some severe issues if some particular conditions happens.

Windows 8.1 Pro not booting after install of Hyper V - ASUS z87 + intel 4670K

Hi,
I am running windows 8.1 pro on a intel 4670K 4th Gen Haswell CPU and ASUS z87 plus motherboard. 16gb of kingston hyperx ddr1600 memory.
I have enabled virtualisation technology in the bios. CPU has SLAT.... or Extended Page Table, as intel likes to refer to it.
When I install HyperV platform and management tools the computer configures and reboots
AFter reboot it brings up the blue window image and spinning circle of dots for a while then reboots. It does the same thing again and then reboots and goings into repair mode and asks me to do a system restore. It then restores to before they HyperV install.
I've tried turning off xHCI mode (i.e USB 3.0) in the bios as this seemed to be a known issue with some gigabyte boards. This did not rectify the issue
Updated to latest asus mainboard bios 1405. Same issue still occurs upon install of hyper V.
Automatic repair does not work and I have to restore from system restore point.
I performed a clean boot after installing the feature and it still couldnt boot to windows.. it just sits at windows logo and then restarts a few times and then launches the startup repair. Once the startup repair begins, the only way I can get into windows
is restoring to a system restore point from before the hyperv feature install.
Please see the following logs which may have further information:
CBS Log
https://skydrive.live.com/redir?resid=1F523A0B8734322C!685&authkey=!AGMjUfosLFpzYNI
Setuperr
https://skydrive.live.com/redir?resid=1F523A0B8734322C!682&authkey=!AKS8Jb1S6W2IAH8
Windows update
https://skydrive.live.com/redir?resid=1F523A0B8734322C!683&authkey=!AJdWKuKj4negBoQ
Windowsupdate(1)
https://skydrive.live.com/redir?resid=1F523A0B8734322C!684&authkey=!APplVjuLpNZW_AY
I logged a job with asus support and their response was:
"Clear CMOS and ensure virtualisation technology is turned on in BIOS. If it still doesn't work, seek assistance from Microsoft"
Previously asked this question but took a while to get back to update with the logs and it was listed as Answered.
This issue is still existing and I'd appreciating any assistance.
Simon

Hi Simon,
Thank you for uploading the Log files.
According to the log files, no actuate clue can be found.
So, I suggest you upload the dump file so that we can help you analyze them.
Automatic Memory Dump Settings on Windows 8:
http://www.thewindowsclub.com/automatic-memory-dump-settings-windows-8
It also applies to windows 8.1.
Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
Note: I highly recommend you use SkyDrive to upload collected files and to post screen shots/pictures. Although you might not be used to it, SkyDrive features a lot of free advanced functionality around file storage capacity, sharing,
privacy, and collaboration:
http://skydrive.com
Regards,
Kelvin hsu
TechNet Community Support

[Solved] Unable to boot after install

Forgive me for the lack of code tags, having to write this on my phone.
I am unable to boot after installation. I receive an error wich has the incorrect UDID string. It doesn't even exist. I will update with error after posting so I can give grub config generation error first
When I run:
grub-mkconfig -o /boot/grub/grub.cfg
I get this:
Found Linux image : /boot/vmlinuz-linux
Found initd image: /boot/initramfs-linux.img
Warning: failed to connect to lvmetad: no such file or directory. falling back to internal scanning.
No volume groups found
[ 279.601712] SQUASHFS error: can't find a SQUASHFS superblock on sda3
[ 279.604502] EXT4-fs (sda3):unable to read superblock
[ 279.607266] EXT4-fs (sda3):unable to read superblock
[ 279.609928] EXT4-fs (sda3):unable to read superblock
Found Windows 7 (loader) on /dev/sda1
Done
Sda3 is an extended volume
Edit: I just deleted the old .cfg and recreated a new one by re running the above command, uncounted and rebooted and it booted into CLI. 3rd time a charm after all. Marking this one solved
Last edited by Kirito (2013-05-15 07:55:31)

Oh, looking at your setup, it would seem that your system is likely still configured to boot to /dev/sdd (the windows drive).
As a user with numerous drives, you should be aware that using /dev/sdXY to identify your disks is a bad idea. There is no gaurantee that Arch will be /dev/sde every time, nor that windows will be /dev/sdd. You should use either filesystem labels (LABEL= or /dev/disk/by-label) or UUIDs (UUID= or /dev/disk/by-uuid). Though if you are using GPT, there is also the option of the PARTLABEL as well (which are the labels you create within the partitioner).

How to auto boot after shutting down bootcamp Windows?

I have an instructional lab of 30 20" imacs that are running dual-boot, 10.5 & XP SP3. They have bootpicker installed to simplify the selection of which OS to boot to and auto-select Windows at 60 sec. (This is for new computer users and English as a second language users that are not familiar with the dual-boot setups.)
In both OS's we run deepfreeze to protect the configurations from change. I have set the Energy Saver settings in the Mac OS to start or wake at 7am weekdays. Deepfreeze for Windows is set to shut off the Macs at 10PM. This is also set by Deepfreeze in the Mac OS but since they primarily run Windows in this classroom the Mac's are shut down from the Windows side.
After making the auto start setting and shutting them down from Windows once they will no longer auto start the next day or ever again after that. I have tried using pmset to remedy this and have tossed the plist for the settings numerous times. Same thing every time. One auto boot and then none after. I would use a script from ARD to wake them but they are not in the same subnet as my ARD setup and my network group will not configure our switching to allow for it.
Does anyone know how to make the Macs boot consistently, automatically, every day I wish them to boot after being shut down from Windows by Deepfreeze.

Supply pertinent information for quicker answers
The more information you supply about your situation, the better equipped other community members will be to answer. Consider including the following in your question:
Adobe product and version number
Operating system and version number
The full text of any error message(s)
What you were doing when the problem occurred
Screenshots of the problem
Computer hardware, such as CPU; GPU; amount of RAM; etc.

Boot data configuration missing or with errors

I have a Satelllite L870-15W, and no way to turn the system on.
All it says is "Toshiba" (the welcome screen) and then (after having pressed f8 or f9):
file: efi/micorsoft/boot/bcd,
status 0x0000001;
the boot configuration data for your or is missing or contains errors.
I have only recovery partition at D: but cannot access it. What shall I do?

Satellite L870-15W (PSKFNE-00700CHU) <- Hungarian version
Spec here too.
boot data configuration missing or with errors
It probably means the BCD is missing or corrupt.
To repair this, you need to access the recovery environment. Microsoft says Windows 8 will eventually take you there if it fails to boot many times. You can also get there using a System Repair Disc or a Windows 8 installation DVD like this downloadable one. You need the 64-bit disc.
It's possble this will also work on your Toshiba machine. Restart the computer by pressing the power button and immediately start tapping the F12 key until the Boot Menu appears. Using the arrow keys, select <HDD Recovery>.
WinRE looks like this. Select Troubleshoot and then Advanced options.
Lots of things to try. See KB2622803 for boot sector problems. The article assumes Windows Vista/7. The same fixes look different in Windows 8, but are all available.
If Automatic Repair (Startup Repair in 8.1) and System Restore fail, use the bootrec tool at the command prompt. This applies to Windows 8 also.
   Use the Bootrec.exe tool in the Windows Recovery Environment to troubleshoot and repair startup issu...
Don't give up until you have tried replacing the BCD itself as follows. (Sometimes the partition is not named "c" and you need to try another letter.)
   c:
   cd boot
   attrib bcd -s -h -r
   ren c:\boot\bcd bcd.old
   bootrec /RebuildBcd
-Jerry

Fresh install of solaris 10 x86 hangs after 'Configuring devices'

Hi All,
I just received a new SuperMicro server with an LSI MegaRAID SAS 9261-8i controller. While trying to install Solaris 10 it hangs after "Configuring devices". I checked the LSI page and Solaris 10 is supported according to them. Any ideas how to proceed?
Fairly new to Solaris on x86 hardware.
The system has a Xeon X5690 processor in an Intel Workstation Board S5520SC motherboard. The motherboard documents claim that not disabling usb 2.0 can hang an install. I have disabled the usb 2.0 in the bios but the system still hangs. Booting it with the -kd and -kv options don't give much information.
Any help is appreciated. I might be returning these machines if I can't get this worked out.
Cheers,
Steve
Edited by: 967729 on Oct 25, 2012 3:51 PM

See if you can add the verbose option "-v" to the kernel boot options. I think you can get to the GRUB menu off the Solaris 10 install disk. That should tell you what device is causing the hang, or at least the last device that worked.
Also, can you try Solaris 11 and see if it gets past that point? A few years ago I has a similar issue with Solaris 10 on a Dell server. Solaris 11/OpenSolaris worked fine, though. IIRC I could work around the issue if I disabled the 2nd CPU - Solaris 10 had a problem bringing up the 2nd CPU on that Dell's CPU/MB config.

Imac late 2009 do not boot

Hello ,
my iMac24 late 2009 doesn't boot normally , only in safe mode .
After that everything works fine but no audio or cam , I've done a clean install of OSX 10.7.5 without any problem ( audio and cam working during the install process ) but once arrived to the screen " .. and now start enjoying Lion .." the screen stopped on a mix of the login screen and the desktop Andromeda Galaxy wallpaper ...
When I start from the off condition it works and the scene shows the spinning icon , but after the mouse pointer shows up I get only a blank screen and the HD makes its usual noise in the background like it's working or defraying .
Please help , many thanks ,
moritz58

Disconnect all devices from the computer then do the following:
Boot up from your system DVD that originally came w/your comp while holding down the "c" key.
Select the language you wish to use, and then choose "Disk Utility" from the menu bar.
Your HD should appear in a panel on the left hand side of the window which opens. Select it and then click on the "repair disk" button in the right hand section of the window.
Once this process has been completed restart your computer and repair permissions directly from Disk Utility.
If Disk Utility is unable to complete the repair, you will need to use a stronger 3rd party utility like DiskWarrior, Techtool PRO (not Deluxe) or Drive Genius.
====================
http://support.apple.com/kb/TS2570 Mac OS X: Gray screen appears during startup

What is a neat way to delete a stale amavisd pid_file on first boot after panic or power failure?

Lion Mail Server component postfix/smtp 100% reproducible blocks inbound smtp mail delivery on first boot after a panic or power failure.
Error messages from mail.log are like:
postfix/smtp[45785]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused postfix/smtp[45785]: 2F7131F9A97: to=<[email protected]>, relay=none, delay=76041, delays=76040/0.36/0.05/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused) postfix/error[45790]: 550D61F9A99: to=<[email protected]>, relay=none, delay=76040, delays=76040/0.39/0/0, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused) postfix/postscreen[45872]: NOQUEUE: reject: RCPT from [100.200.100.159]:65392: 450 4.3.2 Service currently unavailable; from=<[email protected]>, to=<[email protected]>, proto=ESMTP, helo=<host.domain.tld> /usr/libexec/postfix/greylist.pl[45885]: Temporary message rejection to: <[email protected]> from: <[email protected]> sent from: [100.200.100.159] for: 60 seconds due to greylisting postfix/smtpd[45879]: NOQUEUE: reject: RCPT from host.domain.tld[100.200.100.159]: 450 4.7.1 <[email protected]>: Recipient address rejected: Service is unavailable; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<host.domain.tld>
The issue seems to be related to the amavis content filter due to the connection to port number 10024 and amavisd being configured on that port. Amavis.log:
/usr/bin/amavisd[236]: (!)Net::Server: 2012/07/25-13:38:49 Pid_file already exists for running process (88)... aborting\n\n at line 277 in file /System/Library/Perl/Extras/5.12/Net/Server.pm ... /usr/bin/amavisd[236]: Net::Server: 2012/07/25-13:38:49 Server closing! ...repeating roughly every 10 seconds...
The workaround is to reboot the machine, after the second boot the inbound smtp mail delivery is no longer stuck.
The issue seems to be related to http://serverfault.com/questions/138690/amavisd-net-server-pid-file-already-exis ts-after-system-crash-and-startup
How to permanently fix Apple Mail Server to accept smtp inbound messages on first boot, by removing the left over amavis pid_file from the previous unclean shutdown?

Use connection pooling. This will put the connection management in the hands of the webserver, not your code. Check out this post:
http://forum.java.sun.com/thread.jspa?threadID=741788&messageID=4252932#4252932

Mac pro OS X 10.6 Snow Leopard won't boot after software up-date

I am new to Apple/Mac products. I recently bought an iPad and liked it so much mt epiphany was that this must be why Mac users are so loyal to Apple products. So I bought a used Mac Pro on EBAY, received the unit in good condition, set it up and booted. after I got it online I discovered it was due for a software update. No problem. I followed the software update icon, downloaded 4 updates and began the 2 hour download. When the download completed I clicked to install and left the room. when I returned the screen was blank. I grabbed the mouse in an attempt to "wake it up". The fans kicked on and it sounded like a jet taking off bot the screen remained blank. It has not booted since. Any ideas on how to recover?

Me: bought off ebay? then take the DVD OEM discs and clean system install.
Upper right corner "About this Mac..." More.... takes you to System Profiler.
Top lines of what model etc. do not include serial number but you might want to call and / or check that too and order replacement DVDs if it didn't have those.
but for now, Wipe the drive.
You can backup first if you want.
Utility folder: Disk Utility: Restore: allow drag and drop the source and target.
www.macupdate.com "backup programs" I recommend Carbon Copy Cloner to maintain bootable backups and can also archive changes. Similar to what Paragon Manager Suite offers in Clone OS to SSD.
Boot from the OS X DVD it should have come with. Choose the Utilities from menu bar : Disk Utility to repair or format. Then go back and Install OS X.
Using Cloning as a Backup Strategy
http://www.macupdate.com/app/mac/7032/carbon-copy-cloner
http://www.bombich.com/software/updates/ccc-3.5.htmlOS X Lion Install to Different DriveHow to create an OS X Lion installation disc MacFixItMigration Assistant Update for Mac OS X Snow Leopard
http://www.apple.com/support/lion/installrecovery/ Create an OS X Lion Install dischttp://reviews.cnet.com/8301-13727_7-20080989-263/how-to-create-an-os-x-lion-ins tallation-disc
How to clone your system:http://macperformanceguide.com/Mac-HowToClone-backup.htmlhttp://macperformanceguide.com/Mac-HowToClone.htmlhttp://www.macupdate.com/app/mac/7032/carbon-copy-clonerhttp://www.macperformanceguide.com/blog/2012/20120711_2-MacPro-internal-clone-ba ckup.html
Mac OS X Help
Isolating Issues in Mac OShttp://support.apple.com/kb/TS1388
https://www.apple.com/support/osx/https://www.apple.com/support/quickassist/http://www.apple.com/support/mac101/help/http://www.apple.com/support/mac101/tour/
Get Help with your Product
http://docs.info.apple.com/article.html?artnum=304725
TimeMachine 101 https://support.apple.com/kb/HT1427
Mac OS X & Mountain Lion Communityhttps://discussions.apple.com/community/mac_oshttps://discussions.apple.com/community/mac_os/os_x_mountain_lion?view=discussio ns
Recovery Modehttp://support.apple.com/kb/HT4718
reset SMC For "Mac wont' turn on or boot" and relatedhttps://support.apple.com/kb/TS1367
General purpose Mac troubleshooting guide: Isolating issues in Mac OS XCreating a temporary user to isolate user-specific problems: Isolating an issue by using another user accountIdentifying resource hogs and other tips: Using Activity Monitor to read System Memory and determine how much RAM is being usedStarting the computer in "safe mode": Mac OS X: What is Safe Boot, Safe Mode?To identify potential hardware problems: Apple Hardware TestGeneral Mac maintenance: Tips to keep your Mac in top form
First, if at all possible make a backup of the drive in its present configuration. If something goes wrong during repair attempts and makes things worse you will have a backup. You will have to decide how to work this in the light of any present backups you may have, for example, a backup that may be a few days out of date. In that case you may want to keep that one and make a second backup of this as they are now, though I realize people often don't have a lot of empty drives sitting around.
Boot from the System Installer disc that came with your computer or is the one for the version you currently have on there, select language if applicable, choose utilities, run Disk Utility and verify (and repair if necessary) the drive. You can verify a drive from DU on your main drive while booted but I have found this can result in incorrect reporting of errors. To repair your drive you have to run it from a drive other than the boot drive anyway. Next, boot from your drive in Safe Mode (http://docs.info.apple.com/article.html?artnum=107393) and repair permissions. You can repair permissions while booted from the installer disc but this uses the permissions configuration on the installer disc which may be out of date if you have run any updates on your computer. Booting your computer to Safe Mode restricts the number of things running on your computer while permissions are being run and does a bit of spring cleaning at the same time.
Reading
Resolve startup issues and perform disk maintenance with Disk Utility and fsck - http://docs.info.apple.com/article.html?artnum=106214Using Disk Utility in Mac OS X 10.4.3 or later - http://docs.info.apple.com/article.html?artnum=302672Disk Utility's Repair Disk Permissions 10.0-10.6 - http://docs.info.apple.com/article.html?artnum=25751"Try Disk Utility" (modified from http://support.apple.com/kb/TS1417)
1. Insert the Mac OS X Install disc that came with your computer (Edit: Do not use this disc if it is not the same general version as what you have currently on your computer, e.g. use a Tiger disc for a Tiger drive, not a Panther disc), then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.
3. Click the First Aid tab.
4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
5. Select your Mac OS X volume.
6. Click Repair. Disk Utility checks and repairs the disk."

2009 Xserve no boot after configuring LOM

Similar Messages

Maybe you are looking for