[DISSOLVED] was kernel panics, fs corruption, rsync, mem/efi...

Until today, Arch was running essentially fine on my laptop. Today, I had a kernel panic which forced me to cold reboot the machine. On reboot, I got more panics. I get panics whether I boot to runlevel 3, runlevel 5 or runlevel s. I get them with the lts kernel as well as the current one.
I even get kernel panics if I boot from the install usb I installed from in November.
The only boot which seems to work is booting finnix which is installed to a separate partition for emergency use.
fsck reports lots of errors. If I get it to fix one error, it finds more on the next run. Sometimes it will claim the fs is clean but fsck -fn says there are still errors. Sometimes fsck -f will give the partition a clean bill of health but if I repeat it, it will find new errors.
I have tried with fsck from finnix and fsck from the install media and from the system in single user mode. The latter two end with kernel panics.
smartctl finds no problems with the disk.
fsck also finds problems with my backups which are stored on an external drive. This drive was not attached when the original kernel panic occurred. It showed errors without any kernel panic occurring while it was connected. However, fscking it from the arch install media just caused another kernel panic.
At least, they look like kernel panics. I'm not sure whether they are or not because in some cases (not the original), I can switch to another tty. Just I very quickly get a crash there too once that has happened and commands tend to hang, especially disk related commands such as blkid or fsck, or give errors.
I desperately need advice. I have critical data on the drive. My backup is entirely current but since that too has errors, I'm not sure what to do for the best. So far, everything I've tried seems to have only made the situation worse - fsck, looking at the backup, booting from the install media...
Most fsck errors seem to concern incorrect inodes (it offers to clear them), inodes with illegal blocks (it offers to clear them), directory structure e.g. illegal characters in entries (it offers to fix them), incorrect references etc. In some cases, attempts to fix things don't seem to succeed: another run produces the same errors. In other cases, fsck wants to undo previous fixes on a second run e.g. for the same node it will say the reference count is 4 and should be 1 but if I let it fix that, on the next run it will say it is 1 but should be 4. I'm also getting "internal errors" due to missing information.
I'm ending up with a lot of things in lost+found...
The system is currently booted from the install media. I'm trying to shutdown as I'm on my fourth tty but it has hung trying to unmount filesystems.
Filesystems with errors are primarily ext4 because most of my filesystems are ext4.
Last edited by cfr (2012-03-10 03:14:51)

I am getting some worrying output in dmesg:
[ 0.000000] Disabled fast string operations
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000008f000 (usable)
[ 0.000000] BIOS-e820: 000000000008f000 - 0000000000090000 (ACPI NVS)
[ 0.000000] BIOS-e820: 0000000000090000 - 00000000000a0000 (usable)
[ 0.000000] BIOS-e820: 0000000000100000 - 0000000040000000 (usable)
[ 0.000000] BIOS-e820: 0000000040000000 - 0000000040200000 (reserved)
[ 0.000000] BIOS-e820: 0000000040200000 - 000000007a1c9000 (usable)
[ 0.000000] BIOS-e820: 000000007a1c9000 - 000000007a6dc000 (reserved)
[ 0.000000] BIOS-e820: 000000007a6dc000 - 000000007a79f000 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000007a79f000 - 000000007a7ff000 (ACPI data)
[ 0.000000] BIOS-e820: 000000007a7ff000 - 000000007a800000 (usable)
[ 0.000000] BIOS-e820: 00000000f80f8000 - 00000000f80f9000 (reserved)
[ 0.000000] BIOS-e820: 00000000fed1c000 - 00000000fed20000 (reserved)
[ 0.000000] BIOS-e820: 0000000100000000 - 0000000100600000 (usable)
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] EFI v2.00 by Phoenix Technologies Ltd.
[ 0.000000] ACPI=0x7a7fe000 ACPI 2.0=0x7a7fe014 SMBIOS=0x7a665000
[ 0.000000] Kernel-defined memdesc doesn't match the one from EFI!
[ 0.000000] EFI: mem00: type=3, attr=0xf, range=[0x0000000000000000-0x0000000000001000) (0MB)
[ 0.000000] EFI: mem01: type=7, attr=0xf, range=[0x0000000000001000-0x0000000000054000) (0MB)
[ 0.000000] EFI: mem02: type=4, attr=0xf, range=[0x0000000000054000-0x0000000000055000) (0MB)
[ 0.000000] EFI: mem03: type=3, attr=0xf, range=[0x0000000000055000-0x000000000008f000) (0MB)
[ 0.000000] EFI: mem04: type=10, attr=0xf, range=[0x000000000008f000-0x0000000000090000) (0MB)
[ 0.000000] EFI: mem05: type=3, attr=0xf, range=[0x0000000000090000-0x00000000000a0000) (0MB)
[ 0.000000] EFI: mem06: type=2, attr=0xf, range=[0x0000000000100000-0x0000000000424000) (3MB)
[ 0.000000] EFI: mem07: type=7, attr=0xf, range=[0x0000000000424000-0x000000001baa9000) (438MB)
[ 0.000000] EFI: mem08: type=2, attr=0xf, range=[0x000000001baa9000-0x000000003942a000) (473MB)
[ 0.000000] EFI: mem09: type=4, attr=0xf, range=[0x000000003942a000-0x000000003944a000) (0MB)
[ 0.000000] EFI: mem10: type=7, attr=0xf, range=[0x000000003944a000-0x000000003b8c0000) (36MB)
[ 0.000000] EFI: mem11: type=4, attr=0xf, range=[0x000000003b8c0000-0x000000003c41a000) (11MB)
[ 0.000000] EFI: mem12: type=7, attr=0xf, range=[0x000000003c41a000-0x0000000040000000) (59MB)
[ 0.000000] EFI: mem13: type=0, attr=0xf, range=[0x0000000040000000-0x0000000040200000) (2MB)
[ 0.000000] EFI: mem14: type=7, attr=0xf, range=[0x0000000040200000-0x0000000075a33000) (856MB)
[ 0.000000] EFI: mem15: type=1, attr=0xf, range=[0x0000000075a33000-0x0000000075a52000) (0MB)
[ 0.000000] EFI: mem16: type=7, attr=0xf, range=[0x0000000075a52000-0x0000000076c75000) (18MB)
[ 0.000000] EFI: mem17: type=4, attr=0xf, range=[0x0000000076c75000-0x0000000077279000) (6MB)
[ 0.000000] EFI: mem18: type=7, attr=0xf, range=[0x0000000077279000-0x000000007727b000) (0MB)
[ 0.000000] EFI: mem19: type=4, attr=0xf, range=[0x000000007727b000-0x000000007727c000) (0MB)
[ 0.000000] EFI: mem20: type=7, attr=0xf, range=[0x000000007727c000-0x000000007727d000) (0MB)
[ 0.000000] EFI: mem21: type=4, attr=0xf, range=[0x000000007727d000-0x0000000077ce5000) (10MB)
[ 0.000000] EFI: mem22: type=7, attr=0xf, range=[0x0000000077ce5000-0x0000000077e1e000) (1MB)
[ 0.000000] EFI: mem23: type=4, attr=0xf, range=[0x0000000077e1e000-0x0000000077e5e000) (0MB)
[ 0.000000] EFI: mem24: type=7, attr=0xf, range=[0x0000000077e5e000-0x0000000077e5f000) (0MB)
[ 0.000000] EFI: mem25: type=4, attr=0xf, range=[0x0000000077e5f000-0x0000000078282000) (4MB)
[ 0.000000] EFI: mem26: type=7, attr=0xf, range=[0x0000000078282000-0x0000000078285000) (0MB)
[ 0.000000] EFI: mem27: type=4, attr=0xf, range=[0x0000000078285000-0x00000000784d2000) (2MB)
[ 0.000000] EFI: mem28: type=7, attr=0xf, range=[0x00000000784d2000-0x00000000785e5000) (1MB)
[ 0.000000] EFI: mem29: type=4, attr=0xf, range=[0x00000000785e5000-0x00000000785ff000) (0MB)
[ 0.000000] EFI: mem30: type=7, attr=0xf, range=[0x00000000785ff000-0x0000000078602000) (0MB)
[ 0.000000] EFI: mem31: type=4, attr=0xf, range=[0x0000000078602000-0x000000007874a000) (1MB)
[ 0.000000] EFI: mem32: type=7, attr=0xf, range=[0x000000007874a000-0x000000007874b000) (0MB)
[ 0.000000] EFI: mem33: type=4, attr=0xf, range=[0x000000007874b000-0x000000007874f000) (0MB)
[ 0.000000] EFI: mem34: type=7, attr=0xf, range=[0x000000007874f000-0x0000000078750000) (0MB)
[ 0.000000] EFI: mem35: type=4, attr=0xf, range=[0x0000000078750000-0x0000000078782000) (0MB)
[ 0.000000] EFI: mem36: type=7, attr=0xf, range=[0x0000000078782000-0x0000000078783000) (0MB)
[ 0.000000] EFI: mem37: type=4, attr=0xf, range=[0x0000000078783000-0x0000000078795000) (0MB)
[ 0.000000] EFI: mem38: type=7, attr=0xf, range=[0x0000000078795000-0x000000007879a000) (0MB)
[ 0.000000] EFI: mem39: type=4, attr=0xf, range=[0x000000007879a000-0x00000000798c1000) (17MB)
[ 0.000000] Disabled fast string operations
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000008f000 (usable)
[ 0.000000] BIOS-e820: 000000000008f000 - 0000000000090000 (ACPI NVS)
[ 0.000000] BIOS-e820: 0000000000090000 - 00000000000a0000 (usable)
[ 0.000000] BIOS-e820: 0000000000100000 - 0000000040000000 (usable)
[ 0.000000] BIOS-e820: 0000000040000000 - 0000000040200000 (reserved)
[ 0.000000] BIOS-e820: 0000000040200000 - 000000007a1c9000 (usable)
[ 0.000000] BIOS-e820: 000000007a1c9000 - 000000007a6dc000 (reserved)
[ 0.000000] BIOS-e820: 000000007a6dc000 - 000000007a79f000 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000007a79f000 - 000000007a7ff000 (ACPI data)
[ 0.000000] BIOS-e820: 000000007a7ff000 - 000000007a800000 (usable)
[ 0.000000] BIOS-e820: 00000000f80f8000 - 00000000f80f9000 (reserved)
[ 0.000000] BIOS-e820: 00000000fed1c000 - 00000000fed20000 (reserved)
[ 0.000000] BIOS-e820: 0000000100000000 - 0000000100600000 (usable)
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] EFI v2.00 by Phoenix Technologies Ltd.
[ 0.000000] ACPI=0x7a7fe000 ACPI 2.0=0x7a7fe014 SMBIOS=0x7a665000
[ 0.000000] Kernel-defined memdesc doesn't match the one from EFI!
[ 0.000000] EFI: mem00: type=3, attr=0xf, range=[0x0000000000000000-0x0000000000001000) (0MB)
[ 0.000000] EFI: mem01: type=7, attr=0xf, range=[0x0000000000001000-0x0000000000054000) (0MB)
[ 0.000000] EFI: mem02: type=4, attr=0xf, range=[0x0000000000054000-0x0000000000055000) (0MB)
[ 0.000000] EFI: mem03: type=3, attr=0xf, range=[0x0000000000055000-0x000000000008f000) (0MB)
[ 0.000000] EFI: mem04: type=10, attr=0xf, range=[0x000000000008f000-0x0000000000090000) (0MB)
[ 0.000000] EFI: mem05: type=3, attr=0xf, range=[0x0000000000090000-0x00000000000a0000) (0MB)
[ 0.000000] EFI: mem06: type=2, attr=0xf, range=[0x0000000000100000-0x0000000000424000) (3MB)
[ 0.000000] EFI: mem07: type=7, attr=0xf, range=[0x0000000000424000-0x000000001baa9000) (438MB)
[ 0.000000] EFI: mem08: type=2, attr=0xf, range=[0x000000001baa9000-0x000000003942a000) (473MB)
[ 0.000000] EFI: mem09: type=4, attr=0xf, range=[0x000000003942a000-0x000000003944a000) (0MB)
[ 0.000000] EFI: mem10: type=7, attr=0xf, range=[0x000000003944a000-0x000000003b8c0000) (36MB)
[ 0.000000] EFI: mem11: type=4, attr=0xf, range=[0x000000003b8c0000-0x000000003c41a000) (11MB)
[ 0.000000] EFI: mem12: type=7, attr=0xf, range=[0x000000003c41a000-0x0000000040000000) (59MB)
[ 0.000000] EFI: mem13: type=0, attr=0xf, range=[0x0000000040000000-0x0000000040200000) (2MB)
[ 0.000000] EFI: mem14: type=7, attr=0xf, range=[0x0000000040200000-0x0000000075a33000) (856MB)
[ 0.000000] EFI: mem15: type=1, attr=0xf, range=[0x0000000075a33000-0x0000000075a52000) (0MB)
[ 0.000000] EFI: mem16: type=7, attr=0xf, range=[0x0000000075a52000-0x0000000076c75000) (18MB)
[ 0.000000] EFI: mem17: type=4, attr=0xf, range=[0x0000000076c75000-0x0000000077279000) (6MB)
[ 0.000000] EFI: mem18: type=7, attr=0xf, range=[0x0000000077279000-0x000000007727b000) (0MB)
[ 0.000000] EFI: mem19: type=4, attr=0xf, range=[0x000000007727b000-0x000000007727c000) (0MB)
[ 0.000000] EFI: mem20: type=7, attr=0xf, range=[0x000000007727c000-0x000000007727d000) (0MB)
[ 0.000000] EFI: mem21: type=4, attr=0xf, range=[0x000000007727d000-0x0000000077ce5000) (10MB)
[ 0.000000] EFI: mem22: type=7, attr=0xf, range=[0x0000000077ce5000-0x0000000077e1e000) (1MB)
[ 0.000000] EFI: mem23: type=4, attr=0xf, range=[0x0000000077e1e000-0x0000000077e5e000) (0MB)
[ 0.000000] EFI: mem24: type=7, attr=0xf, range=[0x0000000077e5e000-0x0000000077e5f000) (0MB)
[ 0.000000] EFI: mem25: type=4, attr=0xf, range=[0x0000000077e5f000-0x0000000078282000) (4MB)
[ 0.000000] EFI: mem26: type=7, attr=0xf, range=[0x0000000078282000-0x0000000078285000) (0MB)
[ 0.000000] EFI: mem27: type=4, attr=0xf, range=[0x0000000078285000-0x00000000784d2000) (2MB)
[ 0.000000] EFI: mem28: type=7, attr=0xf, range=[0x00000000784d2000-0x00000000785e5000) (1MB)
[ 0.000000] EFI: mem29: type=4, attr=0xf, range=[0x00000000785e5000-0x00000000785ff000) (0MB)
[ 0.000000] EFI: mem30: type=7, attr=0xf, range=[0x00000000785ff000-0x0000000078602000) (0MB)
[ 0.000000] EFI: mem31: type=4, attr=0xf, range=[0x0000000078602000-0x000000007874a000) (1MB)
[ 0.000000] EFI: mem32: type=7, attr=0xf, range=[0x000000007874a000-0x000000007874b000) (0MB)
[ 0.000000] EFI: mem33: type=4, attr=0xf, range=[0x000000007874b000-0x000000007874f000) (0MB)
[ 0.000000] EFI: mem34: type=7, attr=0xf, range=[0x000000007874f000-0x0000000078750000) (0MB)
[ 0.000000] EFI: mem35: type=4, attr=0xf, range=[0x0000000078750000-0x0000000078782000) (0MB)
[ 0.000000] EFI: mem36: type=7, attr=0xf, range=[0x0000000078782000-0x0000000078783000) (0MB)
[ 0.000000] EFI: mem37: type=4, attr=0xf, range=[0x0000000078783000-0x0000000078795000) (0MB)
[ 0.000000] EFI: mem38: type=7, attr=0xf, range=[0x0000000078795000-0x000000007879a000) (0MB)
[ 0.000000] EFI: mem39: type=4, attr=0xf, range=[0x000000007879a000-0x00000000798c1000) (17MB)
[ 0.000000] EFI: mem40: type=7, attr=0xf, range=[0x00000000798c1000-0x0000000079ad4000) (2MB)
[ 0.000000] EFI: mem41: type=2, attr=0xf, range=[0x0000000079ad4000-0x0000000079ada000) (0MB)
[ 0.000000] EFI: mem42: type=3, attr=0xf, range=[0x0000000079ada000-0x000000007a1c9000) (6MB)
[ 0.000000] EFI: mem43: type=5, attr=0x800000000000000f, range=[0x000000007a1c9000-0x000000007a1db000) (0MB)
[ 0.000000] EFI: mem44: type=5, attr=0x800000000000000f, range=[0x000000007a1db000-0x000000007a2c9000) (0MB)
[ 0.000000] EFI: mem45: type=6, attr=0x800000000000000f, range=[0x000000007a2c9000-0x000000007a302000) (0MB)
[ 0.000000] EFI: mem46: type=6, attr=0x800000000000000f, range=[0x000000007a302000-0x000000007a3c9000) (0MB)
[ 0.000000] EFI: mem47: type=0, attr=0xf, range=[0x000000007a3c9000-0x000000007a665000) (2MB)
[ 0.000000] EFI: mem48: type=0, attr=0xf, range=[0x000000007a665000-0x000000007a6dc000) (0MB)
[ 0.000000] EFI: mem49: type=10, attr=0xf, range=[0x000000007a6dc000-0x000000007a6f7000) (0MB)
[ 0.000000] EFI: mem50: type=10, attr=0xf, range=[0x000000007a6f7000-0x000000007a79f000) (0MB)
[ 0.000000] EFI: mem51: type=9, attr=0xf, range=[0x000000007a79f000-0x000000007a7e1000) (0MB)
[ 0.000000] EFI: mem52: type=9, attr=0xf, range=[0x000000007a7e1000-0x000000007a7ff000) (0MB)
[ 0.000000] EFI: mem53: type=4, attr=0xf, range=[0x000000007a7ff000-0x000000007a800000) (0MB)
[ 0.000000] EFI: mem54: type=7, attr=0xf, range=[0x0000000100000000-0x0000000100600000) (6MB)
[ 0.000000] EFI: mem55: type=11, attr=0x8000000000000001, range=[0x00000000f80f8000-0x00000000f80f9000) (0MB)
[ 0.000000] EFI: mem56: type=11, attr=0x8000000000000001, range=[0x00000000fed1c000-0x00000000fed20000) (0MB)
[ 0.000000] DMI 2.6 present.
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
[ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
[ 0.000000] No AGP bridge found
[ 0.000000] last_pfn = 0x100600 max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 0FFC00000 mask FFFC00000 write-protect
[ 0.000000] 1 base 000000000 mask F80000000 write-back
[ 0.000000] 2 base 07C000000 mask FFC000000 uncachable
[ 0.000000] 3 base 07B000000 mask FFF000000 uncachable
[ 0.000000] 4 base 07A800000 mask FFF800000 uncachable
[ 0.000000] 5 base 100000000 mask FE0000000 write-back
[ 0.000000] 6 base 110000000 mask FF0000000 uncachable
[ 0.000000] 7 base 108000000 mask FF8000000 uncachable
[ 0.000000] 8 base 104000000 mask FFC000000 uncachable
[ 0.000000] 9 base 102000000 mask FFE000000 uncachable
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] last_pfn = 0x7a800 max_arch_pfn = 0x400000000
[ 0.000000] initial memory mapped : 0 - 20000000
[ 0.000000] Base memory trampoline at [ffff880000098000] 98000 size 20480
[ 0.000000] init_memory_mapping: 0000000000000000-000000007a800000
[ 0.000000] 0000000000 - 007a800000 page 2M
[ 0.000000] kernel direct mapping tables up to 7a800000 @ 1fffd000-20000000
[ 0.000000] init_memory_mapping: 0000000100000000-0000000100600000
[ 0.000000] 0100000000 - 0100600000 page 2M
[ 0.000000] kernel direct mapping tables up to 100600000 @ 79ad4000-79ada000
[ 0.000000] RAMDISK: 37a3a000 - 37d15000
[ 0.000000] ACPI: RSDP 000000007a7fe014 00024 (v04 LENOVO)
[ 0.000000] ACPI: XSDT 000000007a7fe120 00084 (v01 LENOVO TP-8Q 00001140 PTEC 00000002)
[ 0.000000] ACPI: FACP 000000007a7eb000 000F4 (v03 LENOVO TP-8Q 00001140 PTL 00000002)
[ 0.000000] ACPI: DSDT 000000007a7ee000 0FC7E (v02 LENOVO SNB-CPT 00000000 INTL 20061109)
[ 0.000000] ACPI: FACS 000000007a73c000 00040
[ 0.000000] ACPI: ASF! 000000007a7ed000 000A5 (v32 LENOVO TP-8Q 00001140 PTL 00000002)
[ 0.000000] ACPI: HPET 000000007a7ea000 00038 (v01 LENOVO TP-8Q 00001140 PTL 00000002)
[ 0.000000] ACPI: APIC 000000007a7e9000 00098 (v01 LENOVO TP-8Q 00001140 PTL 00000002)
[ 0.000000] ACPI: MCFG 000000007a7e8000 0003C (v01 LENOVO TP-8Q 00001140 PTL 00000002)
[ 0.000000] ACPI: FACS 000000007a73c000 00040
[ 0.000000] ACPI: ASF! 000000007a7ed000 000A5 (v32 LENOVO TP-8Q 00001140 PTL 00000002)
[ 0.000000] ACPI: HPET 000000007a7ea000 00038 (v01 LENOVO TP-8Q 00001140 PTL 00000002)
[ 0.000000] ACPI: APIC 000000007a7e9000 00098 (v01 LENOVO TP-8Q 00001140 PTL 00000002)
[ 0.000000] ACPI: MCFG 000000007a7e8000 0003C (v01 LENOVO TP-8Q 00001140 PTL 00000002)
[ 0.000000] ACPI: SLIC 000000007a7e7000 00176 (v01 LENOVO TP-8Q 00001140 PTEC 00000001)
[ 0.000000] ACPI: TCPA 000000007a7e6000 00032 (v02 PTL LENOVO 06040000 LNVO 00000001)
[ 0.000000] ACPI: SSDT 000000007a7e5000 0073E (v01 PmRef Cpu0Ist 00003000 INTL 20061109)
[ 0.000000] ACPI: SSDT 000000007a7e4000 00996 (v01 PmRef CpuPm 00003000 INTL 20061109)
[ 0.000000] ACPI: UEFI 000000007a7e3000 0003E (v01 LENOVO TP-8Q 00001140 PTL 00000002)
[ 0.000000] ACPI: UEFI 000000007a7e2000 00042 (v01 PTL COMBUF 00000001 PTL 00000001)
[ 0.000000] ACPI: UEFI 000000007a7e1000 00292 (v01 LENOVO TP-8Q 00001140 PTL 00000002)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] No NUMA configuration found
[ 0.000000] Faking a node at 0000000000000000-0000000100600000
[ 0.000000] Initmem setup node 0 0000000000000000-0000000100600000
[ 0.000000] NODE_DATA [00000001005fb000 - 00000001005fffff]
[ 0.000000] [ffffea0000000000-ffffea00041fffff] PMD -> [ffff880074600000-ffff8800767fffff] on node 0
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000010 -> 0x00001000
[ 0.000000] DMA32 0x00001000 -> 0x00100000
[ 0.000000] Normal 0x00100000 -> 0x00100600
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[6] active PFN ranges
[ 0.000000] 0: 0x00000010 -> 0x0000008f
[ 0.000000] 0: 0x00000090 -> 0x000000a0
[ 0.000000] 0: 0x00000100 -> 0x00040000
[ 0.000000] 0: 0x00040200 -> 0x0007a1c9
[ 0.000000] 0: 0x0007a7ff -> 0x0007a800
[ 0.000000] 0: 0x00100000 -> 0x00100600
[ 0.000000] On node 0 totalpages: 501081
[ 0.000000] DMA zone: 64 pages used for memmap
[ 0.000000] DMA zone: 10 pages reserved
[ 0.000000] DMA zone: 3909 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 16320 pages used for memmap
[ 0.000000] DMA32 zone: 479242 pages, LIFO batch:31
[ 0.000000] Normal zone: 24 pages used for memmap
[ 0.000000] Normal zone: 1512 pages, LIFO batch:0
I'm not sure what to make of this. Do I need to remake the kernel for boot using mkinitcpio? Or do I need to repopulate /boot/efi/efi/grub/? I see there's some sort of inconsistency about memory. I'm wondering if one bit of the system is working with stale data about the installed RAM that I need to somehow update while the other bit is detecting the available RAM "live" and getting a different answer (since I've basically pulled 2*4G of RAM and installed 1*2G from a different source.)
Edit: I was getting this before my system went nuts with my previous memory installed and no problems. So worrying though it may be, I don't think it is more worrying than usual...
Last edited by cfr (2012-03-10 03:13:42)

Similar Messages

  • I just fix my macbook air because it was kernel panic. They changed the hard drive. I could not back up with Time Machine, because it did not work and I had over Adobe creative suite 5 design premium student. But I finished my studies last year and I'd li

    I just fix my macbook air because it was kernel panic. They changed the hard drive. I could not back up with Time Machine, because it did not work and I had over Adobe creative suite 5 design premium student. But I finished my studies last year and I'd like to know how to get the serial number for me to reinstall Adobe creative suite 5 design premium when I am no longer study because I would still like the used? It is not fair if I do anymore because I really need.

    You can download Creative Suite 5 here:
    Other downloads
    To deal with the issue of the serial number and using it again, you'll have to use Web Chat. Here's a link:
    Adobe ID, sign in, and account help
    See the bottom of the page for a link

  • Kernel Panics, Drive Corruption, Directory Issues.

    Desktop M8840LL/A Dual 1.25GHz PowerPC G4 (FW800) MDD
    2GB Ram, 2 WD - 500GB IDE Drives Internal, 4 SATA Dr (2 WD - 500 GB SATA internal 1 WD 500GB SATA, One WD 640GB SATA external ), Sonnet Tempo SATA X4i PCI Card, ATI 9600Pro AGP, 1- 23in Apple Cinema Display, One 24in Samsung Display. 3 Firewire 250Gb WD external Drives.
    This setup was running great for 2 years until a four year old WD drive failed 3 weeks ago and corrupted its data etc. I had the data backed up so no panic.
    I decided to replaced it 3 weeks ago with a new 500GB WD IDE and reinstall 10.5 and migrate users for that drive.
    Ever since I have been getting daily if not hourly kernel panics and issues with ALL drives on my system.
    At one point the system loscked 4 drives and I could not access them at all.
    Discussion group helped fix that issue.
    I have managed to saved all my important data to a 500GB drive without a system on it and hopefully can deal with the issues at hand without worrying about the data.
    Booted from my System 1.5 install disk and had a dark grey/ Must restart your mac screen while I was booting from the DVD!
    Did an Apple Service diagnostics on the machine and all was great - no issues.
    So I did a clean install on a drive and all looked great!
    No other software installed except the system.
    Rebooted OK.
    I then did the apple software update and restarted.
    No startup!
    Rebooted with option key down - no drives??
    I have been working on this for three days and seem to be going backwards at best.
    I can boot sometimes and usually get a kernal panic eventually.
    It can happen right away or an hour later.
    Sometimes I get a message "your computer was shut down etc" sometimes I don't!?
    Sometimes I get a startup chime - sometimes I don't!!??
    What should I do next?
    Advise whatever info you might need and I will do my best to provide it.

    I stripped my Mac down to barebones incluing original 80GB Drive 512 RAM and Original Video card and started over.
    To make a long procedure shorter I found that all hardware was OK and after running ASD to confirm I reinstalled all my hardware/Add ins except for drives.
    I then started to check each drive individually with Applejack and then formatting and reinstalling virgin systems on each drive.
    Applejack and/or the system DVD would not fix and/or install on three of the Hard Drives (1 IDE 500GB and 2 500GB SATA)due to permission corruption. I could not do anything with these drives at all!
    When I had these individual drives in the computer I experienced kernel panics with every one!
    All the drives were under warranty and Western Digital replaced all of them. (I cannot begin to tell you how great Western Digital was in turnaround time and cross shipping and help in this matter.) Their warranty service is the best I have ever experienced bar none!
    I am now running non stop for nearly a week without any kernel panic or problem whatsoever. I have also noticed a significant speed up in my computer.
    I have rebooted many times and run non stop for days at a time.
    I maintain my computer with maintenance scripts once per week and do it faithfully and this type of permission issue can still occur!
    Without my backups there would have been a disaster for me.
    Many thanks to all the peolpe that emailed help to me from all sources.
    Sometimes out of the worst of situations good prevails.

  • Please help diagnose kernel panics

    I'm having intermittent kernel panics on an Intel iMac (10.4.8). When they happen, it is always after a hotsync to a Palm Treo 680. I have never installed the Palm software, only MissingSync from MarkSpace. The sync looks like it's succeeded. MissingSync says it was fine, and the Treo has gone back to its normal hotsync screen. But just as that happens the panic occurs (sometimes). My guess is that it's when the Treo disconnects from the USB port. It's connected directly to a port on the back of the iMac. MarkSpace support had nothing obvious to suggest, other than uninstall, reset PRAM, repair disk, reinstall blah, blah. Can't see how this would help.
    Anyone know if the Treo needs a USB driver as such, that would presumably be supplied by Macos or MissingSync? The panic report follows. Any pointers gratefully accepted!
    panic(cpu 1 caller 0x001A3135): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
    CR0: 0x8001003b, CR2: 0x00000001, CR3: 0x00dd6000, CR4: 0x000006e0
    EAX: 0x00000001, EBX: 0x05249b00, ECX: 0x351e2000, EDX: 0x037ef260
    CR2: 0x00000001, EBP: 0x25643d18, ESI: 0x00000000, EDI: 0x0051b840
    EFL: 0x00010206, EIP: 0x0039929c, CS: 0x00000008, DS: 0x038a0010
    Backtrace, Format - Frame : Return Address (4 potential args on stack)
    0x25643ae8 : 0x128d1f (0x3c9540 0x25643b0c 0x131df4 0x0)
    0x25643b28 : 0x1a3135 (0x3cf1f4 0x1 0xe 0x3cea24)
    0x25643c38 : 0x19a8d4 (0x25643c50 0x764fe976 0x20 0x135920)
    0x25643d18 : 0x51bab0 (0x5249b00 0x51b840 0x545d000 0x0)
    0x25643d48 : 0x532a74 (0x545db00 0x545d000 0x0 0x1a1ec0)
    0x25643d68 : 0x3afe9c (0x545d000 0x4ac694 0x25643db8 0x197b11)
    0x25643d88 : 0x188174 (0x545d000 0x373a810 0x25643da8 0x19d23a)
    0x25643db8 : 0x12b4da (0x48badb4 0x48a08a8 0x0 0x0)
    0x25643df8 : 0x124b2b (0x48bad00 0x0 0x18 0x25643edc)
    0x25643f08 : 0x1955a1 (0x25643f44 0x0 0x0 0x0)
    0x25643fc8 : 0x19ad4e (0x3d26ae0 0x0 0x19d0b5 0x3748880) No mapping exists for frame pointer
    Backtrace terminated-invalid frame pointer 0xb0080288
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.iokit.IOUSBUserClient(2.6.0)@0x52f000
    dependency: com.apple.iokit.IOUSBFamily(2.6.1)@0x515000
    com.apple.iokit.IOUSBFamily(2.6.1)@0x515000
    Kernel version:
    Darwin Kernel Version 8.8.1: Mon Sep 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386
    Model: iMac5,1, BootROM IM51.0090.B03, 2 processors, Intel Core 2 Duo, 2.16 GHz, 2 GB
    Graphics: ATI Radeon X1600, ATY,RadeonX1600, PCIe, 128 MB
    Memory Module: BANK 0/DIMM0, 1 GB, DDR2 SDRAM, 667 MHz
    Memory Module: BANK 1/DIMM1, 1 GB, DDR2 SDRAM, 667 MHz
    AirPort: spairportwireless_card_type_airportextreme (0x14E4, 0x87), Broadcom BCM43xx 1.0 (4.80.79.1)
    Bluetooth: Version 1.7.9f12, 2 service, 1 devices, 1 incoming serial ports
    Network Service: Built-in Ethernet, Ethernet, en0
    Serial ATA Device: WDC WD1600JS-40TGB0, 149.05 GB
    Parallel ATA Device: MATSHITADVD-R UJ-846
    USB Device: Built-in iSight, Micron, Up to 480 Mb/sec, 500 mA
    USB Device: USB2.0 Hub Controller, NEC Corporation, Up to 480 Mb/sec, 500 mA
    USB Device: Mass Storage Device, Generic, Up to 480 Mb/sec, 500 mA
    USB Device: Bluetooth HCI, Up to 12 Mb/sec, 500 mA
    USB Device: IR Receiver, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA

    All modern USB devices rely upon standard device drivers included with the operating system. OS X has built-in USB device drivers. However, not all USB devices are necessarily compliant.
    As for the Treo I have no specific information on any incompatibilities with OS X when used with the proper software. If you use Missing Sync from MarkSpace just be sure you are using the most current version and that you don't also have Palm Desktop software installed as well. There is nothing specific in the panic.log file that points to The Missing Sync software directly, only that the panic was generated in one or more of the USB extensions.
    Visit The XLab FAQs and read the FAQ on diagnosing kernel panics for more information.
    I use Missing Sync with a Palm Tungsten E and it works fine on all my machines.
    Do you use any other USB devices and/or USB hubs?
    There are many possible causes of kernel panics. Corrupted device drivers and hardware defects are common causes. As I suggested before you would be wise to follow the suggestions given you by MarkSpace support.

  • Constant kernel panics since upgrade to 10.4.4. help!

    Well ive just spent the past 3 hours trying to figure out exactly what went wrong with my iBook, but it was Kernel Panicing like crazy. I couldnt even get online long enough to make a post about it.
    Lets recap.
    I updated to 10.4.4
    Several hours later the Mac crashes for the first time since I switched 3 months ago.
    It crashes again.
    Kernel panic!
    More kernel panics!
    So as soon as I logged in, I created a dummy account then rebooted with it. The dummy account would crash too so I knew that it was a system problem. This leads me to believe it was 10.4.4
    I did an archive and install.
    No luck
    Any thoughts? I have not installed any hardware. Its as it was prebuilt. It cant be a hardware problem.
    I installed shapeshifter several weeks ago and uninstalled it about 4 days ago.
    I did repair permissions after updating.
    Here is the crash report:
    panic(cpu 0 caller 0x000A8B98): Uncorrectable machine check: pc = 0000000022428A08, msr = 0000000000149030, dsisr = 00002429, dar = 00000000002F11B6
    AsyncSrc = 0000000000000000, CoreFIR = 0000000000000000
    L2FIR = 0000000000000000, BusFir = 0000000000000000
    Latest stack backtrace for cpu 0:
    Backtrace:
    0x00095544 0x00095A5C 0x0002683C 0x000A8B98 0x000A7E28 0x000ABB00
    Proceeding back via exception chain:
    Exception state (sv=0x2B220280)
    PC=0x22428A08; MSR=0x00149030; DAR=0x002F11B6; DSISR=0x00002429; LR=0x2242A724; R1=0x0D753CC0; XCP=0x00000008 (0x200 - Machine check)
    Backtrace:
    0x01FB4C60 0x2242A724 0x2243EFF0 0x002CD5B4 0x002CC47C 0x000A9694
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.iokit.AppleAirPort2(401.2)@0x22400000
    dependency: com.apple.iokit.IONetworkingFamily(1.5.0)@0x21592000
    dependency: com.apple.iokit.IOPCIFamily(1.6)@0x1d82e000
    Exception state (sv=0x22387780)
    PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
    Kernel version:
    Darwin Kernel Version 8.2.1: Fri Jun 24 23:31:10 PDT 2005; root:xnu-792.3.2.obj~1/RELEASE_PPCModel: PowerBook6,7, BootROM 4.9.3f0, 1 processors, PowerPC G4 (1.5), 1.33 GHz, 512 MB
    Graphics: ATI Mobility Radeon 9550, ATY,M12, AGP, 32 MB
    Memory Module: DIMM0/BUILT-IN, 512 MB, built-in, built-in
    AirPort: AirPort Extreme, 402.6 (3.90.34.0.p13)
    Modem: Jump, , V.92, Version 1.0,
    Bluetooth: Version 1.7.0f18, 2 service, 1 devices, 1 incoming serial ports
    Network Service: AirPort, AirPort, en1
    PCI Card: pci106b,4318, sppci_othernetwork, SLOT-B
    Parallel ATA Device: MATSHITACD-RW CW-8124,
    Parallel ATA Device: TOSHIBA MK8025GAS, 74.53 GB
    USB Device: Bluetooth HCI, , Up to 12 Mb/sec, 500 mA
    USB Device: Apple Internal Trackpad, Apple Computer, Up to 12 Mb/sec, 500 mA

    The kernel panic points to Airport. Either your Airport software is way out of date or your Airport card may not be properly seated or has failed. So the first thing to do is remove the Airport card. If the panics cease, then reinstall the Airport card and see what happens. If it panics again, then remove the Airport card.
    The next thing I would do is:
    Boot from your OS X Installer. Be sure to use the installer for the version of OS X you have installed. After the installer loads select Disk Utility from the Installer menu (or Utilities menu if using Tiger.) After DU loads select your OS X volume from the list on the left, click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now shutdown the computer for a couple of minutes and then restart normally.
    If DU reports errors it cannot fix, then you will need Disk Warrior (3.0.3 for Tiger) and/or TechTool Pro (4.1.1 for Tiger) to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
    The next thing I would do is download the 10.4.4 Combo Updater and reinstall the update. Then reinstall the Airport card and see if it works properly.
    I would suggest that before installing the update that you first boot into safe mode.

  • Powerbook G4 1Ghz,OSX 10.5.8 - Kernel Panic when downloading in Safari

    Revisiting this, as original discussion (August 2010) was archived.
    Original problem was kernel panics particularly when downloading in Safari. Various people had similar issues, and crash logs appeared to indicate Airport Card/Driver as issue - one respondent suggested replacing Airport Card.
    Having left this for a few months, and reverted to Tiger, I decided to give it one last try - purchased a second-hand A1027 Airport Extreme Card on Ebay, installed it (thanks iFfixit!), tested functionality (still in Tiger), then installed Leopard (new, fresh install from retail disk). Software Updated to 10.5.8 (via Ethernet for speed).
    Have been up and running in 10.5.8 for 4 days now - and all running beautifully. iLife 09 installed fine (no iMovie 09 though - failed min-spec).
    Have "thrashed" my 17" Powerbook constantly - this morning tried downloading combo update 10.5.8 - 759 MB - downloaded, verified and mounted fine.
    Leopard runs superbly - not incredibly fast, but appears to be at least as quick as Tiger - one definite improvement is the Airport speed, and strength of signal.
    Whilst I can't categorically state the the "new" Airport Card is the solution, it is the only thing changed in my configuration. Although the card itself appears identical to the one it replaced, I think this may have done the trick.
    Will continue to monitor, and post if any issues arise.
    17"  Powerbook now good for a few more years yet!
    JPRB

    Revisiting this, as original discussion (August 2010) was archived.
    Original problem was kernel panics particularly when downloading in Safari. Various people had similar issues, and crash logs appeared to indicate Airport Card/Driver as issue - one respondent suggested replacing Airport Card.
    Having left this for a few months, and reverted to Tiger, I decided to give it one last try - purchased a second-hand A1027 Airport Extreme Card on Ebay, installed it (thanks iFfixit!), tested functionality (still in Tiger), then installed Leopard (new, fresh install from retail disk). Software Updated to 10.5.8 (via Ethernet for speed).
    Have been up and running in 10.5.8 for 4 days now - and all running beautifully. iLife 09 installed fine (no iMovie 09 though - failed min-spec).
    Have "thrashed" my 17" Powerbook constantly - this morning tried downloading combo update 10.5.8 - 759 MB - downloaded, verified and mounted fine.
    Leopard runs superbly - not incredibly fast, but appears to be at least as quick as Tiger - one definite improvement is the Airport speed, and strength of signal.
    Whilst I can't categorically state the the "new" Airport Card is the solution, it is the only thing changed in my configuration. Although the card itself appears identical to the one it replaced, I think this may have done the trick.
    Will continue to monitor, and post if any issues arise.
    17"  Powerbook now good for a few more years yet!
    JPRB

  • Kernel panics, graphic file corruption with Firewire

    I've been having consistent problems with Firewire since I got my Mac Pro last year. I only recently narrowed it down to Firewire so I thought I'd write it up here for the record.
    I never actually solved the problem, just started using USB-2 instead and the issues went away.
    --I had been getting pretty consistent kernel panics while doing backups or large file transfers to an external FW drive. I tried a few different drives and cables and the panics were consistent.
    --I also noticed a strange problem where graphic files I'd backed up (TIFF, JPEG, etc.) would have these single-pixel horizontal streaks running through them. This was a little disconcerting because it wasn't picked up during verification, it was just there when I opened the backup file.
    I found lots of people with FW problems in these forums but none mentioned that strange file corruption I got.
    I'll try FW again after a future system software upgrade but I'm giving up on it for now.

    I've been having consistent problems with Firewire since I got my Mac Pro last year. I only recently narrowed it down to Firewire so I thought I'd write it up here for the record.
    I never actually solved the problem, just started using USB-2 instead and the issues went away.
    --I had been getting pretty consistent kernel panics while doing backups or large file transfers to an external FW drive. I tried a few different drives and cables and the panics were consistent.
    --I also noticed a strange problem where graphic files I'd backed up (TIFF, JPEG, etc.) would have these single-pixel horizontal streaks running through them. This was a little disconcerting because it wasn't picked up during verification, it was just there when I opened the backup file.
    I found lots of people with FW problems in these forums but none mentioned that strange file corruption I got.
    I'll try FW again after a future system software upgrade but I'm giving up on it for now.

  • Kernel panic - hard drive or corrupt journal system?

    Hi,
    My powerbook G4 shut down today with a kernel panic and now won't boot up (giving a kernel panic error after reaching the gray screen). The computer has been working fine, though the battery has run down, with the exception of not shutting down properly (I would have to power off manually). I tried various things to fix this (repair permissions, check hard drive, checking logs, etc.), but all those checked out and I could never get it figured out. I have been leaving the computer running because of this and it has been working fine. It is a stock G4 with no peripherals, except for a 1 GB RAM upgrade. The RAM was installed two years ago and tested strenuously with memtest with no issues.
    I did have my hard drive near full, as I didn't realize that this could case severe issues. It's probably too full to do a clean Archive and Install. My fault.
    I have reset my PMU/PRAM, but the computer won't boot up in safe mode or single-user mode. I get the following message at the end of single-user mode:
    Kernel version:
    Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007: root:xnu-792.24.17~1/RELEASE_PPC
    panic: We are hanging here ...
    Unfortunately, I do not have my backup disks with me right now, as I recently moved (I will have them in a couple weeks).
    There's some data on the computer it would be nice to pull off, but not absolutely essential. So my question is: Does this sound like a hard drive problem or a journal system/file system problem or something else? I hear no strange noises from the drive (the fan is a little noisy, though). What can I do at this point while I wait for my discs to arrive from across country?
    If this is a file problem, I have heard these are difficult to fix or even deal with in terms of data recovery, since the disk won't mount even in firewire target mode. Should I invest in a firewire external drive in order to create a bootable second drive? Purchase DiskWarrior? Create a bootable Linux CD? Any help would be appreciated!

    darksurtur:
    If you have the original HDD with which the computer was bought you likely have a failed HDD and should have it replaced with a newer, faster and large capacity HDD. The average life of an internal HDD is 3 to 5 years, and although it may not suddenly stop functioning after that performance gradually decreases until the drive fails completely.
    A too full drive can cause serious directory corruption which can in turn lead to data corruption and possible loss, and eventually a crash. You should maintain a minimum of 15% to total disk capacity (5 GB minimum on HDDs of 40 GB or less) as contiguous free space to allow for swap files and directory expansion.
    You should always maintain a current backup of everything you do not wish to lose as even a new HDD can fail suddenly. Using an external firewire drive and making a bootable clone using a utility like SuperDuper or Carbon Copy Cloner is an excellent way to accomplish this. Dr. Smoke's FAQ Backup and Recovery has excellent tips on backup strategies.
    Please do post back if you have further questions or comments.
    cornelius

  • Corrupt Encrypted Sparseimage, PrivateFrameworks and Kernel Panics

    Hi Maclovers,
    After a kernel panic my encrypted sparseimage with valuable data won't mount:
    # hdiutil attach sec3.bak.sparseimage
    hdiutil: attach failed - Defektes Image // german for 'corrupt image'
    Attaching the following string:
    0000b90: 2c45 0000 0000 0000 0000 0000 0000 0000 ,E..............
    0000ba0: 0000 0001 6364 7361 656e 6372 ....cdsaencr
    gives:
    diskimages-helper(11183) malloc: * vm_allocate(size=3190173696) failed (error code=3)
    diskimages-helper(11183) malloc: * error: can't allocate region
    diskimages-helper(11183) malloc: * set a breakpoint in szone_error to debug
    hdiutil: attach failed - Speicher kann nicht zugewiesen werden // german for 'memory not allocable'
    Okay, no problem I thought, Mac OS X builds on Open Source Software, so I can decrypt the sparseimage by hand (with perl) and rescue the needed data with a hexeditor.
    But, the DiskImages Framework (/System/Library/PrivateFrameworks/DiskImages.framework/DiskImages) is not Open Source
    From poking around with gdb and strings I learned that hdiutil uses sha,sha1,sha256,sha512 and md5. But I was unable to figure out
    - how the password is expanded for the 128 bit aes key (plain md5/sha0,1,256,512 won't work)
    - in which mode aes runs (ecb/cbc/ofb)
    Do you know it and can you give me a hint?
    Btw: from gdb:
    openssl related
    0x9194711c aes128_cbccipher
    0x9196cd9a aes128_cfb128cipher
    0x9196cddf aes128_ecbcipher
    0x9196ce39 aes128_ofbcipher
    calling from here?
    0x97e6ba5e CEncryptedEncoding::encodePasswordHeader(Security::CssmData const&, Security::CssmData const&, CEncryptedEncoding::PasswordHeader&)
    0x97e6bd72 CEncryptedEncoding::generateKeyBlob(Security::CssmAutoData&)
    0x97e6bece CEncryptedEncoding::parseKeyBlob(Security::CssmData const&)
    more functions
    0x91946660 AESset_encryptkey
    0x91946a5b AESset_decryptkey
    0x9194715c AEScbcencrypt
    0x919473df AES_encrypt
    0x91947880 AES_decrypt
    0x9194dd91 AEScfb128encrypt
    0x9194de42 AEScfbr_encryptblock
    0x9194df86 AEScfb1encrypt
    0x9194e046 AEScfb8encrypt
    0x9194e095 AESctr128encrypt
    0x9194e20b AESecbencrypt
    0x9194e232 AES_options
    0x9194e242 AESofb128encrypt
    Here's some debug info:
    si hdiutil attach -debug sec3.bak.sparseimage calling DIHLDiskImageAttach with
    <CFDictionary 0x3161a0 [0xa08011c0]>{type = mutable, count = 7, capacity = 8, pairs = (
    2 : <CFString 0x42898 [0xa08011c0]>{contents = "debug"} = <CFBoolean 0xa080188c [0xa08011c0]>{value = true}
    3 : <CFString 0x428d8 [0xa08011c0]>{contents = "drive-options"} = <CFDictionary 0x3160e0 [0xa08011c0]>{type = mutable, count = 0, capacity = 4, pairs = (
    5 : <CFString 0x42888 [0xa08011c0]>{contents = "verbose"} = <CFBoolean 0xa0801884 [0xa08011c0]>{value = false}
    6 : <CFString 0x42658 [0xa08011c0]>{contents = "agent"} = <CFString 0x42648 [0xa08011c0]>{contents = "hdiutil"}
    7 : <CFString 0x428b8 [0xa08011c0]>{contents = "main-url"} = <CFURL 0x316390 [0xa08011c0]>{type = 0, string = sec3.bak.sparseimage,
    base = <CFURL 0x3163f0 [0xa08011c0]>{type = 0, string = /Users/felix/Desktop/si/, base = (null)}}
    8 : <CFString 0x428c8 [0xa08011c0]>{contents = "image-options"} = <CFDictionary 0x316110 [0xa08011c0]>{type = mutable, count = 0, capacity = 4, pairs = (
    10 : <CFString 0x428a8 [0xa08011c0]>{contents = "quiet"} = <CFBoolean 0xa0801884 [0xa08011c0]>{value = false}
    2006-06-13 10:44:39.197 hdiutil[11290] using helper tool at "/System/Library/PrivateFrameworks/DiskImages.framework/Resources/diskimages-he lper".
    2006-06-13 10:44:39.232 hdiutil[11290] connectToFramework
    2006-06-13 10:44:39.233 hdiutil[11290] connectToFramework: about to ask proxy to perform operation
    status proc called: initialize
    2006-06-13 10:44:39.254 diskimages-helper[11291] _imageOptions: {"enable-keychain" = 1; }
    2006-06-13 10:44:39.254 diskimages-helper[11291] _driveOptions: {autodiskmount = 1; "unmount-timeout" = 0; }
    2006-06-13 10:44:39.254 diskimages-helper[11291] DIHelperAttach: initializing framework
    DILoadDriver: checking for disk image driver...DILoadDriver: DI_kextExists() returned 0x00000000 (0)...DIIsInitialized: returning NO2006-06-13 10:44:39.266 diskimages-helper[11291] DIHelperAttach: resolving disk image
    DIIsInitialized: returning YESDIIsInitialized: returning YESDIBackingStoreNewWithCFURL: entry with
    <CFURL 0x3208c0 [0xa08011c0]>{type = 15, string = file://localhost/Users/felix/Desktop/si/sec3.bak.sparseimage, base = (null)}
    <CFDictionary 0x30c1b0 [0xa08011c0]>{type = mutable, count = 2, capacity = 4, pairs = (
    0 : <CFString 0x406c0 [0xa08011c0]>{contents = "enable-keychain"} = <CFBoolean 0xa080188c [0xa08011c0]>{value = true}
    1 : <CFString 0x407b0 [0xa08011c0]>{contents = "image-path"} = <CFString 0x30c2e0 [0xa08011c0]>{contents = "/Users/felix/Desktop/si/sec3.bak.sparseimage"}
    DIBackingStoreInstantiatorProbe: entry
    <CFURL 0x3208c0 [0xa08011c0]>{type = 15, string = file://localhost/Users/felix/Desktop/si/sec3.bak.sparseimage, base = (null)}
    <CFDictionary 0x30c1b0 [0xa08011c0]>{type = mutable, count = 2, capacity = 4, pairs = (
    0 : <CFString 0x406c0 [0xa08011c0]>{contents = "enable-keychain"} = <CFBoolean 0xa080188c [0xa08011c0]>{value = true}
    1 : <CFString 0x407b0 [0xa08011c0]>{contents = "image-path"} = <CFString 0x30c2e0 [0xa08011c0]>{contents = "/Users/felix/Desktop/si/sec3.bak.sparseimage"}
    DIBackingStoreInstantiatorProbe: probing interface 0 CBSDBackingStore
    CBSDBackingStore::newProbe score 100 for file://localhost/Users/felix/Desktop/si/sec3.bak.sparseimage
    DIBackingStoreInstantiatorProbe: probing interface 1 CRAMBackingStore
    CRAMBackingStore::probe: scheme "file": not ram: or ramdisk: scheme.
    CRAMBackingStore::probe: score -1000 for file://localhost/Users/felix/Desktop/si/sec3.bak.sparseimage
    DIBackingStoreInstantiatorProbe: probing interface 2 CCarbonBackingStore
    CCarbonBackingStore::newProbe: setting initial rval to +100
    CCarbonBackingStore::newProbe score 100 for file://localhost/Users/felix/Desktop/si/sec3.bak.sparseimage
    DIBackingStoreInstantiatorProbe: probing interface 3 CDevBackingStore
    CDevBackingStore::newProbe: not /dev/disk or /dev/rdisk (/Users/felix/Desktop/si/sec3.bak.sparseimage).CDevBackingStore::newProbe score -1000 for
    DIBackingStoreInstantiatorProbe: probing interface 4 CCURLBackingStore
    CCURLBackingStore::probe: scheme is
    file
    CCURLBackingStore::probe: not recognized URL scheme.
    CCURLBackingStore::probe: score -1000 for file://localhost/Users/felix/Desktop/si/sec3.bak.sparseimage
    DIBackingStoreInstantiatorProbe: probing interface 5 CVectoredBackingStore
    CVectoredBackingStore::newProbe not "vectored" scheme.
    CVectoredBackingStore::newProbe score -1000 for file://localhost/Users/felix/Desktop/si/sec3.bak.sparseimage
    DIBackingStoreNewWithCFURL: CBSDBackingStore
    DIBackingStoreNewWithCFURL: instantiator returned 0
    DIBackingStoreNewWithCFURL: returning 0x00000000
    DIResolveURLToBackingStore: processing level 1 encodings.
    DIFileEncodingNewWithBackingStore: entry for encoding level 1
    DIFileEncodingInstantiatorProbe: entry for level 1
    <CFDictionary 0x30c1b0 [0xa08011c0]>{type = mutable, count = 2, capacity = 4, pairs = (
    0 : <CFString 0x406c0 [0xa08011c0]>{contents = "enable-keychain"} = <CFBoolean 0xa080188c [0xa08011c0]>{value = true}
    1 : <CFString 0x407b0 [0xa08011c0]>{contents = "image-path"} = <CFString 0x30c2e0 [0xa08011c0]>{contents = "/Users/felix/Desktop/si/sec3.bak.sparseimage"}
    DIFileEncodingInstantiatorProbe: probing level 1 interface 0 CMacBinaryEncoding
    CBSDBackingStore::openDataFork: about to open /Users/felix/Desktop/si/sec3.bak.sparseimage
    CBSDBackingStore::closeDataFork: about to close 500000000: 4e9d dbc8 b429 00eb e882 36a3 d561 9fbd | N....)....6..a.. |
    00000010: ed78 e737 a8bd 55cc f2f3 ad7a 42cd 7379 | .x.7..U....zB.sy |
    00000020: 0499 4256 7ae3 df72 f032 664d c214 074c | ..BVz..r.2fM...L |
    00000030: 1b84 2b0a b849 18c0 c65a dfd9 0ae8 c6dd | ..+..I...Z...... |
    00000040: b6db 15ee 39ce db43 f3cf 7a33 8628 d8b3 | ....9..C..z3.(.. |
    00000050: fefa 725e 148d ecda e728 3889 bcb2 bb27 | ..r^.....(8....' |
    00000060: 3d78 2e88 652f 8e27 71eb a44a 98ca 3148 | =x..e/.'q..J..1H |
    00000070: 0780 a593 0e20 6f81 c2a7 f17d 1d87 5b48 | ..... o....}..[H |
    diskimages-helper: fileNameLength $0000009D
    diskimages-helper: resourceForkLength $DAE72838
    diskimages-helper: dataForkLength $5E148DEC
    diskimages-helper: commentLength $00008865
    diskimages-helper: MacBinary III signature ?'q? (0x8E2771EB)
    diskimages-helper: header CRC $00001D87
    diskimages-helper: minimum decoder version $0000007D
    diskimages-helper: encoder version $000000F1
    no MacBinary III signature - checking for MacBinary I or IIDIFileEncodingInstantiatorProbe: probing level 1 interface 1 CAppleSingleEncoding
    CBSDBackingStore::openDataFork: about to open /Users/felix/Desktop/si/sec3.bak.sparseimage
    00000000: c8db 9d4e eb00 29b4 e882 36a3 d561 9fbd | ...N..)...6..a.. |
    00000010: ed78 e737 a8bd 55cc f3f2 ad7a 42cd 7379 | .x.7..U....zB.sy |
    00000020: 0499 4256 7ae3 .... .... .... .... .... | ..BVz........... |
    CBSDBackingStore::closeDataFork: about to close 5CAppleSingleEncoding::isAppleSingleFile loadAppleSingleHeader failed with error 22
    DIFileEncodingInstantiatorProbe: probing level 1 interface 2 CEncryptedEncoding
    CBSDBackingStore::openDataFork: about to open /Users/felix/Desktop/si/sec3.bak.sparseimage
    CBSDBackingStore::closeDataFork: about to close 5DIFileEncodingNewWithBackingStore: probe fails to find appropriate CFileEncoding class.
    DIFileEncodingNewWithBackingStore: returning 0x0000006A
    DIResolveURLToBackingStore: level 1 encoding match failed. 106.
    (continuing)
    DIResolveURLToBackingStore: processing level 2 encodings.
    DIFileEncodingNewWithBackingStore: entry for encoding level 2
    DIFileEncodingInstantiatorProbe: entry for level 2
    <CFDictionary 0x30c1b0 [0xa08011c0]>{type = mutable, count = 2, capacity = 4, pairs = (
    0 : <CFString 0x406c0 [0xa08011c0]>{contents = "enable-keychain"} = <CFBoolean 0xa080188c [0xa08011c0]>{value = true}
    1 : <CFString 0x407b0 [0xa08011c0]>{contents = "image-path"} = <CFString 0x30c2e0 [0xa08011c0]>{contents = "/Users/felix/Desktop/si/sec3.bak.sparseimage"}
    DIFileEncodingInstantiatorProbe: probing level 2 interface 0 CUDIFEncoding
    CBSDBackingStore::openDataFork: about to open /Users/felix/Desktop/si/sec3.bak.sparseimage
    CBSDBackingStore::closeDataFork: about to close 5CUDIFEncoding::newProbe: failing because backing store is not UDIF file
    DIFileEncodingNewWithBackingStore: probe fails to find appropriate CFileEncoding class.
    DIFileEncodingNewWithBackingStore: returning 0x0000006A
    DIResolveURLToBackingStore: level 2 encoding match failed. 106.
    (continuing)
    DIResolveURLToBackingStore: processing level 3 encodings.
    DIFileEncodingNewWithBackingStore: entry for encoding level 3
    DIFileEncodingInstantiatorProbe: entry for level 3
    <CFDictionary 0x30c1b0 [0xa08011c0]>{type = mutable, count = 2, capacity = 4, pairs = (
    0 : <CFString 0x406c0 [0xa08011c0]>{contents = "enable-keychain"} = <CFBoolean 0xa080188c [0xa08011c0]>{value = true}
    1 : <CFString 0x407b0 [0xa08011c0]>{contents = "image-path"} = <CFString 0x30c2e0 [0xa08011c0]>{contents = "/Users/felix/Desktop/si/sec3.bak.sparseimage"}
    DIFileEncodingInstantiatorProbe: probing level 3 interface 0 CSegmentedNDIFEncoding
    checkTypeCreator: /
    checkTypeCreator: returning , score 0
    CSegmentedNDIFEncoding::isSegmentedNDIFFile checkTypeCreator failed
    DIFileEncodingInstantiatorProbe: probing level 3 interface 1 CSegmentedUDIFEncoding
    CSegmentedUDIFEncoding::isSegmentedUDIFFile backing store is not of type CUDIFEncoding
    DIFileEncodingInstantiatorProbe: probing level 3 interface 2 CSegmentedUDIFRawEncoding
    DIFileEncodingNewWithBackingStore: probe fails to find appropriate CFileEncoding class.
    DIFileEncodingNewWithBackingStore: returning 0x0000006A
    DIResolveURLToBackingStore: level 3 encoding match failed. 106.
    (continuing)
    DIIsInitialized: returning YESDIDiskImageNewWithBackingStore: entry with
    <CFDictionary 0x30c1b0 [0xa08011c0]>{type = mutable, count = 2, capacity = 4, pairs = (
    0 : <CFString 0x406c0 [0xa08011c0]>{contents = "enable-keychain"} = <CFBoolean 0xa080188c [0xa08011c0]>{value = true}
    1 : <CFString 0x407b0 [0xa08011c0]>{contents = "image-path"} = <CFString 0x30c2e0 [0xa08011c0]>{contents = "/Users/felix/Desktop/si/sec3.bak.sparseimage"}
    DIDiskImageInstantiatorProbe: entry
    <CFDictionary 0x30c1b0 [0xa08011c0]>{type = mutable, count = 2, capacity = 4, pairs = (
    0 : <CFString 0x406c0 [0xa08011c0]>{contents = "enable-keychain"} = <CFBoolean 0xa080188c [0xa08011c0]>{value = true}
    1 : <CFString 0x407b0 [0xa08011c0]>{contents = "image-path"} = <CFString 0x30c2e0 [0xa08011c0]>{contents = "/Users/felix/Desktop/si/sec3.bak.sparseimage"}
    DIDiskImageInstantiatorProbe: probing interface 0 CDARTDiskImage
    DIDiskImageInstantiatorProbe: probing interface 1 CDiskCopy42DiskImage
    DIDiskImageInstantiatorProbe: probing interface 2 CNDIFDiskImage
    checkTypeCreator: /
    checkTypeCreator: returning , score 0
    CNDIFDiskImage::checkExtension: sparseimage
    CNDIFDiskImage::newProbe: checkExtension gives score -1000.
    DIDiskImageInstantiatorProbe: probing interface 3 CUDIFDiskImage
    CUDIFDiskImage::checkBackingStoreType: backing store is wrong type
    DIDiskImageInstantiatorProbe: probing interface 5 CRawDiskImage
    checkBackingStoreType returned score 0 type
    checkTypeCreator returned score 0 type
    CRawDiskImage::checkExtension: sparseimage
    checkExtension returned score -1000 type
    CRawDiskImage::newWithBackingStore: setBackingStore() failed. 106
    CRawDiskImage: checkBackingStoreLength score: -100
    DIDiskImageInstantiatorProbe: probing interface 6 CShadowedDiskImage
    DIDiskImageInstantiatorProbe: probing interface 7 CSparseDiskImage
    CSparseDiskImage::checkExtension: sparseimage
    DIDiskImageInstantiatorProbe: probing interface 8 CCFPlugInDiskImage
    DIDiskImageInstantiatorProbe: probing interface 9 CWrappedDiskImage
    DIBackingStore::inUse: this->_fUniqueID
    <CFArray 0x320590 [0xa08011c0]>{type = immutable, count = 1, values = (
    0 : <CFString 0x320dc0 [0xa08011c0]>{contents = "d234881026:i316148"}
    DI_kextCreateDiskImageIdentifierArray: exiting
    <CFArray 0x31fd00 [0xa08011c0]>{type = mutable-small, count = 1, values = (
    0 : <CFDictionary 0x321100 [0xa08011c0]>{type = fixed-mutable, count = 1, capacity = 1, pairs = (
    3 : <CFString 0x321000 [0xa08011c0]>{contents = "writeable-components"} = <CFArray 0x320fe0 [0xa08011c0]>{type = fixed-mutable, count = 1, capacity = 1, values = (
    0 : <CFString 0x321080 [0xa08011c0]>{contents = "d234881026:i1808676"}
    DIBackingStore::inUse: checking against image dictionary array
    <CFArray 0x3210f0 [0xa08011c0]>{type = immutable, count = 1, values = (
    0 : <CFDictionary 0x321100 [0xa08011c0]>{type = fixed-mutable, count = 1, capacity = 1, pairs = (
    3 : <CFString 0x321000 [0xa08011c0]>{contents = "writeable-components"} = <CFArray 0x320fe0 [0xa08011c0]>{type = fixed-mutable, count = 1, capacity = 1, values = (
    0 : <CFString 0x321080 [0xa08011c0]>{contents = "d234881026:i1808676"}
    DIBackingStore::inUse: checking our list looking for who's naughty and nice
    DIBackingStore::inUse: checking image 0000
    CBSDBackingStore::openDataFork: about to open /Users/felix/Desktop/si/sec3.bak.sparseimage
    syncPhysicalAndLogicalForkLengths: returning 0 (cached logEOF: 1540853760, physEOF: 1540853760)
    CBSDBackingStore::closeDataFork: about to close 5CSparseFile::~CSparseFile: WARNING flushing header and index nodes failed. Invalid argument
    syncPhysicalAndLogicalForkLengths: entry (cached logEOF: 1540853760, physEOF: 1540853760)
    : returning 0 (new cached logEOF: 1540853760, physEOF: 1540853760)
    DIDiskImageNewWithBackingStore: returning 0x00000067
    DIResolveBackingStoreToDiskImage: unable to resolve to any disk image class. 103.
    DIResolveURLToDiskImage: resolving disk image format failed. 103.
    status proc called: attach
    error code: 103
    status proc called: cleanup
    2006-06-13 10:44:39.684 diskimages-helper[11291] DIHelperAttach performOperation: returning 103
    2006-06-13 10:44:39.684 diskimages-helper[11291] DIHelper perform_operation: returning {payload = {}; "result-code" = 103; }
    2006-06-13 10:44:39.684 hdiutil[11290] connectToFramework: proxy has finished operation
    2006-06-13 10:44:39.685 hdiutil[11290] results are: {payload = {}; "result-code" = 103; }
    2006-06-13 10:44:39.685 hdiutil[11290] _threadResultsError is 103
    2006-06-13 10:44:39.685 hdiutil[11290] connectToFramework: terminating proxy
    2006-06-13 10:44:39.686 diskimages-helper[11291] terminateHelper
    DIHLDiskImageAttach() returned 103
    <CFDictionary 0x3245a0 [0xa08011c0]>{type = immutable, count = 0, capacity = 0, pairs = (
    hdiutil: attach failed - Defektes Image
    si 2006-06-13 10:44:39.786 diskimages-helper[11291] -DIHelperAgentMaster terminateUIAgentConnection
    2006-06-13 10:44:39.786 diskimages-helper[11291] -exitIfPossible:0 (_drivesServed 0)
    2006-06-13 10:44:39.787 diskimages-helper[11291] -exitWatchThread: trying to get exit lock
    2006-06-13 10:44:39.787 diskimages-helper[11291] -exitWatchThread: got exit lock
    2006-06-13 10:44:39.787 diskimages-helper[11291] -exitWatchCompleted:0
    2006-06-13 10:44:40.788 diskimages-helper[11291] suicide:<NSCFTimer: 0x3217d0>
    cheers, felix
    MBP 15" Mac OS X (10.4.6)

    The key expansion does not work with a substring of the upper hash functions. Create a sparseimage with the password asdf and try the following script:
    #!/opt/local/bin/perl
    use Crypt::GCrypt;
    my $tmp;
    my $i;
    my $subkey;
    # asdf
    %pw = (
    ph => (pack "H*", "61736466000000000000000000000000"),
    pl => (pack "H*", "00000000000000000000000061736466"),
    md5 => (pack "H*", "912ec803b2ce49e4a541068d495ab570"),
    sha1 => (pack "H*", "3da541559918a808c2402bba5012f6c60b27661c"),
    sha => (pack "H*", "71f2cbe0db64c15e9e385525ad5ef854c494898f"),
    sha256 => (pack "H*", "f0e4c2f76c58916ec258f246851bea091d14d4247a2fc3e18694461b1816e13b"),
    sha512 => (pack "H*", "401b09eab3c013d4ca54922bb802bec8fd5318192b0a75f201d8b3727429080fb337591abd3e44 453b954555b7a0812e1081c39b740293f765eae731f5a65ed1"),
    open (INFILE, "< $ARGV[0]") or die "Could not open $filename for reading: $!";
    read(INFILE,$tmp,128);
    close INFILE;
    foreach my $key (keys %pw) {
    for($i=16;$i <= length $pw{$key};$i++) {
    $subkey = substr($pw{$key},$i-16,16);
    #print "------using $key with $pw{$key} and substr $subkey-------";
    $cipher = Crypt::GCrypt->new(
    type => 'cipher',
    algorithm => 'aes',
    mode => 'ecb'
    $cipher->start('decrypting');
    $cipher->setkey($subkey);
    print $cipher->decrypt($tmp);
    }

  • SA_MAGIC header corrupt on ZFS causing kernel panic in S11.1 SRU5.5

    I have a number of Sun Fire x4500s and x4540s running S11.1 SRU5.5. One of the x4540s has recently started kernel panicking within minutes of powering on and sharing its file systems over NFS (it provides user directories for a computing cluster). If I don't share via NFS, the kernel panics do not occur.
    When I run mdb on the kernel panic coredump I get:
    \> ::panicinfo
    cpu 1
    thread fffffffc80e52c20
    message
    assertion failed: BSWAP_32(hdr->sa_magic) == SA_MAGIC, file: ../../common/fs/zfs/sa.c, line: 2079
    \> ::stack
    vpanic()
    0xfffffffffbac1081()
    sa_get_field64+0x96(ffffc1c0aaf34a00, 18)
    zfs_space_delta_cb+0x46(2c, ffffc1c0aaf34a00, fffffffc80e52840, fffffffc80e52848)
    dmu_objset_userquota_get_ids+0xca(ffffc1c1085d9008, 0, ffffc1c080796640)
    dnode_sync+0xa7(ffffc1c1085d9008, ffffc1c080796640)
    dmu_objset_sync_dnodes+0x7f(ffffc1c0299a5b00, ffffc1c0299a5a80, ffffc1c080796640)
    dmu_objset_sync+0x1e2(ffffc1c0299a5940, ffffc1c07f0d17c8, ffffc1c030756680, ffffc1c080796640)
    dsl_dataset_sync+0x63(ffffc1c0418cd300, ffffc1c07f0d17c8, ffffc1c080796640)
    dsl_pool_sync+0xdb(ffffc1c0285493c0, 2c720a)
    spa_sync+0x395(ffffc1c01b1f6a80, 2c720a)
    txg_sync_thread+0x244(ffffc1c0285493c0)
    thread_start+8()In doing some google searching, I'm able to infer from similar lines of code in OpenSolaris (and various ZFS derivatives) that the point of this line of code is to ensure that a ZFS block has a particular header with the correct endianness. Lines of code just prior to this swap the endianness if its is incorrect (at least in these derivatives). For example:
    [ZFS corruption probably from bad RAM|https://github.com/zfsonlinux/spl/issues/157]
    [FreeBSD kernel panic|http://lists.freebsd.org/pipermail/freebsd-stable/2012-July/068882.html]
    [ZFSOnLinux Panic|https://github.com/zfsonlinux/zfs/issues/1303]
    So basically, this assert ought to work unless the header was written to disk incorrectly. I've recently done a resilver since a disk had failed and I'm currently in the middle of a scrub with estimated 90h to go. It did fix about 12kb of mistakes on the scrub even though it was right after the resilver.
    Nevertheless, I don't think this should be able to happen unless the redundant copies of this header were also corrupted.
    I wrote a little script that loops over process IDs and addresses in the core dump and prints this for each
    echo $addr | awk '{print $1,"::pfiles"}' | mdb $DMPNO
    The files that are open are all device files (eg./devices/pseudo/...) or things in /var, /etc, /lib, things like that. The user directories/files do not appear to be actively open in the core dump. That said, I cannot match the thread above to a process ID. So maybe there are open files that are not captured in the core dump
    Since the machine will panic when I make NFS available, I am currently doing two things to try to resolve the problem:
    (1) a zpool scrub
    (2) "zfs send"ing a snapshot of every filesystem straight to /dev/null
    The idea behind (2) is that eventually I'll read the bad block and force the kernel panic to happen. I'll infer from the log of the script which filesystem is bad and NFS share all the others.
    You should assume that I can spell mdb, but not much more than that and everything I've done thus far has been mimicking things I have found in google searching.
    Thanks for any advice the community has to help me fix the bad file/filesystem. I am happy to provide more details from mdb or whatever is needed.
    Tom
    Edited by: 998996 on Apr 9, 2013 7:13 AM
    Edited by: 998996 on Apr 9, 2013 7:13 AM
    Edited by: 998996 on Apr 9, 2013 7:14 AM
    Edited by: 998996 on Apr 9, 2013 7:18 AM
    Edited by: 998996 on Apr 9, 2013 8:48 AM

    The output of fmdump is below. On March 27th, 3 disks were automatically identified as having too many errors and were pulled from their zpools. I replaced them on April 2nd (I believe) and, while they were resilvering, kernel panics started happening on April 6th. After several panic / reboot cycles, I disabled NFS and have not experienced any panics sense. The resilver finished sometime on April 7th (I think) and I started a zpool scrub relatively soon thereafter.
    Mar 27 11:21:05.6894 2b5fca6d-8a55-6a16-d59a-86abf600ce1e DISK-8000-0X Diagnosed
    Mar 27 11:21:18.2224 335f323c-c723-e67f-c194-a346edde5f41 DISK-8000-0X Diagnosed
    Mar 27 11:21:43.8004 f515a18e-235d-c9e8-9b11-ff7284ed1b48 DISK-8000-0X Diagnosed
    Mar 31 12:27:08.8977 864387c6-9b50-6f90-d710-9e213a0ba327 SUNOS-8000-KL Diagnosed
    Apr 02 15:37:45.7040 2b5fca6d-8a55-6a16-d59a-86abf600ce1e FMD-8000-58 Updated
    Apr 02 15:37:45.8345 335f323c-c723-e67f-c194-a346edde5f41 FMD-8000-58 Updated
    Apr 02 15:37:45.9517 f515a18e-235d-c9e8-9b11-ff7284ed1b48 FMD-8000-58 Updated
    Apr 02 15:50:44.1012 2b5fca6d-8a55-6a16-d59a-86abf600ce1e FMD-8000-4M Repaired
    Apr 02 15:50:44.1429 2b5fca6d-8a55-6a16-d59a-86abf600ce1e FMD-8000-6U Resolved
    Apr 02 15:51:00.5162 f515a18e-235d-c9e8-9b11-ff7284ed1b48 FMD-8000-4M Repaired
    Apr 02 15:51:00.5614 f515a18e-235d-c9e8-9b11-ff7284ed1b48 FMD-8000-6U Resolved
    Apr 02 15:51:18.9518 335f323c-c723-e67f-c194-a346edde5f41 FMD-8000-4M Repaired
    Apr 02 15:51:18.9959 335f323c-c723-e67f-c194-a346edde5f41 FMD-8000-6U Resolved
    Apr 02 15:55:22.0946 1ccd6f62-7607-6f63-9069-9d947691df4b ZFS-8000-LR Diagnosed
    Apr 02 15:56:14.7847 f8d032c1-5d6e-e742-f01a-e2f38ccc6ce8 ZFS-8000-QJ Diagnosed
    Apr 02 15:59:05.6633 5564cf7e-3648-cd69-915f-9b6757509bae ZFS-8000-QJ Diagnosed
    Apr 02 15:59:05.8154 0214c0e7-59b6-47ca-c8c6-853d76713257 ZFS-8000-D3 Diagnosed
    Apr 02 16:01:14.5517 513db3ba-27a7-c8f2-f50e-8ef58c0fa71c ZFS-8000-QJ Diagnosed
    Apr 06 05:49:43.6917 eddb3a8f-9117-cfa8-8784-a1fceb242f7f SUNOS-8000-KL Diagnosed
    Apr 06 06:44:24.2562 6186711a-735a-67f7-9226-be419378c70e SUNOS-8000-KL Diagnosed
    Apr 06 07:20:45.2416 33b36e54-c2cd-ee0e-b370-821a00d342fe SUNOS-8000-KL Diagnosed
    Apr 06 08:05:29.7940 a7f6d49b-6b15-ef5a-ca58-911e2c6b1196 SUNOS-8000-KL Diagnosed
    Apr 06 08:28:06.7965 e4eea2e9-c800-e1c9-bd53-c45af9b616b0 SUNOS-8000-KL Diagnosed
    Apr 06 08:56:21.9017 a51779c9-549a-4334-f102-d26ff958c566 SUNOS-8000-KL Diagnosed
    Apr 06 09:26:33.7999 25e4e137-7962-e70f-ea91-f77dfdd8238b SUNOS-8000-KL Diagnosed
    Apr 06 09:47:56.5975 2d416320-f69e-e5c5-ea66-cafab1997546 SUNOS-8000-KL Diagnosed
    Apr 06 10:19:35.7141 ae4e7ef4-bbf5-e80a-8e30-8a99bafbc352 SUNOS-8000-KL Diagnosed
    Apr 06 11:07:14.7489 abc3c89c-d9f9-ee00-e546-99cbff435810 SUNOS-8000-KL Diagnosed
    Apr 06 11:51:31.1321 7aa0ab5e-d54c-4201-e56f-e8a502bb063e SUNOS-8000-KL Diagnosed
    Apr 06 12:17:42.4073 46d85a95-8f15-c0ea-e061-f241628d124a SUNOS-8000-KL Diagnosed
    Apr 06 12:48:15.4996 d16c0c54-33d5-c463-dae8-fc8cc82e517b SUNOS-8000-KL Diagnosed
    Apr 06 13:14:45.4799 021e8659-5359-edea-c7e9-8551c7de6d2c SUNOS-8000-KL Diagnosed
    Apr 06 13:51:56.5406 89620151-c97f-4256-8347-f412ee416282 SUNOS-8000-KL Diagnosed
    Apr 06 14:11:47.2594 b9923bc1-46d6-4fb6-ec7d-f3a1e0076419 SUNOS-8000-KL Diagnosed
    Apr 07 12:54:49.3759 513db3ba-27a7-c8f2-f50e-8ef58c0fa71c FMD-8000-4M Repaired
    Apr 07 12:54:49.4121 513db3ba-27a7-c8f2-f50e-8ef58c0fa71c FMD-8000-6U Resolved
    Apr 07 12:54:49.5092 0214c0e7-59b6-47ca-c8c6-853d76713257 FMD-8000-4M Repaired
    Apr 07 12:54:49.5368 0214c0e7-59b6-47ca-c8c6-853d76713257 FMD-8000-6U Resolved
    Apr 07 12:54:49.5864 5564cf7e-3648-cd69-915f-9b6757509bae FMD-8000-4M Repaired
    Apr 07 12:54:49.6064 5564cf7e-3648-cd69-915f-9b6757509bae FMD-8000-6U Resolved
    Apr 07 12:54:49.6367 f8d032c1-5d6e-e742-f01a-e2f38ccc6ce8 FMD-8000-4M Repaired
    Apr 07 12:54:49.6498 f8d032c1-5d6e-e742-f01a-e2f38ccc6ce8 FMD-8000-6U Resolved
    Apr 07 12:54:49.7409 1ccd6f62-7607-6f63-9069-9d947691df4b FMD-8000-4M Repaired
    Apr 07 12:54:49.7585 1ccd6f62-7607-6f63-9069-9d947691df4b FMD-8000-6U Resolved
    The output of fmadm faulty and fmdump -eV are quite long:
    https://pantherfile.uwm.edu/downes/public/fmdump_ev.txt
    https://pantherfile.uwm.edu/downes/public/fmadm_faulty.txt
    I note a number of events on April 9th in the output of fmdump -eV. Maybe these are the scrub fixing things?
    Tom

  • Kernel panic - corrupt stack

    My iBook g4 has a kernel panic (below text).
    It did a '3 beeb, flash light 5 times' crash last week but then re-booted fine. About 4 months ago, this happened repeatedly and the 'power down now' error message appeared on a black screen. Finally it refused to boot up at all and we took it apart and found a loose connection inside (I don't know what it was), reattached it and it has worked fine since.
    Am worried as I have stupidly not backed up recently and have a website on there that is due to posted. Please help!
    <start>
    System failure: cpu=0; code=00000001 (Corrupt stack)
    Latest crash info for cpu 0:
    Exception state (sv=0x19DC1000)
    PC=0x000940A0; MSR0x00001030; DAR=0x00000000; DSIR=0x42000000; LR=0x00093F8C; R1=0xFFFFFEE0; XCP=0x00000098 (System failure)
    Backtrace:
    backtrace terminated - frame not mapped or invalid: 0xFFFFFEE0
    Proceeding back via exemption chain:
    Exception state (sv0x19DC1000)
    PC=0x00094160; MSR=0x00001030; DAR=0x00000000; DSISR=0x42000000; LR=0x0009413C; R1=0x00000000; XCP=0x00000000C (0x300 - Data access)
    Exception state (sv0x19B6CC80)
    PC=0x90026BC8; MSR=0x0200F030; DAR=0x003B7018; DSISR=0x42000000; LR=0x90008DC0; R1=0xBFFFEB40; XCP=0x000000030 (0xC00 - System call)
    Kernel version:
    Darwin kernel version 7.9.0:
    Wed Mar 30 28:11:17 PST 2005; root:xnu/xnu-517.12.7.obj-1/RELEASE_PPC
    Memory access exception (1,0,0)
    ethernet MAC address: 00:00:00:00:00:00
    ip address: 0.0.0.0
    Waiting for remote debugger connection
    <end>
    iBook G4   Mac OS X (10.4.10)  

    First, sorry for the delay, I only work a few days a week
    Second, there is no panic.log on any of the machines. I looked in the console and system profiler programs in all the directories and searched in terminal using 'find / -name panic.log 2> /dev/null'. That is one reason I had to take a picture of it. I will try hard to get a panic.log.
    Keep in mind that these are very hard lockups so I am wondering if the kernel even CAN sync the log to disk in this situation. However, I come from the Linux world and am fairly new to Macs so perhaps I am expecting it to be a hardware problem when software really can make a Mac Kernel lockup.
    Furthermore they are networked together, we use LDAP/NFS home directories but each machine was prepared with it's own local copy of CS2. There is no sharing of the application.
    Also, i tried a boot with apple-v but all went well and there were no out of place message.
    Since my first posting I have also tried an fsck which revealed nothing but a clean FS.
    Also, we do use radmind to help clone machines. The OS was installed manually with our application loaded using radmind templates.
    We do use our Macs very heavily and use many applications at once using all RAM and heavy swap. Do the Mac Minis not like to be exercised hard? I think I may try to use a 1GB stick in a machine and see if that helps.
    Also, could CS2 really cause a complete lockup of the machine with a corrupt stack? To me an application-level program should never cause the machine to freeze or should never be able to corrupt memory it doesnt own unless the OS lets it meddle with hardware.

  • Kernel Panics: Corrupt Skip Lists

    I recently upgraded my eMac's hard drive to a 160 GB hard drive. Before my eMac was very stable. I experienced maybe one or two kernel panics before upgrading. Now, they are a frequent experience. The curious thing is that all report the same error- "Corrupt Skip Lists". Yet, I cannot find any reference to this error anywhere. Also, I was running Panther before upgrading and switched to Tiger after installing the new drive. I suppose this could also be a factor. The odd thing is that these occur even when it's not running (has booted) off the new internal drive sometimes.
    Here are some screen shots I've taken:
    http://gamoe.net/imagebank/Other/eMacError/KernelPanic1.jpg
    http://gamoe.net/imagebank/Other/eMacError/KernelPanic2.jpg
    Any clues on this?

    Interesting. A topic probably only for the more technically minded. Thank you for your response. I hadn't gotten any leads until now, even though I've posted about this elsewhere. Of course I added more RAM, it's the only decent thing to do, given Apple's traditional skimping on built-in/included RAM.
    So I did as you suggested. I dug up the Apple Hardware Test CD, but it came up with nothing. I then downloaded and ran Memtest in the suggested single user mode under root. I had no idea it would take as long as it did, though I should have known, as it is an thorough test. I used the default suggested 3 passes. Results are as follows.
    Test 1 gave me:
    Bit Flip: FAILURE: 0xfffff3ff != 0xfffff7ff at offset 0x02c53b8b.
    Test 3 gave me:
    Stuck Address: FAILURE: possible bad address line at offset 0x00e52b8b.
    Resulting in these conclusions:
    * Address Test Failed * One or more DIMM address lines are non-functional.
    * Memory Test Failed * Please check logfile for details.
    Actually, I really have had no way of knowing if it was the hard drive or not. When I upgraded I also switched to Tiger, so it could be either. I must say that I am more a little surprised at the results, given that I installed this memory almost immediately after I bought the eMac, and it is Crucial RAM, which is known for quality, and it is the same RAM Apple uses for Macs. I've had absolutely no problems like this in the two years plus I've been using my eMac, under different versions of Mac OS X.
    Given these results, can one reasonably conclude that the memory is responsible for the kernel panics? And, provided that the eMac has panicked even when it has not been booted up from the new internal drive, would you completely rule out the internal hard drive as the cause?-- Or can there be more to this?

  • Working with my 2 FireWire HD i had a crash. the only way to start was a safe start. then id maged to start from a DVD and install a MAC OS 10.3 wich ran 4 some time then the same problem only safeMode. kernel panic inserted the tech tool DVD

    working with my 2 FireWire HD i had a crash. the only way to start was a safe start. then id maged to start from a DVD and install a MAC OS 10.3 wich ran 4 some time then the same problem only safeMode. kernel panic by inserting the tech tool DVD, wich produces the following highligted text:
    panic(cpu 0 caller =xffff0003): 0x300 - Data access
    latest stack backtrace for CPU 0:
    Backtrace:
    0x0009CC88 0x00D63C 0x00029DAO  0x000BOA10 0x000B4270
    proceeding back via exception chain:
    Exception state (sv=0x26acd700)
    PC=0x2717E900; MSR=0x00009030; DAR=0x00000000; DSISR=0x40000000; LR=0x2717EBE4; R1=0x26AD3AE0; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x27178B0 0x00344ACB 0x00345970 0x2717EC08 0x2718458 0x00340590
    0x003496EC 0x0034B59C 0x0034A6BC 0x000B1DD4
    Kernel Loadable modules in backtrace (with dependencies):
    com.apple.driver.AppleFWDHC1(3.9.5)00x2717c000->0x271aafff
    dependency: com.apple.iokit.10PCIFamily(2.6)00x1e840000
    dependency: com.apple.iokit.I0FireWireFamily(3.4.7)00x270dd000
    Exception state (sv=0x26abd280)
    PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000;R1=0x00000000; XCP=0x00000000 (unknown)
    BSD process name corresponding to current thread: kernel_task
    so what
    greetings from berlin

    Greetings,
    It appears to be a FW problem, possibly flaky case, or drive problem.
    One way to test is to Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, Test for problem in Safe Mode...
    PS. Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive
    Reboot, test again.
    If it only does it in Regular Boot, then it could be some hardware problem like Video card, (Quartz is turned off in Safe Mode), or Airport, or some USB or Firewire device, or 3rd party add-on, Check System Preferences>Accounts (Users & Groups in later OSX versions)>Login Items window to see if it or something relevant is listed.
    Check the System Preferences>Other Row, for 3rd party Pref Panes.
    Also look in these if they exist, some are invisible...
    /private/var/run/StartupItems
    /Library/StartupItems
    /System/Library/StartupItems
    /System/Library/LaunchDaemons
    /Library/LaunchDaemons

  • Aperture Kernel Panics & Fusion Disk Corruptions

    We have a  new iMac with the Fusion drive bought not to long ago. It has 16gb memory. Since it's back to school, we are busier than this past summer
    We are editing about 200 - 400 images a day. While in Aperture we have had kernel panics and a major spinning ball freezes with a total reboot freeze that ended up with  corruption on the Fusion drive.
    We have ask some tech people, and all have said, when working with large raw images, which we do, the drive cannot keep up with editing, esp when using the brush tool. Also missing files sometimes, like magic their gone.
    Anyone else have this.
    PS we have swaped out the memory 3 times and still had issues. I don't think the drive can handle the work.

    While I am runing a DIY Fusion Drive on a Mac Pro, I am a heavy user of Aperture and have noticed no problems what so ever with my current setup.
    It might be helpful if you canpost a crash dump from one of your kernel panics.
    Allan

  • My macbook pro was often kernel panic . Help !

    My macbook often kernel panic, if i plug hardisk external . can you help me for solve this problem ?

    The forum specifically for MacBook Pro:
    MacBook Pro
    http://www.apple.com/support/macbookpro
    Avoiding eliminating Kernel panics
    FAQ kernelpanic
    Resolving Kernel Panics
    Could be the case or cable - try a different cable.
    If you are trying to use it with USB,  do you have a different interface to use like Firewire?
    When you do have panic, you also have left your internal system with corrupt directory that now needs to be repaired.  Making and adding more problems.
    Try boot  from OS X DVD and repair your system - go to Utilty menu => Disk Utility: Repair disk drive
    Get your system working. first.
    Do you have backup from before this started? when or how did it begin?
    What has happened to your external? able to repair the drive?
    do you have a backup for it?
    How is it formatted? what is it used for? TimeMachine? PC and Windows? other?
    ps: this forum is Mac Pro "workstations" - not laptops

Maybe you are looking for

  • How to change sound output?

    Howdy I recently bought a high-end toslink cable which I connected from the optical/digital out from my iMac to my receiver. The sound quality is excellent, however I noticed that all sounds now gets passed to my Hifi system all the time. The only wa

  • Set text of container - javascript help, please!

    I have used Dreamweaver behaviours to "Set text of container" and make different writing appear inside a box when I click a hotspot. Now I want people to be able to click on the writing that just appeared and make more text appear in another box. Cou

  • Esata port not working

    Any ideas why my Fathom External HDD is not recognized using esata cable. I've just bought the Q700-3015 1IU. The driver is powered. I did however get it working via USB. Anyone know what could be wrong?

  • DTP - Delete Overlapping Request

    Hi Experts, While working on DTP, i am confused, can we delete overallping requests using DTP's as we were able to do in info packages. Cheers, Kayrene

  • Mapping parameters binding gets removed in process flow

    Hi All, whenever i import a mdl file from development to production parameters binding of few mappings and pprocedures in process flow get removed automatically. for example Map1 in PF1 has input parameter p1 binding set to Pf.p1. this binding is get