Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.mac.system > #63105 > unrolled thread

10.6 no longer boots.

Back to article view | Back to comp.sys.mac.system

Contents

  10.6 no longer boots. Siri Crews <chine.bleu@yahoo.com> - 2014-08-08 21:36 -0700
    Re: 10.6 no longer boots. Jolly Roger <jollyroger@pobox.com> - 2014-08-09 15:37 +0000
    Re: 10.6 no longer boots. Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2014-08-09 11:20 -0700
      Re: 10.6 no longer boots. Siri Crews <chine.bleu@yahoo.com> - 2014-08-09 17:20 -0700
        Re: 10.6 no longer boots. Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2014-08-09 22:31 -0700
          Re: 10.6 no longer boots. Siri Crews <chine.bleu@yahoo.com> - 2014-08-10 11:35 -0700
            Re: 10.6 no longer boots. Jolly Roger <jollyroger@pobox.com> - 2014-08-10 18:50 +0000
              Re: 10.6 no longer boots. Siri Crews <chine.bleu@yahoo.com> - 2014-08-10 11:53 -0700
                Re: 10.6 no longer boots. Jolly Roger <jollyroger@pobox.com> - 2014-08-10 18:55 +0000
            Re: 10.6 no longer boots. FPP <fredp151@gmail.com> - 2014-08-10 15:09 -0400
              Re: 10.6 no longer boots. Siri Crews <chine.bleu@yahoo.com> - 2014-08-10 12:24 -0700
                Re: 10.6 no longer boots. FPP <fredp151@gmail.com> - 2014-08-10 21:26 -0400
              Re: 10.6 no longer boots. Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2014-08-10 19:30 -0700
                Re: 10.6 no longer boots. nospam <nospam@nospam.invalid> - 2014-08-10 22:36 -0400
                  Re: 10.6 no longer boots. FPP <fredp151@gmail.com> - 2014-08-11 01:43 -0400
                  Re: 10.6 no longer boots. nmassello@yahoo.com (Neill Massello) - 2014-08-11 09:54 -0600
                    Re: 10.6 no longer boots. nospam <nospam@nospam.invalid> - 2014-08-11 12:12 -0400
                    Re: 10.6 no longer boots. FPP <fredp151@gmail.com> - 2014-08-11 15:49 -0400
                      Re: 10.6 no longer boots. Your Name <YourName@YourISP.com> - 2014-08-12 09:21 +1200
                        Re: 10.6 no longer boots. FPP <fredp151@gmail.com> - 2014-08-11 18:32 -0400
                          Re: 10.6 no longer boots. Jolly Roger <jollyroger@pobox.com> - 2014-08-11 23:17 +0000
                            Re: 10.6 no longer boots. FPP <fredp151@gmail.com> - 2014-08-11 23:28 -0400
                              Re: 10.6 no longer boots. Your Name <YourName@YourISP.com> - 2014-08-12 16:14 +1200
                                Re: 10.6 no longer boots. FPP <fredp151@gmail.com> - 2014-08-12 01:40 -0400
                                Re: 10.6 no longer boots. Fred Moore <fmoore@gcfn.org> - 2014-08-12 14:21 -0400
                                  Re: 10.6 no longer boots. Your Name <YourName@YourISP.com> - 2014-08-13 09:16 +1200
                          Re: 10.6 no longer boots. Your Name <YourName@YourISP.com> - 2014-08-12 13:26 +1200
                            Re: 10.6 no longer boots. nospam <nospam@nospam.invalid> - 2014-08-11 21:35 -0400
                            Re: 10.6 no longer boots. FPP <fredp151@gmail.com> - 2014-08-11 23:31 -0400
                              Re: 10.6 no longer boots. Your Name <YourName@YourISP.com> - 2014-08-12 16:12 +1200
                                Re: 10.6 no longer boots. nospam <nospam@nospam.invalid> - 2014-08-12 00:31 -0400
                                Re: 10.6 no longer boots. FPP <fredp151@gmail.com> - 2014-08-12 01:40 -0400
                                  Re: 10.6 no longer boots. Your Name <YourName@YourISP.com> - 2014-08-12 17:57 +1200
                                    Re: 10.6 no longer boots. nospam <nospam@nospam.invalid> - 2014-08-12 02:54 -0400
                                    Re: 10.6 no longer boots. FPP <fredp151@gmail.com> - 2014-08-12 03:14 -0400
                    Re: 10.6 no longer boots. nmassello@yahoo.com (Neill Massello) - 2014-10-16 22:46 -0600
                      Re: 10.6 no longer boots. nospam <nospam@nospam.invalid> - 2014-10-17 01:09 -0400
                        Re: 10.6 no longer boots. FPP <fredp151@gmail.com> - 2014-10-17 02:35 -0400
                          Re: 10.6 no longer boots. FPP <fredp151@gmail.com> - 2014-10-17 02:48 -0400
                            Re: 10.6 no longer boots. Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-10-18 01:42 +0000
                        Re: 10.6 no longer boots. nmassello@yahoo.com (Neill Massello) - 2014-10-17 01:45 -0600
                          Re: 10.6 no longer boots. FPP <fredp151@gmail.com> - 2014-10-17 06:27 -0400
                            Re: 10.6 no longer boots. nmassello@yahoo.com (Neill Massello) - 2014-10-17 08:14 -0600
                              Re: 10.6 no longer boots. nospam <nospam@nospam.invalid> - 2014-10-17 10:55 -0400
                                Re: 10.6 no longer boots. nmassello@yahoo.com (Neill Massello) - 2014-10-17 10:12 -0600
                                  Re: 10.6 no longer boots. nospam <nospam@nospam.invalid> - 2014-10-17 12:41 -0400
                                    Re: 10.6 no longer boots. nmassello@yahoo.com (Neill Massello) - 2014-10-18 12:25 -0600
                                      Re: 10.6 no longer boots. nospam <nospam@nospam.invalid> - 2014-10-18 14:49 -0400
                          Re: 10.6 no longer boots. nospam <nospam@nospam.invalid> - 2014-10-17 10:54 -0400
                            Re: 10.6 no longer boots. FPP <fredp151@gmail.com> - 2014-10-19 05:32 -0400
                Re: 10.6 no longer boots. Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-08-11 14:11 +0000
                Re: 10.6 no longer boots. Jolly Roger <jollyroger@pobox.com> - 2014-08-11 14:56 +0000
              Re: 10.6 no longer boots. nmassello@yahoo.com (Neill Massello) - 2014-08-11 09:54 -0600
                Re: 10.6 no longer boots. Jolly Roger <jollyroger@pobox.com> - 2014-08-11 16:25 +0000
                  Re: 10.6 no longer boots. Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2014-08-12 21:03 -0700
                    Re: 10.6 no longer boots. Jolly Roger <jollyroger@pobox.com> - 2014-08-13 15:10 +0000
                    Re: 10.6 no longer boots. Siri Crews <chine.bleu@yahoo.com> - 2014-08-13 09:52 -0700
                    Re: 10.6 no longer boots. FPP <fredp151@gmail.com> - 2014-08-13 14:37 -0400
                      Re: 10.6 no longer boots. Siri Crews <chine.bleu@yahoo.com> - 2014-08-13 11:50 -0700
                      Re: 10.6 no longer boots. Siri Crews <chine.bleu@yahoo.com> - 2014-08-13 11:51 -0700
                    Re: 10.6 no longer boots. nmassello@yahoo.com (Neill Massello) - 2014-08-14 10:17 -0600
                      Re: 10.6 no longer boots. Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2014-08-14 20:43 -0700
                Re: 10.6 no longer boots. George Kerby <ghost_topper@hotmail.com> - 2014-08-11 14:39 -0500
                  Re: 10.6 no longer boots. Jolly Roger <jollyroger@pobox.com> - 2014-08-11 23:15 +0000
                Re: 10.6 no longer boots. FPP <fredp151@gmail.com> - 2014-08-11 15:52 -0400
                  Re: 10.6 no longer boots. nmassello@yahoo.com (Neill Massello) - 2014-08-11 14:30 -0600
                    Re: 10.6 no longer boots. FPP <fredp151@gmail.com> - 2014-08-11 18:42 -0400
            Re: 10.6 no longer boots. Jolly Roger <jollyroger@pobox.com> - 2014-08-10 20:32 +0000
              Re: 10.6 no longer boots. Siri Crews <chine.bleu@yahoo.com> - 2014-08-10 14:25 -0700
                Re: 10.6 no longer boots. FPP <fredp151@gmail.com> - 2014-08-10 21:26 -0400
                Re: 10.6 no longer boots. Jolly Roger <jollyroger@pobox.com> - 2014-08-11 01:32 +0000
                  Re: 10.6 no longer boots. Siri Crews <chine.bleu@yahoo.com> - 2014-08-10 19:08 -0700

Page 1 of 4  [1] 2 3 4  Next page →

#63105 — 10.6 no longer boots.

Any ideas why a 10.6 partition would no longer boot? Disk Utility says it is 
bootable.

The kernel logs run

Darwin Kernel Version 10.8.0: Tue Jun  7 16:33:36 PDT 2011; 
root:xnu-1504.15.3~1/RELEASE_I386
vm_page_bootstrap: 949513 free pages and 25335 wired pages
standard timeslicing quantum is 10000 us
mig_table_max_displ = 73
AppleACPICPU: ProcessorId=0 LocalApicId=0 Enabled
AppleACPICPU: ProcessorId=1 LocalApicId=1 Enabled
calling mpo_policy_init for TMSafetyNet
Security policy loaded: Safety net for Time Machine (TMSafetyNet)
calling mpo_policy_init for Quarantine
Security policy loaded: Quarantine policy (Quarantine)
calling mpo_policy_init for Sandbox
Security policy loaded: Seatbelt sandbox policy (Sandbox)
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
MAC Framework successfully initialized
using 16384 buffer headers and 4096 cluster IO buffer headers
IOAPIC: Version 0x11 Vectors 64:87
ACPI: System State [S0 S3 S4 S5] (S3)
PFM64 0xf10000000, 0xf0000000
[ PCI configuration begin ]
console relocated to 0xf10010000
PCI configuration changed (bridge=3 device=1 cardbus=0)
[ PCI configuration end, bridges 6 devices 18 ]
AppleIntelCPUPowerManagement: (built 16:44:45 Jun  7 2011) initialization 
complete
mbinit: done (64 MB memory set for mbuf pool)
rooting via boot-uuid from /chosen: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
Waiting on <dict ID="0"><key>IOProviderClass</key><string 
ID="1">IOResources</string><key>IOResourceMatch</key><string 
ID="2">boot-uuid-media</string></dict>
com.apple.AppleFSCompressionTypeZlib kmod start
com.apple.AppleFSCompressionTypeZlib load succeeded
AppleIntelCPUPowerManagementClient: ready
BTCOEXIST off 
wl0: Broadcom BCM432b 802.11 Wireless Controller
5.10.131.42
FireWire (OHCI) Lucent ID XXXX built-in now active, GUID XXXXXXXXXXXXXXXX; max 
speed s800.
USBMSC Identifier (non-unique): XXXXXXXXXXXX 0xXXX 0xXXXX 0xXXXX

It used to continue with

Got boot device = 
IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@B/AppleXXXXXXXXX/PRT0
@0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDriv
er/Hitachi XXXXXXXXXXXXXXX Media/IOGUIDPartitionScheme/Untitled 1@2
BSD root: disk0s2, major 14, minor 1
jnl: unknown-dev: replay_journal: from: 3186688 to: 5646848 (joffset 0x1e5000)
...

But it now hangs

Still waiting for root device
Still waiting for root device
Still waiting for root device

-- 
:-<> Siri Seal of Disavowal #000-001. Disavowed. Denied. Deleted.
'I desire mercy, not sacrifice.'
Icke's razor: Given two equally plausible explanations, choose the weirder.

[toc] | [next] | [standalone]

#63107

On 2014-08-09, Siri Crews <chine.bleu@yahoo.com> wrote:
>
> Any ideas why a 10.6 partition would no longer boot? Disk Utility says it is 
> bootable.
>
> The kernel logs run
>
[snip]
>
> It used to continue with
>
> Got boot device = 
> IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@B/AppleXXXXXXXXX/PRT0
> @0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDriv
> er/Hitachi XXXXXXXXXXXXXXX Media/IOGUIDPartitionScheme/Untitled 1@2
> BSD root: disk0s2, major 14, minor 1
> jnl: unknown-dev: replay_journal: from: 3186688 to: 5646848 (joffset 0x1e5000)
> ...
>
> But it now hangs
>
> Still waiting for root device
> Still waiting for root device
> Still waiting for root device

I would first try resetting the PRAM:

<http://support.apple.com/kb/HT1379>

Next, I would try resetting the SMC/PMU (depending on which model Mac
you have):

<http://support.apple.com/kb/HT1431>

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#63109

In article 
<chine.bleu-96911C.21361508082014@news.eternal-september.org>,
 Siri Crews <chine.bleu@yahoo.com> wrote:

> Any ideas why a 10.6 partition would no longer boot? Disk Utility says it is 
> bootable.
> 
> The kernel logs run
> 
> Darwin Kernel Version 10.8.0: Tue Jun  7 16:33:36 PDT 2011; 
> root:xnu-1504.15.3~1/RELEASE_I386
> vm_page_bootstrap: 949513 free pages and 25335 wired pages
> standard timeslicing quantum is 10000 us
> mig_table_max_displ = 73
> AppleACPICPU: ProcessorId=0 LocalApicId=0 Enabled
> AppleACPICPU: ProcessorId=1 LocalApicId=1 Enabled
> calling mpo_policy_init for TMSafetyNet
> Security policy loaded: Safety net for Time Machine (TMSafetyNet)
> calling mpo_policy_init for Quarantine
> Security policy loaded: Quarantine policy (Quarantine)
> calling mpo_policy_init for Sandbox
> Security policy loaded: Seatbelt sandbox policy (Sandbox)
> Copyright (c) 1982, 1986, 1989, 1991, 1993
> The Regents of the University of California. All rights reserved.
> MAC Framework successfully initialized
> using 16384 buffer headers and 4096 cluster IO buffer headers
> IOAPIC: Version 0x11 Vectors 64:87
> ACPI: System State [S0 S3 S4 S5] (S3)
> PFM64 0xf10000000, 0xf0000000
> [ PCI configuration begin ]
> console relocated to 0xf10010000
> PCI configuration changed (bridge=3 device=1 cardbus=0)
> [ PCI configuration end, bridges 6 devices 18 ]
> AppleIntelCPUPowerManagement: (built 16:44:45 Jun  7 2011) initialization 
> complete
> mbinit: done (64 MB memory set for mbuf pool)
> rooting via boot-uuid from /chosen: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
> Waiting on <dict ID="0"><key>IOProviderClass</key><string 
> ID="1">IOResources</string><key>IOResourceMatch</key><string 
> ID="2">boot-uuid-media</string></dict>
> com.apple.AppleFSCompressionTypeZlib kmod start
> com.apple.AppleFSCompressionTypeZlib load succeeded
> AppleIntelCPUPowerManagementClient: ready
> BTCOEXIST off 
> wl0: Broadcom BCM432b 802.11 Wireless Controller
> 5.10.131.42
> FireWire (OHCI) Lucent ID XXXX built-in now active, GUID XXXXXXXXXXXXXXXX; 
> max 
> speed s800.
> USBMSC Identifier (non-unique): XXXXXXXXXXXX 0xXXX 0xXXXX 0xXXXX
> 
> It used to continue with
> 
> Got boot device = 
> IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@B/AppleXXXXXXXXX/P
> RT0
> @0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageD
> riv
> er/Hitachi XXXXXXXXXXXXXXX Media/IOGUIDPartitionScheme/Untitled 1@2
> BSD root: disk0s2, major 14, minor 1
> jnl: unknown-dev: replay_journal: from: 3186688 to: 5646848 (joffset 
> 0x1e5000)
> ...
> 
> But it now hangs
> 
> Still waiting for root device
> Still waiting for root device
> Still waiting for root device

Is this a laptop sized drive?  If so, see if the hard drive connector 
popped off.

If the drive is mechanical but doesn't spin up, remove it and twist it 
back and forth as fast as you can in your hand.  Definitely prepare to 
replace it if this fixes it.  It means the bearings are worn out and the 
noise from them will soon scramble everything.

[toc] | [prev] | [next] | [standalone]

#63116

In article <mcmurtrie-983C91.11200409082014@news.sonic.net>,
 Kevin McMurtrie <mcmurtrie@pixelmemory.us> wrote:

> In article 
> <chine.bleu-96911C.21361508082014@news.eternal-september.org>,
>  Siri Crews <chine.bleu@yahoo.com> wrote:
> 
> > Any ideas why a 10.6 partition would no longer boot? Disk Utility says it 
> > is 
> > bootable.
> > 
> > The kernel logs run
> > 
> > Darwin Kernel Version 10.8.0: Tue Jun  7 16:33:36 PDT 2011; 
> > root:xnu-1504.15.3~1/RELEASE_I386
> > vm_page_bootstrap: 949513 free pages and 25335 wired pages
> > standard timeslicing quantum is 10000 us
> > mig_table_max_displ = 73
> > AppleACPICPU: ProcessorId=0 LocalApicId=0 Enabled
> > AppleACPICPU: ProcessorId=1 LocalApicId=1 Enabled
> > calling mpo_policy_init for TMSafetyNet
> > Security policy loaded: Safety net for Time Machine (TMSafetyNet)
> > calling mpo_policy_init for Quarantine
> > Security policy loaded: Quarantine policy (Quarantine)
> > calling mpo_policy_init for Sandbox
> > Security policy loaded: Seatbelt sandbox policy (Sandbox)
> > Copyright (c) 1982, 1986, 1989, 1991, 1993
> > The Regents of the University of California. All rights reserved.
> > MAC Framework successfully initialized
> > using 16384 buffer headers and 4096 cluster IO buffer headers
> > IOAPIC: Version 0x11 Vectors 64:87
> > ACPI: System State [S0 S3 S4 S5] (S3)
> > PFM64 0xf10000000, 0xf0000000
> > [ PCI configuration begin ]
> > console relocated to 0xf10010000
> > PCI configuration changed (bridge=3 device=1 cardbus=0)
> > [ PCI configuration end, bridges 6 devices 18 ]
> > AppleIntelCPUPowerManagement: (built 16:44:45 Jun  7 2011) initialization 
> > complete
> > mbinit: done (64 MB memory set for mbuf pool)
> > rooting via boot-uuid from /chosen: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
> > Waiting on <dict ID="0"><key>IOProviderClass</key><string 
> > ID="1">IOResources</string><key>IOResourceMatch</key><string 
> > ID="2">boot-uuid-media</string></dict>
> > com.apple.AppleFSCompressionTypeZlib kmod start
> > com.apple.AppleFSCompressionTypeZlib load succeeded
> > AppleIntelCPUPowerManagementClient: ready
> > BTCOEXIST off 
> > wl0: Broadcom BCM432b 802.11 Wireless Controller
> > 5.10.131.42
> > FireWire (OHCI) Lucent ID XXXX built-in now active, GUID XXXXXXXXXXXXXXXX; 
> > max 
> > speed s800.
> > USBMSC Identifier (non-unique): XXXXXXXXXXXX 0xXXX 0xXXXX 0xXXXX
> > 
> > It used to continue with
> > 
> > Got boot device = 
> > IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@B/AppleXXXXXXXXX
> > /P
> > RT0
> > @0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorag
> > eD
> > riv
> > er/Hitachi XXXXXXXXXXXXXXX Media/IOGUIDPartitionScheme/Untitled 1@2
> > BSD root: disk0s2, major 14, minor 1
> > jnl: unknown-dev: replay_journal: from: 3186688 to: 5646848 (joffset 
> > 0x1e5000)
> > ...
> > 
> > But it now hangs
> > 
> > Still waiting for root device
> > Still waiting for root device
> > Still waiting for root device
> 
> Is this a laptop sized drive?  If so, see if the hard drive connector 
> popped off.

The 10.6 partition is on the same disk as the 10.7, and the 10.7 boots. Also the 
partition is available once booted in 10.7. So it's not mechanical but something 
about the disk contents or the PRAM (not yet tested).

-- 
:-<> Siri Seal of Disavowal #000-001. Disavowed. Denied. Deleted.
'I desire mercy, not sacrifice.'
Icke's razor: Given two equally plausible explanations, choose the weirder.

[toc] | [prev] | [next] | [standalone]

#63119

In article 
<chine.bleu-A6FCDC.17202409082014@news.eternal-september.org>,
 Siri Crews <chine.bleu@yahoo.com> wrote:

> In article <mcmurtrie-983C91.11200409082014@news.sonic.net>,
>  Kevin McMurtrie <mcmurtrie@pixelmemory.us> wrote:
> 
> > In article 
> > <chine.bleu-96911C.21361508082014@news.eternal-september.org>,
> >  Siri Crews <chine.bleu@yahoo.com> wrote:
> > 
> > > Any ideas why a 10.6 partition would no longer boot? Disk Utility says it 
> > > is 
> > > bootable.
> > > 
> > > The kernel logs run
> > > 
> > > Darwin Kernel Version 10.8.0: Tue Jun  7 16:33:36 PDT 2011; 
> > > root:xnu-1504.15.3~1/RELEASE_I386
> > > vm_page_bootstrap: 949513 free pages and 25335 wired pages
> > > standard timeslicing quantum is 10000 us
> > > mig_table_max_displ = 73
> > > AppleACPICPU: ProcessorId=0 LocalApicId=0 Enabled
> > > AppleACPICPU: ProcessorId=1 LocalApicId=1 Enabled
> > > calling mpo_policy_init for TMSafetyNet
> > > Security policy loaded: Safety net for Time Machine (TMSafetyNet)
> > > calling mpo_policy_init for Quarantine
> > > Security policy loaded: Quarantine policy (Quarantine)
> > > calling mpo_policy_init for Sandbox
> > > Security policy loaded: Seatbelt sandbox policy (Sandbox)
> > > Copyright (c) 1982, 1986, 1989, 1991, 1993
> > > The Regents of the University of California. All rights reserved.
> > > MAC Framework successfully initialized
> > > using 16384 buffer headers and 4096 cluster IO buffer headers
> > > IOAPIC: Version 0x11 Vectors 64:87
> > > ACPI: System State [S0 S3 S4 S5] (S3)
> > > PFM64 0xf10000000, 0xf0000000
> > > [ PCI configuration begin ]
> > > console relocated to 0xf10010000
> > > PCI configuration changed (bridge=3 device=1 cardbus=0)
> > > [ PCI configuration end, bridges 6 devices 18 ]
> > > AppleIntelCPUPowerManagement: (built 16:44:45 Jun  7 2011) initialization 
> > > complete
> > > mbinit: done (64 MB memory set for mbuf pool)
> > > rooting via boot-uuid from /chosen: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
> > > Waiting on <dict ID="0"><key>IOProviderClass</key><string 
> > > ID="1">IOResources</string><key>IOResourceMatch</key><string 
> > > ID="2">boot-uuid-media</string></dict>
> > > com.apple.AppleFSCompressionTypeZlib kmod start
> > > com.apple.AppleFSCompressionTypeZlib load succeeded
> > > AppleIntelCPUPowerManagementClient: ready
> > > BTCOEXIST off 
> > > wl0: Broadcom BCM432b 802.11 Wireless Controller
> > > 5.10.131.42
> > > FireWire (OHCI) Lucent ID XXXX built-in now active, GUID 
> > > XXXXXXXXXXXXXXXX; 
> > > max 
> > > speed s800.
> > > USBMSC Identifier (non-unique): XXXXXXXXXXXX 0xXXX 0xXXXX 0xXXXX
> > > 
> > > It used to continue with
> > > 
> > > Got boot device = 
> > > IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@B/AppleXXXXXXX
> > > XX
> > > /P
> > > RT0
> > > @0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStor
> > > ag
> > > eD
> > > riv
> > > er/Hitachi XXXXXXXXXXXXXXX Media/IOGUIDPartitionScheme/Untitled 1@2
> > > BSD root: disk0s2, major 14, minor 1
> > > jnl: unknown-dev: replay_journal: from: 3186688 to: 5646848 (joffset 
> > > 0x1e5000)
> > > ...
> > > 
> > > But it now hangs
> > > 
> > > Still waiting for root device
> > > Still waiting for root device
> > > Still waiting for root device
> > 
> > Is this a laptop sized drive?  If so, see if the hard drive connector 
> > popped off.
> 
> The 10.6 partition is on the same disk as the 10.7, and the 10.7 boots. Also 
> the 
> partition is available once booted in 10.7. So it's not mechanical but 
> something 
> about the disk contents or the PRAM (not yet tested).

Try booting into single user mode and fully reading the disk device with 
'dd' or one of the 'fsck' options.  I've had bad experiences with 
Hitachi failing while still reporting a good SMART status.  MacOS X 
rarely reports fatal disk I/O errors on its own.

[toc] | [prev] | [next] | [standalone]

#63124

In article <mcmurtrie-3871F7.22313309082014@news.sonic.net>,
 Kevin McMurtrie <mcmurtrie@pixelmemory.us> wrote:

> Try booting into single user mode and fully reading the disk device with 
> 'dd' or one of the 'fsck' options.  I've had bad experiences with 
> Hitachi failing while still reporting a good SMART status.  MacOS X 
> rarely reports fatal disk I/O errors on its own.

I finally got the 64-bit 10.6 up again, but then it failed on reboot, so, crap, 
that means a race condition (unlikely) or a flakey disk or disk sector. Oh, 
well. I got an external disk with more than enough spare room, so I can copying 
off to a spare and all that kind of nonsense. Oh, mother pus bucket.

-- 
:-<> Siri Seal of Disavowal #000-001. Disavowed. Denied. Deleted.
'I desire mercy, not sacrifice.'
Icke's razor: Given two equally plausible explanations, choose the weirder.

[toc] | [prev] | [next] | [standalone]

#63125

On 2014-08-10, Siri Crews <chine.bleu@yahoo.com> wrote:
> In article <mcmurtrie-3871F7.22313309082014@news.sonic.net>,
>  Kevin McMurtrie <mcmurtrie@pixelmemory.us> wrote:
>
>> Try booting into single user mode and fully reading the disk device with 
>> 'dd' or one of the 'fsck' options.  I've had bad experiences with 
>> Hitachi failing while still reporting a good SMART status.  MacOS X 
>> rarely reports fatal disk I/O errors on its own.
>
> I finally got the 64-bit 10.6 up again, but then it failed on reboot, so, crap, 
> that means a race condition (unlikely) or a flakey disk or disk sector. Oh, 
> well. I got an external disk with more than enough spare room, so I can copying 
> off to a spare and all that kind of nonsense. Oh, mother pus bucket.

You tried resetting the PRAM and SMC/PMU?

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#63126

In article <c4pt8aF6o75U1@mid.individual.net>,
 Jolly Roger <jollyroger@pobox.com> wrote:

> On 2014-08-10, Siri Crews <chine.bleu@yahoo.com> wrote:
> > In article <mcmurtrie-3871F7.22313309082014@news.sonic.net>,
> >  Kevin McMurtrie <mcmurtrie@pixelmemory.us> wrote:
> >
> >> Try booting into single user mode and fully reading the disk device with 
> >> 'dd' or one of the 'fsck' options.  I've had bad experiences with 
> >> Hitachi failing while still reporting a good SMART status.  MacOS X 
> >> rarely reports fatal disk I/O errors on its own.
> >
> > I finally got the 64-bit 10.6 up again, but then it failed on reboot, so, 
> > crap, 
> > that means a race condition (unlikely) or a flakey disk or disk sector. Oh, 
> > well. I got an external disk with more than enough spare room, so I can 
> > copying 
> > off to a spare and all that kind of nonsense. Oh, mother pus bucket.
> 
> You tried resetting the PRAM and SMC/PMU?

Yes. No help.

-- 
:-<> Siri Seal of Disavowal #000-001. Disavowed. Denied. Deleted.
'I desire mercy, not sacrifice.'
Icke's razor: Given two equally plausible explanations, choose the weirder.

[toc] | [prev] | [next] | [standalone]

#63127

On 2014-08-10, Siri Crews <chine.bleu@yahoo.com> wrote:
> In article <c4pt8aF6o75U1@mid.individual.net>,
>  Jolly Roger <jollyroger@pobox.com> wrote:
>
>> On 2014-08-10, Siri Crews <chine.bleu@yahoo.com> wrote:
>> > In article <mcmurtrie-3871F7.22313309082014@news.sonic.net>,
>> >  Kevin McMurtrie <mcmurtrie@pixelmemory.us> wrote:
>> >
>> >> Try booting into single user mode and fully reading the disk device with 
>> >> 'dd' or one of the 'fsck' options.  I've had bad experiences with 
>> >> Hitachi failing while still reporting a good SMART status.  MacOS X 
>> >> rarely reports fatal disk I/O errors on its own.
>> >
>> > I finally got the 64-bit 10.6 up again, but then it failed on reboot, so, 
>> > crap, 
>> > that means a race condition (unlikely) or a flakey disk or disk sector. Oh, 
>> > well. I got an external disk with more than enough spare room, so I can 
>> > copying 
>> > off to a spare and all that kind of nonsense. Oh, mother pus bucket.
>> 
>> You tried resetting the PRAM and SMC/PMU?
>
> Yes. No help.

: / Sorry.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#63128

On 2014-08-10 18:35:09 +0000, Siri Crews <chine.bleu@yahoo.com> said:

> In article <mcmurtrie-3871F7.22313309082014@news.sonic.net>,
>  Kevin McMurtrie <mcmurtrie@pixelmemory.us> wrote:
> 
>> Try booting into single user mode and fully reading the disk device with
>> 'dd' or one of the 'fsck' options.  I've had bad experiences with
>> Hitachi failing while still reporting a good SMART status.  MacOS X
>> rarely reports fatal disk I/O errors on its own.
> 
> I finally got the 64-bit 10.6 up again, but then it failed on reboot, so, crap,
> that means a race condition (unlikely) or a flakey disk or disk sector. Oh,
> well. I got an external disk with more than enough spare room, so I can copying
> off to a spare and all that kind of nonsense. Oh, mother pus bucket.

I take it you don't have something like Diskwarrior...  I've 
resurrected drives that wouldn't boot with DW before.

It's expensive, and a one-trick pony - but it does what it does very 
well.  Their tech support will even give you a password that will 
unlock hidden diagnostics within the program for specific needs.

I've heard of cases where it's run for hours, or even days to fix 
problems on a drive.
-- 
“I'm fairly certain that YOLO is just Carpe Diem for stupid people.”  - 
Jack Black

[toc] | [prev] | [next] | [standalone]

#63130

In article <ls8g0s$t25$1@dont-email.me>, FPP <fredp151@gmail.com> wrote:

> On 2014-08-10 18:35:09 +0000, Siri Crews <chine.bleu@yahoo.com> said:
> 
> > In article <mcmurtrie-3871F7.22313309082014@news.sonic.net>,
> >  Kevin McMurtrie <mcmurtrie@pixelmemory.us> wrote:
> > 
> >> Try booting into single user mode and fully reading the disk device with
> >> 'dd' or one of the 'fsck' options.  I've had bad experiences with
> >> Hitachi failing while still reporting a good SMART status.  MacOS X
> >> rarely reports fatal disk I/O errors on its own.
> > 
> > I finally got the 64-bit 10.6 up again, but then it failed on reboot, so, 
> > crap,
> > that means a race condition (unlikely) or a flakey disk or disk sector. Oh,
> > well. I got an external disk with more than enough spare room, so I can 
> > copying
> > off to a spare and all that kind of nonsense. Oh, mother pus bucket.
> 
> I take it you don't have something like Diskwarrior...  I've 
> resurrected drives that wouldn't boot with DW before.
> 
> It's expensive, and a one-trick pony - but it does what it does very 
> well.  Their tech support will even give you a password that will 
> unlock hidden diagnostics within the program for specific needs.
> 
> I've heard of cases where it's run for hours, or even days to fix 
> problems on a drive.

The first thing is to try to copy the disk to another drive before messing 
around with the drive with the root file system.

-- 
:-<> Siri Seal of Disavowal #000-001. Disavowed. Denied. Deleted.
'I desire mercy, not sacrifice.'
Icke's razor: Given two equally plausible explanations, choose the weirder.

[toc] | [prev] | [next] | [standalone]

#63135

On 2014-08-10 19:24:42 +0000, Siri Crews <chine.bleu@yahoo.com> said:

> In article <ls8g0s$t25$1@dont-email.me>, FPP <fredp151@gmail.com> wrote:
> 
>> On 2014-08-10 18:35:09 +0000, Siri Crews <chine.bleu@yahoo.com> said:
>> 
>>> In article <mcmurtrie-3871F7.22313309082014@news.sonic.net>,
>>> Kevin McMurtrie <mcmurtrie@pixelmemory.us> wrote:
>>> 
>>>> Try booting into single user mode and fully reading the disk device with
>>>> 'dd' or one of the 'fsck' options.  I've had bad experiences with
>>>> Hitachi failing while still reporting a good SMART status.  MacOS X
>>>> rarely reports fatal disk I/O errors on its own.
>>> 
>>> I finally got the 64-bit 10.6 up again, but then it failed on reboot, so,
>>> crap,
>>> that means a race condition (unlikely) or a flakey disk or disk sector. Oh,
>>> well. I got an external disk with more than enough spare room, so I can
>>> copying
>>> off to a spare and all that kind of nonsense. Oh, mother pus bucket.
>> 
>> I take it you don't have something like Diskwarrior...  I've
>> resurrected drives that wouldn't boot with DW before.
>> 
>> It's expensive, and a one-trick pony - but it does what it does very
>> well.  Their tech support will even give you a password that will
>> unlock hidden diagnostics within the program for specific needs.
>> 
>> I've heard of cases where it's run for hours, or even days to fix
>> problems on a drive.
> 
> The first thing is to try to copy the disk to another drive before messing
> around with the drive with the root file system.

Really, backing up BEFORE you had a disk problem was the first, last 
and only thing you really needed to do.

At this point, if you're fucked, you're fucked.

Diskwarrior won't actually DO anything until you tell it to.  I assumed 
you'd have tried to copy the disk first, before even thinking about 
trying anything else.

If DW thinks it's too far gone to repair, it allows you to preview your 
drive, and that's when you would try a last ditch effort to copy the 
data off the drive.
-- 
Never wrestle with a pig.  You both get dirty... and the pig LIKES it.

[toc] | [prev] | [next] | [standalone]

#63141

In article <ls8g0s$t25$1@dont-email.me>, FPP <fredp151@gmail.com> 
wrote:

> On 2014-08-10 18:35:09 +0000, Siri Crews <chine.bleu@yahoo.com> said:
> 
> > In article <mcmurtrie-3871F7.22313309082014@news.sonic.net>,
> >  Kevin McMurtrie <mcmurtrie@pixelmemory.us> wrote:
> > 
> >> Try booting into single user mode and fully reading the disk device with
> >> 'dd' or one of the 'fsck' options.  I've had bad experiences with
> >> Hitachi failing while still reporting a good SMART status.  MacOS X
> >> rarely reports fatal disk I/O errors on its own.
> > 
> > I finally got the 64-bit 10.6 up again, but then it failed on reboot, so, 
> > crap,
> > that means a race condition (unlikely) or a flakey disk or disk sector. Oh,
> > well. I got an external disk with more than enough spare room, so I can 
> > copying
> > off to a spare and all that kind of nonsense. Oh, mother pus bucket.
> 
> I take it you don't have something like Diskwarrior...  I've 
> resurrected drives that wouldn't boot with DW before.
> 
> It's expensive, and a one-trick pony - but it does what it does very 
> well.  Their tech support will even give you a password that will 
> unlock hidden diagnostics within the program for specific needs.
> 
> I've heard of cases where it's run for hours, or even days to fix 
> problems on a drive.

Lucky you.  For me it usually crashes or runs out of memory.  It's a bad 
hack that can't repair volumes with lots files on them.  It's such a bad 
hack that Alsoft can't seem to fix it or make it 64 bit so it stops 
running out of memory.

Recent versions of fsck_hfs have all the same features as DW but without 
the crashing and aborting.  Yes, it even does lossy repairs 
(cross-linked files) and can rebuild btrees.

[toc] | [prev] | [next] | [standalone]

#63142

In article <mcmurtrie-B282FA.19303010082014@news.sonic.net>, Kevin
McMurtrie <mcmurtrie@pixelmemory.us> wrote:

> > I take it you don't have something like Diskwarrior...  I've 
> > resurrected drives that wouldn't boot with DW before.
> > 
> > It's expensive, and a one-trick pony - but it does what it does very 
> > well.  Their tech support will even give you a password that will 
> > unlock hidden diagnostics within the program for specific needs.
> > 
> > I've heard of cases where it's run for hours, or even days to fix 
> > problems on a drive.
> 
> Lucky you.  For me it usually crashes or runs out of memory.  It's a bad 
> hack that can't repair volumes with lots files on them.  It's such a bad 
> hack that Alsoft can't seem to fix it or make it 64 bit so it stops 
> running out of memory.

diskwarrior is not a hack and they're working on 64 bit.

it also rarely runs out of memory.

> Recent versions of fsck_hfs have all the same features as DW but without 
> the crashing and aborting.  Yes, it even does lossy repairs 
> (cross-linked files) and can rebuild btrees.

nonsense. fsck doesn't do anywhere near as much as diskwarrior nor as
well.

[toc] | [prev] | [next] | [standalone]

#63143

On 2014-08-11 02:36:48 +0000, nospam <nospam@nospam.invalid> said:

> In article <mcmurtrie-B282FA.19303010082014@news.sonic.net>, Kevin
> McMurtrie <mcmurtrie@pixelmemory.us> wrote:
> 
>>> I take it you don't have something like Diskwarrior...  I've
>>> resurrected drives that wouldn't boot with DW before.
>>> 
>>> It's expensive, and a one-trick pony - but it does what it does very
>>> well.  Their tech support will even give you a password that will
>>> unlock hidden diagnostics within the program for specific needs.
>>> 
>>> I've heard of cases where it's run for hours, or even days to fix
>>> problems on a drive.
>> 
>> Lucky you.  For me it usually crashes or runs out of memory.  It's a bad
>> hack that can't repair volumes with lots files on them.  It's such a bad
>> hack that Alsoft can't seem to fix it or make it 64 bit so it stops
>> running out of memory.
> 
> diskwarrior is not a hack and they're working on 64 bit.
> 
> it also rarely runs out of memory.
> 
>> Recent versions of fsck_hfs have all the same features as DW but without
>> the crashing and aborting.  Yes, it even does lossy repairs
>> (cross-linked files) and can rebuild btrees.
> 
> nonsense. fsck doesn't do anywhere near as much as diskwarrior nor as
> well.

I've had two systems that wouldn't boot.  Used fsck, techtool pro, 
drive genius.  Nothing would work.

Except Diskwarrior.

I've never had a problem running it, and I think it's money well spent, 
even it it's only fixed severe problems twice.

Like I said, it's expensive... but so is losing your work.  I run it 
routinely every month, or so... and it rarely finds any errors to 
correct.  I suspect I run it far more than I really need to... but it 
doesn't cost anything  but time, and has never caused a problem.

Now, when I run it on our machines at work, it usually finds a problem, 
here and there... but that's probably because they get heavier usage - 
and nobody seems to really care about a work machine.
-- 
Is it true that cannibals don't eat clowns because they taste funny?

[toc] | [prev] | [next] | [standalone]

#63148

nospam <nospam@nospam.invalid> wrote:

> they're working on 64 bit.

I'll believe that when I see it. It's seven years since the last major
upgrade (DiskWarrior 4) was released and the last 32-bit Mac shipped. If
Alsoft couldn't get a 64-bit version out the door before now, they
probably never will. Think Copland. 

DiskWarrior is zombieware, done in by the Recovery Disk and Time Machine
software that comes with every free copy of OS X. 

[toc] | [prev] | [next] | [standalone]

#63150

In article <1lq7j29.15q85hrwhotq6N%nmassello@yahoo.com>, Neill Massello
<nmassello@yahoo.com> wrote:

> nospam <nospam@nospam.invalid> wrote:
> 
> > they're working on 64 bit.
> 
> I'll believe that when I see it. It's seven years since the last major
> upgrade (DiskWarrior 4) was released and the last 32-bit Mac shipped. If
> Alsoft couldn't get a 64-bit version out the door before now, they
> probably never will. Think Copland. 

it took apple over 5 years to port final cut to 64 bit, and only by
removing most of its features. 

apple also had a *lot* more resources than alsoft does.

diskwarrior also needs to be battle-tested, which is likely what's
taking the bulk of the time. 

unlike final cut, where a bug might cause an artifact in a movie that
can't even be seen, a bug in diskwarrior can mean not recovering files.

> DiskWarrior is zombieware, done in by the Recovery Disk and Time Machine
> software that comes with every free copy of OS X. 

nonsense.

[toc] | [prev] | [next] | [standalone]

#63153

On 2014-08-11 15:54:34 +0000, nmassello@yahoo.com (Neill Massello) said:

> nospam <nospam@nospam.invalid> wrote:
> 
>> they're working on 64 bit.
> 
> I'll believe that when I see it. It's seven years since the last major
> upgrade (DiskWarrior 4) was released and the last 32-bit Mac shipped. If
> Alsoft couldn't get a 64-bit version out the door before now, they
> probably never will. Think Copland.
> 
> DiskWarrior is zombieware, done in by the Recovery Disk and Time Machine
> software that comes with every free copy of OS X.

Really?  What oes Time Machine repair?

What does the Recovery Disk do that you can't do from any other 
partition with OSX on it?
-- 
It's 99% of politicians that give the rest a bad name.

[toc] | [prev] | [next] | [standalone]

#63160

In article <lsb6od$8so$1@dont-email.me>, FPP <fredp151@gmail.com> wrote:
> On 2014-08-11 15:54:34 +0000, nmassello@yahoo.com (Neill Massello) said:
> > nospam <nospam@nospam.invalid> wrote:
> >>  
> >> they're working on 64 bit.
> > 
> > I'll believe that when I see it. It's seven years since the last major
> > upgrade (DiskWarrior 4) was released and the last 32-bit Mac shipped. If
> > Alsoft couldn't get a 64-bit version out the door before now, they
> > probably never will. Think Copland.
> > 
> > DiskWarrior is zombieware, done in by the Recovery Disk and Time Machine
> > software that comes with every free copy of OS X.
> 
> Really?  What oes Time Machine repair?

Nothing. that was Neill's point - you don't need to repair the drive,
you simply reformat or replace it, and then restore the backup.

[toc] | [prev] | [next] | [standalone]

#63162

On 2014-08-11 21:21:01 +0000, Your Name <YourName@YourISP.com> said:

> In article <lsb6od$8so$1@dont-email.me>, FPP <fredp151@gmail.com> wrote:
>> On 2014-08-11 15:54:34 +0000, nmassello@yahoo.com (Neill Massello) said:
>>> nospam <nospam@nospam.invalid> wrote:
>>>> 
>>>> they're working on 64 bit.
>>> 
>>> I'll believe that when I see it. It's seven years since the last major
>>> upgrade (DiskWarrior 4) was released and the last 32-bit Mac shipped. If
>>> Alsoft couldn't get a 64-bit version out the door before now, they
>>> probably never will. Think Copland.
>>> 
>>> DiskWarrior is zombieware, done in by the Recovery Disk and Time Machine
>>> software that comes with every free copy of OS X.
>> 
>> Really?  What oes Time Machine repair?
> 
> Nothing. that was Neill's point - you don't need to repair the drive,
> you simply reformat or replace it, and then restore the backup.

If the drive is bad, fine... that makes sense.

If it's the OS, then just porting the problem over to a new drive does 
nothing.  Your backup might just contain the seed of the root problem, 
and you'd never know it.

In which case, repairing the OS is what you should do.
-- 
All those who believe in telekinesis raise my hand.

[toc] | [prev] | [next] | [standalone]

Page 1 of 4  [1] 2 3 4  Next page →

Back to top | Article view | comp.sys.mac.system

csiph-web