Fsck error

Moin,
we are facing this problem:
#fsck -n
gives following output:
FILESYSTEM IN SUPERBLOCK IS WRONG;FIX n
How can I fix it: ??
# umount filesystem
# newfs -N /dev/rdsk/devicename
# fsck -F ufs -o=block-number /dev/rdsk/device-name
What can I do, if it is the /root, /usr, /var slice??
Thanks
Thomas

boot cdrom -s
fsck /dev/rdsk/c0t0d0s0 ( this depends on the output of the format command since your c# may be different from a cdrom boot. I have had success fsck'ing a /dev/md/rdsk/d0 and /dev/vx/rdsk/rootvol on systems under DiskSuite & Veritas control for the root slice etc. but it is never wise to fsck a mounted filesystem. fsck'ing from Cd is the safest route when /, /usr or /var is concerned although you could probably umount /var and fsck it from single user.

Similar Messages

10.4.11 breaks .dmg mounting - now I get fsck errors.

I am having problems. About 75% of my .dmg files give me errors.
Many of these .dmg files have been working flawlessly on three computers since the 10.3 days... The others were created more recently (including two which were created using 10.4.11).
But on about 75% of my .dmg files I get this error when I try to open them:
"The disk image you are opening may be damaged and could damage your system. Are you sure you want to open this disk image?" and it has two options, "Open" and "Don't Open".
If I chose "Open" it mounts just fine and works just like it used to before 10.4.11. But I get this in my console:
"/sbin/fsck_hfs(/dev/disk2s2) failure for /Users/myUser/Desktop/imac/DiskImages/myDiskImage.dmg.
Dec 31 10:17:52 myComputerName diskimages-helper[1544]: user is overriding fsck failure for myDiskImage.dmg."
If I chose "Don't Open" I get a window that says "Warning. The following disk images failed to mount. Image: myDiskImage.dmg Reason: no mountable file systems" and it presents me with an "OK" button, and I get the same fsck failure message in my console.
This only happens with 10.4.11 and it is happening on two PPC computers and one Intel computer.
This is happening with all sorts of .dmg files, like I mentioned - some were even CREATED WITH 10.4.11!!!
Now - this all works OK if you just need to mount a disk interactively because you can just click "Open" and it works fine. But it completely breaks any scripts I have that mount images automatically (non interactively).
So I am quite frustrated about this...
10.4.11 should be quite mature considering it is the 11th update. I don't see how they could introduce problems like this in such a late update...

Hi John,
I've seen a few with the same symptom, but never the option to Open or Not!
I believe it's not so much a bug in 10.4.11 as it is with not doing Permission fixes before & after any update/upgrade... you end up with components from different versions and incompatabilities arise.
Use Disk Utility to Repair Permissions, (never hurts to verify the HD first), reboot & try it again, if it doesn't work, then try reapplying the big Combo Updates...
The combo update for PowerPC-based Macs...
http://www.apple.com/support/downloads/macosx10411comboupdateppc.html
The combo update for Intel-based Macs...
http://www.apple.com/support/downloads/macosx10411comboupdateintel.html
Repair Permissions afterwards, reboot.
If that doesn't work, looks like an Archive & Install with Permission Repairs along the way.

Getting and fsck error on startup about /bin/plymouth

Hello,
Yesterday I was rebooting my laptop when this happened, during the booting up there was an usual filesystem check and the it gave me an error and asked me to enter my root password for maintenance or press ctrl+D to continue I just continued to the DM and did run
journalctl -xb
I run openbox with compton and conky and basic apps I do not have KDE installed although I did try installing kde5 but was unable to install completely due to some depenecides not installing.
this is the output:
-- Logs begin at Mon 2014-06-30 10:27:20 IST, end at Mon 2014-07-28 07:02:38 IST. --
Jul 28 06:47:43 sentinel systemd-journal[118]: Runtime journal is using 6.2M (max allowed 49.8M, trying to leave 74.7M free of 491.9M available → current limit 49.8M).
Jul 28 06:47:43 sentinel systemd-journal[118]: Runtime journal is using 6.2M (max allowed 49.8M, trying to leave 74.7M free of 491.9M available → current limit 49.8M).
Jul 28 06:47:43 sentinel kernel: Initializing cgroup subsys cpuset
Jul 28 06:47:43 sentinel kernel: Initializing cgroup subsys cpu
Jul 28 06:47:43 sentinel kernel: Initializing cgroup subsys cpuacct
Jul 28 06:47:43 sentinel kernel: Linux version 3.14.4-1-ARCH (nobody@var-lib-archbuild-testing-i686-tobias) (gcc version 4.9.0 20140507 (prerelease) (GCC) ) #1 SMP PREEMPT Tue May 13 16:44:54 CEST 2014
Jul 28 06:47:43 sentinel kernel: e820: BIOS-provided physical RAM map:
Jul 28 06:47:43 sentinel kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009f7ff] usable
Jul 28 06:47:43 sentinel kernel: BIOS-e820: [mem 0x000000000009f800-0x000000000009ffff] reserved
Jul 28 06:47:43 sentinel kernel: BIOS-e820: [mem 0x00000000000d2000-0x00000000000d3fff] reserved
Jul 28 06:47:43 sentinel kernel: BIOS-e820: [mem 0x00000000000dc000-0x00000000000fffff] reserved
Jul 28 06:47:43 sentinel kernel: BIOS-e820: [mem 0x0000000000100000-0x000000003f6cffff] usable
Jul 28 06:47:43 sentinel kernel: BIOS-e820: [mem 0x000000003f6d0000-0x000000003f6e2fff] ACPI NVS
Jul 28 06:47:43 sentinel kernel: BIOS-e820: [mem 0x000000003f6e3000-0x000000003fffffff] reserved
Jul 28 06:47:43 sentinel kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Jul 28 06:47:43 sentinel kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec0ffff] reserved
Jul 28 06:47:43 sentinel kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed003ff] reserved
Jul 28 06:47:43 sentinel kernel: BIOS-e820: [mem 0x00000000fed14000-0x00000000fed19fff] reserved
Jul 28 06:47:43 sentinel kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed8ffff] reserved
Jul 28 06:47:43 sentinel kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Jul 28 06:47:43 sentinel kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 28 06:47:43 sentinel kernel: Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!
Jul 28 06:47:43 sentinel kernel: SMBIOS 2.4 present.
Jul 28 06:47:43 sentinel kernel: DMI: LENOVO LENOVO3000 Y410 /IGT30, BIOS 05CN39WW(V1.10) 08/29/2007
Jul 28 06:47:43 sentinel kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 28 06:47:43 sentinel kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 28 06:47:43 sentinel kernel: e820: last_pfn = 0x3f6d0 max_arch_pfn = 0x100000
Jul 28 06:47:43 sentinel kernel: MTRR default type: uncachable
Jul 28 06:47:43 sentinel kernel: MTRR fixed ranges enabled:
Jul 28 06:47:43 sentinel kernel: 00000-9FFFF write-back
Jul 28 06:47:43 sentinel kernel: A0000-BFFFF uncachable
Jul 28 06:47:43 sentinel kernel: C0000-FFFFF write-protect
Jul 28 06:47:43 sentinel kernel: MTRR variable ranges enabled:
Jul 28 06:47:43 sentinel kernel: 0 base 000000000 mask FC0000000 write-back
Jul 28 06:47:43 sentinel kernel: 1 base 03F700000 mask FFFF00000 uncachable
Jul 28 06:47:43 sentinel kernel: 2 base 03F800000 mask FFF800000 uncachable
Jul 28 06:47:43 sentinel kernel: 3 disabled
Jul 28 06:47:43 sentinel kernel: 4 disabled
Jul 28 06:47:43 sentinel kernel: 5 disabled
Jul 28 06:47:43 sentinel kernel: 6 disabled
Jul 28 06:47:43 sentinel kernel: 7 disabled
Jul 28 06:47:43 sentinel kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 28 06:47:43 sentinel kernel: found SMP MP-table at [mem 0x000f70d0-0x000f70df] mapped at [c00f70d0]
Jul 28 06:47:43 sentinel kernel: Scanning 1 areas for low memory corruption
Jul 28 06:47:43 sentinel kernel: initial memory mapped: [mem 0x00000000-0x01bfffff]
Jul 28 06:47:43 sentinel kernel: Base memory trampoline at [c009b000] 9b000 size 16384
Jul 28 06:47:43 sentinel kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 28 06:47:43 sentinel kernel: [mem 0x00000000-0x000fffff] page 4k
Jul 28 06:47:43 sentinel kernel: init_memory_mapping: [mem 0x37000000-0x373fffff]
Jul 28 06:47:43 sentinel kernel: [mem 0x37000000-0x373fffff] page 2M
Jul 28 06:47:43 sentinel kernel: init_memory_mapping: [mem 0x30000000-0x36ffffff]
Jul 28 06:47:43 sentinel kernel: [mem 0x30000000-0x36ffffff] page 2M
Jul 28 06:47:43 sentinel kernel: init_memory_mapping: [mem 0x00100000-0x2fffffff]
Jul 28 06:47:43 sentinel kernel: [mem 0x00100000-0x003fffff] page 4k
Jul 28 06:47:43 sentinel kernel: [mem 0x00400000-0x2fffffff] page 2M
Jul 28 06:47:43 sentinel kernel: init_memory_mapping: [mem 0x37400000-0x377fdfff]
Jul 28 06:47:43 sentinel kernel: [mem 0x37400000-0x377fdfff] page 4k
Jul 28 06:47:43 sentinel kernel: BRK [0x01798000, 0x01798fff] PGTABLE
Jul 28 06:47:43 sentinel kernel: RAMDISK: [mem 0x37958000-0x37ca3fff]
Jul 28 06:47:43 sentinel kernel: Allocated new RAMDISK: [mem 0x374b2000-0x377fda97]
Jul 28 06:47:43 sentinel kernel: Move RAMDISK from [mem 0x37958000-0x37ca3a97] to [mem 0x374b2000-0x377fda97]
Jul 28 06:47:43 sentinel kernel: ACPI: RSDP 000f7050 000024 (v02 LENOVO)
Jul 28 06:47:43 sentinel kernel: ACPI: XSDT 3f6d7561 00008C (v01 LENOVO CB-01 06040000 LTP 00000000)
Jul 28 06:47:43 sentinel kernel: ACPI: FACP 3f6dfc3a 0000F4 (v03 LENOVO CB-01 06040000 ALAN 00000001)
Jul 28 06:47:43 sentinel kernel: ACPI: DSDT 3f6d92a6 006920 (v02 LENOVO CB-01 06040000 INTL 20060608)
Jul 28 06:47:43 sentinel kernel: ACPI: FACS 3f6e2fc0 000040
Jul 28 06:47:43 sentinel kernel: ACPI: HPET 3f6dfd2e 000038 (v01 LENOVO CB-01 06040000 LOHR 0000005A)
Jul 28 06:47:43 sentinel kernel: ACPI: MCFG 3f6dfd66 00003C (v01 LENOVO CB-01 06040000 LOHR 0000005A)
Jul 28 06:47:43 sentinel kernel: ACPI: TCPA 3f6dfda2 000032 (v01 LENOVO CB-01 06040000 LOHR 0000005A)
Jul 28 06:47:43 sentinel kernel: ACPI: TMOR 3f6dfdd4 000026 (v01 LENOVO CB-01 06040000 PTL 00000003)
Jul 28 06:47:43 sentinel kernel: ACPI: SLIC 3f6dfdfa 000176 (v01 LENOVO CB-01 06040000 TBD 00000001)
Jul 28 06:47:43 sentinel kernel: ACPI: APIC 3f6dff70 000068 (v01 LENOVO CB-01 06040000 LTP 00000000)
Jul 28 06:47:43 sentinel kernel: ACPI: BOOT 3f6dffd8 000028 (v01 LENOVO CB-01 06040000 LTP 00000001)
Jul 28 06:47:43 sentinel kernel: ACPI: SSDT 3f6d8c57 00064F (v01 SataRe SataPri 00001000 INTL 20050624)
Jul 28 06:47:43 sentinel kernel: ACPI: SSDT 3f6d85c5 000692 (v01 SataRe SataSec 00001000 INTL 20050624)
Jul 28 06:47:43 sentinel kernel: ACPI: SSDT 3f6d7b79 00025F (v01 PmRef Cpu0Tst 00003000 INTL 20050624)
Jul 28 06:47:43 sentinel kernel: ACPI: SSDT 3f6d7ad3 0000A6 (v01 PmRef Cpu1Tst 00003000 INTL 20050624)
Jul 28 06:47:43 sentinel kernel: ACPI: SSDT 3f6d75ed 0004E6 (v01 PmRef CpuPm 00003000 INTL 20050624)
Jul 28 06:47:43 sentinel kernel: ACPI: Local APIC address 0xfee00000
Jul 28 06:47:43 sentinel kernel: 126MB HIGHMEM available.
Jul 28 06:47:43 sentinel kernel: 887MB LOWMEM available.
Jul 28 06:47:43 sentinel kernel: mapped low ram: 0 - 377fe000
Jul 28 06:47:43 sentinel kernel: low ram: 0 - 377fe000
Jul 28 06:47:43 sentinel kernel: BRK [0x01799000, 0x01799fff] PGTABLE
Jul 28 06:47:43 sentinel kernel: Zone ranges:
Jul 28 06:47:43 sentinel kernel: DMA [mem 0x00001000-0x00ffffff]
Jul 28 06:47:43 sentinel kernel: Normal [mem 0x01000000-0x377fdfff]
Jul 28 06:47:43 sentinel kernel: HighMem [mem 0x377fe000-0x3f6cffff]
Jul 28 06:47:43 sentinel kernel: Movable zone start for each node
Jul 28 06:47:43 sentinel kernel: Early memory node ranges
Jul 28 06:47:43 sentinel kernel: node 0: [mem 0x00001000-0x0009efff]
Jul 28 06:47:43 sentinel kernel: node 0: [mem 0x00100000-0x3f6cffff]
Jul 28 06:47:43 sentinel kernel: On node 0 totalpages: 259694
Jul 28 06:47:43 sentinel kernel: free_area_init_node: node 0, pgdat c15fc600, node_mem_map f6cc2020
Jul 28 06:47:43 sentinel kernel: DMA zone: 32 pages used for memmap
Jul 28 06:47:43 sentinel kernel: DMA zone: 0 pages reserved
Jul 28 06:47:43 sentinel kernel: DMA zone: 3998 pages, LIFO batch:0
Jul 28 06:47:43 sentinel kernel: Normal zone: 1744 pages used for memmap
Jul 28 06:47:43 sentinel kernel: Normal zone: 223230 pages, LIFO batch:31
Jul 28 06:47:43 sentinel kernel: HighMem zone: 254 pages used for memmap
Jul 28 06:47:43 sentinel kernel: HighMem zone: 32466 pages, LIFO batch:7
Jul 28 06:47:43 sentinel kernel: Using APIC driver default
Jul 28 06:47:43 sentinel kernel: ACPI: PM-Timer IO Port: 0x1008
Jul 28 06:47:43 sentinel kernel: ACPI: Local APIC address 0xfee00000
Jul 28 06:47:43 sentinel kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 28 06:47:43 sentinel kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 28 06:47:43 sentinel kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 28 06:47:43 sentinel kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 28 06:47:43 sentinel kernel: ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
Jul 28 06:47:43 sentinel kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
Jul 28 06:47:43 sentinel kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
Jul 28 06:47:43 sentinel kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 28 06:47:43 sentinel kernel: ACPI: IRQ0 used by override.
Jul 28 06:47:43 sentinel kernel: ACPI: IRQ2 used by override.
Jul 28 06:47:43 sentinel kernel: ACPI: IRQ9 used by override.
Jul 28 06:47:43 sentinel kernel: Using ACPI (MADT) for SMP configuration information
Jul 28 06:47:43 sentinel kernel: ACPI: HPET id: 0x8086a201 base: 0xfed00000
Jul 28 06:47:43 sentinel kernel: smpboot: Allowing 2 CPUs, 0 hotplug CPUs
Jul 28 06:47:43 sentinel kernel: nr_irqs_gsi: 40
Jul 28 06:47:43 sentinel kernel: PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 28 06:47:43 sentinel kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000d1fff]
Jul 28 06:47:43 sentinel kernel: PM: Registered nosave memory: [mem 0x000d2000-0x000d3fff]
Jul 28 06:47:43 sentinel kernel: PM: Registered nosave memory: [mem 0x000d4000-0x000dbfff]
Jul 28 06:47:43 sentinel kernel: PM: Registered nosave memory: [mem 0x000dc000-0x000fffff]
Jul 28 06:47:43 sentinel kernel: e820: [mem 0x40000000-0xdfffffff] available for PCI devices
Jul 28 06:47:43 sentinel kernel: Booting paravirtualized kernel on bare hardware
Jul 28 06:47:43 sentinel kernel: setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2 nr_node_ids:1
Jul 28 06:47:43 sentinel kernel: PERCPU: Embedded 14 pages/cpu @f6ca0000 s33792 r0 d23552 u57344
Jul 28 06:47:43 sentinel kernel: pcpu-alloc: s33792 r0 d23552 u57344 alloc=14*4096
Jul 28 06:47:43 sentinel kernel: pcpu-alloc: [0] 0 [0] 1
Jul 28 06:47:43 sentinel kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 257918
Jul 28 06:47:43 sentinel kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=45e3c622-e8c8-40b6-be7c-0c847fe91502 rw quiet
Jul 28 06:47:43 sentinel kernel: PID hash table entries: 4096 (order: 2, 16384 bytes)
Jul 28 06:47:43 sentinel kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Jul 28 06:47:43 sentinel kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Jul 28 06:47:43 sentinel kernel: Initializing CPU#0
Jul 28 06:47:43 sentinel kernel: allocated 2078328 bytes of page_cgroup
Jul 28 06:47:43 sentinel kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 28 06:47:43 sentinel kernel: Initializing HighMem for node 0 (000377fe:0003f6d0)
Jul 28 06:47:43 sentinel kernel: Initializing Movable for node 0 (00000000:00000000)
Jul 28 06:47:43 sentinel kernel: Memory: 1016448K/1038776K available (4445K kernel code, 470K rwdata, 1280K rodata, 568K init, 956K bss, 22328K reserved, 129864K highmem)
Jul 28 06:47:43 sentinel kernel: virtual kernel memory layout:
fixmap : 0xfff15000 - 0xfffff000 ( 936 kB)
pkmap : 0xff800000 - 0xffc00000 (4096 kB)
vmalloc : 0xf7ffe000 - 0xff7fe000 ( 120 MB)
lowmem : 0xc0000000 - 0xf77fe000 ( 887 MB)
.init : 0xc160f000 - 0xc169d000 ( 568 kB)
.data : 0xc1457b12 - 0xc160eb40 (1756 kB)
.text : 0xc1000000 - 0xc1457b12 (4446 kB)
Jul 28 06:47:43 sentinel kernel: Checking if this processor honours the WP bit even in supervisor mode...Ok.
Jul 28 06:47:43 sentinel kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Jul 28 06:47:43 sentinel kernel: Preemptible hierarchical RCU implementation.
Jul 28 06:47:43 sentinel kernel: RCU dyntick-idle grace-period acceleration is enabled.
Jul 28 06:47:43 sentinel kernel: Dump stacks of tasks blocking RCU-preempt GP.
Jul 28 06:47:43 sentinel kernel: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2.
Jul 28 06:47:43 sentinel kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
Jul 28 06:47:43 sentinel kernel: NR_IRQS:2304 nr_irqs:512 16
Jul 28 06:47:43 sentinel kernel: CPU 0 irqstacks, hard=f6408000 soft=f640a000
Jul 28 06:47:43 sentinel kernel: Console: colour dummy device 80x25
Jul 28 06:47:43 sentinel kernel: console [tty0] enabled
Jul 28 06:47:43 sentinel kernel: hpet clockevent registered
Jul 28 06:47:43 sentinel kernel: tsc: Fast TSC calibration using PIT
Jul 28 06:47:43 sentinel kernel: tsc: Detected 1463.025 MHz processor
Jul 28 06:47:43 sentinel kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 2927.96 BogoMIPS (lpj=4876750)
Jul 28 06:47:43 sentinel kernel: pid_max: default: 32768 minimum: 301
Jul 28 06:47:43 sentinel kernel: ACPI: Core revision 20131218
Jul 28 06:47:43 sentinel kernel: ACPI: All ACPI Tables successfully acquired
Jul 28 06:47:43 sentinel kernel: Security Framework initialized
Jul 28 06:47:43 sentinel kernel: Yama: becoming mindful.
Jul 28 06:47:43 sentinel kernel: Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
Jul 28 06:47:43 sentinel kernel: Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
Jul 28 06:47:43 sentinel kernel: Initializing cgroup subsys memory
Jul 28 06:47:43 sentinel kernel: Initializing cgroup subsys devices
Jul 28 06:47:43 sentinel kernel: Initializing cgroup subsys freezer
Jul 28 06:47:43 sentinel kernel: Initializing cgroup subsys net_cls
Jul 28 06:47:43 sentinel kernel: Initializing cgroup subsys blkio
Jul 28 06:47:43 sentinel kernel: CPU: Physical Processor ID: 0
Jul 28 06:47:43 sentinel kernel: CPU: Processor Core ID: 0
Jul 28 06:47:43 sentinel kernel: mce: CPU supports 6 MCE banks
Jul 28 06:47:43 sentinel kernel: CPU0: Thermal monitoring handled by SMI
Jul 28 06:47:43 sentinel kernel: Last level iTLB entries: 4KB 128, 2MB 4, 4MB 4
Last level dTLB entries: 4KB 256, 2MB 0, 4MB 32, 1GB 0
tlb_flushall_shift: -1
Jul 28 06:47:43 sentinel kernel: Freeing SMP alternatives memory: 16K (c169d000 - c16a1000)
Jul 28 06:47:43 sentinel kernel: ftrace: allocating 18913 entries in 37 pages
Jul 28 06:47:43 sentinel kernel: Enabling APIC mode: Flat. Using 1 I/O APICs
Jul 28 06:47:43 sentinel kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 28 06:47:43 sentinel kernel: smpboot: CPU0: Intel(R) Pentium(R) Dual CPU T2310 @ 1.46GHz (fam: 06, model: 0f, stepping: 0d)
Jul 28 06:47:43 sentinel kernel: Performance Events: PEBS fmt0+, 4-deep LBR, Core2 events, Intel PMU driver.
Jul 28 06:47:43 sentinel kernel: perf_event_intel: PEBS disabled due to CPU errata
Jul 28 06:47:43 sentinel kernel: ... version: 2
Jul 28 06:47:43 sentinel kernel: ... bit width: 40
Jul 28 06:47:43 sentinel kernel: ... generic registers: 2
Jul 28 06:47:43 sentinel kernel: ... value mask: 000000ffffffffff
Jul 28 06:47:43 sentinel kernel: ... max period: 000000007fffffff
Jul 28 06:47:43 sentinel kernel: ... fixed-purpose events: 3
Jul 28 06:47:43 sentinel kernel: ... event mask: 0000000700000003
Jul 28 06:47:43 sentinel kernel: CPU 1 irqstacks, hard=f64cc000 soft=f64ce000
Jul 28 06:47:43 sentinel kernel: x86: Booting SMP configuration:
Jul 28 06:47:43 sentinel kernel: .... node #0, CPUs: #1
Jul 28 06:47:43 sentinel kernel: Initializing CPU#1
Jul 28 06:47:43 sentinel kernel: CPU1: Thermal monitoring handled by SMI
Jul 28 06:47:43 sentinel kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 28 06:47:43 sentinel kernel: x86: Booted up 1 node, 2 CPUs
Jul 28 06:47:43 sentinel kernel: smpboot: Total of 2 processors activated (5854.93 BogoMIPS)
Jul 28 06:47:43 sentinel kernel: devtmpfs: initialized
Jul 28 06:47:43 sentinel kernel: PM: Registering ACPI NVS region [mem 0x3f6d0000-0x3f6e2fff] (77824 bytes)
Jul 28 06:47:43 sentinel kernel: pinctrl core: initialized pinctrl subsystem
Jul 28 06:47:43 sentinel kernel: RTC time: 1:17:37, date: 07/28/14
Jul 28 06:47:43 sentinel kernel: NET: Registered protocol family 16
Jul 28 06:47:43 sentinel kernel: cpuidle: using governor ladder
Jul 28 06:47:43 sentinel kernel: cpuidle: using governor menu
Jul 28 06:47:43 sentinel kernel: ACPI: bus type PCI registered
Jul 28 06:47:43 sentinel kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 28 06:47:43 sentinel kernel: PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
Jul 28 06:47:43 sentinel kernel: PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
Jul 28 06:47:43 sentinel kernel: PCI: Using MMCONFIG for extended config space
Jul 28 06:47:43 sentinel kernel: PCI: Using configuration type 1 for base access
Jul 28 06:47:43 sentinel kernel: mtrr: your CPUs had inconsistent variable MTRR settings
Jul 28 06:47:43 sentinel kernel: mtrr: probably your BIOS does not setup all CPUs.
Jul 28 06:47:43 sentinel kernel: mtrr: corrected configuration.
Jul 28 06:47:43 sentinel kernel: bio: create slab <bio-0> at 0
Jul 28 06:47:43 sentinel kernel: ACPI: Added _OSI(Module Device)
Jul 28 06:47:43 sentinel kernel: ACPI: Added _OSI(Processor Device)
Jul 28 06:47:43 sentinel kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 28 06:47:43 sentinel kernel: ACPI: Added _OSI(Processor Aggregator Device)
Jul 28 06:47:43 sentinel kernel: [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 28 06:47:43 sentinel kernel: ACPI: SSDT 3f6d8307 0001F6 (v01 PmRef Cpu0Ist 00003000 INTL 20050624)
Jul 28 06:47:43 sentinel kernel: ACPI: Dynamic OEM Table Load:
Jul 28 06:47:43 sentinel kernel: ACPI: SSDT (null) 0001F6 (v01 PmRef Cpu0Ist 00003000 INTL 20050624)
Jul 28 06:47:43 sentinel kernel: ACPI: SSDT 3f6d7dd8 0004AA (v01 PmRef Cpu0Cst 00003001 INTL 20050624)
Jul 28 06:47:43 sentinel kernel: ACPI: Dynamic OEM Table Load:
Jul 28 06:47:43 sentinel kernel: ACPI: SSDT (null) 0004AA (v01 PmRef Cpu0Cst 00003001 INTL 20050624)
Jul 28 06:47:43 sentinel kernel: ACPI: SSDT 3f6d84fd 0000C8 (v01 PmRef Cpu1Ist 00003000 INTL 20050624)
Jul 28 06:47:43 sentinel kernel: ACPI: Dynamic OEM Table Load:
Jul 28 06:47:43 sentinel kernel: ACPI: SSDT (null) 0000C8 (v01 PmRef Cpu1Ist 00003000 INTL 20050624)
Jul 28 06:47:43 sentinel kernel: ACPI: SSDT 3f6d8282 000085 (v01 PmRef Cpu1Cst 00003000 INTL 20050624)
Jul 28 06:47:43 sentinel kernel: ACPI: Dynamic OEM Table Load:
Jul 28 06:47:43 sentinel kernel: ACPI: SSDT (null) 000085 (v01 PmRef Cpu1Cst 00003000 INTL 20050624)
Jul 28 06:47:43 sentinel kernel: ACPI: Interpreter enabled
Jul 28 06:47:43 sentinel kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131218/hwxface-580)
Jul 28 06:47:43 sentinel kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131218/hwxface-580)
Jul 28 06:47:43 sentinel kernel: ACPI: (supports S0 S3 S4 S5)
Jul 28 06:47:43 sentinel kernel: ACPI: Using IOAPIC for interrupt routing
Jul 28 06:47:43 sentinel kernel: PCI: Ignoring host bridge windows from ACPI; if necessary, use "pci=use_crs" and report a bug
Jul 28 06:47:43 sentinel kernel: ACPI: No dock devices found.
Jul 28 06:47:43 sentinel kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
Jul 28 06:47:43 sentinel kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 28 06:47:43 sentinel kernel: acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 28 06:47:43 sentinel kernel: acpi PNP0A08:00: host bridge window [io 0x0000-0x0cf7] (ignored)
Jul 28 06:47:43 sentinel kernel: acpi PNP0A08:00: host bridge window [io 0x0d00-0xffff] (ignored)
Jul 28 06:47:43 sentinel kernel: acpi PNP0A08:00: host bridge window [mem 0x000a0000-0x000bffff] (ignored)
Jul 28 06:47:43 sentinel kernel: acpi PNP0A08:00: host bridge window [mem 0x000d4000-0x000d7fff] (ignored)
Jul 28 06:47:43 sentinel kernel: acpi PNP0A08:00: host bridge window [mem 0x000d8000-0x000dbfff] (ignored)
Jul 28 06:47:43 sentinel kernel: acpi PNP0A08:00: host bridge window [mem 0x40000000-0xdfffffff] (ignored)
Jul 28 06:47:43 sentinel kernel: acpi PNP0A08:00: host bridge window [mem 0xf0000000-0xfebfffff] (ignored)
Jul 28 06:47:43 sentinel kernel: PCI: root bus 00: using default resources
Jul 28 06:47:43 sentinel kernel: PCI host bridge to bus 0000:00
Jul 28 06:47:43 sentinel kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
Jul 28 06:47:43 sentinel kernel: pci_bus 0000:00: root bus resource [io 0x0000-0xffff]
Jul 28 06:47:43 sentinel kernel: pci_bus 0000:00: root bus resource [mem 0x00000000-0xffffffff]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:00.0: [8086:2a00] type 00 class 0x060000
Jul 28 06:47:43 sentinel kernel: pci 0000:00:02.0: [8086:2a02] type 00 class 0x030000
Jul 28 06:47:43 sentinel kernel: pci 0000:00:02.0: reg 0x10: [mem 0xf8000000-0xf80fffff 64bit]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:02.0: reg 0x18: [mem 0xd0000000-0xdfffffff 64bit pref]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:02.0: reg 0x20: [io 0x1800-0x1807]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:02.1: [8086:2a03] type 00 class 0x038000
Jul 28 06:47:43 sentinel kernel: pci 0000:00:02.1: reg 0x10: [mem 0xf8100000-0xf81fffff 64bit]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1a.0: [8086:2834] type 00 class 0x0c0300
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1a.0: reg 0x20: [io 0x1820-0x183f]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1a.1: [8086:2835] type 00 class 0x0c0300
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1a.1: reg 0x20: [io 0x1840-0x185f]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1a.1: System wakeup disabled by ACPI
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1a.7: [8086:283a] type 00 class 0x0c0320
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1a.7: reg 0x10: [mem 0xf8504000-0xf85043ff]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1a.7: System wakeup disabled by ACPI
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1b.0: [8086:284b] type 00 class 0x040300
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xf8300000-0xf8303fff 64bit]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1b.0: System wakeup disabled by ACPI
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.0: [8086:283f] type 01 class 0x060400
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.1: [8086:2841] type 01 class 0x060400
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.2: [8086:2843] type 01 class 0x060400
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.3: [8086:2845] type 01 class 0x060400
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1d.0: [8086:2830] type 00 class 0x0c0300
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1d.0: reg 0x20: [io 0x1860-0x187f]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1d.1: [8086:2831] type 00 class 0x0c0300
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1d.1: reg 0x20: [io 0x1880-0x189f]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1d.1: System wakeup disabled by ACPI
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1d.2: [8086:2832] type 00 class 0x0c0300
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1d.2: reg 0x20: [io 0x18a0-0x18bf]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1d.2: System wakeup disabled by ACPI
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1d.7: [8086:2836] type 00 class 0x0c0320
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1d.7: reg 0x10: [mem 0xf8504400-0xf85047ff]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1d.7: System wakeup disabled by ACPI
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1e.0: [8086:2448] type 01 class 0x060401
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1f.0: [8086:2815] type 00 class 0x060100
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1f.0: address space collision: [io 0x1000-0x107f] conflicts with ACPI CPU throttle [??? 0x00001010-0x00001015 flags 0x80000000]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1f.0: quirk: [io 0x1180-0x11bf] claimed by ICH6 GPIO
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0680 (mask 007f)
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1f.0: ICH7 LPC Generic IO decode 2 PIO at 1640 (mask 000f)
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1f.0: ICH7 LPC Generic IO decode 4 PIO at 0068 (mask 0007)
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1f.2: [8086:2828] type 00 class 0x010180
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1f.2: reg 0x10: [io 0x0000-0x0007]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1f.2: reg 0x14: [io 0x0000-0x0003]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1f.2: reg 0x18: [io 0x0000-0x0007]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1f.2: reg 0x1c: [io 0x0000-0x0003]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1f.2: reg 0x20: [io 0x18e0-0x18ef]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1f.2: reg 0x24: [io 0x18d0-0x18df]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1f.2: PME# supported from D3hot
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1f.3: [8086:283e] type 00 class 0x0c0500
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1f.3: reg 0x10: [mem 0x00000000-0x000000ff]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1f.3: reg 0x20: [io 0x1c00-0x1c1f]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.0: bridge window [io 0x2000-0x2fff]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.0: bridge window [mem 0xc0000000-0xc3ffffff]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.0: bridge window [mem 0xcc000000-0xcdffffff 64bit pref]
Jul 28 06:47:43 sentinel kernel: pci 0000:04:00.0: [8086:4222] type 00 class 0x028000
Jul 28 06:47:43 sentinel kernel: pci 0000:04:00.0: reg 0x10: [mem 0xf0000000-0xf0000fff]
Jul 28 06:47:43 sentinel kernel: pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 28 06:47:43 sentinel kernel: pci 0000:04:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.1: PCI bridge to [bus 04]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.1: bridge window [io 0x3000-0x3fff]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.1: bridge window [mem 0xf0000000-0xf3ffffff]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.1: bridge window [mem 0xfa000000-0xfbffffff 64bit pref]
Jul 28 06:47:43 sentinel kernel: acpiphp: Slot [1] registered
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.2: PCI bridge to [bus 05]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.2: bridge window [io 0x4000-0x4fff]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.2: bridge window [mem 0xf4000000-0xf7ffffff]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.2: bridge window [mem 0xfc000000-0xfdffffff 64bit pref]
Jul 28 06:47:43 sentinel kernel: pci 0000:06:00.0: [14e4:1713] type 00 class 0x020000
Jul 28 06:47:43 sentinel kernel: pci 0000:06:00.0: reg 0x10: [mem 0xb8000000-0xb800ffff 64bit]
Jul 28 06:47:43 sentinel kernel: pci 0000:06:00.0: PME# supported from D3hot D3cold
Jul 28 06:47:43 sentinel kernel: pci 0000:06:00.0: System wakeup disabled by ACPI
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.3: PCI bridge to [bus 06]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.3: bridge window [io 0x5000-0x5fff]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.3: bridge window [mem 0xb8000000-0xbbffffff]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.3: bridge window [mem 0xc8000000-0xc9ffffff 64bit pref]
Jul 28 06:47:43 sentinel kernel: pci 0000:08:06.0: [1180:0832] type 00 class 0x0c0010
Jul 28 06:47:43 sentinel kernel: pci 0000:08:06.0: proprietary Ricoh MMC controller disabled (via firewire function)
Jul 28 06:47:43 sentinel kernel: pci 0000:08:06.0: MMC cards are now supported by standard SDHCI controller
Jul 28 06:47:43 sentinel kernel: pci 0000:08:06.0: reg 0x10: [mem 0xf8200000-0xf82007ff]
Jul 28 06:47:43 sentinel kernel: pci 0000:08:06.0: supports D1 D2
Jul 28 06:47:43 sentinel kernel: pci 0000:08:06.0: PME# supported from D0 D1 D2 D3hot D3cold
Jul 28 06:47:43 sentinel kernel: pci 0000:08:06.1: [1180:0822] type 00 class 0x080500
Jul 28 06:47:43 sentinel kernel: pci 0000:08:06.1: reg 0x10: [mem 0xf8200800-0xf82008ff]
Jul 28 06:47:43 sentinel kernel: pci 0000:08:06.1: supports D1 D2
Jul 28 06:47:43 sentinel kernel: pci 0000:08:06.1: PME# supported from D0 D1 D2 D3hot D3cold
Jul 28 06:47:43 sentinel kernel: pci 0000:08:06.2: [1180:0592] type 00 class 0x088000
Jul 28 06:47:43 sentinel kernel: pci 0000:08:06.2: reg 0x10: [mem 0xf8201000-0xf82010ff]
Jul 28 06:47:43 sentinel kernel: pci 0000:08:06.2: supports D1 D2
Jul 28 06:47:43 sentinel kernel: pci 0000:08:06.2: PME# supported from D0 D1 D2 D3hot D3cold
Jul 28 06:47:43 sentinel kernel: pci 0000:08:06.3: [1180:0852] type 00 class 0x088000
Jul 28 06:47:43 sentinel kernel: pci 0000:08:06.3: reg 0x10: [mem 0xf8201400-0xf82014ff]
Jul 28 06:47:43 sentinel kernel: pci 0000:08:06.3: supports D1 D2
Jul 28 06:47:43 sentinel kernel: pci 0000:08:06.3: PME# supported from D0 D1 D2 D3hot D3cold
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1e.0: PCI bridge to [bus 08] (subtractive decode)
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1e.0: bridge window [mem 0xf8200000-0xf82fffff]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1e.0: bridge window [io 0x0000-0xffff] (subtractive decode)
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1e.0: bridge window [mem 0x00000000-0xffffffff] (subtractive decode)
Jul 28 06:47:43 sentinel kernel: pci_bus 0000:00: on NUMA node 0
Jul 28 06:47:43 sentinel kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 *5 6 7 10 12 14 15)
Jul 28 06:47:43 sentinel kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 11 12 14 15) *10
Jul 28 06:47:43 sentinel kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 *7 10 12 14 15)
Jul 28 06:47:43 sentinel kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 11 12 14 15) *10
Jul 28 06:47:43 sentinel kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 7 10 12 14 15) *0, disabled.
Jul 28 06:47:43 sentinel kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 7 *11 12 14 15)
Jul 28 06:47:43 sentinel kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
Jul 28 06:47:43 sentinel kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 7 11 12 14 15) *10
Jul 28 06:47:43 sentinel kernel: ACPI: Enabled 4 GPEs in block 00 to 1F
Jul 28 06:47:43 sentinel kernel: ACPI : EC: GPE = 0x1c, I/O: command/status = 0x66, data = 0x62
Jul 28 06:47:43 sentinel kernel: vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
Jul 28 06:47:43 sentinel kernel: vgaarb: loaded
Jul 28 06:47:43 sentinel kernel: vgaarb: bridge control possible 0000:00:02.0
Jul 28 06:47:43 sentinel kernel: PCI: Using ACPI for IRQ routing
Jul 28 06:47:43 sentinel kernel: PCI: pci_cache_line_size set to 64 bytes
Jul 28 06:47:43 sentinel kernel: e820: reserve RAM buffer [mem 0x0009f800-0x0009ffff]
Jul 28 06:47:43 sentinel kernel: e820: reserve RAM buffer [mem 0x3f6d0000-0x3fffffff]
Jul 28 06:47:43 sentinel kernel: NetLabel: Initializing
Jul 28 06:47:43 sentinel kernel: NetLabel: domain hash size = 128
Jul 28 06:47:43 sentinel kernel: NetLabel: protocols = UNLABELED CIPSOv4
Jul 28 06:47:43 sentinel kernel: NetLabel: unlabeled traffic allowed by default
Jul 28 06:47:43 sentinel kernel: HPET: 3 timers in total, 0 timers will be used for per-cpu timer
Jul 28 06:47:43 sentinel kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
Jul 28 06:47:43 sentinel kernel: hpet0: 3 comparators, 64-bit 14.318180 MHz counter
Jul 28 06:47:43 sentinel kernel: Switched to clocksource hpet
Jul 28 06:47:43 sentinel kernel: pnp: PnP ACPI init
Jul 28 06:47:43 sentinel kernel: ACPI: bus type PNP registered
Jul 28 06:47:43 sentinel kernel: system 00:00: [mem 0xfed1c000-0xfed1ffff] has been reserved
Jul 28 06:47:43 sentinel kernel: system 00:00: [mem 0xfed14000-0xfed17fff] has been reserved
Jul 28 06:47:43 sentinel kernel: system 00:00: [mem 0xfed18000-0xfed18fff] has been reserved
Jul 28 06:47:43 sentinel kernel: system 00:00: [mem 0xfed19000-0xfed19fff] has been reserved
Jul 28 06:47:43 sentinel kernel: system 00:00: [mem 0xe0000000-0xefffffff] has been reserved
Jul 28 06:47:43 sentinel kernel: system 00:00: [mem 0xfed20000-0xfed3ffff] has been reserved
Jul 28 06:47:43 sentinel kernel: system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
Jul 28 06:47:43 sentinel kernel: system 00:00: [mem 0xfed45000-0xfed8ffff] has been reserved
Jul 28 06:47:43 sentinel kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 28 06:47:43 sentinel kernel: pnp 00:01: [dma 4]
Jul 28 06:47:43 sentinel kernel: pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 28 06:47:43 sentinel kernel: pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
Jul 28 06:47:43 sentinel kernel: system 00:03: [mem 0xfed00000-0xfed003ff] has been reserved
Jul 28 06:47:43 sentinel kernel: system 00:03: Plug and Play ACPI device, IDs PNP0103 PNP0c01 (active)
Jul 28 06:47:43 sentinel kernel: pnp 00:04: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 28 06:47:43 sentinel kernel: system 00:05: [io 0x0680-0x069f] has been reserved
Jul 28 06:47:43 sentinel kernel: system 00:05: [io 0x0800-0x080f] has been reserved
Jul 28 06:47:43 sentinel kernel: system 00:05: [io 0x1000-0x107f] could not be reserved
Jul 28 06:47:43 sentinel kernel: system 00:05: [io 0x1180-0x11bf] has been reserved
Jul 28 06:47:43 sentinel kernel: system 00:05: [io 0xfe00] has been reserved
Jul 28 06:47:43 sentinel kernel: system 00:05: [io 0xff00-0xff7f] has been reserved
Jul 28 06:47:43 sentinel kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 28 06:47:43 sentinel kernel: pnp 00:06: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 28 06:47:43 sentinel kernel: pnp 00:07: Plug and Play ACPI device, IDs PNP0303 (active)
Jul 28 06:47:43 sentinel kernel: pnp 00:08: Plug and Play ACPI device, IDs PNP0f13 (active)
Jul 28 06:47:43 sentinel kernel: pnp: PnP ACPI: found 9 devices
Jul 28 06:47:43 sentinel kernel: ACPI: bus type PNP unregistered
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1f.0: BAR 13: [io 0x1000-0x107f] has bogus alignment
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1f.3: BAR 0: assigned [mem 0x40000000-0x400000ff]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.0: bridge window [io 0x2000-0x2fff]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.0: bridge window [mem 0xc0000000-0xc3ffffff]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.0: bridge window [mem 0xcc000000-0xcdffffff 64bit pref]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.1: PCI bridge to [bus 04]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.1: bridge window [io 0x3000-0x3fff]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.1: bridge window [mem 0xf0000000-0xf3ffffff]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.1: bridge window [mem 0xfa000000-0xfbffffff 64bit pref]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.2: PCI bridge to [bus 05]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.2: bridge window [io 0x4000-0x4fff]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.2: bridge window [mem 0xf4000000-0xf7ffffff]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.2: bridge window [mem 0xfc000000-0xfdffffff 64bit pref]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.3: PCI bridge to [bus 06]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.3: bridge window [io 0x5000-0x5fff]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.3: bridge window [mem 0xb8000000-0xbbffffff]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1c.3: bridge window [mem 0xc8000000-0xc9ffffff 64bit pref]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1e.0: PCI bridge to [bus 08]
Jul 28 06:47:43 sentinel kernel: pci 0000:00:1e.0: bridge window [mem 0xf8200000-0xf82fffff]
Jul 28 06:47:43 sentinel kernel: pci_bus 0000:00: resource 4 [io 0x0000-0xffff]
Jul 28 06:47:43 sentinel kernel: pci_bus 0000:00: resource 5 [mem 0x00000000-0xffffffff]
Jul 28 06:47:43 sentinel kernel: pci_bus 0000:02: resource 0 [io 0x2000-0x2fff]
Jul 28 06:47:43 sentinel kernel: pci_bus 0000:02: resource 1 [mem 0xc0000000-0xc3ffffff]
Jul 28 06:47:43 sentinel kernel: pci_bus 0000:02: resource 2 [mem 0xcc000000-0xcdffffff 64bit pref]
Jul 28 06:47:43 sentinel kernel: pci_bus 0000:04: resource 0 [io 0x3000-0x3fff]
Jul 28 06:47:43 sentinel kernel: pci_bus 0000:04: resource 1 [mem 0xf0000000-0xf3ffffff]
Jul 28 06:47:43 sentinel kernel: pci_bus 0000:04: resource 2 [mem 0xfa000000-0xfbffffff 64bit pref]
Jul 28 06:47:43 sentinel kernel: pci_bus 0000:05: resource 0 [io 0x4000-0x4fff]
Jul 28 06:47:43 sentinel kernel: pci_bus 0000:05: resource 1 [mem 0xf4000000-0xf7ffffff]
Jul 28 06:47:43 sentinel kernel: pci_bus 0000:05: resource 2 [mem 0xfc000000-0xfdffffff 64bit pref]
Jul 28 06:47:43 sentinel kernel: pci_bus 0000:06: resource 0 [io 0x5000-0x5fff]
Jul 28 06:47:43 sentinel kernel: pci_bus 0000:06: resource 1 [mem 0xb8000000-0xbbffffff]
Jul 28 06:47:43 sentinel kernel: pci_bus 0000:06: resource 2 [mem 0xc8000000-0xc9ffffff 64bit pref]
Jul 28 06:47:43 sentinel kernel: pci_bus 0000:08: resource 1 [mem 0xf8200000-0xf82fffff]
Jul 28 06:47:43 sentinel kernel: pci_bus 0000:08: resource 4 [io 0x0000-0xffff]
Jul 28 06:47:43 sentinel kernel: pci_bus 0000:08: resource 5 [mem 0x00000000-0xffffffff]
Jul 28 06:47:43 sentinel kernel: NET: Registered protocol family 2
Jul 28 06:47:43 sentinel kernel: TCP established hash table entries: 8192 (order: 3, 32768 bytes)
Jul 28 06:47:43 sentinel kernel: TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
Jul 28 06:47:43 sentinel kernel: TCP: Hash tables configured (established 8192 bind 8192)
Jul 28 06:47:43 sentinel kernel: TCP: reno registered
Jul 28 06:47:43 sentinel kernel: UDP hash table entries: 512 (order: 2, 16384 bytes)
Jul 28 06:47:43 sentinel kernel: UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
Jul 28 06:47:43 sentinel kernel: NET: Registered protocol family 1
Jul 28 06:47:43 sentinel kernel: pci 0000:00:02.0: Boot video device
Jul 28 06:47:43 sentinel kernel: PCI: CLS 64 bytes, default 64
Jul 28 06:47:43 sentinel kernel: Unpacking initramfs...
Jul 28 06:47:43 sentinel kernel: Freeing initrd memory: 3376K (f74b2000 - f77fe000)
Jul 28 06:47:43 sentinel kernel: Simple Boot Flag at 0x37 set to 0x1
Jul 28 06:47:43 sentinel kernel: apm: BIOS not found.
Jul 28 06:47:43 sentinel kernel: Scanning for low memory corruption every 60 seconds
Jul 28 06:47:43 sentinel kernel: futex hash table entries: 512 (order: 3, 32768 bytes)
Jul 28 06:47:43 sentinel kernel: bounce pool size: 64 pages
Jul 28 06:47:43 sentinel kernel: HugeTLB registered 4 MB page size, pre-allocated 0 pages
Jul 28 06:47:43 sentinel kernel: zbud: loaded
Jul 28 06:47:43 sentinel kernel: VFS: Disk quotas dquot_6.5.2
Jul 28 06:47:43 sentinel kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Jul 28 06:47:43 sentinel kernel: msgmni has been set to 1738
Jul 28 06:47:43 sentinel kernel: Key type big_key registered
Jul 28 06:47:43 sentinel kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 28 06:47:43 sentinel kernel: io scheduler noop registered
Jul 28 06:47:43 sentinel kernel: io scheduler deadline registered
Jul 28 06:47:43 sentinel kernel: io scheduler cfq registered (default)
Jul 28 06:47:43 sentinel kernel: pcieport 0000:00:1c.0: irq 40 for MSI/MSI-X
Jul 28 06:47:43 sentinel kernel: pcieport 0000:00:1c.1: irq 41 for MSI/MSI-X
Jul 28 06:47:43 sentinel kernel: pcieport 0000:00:1c.2: irq 42 for MSI/MSI-X
Jul 28 06:47:43 sentinel kernel: pcieport 0000:00:1c.3: irq 43 for MSI/MSI-X
Jul 28 06:47:43 sentinel kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 28 06:47:43 sentinel kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 28 06:47:43 sentinel kernel: vesafb: mode is 1280x800x32, linelength=5120, pages=0
Jul 28 06:47:43 sentinel kernel: vesafb: scrolling: redraw
Jul 28 06:47:43 sentinel kernel: vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 28 06:47:43 sentinel kernel: vesafb: framebuffer at 0xd0000000, mapped to 0xf8080000, using 4032k, total 4032k
Jul 28 06:47:43 sentinel kernel: Console: switching to colour frame buffer device 160x50
Jul 28 06:47:43 sentinel kernel: fb0: VESA VGA frame buffer device
Jul 28 06:47:43 sentinel kernel: intel_idle: does not run on family 6 model 15
Jul 28 06:47:43 sentinel kernel: GHES: HEST is not enabled!
Jul 28 06:47:43 sentinel kernel: isapnp: Scanning for PnP cards...
Jul 28 06:47:43 sentinel kernel: isapnp: No Plug & Play device found
Jul 28 06:47:43 sentinel kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
Jul 28 06:47:43 sentinel kernel: rtc_cmos 00:06: RTC can wake from S4
Jul 28 06:47:43 sentinel kernel: rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
Jul 28 06:47:43 sentinel kernel: rtc_cmos 00:06: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
Jul 28 06:47:43 sentinel kernel: ledtrig-cpu: registered to indicate activity on CPUs
Jul 28 06:47:43 sentinel kernel: TCP: cubic registered
Jul 28 06:47:43 sentinel kernel: NET: Registered protocol family 10
Jul 28 06:47:43 sentinel kernel: NET: Registered protocol family 17
Jul 28 06:47:43 sentinel kernel: Using IPI No-Shortcut mode
Jul 28 06:47:43 sentinel kernel: registered taskstats version 1
Jul 28 06:47:43 sentinel kernel: Magic number: 6:931:256
Jul 28 06:47:43 sentinel kernel: rtc_cmos 00:06: setting system clock to 2014-07-28 01:17:37 UTC (1406510257)
Jul 28 06:47:43 sentinel kernel: PM: Hibernation image not present or could not be loaded.
Jul 28 06:47:43 sentinel kernel: Freeing unused kernel memory: 568K (c160f000 - c169d000)
Jul 28 06:47:43 sentinel kernel: Write protecting the kernel text: 4448k
Jul 28 06:47:43 sentinel kernel: Write protecting the kernel read-only data: 1284k
Jul 28 06:47:43 sentinel kernel: random: systemd-tmpfile urandom read with 0 bits of entropy available
Jul 28 06:47:43 sentinel systemd-udevd[47]: starting version 215
Jul 28 06:47:43 sentinel kernel: ACPI: bus type USB registered
Jul 28 06:47:43 sentinel kernel: usbcore: registered new interface driver usbfs
Jul 28 06:47:43 sentinel kernel: usbcore: registered new interface driver hub
Jul 28 06:47:43 sentinel kernel: usbcore: registered new device driver usb
Jul 28 06:47:43 sentinel kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 28 06:47:43 sentinel kernel: uhci_hcd: USB Universal Host Controller Interface driver
Jul 28 06:47:43 sentinel kernel: uhci_hcd 0000:00:1a.0: UHCI Host Controller
Jul 28 06:47:43 sentinel kernel: uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 28 06:47:43 sentinel kernel: uhci_hcd 0000:00:1a.0: detected 2 ports
Jul 28 06:47:43 sentinel kernel: uhci_hcd 0000:00:1a.0: irq 16, io base 0x00001820
Jul 28 06:47:43 sentinel kernel: hub 1-0:1.0: USB hub found
Jul 28 06:47:43 sentinel kernel: hub 1-0:1.0: 2 ports detected
Jul 28 06:47:43 sentinel kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
Jul 28 06:47:43 sentinel kernel: ehci-pci: EHCI PCI platform driver
Jul 28 06:47:43 sentinel kernel: uhci_hcd 0000:00:1a.1: UHCI Host Controller
Jul 28 06:47:43 sentinel kernel: uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 2
Jul 28 06:47:43 sentinel kernel: uhci_hcd 0000:00:1a.1: detected 2 ports
Jul 28 06:47:43 sentinel kernel: uhci_hcd 0000:00:1a.1: irq 21, io base 0x00001840
Jul 28 06:47:43 sentinel kernel: SCSI subsystem initialized
Jul 28 06:47:43 sentinel kernel: hub 2-0:1.0: USB hub found
Jul 28 06:47:43 sentinel kernel: hub 2-0:1.0: 2 ports detected
Jul 28 06:47:43 sentinel kernel: ehci-pci 0000:00:1a.7: EHCI Host Controller
Jul 28 06:47:43 sentinel kernel: ehci-pci 0000:00:1a.7: new USB bus registered, assigned bus number 3
Jul 28 06:47:43 sentinel kernel: ehci-pci 0000:00:1a.7: debug port 1
Jul 28 06:47:43 sentinel kernel: ehci-pci 0000:00:1a.7: cache line size of 64 is not supported
Jul 28 06:47:43 sentinel kernel: ehci-pci 0000:00:1a.7: irq 18, io mem 0xf8504000
Jul 28 06:47:43 sentinel kernel: sdhci: Secure Digital Host Controller Interface driver
Jul 28 06:47:43 sentinel kernel: sdhci: Copyright(c) Pierre Ossman
Jul 28 06:47:43 sentinel kernel: sdhci-pci 0000:08:06.1: SDHCI controller found [1180:0822] (rev 22)
Jul 28 06:47:43 sentinel kernel: sdhci-pci 0000:08:06.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 28 06:47:43 sentinel kernel: sdhci-pci 0000:08:06.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 28 06:47:43 sentinel kernel: mmc0: SDHCI controller on PCI [0000:08:06.1] using DMA
Jul 28 06:47:43 sentinel kernel: libata version 3.00 loaded.
Jul 28 06:47:43 sentinel kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Jul 28 06:47:43 sentinel kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Jul 28 06:47:43 sentinel kernel: ehci-pci 0000:00:1a.7: USB 2.0 started, EHCI 1.00
Jul 28 06:47:43 sentinel kernel: hub 3-0:1.0: USB hub found
Jul 28 06:47:43 sentinel kernel: hub 3-0:1.0: 4 ports detected
Jul 28 06:47:43 sentinel kernel: hub 1-0:1.0: USB hub found
Jul 28 06:47:43 sentinel kernel: hub 1-0:1.0: 2 ports detected
Jul 28 06:47:43 sentinel kernel: hub 2-0:1.0: USB hub found
Jul 28 06:47:43 sentinel kernel: hub 2-0:1.0: 2 ports detected
Jul 28 06:47:43 sentinel kernel: ehci-pci 0000:00:1d.7: EHCI Host Controller
Jul 28 06:47:43 sentinel kernel: ehci-pci 0000:00:1d.7: new USB bus registered, assigned bus number 4
Jul 28 06:47:43 sentinel kernel: ehci-pci 0000:00:1d.7: debug port 1
Jul 28 06:47:43 sentinel kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
Jul 28 06:47:43 sentinel kernel: ehci-pci 0000:00:1d.7: cache line size of 64 is not supported
Jul 28 06:47:43 sentinel kernel: ehci-pci 0000:00:1d.7: irq 23, io mem 0xf8504400
Jul 28 06:47:43 sentinel kernel: firewire_ohci 0000:08:06.0: added OHCI v1.10 device as card 0, 4 IR + 4 IT contexts, quirks 0x11
Jul 28 06:47:43 sentinel kernel: ehci-pci 0000:00:1d.7: USB 2.0 started, EHCI 1.00
Jul 28 06:47:43 sentinel kernel: hub 4-0:1.0: USB hub found
Jul 28 06:47:43 sentinel kernel: hub 4-0:1.0: 6 ports detected
Jul 28 06:47:43 sentinel kernel: uhci_hcd 0000:00:1d.0: UHCI Host Controller
Jul 28 06:47:43 sentinel kernel: uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 5
Jul 28 06:47:43 sentinel kernel: uhci_hcd 0000:00:1d.0: detected 2 ports
Jul 28 06:47:43 sentinel kernel: uhci_hcd 0000:00:1d.0: irq 23, io base 0x00001860
Jul 28 06:47:43 sentinel kernel: hub 5-0:1.0: USB hub found
Jul 28 06:47:43 sentinel kernel: hub 5-0:1.0: 2 ports detected
Jul 28 06:47:43 sentinel kernel: uhci_hcd 0000:00:1d.1: UHCI Host Controller
Jul 28 06:47:43 sentinel kernel: uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 6
Jul 28 06:47:43 sentinel kernel: uhci_hcd 0000:00:1d.1: detected 2 ports
Jul 28 06:47:43 sentinel kernel: uhci_hcd 0000:00:1d.1: irq 19, io base 0x00001880
Jul 28 06:47:43 sentinel kernel: hub 6-0:1.0: USB hub found
Jul 28 06:47:43 sentinel kernel: hub 6-0:1.0: 2 ports detected
Jul 28 06:47:43 sentinel kernel: uhci_hcd 0000:00:1d.2: UHCI Host Controller
Jul 28 06:47:43 sentinel kernel: uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 7
Jul 28 06:47:43 sentinel kernel: uhci_hcd 0000:00:1d.2: detected 2 ports
Jul 28 06:47:43 sentinel kernel: uhci_hcd 0000:00:1d.2: irq 18, io base 0x000018a0
Jul 28 06:47:43 sentinel kernel: hub 7-0:1.0: USB hub found
Jul 28 06:47:43 sentinel kernel: hub 7-0:1.0: 2 ports detected
Jul 28 06:47:43 sentinel kernel: ata_piix 0000:00:1f.2: version 2.13
Jul 28 06:47:43 sentinel kernel: ata_piix 0000:00:1f.2: MAP [ P0 P2 IDE IDE ]
Jul 28 06:47:43 sentinel kernel: scsi0 : ata_piix
Jul 28 06:47:43 sentinel kernel: scsi1 : ata_piix
Jul 28 06:47:43 sentinel kernel: ata1: SATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0x18e0 irq 14
Jul 28 06:47:43 sentinel kernel: ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x18e8 irq 15
Jul 28 06:47:43 sentinel kernel: usb 4-4: new high-speed USB device number 2 using ehci-pci
Jul 28 06:47:43 sentinel kernel: ata2.00: ATAPI: MATSHITADVD-RAM UJ-85JS, FYX4, max UDMA/66
Jul 28 06:47:43 sentinel kernel: ata1.00: ATA-8: FUJITSU MHW2120BH, 00000012, max UDMA/100
Jul 28 06:47:43 sentinel kernel: ata1.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 0/32)
Jul 28 06:47:43 sentinel kernel: ata2.00: configured for UDMA/66
Jul 28 06:47:43 sentinel kernel: ata1.00: configured for UDMA/100
Jul 28 06:47:43 sentinel kernel: scsi 0:0:0:0: Direct-Access ATA FUJITSU MHW2120B 0000 PQ: 0 ANSI: 5
Jul 28 06:47:43 sentinel kernel: scsi 1:0:0:0: CD-ROM MATSHITA DVD-RAM UJ-85JS FYX4 PQ: 0 ANSI: 5
Jul 28 06:47:43 sentinel kernel: sd 0:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/111 GiB)
Jul 28 06:47:43 sentinel kernel: sd 0:0:0:0: [sda] Write Protect is off
Jul 28 06:47:43 sentinel kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Jul 28 06:47:43 sentinel kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jul 28 06:47:43 sentinel kernel: sda: sda1 sda2 sda3 sda4
Jul 28 06:47:43 sentinel kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Jul 28 06:47:43 sentinel kernel: sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda caddy
Jul 28 06:47:43 sentinel kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
Jul 28 06:47:43 sentinel kernel: sr 1:0:0:0: Attached scsi CD-ROM sr0
Jul 28 06:47:43 sentinel kernel: tsc: Refined TSC clocksource calibration: 1462.999 MHz
Jul 28 06:47:43 sentinel kernel: firewire_core 0000:08:06.0: created device fw0: GUID 00023f79af40a4d3, S400
Jul 28 06:47:43 sentinel kernel: Switched to clocksource tsc
Jul 28 06:47:43 sentinel kernel: random: nonblocking pool is initialized
Jul 28 06:47:43 sentinel kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
Jul 28 06:47:43 sentinel kernel: EXT4-fs (sda2): re-mounted. Opts: data=ordered
Jul 28 06:47:43 sentinel systemd-journal[118]: Journal started
-- Subject: The Journal has been started
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- The system journal process has been starting up, opened the journal
-- files for writing and is now ready to process requests.
Jul 28 06:47:43 sentinel systemd-udevd[141]: starting version 215
Jul 28 06:47:44 sentinel kernel: Monitor-Mwait will be used to enter C-1 state
Jul 28 06:47:44 sentinel kernel: Monitor-Mwait will be used to enter C-2 state
Jul 28 06:47:44 sentinel kernel: Monitor-Mwait will be used to enter C-3 state
Jul 28 06:47:44 sentinel kernel: tsc: Marking TSC unstable due to TSC halts in idle
Jul 28 06:47:44 sentinel kernel: ACPI: acpi_idle registered with cpuidle
Jul 28 06:47:44 sentinel kernel: Switched to clocksource hpet
Jul 28 06:47:44 sentinel kernel: input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input2
Jul 28 06:47:44 sentinel kernel: ACPI: Lid Switch [LID0]
Jul 28 06:47:44 sentinel kernel: input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3
Jul 28 06:47:44 sentinel kernel: ACPI: Power Button [PWRB]
Jul 28 06:47:44 sentinel kernel: input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input4
Jul 28 06:47:44 sentinel kernel: ACPI: Sleep Button [SLPB]
Jul 28 06:47:44 sentinel kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input5
Jul 28 06:47:44 sentinel kernel: ACPI: Power Button [PWRF]
Jul 28 06:47:44 sentinel kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 28 06:47:44 sentinel kernel: wmi: Mapper loaded
Jul 28 06:47:44 sentinel kernel: ACPI: Battery Slot [BAT1] (battery present)
Jul 28 06:47:44 sentinel kernel: ACPI: AC Adapter [ACAD] (on-line)
Jul 28 06:47:44 sentinel kernel: Linux agpgart interface v0.103
Jul 28 06:47:44 sentinel kernel: ACPI Warning: SystemIO range 0x00001028-0x0000102f conflicts with OpRegion 0x00001000-0x0000107f (\PMIO) (20131218/utaddress-258)
Jul 28 06:47:44 sentinel kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 28 06:47:44 sentinel kernel: ACPI Warning: SystemIO range 0x000011b0-0x000011bf conflicts with OpRegion 0x00001180-0x000011bb (\GPIO) (20131218/utaddress-258)
Jul 28 06:47:44 sentinel kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 28 06:47:44 sentinel kernel: ACPI Warning: SystemIO range 0x00001180-0x000011af conflicts with OpRegion 0x00001180-0x000011bb (\GPIO) (20131218/utaddress-258)
Jul 28 06:47:44 sentinel kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 28 06:47:44 sentinel kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 28 06:47:45 sentinel kernel: agpgart-intel 0000:00:00.0: Intel 965GM Chipset
Jul 28 06:47:45 sentinel kernel: agpgart-intel 0000:00:00.0: detected gtt size: 524288K total, 262144K mappable
Jul 28 06:47:45 sentinel kernel: agpgart-intel 0000:00:00.0: detected 8192K stolen memory
Jul 28 06:47:45 sentinel kernel: agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000
Jul 28 06:47:45 sentinel kernel: ACPI: Invalid active0 threshold
Jul 28 06:47:45 sentinel kernel: thermal LNXTHERM:00: registered as thermal_zone0
Jul 28 06:47:45 sentinel kernel: ACPI: Thermal Zone [TZ00] (44 C)
Jul 28 06:47:45 sentinel kernel: ACPI Warning: SystemIO range 0x00001c00-0x00001c1f conflicts with OpRegion 0x00001c00-0x00001c0f (\_SB_.PCI0.SBUS.SMBI) (20131218/utaddress-258)
Jul 28 06:47:45 sentinel kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 28 06:47:45 sentinel kernel: [drm] Initialized drm 1.1.0 20060810
Jul 28 06:47:45 sentinel kernel: ideapad_laptop: timeout in read_ec_cmd
Jul 28 06:47:45 sentinel kernel: input: Ideapad extra buttons as /devices/platform/VPC2004:00/input/input6
Jul 28 06:47:45 sentinel kernel: cfg80211: Calling CRDA to update world regulatory domain
Jul 28 06:47:45 sentinel kernel: pps_core: LinuxPPS API ver. 1 registered
Jul 28 06:47:45 sentinel kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]>
Jul 28 06:47:45 sentinel kernel: r852: driver loaded successfully
Jul 28 06:47:45 sentinel kernel: PTP clock support registered
Jul 28 06:47:45 sentinel kernel: [drm] Memory usable by graphics device = 512M
Jul 28 06:47:45 sentinel kernel: checking generic (d0000000 3f0000) vs hw (d0000000 10000000)
Jul 28 06:47:45 sentinel kernel: fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver
Jul 28 06:47:45 sentinel kernel: Console: switching to colour dummy device 80x25
Jul 28 06:47:45 sentinel kernel: i915 0000:00:02.0: irq 44 for MSI/MSI-X
Jul 28 06:47:45 sentinel kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Jul 28 06:47:45 sentinel kernel: [drm] Driver supports precise vblank timestamp query.
Jul 28 06:47:45 sentinel kernel: vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
Jul 28 06:47:45 sentinel kernel: [drm] initialized overlay support
Jul 28 06:47:46 sentinel kernel: tg3.c:v3.136 (Jan 03, 2014)
Jul 28 06:47:46 sentinel kernel: tg3 0000:06:00.0 eth0: Tigon3 [partno(BCM95906) rev c002] (PCI Express) MAC address 00:1b:38:98:bc:f2
Jul 28 06:47:46 sentinel kernel: tg3 0000:06:00.0 eth0: attached PHY is 5906 (10/100Base-TX Ethernet) (WireSpeed[0], EEE[0])
Jul 28 06:47:46 sentinel kernel: tg3 0000:06:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
Jul 28 06:47:46 sentinel kernel: tg3 0000:06:00.0 eth0: dma_rwctrl[76180000] dma_mask[64-bit]
Jul 28 06:47:46 sentinel kernel: iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, in-tree:s
Jul 28 06:47:46 sentinel kernel: iwl3945: Copyright(c) 2003-2011 Intel Corporation
Jul 28 06:47:46 sentinel kernel: iwl3945 0000:04:00.0: can't disable ASPM; OS doesn't have ASPM control
Jul 28 06:47:46 sentinel kernel: snd_hda_intel: unknown parameter 'vid' ignored
Jul 28 06:47:46 sentinel kernel: snd_hda_intel: unknown parameter 'pid' ignored
Jul 28 06:47:46 sentinel kernel: fbcon: inteldrmfb (fb0) is primary device
Jul 28 06:47:46 sentinel kernel: iwl3945 0000:04:00.0: Tunable channels: 11 802.11bg, 13 802.11a channels
Jul 28 06:47:46 sentinel kernel: iwl3945 0000:04:00.0: Detected Intel Wireless WiFi Link 3945ABG
Jul 28 06:47:46 sentinel kernel: iwl3945 0000:04:00.0: irq 45 for MSI/MSI-X
Jul 28 06:47:46 sentinel kernel: r592: driver successfully loaded
Jul 28 06:47:46 sentinel kernel: input: PC Speaker as /devices/platform/pcspkr/input/input7
Jul 28 06:47:46 sentinel kernel: media: Linux media interface: v0.10
Jul 28 06:47:46 sentinel kernel: ieee80211 phy0: Selected rate control algorithm 'iwl-3945-rs'
Jul 28 06:47:46 sentinel kernel: microcode: CPU0 sig=0x6fd, pf=0x80, revision=0xa1
Jul 28 06:47:46 sentinel kernel: microcode: CPU1 sig=0x6fd, pf=0x80, revision=0xa1
Jul 28 06:47:46 sentinel kernel: microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
Jul 28 06:47:46 sentinel kernel: Adding 2000088k swap on /dev/sda3. Priority:-1 extents:1 across:2000088k FS
Jul 28 06:47:46 sentinel kernel: iTCO_vendor_support: vendor-support=0
Jul 28 06:47:46 sentinel systemd-udevd[152]: renamed network interface wlan0 to wlp4s0
Jul 28 06:47:46 sentinel kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
Jul 28 06:47:46 sentinel kernel: iTCO_wdt: Found a ICH8M TCO device (Version=2, TCOBASE=0x1060)
Jul 28 06:47:46 sentinel kernel: iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
Jul 28 06:47:46 sentinel kernel: Console: switching to colour frame buffer device 160x50
Jul 28 06:47:46 sentinel kernel: i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
Jul 28 06:47:46 sentinel kernel: i915 0000:00:02.0: registered panic notifier
Jul 28 06:47:46 sentinel kernel: Linux video capture interface: v2.00
Jul 28 06:47:46 sentinel systemd-udevd[148]: renamed network interface eth0 to enp6s0
Jul 28 06:47:46 sentinel kernel: ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
Jul 28 06:47:46 sentinel kernel: ideapad_laptop: timeout in write_ec_cmd
Jul 28 06:47:46 sentinel kernel: acpi device:09: registered as cooling_device2
Jul 28 06:47:46 sentinel kernel: input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/input/input9
Jul 28 06:47:46 sentinel kernel: [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
Jul 28 06:47:46 sentinel kernel: snd_hda_intel 0000:00:1b.0: irq 46 for MSI/MSI-X
Jul 28 06:47:47 sentinel kernel: input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input10
Jul 28 06:47:47 sentinel kernel: uvcvideo: Found UVC 1.00 device USB 2.0 Camera (04f2:b008)
Jul 28 06:47:47 sentinel kernel: input: USB 2.0 Camera as /devices/pci0000:00/0000:00:1d.7/usb4/4-4/4-4:1.0/input/input11
Jul 28 06:47:47 sentinel kernel: usbcore: registered new interface driver uvcvideo
Jul 28 06:47:47 sentinel kernel: USB Video Class driver (1.1.1)
Jul 28 06:47:47 sentinel kernel: input: HDA Intel Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14
Jul 28 06:47:47 sentinel kernel: input: HDA Intel Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
Jul 28 06:47:47 sentinel systemd-fsck[178]: /dev/sda4: recovering journal
Jul 28 06:47:47 sentinel kernel: input: ALPS PS/2 Device as /devices/platform/i8042/serio1/input/input12
Jul 28 06:47:47 sentinel kernel: input: AlpsPS/2 ALPS GlidePoint as /devices/platform/i8042/serio1/input/input8
Jul 28 06:47:47 sentinel kernel: mousedev: PS/2 mouse device common for all mice
Jul 28 06:47:47 sentinel kernel: usb 1-2: new full-speed USB device number 2 using uhci_hcd
Jul 28 06:47:48 sentinel systemd-fsck[178]: /dev/sda4 contains a file system with errors, check forced.
Jul 28 06:47:48 sentinel kernel: Bluetooth: Core ver 2.18
Jul 28 06:47:48 sentinel kernel: NET: Registered protocol family 31
Jul 28 06:47:48 sentinel kernel: Bluetooth: HCI device and connection manager initialized
Jul 28 06:47:48 sentinel kernel: Bluetooth: HCI socket layer initialized
Jul 28 06:47:48 sentinel kernel: Bluetooth: L2CAP socket layer initialized
Jul 28 06:47:48 sentinel kernel: Bluetooth: SCO socket layer initialized
Jul 28 06:47:48 sentinel kernel: usbcore: registered new interface driver btusb
Jul 28 06:47:48 sentinel kernel: hda-codec: out of range cmd 1:a:100:fffffffe
Jul 28 06:47:50 sentinel systemd-fsck[178]: /dev/sda4: Inode 2753367, i_blocks is 1552, should be 1536. FIXED.
Jul 28 06:47:50 sentinel systemd-fsck[178]: /dev/sda4: Inodes that were part of a corrupted orphan linked list found.
Jul 28 06:47:50 sentinel systemd-fsck[178]: /dev/sda4: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Jul 28 06:47:50 sentinel systemd-fsck[178]: (i.e., without -a or -p options)
Jul 28 06:47:50 sentinel systemd-fsck[178]: fsck failed with error code 4.
Jul 28 06:47:50 sentinel systemd-fsck[178]: Running request emergency.target/start/replace
Jul 28 06:47:50 sentinel kernel: EXT4-fs (sda4): warning: mounting fs with errors, running e2fsck is recommended
Jul 28 06:47:50 sentinel kernel: EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: data=ordered
Jul 28 06:47:51 sentinel systemd-journal[118]: Permanent journal is using 520.1M (max allowed 2.8G, trying to leave 354.1M free of 18.5G available → current limit 2.8G).
Jul 28 06:47:51 sentinel systemd-journal[118]: Time spent on flushing to /var is 509.727ms for 733 entries.
Jul 28 06:47:50 sentinel systemd[203]: Failed at step EXEC spawning /bin/plymouth: No such file or directory
-- Subject: Process /bin/plymouth could not be executed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- The process /bin/plymouth could not be executed and failed.
-- The error number returned while executing this process is 2.
Jul 28 06:48:05 sentinel dbus[241]: [system] Successfully activated service 'org.freedesktop.systemd1'
Jul 28 06:48:05 sentinel systemd-logind[240]: New seat seat0.
-- Subject: A new seat seat0 is now available
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
-- A new seat seat0 has been configured and is now available.
Jul 28 06:48:05 sentinel systemd-logind[240]: Watching system buttons on /dev/input/event4 (Power Button)
Jul 28 06:48:05 sentinel systemd-logind[240]: Watching system buttons on /dev/input/event7 (Video Bus)
Jul 28 06:48:05 sentinel systemd-logind[240]: Watching system buttons on /dev/input/event2 (Power Button)
Jul 28 06:48:05 sentinel systemd-logind[240]: Watching system buttons on /dev/input/event1 (Lid Switch)
Jul 28 06:48:05 sentinel systemd-logind[240]: Watching system buttons on /

I'm not a hardware person, but I doubt it can be repaired.
You might put it in a USB enclosure and try to access the data from another computer. Some have had luck with this treatment.
-Jerry

Fsck error after installation

Hi Everyone!
I installed Arch on my system with three hdds, sda, sdb, and sdc. Arch is installed on sdb with two linux partitions, sdb1 and sdb2. On sda and sdc I use Windows and they are ntfs formatted.
I don't want to use those two disks in Arch, so I only have sdb1 and sdb2 in fstab and sdb1, which is bootable and mounted at /boot, in syslinux.
But when I try to boot the system, I get an error from fsck:
fsck: fsck.ntfs: not found
dsck: error 2 while executing fsck.ntfs for /dev/sda1
ERROR: fsck failed on '/dev/sda1'
:: mounting '/dev/sda1' on real root
mount: unknown filesystem type 'ntfs'
So I googled how to disable fsck for those disks and tried
tune2fs -c 0 /dev/sda
and also
tune2fs -c 0 /dev/sda1
which both raised the error
tune2fs: Bad magic number in super-block while trying to open /dev/sda(1)
Couldn't find valid filesystem superblock
So I can't boot because these disks can't be checked, but I can't seem to be able to disable checking either. And I don't want to fiddle around with reading ntfs drives on linux.
What is wrong and what can I do? Arch shouldn't concern itself with sda at all, I just want it to leave the disk alone...
Thanks in advance!

mohack wrote:In the bootloader config for syslinux, there is only sdb1, which is the linux boot partiton. On my virtualbox with only one virtual disk, it works this way. Or what do you mean?
Prove it. Post your config. My claim is that you're passing root=/dev/sda1 in the APPEND line for the selected bootloader entry. That's the logical reason that the initramfs wants to fsck and mount /dev/sda1.
mohack wrote:bohoomil: I know how to use the check flags in fstab (at least I think so), but those disks sda and sdc are not in fstab! Only the two linux partitions sdb1 and sdb2 are in fstab. I generated fstab and installed and configured the syslinux bootloader exactly as described in Arch-fstab and Arch-Syslinux.
This worked perfectly fine on my Virtualbox, but on this system with the three disks, it doesn't.
sdb? are ext4, same as in the working VB installation.
None of this is relevant when /etc/fstab isn't even available yet.
Last edited by falconindy (2012-12-17 02:01:09)

Custom kernel config and fsck error

Why does arch kernel config pass while custom kernel config fail the fsck during boot? Udev obviously populates /dev/sda* with the archlinux kernel config while the custom kernel config populates /dev/hda*. Is there a reason for this behavior related to the config file or is it a initscript based on /etc/fstab related issue? I have the two different kernel configuration files for the i686 machines, just in case someone can figure this out.
http://aur.archlinux.org/packages/longe … ig-longene
http://aur.archlinux.org/packages/longe … -archlinux

Check to make sure that it is not because of the system time being changed. It will complain about this if it has changed and fail the first filesystem check.
Last edited by Wintervenom (2009-09-08 15:56:26)

Repeated Disk Utility & fsck errors - what to do next?

After nearly a year of flawless operation (yes, my warranty will soon expire), my iMac has suddenly started to misbehave. Disk Utility has reported finding errors which it is unable to repair. I've run fsck_hfs in single-user mode a couple of times, and after each reboot it again finds errors. Then I bought DiskWarrior and it repaired my drive. All was well for nearly a day, and now I'm back to the same situation. So, what to do now?
Should I reinstall the OS and just run it bare without any additional apps for a while, to see if I get more errors? (I've made a SuperDuper! bootable backup which I should be able to reboot from if needed). Or are these repeated errors to be more likely the sign of permanent problems with my hard disc, and I should go to the local Apple store without wasting any more time?
Fortunately I have a Powerbook to hold me over as a spare machine if I do have to give up my iMac.
All suggestions welcome.
Thanks
S

Since you have a backup I'd suggest you wipe the drive and reinstall. Do this:
Extended Hard Drive Preparation
1. Boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger or Leopard.)
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Set the number of partitions from the dropdown menu (use 1 partition unless you wish to make more.) Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID (only required for Intel Macs) then click on the OK button. Click on the Partition button and wait until the volume(s) mount on the Desktop.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
Upon completion quit DU and return to the installer. Now complete the reinstallation of OS X.

[SOLVED] Error while booting, related to nilfs2

I've just installed my fresh Arch and used nilfs2 inside vlm2 as my home partition. While booting, I'm getting these errors:
fsck: fsck.nilfs2: not found
fsck: error 2 while executing fsck.nilfs2 for /dev/mapper/TheVG-HomeLV
Other logical volumes are getting "clean" output while checked so it's not vlm-related; they are all ext4.
Partition is mounted and seems to work but I'm scared of just ignoring it and creating my user. ;-)
I have nilfs-utils installed. Is there any hook or module I need to add somewhere in order to use nilfs2 properly (like reiserfs hook)? There is nothing in the Wiki about this file system...
Edit: well, it appears that nilfs doesn't not come with check utility so I'm marking this as solved; sorry for garbage post...
Last edited by smsware (2013-03-16 22:07:55)

As there is no fsck utility and as it actually is planned to be created (I read that it's needed because the fs can easily crash on power loss; still, it can be recreated, as you stated) - there is a warning while building the kernel. I deleted fsck hook to not see it as my /var and root are sub-volumes of btrfs partition which doesn't need fsck as well. I made a service to umount, fsck and mount back the /boot (ext4) and uefi partitions... just to let you know what you can expect. But it's great anyway, snapshots are really easy to mount and use. I thought it has no wiki page because it's not popular (and probably for a reason) but now I believe it's because there is nothing to write about... it just works. ;-)
Last edited by smsware (2013-05-29 15:58:26)

[solved]udev boot error - usb keyboard wont work in recovery shell

i just hooked up an external drive for the first time to this system, i didnt do anything to it yet, except i went to run gdisk and realized it wasnt installed yet. So i ran
pacman -Syu gdisk
from an SSh terminal, then when it was updating a package, cant exactly remember which one but i hitnk it was either kernel or udev, the ssh termilal appeared to disconnect becuause it lost its output.
then i opened another terminal sshed in, and was able to run pacman -Syu again, which means the first update did finish, or the lockfile wouldnt have let me update a 2nd time i would think. (note, the newly external hard drive was connected during all these events). Something wierd happened here.It had files that needed updating, which i thought that would be rare since i just updated, unless it simply didnt finish, and the lockfile wasnt in place or something, then it finished updating successfully, and i was still remoted into a working SSH command line (i.e. didnt get kicked out this time).
Now is where the fun begins. i typed 'reboot', and the system appeared to reboot, but i wasnt able to shell in this time. i connected the monitor to the system almost a minute later, and realized it was still shutting down, then when it rebooted i get an error message.
running early hook [udev]
Warning lib/modules/3.12.8-1-ARCH/modules.devname not found - ignoring
runnign hook [udev]
tiggering events
Waiting 10 seconds for device /dev/sda2
ERROR: device /dev/sda2 not found Skipping fsck
Error unable to find root device /dev/sda2
your being dropped to recovery shell
[rootfs /]#
NOW THE KEYBOARD DOESNT WORK, it only works in bios. It stops functioning (the numlock light) as soon as udev starts to initiate, which leaves me with no way to try to reupdate udev and the kernel again to see if i can fix it.
all i could think of was to disconnect the external drive, that didnt help. then i tried checking the USB settings in bios for any legacy options, it doesnt have them (Dell Optiplex), so i just made sure the USB boot was off and all ports enabled.
Now im totally stuck short of a recovery disk.
any suggestions how i can just get the keyboard working and chroot into arch and update some package to fix it without having to jump through hoops to make a recovery disk while here at work with limited resources?
Last edited by wolfdogg (2014-01-22 22:53:02)

ok i found what happened, so far.
looking in /var/log/pacman.log i see a gap in the installs, a 2 minute gap, which is the time i rebooted and reran the install.
at 9:25.. i was running an upgrade, and the last one in the minute of 9:25 is
9:25[PACMAN] upgraded linux-firmware (20131013.7d0c7a8-1 -> 20131230.52d77db-1)
this is where the shell got disconnected therefore i wasnt able to see what happened after this.
the the log continues at 9:27 minute, has to be when i rebooted and shelled back in and reran the upgrade, the log starts with
9:27[PACMAN] upgraded linux (3.12.6-1 -> 3.12.8-1)
so it appears that the shell got disconnected as it was upgrading linux-firmware (20131013.7d0c7a8-1 -> 20131230.52d77db-1) .
This begs the questions; Did the SSH shell get disconnected simply because the system was using those resources at the time? i assume this. the next question is, was it wrong to be upgrading via remote SSH shell then? Or whats likely that happened here?
Last edited by wolfdogg (2014-01-22 22:20:04)

[fsck] Superblock last write time is in the future

Hello,
I have HARDWARECLOCK="localtime" in my rc.conf but every time I reboot I get the below fsck error
Superblock last write time is in the future
then I am required to enter root password to get a shell. I usually fix the issue by remounting the root partition as read-write and rebooting. Strangely, on next reboot fsck will fix the issue, run a complete fsck and then give me my Arch Linux.
Some notes:
1) I have always had this last write time issue, but previously (1 month ago?) fsck just fixed it and continued the boot process, didn't stop asking me the root password
2) if I use 'rw' in the kernel command-line I can never boot because it always stops asking for root password, even after running fsck through a livecd, so I am currently using 'ro'
Has somebody any clue about this problem?
My relevant fstab line is:
LABEL=LINUX / ext3 defaults,noatime 0 1
Thanks
Last edited by legolas558 (2009-10-06 10:59:43)

Ramses de Norre wrote:I encountered this too and I worked around it by setting my bios clock to my system time, it was a month off. I never encountered this issue before though and I guess this is a bug in some program (fsck?).
So until this is fixed, try setting your bios clock to the same time your system's at. And maybe file a bug.
This is not a solution! There is a reason if I keep localtime in my system, and no I am not going to change it because of a bug. That's Windows solutions, not Linux.
Some bug reports found with uncle Google:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540575
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343662
https://bugs.launchpad.net/ubuntu/+sour … bug/427822

Error when upgrading kernel (error: command failed to execute corre...

Hi, twice now when upgrading the kernel I have seen
"error: command failed to execute correctly"
in pacmans output, any ideas as to what it might be?
Bit of pacman output:
( 4/11) upgrading fontconfig [###################] 100%
updating font cache... done.
( 5/11) upgrading gpm [###################] 100%
( 6/11) upgrading linux [###################] 100%
>>> Updating module dependencies. Please wait ...
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.9.3-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> ERROR: file not found: `fsck.btrfs'
==> WARNING: No fsck helpers found. fsck will not be run on boot.
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.9.3-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: bfa
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
error: command failed to execute correctly
( 7/11) upgrading man-db [###################] 100%
( 8/11) upgrading mdadm
jason@jason-laptop ~ % sudo mkinitcpio -p linux
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.9.3-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> ERROR: file not found: `fsck.btrfs'
==> WARNING: No fsck helpers found. fsck will not be run on boot.
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.9.3-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: bfa
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful

First search result: https://bbs.archlinux.org/viewtopic.php?id=139370
Please make some effort yourself...

ERROR: Device '/dev/sda3' not found.

This is my first time compiling a custom kernel. I am trying to compile zen kernel 3.12.3. Whenever I try to boot it up, it says this:
ERROR: device '/dev/sda3' not found. Skipping fsck
ERROR: Unable to find root device '/dev/sda3'
Then it drops me to a recovery shell. When I look at the contents of '/dev' none of my partitions are found on sda. '/dev/sda' is listed but nothing else. Has anybody else had this problem? /i have read various fixes but none of them have helped.
Sorry this is my first post.
Thanks in advance.

Well, the whole point of the initramfs is to have it load the necessary modules to mount the rootfs. So if mkinitpcio complains that there are no modules to put in there, that is pretty problematic.
I think you should take a look at the PKGBUILD for the official Arch kernel. It includes a few lines that allow you to use menuconfig or nconfig or whatever, prior to that actual 'make'. I think that any time you install things to your system, you should probably be leveraging the package manager in order to properly track the files. This is particularly true when you are an Arch user and the creation of packages is so damn easy.

Fsck.ntfs ?

I'm pretty sure this is a stupid question, but...
[raul@horus ~]$ sudo fsck -t ntfs /dev/sda2
fsck 1.40.8 (13-Mar-2008)
fsck: fsck.ntfs: not found
fsck: Error 2 while executing fsck.ntfs for /dev/sda2

ntfsck is not yet available.
http://www.linux-ntfs.org/doku.php?id=ntfsck

Macbook Pro 8,2 EFI_STUB loading with rEFInd Failing

Hello fellow Arch users, I've been struggling with trying to get Arch running on my Macbook Pro 8,2 (Early 2011) for the past couple of days and I was hoping that the collective intelligence of the community might be able to help me. I feel that the combination of recent changes in the installation medium, using a Macbook, and my hardware modifications have all converged to make it hard to diagnose what is wrong. First off for hardware I have:
Processor: Core i7 (I7-2820QM)
Integrated Graphics: Intel HD Graphics 3000
Dedicated Graphics: AMD Radeon HD 6750M 1024 MB
Ram: 16G (8Gx2) 1333 MHz
Internal Harddrive: 1Tb WDC WD10TPVT-00HT5T1
Internal Harddrive (in optical drive spot with an OWC Data Doubler): 128Gb APPLE SSD TS128C
I have the SSD setup with only OSX and I planned on installing Arch to the HHD and using rEFInd to boot everything with EFI_STUB. Initially started by trying to install from an external source, but was unable to do so. In the past I had attempted to install windows 7 from an external CD drive only to learn that it is essentially imposible (it would appear to firmware constraint as the Macbook Airs and rMacbook Pros as able to) and I wonder if the same constraint applies for linux live CDs. I tried the "Remove UEFI boot support from ISO" from the UEFI page as well and that did not help. Oddly enough I also was unable to get any usb medium to work as well (both the regular install disk and Archboot, the "Create UEFI bootable USB from ISO" method of the UEFI page) even though it seems that many others have successfully gotten this to work and it should not be affected by my modifications.
At this point I removed the SSD from inside and replaced it with the original super drive. rEFInd will not boot it through efi, but will boot it through BIOS emulation (the partition is listed as windows in rEFInd). From there I followed the standard insertion procedure to get Arch installed (following UEFI_Bootloaders#Linux_Kernel_EFISTUB, Unified_Extensible_Firmware_Interface#Create_an_UEFI_System_Partition_in_Linux and MacBook_Pro_8,1_/_8,2_/_8,3_(2011_Macbook_Pro):
$ cgdisk /dev/sda
512M partition of type EF00, name efi
the rest default type (linux), name root
$ mkfs.vfat -F32 /dev/sda1
$ mkfs.ext4 /dev/sda2
$ mount /dev/sda2 /mnt
$ mkdir /mnt/boot/efi
$ mount /dev/sda1 /mnt/boot/efi
$ mkdir /mnt/boot/efi/EFI/arch/
$ pacstrap /mnt base{,-devel}
$ genfstab -p /mnt >> /mnt/etc/fstab
$ arch-chroot /mnt
$ nano /etc/mkinitcpio.conf
MODULES="..ahci libahci.." #The Macbook page recommends this and I tried it with sd_mod as well based off some previous forum posts.
$ mkinitcpio -p linux
$ cp /boot/vmlinuz-linux /boot/efi/EFI/arch/vmlinuz-arch.efi
$ cp /boot/initramfs-linux.img /boot/efi/EFI/arch/initramfs-arch.img
$ cp /boot/initramfs-linux-fallback.img to /boot/efi/EFI/arch/initramfs-arch-fallback.img
# create /boot/efi/EFI/arch/refind_linux.conf as instructed with the UUID of sda2
$ echo “archy” >> /etc/hostname
$ ln -s /usr/share/zoneinfo/America/New_York /etc/localtime
$ echo “America/New_York” >> /etc/timezone
$ vi /etc/locale.gen
/#en_US and uncomment
$ locale-gen
$ hwclock --systohc --utc
$ echo “KEYMAP=us” >> /etc/vconsole.conf
$ passwd root
$ exit
$ umount /mnt/boot/efi
$ umount /mnt
$ reboot
When I reboot rEFInd does not show the arch partition, but if I boot holding option to bring up the built in partition selection and select the efi partition, rEFInd loads showing the arch linux partition. At this point it loads and gets stuck displaying:
Error: device '' not found. Skipping fsck
Error: Unable to find root device ''.
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: cant access tty; job control turned off
[rootfs /]#
I've tried mounting /dev/sda and I simply presents the same error again.
I can confirm the default kernel has EFI_STUB enable as:
$ zcat /proc/config.gz | grep EFI_STUB
displays:
CONFIG_EFI_STUB=y
Any help would be greatly appreciated. I have refined installed on the SSD with OSX and most guides have it installed on the EFI partition with Arch. Is there a different approach I should be taking to set this up with two disks? Thanks.

So, I really don't want to hijack this thread, but seeing that I've now 'repaired' my system from the damage mentioned before, I feel I should.
@WonderWoofy:
Well, I very much doubt that this was an issue with my firmware, my reasoning being that it quite simply did not change, the arch-packages however did, quite invasively I may add.
To clarify,
linux (3.6.2-1 -> 3.6.4-1) was the update that broke my systen boot for me.
linux (3.6.4-1 -> 3.6.6-1) since today has again fixed it.
My custom kernel was just vanilla 3.6.0.
So what I did to repair, was to boot up using a live-cd and after discovering I still had my custom-built kernel I copied it back to my EFI-partition, and guess what, it no longer booted!!
to be more precise, it booted, but no display, and after my hdd seemed to have settled, unresponsive/frozen system, hard-reset the only option. The stock kernel(3.6.4-1) never did boot, just froze immediately on load(I could still see the efi-shell).
So, I figured it must be systemd`s fault (because its responsible for loading my system and it was probably no longer working properly with the older kernel version + udev).
My solution was to boot using an older arch-installation cd (in bios-mode!!! again efimode broken) and chroot, update the system, and for now it seems to work again.
So I restate, that arch+efi can be quite unstable at times, even though it could well be my 'luck' to have multiple issues all at once.
To round this off, and maybe benefit the OP, I thought I'd clarify my setup.
I have a single disk, gpt formatted. It holds 7 partitions:
/dev/sda1 -> EFI
/dev/sda2 -> MSRESERVE
/dev/sda3 -> WINDOWS
/dev/sda4 -> DATA
/dev/sda5 -> LINUX
/dev/sda6 -> HOME
/dev/sda7 -> SWAP
Note, I do not have a separate boot partition.
My LINUX partition is laid out in the following way:
/boot -> contains the stock vmlinuz-linux and initramfs-linux.img
/boot/efi -> mountpoint for the EFI partition
fstab entry:
/dev/sda1 /boot/efi vfat rw,noexec,fmask=0113,dmask=0022 0 0
When mounted in such a way, /boot/efi contains:
ls -l /boot/efi/ ->
drwxr-xr-x 8 root root 2.0K Nov 20 14:29 EFI/
ls -l /boot/efi/EFI/ ->
drwxr-xr-x 2 root root 2.0K Nov 20 14:30 arch/
drwxr-xr-x 2 root root 2.0K Nov 20 14:30 archmy/
drwxr-xr-x 2 root root 2.0K Jun 15 19:41 Boot/
drwxr-xr-x 3 root root 2.0K Jun 15 19:25 Microsoft/
drwxr-xr-x 4 root root 2.0K Aug 9 14:48 refind/
drwxr-xr-x 2 root root 2.0K Aug 9 15:09 tools/
Now of interest are the /boot/efi/EFI/refind/ and /boot/efi/EFI/arch folders.
Notice the /boot/efi/EFI/archmy folder is for my custom kernel mentioned above.
Separate folders are one way to use refind's auto-detection mechanism (hence no need to mess with manual boot stanzas) and not have the arch-specific problem of unversioned kernel files.
So /boot/efi/EFI/arch contains:
-rw-rw-r-- 1 root root 13M Nov 21 13:08 initramfs-linux-fallback.img
-rw-rw-r-- 1 root root 4.0M Nov 21 13:08 initramfs-linux.img
-rw-rw-r-- 1 root root 200 Nov 20 14:14 refind_linux.conf
-rw-rw-r-- 1 root root 3.4M Nov 21 13:08 vmlinuz-linux.efi
and /boot/efi/EFI/refind contains:
drwxr-xr-x 2 root root 2.0K Aug 9 14:48 drivers_x64/
drwxr-xr-x 2 root root 4.0K Aug 9 14:48 icons/
-rw-rw-r-- 1 root root 12K Nov 20 14:14 refind.conf
-rw-rw-r-- 1 root root 137K Jun 23 23:26 refind_x64.efi
The two important configuration files are /boot/efi/EFI/arch/refind_linux.conf:
"Boot with Default Options" "root=/dev/sda5 ro rootfstype=ext4 add_efi_memmap"
"Boot with More Options" "root=/dev/sda5 ro rootfstype=ext4 add_efi_memmap radeon.modeset=1 iommu=pt radeon.pcie_gen2=1"
In this case I have two seperate kernel-cmd lines, each with different options. I can select which to use, by selecting the 'kernel-entry' I want when refind loads up(each directory, arch/ and archmy/ are a seperate icon)
and pressing'+'. A menu will appear which will show both those lines and I can choose the one I want. This can also be handy when wanting to boot with debugging options.
For instance, the 'radeon-options' are specific to my hw-setup.
Notice that there is no mention of which initramfs file to use, this is handled by refind automatically, BUT can be wonky if not separating kernel versions properly!!!
The only required option is 'root=/dev/sda5' which obviously points at my root partition. (in this case /dev/sda5 -> LINUX)
And /boot/efi/EFI/refind/refind.conf:
timeout 7
hideui banner,label
#icons_dir myicons
#banner hostname.bmp
#selection_big selection-big.bmp
#selection_small selection-small.bmp
#textonly
#resolution 1024 768
use_graphics_for osx,windows
#showtools shell, about, reboot
#scan_driver_dirs EFI/tools/drivers,drivers
#scanfor internal,external,optical
#also_scan_dirs boot,EFI/linux/kernels
dont_scan_dirs EFI/boot
#scan_all_linux_kernels
#max_tags 0
#default_selection 1
These are just the configuration options I have set/unset. Note that some of the commented-out options are still in use, they are just the defaults.
This gives me automatic kernel detection (as long as properly separating things!) and at least when the image itself is working, results in a boot-able system

[unsolved] BCache issues - Can't figure out what I'm doing wrong

My setup is as follows:
SSD on /dev/sda
HDD on /dev/sdb
I'm doing a EFI setup, so basically I need nothing more that an ESP and ROOT partition on /dev/sdb. I don't mind too much if the ESP partition is cached, but I suspect that could cause problems.
There's really no need to cache ESP, so my approach have been to only cache the root partition:
make-bcache -B /dev/sdb2 -C /dev/sda
Which seem to work.
After this everything seems to go wrong. I've tried several different approached and following the arch, gentoo and the official guide, but regardless I continually stumble.
Following the arch guide: https://wiki.archlinux.org/index.php/Bcache I run in to trouble already at step 3.
for i in /dev/sd*; do echo $i; echo $i > /sys/fs/bcache/register_quiet; done
But as I understand it, the fact that I can't write to register_quiet just mean that I don't need to. Well, that doesn't sound very sensible.
Apparently I can skip step 4., but even so I've tried different approaches as I said. However, no matter what I do, I end up missing /dev/bcache0, /sys/block/bcache0 or something similar, thus preventing me from continuing.
At this point I have no other options than to ask a few question here, and maybe get some advice.
1. In the case described, does sdb need to become backing device, or is it sensible to only make sdb2 (root) the backing device? [probably solved]
2. Assuming that sdb need to become the backing device, will EFI boot even be possible? [solved]
3. is btrfs a necessity, or is any file system in theory viable? [Suspect I don't need to use btrfs]
4. Whatever questions you may think I've left out. [still have issues]
Thanks and best regards.
Last edited by zacariaz (2013-08-19 15:15:12)

Just a small update.
I think I did it mostly right on the last try, however, I couldn't boot:
Attempting to register /dev/sda with bcache
ash: write error: Invalid argument
Attempting to register /dev/sdb with bcache
ash: write error: Invalid argument
Attempting to register /dev/sdb1 with bcache
ash: write error: Invalid argument
Attempting to register /dev/sdb2 with bcache
ash: write error: Invalid argument
Waiting 10 seconds for device /dev/bcache0 ...
ERROR: device '/dev/bcache0' not found. Skipping fsck
ERROR: Unable to find root device '/dev/bcache0'.
The only thing that comes to mind it that I made two boot entries with gummiboot, as I wasn't sure if I should define sdb2 or bcache0 as the root partition, but if that was the issue, I should at least get a boot menu I would think.
So that's how it is right now. I haven't got a clue what might be wrong.
Best regards.

Mac mini server hang at startup

My mac mini server (1st gen) installed with Lion server has a strange problem.
At some point, it stop to deliver it services (imap, dhcp and ical server). I connect on it (wich take a long long time), make it restart by the system menu entry.
It restart, and stay forever with the blank screen with Apple logo and the waiting circle which loop.
No way to restart.
I then boot on a Mountain Lion installation USB key (I loose my Lion one :-( ), choose the restore from time machine option, selecting the last entry on my Time capsule, everything goes well, and the server restart with no problem. I can even restart it by the system menu.
But after 2 or 3 month, it has the same problem, and again no way to restart without restoring the last time machine backup.
It's now the third time it does this, and it's make me go crazy.
I've try to start in verbose mode, and I have the following fsck error message :
disk0s2 : I/O error.
Invalid node structure
(4,26622)
the volume on macintosh hd could not ve verified completely
fsck failed !
I've try to start on single mode and do the fsck -fy -> same result.
Does someone has an idea of why it does this ?
Regards,
Marc

Just recently I ran into a problem when I tried to Verify my hard disk and when it tried to verify the catalog, it responded "Invalid sibling link." Repair Disk didn't work. I searched the web and Apple's site, and couldn't find anything useful except to buy DiskWarrior or reformat the drive. Knowing that OS X is built on Unix gave me a few clues on how to proceed. The solution is pretty simple:
    1.    Boot off the OS X CD (reboot, hold C while booting).
    2.    The installer will load up, go to Utilities in the menu and run Terminal.
    3.    Type df and look for the drive that has your Mac system mounted---you'll have to unmount this. On my MacBook Pro, it was /dev/disk0s2.
    4.    Type umount /dev/disk0s2, replacing disk0s2 with whatever disk your OS lives on.
    5.    Type fsck_hfs -r /dev/disk0s2. If you umounted the wrong thing, it will complain that you can't repair a mounted drive. Go back and umount the right thing and repeat this step.
Just for fun, you might want to run another fsck_hfs on your disk (use the -f option because your drive is probably journaled). Hope this helps someone so they don't buy a program that's going to do pretty much what we did with fsck_hfs, and so they don't waste time searching for an answer to no avail. By the way, TechTool Deluxe (3.1.1) didn't find the Catalog problem for some reason (you'll have this on a CD if you have AppleCare), which is why I resorted to fsck.
http://hints.macworld.com/article.php?story=20070204093925888

Fsck error

Similar Messages

Maybe you are looking for