Must be another m.r. glitch, but today flickr will not load on this particular machine. Other macs/pc's in my house/office load it fine, so something goofy has struck again. Flickr loaded fine last night, was using 1001 to upload a few images, was browsing some interesting photos by shikeroku, etc.
(late edit, turns out my system hosed itself the same time that flickr was actually having a major hiccup; and I bet a lot of dead chickens that there was zero cause/effect between my screwed up system and flickrs outage)
Checked console log, and there is this troubling message, repeated over and over.
crashdump: SampleAllThreads() returned no stacks for pid: 24220 name: sh Unable to determine CPSProcessSerNum pid: 24220 name: sh
I don't see any process by that particular pid, but then I noticed the pid changes....
Apr 4 20:30:14 crashdump: Started writing crash report to: /Library/Logs/CrashReporter/sh.crash.logApr 4 20:30:14 crashdump: Finished writing crash report to: /Library/Logs/CrashReporter/sh.crash.log
Apr 4 20:30:20 crashdump: SampleAllThreads() returned no stacks for pid: 25162 name: sh Unable to determine CPSProcessSerNum pid: 25162 name: sh
Apr 4 20:30:20 crashdump: Started writing crash report to: /Library/Logs/CrashReporter/sh.crash.log
Apr 4 20:30:20 crashdump: Finished writing crash report to: /Library/Logs/CrashReporter/sh.crash.log
Apr 4 20:30:24 crashdump: SampleAllThreads() returned no stacks for pid: 25165 name: sh Unable to determine CPSProcessSerNum pid: 25165 name: sh
Apr 4 20:30:24 crashdump: Started writing crash report to: /Library/Logs/CrashReporter/sh.crash.log
Apr 4 20:30:24 crashdump: Finished writing crash report to: /Library/Logs/CrashReporter/sh.crash.log
Apr 4 20:30:30 crashdump: SampleAllThreads() returned no stacks for pid: 25168 name: sh Unable to determine CPSProcessSerNum pid: 25168 name: sh
Apr 4 20:30:30 crashdump: Started writing crash report to: /Library/Logs/CrashReporter/sh.crash.log
Apr 4 20:30:30 crashdump: Finished writing crash report to: /Library/Logs/CrashReporter/sh.crash.log
hmmm, taking a look at that particular crash log gives:
Date/Time: 2005-04-04 20:37:49 -0500 OS Version: 10.3.8 (Build 7U16) Report Version: 2Command: sh
Path: /bin/sh
Version: ??? (???)
PID: 25417
Thread: UnknownException: EXC_SOFTWARE (0x0005)
Code[0]: 0x00000001
Code[1]: 0x00002100
Backtrace not availablePPC Thread State:
srr0: 0x00002100 srr1: 0x0002d030 vrsave: 0x00000000
cr: 0x22000024 xer: 0x00000000 lr: 0x00001db4 ctr: 0x000020f4
r0: 0x0a090909 r1: 0x64690000 r2: 0x00091d30 r3: 0x8fe50480
r4: 0x00000000 r5: 0x00000000 r6: 0x8fe505fc r7: 0x8fe50664
r8: 0x8fe505fc r9: 0x8fe48ba5 r10: 0x0000000d r11: 0x00000000
r12: 0x000020f4 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00003e1a r21: 0x00000000 r22: 0x00000000 r23: 0x00000000
r24: 0x00000000 r25: 0x00000000 r26: 0xbfffff38 r27: 0x00000010
r28: 0x00000003 r29: 0xbfffff3c r30: 0xbfffff4c r31: 0x00001d30Binary Images Description:
0x1000 - 0x8afff sh sh
0x8fe00000 - 0x8fe4ffff dyld /usr/lib/dyld
0x90000000 - 0x90122fff libSystem.B.dylib /usr/lib/libSystem.B.dylib
0x939d0000 - 0x939d4fff libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib
0x94120000 - 0x9414bfff libncurses.5.dylib /usr/lib/libncurses.5.dylib
every few seconds, another crash report.
Time to reboot, pray, and sprinkle more chicken blood on my G5.....
Processes: 81Update several hours later: oh shite, I really fucked everything up this time.
Averages: 8.85 8.76 8.49
Uptime: 11 days 3:33
3. Ok, I thought, I'll just reboot, and whatever this is will fix itself. Doh!
After rebooting, the apple logo showed up, then the screen went black, and the text message “init: can't exececute /bin/sh for single user: exec format error”
and “can't exececute /bin/sh for /etc/rc: exec format error.
4. Uh oh. Was unable to progress anywhere past this (using my bare-bones command line skills).
5. Rebooted a few times, eventually holding the eject button on my keyboard, and used my G5 software install and restore disk. First ran disk utility, and found several ”overlapped extent allocation files“. Repaired permissions for good measure (plenty of permissions were repaired, I didn't write any of these messages down).
6. My admin password now would not work, so I used the 'reset password' tool on the System restore disc. Reinstalled system (using the archive option)
7. My software restore/install disk is actually 10.2 (took me a moment to notice), so started re-installing OS 3 from a store bought copy.
8. Seem to have lost disk 2 (have 1, 3, and even the original box, but cannot find disk 2), but system seems to work.
9. Except, and this is the key part: none of my user passwords work anymore! Including several afp users on my local network. They can only log on as guest, even though the user names are recognized, the system seems to have mucked up the passwords (which I have written down on paper in a notebook, so I know nothing has changed).