Is my old Linux/Debian box's Quantum 15 GB HDD dying?

[Ant]

Hello.

I woke up overnight (about six hours since I last used my computer
without any problems) and noticed my old Debian/Linux box was acting
weird (IRC chat bot/rbot gave errors about corrupted database, detached
screen logged me out, could not log back in through SSH2 from a Windows
box on LAN, Xscreensaver wouldn't let me back in locally (PAM errors),
could not ctrl-alt-backspace on local PC, etc.). I did a hard reset to
reboot. I went back to KDE v3.5.10, and noticed it took longer than
usual to boot up and a pause. Then, I noticed scary errors in dmesg:

# dmesg
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.32-5-686 (Debian 2.6.32-30)
(b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed
Jan 12 04:01:41 UTC 2011
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] NSC Geode by NSC
[ 0.000000] Cyrix CyrixInstead
[ 0.000000] Centaur CentaurHauls
[ 0.000000] Transmeta GenuineTMx86
[ 0.000000] Transmeta TransmetaCPU
[ 0.000000] UMC UMC UMC UMC
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000007ff90000 (usable)
[ 0.000000] BIOS-e820: 000000007ff90000 - 000000007ff9e000 (ACPI data)
[ 0.000000] BIOS-e820: 000000007ff9e000 - 000000007ffe0000 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000007ffe0000 - 0000000080000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
[ 0.000000] DMI present.
[ 0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working
around it.
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000
(usable) ==> (reserved)
[ 0.000000] last_pfn = 0x7ff90 max_arch_pfn = 0x100000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-CFFFF write-protect
[ 0.000000] D0000-DFFFF uncachable
[ 0.000000] E0000-EFFFF write-through
[ 0.000000] F0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 000000000 mask F80000000 write-back
[ 0.000000] 1 disabled
[ 0.000000] 2 disabled
[ 0.000000] 3 disabled
[ 0.000000] 4 disabled
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new
0x7010600070106
[ 0.000000] initial memory mapped : 0 - 01800000
[ 0.000000] init_memory_mapping: 0000000000000000-00000000373fe000
[ 0.000000] 0000000000 - 0000400000 page 4k
[ 0.000000] 0000400000 - 0037000000 page 2M
[ 0.000000] 0037000000 - 00373fe000 page 4k
[ 0.000000] kernel direct mapping tables up to 373fe000 @ 10000-16000
[ 0.000000] RAMDISK: 37848000 - 37fef173
[ 0.000000] Allocated new RAMDISK: 00100000 - 008a7173
[ 0.000000] Move RAMDISK from 0000000037848000 - 0000000037fef172 to
00100000 - 008a7172
[ 0.000000] ACPI: RSDP 000f9aa0 00014 (v00 ACPIAM)
[ 0.000000] ACPI: RSDT 7ff90000 0003C (v01 7514MS A7514200 20090904
MSFT 00000097)
[ 0.000000] ACPI: FACP 7ff90200 00084 (v01 7514MS A7514200 20090904
MSFT 00000097)
[ 0.000000] ACPI: DSDT 7ff90440 063EE (v01 A7514 A7514200 00000200
INTL 20051117)
[ 0.000000] ACPI: FACS 7ff9e000 00040
[ 0.000000] ACPI: APIC 7ff90390 0006C (v01 7514MS A7514200 20090904
MSFT 00000097)
[ 0.000000] ACPI: MCFG 7ff90400 0003C (v01 7514MS OEMMCFG 20090904
MSFT 00000097)
[ 0.000000] ACPI: OEMB 7ff9e040 00072 (v01 7514MS A7514200 20090904
MSFT 00000097)
[ 0.000000] ACPI: HPET 7ff98440 00038 (v01 7514MS OEMHPET 20090904
MSFT 00000097)
[ 0.000000] ACPI: SSDT 7ff9e8c0 00A7C (v01 DpgPmm CpuPm 00000012
INTL 20051117)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] 1163MB HIGHMEM available.
[ 0.000000] 883MB LOWMEM available.
[ 0.000000] mapped low ram: 0 - 373fe000
[ 0.000000] low ram: 0 - 373fe000
[ 0.000000] node 0 low ram: 00000000 - 373fe000
[ 0.000000] node 0 bootmap 00012000 - 00018e80
[ 0.000000] (9 early reservations) ==> bootmem [0000000000 - 00373fe000]
[ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==>
[0000000000 - 0000001000]
[ 0.000000] #1 [0000001000 - 0000002000] EX TRAMPOLINE ==>
[0000001000 - 0000002000]
[ 0.000000] #2 [0000006000 - 0000007000] TRAMPOLINE ==>
[0000006000 - 0000007000]
[ 0.000000] #3 [0001000000 - 00014c9bb4] TEXT DATA BSS ==>
[0001000000 - 00014c9bb4]
[ 0.000000] #4 [000009fc00 - 0000100000] BIOS reserved ==>
[000009fc00 - 0000100000]
[ 0.000000] #5 [00014ca000 - 00014d0195] BRK ==>
[00014ca000 - 00014d0195]
[ 0.000000] #6 [0000010000 - 0000012000] PGTABLE ==>
[0000010000 - 0000012000]
[ 0.000000] #7 [0000100000 - 00008a7173] NEW RAMDISK ==>
[0000100000 - 00008a7173]
[ 0.000000] #8 [0000012000 - 0000019000] BOOTMAP ==>
[0000012000 - 0000019000]
[ 0.000000] found SMP MP-table at [c00ff780] ff780
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000010 -> 0x00001000
[ 0.000000] Normal 0x00001000 -> 0x000373fe
[ 0.000000] HighMem 0x000373fe -> 0x0007ff90
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[2] active PFN ranges
[ 0.000000] 0: 0x00000010 -> 0x0000009f
[ 0.000000] 0: 0x00000100 -> 0x0007ff90
[ 0.000000] On node 0 totalpages: 524063
[ 0.000000] free_area_init_node: node 0, pgdat c13b2860, node_mem_map
c14d2200
[ 0.000000] DMA zone: 32 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 3951 pages, LIFO batch:0
[ 0.000000] Normal zone: 1736 pages used for memmap
[ 0.000000] Normal zone: 220470 pages, LIFO batch:31
[ 0.000000] HighMem zone: 2328 pages used for memmap
[ 0.000000] HighMem zone: 295546 pages, LIFO batch:31
[ 0.000000] Using APIC driver default
[ 0.000000] ACPI: PM-Timer IO Port: 0x808
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
[ 0.000000] ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI
0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ2 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0xffffffff base: 0xfed00000
[ 0.000000] SMP: Allowing 4 CPUs, 0 hotplug CPUs
[ 0.000000] nr_irqs_gsi: 24
[ 0.000000] PM: Registered nosave memory: 000000000009f000 -
00000000000a0000
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 -
00000000000e0000
[ 0.000000] PM: Registered nosave memory: 00000000000e0000 -
0000000000100000
[ 0.000000] Allocating PCI resources starting at 80000000 (gap:
80000000:7ee00000)
[ 0.000000] Booting paravirtualized kernel on bare hardware
[ 0.000000] NR_CPUS:32 nr_cpumask_bits:32 nr_cpu_ids:4 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 14 pages/cpu @c2800000 s34296 r0 d23048
u1048576
[ 0.000000] pcpu-alloc: s34296 r0 d23048 u1048576 alloc=1*4194304
[ 0.000000] pcpu-alloc: [0] 0 1 2 3
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on.
Total pages: 519967
[ 0.000000] Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686
root=UUID=fe4a1af1-1979-49fb-9668-314a24b12890 ro quiet nouveau.modeset=0
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288
bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144
bytes)
[ 0.000000] Enabling fast FPU save and restore... done.
[ 0.000000] Enabling unmasked SIMD FPU exception support... done.
[ 0.000000] Initializing CPU#0
[ 0.000000] Initializing HighMem for node 0 (000373fe:0007ff90)
[ 0.000000] Memory: 2064760k/2096704k available (2501k kernel code,
30244k reserved, 1323k data, 376k init, 1191496k highmem)
[ 0.000000] virtual kernel memory layout:
[ 0.000000] fixmap : 0xffd56000 - 0xfffff000 (2724 kB)
[ 0.000000] pkmap : 0xff400000 - 0xff800000 (4096 kB)
[ 0.000000] vmalloc : 0xf7bfe000 - 0xff3fe000 ( 120 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xf73fe000 ( 883 MB)
[ 0.000000] .init : 0xc13bd000 - 0xc141b000 ( 376 kB)
[ 0.000000] .data : 0xc12716a1 - 0xc13bc460 (1323 kB)
[ 0.000000] .text : 0xc1000000 - 0xc12716a1 (2501 kB)
[ 0.000000] Checking if this processor honours the WP bit even in
supervisor mode...Ok.
[ 0.000000] SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0,
CPUs=4, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] NR_IRQS:1280
[ 0.000000] Console: colour VGA+ 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] hpet clockevent registered
[ 0.000000] HPET: 4 timers in total, 0 timers will be used for
per-cpu timer
[ 0.000000] Fast TSC calibration using PIT
[ 0.000000] Detected 2339.227 MHz processor.
[ 0.004005] Calibrating delay loop (skipped), value calculated using
timer frequency.. 4678.45 BogoMIPS (lpj=9356908)
[ 0.004017] Security Framework initialized
[ 0.004021] SELinux: Disabled at boot.
[ 0.004025] Mount-cache hash table entries: 512
[ 0.004116] Initializing cgroup subsys ns
[ 0.004119] Initializing cgroup subsys cpuacct
[ 0.004123] Initializing cgroup subsys devices
[ 0.004125] Initializing cgroup subsys freezer
[ 0.004126] Initializing cgroup subsys net_cls
[ 0.004145] CPU: L1 I cache: 32K, L1 D cache: 32K
[ 0.004146] CPU: L2 cache: 2048K
[ 0.004149] CPU: Physical Processor ID: 0
[ 0.004150] CPU: Processor Core ID: 0
[ 0.004153] mce: CPU supports 6 MCE banks
[ 0.004159] CPU0: Thermal monitoring enabled (TM2)
[ 0.004162] using mwait in idle threads.
[ 0.004167] Performance Events: Core2 events, Intel PMU driver.
[ 0.004172] ... version: 2
[ 0.004173] ... bit width: 40
[ 0.004175] ... generic registers: 2
[ 0.004176] ... value mask: 000000ffffffffff
[ 0.004178] ... max period: 000000007fffffff
[ 0.004179] ... fixed-purpose events: 3
[ 0.004181] ... event mask: 0000000700000003
[ 0.004184] Checking 'hlt' instruction... OK.
[ 0.021039] ACPI: Core revision 20090903
[ 0.026940] Enabling APIC mode: Flat. Using 1 I/O APICs
[ 0.027244] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.066934] CPU0: Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz
stepping 07
[ 0.068001] Booting processor 1 APIC 0x1 ip 0x6000
[ 0.008000] Initializing CPU#1
[ 0.008000] CPU: L1 I cache: 32K, L1 D cache: 32K
[ 0.008000] CPU: L2 cache: 2048K
[ 0.008000] CPU: Physical Processor ID: 0
[ 0.008000] CPU: Processor Core ID: 1
[ 0.008000] CPU1: Thermal monitoring enabled (TM2)
[ 0.152037] CPU1: Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz
stepping 07
[ 0.152043] checking TSC synchronization [CPU#0 -> CPU#1]: passed.
[ 0.156103] Booting processor 2 APIC 0x2 ip 0x6000
[ 0.008000] Initializing CPU#2
[ 0.008000] CPU: L1 I cache: 32K, L1 D cache: 32K
[ 0.008000] CPU: L2 cache: 2048K
[ 0.008000] CPU: Physical Processor ID: 0
[ 0.008000] CPU: Processor Core ID: 2
[ 0.008000] CPU2: Thermal monitoring enabled (TM2)
[ 0.244091] CPU2: Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz
stepping 07
[ 0.244097] checking TSC synchronization [CPU#0 -> CPU#2]: passed.
[ 0.248082] Booting processor 3 APIC 0x3 ip 0x6000
[ 0.008000] Initializing CPU#3
[ 0.008000] CPU: L1 I cache: 32K, L1 D cache: 32K
[ 0.008000] CPU: L2 cache: 2048K
[ 0.008000] CPU: Physical Processor ID: 0
[ 0.008000] CPU: Processor Core ID: 3
[ 0.008000] CPU3: Thermal monitoring enabled (TM2)
[ 0.336031] CPU3: Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz
stepping 07
[ 0.336037] checking TSC synchronization [CPU#0 -> CPU#3]: passed.
[ 0.340035] Brought up 4 CPUs
[ 0.340037] Total of 4 processors activated (18713.31 BogoMIPS).
[ 0.341229] CPU0 attaching sched-domain:
[ 0.341232] domain 0: span 0-1 level MC
[ 0.341234] groups: 0 1
[ 0.341237] domain 1: span 0-3 level CPU
[ 0.341239] groups: 0-1 (cpu_power = 2048) 2-3 (cpu_power = 2048)
[ 0.341245] CPU1 attaching sched-domain:
[ 0.341246] domain 0: span 0-1 level MC
[ 0.341248] groups: 1 0
[ 0.341251] domain 1: span 0-3 level CPU
[ 0.341253] groups: 0-1 (cpu_power = 2048) 2-3 (cpu_power = 2048)
[ 0.341258] CPU2 attaching sched-domain:
[ 0.341259] domain 0: span 2-3 level MC
[ 0.341261] groups: 2 3
[ 0.341264] domain 1: span 0-3 level CPU
[ 0.341266] groups: 2-3 (cpu_power = 2048) 0-1 (cpu_power = 2048)
[ 0.341271] CPU3 attaching sched-domain:
[ 0.341272] domain 0: span 2-3 level MC
[ 0.341274] groups: 3 2
[ 0.341277] domain 1: span 0-3 level CPU
[ 0.341279] groups: 2-3 (cpu_power = 2048) 0-1 (cpu_power = 2048)
[ 0.341384] devtmpfs: initialized
[ 0.341384] regulator: core version 0.5
[ 0.341384] NET: Registered protocol family 16
[ 0.341384] ACPI: bus type pci registered
[ 0.341384] PCI: MCFG configuration 0: base e0000000 segment 0 buses
0 - 255
[ 0.341384] PCI: Not using MMCONFIG.
[ 0.341384] PCI: Using configuration type 1 for base access
[ 0.341384] bio: create slab <bio-0> at 0
[ 0.341384] ACPI: EC: Detected MSI hardware, enabling workarounds.
[ 0.341384] ACPI: EC: Look up EC in DSDT
[ 0.345949] ACPI: Executed 1 blocks of module-level executable AML code
[ 0.350223] ACPI: Interpreter enabled
[ 0.350232] ACPI: (supports S0 S3 S4 S5)
[ 0.350253] ACPI: Using IOAPIC for interrupt routing
[ 0.350294] PCI: MCFG configuration 0: base e0000000 segment 0 buses
0 - 255
[ 0.352951] PCI: MCFG area at e0000000 reserved in ACPI motherboard
resources
[ 0.352953] PCI: Using MMCONFIG for extended config space
[ 0.360325] ACPI Warning: Incorrect checksum in table [OEMB] - BB,
should be B2 (20090903/tbutils-314)
[ 0.360431] ACPI: No dock devices found.
[ 0.360556] ACPI: PCI Root Bridge [PCI0] (0000:00)
[ 0.360633] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[ 0.360636] pci 0000:00:01.0: PME# disabled
[ 0.360694] pci 0000:00:1a.0: reg 20 io port: [0x8800-0x881f]
[ 0.360751] pci 0000:00:1a.1: reg 20 io port: [0x8480-0x849f]
[ 0.360809] pci 0000:00:1a.2: reg 20 io port: [0x8400-0x841f]
[ 0.360869] pci 0000:00:1a.7: reg 10 32bit mmio: [0xf7fff400-0xf7fff7ff]
[ 0.360915] pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
[ 0.360919] pci 0000:00:1a.7: PME# disabled
[ 0.360953] pci 0000:00:1b.0: reg 10 64bit mmio: [0xf7ff8000-0xf7ffbfff]
[ 0.360987] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.360990] pci 0000:00:1b.0: PME# disabled
[ 0.361041] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 0.361044] pci 0000:00:1c.0: PME# disabled
[ 0.361096] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
[ 0.361099] pci 0000:00:1c.1: PME# disabled
[ 0.361154] pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
[ 0.361157] pci 0000:00:1c.5: PME# disabled
[ 0.361202] pci 0000:00:1d.0: reg 20 io port: [0x9000-0x901f]
[ 0.361260] pci 0000:00:1d.1: reg 20 io port: [0x8c00-0x8c1f]
[ 0.361317] pci 0000:00:1d.2: reg 20 io port: [0x8880-0x889f]
[ 0.361377] pci 0000:00:1d.7: reg 10 32bit mmio: [0xf7fff800-0xf7fffbff]
[ 0.361424] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
[ 0.361428] pci 0000:00:1d.7: PME# disabled
[ 0.361570] pci 0000:00:1f.2: reg 10 io port: [0xac00-0xac07]
[ 0.361575] pci 0000:00:1f.2: reg 14 io port: [0xa880-0xa883]
[ 0.361580] pci 0000:00:1f.2: reg 18 io port: [0xa800-0xa807]
[ 0.361585] pci 0000:00:1f.2: reg 1c io port: [0xa480-0xa483]
[ 0.361590] pci 0000:00:1f.2: reg 20 io port: [0xa400-0xa40f]
[ 0.361595] pci 0000:00:1f.2: reg 24 io port: [0xa080-0xa08f]
[ 0.361633] pci 0000:00:1f.3: reg 10 64bit mmio: [0xf7fffc00-0xf7fffcff]
[ 0.361644] pci 0000:00:1f.3: reg 20 io port: [0x400-0x41f]
[ 0.361680] pci 0000:00:1f.5: reg 10 io port: [0x9c00-0x9c07]
[ 0.361685] pci 0000:00:1f.5: reg 14 io port: [0x9880-0x9883]
[ 0.361690] pci 0000:00:1f.5: reg 18 io port: [0x9800-0x9807]
[ 0.361695] pci 0000:00:1f.5: reg 1c io port: [0x9480-0x9483]
[ 0.361700] pci 0000:00:1f.5: reg 20 io port: [0x9400-0x940f]
[ 0.361705] pci 0000:00:1f.5: reg 24 io port: [0x9080-0x908f]
[ 0.361750] pci 0000:05:00.0: reg 10 32bit mmio: [0xfd000000-0xfdffffff]
[ 0.361757] pci 0000:05:00.0: reg 14 64bit mmio pref:
[0xd0000000-0xdfffffff]
[ 0.361765] pci 0000:05:00.0: reg 1c 64bit mmio: [0xfa000000-0xfbffffff]
[ 0.361769] pci 0000:05:00.0: reg 24 io port: [0xec00-0xec7f]
[ 0.361774] pci 0000:05:00.0: reg 30 32bit mmio pref: [0x000000-0x01ffff]
[ 0.361861] pci 0000:00:01.0: bridge io port: [0xe000-0xefff]
[ 0.361864] pci 0000:00:01.0: bridge 32bit mmio: [0xfa000000-0xfebfffff]
[ 0.361868] pci 0000:00:01.0: bridge 64bit mmio pref:
[0xd0000000-0xdfffffff]
[ 0.361948] pci 0000:02:00.0: reg 24 32bit mmio: [0xf9efe000-0xf9efffff]
[ 0.361983] pci 0000:02:00.0: PME# supported from D3hot
[ 0.361988] pci 0000:02:00.0: PME# disabled
[ 0.362036] pci 0000:02:00.1: reg 10 io port: [0xcc00-0xcc07]
[ 0.362044] pci 0000:02:00.1: reg 14 io port: [0xc880-0xc883]
[ 0.362052] pci 0000:02:00.1: reg 18 io port: [0xc800-0xc807]
[ 0.362061] pci 0000:02:00.1: reg 1c io port: [0xc480-0xc483]
[ 0.362069] pci 0000:02:00.1: reg 20 io port: [0xc400-0xc40f]
[ 0.362131] pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device.
You can enable it with 'pcie_aspm=force'
[ 0.362192] pci 0000:00:1c.0: bridge io port: [0xc000-0xcfff]
[ 0.362196] pci 0000:00:1c.0: bridge 32bit mmio: [0xf9e00000-0xf9efffff]
[ 0.362274] pci 0000:04:00.0: reg 10 io port: [0xd800-0xd8ff]
[ 0.362292] pci 0000:04:00.0: reg 18 64bit mmio pref:
[0xcffff000-0xcfffffff]
[ 0.362305] pci 0000:04:00.0: reg 20 64bit mmio pref:
[0xcffe0000-0xcffeffff]
[ 0.362313] pci 0000:04:00.0: reg 30 32bit mmio pref:
[0xf9ff0000-0xf9ffffff]
[ 0.362348] pci 0000:04:00.0: supports D1 D2
[ 0.362350] pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.362354] pci 0000:04:00.0: PME# disabled
[ 0.368096] pci 0000:00:1c.5: bridge io port: [0xd000-0xdfff]
[ 0.368100] pci 0000:00:1c.5: bridge 32bit mmio: [0xf9f00000-0xf9ffffff]
[ 0.368105] pci 0000:00:1c.5: bridge 64bit mmio pref:
[0xcff00000-0xcfffffff]
[ 0.368138] pci 0000:01:00.0: reg 10 32bit mmio: [0xf8000000-0xf8ffffff]
[ 0.368222] pci 0000:01:02.0: reg 10 32bit mmio: [0xf9dff000-0xf9dfffff]
[ 0.368228] pci 0000:01:02.0: reg 14 io port: [0xbc00-0xbc3f]
[ 0.368234] pci 0000:01:02.0: reg 18 32bit mmio: [0xf9c00000-0xf9cfffff]
[ 0.368251] pci 0000:01:02.0: reg 30 32bit mmio pref:
[0xf9b00000-0xf9bfffff]
[ 0.368267] pci 0000:01:02.0: supports D1 D2
[ 0.368269] pci 0000:01:02.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.368273] pci 0000:01:02.0: PME# disabled
[ 0.368315] pci 0000:00:1e.0: transparent bridge
[ 0.368318] pci 0000:00:1e.0: bridge io port: [0xb000-0xbfff]
[ 0.368322] pci 0000:00:1e.0: bridge 32bit mmio: [0xf8000000-0xf9dfffff]
[ 0.368342] pci_bus 0000:00: on NUMA node 0
[ 0.368345] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 0.368517] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
[ 0.368664] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._PRT]
[ 0.368729] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P5._PRT]
[ 0.368789] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P9._PRT]
[ 0.383573] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 6 7 *10 11 12
14 15)
[ 0.383671] ACPI: PCI Interrupt Link [LNKB] (IRQs *5)
[ 0.383762] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 6 7 10 11 12 14
*15)
[ 0.383855] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 6 7 10 *11 12
14 15)
[ 0.383949] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 6 7 10 11 12 14
15) *0, disabled.
[ 0.384053] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 6 *7 10 11 12
14 15)
[ 0.384157] ACPI: PCI Interrupt Link [LNKG] (IRQs *3 4 6 7 10 11 12
14 15)
[ 0.384251] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 6 7 10 11 12
*14 15)
[ 0.384340] vgaarb: device added:
PCI:0000:05:00.0,decodes=io+mem,owns=io+mem,locks=none
[ 0.384345] vgaarb: loaded
[ 0.384357] PCI: Using ACPI for IRQ routing
[ 0.384357] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0
[ 0.384357] hpet0: 4 comparators, 64-bit 14.318180 MHz counter
[ 0.392018] Switching to clocksource tsc
[ 0.393128] pnp: PnP ACPI init
[ 0.393143] ACPI: bus type pnp registered
[ 0.396357] pnp: PnP ACPI: found 18 devices
[ 0.396359] ACPI: ACPI bus type pnp unregistered
[ 0.396362] PnPBIOS: Disabled by ACPI PNP
[ 0.396371] system 00:01: iomem range 0xfed14000-0xfed19fff has been
reserved
[ 0.396374] system 00:01: iomem range 0xfed90000-0xfed93fff has been
reserved
[ 0.396381] system 00:08: ioport range 0x4c0-0x4ff has been reserved
[ 0.396384] system 00:08: ioport range 0x4d0-0x4d1 has been reserved
[ 0.396386] system 00:08: ioport range 0x800-0x87f has been reserved
[ 0.396389] system 00:08: ioport range 0x480-0x4bf has been reserved
[ 0.396392] system 00:08: iomem range 0xfed1c000-0xfed1ffff has been
reserved
[ 0.396395] system 00:08: iomem range 0xfed20000-0xfed3ffff has been
reserved
[ 0.396397] system 00:08: iomem range 0xfed40000-0xfed8ffff has been
reserved
[ 0.396403] system 00:0b: iomem range 0xffc00000-0xffefffff has been
reserved
[ 0.396407] system 00:0c: iomem range 0xfec00000-0xfec00fff could not
be reserved
[ 0.396410] system 00:0c: iomem range 0xfee00000-0xfee00fff has been
reserved
[ 0.396415] system 00:0f: ioport range 0xa00-0xadf has been reserved
[ 0.396418] system 00:0f: ioport range 0xae0-0xaef has been reserved
[ 0.396422] system 00:10: iomem range 0xe0000000-0xefffffff has been
reserved
[ 0.396427] system 00:11: iomem range 0x0-0x9ffff could not be reserved
[ 0.396430] system 00:11: iomem range 0xc0000-0xcffff could not be
reserved
[ 0.396432] system 00:11: iomem range 0xe0000-0xfffff could not be
reserved
[ 0.396435] system 00:11: iomem range 0x100000-0x7fffffff could not
be reserved
[ 0.396438] system 00:11: iomem range 0xfed90000-0xffffffff could not
be reserved
[ 0.431210] pci 0000:01:02.0: BAR 6: address space collision on of
device [0xf9b00000-0xf9bfffff]
[ 0.431289] pci 0000:00:01.0: PCI bridge, secondary bus 0000:05
[ 0.431292] pci 0000:00:01.0: IO window: 0xe000-0xefff
[ 0.431295] pci 0000:00:01.0: MEM window: 0xfa000000-0xfebfffff
[ 0.431298] pci 0000:00:01.0: PREFETCH window:
0x000000d0000000-0x000000dfffffff
[ 0.431302] pci 0000:00:1c.0: PCI bridge, secondary bus 0000:02
[ 0.431305] pci 0000:00:1c.0: IO window: 0xc000-0xcfff
[ 0.431309] pci 0000:00:1c.0: MEM window: 0xf9e00000-0xf9efffff
[ 0.431313] pci 0000:00:1c.0: PREFETCH window:
0x00000080000000-0x000000801fffff
[ 0.431318] pci 0000:00:1c.1: PCI bridge, secondary bus 0000:03
[ 0.431321] pci 0000:00:1c.1: IO window: 0x1000-0x1fff
[ 0.431325] pci 0000:00:1c.1: MEM window: 0x80200000-0x803fffff
[ 0.431328] pci 0000:00:1c.1: PREFETCH window:
0x00000080400000-0x000000805fffff
[ 0.431334] pci 0000:00:1c.5: PCI bridge, secondary bus 0000:04
[ 0.431336] pci 0000:00:1c.5: IO window: 0xd000-0xdfff
[ 0.431341] pci 0000:00:1c.5: MEM window: 0xf9f00000-0xf9ffffff
[ 0.431344] pci 0000:00:1c.5: PREFETCH window:
0x000000cff00000-0x000000cfffffff
[ 0.431350] pci 0000:00:1e.0: PCI bridge, secondary bus 0000:01
[ 0.431353] pci 0000:00:1e.0: IO window: 0xb000-0xbfff
[ 0.431357] pci 0000:00:1e.0: MEM window: 0xf8000000-0xf9dfffff
[ 0.431361] pci 0000:00:1e.0: PREFETCH window: 0x80600000-0x806fffff
[ 0.431372] pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 0.431375] pci 0000:00:01.0: setting latency timer to 64
[ 0.431383] pci 0000:00:1c.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 0.431387] pci 0000:00:1c.0: setting latency timer to 64
[ 0.431393] pci 0000:00:1c.1: enabling device (0104 -> 0107)
[ 0.431396] pci 0000:00:1c.1: PCI INT B -> GSI 16 (level, low) -> IRQ 16
[ 0.431400] pci 0000:00:1c.1: setting latency timer to 64
[ 0.431406] pci 0000:00:1c.5: PCI INT B -> GSI 16 (level, low) -> IRQ 16
[ 0.431410] pci 0000:00:1c.5: setting latency timer to 64
[ 0.431415] pci 0000:00:1e.0: setting latency timer to 64
[ 0.431418] pci_bus 0000:00: resource 0 io: [0x00-0xffff]
[ 0.431421] pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff]
[ 0.431423] pci_bus 0000:05: resource 0 io: [0xe000-0xefff]
[ 0.431425] pci_bus 0000:05: resource 1 mem: [0xfa000000-0xfebfffff]
[ 0.431428] pci_bus 0000:05: resource 2 pref mem [0xd0000000-0xdfffffff]
[ 0.431430] pci_bus 0000:02: resource 0 io: [0xc000-0xcfff]
[ 0.431432] pci_bus 0000:02: resource 1 mem: [0xf9e00000-0xf9efffff]
[ 0.431434] pci_bus 0000:02: resource 2 pref mem [0x80000000-0x801fffff]
[ 0.431436] pci_bus 0000:03: resource 0 io: [0x1000-0x1fff]
[ 0.431439] pci_bus 0000:03: resource 1 mem: [0x80200000-0x803fffff]
[ 0.431441] pci_bus 0000:03: resource 2 pref mem [0x80400000-0x805fffff]
[ 0.431443] pci_bus 0000:04: resource 0 io: [0xd000-0xdfff]
[ 0.431445] pci_bus 0000:04: resource 1 mem: [0xf9f00000-0xf9ffffff]
[ 0.431447] pci_bus 0000:04: resource 2 pref mem [0xcff00000-0xcfffffff]
[ 0.431450] pci_bus 0000:01: resource 0 io: [0xb000-0xbfff]
[ 0.431452] pci_bus 0000:01: resource 1 mem: [0xf8000000-0xf9dfffff]
[ 0.431454] pci_bus 0000:01: resource 2 pref mem [0x80600000-0x806fffff]
[ 0.431456] pci_bus 0000:01: resource 3 io: [0x00-0xffff]
[ 0.431458] pci_bus 0000:01: resource 4 mem: [0x000000-0xffffffff]
[ 0.431485] NET: Registered protocol family 2
[ 0.431560] IP route cache hash table entries: 32768 (order: 5,
131072 bytes)
[ 0.431775] TCP established hash table entries: 131072 (order: 8,
1048576 bytes)
[ 0.432072] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[ 0.432213] TCP: Hash tables configured (established 131072 bind 65536)
[ 0.432216] TCP reno registered
[ 0.432273] NET: Registered protocol family 1
[ 0.432396] pci 0000:05:00.0: Boot video device
[ 0.432409] pci 0000:01:02.0: Firmware left e100 interrupts enabled;
disabling
[ 0.432454] Unpacking initramfs...
[ 0.623273] Freeing initrd memory: 7836k freed
[ 0.626245] audit: initializing netlink socket (disabled)
[ 0.626256] type=2000 audit(1295843517.623:1): initialized
[ 0.629248] highmem bounce pool size: 64 pages
[ 0.629251] HugeTLB registered 4 MB page size, pre-allocated 0 pages
[ 0.630511] VFS: Disk quotas dquot_6.5.2
[ 0.630556] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.630614] msgmni has been set to 1723
[ 0.630937] alg: No test for stdrng (krng)
[ 0.630989] Block layer SCSI generic (bsg) driver version 0.4 loaded
(major 253)
[ 0.630991] io scheduler noop registered
[ 0.630993] io scheduler anticipatory registered
[ 0.630995] io scheduler deadline registered
[ 0.631025] io scheduler cfq registered (default)
[ 0.631121] pcieport 0000:00:01.0: irq 24 for MSI/MSI-X
[ 0.631126] pcieport 0000:00:01.0: setting latency timer to 64
[ 0.631203] pcieport 0000:00:1c.0: irq 25 for MSI/MSI-X
[ 0.631210] pcieport 0000:00:1c.0: setting latency timer to 64
[ 0.631301] pcieport 0000:00:1c.1: irq 26 for MSI/MSI-X
[ 0.631308] pcieport 0000:00:1c.1: setting latency timer to 64
[ 0.631403] pcieport 0000:00:1c.5: irq 27 for MSI/MSI-X
[ 0.631410] pcieport 0000:00:1c.5: setting latency timer to 64
[ 0.631547] isapnp: Scanning for PnP cards...
[ 0.984350] isapnp: No Plug & Play device found
[ 0.985429] Linux agpgart interface v0.103
[ 0.985541] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 0.985624] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.985878] 00:06: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.986089] PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at
0x60,0x64 irq 1,12
[ 0.988622] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 0.988626] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 0.988675] mice: PS/2 mouse device common for all mice
[ 0.988718] rtc_cmos 00:03: RTC can wake from S4
[ 0.988742] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[ 0.988763] rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
[ 0.988775] cpuidle: using governor ladder
[ 0.988776] cpuidle: using governor menu
[ 0.988780] No iBFT detected.
[ 0.989039] TCP cubic registered
[ 0.989149] NET: Registered protocol family 10
[ 0.989498] lo: Disabled Privacy Extensions
[ 0.989745] Mobile IPv6
[ 0.989747] NET: Registered protocol family 17
[ 0.989757] Using IPI No-Shortcut mode
[ 0.989808] PM: Resume from disk failed.
[ 0.989816] registered taskstats version 1
[ 0.990210] rtc_cmos 00:03: setting system clock to 2011-01-24
04:31:58 UTC (1295843518)
[ 0.990237] Initalizing network drop monitor service
[ 0.990264] Freeing unused kernel memory: 376k freed
[ 0.990413] Write protecting the kernel text: 2504k
[ 0.990442] Write protecting the kernel read-only data: 920k
[ 0.998445] udev[76]: starting version 164
[ 1.008570] input: AT Translated Set 2 keyboard as
/devices/platform/i8042/serio0/input/input0
[ 1.057440] SCSI subsystem initialized
[ 1.057881] usbcore: registered new interface driver usbfs
[ 1.057901] usbcore: registered new interface driver hub
[ 1.057941] usbcore: registered new device driver usb
[ 1.070642] libata version 3.00 loaded.
[ 1.073528] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.073565] ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low)
-> IRQ 18
[ 1.073583] ehci_hcd 0000:00:1a.7: setting latency timer to 64
[ 1.073586] ehci_hcd 0000:00:1a.7: EHCI Host Controller
[ 1.073603] ehci_hcd 0000:00:1a.7: new USB bus registered, assigned
bus number 1
[ 1.073624] ehci_hcd 0000:00:1a.7: debug port 1
[ 1.076539] ahci 0000:02:00.0: version 3.0
[ 1.076564] ahci 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 1.077521] ehci_hcd 0000:00:1a.7: cache line size of 32 is not supported
[ 1.077535] ehci_hcd 0000:00:1a.7: irq 18, io mem 0xf7fff400
[ 1.082850] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 1.082868] r8169 0000:04:00.0: PCI INT A -> GSI 17 (level, low) ->
IRQ 17
[ 1.082898] r8169 0000:04:00.0: setting latency timer to 64
[ 1.082945] r8169 0000:04:00.0: irq 28 for MSI/MSI-X
[ 1.083443] eth0: RTL8168c/8111c at 0xf7e86000, 00:21:85:1a:c6:72,
XID 1c4000c0 IRQ 28
[ 1.084640] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[ 1.084642] e100: Copyright(c) 1999-2006 Intel Corporation
[ 1.084685] e100 0000:01:02.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[ 1.085858] Floppy drive(s): fd0 is 1.44M
[ 1.089543] ahci 0000:02:00.0: AHCI 0001.0000 32 slots 2 ports 3 Gbps
0x3 impl SATA mode
[ 1.089547] ahci 0000:02:00.0: flags: 64bit ncq pm led clo pmp pio
slum part
[ 1.089553] ahci 0000:02:00.0: setting latency timer to 64
[ 1.089673] scsi0 : ahci
[ 1.089755] scsi1 : ahci
[ 1.089837] ata1: SATA max UDMA/133 abar m8192@0xf9efe000 port
0xf9efe100 irq 16
[ 1.089841] ata2: SATA max UDMA/133 abar m8192@0xf9efe000 port
0xf9efe180 irq 16
[ 1.089872] pata_jmicron 0000:02:00.1: enabling device (0000 -> 0001)
[ 1.089878] pata_jmicron 0000:02:00.1: PCI INT B -> GSI 17 (level,
low) -> IRQ 17
[ 1.089907] pata_jmicron 0000:02:00.1: setting latency timer to 64
[ 1.089981] scsi2 : pata_jmicron
[ 1.090064] scsi3 : pata_jmicron
[ 1.090556] ata3: PATA max UDMA/100 cmd 0xcc00 ctl 0xc880 bmdma
0xc400 irq 17
[ 1.090559] ata4: PATA max UDMA/100 cmd 0xc800 ctl 0xc480 bmdma
0xc408 irq 17
[ 1.096006] ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
[ 1.096034] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.096037] usb usb1: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.096039] usb usb1: Product: EHCI Host Controller
[ 1.096041] usb usb1: Manufacturer: Linux 2.6.32-5-686 ehci_hcd
[ 1.096043] usb usb1: SerialNumber: 0000:00:1a.7
[ 1.096110] usb usb1: configuration #1 chosen from 1 choice
[ 1.096134] hub 1-0:1.0: USB hub found
[ 1.096140] hub 1-0:1.0: 6 ports detected
[ 1.096200] ata_piix 0000:00:1f.2: version 2.13
[ 1.096218] ata_piix 0000:00:1f.2: PCI INT B -> GSI 19 (level, low)
-> IRQ 19
[ 1.096222] ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
[ 1.096261] ata_piix 0000:00:1f.2: setting latency timer to 64
[ 1.096300] scsi4 : ata_piix
[ 1.096350] scsi5 : ata_piix
[ 1.097412] ata5: SATA max UDMA/133 cmd 0xac00 ctl 0xa880 bmdma
0xa400 irq 19
[ 1.097416] ata6: SATA max UDMA/133 cmd 0xa800 ctl 0xa480 bmdma
0xa408 irq 19
[ 1.097476] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low)
-> IRQ 23
[ 1.097494] ehci_hcd 0000:00:1d.7: setting latency timer to 64
[ 1.097497] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[ 1.097509] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned
bus number 2
[ 1.097538] ehci_hcd 0000:00:1d.7: debug port 1
[ 1.101418] ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
[ 1.101430] ehci_hcd 0000:00:1d.7: irq 23, io mem 0xf7fff800
[ 1.106009] FDC 0 is a post-1991 82077
[ 1.109096] e100 0000:01:02.0: PME# disabled
[ 1.109655] e100: eth1: e100_probe: addr 0xf9dff000, irq 21, MAC addr
00:d0:b7:85:0a:3f
[ 1.120011] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
[ 1.120028] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.120030] usb usb2: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.120033] usb usb2: Product: EHCI Host Controller
[ 1.120035] usb usb2: Manufacturer: Linux 2.6.32-5-686 ehci_hcd
[ 1.120037] usb usb2: SerialNumber: 0000:00:1d.7
[ 1.120103] usb usb2: configuration #1 chosen from 1 choice
[ 1.120135] hub 2-0:1.0: USB hub found
[ 1.120140] hub 2-0:1.0: 6 ports detected
[ 1.120213] ata_piix 0000:00:1f.5: PCI INT B -> GSI 19 (level, low)
-> IRQ 19
[ 1.120222] ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ]
[ 1.120258] ata_piix 0000:00:1f.5: setting latency timer to 64
[ 1.120305] scsi6 : ata_piix
[ 1.120384] scsi7 : ata_piix
[ 1.121344] ata7: SATA max UDMA/133 cmd 0x9c00 ctl 0x9880 bmdma
0x9400 irq 19
[ 1.121348] ata8: SATA max UDMA/133 cmd 0x9800 ctl 0x9480 bmdma
0x9408 irq 19
[ 1.178313] uhci_hcd: USB Universal Host Controller Interface driver
[ 1.178352] uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low)
-> IRQ 16
[ 1.178358] uhci_hcd 0000:00:1a.0: setting latency timer to 64
[ 1.178361] uhci_hcd 0000:00:1a.0: UHCI Host Controller
[ 1.178374] uhci_hcd 0000:00:1a.0: new USB bus registered, assigned
bus number 3
[ 1.178398] uhci_hcd 0000:00:1a.0: irq 16, io base 0x00008800
[ 1.178429] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.178432] usb usb3: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.178434] usb usb3: Product: UHCI Host Controller
[ 1.178435] usb usb3: Manufacturer: Linux 2.6.32-5-686 uhci_hcd
[ 1.178437] usb usb3: SerialNumber: 0000:00:1a.0
[ 1.178514] usb usb3: configuration #1 chosen from 1 choice
[ 1.178541] hub 3-0:1.0: USB hub found
[ 1.178547] hub 3-0:1.0: 2 ports detected
[ 1.178592] uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low)
-> IRQ 21
[ 1.178597] uhci_hcd 0000:00:1a.1: setting latency timer to 64
[ 1.178600] uhci_hcd 0000:00:1a.1: UHCI Host Controller
[ 1.178606] uhci_hcd 0000:00:1a.1: new USB bus registered, assigned
bus number 4
[ 1.178635] uhci_hcd 0000:00:1a.1: irq 21, io base 0x00008480
[ 1.178662] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.178664] usb usb4: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.178666] usb usb4: Product: UHCI Host Controller
[ 1.178668] usb usb4: Manufacturer: Linux 2.6.32-5-686 uhci_hcd
[ 1.178670] usb usb4: SerialNumber: 0000:00:1a.1
[ 1.178784] usb usb4: configuration #1 chosen from 1 choice
[ 1.178836] hub 4-0:1.0: USB hub found
[ 1.178842] hub 4-0:1.0: 2 ports detected
[ 1.178884] uhci_hcd 0000:00:1a.2: PCI INT D -> GSI 19 (level, low)
-> IRQ 19
[ 1.178889] uhci_hcd 0000:00:1a.2: setting latency timer to 64
[ 1.178891] uhci_hcd 0000:00:1a.2: UHCI Host Controller
[ 1.178898] uhci_hcd 0000:00:1a.2: new USB bus registered, assigned
bus number 5
[ 1.178919] uhci_hcd 0000:00:1a.2: irq 19, io base 0x00008400
[ 1.178945] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.178947] usb usb5: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.178949] usb usb5: Product: UHCI Host Controller
[ 1.178951] usb usb5: Manufacturer: Linux 2.6.32-5-686 uhci_hcd
[ 1.178953] usb usb5: SerialNumber: 0000:00:1a.2
[ 1.179046] usb usb5: configuration #1 chosen from 1 choice
[ 1.179099] hub 5-0:1.0: USB hub found
[ 1.179104] hub 5-0:1.0: 2 ports detected
[ 1.179144] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low)
-> IRQ 23
[ 1.179149] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[ 1.179152] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[ 1.179158] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned
bus number 6
[ 1.179179] uhci_hcd 0000:00:1d.0: irq 23, io base 0x00009000
[ 1.179203] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.179206] usb usb6: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.179208] usb usb6: Product: UHCI Host Controller
[ 1.179210] usb usb6: Manufacturer: Linux 2.6.32-5-686 uhci_hcd
[ 1.179211] usb usb6: SerialNumber: 0000:00:1d.0
[ 1.179295] usb usb6: configuration #1 chosen from 1 choice
[ 1.179347] hub 6-0:1.0: USB hub found
[ 1.179352] hub 6-0:1.0: 2 ports detected
[ 1.179389] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low)
-> IRQ 19
[ 1.179394] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[ 1.179396] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[ 1.179402] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned
bus number 7
[ 1.179422] uhci_hcd 0000:00:1d.1: irq 19, io base 0x00008c00
[ 1.179448] usb usb7: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.179450] usb usb7: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.179453] usb usb7: Product: UHCI Host Controller
[ 1.179454] usb usb7: Manufacturer: Linux 2.6.32-5-686 uhci_hcd
[ 1.179456] usb usb7: SerialNumber: 0000:00:1d.1
[ 1.179542] usb usb7: configuration #1 chosen from 1 choice
[ 1.179595] hub 7-0:1.0: USB hub found
[ 1.179601] hub 7-0:1.0: 2 ports detected
[ 1.179638] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low)
-> IRQ 18
[ 1.179643] uhci_hcd 0000:00:1d.2: setting latency timer to 64
[ 1.179646] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[ 1.179651] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned
bus number 8
[ 1.179672] uhci_hcd 0000:00:1d.2: irq 18, io base 0x00008880
[ 1.179696] usb usb8: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.179699] usb usb8: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.179701] usb usb8: Product: UHCI Host Controller
[ 1.179703] usb usb8: Manufacturer: Linux 2.6.32-5-686 uhci_hcd
[ 1.179704] usb usb8: SerialNumber: 0000:00:1d.2
[ 1.179789] usb usb8: configuration #1 chosen from 1 choice
[ 1.179840] hub 8-0:1.0: USB hub found
[ 1.179845] hub 8-0:1.0: 2 ports detected
[ 1.409524] ata1: SATA link down (SStatus 0 SControl 300)
[ 1.413022] ata2: SATA link down (SStatus 0 SControl 300)
[ 1.429742] ata3.00: ATA-6: ST380011A, 8.01, max UDMA/100
[ 1.429746] ata3.00: 156301488 sectors, multi 16: LBA48
[ 1.430129] ata3.01: ATA-5: QUANTUM FIREBALLP LM15, A35.0700, max UDMA/66
[ 1.430132] ata3.01: 29336832 sectors, multi 16: LBA
[ 1.444750] ata3.00: configured for UDMA/100
[ 1.450625] ata7: SATA link down (SStatus 0 SControl 300)
[ 1.461133] ata8: SATA link down (SStatus 0 SControl 300)
[ 1.468831] ata3.01: configured for UDMA/66
[ 1.468937] scsi 2:0:0:0: Direct-Access ATA ST380011A 8.01
PQ: 0 ANSI: 5
[ 1.469077] scsi 2:0:1:0: Direct-Access ATA QUANTUM FIREBALL
A35. PQ: 0 ANSI: 5
[ 1.700007] usb 4-2: new low speed USB device using uhci_hcd and
address 2
[ 1.750556] ata6.00: SATA link down (SStatus 0 SControl 300)
[ 1.750568] ata6.01: SATA link down (SStatus 0 SControl 300)
[ 1.892051] ata5.00: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 1.892064] ata5.01: SATA link down (SStatus 0 SControl 300)
[ 1.892074] ata5.01: link offline, clearing class 3 to NONE
[ 1.900183] ata5.00: ATAPI: PIONEER DVD-RW DVR-218L, 1.02, max UDMA/100
[ 1.916214] ata5.00: configured for UDMA/100
[ 1.921043] scsi 4:0:0:0: CD-ROM PIONEER DVD-RW DVR-218L
1.02 PQ: 0 ANSI: 5
[ 1.927755] sd 2:0:0:0: [sda] 156301488 512-byte logical blocks:
(80.0 GB/74.5 GiB)
[ 1.927860] sd 2:0:0:0: [sda] Write Protect is off
[ 1.927863] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1.927895] sd 2:0:0:0: [sda] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 1.928019] sda:sr0: scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw
xa/form2 cdda tray
[ 1.937916] Uniform CD-ROM driver Revision: 3.20
[ 1.937997] sr 4:0:0:0: Attached scsi CD-ROM sr0
[ 1.938833] sda1 sda2 <
[ 1.938850] sd 2:0:1:0: [sdb] 29336832 512-byte logical blocks: (15.0
GB/13.9 GiB)
[ 1.949052] sda5 sda6
[ 1.969442] sd 2:0:1:0: [sdb] Write Protect is off
[ 1.969449] sda7
[ 1.969456] sd 2:0:1:0: [sdb] Mode Sense: 00 3a 00 00
[ 1.978044] sda8
[ 1.978049] sd 2:0:1:0: [sdb] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 1.986649] sda9 sda10
[ 2.005638] usb 4-2: New USB device found, idVendor=051d, idProduct=0002
[ 2.005641] usb 4-2: New USB device strings: Mfr=3, Product=1,
SerialNumber=2
[ 2.005644] usb 4-2: Product: Back-UPS RS 1500 FW:8.g8 .D USB FW:g8
[ 2.005646] usb 4-2: Manufacturer: American Power Conversion
[ 2.005648] usb 4-2: SerialNumber: BB0100009999
[ 2.005717] usb 4-2: configuration #1 chosen from 1 choice
[ 2.009207] sda11 sda12 >
[ 2.016665] sdb: sdb1
[ 2.024551] sd 2:0:0:0: [sda] Attached SCSI disk
[ 2.024588] sd 2:0:1:0: [sdb] Attached SCSI disk
[ 2.027581] usbcore: registered new interface driver hiddev
[ 2.029689] sd 2:0:0:0: Attached scsi generic sg0 type 0
[ 2.029785] sd 2:0:1:0: Attached scsi generic sg1 type 0
[ 2.030093] sr 4:0:0:0: Attached scsi generic sg2 type 5
[ 2.249011] usb 6-1: new full speed USB device using uhci_hcd and
address 2
[ 2.392171] usb 6-1: not running at top speed; connect to a high
speed hub
[ 2.420169] usb 6-1: New USB device found, idVendor=058f, idProduct=6366
[ 2.420172] usb 6-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 2.420174] usb 6-1: Product: Mass Storage Device
[ 2.420176] usb 6-1: Manufacturer: Generic
[ 2.420177] usb 6-1: SerialNumber: 058F0O1111B1
[ 2.420248] usb 6-1: configuration #1 chosen from 1 choice
[ 2.428453] Initializing USB Mass Storage driver...
[ 2.428588] scsi8 : SCSI emulation for USB Mass Storage devices
[ 2.428673] usb-storage: device found at 2
[ 2.428681] usb-storage: waiting for device to settle before scanning
[ 2.428692] usbcore: registered new interface driver usb-storage
[ 2.428695] USB Mass Storage support registered.
[ 3.095686] generic-usb 0003:051D:0002.0001: hiddev0,hidraw0: USB HID
v1.10 Device [American Power Conversion Back-UPS RS 1500 FW:8.g8 .D USB
FW:g8 ] on usb-0000:00:1a.1-2/input0
[ 3.095718] usbcore: registered new interface driver usbhid
[ 3.095721] usbhid: v2.6:USB HID core driver
[ 3.156671] PM: Starting manual resume from disk
[ 3.156674] PM: Resume from partition 8:10
[ 3.156675] PM: Checking hibernation image.
[ 3.174316] PM: Error -22 checking image file
[ 3.174318] PM: Resume from disk failed.
[ 3.185311] EXT3-fs: INFO: recovery required on readonly filesystem.
[ 3.185313] EXT3-fs: write access will be enabled during recovery.
[ 6.128358] kjournald starting. Commit interval 5 seconds
[ 6.128368] EXT3-fs: sda1: orphan cleanup on readonly fs
[ 6.128373] ext3_orphan_cleanup: deleting unreferenced inode 14362
[ 6.150252] ext3_orphan_cleanup: deleting unreferenced inode 14361
[ 6.176451] ext3_orphan_cleanup: deleting unreferenced inode 14360
[ 6.176618] ext3_orphan_cleanup: deleting unreferenced inode 14359
[ 6.182768] ext3_orphan_cleanup: deleting unreferenced inode 14353
[ 6.182781] ext3_orphan_cleanup: deleting unreferenced inode 14352
[ 6.193014] ext3_orphan_cleanup: deleting unreferenced inode 14351
[ 6.200836] ext3_orphan_cleanup: deleting unreferenced inode 14350
[ 6.201043] ext3_orphan_cleanup: deleting unreferenced inode 14348
[ 6.203151] ext3_orphan_cleanup: deleting unreferenced inode 14346
[ 6.208829] ext3_orphan_cleanup: deleting unreferenced inode 14345
[ 6.217205] ext3_orphan_cleanup: deleting unreferenced inode 14344
[ 6.217383] ext3_orphan_cleanup: deleting unreferenced inode 14343
[ 6.217569] ext3_orphan_cleanup: deleting unreferenced inode 14110
[ 6.217579] EXT3-fs: sda1: 14 orphan inodes deleted
[ 6.217581] EXT3-fs: recovery complete.
[ 6.303033] EXT3-fs: mounted filesystem with ordered data mode.
[ 7.434000] usb-storage: device scan complete
[ 7.436996] scsi 8:0:0:0: Direct-Access Multi Flash Reader
1.00 PQ: 0 ANSI: 0
[ 7.437315] sd 8:0:0:0: Attached scsi generic sg3 type 0
[ 7.446983] sd 8:0:0:0: [sdc] Attached SCSI removable disk
[ 7.794137] udev[430]: starting version 164
[ 8.147267] input: Power Button as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
[ 8.147273] ACPI: Power Button [PWRB]
[ 8.147323] input: Power Button as
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[ 8.147326] ACPI: Power Button [PWRF]
[ 8.754848] ACPI: SSDT 7ff9e0c0 001F3 (v01 DpgPmm P001Ist 00000011
INTL 20051117)
[ 8.755094] processor LNXCPU:00: registered as cooling_device0
[ 8.755446] ACPI: SSDT 7ff9e2c0 001F3 (v01 DpgPmm P002Ist 00000012
INTL 20051117)
[ 8.755650] processor LNXCPU:01: registered as cooling_device1
[ 8.755962] ACPI: SSDT 7ff9e4c0 001F3 (v01 DpgPmm P003Ist 00000012
INTL 20051117)
[ 8.756179] processor LNXCPU:02: registered as cooling_device2
[ 8.756495] ACPI: SSDT 7ff9e6c0 001F3 (v01 DpgPmm P004Ist 00000012
INTL 20051117)
[ 8.756697] processor LNXCPU:03: registered as cooling_device3
[ 8.901692] input: PC Speaker as /devices/platform/pcspkr/input/input3
[ 9.594392] nvidia: module license 'NVIDIA' taints kernel.
[ 9.594395] Disabling lock debugging due to kernel taint
[ 10.354343] i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low)
-> IRQ 18
[ 10.601777] nvidia 0000:05:00.0: PCI INT A -> GSI 16 (level, low) ->
IRQ 16
[ 10.601785] nvidia 0000:05:00.0: setting latency timer to 64
[ 10.601789] vgaarb: device changed decodes:
PCI:0000:05:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[ 10.601912] NVRM: loading NVIDIA UNIX x86 Kernel Module 260.19.36
Tue Jan 18 17:10:40 PST 2011
[ 11.161000] input: ImPS/2 Generic Wheel Mouse as
/devices/platform/i8042/serio1/input/input4
[ 11.428829] Linux video capture interface: v2.00
[ 11.631623] cx88/0: cx2388x v4l2 driver version 0.0.7 loaded
[ 11.631656] cx8800 0000:01:00.0: PCI INT A -> GSI 16 (level, low) ->
IRQ 16
[ 11.632004] cx88[0]: subsystem: 1043:4820, board: ASUS PVR-416
[card=12,insmod option], frontend(s): 0
[ 11.632007] cx88[0]: TV tuner type 43, Radio tuner type -1
[ 11.694653] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low)
-> IRQ 22
[ 11.694679] HDA Intel 0000:00:1b.0: setting latency timer to 64
[ 11.801413] hda_codec: ALC888: BIOS auto-probing.
[ 11.802790] input: HDA Digital PCBeep as
/devices/pci0000:00/0000:00:1b.0/input/input5
[ 11.830921] All bytes are equal. It is not a TEA5767
[ 11.830972] tuner 1-0060: chip found @ 0xc0 (cx88[0])
[ 11.903423] tuner-simple 1-0060: creating new instance
[ 11.903427] tuner-simple 1-0060: type set to 43 (Philips NTSC MK3
(FM1236MK3 or FM1236/F))
[ 11.904224] cx88[0]/0: found at 0000:01:00.0, rev: 3, irq: 16,
latency: 64, mmio: 0xf8000000
[ 11.904232] IRQ 16/cx88[0]: IRQF_DISABLED is not guaranteed on shared
IRQs
[ 11.904287] cx88[0]/0: registered device video0 [v4l2]
[ 11.904309] cx88[0]/0: registered device vbi0
[ 11.904329] cx88[0]/0: registered device radio0
[ 12.324638] Adding 2361512k swap on /dev/sda10. Priority:-1
extents:1 across:2361512k
[ 13.047660] EXT3 FS on sda1, internal journal
[ 13.137373] loop: module loaded
[ 13.177855] fuse init (API version 7.13)
[ 13.248752] f71882fg: Found f71882fg chip at 0xa00, revision 32
[ 13.249035] f71882fg f71882fg.2560: Fan: 1 is in duty-cycle mode
[ 13.249038] f71882fg f71882fg.2560: Fan: 2 is in duty-cycle mode
[ 13.249040] f71882fg f71882fg.2560: Fan: 3 is in duty-cycle mode
[ 13.249041] f71882fg f71882fg.2560: Fan: 4 is in duty-cycle mode
[ 51.574470] kjournald starting. Commit interval 5 seconds
[ 51.574693] EXT3 FS on sda5, internal journal
[ 51.574698] EXT3-fs: mounted filesystem with ordered data mode.
[ 51.622972] kjournald starting. Commit interval 5 seconds
[ 51.623200] EXT3 FS on sda6, internal journal
[ 51.623204] EXT3-fs: mounted filesystem with ordered data mode.
[ 51.684135] kjournald starting. Commit interval 5 seconds
[ 51.684362] EXT3 FS on sda7, internal journal
[ 51.684365] EXT3-fs: mounted filesystem with ordered data mode.
[ 51.749740] kjournald starting. Commit interval 5 seconds
[ 51.769508] EXT3 FS on sda8, internal journal
[ 51.769512] EXT3-fs: mounted filesystem with ordered data mode.
[ 52.057012] kjournald starting. Commit interval 5 seconds
[ 52.057300] EXT3 FS on sda9, internal journal
[ 52.057304] EXT3-fs: mounted filesystem with ordered data mode.
[ 52.465188] kjournald starting. Commit interval 5 seconds
[ 52.483609] EXT3 FS on sda11, internal journal
[ 52.483614] EXT3-fs: mounted filesystem with ordered data mode.
[ 52.813574] kjournald starting. Commit interval 5 seconds
[ 52.813843] EXT3 FS on sda12, internal journal
[ 52.813847] EXT3-fs: mounted filesystem with ordered data mode.
[ 53.006418] kjournald starting. Commit interval 5 seconds
[ 53.006734] EXT3 FS on sdb1, internal journal
[ 53.006738] EXT3-fs: mounted filesystem with ordered data mode.
[ 54.235242] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 54.329483] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[ 54.329788] CONFIG_NF_CT_ACCT is deprecated and will be removed soon.
Please use
[ 54.329790] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack
module option or
[ 54.329791] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
[ 55.757636] r8169: eth0: link up
[ 55.757641] r8169: eth0: link up
[ 64.535729] vboxdrv: Found 4 processor cores.
[ 64.535837] vboxdrv: fAsync=0 offMin=0x19d offMax=0x44be
[ 64.535872] vboxdrv: TSC mode is 'synchronous', kernel timer mode is
'normal'.
[ 64.535874] vboxdrv: Successfully loaded version 4.0.2 (interface
0x00160000).
[ 66.692503] eth0: no IPv6 routers present
[ 941.977036] ata3.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
frozen
[ 941.977042] ata3.01: failed command: READ DMA
[ 941.977048] ata3.01: cmd c8/00:08:57:2c:00/00:00:00:00:00/f0 tag 0
dma 4096 in
[ 941.977049] res 40/00:00:01:4f:c2/00:00:00:00:00/10 Emask
0x4 (timeout)
[ 941.977052] ata3.01: status: { DRDY }
[ 947.016010] ata3: link is slow to respond, please be patient (ready=0)
[ 949.480017] ata3: soft resetting link
[ 949.636185] ata3.01: NODEV after polling detection
[ 949.636188] ata3.01: revalidation failed (errno=-2)
[ 959.508018] ata3: soft resetting link
[ 959.696731] ata3.00: configured for UDMA/100
[ 959.713866] ata3.01: configured for UDMA/66
[ 959.713874] ata3: EH complete
[ 1497.988533] ata3.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
frozen
[ 1497.988538] ata3.01: failed command: SMART
[ 1497.988544] ata3.01: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/10 tag 0
pio 512 in
[ 1497.988546] res 40/00:00:00:00:00/00:00:00:00:00/10 Emask
0x4 (timeout)
[ 1497.988549] ata3.01: status: { DRDY }
[ 1503.028008] ata3: link is slow to respond, please be patient (ready=0)
[ 1508.016007] ata3: device not ready (errno=-16), forcing hardreset
[ 1508.016017] ata3: soft resetting link
[ 1510.320680] ata3.01: NODEV after polling detection
[ 1510.320683] ata3.01: revalidation failed (errno=-2)
[ 1520.364507] ata3: link is slow to respond, please be patient (ready=0)
[ 1521.600014] ata3: soft resetting link
[ 1521.885740] ata3.00: configured for UDMA/100
[ 1521.901347] ata3.01: configured for UDMA/66
[ 1521.901358] ata3: EH complete
[ 1892.723122] ABORTED IN=eth0 OUT=
MAC=00:21:85:1a:c6:72:00:25:9c:4a:c8:b4:08:00 SRC=209.17.70.143
DST=192.168.0.82 LEN=40 TOS=0x00 PREC=0x00 TTL=51 ID=0 DF PROTO=TCP
SPT=80 DPT=4039 SEQ=2099322950 ACK=0 WINDOW=0 RES=0x00 RST URGP=0
[ 3404.988023] ata3: lost interrupt (Status 0x0)
[ 3404.988053] ata3.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
frozen
[ 3404.988058] ata3.01: failed command: READ DMA
[ 3404.988064] ata3.01: cmd c8/00:08:4f:00:7c/00:00:00:00:00/f1 tag 0
dma 4096 in
[ 3404.988065] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask
0x4 (timeout)
[ 3404.988068] ata3.01: status: { DRDY }
[ 3404.988087] ata3: soft resetting link
[ 3405.144187] ata3.01: NODEV after polling detection
[ 3405.144190] ata3.01: revalidation failed (errno=-2)
[ 3410.260515] ata3: soft resetting link
[ 3410.528676] ata3.01: NODEV after polling detection
[ 3410.528679] ata3.01: revalidation failed (errno=-2)
[ 3415.528020] ata3: soft resetting link
[ 3415.684177] ata3.01: NODEV after polling detection
[ 3415.684180] ata3.01: revalidation failed (errno=-2)
[ 3415.684183] ata3.01: disabled
[ 3415.684187] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x40)
[ 3415.684189] ata3.00: revalidation failed (errno=-5)
[ 3420.684522] ata3: soft resetting link
[ 3420.844681] ata3.00: NODEV after polling detection
[ 3420.844684] ata3.00: revalidation failed (errno=-2)
[ 3425.844021] ata3: soft resetting link
[ 3426.000178] ata3.00: NODEV after polling detection
[ 3426.000181] ata3.00: revalidation failed (errno=-2)
[ 3426.000184] ata3.00: disabled
[ 3426.000189] ata3.01: device reported invalid CHS sector 0
[ 3426.000211] ata3: soft resetting link
[ 3426.156076] ata3: EH complete
[ 3426.156096] sd 2:0:1:0: [sdb] Unhandled error code
[ 3426.156099] sd 2:0:1:0: [sdb] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3426.156103] sd 2:0:1:0: [sdb] CDB: Read(10): 28 00 01 7c 00 4f 00 00
08 00
[ 3426.156112] end_request: I/O error, dev sdb, sector 24903759
[ 3426.156122] EXT3-fs error (device sdb1): ext3_get_inode_loc: unable
to read inode block - inode=778242, block=3112962
[ 3426.156135] sd 2:0:0:0: [sda] Unhandled error code
[ 3426.156141] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3426.156145] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 00 00 07 79 00 00
02 00
[ 3426.156154] end_request: I/O error, dev sda, sector 1913
[ 3426.156157] sd 2:0:0:0: [sda] Unhandled error code
[ 3426.156160] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3426.156163] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 00 00 07 7b 00 00
02 00
[ 3426.156171] end_request: I/O error, dev sda, sector 1915
[ 3426.156185] sd 2:0:1:0: [sdb] Unhandled error code
[ 3426.156187] sd 2:0:1:0: [sdb]
[ 3426.156191] Aborting journal on device sda1.
[ 3426.156198] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 3426.156200] sd 2:0:1:0: [sdb] CDB: Write(10): 2a 00 00 00 00 3f 00 00
08 00
[ 3426.156209] end_request: I/O error, dev sdb, sector 63
[ 3426.156212] Buffer I/O error on device sdb1, logical block 0
[ 3426.156214] lost page write due to I/O error on sdb1
[ 3426.156229] sd 2:0:0:0: [sda] Unhandled error code
[ 3426.156231] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3426.156234] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 02 5c fe cb 00 00
08 00
[ 3426.156241] end_request: I/O error, dev sda, sector 39648971
[ 3426.156244] Buffer I/O error on device sda7, logical block 61
[ 3426.156246] lost page write due to I/O error on sda7
[ 3426.156256] sd 2:0:1:0: [sdb] Unhandled error code
[ 3426.156258] sd 2:0:1:0: [sdb] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3426.156262] sd 2:0:1:0: [sdb] CDB: Write(10): 2a 00 00 00 2c 87 00 00
08 00
[ 3426.156269] end_request: I/O error, dev sdb, sector 11399
[ 3426.156271] Buffer I/O error on device sdb1, logical block 1417
[ 3426.156274] lost page write due to I/O error on sdb1
[ 3426.156284] sd 2:0:0:0: [sda] Unhandled error code
[ 3426.156286] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3426.156289] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 02 5c fe db 00 00
08 00
[ 3426.156296] end_request: I/O error, dev sda, sector 39648987
[ 3426.156299] Buffer I/O error on device sda7, logical block 63
[ 3426.156301] lost page write due to I/O error on sda7
[ 3426.156306] sd 2:0:1:0: [sdb] Unhandled error code
[ 3426.156308] sd 2:0:0:0: [sda] Unhandled error code
[ 3426.156310] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3426.156314] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 02 5c fe eb 00 00
08 00
[ 3426.156320] end_request: I/O error, dev sda, sector 39649003
[ 3426.156323] Buffer I/O error on device sda7, logical block 65
[ 3426.156325] sd 2:0:1:0: [sdb] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3426.156329] sd 2:0:1:0: [sdb] CDB: Write(10): 2a 00 00 00 2c 8f 00 00
10 00
[ 3426.156336] end_request: I/O error, dev sdb, sector 11407
[ 3426.156339] lost page write due to I/O error on sda7
[ 3426.156345] sd 2:0:0:0: [sda] Unhandled error code
[ 3426.156347] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3426.156350] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 02 5c ff 3b 00 00
10 00
[ 3426.156358] end_request: I/O error, dev sda, sector 39649083
[ 3426.156360] Buffer I/O error on device sda7, logical block 75
[ 3426.156362] lost page write due to I/O error on sda7
[ 3426.156365] Buffer I/O error on device sda7, logical block 76
[ 3426.156367] lost page write due to I/O error on sda7
[ 3426.156378] sd 2:0:0:0: [sda] Unhandled error code
[ 3426.156382] Aborting journal on device sdb1.
[ 3426.156388] ------------[ cut here ]------------
[ 3426.156397] WARNING: at
/build/buildd-linux-2.6_2.6.32-30-i386-UYhWt7/linux-2.6-2.6.32/debian/build/source_i386_none/fs/buffer.c:1160
mark_buffer_dirty+0x20/0x7a()
[ 3426.156408] Hardware name: MS-7514
[ 3426.156412] Modules linked in: vboxnetadp
[ 3426.156422] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3426.156432] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 02 77 ae 13 00 00
08 00
[ 3426.156448] end_request: I/O error, dev sda, sector 41397779
[ 3426.156453] vboxnetflt
[ 3426.156460] Buffer I/O error on device sda7, logical block 218662
[ 3426.156465] lost page write due to I/O error on sda7
[ 3426.156470] vboxdrv acpi_cpufreq cpufreq_powersave cpufreq_userspace
cpufreq_stats cpufreq_conservative xt_tcpudp xt_limit nf_conntrack_ipv4
nf_defrag_ipv4 xt_state ipt_LOG ipt_REJECT nf_conntrack_irc
[ 3426.156485] sd 2:0:0:0: [sda] Unhandled error code
[ 3426.156489] nf_conntrack_ftp nf_conntrack iptable_filter ip_tables
[ 3426.156506] JBD: Detected IO errors while flushing file data on sda7
[ 3426.156512] x_tables f71882fg coretemp adt7473 fuse loop
tuner_simple tuner_types tea5767 snd_hda_codec_realtek tuner
snd_hda_intel snd_hda_codec snd_hwdep cx8800 cx88xx snd_pcm_oss
snd_mixer_oss ir_common snd_pcm i2c_algo_bit snd_seq_midi snd_rawmidi
tveeprom snd_seq_midi_event v4l2_common snd_seq videodev v4l1_compat
snd_timer snd_seq_device videobuf_dma_sg snd videobuf_core soundcore
snd_page_alloc btcx_risc psmouse i2c_i801 nvidia(P) pcspkr i2c_core
serio_raw evdev processor button ext3 jbd mbcache usb_storage sg usbhid
hid sr_mod sd_mod crc_t10dif cdrom uhci_hcd ata_generic pata_jmicron
floppy e100 r8169 mii ata_piix thermal ahci ehci_hcd thermal_sys libata
scsi_mod usbcore nls_base [last unloaded: scsi_wait_scan]
[ 3426.156691] Pid: 1339, comm: kjournald Tainted: P 2.6.32-5-686 #1
[ 3426.156698] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3426.156706] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 00 00 04 5d 00 00
02 00
[ 3426.156729] end_request: I/O error, dev sda, sector 1117
[ 3426.156735] Buffer I/O error on device sda1, logical block 527
[ 3426.156740] lost page write due to I/O error on sda1
[ 3426.156745] Call Trace:
[ 3426.156752] [<c10303fd>] ? warn_slowpath_common+0x5e/0x8a
[ 3426.156757] sd 2:0:0:0: [sda] Unhandled error code
[ 3426.156762] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3426.156770] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 02 5d 28 73 00 00
40 00
[ 3426.156793] end_request: I/O error, dev sda, sector 39659635
[ 3426.156800] [<c1030433>] ? warn_slowpath_null+0xa/0xc
[ 3426.156805] [<c10cdac0>] ? mark_buffer_dirty+0x20/0x7a
[ 3426.156810] Aborting journal on device sda7.
[ 3426.156823] [<f802e365>] ? journal_update_superblock+0x5b/0x99 [jbd]
[ 3426.156841] [<f802e4b8>] ? __journal_abort_soft+0x89/0xa1 [jbd]
[ 3426.156848] [<f802c390>] ? journal_commit_transaction+0x962/0xd56 [jbd]
[ 3426.156857] sd 2:0:0:0: [sda] Unhandled error code
[ 3426.156863] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3426.156877] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 02 5d 0e 03 00 00
08 00
[ 3426.156907] end_request: I/O error, dev sda, sector 39652867
[ 3426.156915] Buffer I/O error on device sda7, logical block 548
[ 3426.156923] lost page write due to I/O error on sda7
[ 3426.156935] [<c1020705>] ? __wake_up_common+0x34/0x59
[ 3426.156940] [<c103adc8>] ? lock_timer_base+0x19/0x35
[ 3426.156944] [<c103afd6>] ? try_to_del_timer_sync+0x4f/0x56
[ 3426.156951] [<f802eb7f>] ? kjournald+0xb9/0x1e0 [jbd]
[ 3426.156956] [<c1043cc6>] ? autoremove_wake_function+0x0/0x2d
[ 3426.156963] sd 2:0:0:0: [sda] Unhandled error code
[ 3426.156971] [<f802eac6>] ? kjournald+0x0/0x1e0 [jbd]
[ 3426.156980] [<c1043a94>] ? kthread+0x61/0x66
[ 3426.156987] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3426.157000] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 02 6d ac 73 00 00
10 00
[ 3426.157027] end_request: I/O error, dev sda, sector 40742003
[ 3426.157036] [<c1043a33>] ? kthread+0x0/0x66
[ 3426.157042] [<c1003d47>] ? kernel_thread_helper+0x7/0x10
[ 3426.157048] sd 2:0:0:0: [sda] Unhandled error code
[ 3426.157054] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3426.157067] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 02 6d ac d3 00 00
08 00
[ 3426.157096] end_request: I/O error, dev sda, sector 40742099
[ 3426.157104] ---[ end trace a0ff2403379086e6 ]---
[ 3426.157108] sd 2:0:0:0: [sda] Unhandled error code
[ 3426.157114] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3426.157125] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 02 6d ad 53 00 00
10 00
[ 3426.157155] end_request: I/O error, dev sda, sector 40742227
[ 3426.157164] sd 2:0:0:0: [sda] Unhandled error code
[ 3426.157172] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3426.157186] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 02 6f c9 4b 00 00
08 00
[ 3426.157230] end_request: I/O error, dev sda, sector 40880459
[ 3426.157250] JBD: Detected IO errors while flushing file data on sda7
[ 3426.157263] __journal_remove_journal_head: freeing b_committed_data
[ 3426.157447] sd 2:0:1:0: [sdb] Unhandled error code
[ 3426.157450] sd 2:0:1:0: [sdb] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3426.157453] sd 2:0:1:0: [sdb] CDB: Write(10): 2a 00 00 00 2c 87 00 00
08 00
[ 3426.157461] end_request: I/O error, dev sdb, sector 11399
[ 3426.157470] sd 2:0:1:0: [sdb] Unhandled error code
[ 3426.157472] sd 2:0:1:0: [sdb] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3426.157476] sd 2:0:1:0: [sdb] CDB: Read(10): 28 00 01 80 00 4f 00 00
08 00
[ 3426.157483] end_request: I/O error, dev sdb, sector 25165903
[ 3426.157490] EXT3-fs error (device sdb1): ext3_get_inode_loc: unable
to read inode block - inode=786442, block=3145730
[ 3426.157505] ext3_abort called.
[ 3426.157507] sd 2:0:1:0: [sdb] Unhandled error code
[ 3426.157509] sd 2:0:1:0: [sdb] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3426.157513] sd 2:0:1:0: [sdb] CDB: Write(10): 2a 00 00 00 00 3f 00 00
08 00
[ 3426.157520] end_request: I/O error, dev sdb, sector 63
[ 3426.157523] EXT3-fs error (device sda7): ext3_journal_start_sb:
Detected aborted journal
[ 3426.157526] Remounting filesystem read-only
[ 3426.157566] sd 2:0:1:0: [sdb] Unhandled error code
[ 3426.157568] sd 2:0:1:0: [sdb] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3426.157571] sd 2:0:1:0: [sdb] CDB: Read(10): 28 00 01 90 00 4f 00 00
08 00
[ 3426.157579] end_request: I/O error, dev sdb, sector 26214479
[ 3426.157585] EXT3-fs error (device sdb1): ext3_get_inode_loc: unable
to read inode block - inode=819209, block=3276802
[ 3426.157600] sd 2:0:1:0: [sdb] Unhandled error code
[ 3426.157602] sd 2:0:1:0: [sdb] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3426.157605] sd 2:0:1:0: [sdb] CDB: Write(10): 2a 00 00 00 00 3f 00 00
08 00
[ 3426.157612] end_request: I/O error, dev sdb, sector 63
[ 3426.157652] sd 2:0:1:0: [sdb] Unhandled error code
[ 3426.157654] sd 2:0:1:0: [sdb] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3426.157658] sd 2:0:1:0: [sdb] CDB: Read(10): 28 00 01 7c 00 5f 00 00
08 00
[ 3426.157665] end_request: I/O error, dev sdb, sector 24903775
[ 3426.157671] EXT3-fs error (device sdb1): ext3_get_inode_loc: unable
to read inode block - inode=778274, block=3112964
[ 3426.157686] sd 2:0:1:0: [sdb] Unhandled error code
[ 3426.157688] sd 2:0:1:0: [sdb] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3426.157691] sd 2:0:1:0: [sdb] CDB: Write(10): 2a 00 00 00 00 3f 00 00
08 00
[ 3426.157698] end_request: I/O error, dev sdb, sector 63
[ 3543.984027] sd 2:0:0:0: [sda] Unhandled error code
[ 3543.984030] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3543.984034] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 02 63 7f ab 00 00
08 00
[ 3543.984042] end_request: I/O error, dev sda, sector 40075179
[ 3543.984046] __ratelimit: 10 callbacks suppressed
[ 3543.984049] Buffer I/O error on device sda7, logical block 53337
[ 3543.984051] lost page write due to I/O error on sda7
[ 3543.984060] sd 2:0:0:0: [sda] Unhandled error code
[ 3543.984062] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3543.984065] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 02 63 7f e3 00 00
08 00
[ 3543.984072] end_request: I/O error, dev sda, sector 40075235
[ 3543.984075] Buffer I/O error on device sda7, logical block 53344
[ 3543.984077] lost page write due to I/O error on sda7
[ 3583.988020] sd 2:0:0:0: [sda] Unhandled error code
[ 3583.988023] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3583.988027] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 02 63 7f e3 00 00
08 00
[ 3583.988036] end_request: I/O error, dev sda, sector 40075235
[ 3583.988040] Buffer I/O error on device sda7, logical block 53344
[ 3583.988043] lost page write due to I/O error on sda7
[ 3583.988051] sd 2:0:0:0: [sda] Unhandled error code
[ 3583.988053] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3583.988056] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 02 63 7f ab 00 00
08 00
[ 3583.988064] end_request: I/O error, dev sda, sector 40075179
[ 3583.988066] Buffer I/O error on device sda7, logical block 53337
[ 3583.988068] lost page write due to I/O error on sda7
[ 3669.000053] sd 2:0:0:0: [sda] Unhandled error code
[ 3669.000057] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3669.000061] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 00 13 b0 73 00 00
10 00
[ 3669.000069] end_request: I/O error, dev sda, sector 1290355
[ 3669.000073] Buffer I/O error on device sda5, logical block 88994
[ 3669.000076] lost page write due to I/O error on sda5
[ 3669.000078] Buffer I/O error on device sda5, logical block 88995
[ 3669.000080] lost page write due to I/O error on sda5
[ 3669.000088] JBD: Detected IO errors while flushing file data on sda5
[ 3669.000125] sd 2:0:0:0: [sda] Unhandled error code
[ 3669.000127] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3669.000131] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 00 0a 05 9b 00 00
28 00
[ 3669.000139] end_request: I/O error, dev sda, sector 656795
[ 3669.000150] Aborting journal on device sda5.
[ 3669.000165] sd 2:0:0:0: [sda] Unhandled error code
[ 3669.000167] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3669.000170] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 00 08 e3 e3 00 00
08 00
[ 3669.000178] end_request: I/O error, dev sda, sector 582627
[ 3669.000181] Buffer I/O error on device sda5, logical block 528
[ 3669.000183] lost page write due to I/O error on sda5
[ 3675.471813] sd 2:0:0:0: [sda] Unhandled error code
[ 3675.471817] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3675.471821] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 49 23 ab 00 00
20 00
[ 3675.471829] end_request: I/O error, dev sda, sector 38347691
[ 3675.471853] sd 2:0:0:0: [sda] Unhandled error code
[ 3675.471856] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3675.471860] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 49 23 ab 00 00
08 00
[ 3675.471868] end_request: I/O error, dev sda, sector 38347691
[ 3675.471954] sd 2:0:0:0: [sda] Unhandled error code
[ 3675.471957] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3675.471960] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 49 23 ab 00 00
08 00
[ 3675.471968] end_request: I/O error, dev sda, sector 38347691
[ 3675.472096] ext3_abort called.
[ 3675.472099] EXT3-fs error (device sda1): ext3_journal_start_sb:
Detected aborted journal
[ 3675.472102] Remounting filesystem read-only
[ 3675.472284] sd 2:0:0:0: [sda] Unhandled error code
[ 3675.472286] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3675.472290] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 49 23 ab 00 00
08 00
[ 3675.472298] end_request: I/O error, dev sda, sector 38347691
[ 3675.472367] sd 2:0:0:0: [sda] Unhandled error code
[ 3675.472369] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3675.472373] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 49 23 ab 00 00
08 00
[ 3675.472380] end_request: I/O error, dev sda, sector 38347691
[ 3675.472470] sd 2:0:0:0: [sda] Unhandled error code
[ 3675.472473] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3675.472476] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 04 1d 13 00 00
02 00
[ 3675.472484] end_request: I/O error, dev sda, sector 269587
[ 3675.472487] Buffer I/O error on device sda1, logical block 134762
[ 3675.472494] sd 2:0:0:0: [sda] Unhandled error code
[ 3675.472496] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3675.472499] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 04 1d 33 00 00
04 00
[ 3675.472507] end_request: I/O error, dev sda, sector 269619
[ 3675.472509] Buffer I/O error on device sda1, logical block 134778
[ 3675.472512] Buffer I/O error on device sda1, logical block 134779
[ 3675.472533] sd 2:0:0:0: [sda] Unhandled error code
[ 3675.472535] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3675.472538] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 04 1d 33 00 00
04 00
[ 3675.472546] end_request: I/O error, dev sda, sector 269619
[ 3675.472549] Buffer I/O error on device sda1, logical block 134778
[ 3675.472552] Buffer I/O error on device sda1, logical block 134779
[ 3675.472558] sd 2:0:0:0: [sda] Unhandled error code
[ 3675.472560] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3675.472563] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 04 1d 13 00 00
02 00
[ 3675.472570] end_request: I/O error, dev sda, sector 269587
[ 3675.472573] Buffer I/O error on device sda1, logical block 134762
[ 3675.472625] sd 2:0:0:0: [sda] Unhandled error code
[ 3675.472628] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3675.472631] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 5c ff 2b 00 00
08 00
[ 3675.472638] end_request: I/O error, dev sda, sector 39649067
[ 3675.472644] EXT3-fs error (device sda7): ext3_get_inode_loc: unable
to read inode block - inode=340, block=73
[ 3675.472852] sd 2:0:0:0: [sda] Unhandled error code
[ 3675.472854] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3675.472858] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 01 dc 7d eb 00 00
20 00
[ 3675.472866] end_request: I/O error, dev sda, sector 31227371
[ 3675.472882] sd 2:0:0:0: [sda] Unhandled error code
[ 3675.472884] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3675.472887] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 01 dc 7d eb 00 00
08 00
[ 3675.472895] end_request: I/O error, dev sda, sector 31227371
[ 3675.472971] sd 2:0:0:0: [sda] Unhandled error code
[ 3675.472973] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3675.472976] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 01 dc 7d d3 00 00
10 00
[ 3675.472984] end_request: I/O error, dev sda, sector 31227347
[ 3675.472999] sd 2:0:0:0: [sda] Unhandled error code
[ 3675.473001] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3675.473004] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 01 dc 7d d3 00 00
08 00
[ 3675.473012] end_request: I/O error, dev sda, sector 31227347
[ 3675.473086] sd 2:0:0:0: [sda] Unhandled error code
[ 3675.473089] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3675.473093] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 01 dc 7d d3 00 00
08 00
[ 3675.473106] end_request: I/O error, dev sda, sector 31227347
[ 3675.473216] sd 2:0:0:0: [sda] Unhandled error code
[ 3675.473219] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3675.473222] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 49 23 ab 00 00
08 00
[ 3675.473230] end_request: I/O error, dev sda, sector 38347691
[ 3675.473296] sd 2:0:0:0: [sda] Unhandled error code
[ 3675.473298] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3675.473301] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 49 23 ab 00 00
08 00
[ 3675.473309] end_request: I/O error, dev sda, sector 38347691
[ 3675.473566] sd 2:0:0:0: [sda] Unhandled error code
[ 3675.473569] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3675.473572] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 01 dc 7d eb 00 00
08 00
[ 3675.473580] end_request: I/O error, dev sda, sector 31227371
[ 3675.473650] sd 2:0:0:0: [sda] Unhandled error code
[ 3675.473652] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3675.473656] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 01 dc 7d eb 00 00
08 00
[ 3675.473664] end_request: I/O error, dev sda, sector 31227371
[ 3675.473730] sd 2:0:0:0: [sda] Unhandled error code
[ 3675.473732] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3675.473735] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 01 dc 7d eb 00 00
08 00
[ 3675.473743] end_request: I/O error, dev sda, sector 31227371
[ 3675.473809] sd 2:0:0:0: [sda] Unhandled error code
[ 3675.473817] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3675.473829] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 01 dc 7d eb 00 00
08 00
[ 3675.473863] end_request: I/O error, dev sda, sector 31227371
[ 3675.473933] sd 2:0:0:0: [sda] Unhandled error code
[ 3675.473941] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3675.473954] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 01 dc 7d d3 00 00
08 00
[ 3675.473988] end_request: I/O error, dev sda, sector 31227347
[ 3675.474055] sd 2:0:0:0: [sda] Unhandled error code
[ 3675.474057] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3675.474060] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 01 dc 7d d3 00 00
08 00
[ 3675.474068] end_request: I/O error, dev sda, sector 31227347
[ 3680.977064] sd 2:0:0:0: [sda] Unhandled error code
[ 3680.977068] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3680.977072] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 01 c8 0e 83 00 00
18 00
[ 3680.977081] end_request: I/O error, dev sda, sector 29888131
[ 3680.977095] Aborting journal on device sda6.
[ 3680.977115] sd 2:0:0:0: [sda] Unhandled error code
[ 3680.977118] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3680.977121] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 01 c8 02 bb 00 00
08 00
[ 3680.977129] end_request: I/O error, dev sda, sector 29885115
[ 3680.977132] Buffer I/O error on device sda6, logical block 519
[ 3680.977134] lost page write due to I/O error on sda6
[ 3826.062544] ext3_abort called.
[ 3826.062549] EXT3-fs error (device sda5): ext3_journal_start_sb:
Detected aborted journal
[ 3826.062552] Remounting filesystem read-only
[ 3949.077661] ext3_abort called.
[ 3949.077666] EXT3-fs error (device sda6): ext3_journal_start_sb:
Detected aborted journal
[ 3949.077669] Remounting filesystem read-only
[ 3949.077998] sd 2:0:0:0: [sda] Unhandled error code
[ 3949.078001] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3949.078005] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 0a 57 7b 00 00
20 00
[ 3949.078014] end_request: I/O error, dev sda, sector 34232187
[ 3949.078032] sd 2:0:0:0: [sda] Unhandled error code
[ 3949.078034] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3949.078037] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 0a 57 7b 00 00
08 00
[ 3949.078045] end_request: I/O error, dev sda, sector 34232187
[ 3949.078109] sd 2:0:0:0: [sda] Unhandled error code
[ 3949.078111] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 3949.078115] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 0a 57 7b 00 00
08 00
[ 3949.078123] end_request: I/O error, dev sda, sector 34232187
[ 4057.976069] sd 2:0:0:0: [sda] Unhandled error code
[ 4057.976073] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4057.976077] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 02 7d a4 dd 00 00
68 00
[ 4057.976085] end_request: I/O error, dev sda, sector 41788637
[ 4057.976089] Buffer I/O error on device sda8, logical block 22528
[ 4057.976092] lost page write due to I/O error on sda8
[ 4057.976095] Buffer I/O error on device sda8, logical block 22529
[ 4057.976097] lost page write due to I/O error on sda8
[ 4057.976099] Buffer I/O error on device sda8, logical block 22530
[ 4057.976102] lost page write due to I/O error on sda8
[ 4057.976104] Buffer I/O error on device sda8, logical block 22531
[ 4057.976106] lost page write due to I/O error on sda8
[ 4057.976109] Buffer I/O error on device sda8, logical block 22532
[ 4057.976111] lost page write due to I/O error on sda8
[ 4057.976113] Buffer I/O error on device sda8, logical block 22533
[ 4057.976115] lost page write due to I/O error on sda8
[ 4057.976118] Buffer I/O error on device sda8, logical block 22534
[ 4057.976120] lost page write due to I/O error on sda8
[ 4057.976122] Buffer I/O error on device sda8, logical block 22535
[ 4057.976125] lost page write due to I/O error on sda8
[ 4057.976127] Buffer I/O error on device sda8, logical block 22536
[ 4057.976129] lost page write due to I/O error on sda8
[ 4057.976139] sd 2:0:0:0: [sda] Unhandled error code
[ 4057.976141] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4057.976144] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 02 7d a5 4d 00 00
48 00
[ 4057.976152] end_request: I/O error, dev sda, sector 41788749
[ 4057.976175] JBD: Detected IO errors while flushing file data on sda8
[ 4057.976214] sd 2:0:0:0: [sda] Unhandled error code
[ 4057.976216] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4057.976220] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 02 7b 08 ad 00 00
38 00
[ 4057.976228] end_request: I/O error, dev sda, sector 41617581
[ 4057.976241] Aborting journal on device sda8.
[ 4057.976255] sd 2:0:0:0: [sda] Unhandled error code
[ 4057.976258] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4057.976261] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 02 7a f5 fd 00 00
08 00
[ 4057.976268] end_request: I/O error, dev sda, sector 41612797
[ 4069.738094] sd 2:0:0:0: [sda] Unhandled error code
[ 4069.738097] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4069.738101] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 2f f3 ab 00 00
08 00
[ 4069.738110] end_request: I/O error, dev sda, sector 36697003
[ 4069.738118] EXT3-fs error (device sda6): ext3_get_inode_loc: unable
to read inode block - inode=418727, block=852005
[ 4445.560548] sd 2:0:0:0: [sda] Unhandled error code
[ 4445.560552] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4445.560556] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 02 63 7f ab 00 00
08 00
[ 4445.560564] end_request: I/O error, dev sda, sector 40075179
[ 4445.560568] __ratelimit: 14 callbacks suppressed
[ 4445.560571] Buffer I/O error on device sda7, logical block 53337
[ 4445.560573] lost page write due to I/O error on sda7
[ 4445.560586] sd 2:0:0:0: [sda] Unhandled error code
[ 4445.560588] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4445.560591] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 02 63 7f e3 00 00
08 00
[ 4445.560599] end_request: I/O error, dev sda, sector 40075235
[ 4445.560602] Buffer I/O error on device sda7, logical block 53344
[ 4445.560604] lost page write due to I/O error on sda7
[ 4495.568018] sd 2:0:0:0: [sda] Unhandled error code
[ 4495.568022] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4495.568025] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 02 63 7f e3 00 00
08 00
[ 4495.568034] end_request: I/O error, dev sda, sector 40075235
[ 4495.568038] Buffer I/O error on device sda7, logical block 53344
[ 4495.568040] lost page write due to I/O error on sda7
[ 4495.568049] sd 2:0:0:0: [sda] Unhandled error code
[ 4495.568051] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4495.568054] sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 02 63 7f ab 00 00
08 00
[ 4495.568061] end_request: I/O error, dev sda, sector 40075179
[ 4495.568064] Buffer I/O error on device sda7, logical block 53337
[ 4495.568066] lost page write due to I/O error on sda7
[ 4809.297666] ext3_abort called.
[ 4809.297671] EXT3-fs error (device sda8): ext3_journal_start_sb:
Detected aborted journal
[ 4809.297674] Remounting filesystem read-only
[ 4832.298725] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.298729] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.298733] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 01 e0 8d 1b 00 00
08 00
[ 4832.298741] end_request: I/O error, dev sda, sector 31493403
[ 4832.298752] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.298754] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.298757] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 01 e0 8e 1b 00 00
08 00
[ 4832.298766] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.298768]
[ 4832.298769] end_request: I/O error, dev sda, sector 31493659
[ 4832.298773] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.298776] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 01 e0 8d 1b 00 00
08 00
[ 4832.298784] end_request: I/O error, dev sda, sector 31493403
[ 4832.301537] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.301540] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.301544] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 0c 0a 8b 00 00
08 00
[ 4832.301552] end_request: I/O error, dev sda, sector 34343563
[ 4832.301573] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.301575] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.301579] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 0c 0a 8b 00 00
08 00
[ 4832.301586] end_request: I/O error, dev sda, sector 34343563
[ 4832.302182] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.302185] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.302188] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d7 93 00 00
08 00
[ 4832.302196] end_request: I/O error, dev sda, sector 2152339
[ 4832.302203] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=102283, block=196742
[ 4832.302422] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.302424] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.302427] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d6 83 00 00
08 00
[ 4832.302435] end_request: I/O error, dev sda, sector 2152067
[ 4832.302441] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=101212, block=196708
[ 4832.302470] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.302472] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.302475] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d7 93 00 00
08 00
[ 4832.302483] end_request: I/O error, dev sda, sector 2152339
[ 4832.302488] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=102283, block=196742
[ 4832.302519] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.302521] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.302525] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d8 6b 00 00
08 00
[ 4832.302532] end_request: I/O error, dev sda, sector 2152555
[ 4832.302538] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=103165, block=196769
[ 4832.302656] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.302658] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.302661] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 25 31 1b 00 00
10 00
[ 4832.302669] end_request: I/O error, dev sda, sector 2437403
[ 4832.302684] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.302686] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.302689] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 25 31 1b 00 00
08 00
[ 4832.302697] end_request: I/O error, dev sda, sector 2437403
[ 4832.303414] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.303417] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.303420] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d7 b3 00 00
08 00
[ 4832.303428] end_request: I/O error, dev sda, sector 2152371
[ 4832.303435] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=102419, block=196746
[ 4832.303664] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.303666] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.303670] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d7 b3 00 00
08 00
[ 4832.303677] end_request: I/O error, dev sda, sector 2152371
[ 4832.303683] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=102419, block=196746
[ 4832.303753] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.303755] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.303759] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 24 b9 2b 00 00
08 00
[ 4832.303766] end_request: I/O error, dev sda, sector 2406699
[ 4832.303781] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.303783] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.303786] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 24 b9 2b 00 00
08 00
[ 4832.303794] end_request: I/O error, dev sda, sector 2406699
[ 4832.305356] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.305358] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.305362] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 0c 0b 3b 00 00
08 00
[ 4832.305370] end_request: I/O error, dev sda, sector 34343739
[ 4832.305386] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.305389] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.305392] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 0c 0b 3b 00 00
08 00
[ 4832.305399] end_request: I/O error, dev sda, sector 34343739
[ 4832.306455] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.306458] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.306461] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 24 e4 4b 00 00
08 00
[ 4832.306469] end_request: I/O error, dev sda, sector 2417739
[ 4832.306490] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.306492] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.306496] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 24 e4 4b 00 00
08 00
[ 4832.306503] end_request: I/O error, dev sda, sector 2417739
[ 4832.307471] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.307474] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.307477] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 24 d2 83 00 00
08 00
[ 4832.307485] end_request: I/O error, dev sda, sector 2413187
[ 4832.307503] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.307505] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.307509] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 24 d2 83 00 00
08 00
[ 4832.307516] end_request: I/O error, dev sda, sector 2413187
[ 4832.308210] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.308213] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.308217] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 24 e3 bb 00 00
08 00
[ 4832.308224] end_request: I/O error, dev sda, sector 2417595
[ 4832.308240] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.308243] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.308246] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 24 e3 bb 00 00
08 00
[ 4832.308253] end_request: I/O error, dev sda, sector 2417595
[ 4832.308437] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.308439] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.308442] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d7 8b 00 00
08 00
[ 4832.308450] end_request: I/O error, dev sda, sector 2152331
[ 4832.308456] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=102241, block=196741
[ 4832.308653] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.308656] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.308659] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d7 53 00 00
08 00
[ 4832.308666] end_request: I/O error, dev sda, sector 2152275
[ 4832.308672] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=102036, block=196734
[ 4832.308706] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.308708] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.308712] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d7 8b 00 00
08 00
[ 4832.308719] end_request: I/O error, dev sda, sector 2152331
[ 4832.308724] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=102241, block=196741
[ 4832.308831] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.308834] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.308837] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 24 c9 43 00 00
08 00
[ 4832.308844] end_request: I/O error, dev sda, sector 2410819
[ 4832.308859] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.308862] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.308865] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 24 c9 43 00 00
08 00
[ 4832.308872] end_request: I/O error, dev sda, sector 2410819
[ 4832.308994] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.308997] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.309000] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 24 e9 6b 00 00
08 00
[ 4832.309008] end_request: I/O error, dev sda, sector 2419051
[ 4832.309024] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.309027] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.309031] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 24 e9 6b 00 00
08 00
[ 4832.309044] end_request: I/O error, dev sda, sector 2419051
[ 4832.309130] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.309133] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.309137] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d7 8b 00 00
08 00
[ 4832.309150] end_request: I/O error, dev sda, sector 2152331
[ 4832.309157] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=102249, block=196741
[ 4832.309372] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.309374] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.309377] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d7 8b 00 00
08 00
[ 4832.309385] end_request: I/O error, dev sda, sector 2152331
[ 4832.309391] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=102249, block=196741
[ 4832.309452] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.309455] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.309458] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 24 b3 c3 00 00
08 00
[ 4832.309466] end_request: I/O error, dev sda, sector 2405315
[ 4832.309480] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.309482] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.309485] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 24 b3 c3 00 00
08 00
[ 4832.309493] end_request: I/O error, dev sda, sector 2405315
[ 4832.309608] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.309610] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.309613] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d8 1b 00 00
08 00
[ 4832.309621] end_request: I/O error, dev sda, sector 2152475
[ 4832.309628] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=102817, block=196759
[ 4832.309850] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.309852] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.309855] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d8 1b 00 00
08 00
[ 4832.309863] end_request: I/O error, dev sda, sector 2152475
[ 4832.309869] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=102817, block=196759
[ 4832.310416] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.310419] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.310422] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d6 9b 00 00
08 00
[ 4832.310430] end_request: I/O error, dev sda, sector 2152091
[ 4832.310438] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=101287, block=196711
[ 4832.310637] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.310639] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.310643] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d6 9b 00 00
08 00
[ 4832.310650] end_request: I/O error, dev sda, sector 2152091
[ 4832.310657] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=101287, block=196711
[ 4832.310737] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.310739] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.310743] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 24 e8 c3 00 00
08 00
[ 4832.310752] end_request: I/O error, dev sda, sector 2418883
[ 4832.310767] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.310770] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.310774] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 24 e8 c3 00 00
08 00
[ 4832.310787] end_request: I/O error, dev sda, sector 2418883
[ 4832.310993] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.310996] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.310999] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 24 c4 c3 00 00
08 00
[ 4832.311007] end_request: I/O error, dev sda, sector 2409667
[ 4832.311022] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.311024] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.311027] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 24 c4 c3 00 00
08 00
[ 4832.311035] end_request: I/O error, dev sda, sector 2409667
[ 4832.311429] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.311432] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.311435] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d7 f3 00 00
08 00
[ 4832.311443] end_request: I/O error, dev sda, sector 2152435
[ 4832.311452] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=102679, block=196754
[ 4832.312182] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.312184] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.312188] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 4f f4 83 00 00
08 00
[ 4832.312195] end_request: I/O error, dev sda, sector 38794371
[ 4832.312203] EXT3-fs error (device sda6): ext3_get_inode_loc: unable
to read inode block - inode=548112, block=1114176
[ 4832.312232] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.312234] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.312238] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 4f f4 83 00 00
08 00
[ 4832.312245] end_request: I/O error, dev sda, sector 38794371
[ 4832.312250] EXT3-fs error (device sda6): ext3_get_inode_loc: unable
to read inode block - inode=548112, block=1114176
[ 4832.312535] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.312538] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.312541] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 4f f4 83 00 00
08 00
[ 4832.312549] end_request: I/O error, dev sda, sector 38794371
[ 4832.312554] EXT3-fs error (device sda6): ext3_get_inode_loc: unable
to read inode block - inode=548112, block=1114176
[ 4832.312581] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.312584] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.312587] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 4f f4 83 00 00
08 00
[ 4832.312594] end_request: I/O error, dev sda, sector 38794371
[ 4832.312600] EXT3-fs error (device sda6): ext3_get_inode_loc: unable
to read inode block - inode=548112, block=1114176
[ 4832.312681] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.312683] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.312686] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 01 d3 f2 f3 00 00
08 00
[ 4832.312694] end_request: I/O error, dev sda, sector 30667507
[ 4832.312699] EXT3-fs error (device sda6): ext3_get_inode_loc: unable
to read inode block - inode=48532, block=98318
[ 4832.312729] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.312731] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.312734] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 01 d3 f2 f3 00 00
08 00
[ 4832.312742] end_request: I/O error, dev sda, sector 30667507
[ 4832.312747] EXT3-fs error (device sda6): ext3_get_inode_loc: unable
to read inode block - inode=48532, block=98318
[ 4832.312831] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.312833] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.312836] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 47 f2 c3 00 00
08 00
[ 4832.312844] end_request: I/O error, dev sda, sector 38269635
[ 4832.312849] EXT3-fs error (device sda6): ext3_get_inode_loc: unable
to read inode block - inode=514194, block=1048584
[ 4832.312877] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.312879] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.312882] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 47 f2 c3 00 00
08 00
[ 4832.312890] end_request: I/O error, dev sda, sector 38269635
[ 4832.312895] EXT3-fs error (device sda6): ext3_get_inode_loc: unable
to read inode block - inode=514194, block=1048584
[ 4832.312973] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.312975] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.312979] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 1f f4 7b 00 00
08 00
[ 4832.312986] end_request: I/O error, dev sda, sector 35648635
[ 4832.312991] EXT3-fs error (device sda6): ext3_get_inode_loc: unable
to read inode block - inode=355310, block=720959
[ 4832.313019] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.313022] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.313026] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 1f f4 7b 00 00
08 00
[ 4832.313038] end_request: I/O error, dev sda, sector 35648635
[ 4832.313046] EXT3-fs error (device sda6): ext3_get_inode_loc: unable
to read inode block - inode=355310, block=720959
[ 4832.313126] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.313128] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.313133] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 01 e7 f5 6b 00 00
08 00
[ 4832.313146] end_request: I/O error, dev sda, sector 31978859
[ 4832.313153] EXT3-fs error (device sda6): ext3_get_inode_loc: unable
to read inode block - inode=131371, block=262237
[ 4832.313179] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.313182] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.313186] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 01 e7 f5 6b 00 00
08 00
[ 4832.313199] end_request: I/O error, dev sda, sector 31978859
[ 4832.313205] EXT3-fs error (device sda6): ext3_get_inode_loc: unable
to read inode block - inode=131371, block=262237
[ 4832.313321] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.313323] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.313326] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 2d 8f 1b 00 00
20 00
[ 4832.313334] end_request: I/O error, dev sda, sector 36540187
[ 4832.313349] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.313351] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.313354] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 2d 8f 1b 00 00
08 00
[ 4832.313361] end_request: I/O error, dev sda, sector 36540187
[ 4832.313489] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.313491] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.313494] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 24 e4 c3 00 00
08 00
[ 4832.313508] end_request: I/O error, dev sda, sector 2417859
[ 4832.313528] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.313530] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.313533] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 24 e4 c3 00 00
08 00
[ 4832.313541] end_request: I/O error, dev sda, sector 2417859
[ 4832.313640] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.313642] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.313645] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 01 e1 b7 53 00 00
08 00
[ 4832.313653] end_request: I/O error, dev sda, sector 31569747
[ 4832.313660] EXT3-fs error (device sda6): ext3_find_entry: reading
directory #103744 offset 0
[ 4832.313722] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.313724] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.313727] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 01 e1 b7 53 00 00
08 00
[ 4832.313735] end_request: I/O error, dev sda, sector 31569747
[ 4832.313742] EXT3-fs error (device sda6): ext3_find_entry: reading
directory #103744 offset 0
[ 4832.313789] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.313791] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.313795] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 01 e1 b7 53 00 00
08 00
[ 4832.313802] end_request: I/O error, dev sda, sector 31569747
[ 4832.313809] EXT3-fs error (device sda6): ext3_find_entry: reading
directory #103744 offset 0
[ 4832.313869] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.313872] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.313875] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d8 33 00 00
08 00
[ 4832.313882] end_request: I/O error, dev sda, sector 2152499
[ 4832.313889] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=102929, block=196762
[ 4832.314072] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.314075] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.314079] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d7 53 00 00
08 00
[ 4832.314092] end_request: I/O error, dev sda, sector 2152275
[ 4832.314099] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=102026, block=196734
[ 4832.314126] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.314129] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.314134] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d8 33 00 00
08 00
[ 4832.314146] end_request: I/O error, dev sda, sector 2152499
[ 4832.314153] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=102929, block=196762
[ 4832.314220] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.314223] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.314227] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 24 c8 f3 00 00
08 00
[ 4832.314240] end_request: I/O error, dev sda, sector 2410739
[ 4832.314255] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.314258] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.314262] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 24 c8 f3 00 00
08 00
[ 4832.314275] end_request: I/O error, dev sda, sector 2410739
[ 4832.314641] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.314644] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.314647] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d8 33 00 00
08 00
[ 4832.314655] end_request: I/O error, dev sda, sector 2152499
[ 4832.314662] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=102937, block=196762
[ 4832.314846] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.314848] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.314852] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d7 53 00 00
08 00
[ 4832.314859] end_request: I/O error, dev sda, sector 2152275
[ 4832.314865] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=102037, block=196734
[ 4832.314892] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.314894] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.314898] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d8 33 00 00
08 00
[ 4832.314905] end_request: I/O error, dev sda, sector 2152499
[ 4832.314911] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=102937, block=196762
[ 4832.315917] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.315920] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.315924] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d8 43 00 00
08 00
[ 4832.315933] end_request: I/O error, dev sda, sector 2152515
[ 4832.315943] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=102978, block=196764
[ 4832.316181] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.316183] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.316187] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d8 43 00 00
08 00
[ 4832.316195] end_request: I/O error, dev sda, sector 2152515
[ 4832.316201] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=102978, block=196764
[ 4832.316294] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.316297] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.316300] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 24 d0 53 00 00
08 00
[ 4832.316308] end_request: I/O error, dev sda, sector 2412627
[ 4832.316324] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.316326] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.316330] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 24 d0 53 00 00
08 00
[ 4832.316337] end_request: I/O error, dev sda, sector 2412627
[ 4832.316441] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.316444] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.316447] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d8 4b 00 00
08 00
[ 4832.316455] end_request: I/O error, dev sda, sector 2152523
[ 4832.316460] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=103012, block=196765
[ 4832.316668] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.316671] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.316674] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d7 6b 00 00
08 00
[ 4832.316681] end_request: I/O error, dev sda, sector 2152299
[ 4832.316687] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=102129, block=196737
[ 4832.316717] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.316719] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.316723] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 20 d8 4b 00 00
08 00
[ 4832.316730] end_request: I/O error, dev sda, sector 2152523
[ 4832.316736] EXT3-fs error (device sda5): ext3_get_inode_loc: unable
to read inode block - inode=103012, block=196765
[ 4832.803448] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.803452] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.803456] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 01 f1 3f f3 00 00
08 00
[ 4832.803465] end_request: I/O error, dev sda, sector 32587763
[ 4832.803474] EXT3-fs error (device sda6): ext3_find_entry: reading
directory #162811 offset 0
[ 4832.833747] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.833750] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.833754] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 01 f1 3f f3 00 00
08 00
[ 4832.833761] end_request: I/O error, dev sda, sector 32587763
[ 4832.833770] EXT3-fs error (device sda6): ext3_find_entry: reading
directory #162811 offset 0
[ 4832.833821] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.833823] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.833826] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 01 f1 3f f3 00 00
08 00
[ 4832.833833] end_request: I/O error, dev sda, sector 32587763
[ 4832.833838] EXT3-fs error (device sda6): ext3_find_entry: reading
directory #162811 offset 0
[ 4832.847471] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.847474] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.847477] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 24 c7 9b 00 00
08 00
[ 4832.847485] end_request: I/O error, dev sda, sector 2410395
[ 4832.847512] sd 2:0:0:0: [sda] Unhandled error code
[ 4832.847515] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4832.847518] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 24 c7 9b 00 00
08 00
[ 4832.847524] end_request: I/O error, dev sda, sector 2410395
[ 4834.492677] sd 2:0:0:0: [sda] Unhandled error code
[ 4834.492681] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4834.492685] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 05 8e 5d 00 00
06 00
[ 4834.492693] end_request: I/O error, dev sda, sector 364125
[ 4834.492809] sd 2:0:0:0: [sda] Unhandled error code
[ 4834.492811] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4834.492815] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 05 8e 5d 00 00
06 00
[ 4834.492822] end_request: I/O error, dev sda, sector 364125
[ 4834.492922] sd 2:0:0:0: [sda] Unhandled error code
[ 4834.492924] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4834.492928] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 2c e5 eb 00 00
08 00
[ 4834.492935] end_request: I/O error, dev sda, sector 2942443
[ 4834.492944] sd 2:0:0:0: [sda] Unhandled error code
[ 4834.492946] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4834.492949] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 2c e6 03 00 00
08 00
[ 4834.492957] end_request: I/O error, dev sda, sector 2942467
[ 4834.492962] sd 2:0:0:0: [sda] Unhandled error code
[ 4834.492964] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4834.492967] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 2e 2d 33 00 00
08 00
[ 4834.492974] end_request: I/O error, dev sda, sector 3026227
[ 4834.492991] sd 2:0:0:0: [sda] Unhandled error code
[ 4834.492994] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4834.492997] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 2c e5 eb 00 00
08 00
[ 4834.493004] end_request: I/O error, dev sda, sector 2942443
[ 4834.498181] sd 2:0:0:0: [sda] Unhandled error code
[ 4834.498185] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4834.498189] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 2e da 83 00 00
48 00
[ 4834.498197] end_request: I/O error, dev sda, sector 36625027
[ 4834.498352] sd 2:0:0:0: [sda] Unhandled error code
[ 4834.498354] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4834.498358] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 2e da b3 00 00
08 00
[ 4834.498365] end_request: I/O error, dev sda, sector 36625075
[ 4835.417079] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.417082] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.417086] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 0b cb 5b 00 00
18 00
[ 4835.417095] end_request: I/O error, dev sda, sector 34327387
[ 4835.417119] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.417122] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.417126] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 0b cb 5b 00 00
08 00
[ 4835.417134] end_request: I/O error, dev sda, sector 34327387
[ 4835.417185] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.417187] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.417190] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 0b cb 5b 00 00
08 00
[ 4835.417198] end_request: I/O error, dev sda, sector 34327387
[ 4835.421019] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.421023] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.421026] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 04 cc 9b 00 00
08 00
[ 4835.421033] end_request: I/O error, dev sda, sector 33868955
[ 4835.423108] EXT3-fs error (device sda6): ext3_find_entry: reading
directory #242275 offset 1
[ 4835.424194] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.424197] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.424201] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 2e 37 d3 00 00
10 00
[ 4835.424209] end_request: I/O error, dev sda, sector 36583379
[ 4835.424221] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.424223] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.424226] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 2e 38 13 00 00 10
[ 4835.424234] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.424237] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.424240] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 2e 37 d3 00 00
08 00
[ 4835.424253] end_request: I/O error, dev sda, sector 36583379
[ 4835.424254] 00
[ 4835.424256] end_request: I/O error, dev sda, sector 36583443
[ 4835.427841] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.427844] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.427848] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 02 7c 4b 00 00
1a 00
[ 4835.427856] end_request: I/O error, dev sda, sector 162891
[ 4835.427880] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.427882] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.427886] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 02 7c 63 00 00
02 00
[ 4835.427894] end_request: I/O error, dev sda, sector 162915
[ 4835.427910] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.427912] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.427915] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 02 7c 63 00 00
02 00
[ 4835.427923] end_request: I/O error, dev sda, sector 162915
[ 4835.427938] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.427940] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.427943] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 02 7c 63 00 00
02 00
[ 4835.427951] end_request: I/O error, dev sda, sector 162915
[ 4835.427966] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.427968] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.427971] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 02 7c 63 00 00
02 00
[ 4835.427978] end_request: I/O error, dev sda, sector 162915
[ 4835.427995] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.427997] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.428000] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 02 7c 4b 00 00
08 00
[ 4835.428008] end_request: I/O error, dev sda, sector 162891
[ 4835.429626] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.429629] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.429633] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 2e 37 d3 00 00
08 00
[ 4835.429640] end_request: I/O error, dev sda, sector 36583379
[ 4835.433106] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.433109] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.433113] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 02 7c 4b 00 00
08 00
[ 4835.433121] end_request: I/O error, dev sda, sector 162891
[ 4835.434689] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.434692] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.434696] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 2e 37 d3 00 00
08 00
[ 4835.434704] end_request: I/O error, dev sda, sector 36583379
[ 4835.437887] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.437890] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.437894] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 02 7c 4b 00 00
08 00
[ 4835.437902] end_request: I/O error, dev sda, sector 162891
[ 4835.439435] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.439438] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.439441] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 2e 37 d3 00 00
08 00
[ 4835.439450] end_request: I/O error, dev sda, sector 36583379
[ 4835.442480] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.442483] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.442487] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 02 7c 4b 00 00
08 00
[ 4835.442495] end_request: I/O error, dev sda, sector 162891
[ 4835.444021] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.444024] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.444028] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 2e 37 d3 00 00
08 00
[ 4835.444036] end_request: I/O error, dev sda, sector 36583379
[ 4835.447056] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.447060] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.447064] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 02 7c 4b 00 00
08 00
[ 4835.447071] end_request: I/O error, dev sda, sector 162891
[ 4835.448601] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.448604] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.448607] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 2e 37 d3 00 00
08 00
[ 4835.448615] end_request: I/O error, dev sda, sector 36583379
[ 4835.451786] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.451789] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.451792] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 02 7c 4b 00 00
08 00
[ 4835.451800] end_request: I/O error, dev sda, sector 162891
[ 4835.453385] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.453388] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.453392] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 2e 37 d3 00 00
08 00
[ 4835.453400] end_request: I/O error, dev sda, sector 36583379
[ 4835.456637] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.456640] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.456643] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 02 7c 4b 00 00
08 00
[ 4835.456650] end_request: I/O error, dev sda, sector 162891
[ 4835.472794] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.472798] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.472801] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 05 8e 5d 00 00
06 00
[ 4835.472808] end_request: I/O error, dev sda, sector 364125
[ 4835.472885] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.472887] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.472890] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 2c e5 eb 00 00
08 00
[ 4835.472897] end_request: I/O error, dev sda, sector 2942443
[ 4835.477601] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.477603] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.477607] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 2e 37 d3 00 00
08 00
[ 4835.477614] end_request: I/O error, dev sda, sector 36583379
[ 4835.480328] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.480331] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.480334] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 02 7c 4b 00 00
08 00
[ 4835.480341] end_request: I/O error, dev sda, sector 162891
[ 4835.520721] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.520725] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.520729] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 0a 2a 4b 00 00
20 00
[ 4835.520737] end_request: I/O error, dev sda, sector 34220619
[ 4835.520759] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.520762] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.520765] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 0a 2a 4b 00 00
08 00
[ 4835.520773] end_request: I/O error, dev sda, sector 34220619
[ 4835.520822] sd 2:0:0:0: [sda] Unhandled error code
[ 4835.520824] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4835.520827] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 02 0a 2a 4b 00 00
08 00
[ 4835.520835] end_request: I/O error, dev sda, sector 34220619
...

# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 280003 174103 91444 66% /
tmpfs 1037112 0 1037112 0% /lib/init/rw
udev 1033004 252 1032752 1% /dev
tmpfs 1037112 0 1037112 0% /dev/shm
/dev/sda5 14421344 1750232 11938552 13% /home
/dev/sda6 4807056 3236860 1326012 71% /usr
/dev/sda7 964500 614576 300928 68% /var
/dev/sda8 964500 17672 897832 2% /tmp
/dev/sda9 4807056 209124 4353748 5% /usr/local
/dev/sda11 47383396 43219420 1757040 97% /extra
/dev/sda12 918322 16452 852874 2% /others
/dev/sdb1 14436960 3846056 9857540 29% /storage

# smartctl -a /dev/sda
smartctl 5.40 2010-07-12 r3124 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.7 and 7200.7 Plus family
Device Model: ST380011A
Serial Number: 4JV5P7LN
Firmware Version: 8.01
User Capacity: 80,026,361,856 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 6
ATA Standard is: ATA/ATAPI-6 T13 1410D revision 2
Local Time is: Mon Jan 24 04:53:56 2011 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection:
Enabled.
Self-test execution status: ( 0) The previous self-test routine
completed
without error or no self-test
has ever
been run.
Total time to complete Offline
data collection: ( 430) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection
on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 58) minutes.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 059 056 006 Pre-fail Always
- 223313989
3 Spin_Up_Time 0x0003 098 098 000 Pre-fail Always
- 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always
- 0
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always
- 0
7 Seek_Error_Rate 0x000f 086 060 030 Pre-fail Always
- 430731234
9 Power_On_Hours 0x0032 051 051 000 Old_age Always
- 43201
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always
- 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always
- 308
194 Temperature_Celsius 0x0022 035 048 000 Old_age Always
- 35
195 Hardware_ECC_Recovered 0x001a 059 055 000 Old_age Always
- 223313989
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always
- 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline
- 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always
- 0
200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline
- 0
202 Data_Address_Mark_Errs 0x0032 100 253 000 Old_age Always
- 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining
LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 39844 -
# 2 Extended offline Interrupted (host reset) 20% 38502 -
# 3 Extended offline Completed without error 00% 35555 -
# 4 Extended offline Completed without error 00% 31886 -
# 5 Extended offline Completed without error 00% 22233 -
# 6 Extended offline Completed without error 00% 18951 -
# 7 Extended offline Completed without error 00% 18674 -
# 8 Extended offline Completed without error 00% 15957 -
# 9 Extended offline Completed without error 00% 14448 -

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

I ran two smartctl -t long on both /dev/hda and /dev/hdb, but not sure
if they finished since I got errors and disconnections(?). I powered off
PC and rebooted back to Debian and checked its results after an hour:

# smartctl -a /dev/sdb
smartctl 5.40 2010-07-12 r3124 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Quantum Fireball Plus LM series
Device Model: QUANTUM FIREBALLP LM15
Serial Number: 183006136328
Firmware Version: A35.0700
User Capacity: 15,020,457,984 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 5
ATA Standard is: ATA/ATAPI-5 T13 1321D revision 1
Local Time is: Mon Jan 24 06:17:01 2011 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection:
Disabled.
Self-test execution status: ( 0) The previous self-test routine
completed
without error or no self-test
has ever
been run.
Total time to complete Offline
data collection: ( 46) seconds.
Offline data collection
capabilities: (0x1b) SMART execute Offline immediate.
Auto Offline data collection
on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
No General Purpose Logging support.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 13) minutes.

SMART Attributes Data Structure revision number: 11
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x0029 100 253 020 Pre-fail
Offline - 0
3 Spin_Up_Time 0x0027 064 063 020 Pre-fail Always
- 4535
4 Start_Stop_Count 0x0032 097 097 008 Old_age Always
- 2368
5 Reallocated_Sector_Ct 0x0033 100 100 020 Pre-fail Always
- 0
7 Seek_Error_Rate 0x000b 100 100 023 Pre-fail Always
- 0
9 Power_On_Hours 0x0012 012 012 001 Old_age Always
- 58064
10 Spin_Retry_Count 0x0026 100 100 020 Old_age Always
- 0
11 Calibration_Retry_Count 0x0013 100 100 020 Pre-fail Always
- 0
12 Power_Cycle_Count 0x0032 097 097 008 Old_age Always
- 2254
13 Read_Soft_Error_Rate 0x000b 100 100 023 Pre-fail Always
- 0
199 UDMA_CRC_Error_Count 0x001a 200 200 000 Old_age Always
- 0
196 Reallocated_Event_Count 0x0010 100 100 020 Old_age Offline
- 0
197 Current_Pending_Sector 0x0032 100 100 020 Old_age Always
- 0
198 Offline_Uncorrectable 0x0010 100 253 000 Old_age Offline
- 0

SMART Error Log Version: 0
No Errors Logged

SMART Self-test log structure revision number 0
Warning: ATA Specification requires self-test log structure revision
number = 1
Num Test_Description Status Remaining
LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 54663 -
# 2 Extended offline Completed without error 00% 53303 -
# 3 Extended offline Completed without error 00% 46603 -
# 4 Short offline Completed without error 00% 15067 -
# 5 Extended offline Completed without error 00% 13222 -
# 6 Short offline Completed without error 00% 13218 -
# 7 Short offline Completed without error 00% 8391 -
# 8 Short offline Completed without error 00% 8391 -

Device does not support Selective Self Tests/Logging

# smartctl -a /dev/sda
smartctl 5.40 2010-07-12 r3124 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.7 and 7200.7 Plus family
Device Model: ST380011A
Serial Number: 4JV5P7LN
Firmware Version: 8.01
User Capacity: 80,026,361,856 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 6
ATA Standard is: ATA/ATAPI-6 T13 1410D revision 2
Local Time is: Mon Jan 24 06:17:03 2011 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection:
Enabled.
Self-test execution status: ( 41) The self-test routine was
interrupted
by the host with a hard or soft
reset.
Total time to complete Offline
data collection: ( 430) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection
on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 58) minutes.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 063 056 006 Pre-fail Always
- 34855661
3 Spin_Up_Time 0x0003 098 098 000 Pre-fail Always
- 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always
- 0
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always
- 0
7 Seek_Error_Rate 0x000f 086 060 030 Pre-fail Always
- 430814830
9 Power_On_Hours 0x0032 051 051 000 Old_age Always
- 43202
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always
- 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always
- 310
194 Temperature_Celsius 0x0022 036 048 000 Old_age Always
- 36
195 Hardware_ECC_Recovered 0x001a 063 055 000 Old_age Always
- 34855661
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always
- 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline
- 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always
- 0
200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline
- 0
202 Data_Address_Mark_Errs 0x0032 100 253 000 Old_age Always
- 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining
LifeTime(hours) LBA_of_first_error
# 1 Extended offline Interrupted (host reset) 90% 43201 -
# 2 Extended offline Completed without error 00% 39844 -
# 3 Extended offline Interrupted (host reset) 20% 38502 -
# 4 Extended offline Completed without error 00% 35555 -
# 5 Extended offline Completed without error 00% 31886 -
# 6 Extended offline Completed without error 00% 22233 -
# 7 Extended offline Completed without error 00% 18951 -
# 8 Extended offline Completed without error 00% 18674 -
# 9 Extended offline Completed without error 00% 15957 -
#10 Extended offline Completed without error 00% 14448 -

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

FYI for other helpful(?) information:

# hdparm /dev/sda

/dev/sda:
multcount = 16 (on)
IO_support = 0 (default)
readonly = 0 (off)
readahead = 256 (on)
geometry = 9729/255/63, sectors = 156301488, start = 0

# hdparm /dev/sdb

/dev/sdb:
multcount = 0 (off)
IO_support = 0 (default)
readonly = 0 (off)
readahead = 256 (on)
geometry = 1826/255/63, sectors = 29336832, start = 0

# cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/hda1 / ext3 defaults,errors=remount-ro 0 1
UUID=fe4a1af1-1979-49fb-9668-314a24b12890 / ext3
defaults,errors=remount-ro 0 1
# /dev/hda5 /home ext3 defaults 0 2
UUID=5171f646-535c-4dc2-8adf-41e4fed2b453 /home ext3
defaults 0 2
# /dev/hda6 /usr ext3 defaults 0 2
UUID=8d0bf8c2-1358-4b2f-aa9a-d13ea676c647 /usr ext3
defaults 0 2
# /dev/hda7 /var ext3 defaults 0 2
UUID=0278e896-de67-459c-bd0a-eff64df316a7 /var ext3
defaults 0 2
# /dev/hda8 /tmp ext3 defaults 0 2
UUID=c428ab09-5b41-4120-8c79-2685a6f42086 /tmp ext3
defaults 0 2
# /dev/hda9 /usr/local ext3 defaults 0 2
UUID=7b15718e-cdf0-4d93-aca3-2b99100a2d74 /usr/local ext3
defaults 0 2
# /dev/hda10 none swap sw 0 0
UUID=605eb2f4-913e-4cc3-b8ca-99ab350b532b none swap sw
0 0
# /dev/hda11 /extra ext3 defaults 0 2
UUID=4c6ab6ae-fbc8-4cd5-aaf2-947a155be324 /extra ext3
defaults 0 2
# /dev/hda12 /others ext3 defaults 0 2
UUID=0835d191-f8b3-4f6c-b623-6bf2933c40b6 /others ext3
defaults 0 2
# /dev/hdb1 /storage ext3 defaults 0 2
UUID=e7405433-9fee-40e4-8736-dd26b9c6ed88 /storage ext3
defaults 0 2
# /dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/cdrom1 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
/dev/sda1 /mnt/usb-flash vfat noauto,users,umask=000 0 0

none /proc/bus/usb usbfs devgid=46,devmode=664 0 0

$ ls /storage/
ls: cannot access /storage/stuff: Input/output error
ls: cannot access /storage/Songs: Input/output error
ls: cannot access /storage/Zips: Input/output error
ls: cannot access /storage/backups: Input/output error
stuff backups lost+found Songs SharedFiles Zips

Am I reading correctly that my Quantum 15 GB IDE/PATA HDD is dying since
it can't seem to connect to it and stuff? Or is it somethign else?

Assuming my storage Quantum IDE/PATA drive is dying and I can't replace
it right away, I guess I can live without it for a bit for now. I have
three questions:
1. How do I tell Linux/Debian to enable write again without
rebooting/restarting the computer?
2. How can I tell Linux/Debian to stop using/ignore that drive or do I
have to physically disconnect/unplug it? I am disabled and can't even
open my PC case and reach inside so I am hoping I can just tell computer
with commands or something. :(
3. What's the best way to copy all the datas from this one to another
HDD (have two old IDE/PATA HDDs in my drawer)? Is it still drescue or
something like that command in KNOPPIX's boot liveCD? Or is there
something better now since I last used was over five years or so.

Thank you in advance. :(
--
"A coconut shell full of water is a(n) sea/ocean to an ant." --Indians
/\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) If e-mailing, then axe ANT from its address if needed.
Ant is currently not listening to any songs on this computer.

[Trevor Hemsley]

On Mon, 24 Jan 2011 15:13:26 UTC in comp.os.linux.hardware, Ant
<a...@zimage.comANT> wrote:

>
> Device Model: QUANTUM FIREBALLP LM15

The poor thing is 11 years old. Take it out and give it a decent burial!

You're running a quad core core 2 Q8200 CPU with a disk that old - it's like
having a Ferrari with bike tyres :-)

--
Trevor Hemsley, Brighton, UK
Trevor dot Hemsley at ntlworld dot com

[Rod Speed]

Ant wrote:
> Hello.
>
> I woke up overnight (about six hours since I last used my computer
> without any problems) and noticed my old Debian/Linux box was acting
> weird (IRC chat bot/rbot gave errors about corrupted database,
> detached screen logged me out, could not log back in through SSH2
> from a Windows box on LAN, Xscreensaver wouldn't let me back in locally (PAM errors),
> could not ctrl-alt-backspace on local PC, etc.). I did a hard reset to
> reboot. I went back to KDE v3.5.10, and noticed it took longer than
> usual to boot up and a pause. Then, I noticed scary errors in dmesg:

...

> Am I reading correctly that my Quantum 15 GB IDE/PATA HDD is dying

Yes, she's dead Jim. You into necrophilia ?

[Ant]

> > Device Model: QUANTUM FIREBALLP LM15

> The poor thing is 11 years old. Take it out and give it a decent burial!

> You're running a quad core core 2 Q8200 CPU with a disk that old - it's like
> having a Ferrari with bike tyres :-)

I have so many old IDE HDDs. ;)
--
Quote of the Week: "A coconut shell full of water is a(n) sea/ocean to an ant." --Indians
/\___/\ Ant @ http://antfarm.home.dhs.org (Personal Web Site)

/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |

\ _ / Please nuke ANT if replying by e-mail. If crediting,
( ) then please kindly use Ant nickname and AQFL URL/link.

[Ant]

In comp.sys.ibm.pc.hardware.storage Ant <a...@zimage.comant> wrote:

> I woke up overnight (about six hours since I last used my computer
> without any problems) and noticed my old Debian/Linux box was acting
> weird (IRC chat bot/rbot gave errors about corrupted database, detached
> screen logged me out, could not log back in through SSH2 from a Windows
> box on LAN, Xscreensaver wouldn't let me back in locally (PAM errors),
> could not ctrl-alt-backspace on local PC, etc.). I did a hard reset to
> reboot. I went back to KDE v3.5.10, and noticed it took longer than
> usual to boot up and a pause. Then, I noticed scary errors in dmesg:

...

After about four hours, things were quiet/calm/stable after the
craziness. I noticed even both BIOS and CMOS would not find/autodetect
both or one of the HDDs either. Even idling in Debian/Linux could do it
too. I could not reproduce it in BIOS and CMOS. One time, BIOS saw the
HDDs, but said an error about SMART, but I didn't see anything in
smartctl? One of my hardware friends said if one drive goes crazy on the
IDE channel, it can affect both. Is that right/correct? Does it happen
with SATA drives too?

I am rerunning smartctl's long tests since things are quiet for now(?)
since earlier's long tests were during the craziness (not sure if they
even finished).

It's nice that Debian/Linux stops writing and makes my HDD read only if
too many errors. I wished Windows did that too if things get very bad.
--
Quote of the Week: "A coconut shell full of water is a(n) sea/ocean to an ant." --Indians
/\___/\ Ant @ http://antfarm.home.dhs.org (Personal Web Site)

/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |

\ _ / Please nuke ANT if replying by e-mail. If crediting,

( ) then please kindly use Ant nickname and AQFL URL/link.

[Ant]

Wait, is it both dead or just Quantum? I have seen both giving errors
and missing in CMOS, BIOS, and Linux/Debian.
--
Quote of the Week: "A coconut shell full of water is a(n) sea/ocean to an ant." --Indians
/\___/\ Ant @ http://antfarm.home.dhs.org (Personal Web Site)

/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |

\ _ / Please nuke ANT if replying by e-mail. If crediting,

( ) then please kindly use Ant nickname and AQFL URL/link.

[Ant]

> > I woke up overnight (about six hours since I last used my computer
> > without any problems) and noticed my old Debian/Linux box was acting
> > weird (IRC chat bot/rbot gave errors about corrupted database, detached
> > screen logged me out, could not log back in through SSH2 from a Windows
> > box on LAN, Xscreensaver wouldn't let me back in locally (PAM errors),
> > could not ctrl-alt-backspace on local PC, etc.). I did a hard reset to
> > reboot. I went back to KDE v3.5.10, and noticed it took longer than
> > usual to boot up and a pause. Then, I noticed scary errors in dmesg:
> ...

> After about four hours, things were quiet/calm/stable after the
> craziness. I noticed even both BIOS and CMOS would not find/autodetect
> both or one of the HDDs either. Even idling in Debian/Linux could do it
> too. I could not reproduce it in BIOS and CMOS. One time, BIOS saw the
> HDDs, but said an error about SMART, but I didn't see anything in
> smartctl? One of my hardware friends said if one drive goes crazy on the
> IDE channel, it can affect both. Is that right/correct? Does it happen
> with SATA drives too?

> I am rerunning smartctl's long tests since things are quiet for now(?)
> since earlier's long tests were during the craziness (not sure if they
> even finished).

> It's nice that Debian/Linux stops writing and makes my HDD read only if
> too many errors. I wished Windows did that too if things get very bad.

I forgot to mention that every BIOS' boot up to detect the drives, I
could hear a low beep/noise (doesn't sound like from my non-powered
audio speakers and PC speakers [heard this PC speaker's beep before the
drives]). This is easily 100% reproducable. Is that a sign of a dying
HDD?

[Ant]

> ... I am rerunning smartctl's long tests since things are quiet for

> now(?) since earlier's long tests were during the craziness (not sure

> if they even finished) ...

Here are the long test results (hope they finished on time based on
their ETAs), from smartctl:
http://pastie.org/private/pnz3vfteloml0mypqlkqa

[Richard Kettlewell]

Ant <a...@zimage.comANT> writes:

[Over 2000 lines snipped. Can't you post anything short??]

> Assuming my storage Quantum IDE/PATA drive is dying and I can't replace
> it right away, I guess I can live without it for a bit for now. I have
> three questions:
> 1. How do I tell Linux/Debian to enable write again without
> rebooting/restarting the computer?

AFAIK you cannot. If the disk is broken then it would not help anyway.

> 2. How can I tell Linux/Debian to stop using/ignore that drive or do I
> have to physically disconnect/unplug it? I am disabled and can't even
> open my PC case and reach inside so I am hoping I can just tell computer
> with commands or something. :(

Remove all references to it from /etc/fstab and reboot.

> 3. What's the best way to copy all the datas from this one to another
> HDD (have two old IDE/PATA HDDs in my drawer)? Is it still drescue or
> something like that command in KNOPPIX's boot liveCD? Or is there
> something better now since I last used was over five years or so.

If you still have a bootable system then just copy the contents with cp
-a or rsync. But this depends on the disk working at all, which it
evidently doesn't. Time to restore from backups.

--
http://www.greenend.org.uk/rjk/

[Ant]

> > Assuming my storage Quantum IDE/PATA drive is dying and I can't replace
> > it right away, I guess I can live without it for a bit for now. I have
> > three questions:
> > 1. How do I tell Linux/Debian to enable write again without
> > rebooting/restarting the computer?

> AFAIK you cannot. If the disk is broken then it would not help anyway.

Oh, you can't force it to be on again? :( Is that design by the HDD or
Linux?

> > 2. How can I tell Linux/Debian to stop using/ignore that drive or do I
> > have to physically disconnect/unplug it? I am disabled and can't even
> > open my PC case and reach inside so I am hoping I can just tell computer
> > with commands or something. :(

> Remove all references to it from /etc/fstab and reboot.

OK so I just add a # to rem/comment out
"UUID=e7405433-9fee-40e4-8736-dd26b9c6ed88 /storage ext3 defaults 0 2" line.
Can't I unmount without reboot?

> > 3. What's the best way to copy all the datas from this one to another
> > HDD (have two old IDE/PATA HDDs in my drawer)? Is it still drescue or
> > something like that command in KNOPPIX's boot liveCD? Or is there
> > something better now since I last used was over five years or so.

> If you still have a bootable system then just copy the contents with cp
> -a or rsync. But this depends on the disk working at all, which it
> evidently doesn't. Time to restore from backups.

Thanks. :)
--
Quote of the Week: "A coconut shell full of water is a(n) sea/ocean to an ant." --Indians
/\___/\ Ant @ http://antfarm.home.dhs.org (Personal Web Site)

/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |

\ _ / Please nuke ANT if replying by e-mail. If crediting,

( ) then please kindly use Ant nickname and AQFL URL/link.

[Pascal Hambourg]

Hello,

Ant a écrit :

>
> One of my hardware friends said if one drive goes crazy on the
> IDE channel, it can affect both. Is that right/correct?

Yes, as they are physically connected to each other on the same bus.

> Does it happen with SATA drives too?

Normally no, because each SATA device has its own physical bus.

[Ant]

Ah thanks. I thought maybe the ribbon cable was going bad or something.
That's news to me, but then I am not a hardware guy. :)

[Pascal Hambourg]

Ant a écrit :

>
> Ah thanks. I thought maybe the ribbon cable was going bad or something.

Maybe, if SMART does not show any error. Check the cable and connections.

[Richard Kettlewell]

ANT...@zimage.com (Ant) writes:

>>> Assuming my storage Quantum IDE/PATA drive is dying and I can't replace
>>> it right away, I guess I can live without it for a bit for now. I have
>>> three questions:
>>> 1. How do I tell Linux/Debian to enable write again without
>>> rebooting/restarting the computer?
>
>> AFAIK you cannot. If the disk is broken then it would not help anyway.
>
> Oh, you can't force it to be on again? :( Is that design by the HDD or
> Linux?

It's a property of Linux. There is code to disable the drive but as far
as I can see, none to re-enable it.

>>> 2. How can I tell Linux/Debian to stop using/ignore that drive or do I
>>> have to physically disconnect/unplug it? I am disabled and can't even
>>> open my PC case and reach inside so I am hoping I can just tell computer
>>> with commands or something. :(
>
>> Remove all references to it from /etc/fstab and reboot.
>
> OK so I just add a # to rem/comment out
> "UUID=e7405433-9fee-40e4-8736-dd26b9c6ed88 /storage ext3 defaults 0 2" line.
> Can't I unmount without reboot?

You can certainly try, but under the circumstances it may well fail.

--
http://www.greenend.org.uk/rjk/

[Ant]

> > Ah thanks. I thought maybe the ribbon cable was going bad or something.

> Maybe, if SMART does not show any error. Check the cable and connections.

Yeah maybe. Did my smartctl results show anything odd that I mentioned
earlier in my newsgroup/usenet thread posts?

[Ant]

> >>> Assuming my storage Quantum IDE/PATA drive is dying and I can't replace
> >>> it right away, I guess I can live without it for a bit for now. I have
> >>> three questions:
> >>> 1. How do I tell Linux/Debian to enable write again without
> >>> rebooting/restarting the computer?
> >
> >> AFAIK you cannot. If the disk is broken then it would not help anyway.
> >
> > Oh, you can't force it to be on again? :( Is that design by the HDD or
> > Linux?

> It's a property of Linux. There is code to disable the drive but as far
> as I can see, none to re-enable it.

Ah. I wonder why MS didn't implement this in Windows and DOS. It would
have been handy to keep data corruptions low.

> >>> 2. How can I tell Linux/Debian to stop using/ignore that drive or do I
> >>> have to physically disconnect/unplug it? I am disabled and can't even
> >>> open my PC case and reach inside so I am hoping I can just tell computer
> >>> with commands or something. :(
> >
> >> Remove all references to it from /etc/fstab and reboot.
> >
> > OK so I just add a # to rem/comment out
> > "UUID=e7405433-9fee-40e4-8736-dd26b9c6ed88 /storage ext3 defaults 0 2" line.
> > Can't I unmount without reboot?

> You can certainly try, but under the circumstances it may well fail.

Good point if my CMOS and BIOS failed to see the HDDs earlier.

[Rod Speed]

Ant wrote

>>> Device Model: QUANTUM FIREBALLP LM15

>> The poor thing is 11 years old. Take it out and give it a decent burial!

>> You're running a quad core core 2 Q8200 CPU with a
>> disk that old - it's like having a Ferrari with bike tyres :-)

> I have so many old IDE HDDs. ;)

And their replacements are so cheap that it makes no sense to do
anything but bin them when they waste your time so comprehensively.

They werent called a fireball for nuffin, stupid.

[Rod Speed]

Ant wrote:

>>> I woke up overnight (about six hours since I last used my computer
>>> without any problems) and noticed my old Debian/Linux box was acting
>>> weird (IRC chat bot/rbot gave errors about corrupted database,
>>> detached screen logged me out, could not log back in through SSH2
>>> from a Windows box on LAN, Xscreensaver wouldn't let me back in
>>> locally (PAM errors), could not ctrl-alt-backspace on local PC,
>>> etc.). I did a hard reset to
>>> reboot. I went back to KDE v3.5.10, and noticed it took longer than
>>> usual to boot up and a pause. Then, I noticed scary errors in dmesg:
>> ...
>>> Am I reading correctly that my Quantum 15 GB IDE/PATA HDD is dying

>> Yes, she's dead Jim. You into necrophilia ?

> Wait,

No way, we aint stopping for anyone, and dont you forget it.

> is it both dead

Que ?

> or just Quantum? I have seen both giving errors
> and missing in CMOS, BIOS, and Linux/Debian.

Yeah, you can get that that effect with IDEs/PATAs even when its just a bad cable.

[Pascal Hambourg]

Ant a ï¿œcrit :

>
> Did my smartctl results show anything odd that I mentioned
> earlier in my newsgroup/usenet thread posts?

I didn't see anything odd, but I am not an expert.

[Rod Speed]

Ant wrote:
> Ant <a...@zimage.comant> wrote

You'll end up completely blind if you dont watch out, boy.

>> I woke up overnight (about six hours since I last used my computer
>> without any problems) and noticed my old Debian/Linux box was acting
>> weird (IRC chat bot/rbot gave errors about corrupted database,
>> detached screen logged me out, could not log back in through SSH2
>> from a Windows box on LAN, Xscreensaver wouldn't let me back in
>> locally (PAM errors), could not ctrl-alt-backspace on local PC,
>> etc.). I did a hard reset to reboot. I went back to KDE v3.5.10, and
>> noticed it took longer than usual to boot up and a pause. Then, I
>> noticed scary errors in dmesg: ...

> After about four hours, things were quiet/calm/stable after the
> craziness. I noticed even both BIOS and CMOS would not find/autodetect
> both or one of the HDDs either. Even idling in Debian/Linux could do it too.
> I could not reproduce it in BIOS and CMOS.

Could even be just a bad cable or the connector loose or bad
power connectors to the drives or even a failing power supply too.

You can resolve that by diagnosing it systematically, by trying
a new ribbon cable first, then a spare power supply etc.

> One time, BIOS saw the HDDs, but said an error
> about SMART, but I didn't see anything in smartctl?

Yes you did with the report you posted.

> One of my hardware friends said if one drive goes crazy on
> the IDE channel, it can affect both. Is that right/correct?

Yes, and you can get that effect with a controller
going bad and even a cable going bad too.

> Does it happen with SATA drives too?

Nope, because they dont share a cable.

> I am rerunning smartctl's long tests since things are quiet for now(?)
> since earlier's long tests were during the craziness (not sure if they
> even finished).

> It's nice that Debian/Linux stops writing and makes my HDD read only
> if too many errors. I wished Windows did that too if things get very bad.

It isnt practical when there is only one drive.

[Rod Speed]

Ant wrote

Thats the bios swearing at you for making it use such a dinosaur of a hard drive.

> This is easily 100% reproducable. Is that a sign of a dying HDD?

A few drives do beep when they are dying, pretty sure the fireball did beep, but its been too long now.

You'd have to check where the beeps are coming from with the drive loose on the desktop to be sure.

[Rod Speed]

Ant wrote:

>>>>> Assuming my storage Quantum IDE/PATA drive is dying and I can't
>>>>> replace it right away, I guess I can live without it for a bit
>>>>> for now. I have three questions:

>>>>> 1. How do I tell Linux/Debian to enable write again without
>>>>> rebooting/restarting the computer?

>>>> AFAIK you cannot. If the disk is broken then it would not help anyway.

>>> Oh, you can't force it to be on again? :( Is that design by the HDD or Linux?

>> It's a property of Linux. There is code to disable the drive but as
>> far as I can see, none to re-enable it.

> Ah. I wonder why MS didn't implement this in Windows and DOS.

Its just not practical with single drive systems and most Win and dos systems only have one drive.

Win does turn DMA off if it sees too many errors on the cable.

> It would have been handy to keep data corruptions low.

Not with single drive systems. Win normally swaps to the system drive
and you cant stop that from happening by making the drive read only.

[Charlie Gibbs]

In article <Fr-dnYNCutToSKDQ...@earthlink.com>,
ANT...@zimage.com (Ant) writes:

>>> Am I reading correctly that my Quantum 15 GB IDE/PATA HDD is dying
>>
>> Yes, she's dead Jim. You into necrophilia ?
>
> Wait, is it both dead or just Quantum?

Is it live or is it Memorex?

--
/~\ cgi...@kltpzyxm.invalid (Charlie Gibbs)
\ / I'm really at ac.dekanfrus if you read it the right way.
X Top-posted messages will probably be ignored. See RFC1855.
/ \ HTML will DEFINITELY be ignored. Join the ASCII ribbon campaign!

[Charlie Gibbs]

In article <J8ednfeDOcRVfqDQ...@earthlink.com>,
ANT...@zimage.com (Ant) writes:

>> It's a property of Linux. There is code to disable the drive but as
>> far as I can see, none to re-enable it.
>
> Ah. I wonder why MS didn't implement this in Windows and DOS. It would
> have been handy to keep data corruptions low.

They tried. But the way their file system keeps corrupting things,
it kept shutting down the system, so they had to take it out again.

[Ant]

In alt.comp.periphs.hdd Rod Speed <rod.sp...@gmail.com> wrote:
> Ant wrote

> >>> Device Model: QUANTUM FIREBALLP LM15

> >> The poor thing is 11 years old. Take it out and give it a decent burial!

> >> You're running a quad core core 2 Q8200 CPU with a
> >> disk that old - it's like having a Ferrari with bike tyres :-)

> > I have so many old IDE HDDs. ;)

> And their replacements are so cheap that it makes no sense to do
> anything but bin them when they waste your time so comprehensively.

Bah, I don't want to waste them. I will get new ones when motherboards
don't use IDE/PATA anymore or I don't have any left.

> They werent called a fireball for nuffin, stupid.

Only one Quantum Firewall. :P

[Ant]

> > or just Quantum? I have seen both giving errors
> > and missing in CMOS, BIOS, and Linux/Debian.

> Yeah, you can get that that effect with IDEs/PATAs even when its just a bad cable.

Interesting. What happens when it is a bad cable? What symptoms and
errors?

[Ant]

> >>> Am I reading correctly that my Quantum 15 GB IDE/PATA HDD is dying
> >>
> >> Yes, she's dead Jim. You into necrophilia ?
> >
> > Wait, is it both dead or just Quantum?

> Is it live or is it Memorex?

Memorex brand? Eh?

[Ant]

Bah. If it was swearing, then how it didn't complain in the past like
last month? :P

> > This is easily 100% reproducable. Is that a sign of a dying HDD?

> A few drives do beep when they are dying, pretty sure the fireball did
> beep, but its been too long now.

Interesting. I have never knew they do that. How come newer/modern HDDs
don't do that?

> You'd have to check where the beeps are coming from with the drive
> loose on the desktop to be sure.

OK.

[Ant]

> > Did my smartctl results show anything odd that I mentioned
> > earlier in my newsgroup/usenet thread posts?

> I didn't see anything odd, but I am not an expert.

OK and thanks. :)

[Ant]

In alt.comp.periphs.hdd Rod Speed <rod.sp...@gmail.com> wrote:

> Ant wrote:
> > Ant <a...@zimage.comant> wrote

> You'll end up completely blind if you dont watch out, boy.

Eh?

> >> I woke up overnight (about six hours since I last used my computer
> >> without any problems) and noticed my old Debian/Linux box was acting
> >> weird (IRC chat bot/rbot gave errors about corrupted database,
> >> detached screen logged me out, could not log back in through SSH2
> >> from a Windows box on LAN, Xscreensaver wouldn't let me back in
> >> locally (PAM errors), could not ctrl-alt-backspace on local PC,
> >> etc.). I did a hard reset to reboot. I went back to KDE v3.5.10, and
> >> noticed it took longer than usual to boot up and a pause. Then, I
> >> noticed scary errors in dmesg: ...

> > After about four hours, things were quiet/calm/stable after the
> > craziness. I noticed even both BIOS and CMOS would not find/autodetect
> > both or one of the HDDs either. Even idling in Debian/Linux could do it too.
> > I could not reproduce it in BIOS and CMOS.

> Could even be just a bad cable or the connector loose or bad
> power connectors to the drives or even a failing power supply too.

Hmm, my old 650 watts SeaSonic PSU failing? Hmm. That could be.
Shouldn't other hardwares be failing too or showing symptoms? I did try
hitting on my case to see if there was anything loose (can't open my PC
case due to my disabilities). Still no errors from that.

I wonder if my computer was too hot? it was about 80F degrees in my room
and CMOS' sensors show 100+F degrees. I wished these old HDDs showed
their temperatures.

> You can resolve that by diagnosing it systematically, by trying
> a new ribbon cable first, then a spare power supply etc.

OK. I still haven't seen the issue come back. Weird stuff!

> > One time, BIOS saw the HDDs, but said an error
> > about SMART, but I didn't see anything in smartctl?

> Yes you did with the report you posted.

Uhh, which one? The lines with interrupted?

> > One of my hardware friends said if one drive goes crazy on
> > the IDE channel, it can affect both. Is that right/correct?

> Yes, and you can get that effect with a controller
> going bad and even a cable going bad too.

Hmm. Now, I need to figure if it is the drive, cables, controller, or
PSU. Ugh.

> > Does it happen with SATA drives too?

> Nope, because they dont share a cable.

OK.

> > I am rerunning smartctl's long tests since things are quiet for now(?)
> > since earlier's long tests were during the craziness (not sure if they
> > even finished).

> > It's nice that Debian/Linux stops writing and makes my HDD read only
> > if too many errors. I wished Windows did that too if things get very bad.

> It isnt practical when there is only one drive.

Uh, why? Wouldn't still make sense for the software to stop writing to
avoid more data losses/corruptions from too many errors?

[Ant]

> >>>>> 1. How do I tell Linux/Debian to enable write again without
> >>>>> rebooting/restarting the computer?

> >>>> AFAIK you cannot. If the disk is broken then it would not help anyway.

> >>> Oh, you can't force it to be on again? :( Is that design by the HDD or Linux?

> >> It's a property of Linux. There is code to disable the drive but as
> >> far as I can see, none to re-enable it.

> > Ah. I wonder why MS didn't implement this in Windows and DOS.

> Its just not practical with single drive systems and most Win and dos systems only have one drive.

> Win does turn DMA off if it sees too many errors on the cable.

> > It would have been handy to keep data corruptions low.

> Not with single drive systems. Win normally swaps to the system drive
> and you cant stop that from happening by making the drive read only.

Ah. Interesting. So if Debian/Linux had one drive, it would not put in
read only either like Windows? I noticed both drives went read only
when things went crazy.

[Ant]

> >> It's a property of Linux. There is code to disable the drive but as
> >> far as I can see, none to re-enable it.
> >
> > Ah. I wonder why MS didn't implement this in Windows and DOS. It would
> > have been handy to keep data corruptions low.

> They tried. But the way their file system keeps corrupting things,
> it kept shutting down the system, so they had to take it out again.

Hahaha. That's funny when Linux does it fine. Is it because of their
file systems/FS' compared to EXT3 which I am using?

[Arno]

From the absence of any disk problem visible in the SMART data,
I would conclude that your disk controller is dying, not the disks.

Could also be a random bug that put the disk controller/disk in
an inconsistent state. I have that about once a year in my
fileserver, although I think I have tracked it down to yet
another bad ASUS mainboard. ASUS engineering has sucked badly
for the last few years.

In comp.sys.ibm.pc.hardware.storage Ant <a...@zimage.comant> wrote:
> Hello.

> I woke up overnight (about six hours since I last used my computer
> without any problems) and noticed my old Debian/Linux box was acting
> weird (IRC chat bot/rbot gave errors about corrupted database, detached
> screen logged me out, could not log back in through SSH2 from a Windows
> box on LAN, Xscreensaver wouldn't let me back in locally (PAM errors),
> could not ctrl-alt-backspace on local PC, etc.). I did a hard reset to
> reboot. I went back to KDE v3.5.10, and noticed it took longer than
> usual to boot up and a pause. Then, I noticed scary errors in dmesg:

[...]
> Am I reading correctly that my Quantum 15 GB IDE/PATA HDD is dying since
> it can't seem to connect to it and stuff? Or is it somethign else?

I suspedt the controller. Did a power-cycle fix things?

> Assuming my storage Quantum IDE/PATA drive is dying and I can't replace
> it right away, I guess I can live without it for a bit for now. I have
> three questions:

> 1. How do I tell Linux/Debian to enable write again without
> rebooting/restarting the computer?

Basically you cannot. Especially if the controller or disk is
sort-of crashed.

> 2. How can I tell Linux/Debian to stop using/ignore that drive or do I
> have to physically disconnect/unplug it? I am disabled and can't even
> open my PC case and reach inside so I am hoping I can just tell computer
> with commands or something. :(

For SATA this would be easer, there are drive removal scripts.
For ATA, maybe you can send it to sleep woth hdparm. But I
am not sure.

> 3. What's the best way to copy all the datas from this one to another
> HDD (have two old IDE/PATA HDDs in my drawer)? Is it still drescue or
> something like that command in KNOPPIX's boot liveCD? Or is there
> something better now since I last used was over five years or so.

If the drive is inaccessible, then nothing software-only will
help. If this is indeed just an inconsistent state, try a reboot
and then copy with the copy utility of your choice (cp, tar, etc.)

Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: ar...@wagner.name
GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans

[Rod Speed]

Ant wrote

> Rod Speed <rod.sp...@gmail.com> wrote
>> Ant wrote

>>>>> Device Model: QUANTUM FIREBALLP LM15

>>>> The poor thing is 11 years old. Take it out and give it a decent burial!

>>>> You're running a quad core core 2 Q8200 CPU with a
>>>> disk that old - it's like having a Ferrari with bike tyres :-)

>>> I have so many old IDE HDDs. ;)

>> And their replacements are so cheap that it makes no sense to do
>> anything but bin them when they waste your time so comprehensively.

> Bah, I don't want to waste them.

I prefer to not waste my time instead. Much more important to me than some dinosaur drive.

> I will get new ones when motherboards don't use IDE/PATA anymore

You wont have to stop using them then, SATA/IDE adapters cost peanuts.

> or I don't have any left.

More fool you.

>> They werent called a fireball for nuffin, stupid.

> Only one Quantum Firewall. :P

It only takes one to kill you. Remember, you cant run away |-(

[Rod Speed]

Ant wrote:

>>> or just Quantum? I have seen both giving errors
>>> and missing in CMOS, BIOS, and Linux/Debian.

>> Yeah, you can get that that effect with IDEs/PATAs even when its just a bad cable.

> Interesting. What happens when it is a bad cable? What symptoms and errors?

Varys with where the fault is. It can be anything from the drives disappearing
to lots of errors to all sorts of other symptoms. They can be surprisingly diverse.

[Rod Speed]

Ant wrote:

> Bah.

Thats not very nice.

> If it was swearing,

No if about it. Its swearing at you in morse code, you just cant read morse.

> then how it didn't complain in the past like last month? :P

It did, you just didnt even notice. So it fucked over the drive to get your attention.

>>> This is easily 100% reproducable. Is that a sign of a dying HDD?

>> A few drives do beep when they are dying, pretty sure
>> the fireball did beep, but its been too long now.

> Interesting. I have never knew they do that.
> How come newer/modern HDDs don't do that?

They moved on to more sophisticated ways of telling
the system that there is a problem like with SMART.

[Rod Speed]

Ant wrote

> Rod Speed <rod.sp...@gmail.com> wrote
>> Ant wrote:
>>> Ant <a...@zimage.comant> wrote

>> You'll end up completely blind if you dont watch out, boy.

> Eh?

That was a joke, Joyce. You were clearly having it off with yourself, again.

Dont laugh, see if I care. I'll just have quiet cry here by myself where you cant see me.

>>>> I woke up overnight (about six hours since I last used my computer
>>>> without any problems) and noticed my old Debian/Linux box was
>>>> acting weird (IRC chat bot/rbot gave errors about corrupted
>>>> database, detached screen logged me out, could not log back in
>>>> through SSH2 from a Windows box on LAN, Xscreensaver wouldn't let
>>>> me back in locally (PAM errors), could not ctrl-alt-backspace on
>>>> local PC, etc.). I did a hard reset to reboot. I went back to KDE
>>>> v3.5.10, and noticed it took longer than usual to boot up and a
>>>> pause. Then, I noticed scary errors in dmesg: ...

>>> After about four hours, things were quiet/calm/stable after the craziness.
>>> I noticed even both BIOS and CMOS would not find/autodetect
>>> both or one of the HDDs either. Even idling in Debian/Linux could
>>> do it too. I could not reproduce it in BIOS and CMOS.

>> Could even be just a bad cable or the connector loose or bad
>> power connectors to the drives or even a failing power supply too.

> Hmm, my old 650 watts SeaSonic PSU failing? Hmm.

Everything can fail, even the case.

> That could be. Shouldn't other hardwares be failing too or showing symptoms?

Not necessarily, there is usually something that shows symptoms first when
the rail sags, or when there is a lot more noise on the rail than there should be.

> I did try hitting on my case to see if there was anything loose

You're sposed to take to it with the largest waddy you can find.
http://en.wiktionary.org/wiki/waddy

> (can't open my PC case due to my disabilities).

Guess you'd have a problem with a waddy too then.

> Still no errors from that.

> I wonder if my computer was too hot?

Yes, you can get symptoms like that if its too hot.

> it was about 80F degrees in my room and CMOS' sensors show 100+F degrees.

Thats not too bad tho.

> I wished these old HDDs showed their temperatures.

Yeah, thats just one of their deficiencys.

>> You can resolve that by diagnosing it systematically, by trying
>> a new ribbon cable first, then a spare power supply etc.

> OK. I still haven't seen the issue come back. Weird stuff!

Thats not that uncommon with a bad cable, connector not plugged in properly or a failing power supply.

Hard to diagnose when its intermittent tho.

>>> One time, BIOS saw the HDDs, but said an error
>>> about SMART, but I didn't see anything in smartctl?

>> Yes you did with the report you posted.

> Uhh, which one? The lines with interrupted?

>>> One of my hardware friends said if one drive goes crazy on
>>> the IDE channel, it can affect both. Is that right/correct?

>> Yes, and you can get that effect with a controller
>> going bad and even a cable going bad too.

> Hmm. Now, I need to figure if it is the drive, cables, controller, or PSU. Ugh.

Yeah, and intermittent makes it even harder.

Particularly when its not easy to change the cable and power supply.

>>> Does it happen with SATA drives too?

>> Nope, because they dont share a cable.

> OK.

>>> I am rerunning smartctl's long tests since things are quiet for
>>> now(?) since earlier's long tests were during the craziness (not
>>> sure if they even finished).

>>> It's nice that Debian/Linux stops writing and makes my HDD read only
>>> if too many errors. I wished Windows did that too if things get very bad.

>> It isnt practical when there is only one drive.

> Uh, why?

Because Win uses the swap file extensively and there is no place to write the log to either.

> Wouldn't still make sense for the software to stop writing to
> avoid more data losses/corruptions from too many errors?

You dont normally see much data loss/corruption. It can happen, but
the system will just stop completely when it cant write to the swap file.

When things get bad, the BSOD does stop everything completely.

[Rod Speed]

>>>>>>> 1. How do I tell Linux/Debian to enable write
>>>>>>> again without rebooting/restarting the computer?

>>>>>> AFAIK you cannot. If the disk is broken then it would not help anyway.

>>>>> Oh, you can't force it to be on again? :( Is that design by the HDD or Linux?

>>>> It's a property of Linux. There is code to disable the drive but
>>>> as far as I can see, none to re-enable it.

>>> Ah. I wonder why MS didn't implement this in Windows and DOS.

>> Its just not practical with single drive systems and most Win and
>> dos systems only have one drive.

>> Win does turn DMA off if it sees too many errors on the cable.

>>> It would have been handy to keep data corruptions low.

>> Not with single drive systems. Win normally swaps to the system drive
>> and you cant stop that from happening by making the drive read only.

> Ah. Interesting. So if Debian/Linux had one drive,
> it would not put in read only either like Windows?

Dunno, I dont use it enough like that to be sure, have a look at the code.

> I noticed both drives went read only when things went crazy.

They cant have both been completely read only otherwise you wouldnt have had the log.

[Rod Speed]

>>>> It's a property of Linux. There is code to disable
>>>> the drive but as far as I can see, none to re-enable it.

>>> Ah. I wonder why MS didn't implement this in Windows and DOS.
>>> It would have been handy to keep data corruptions low.

>> They tried.

Thats a lie.

>> But the way their file system keeps corrupting
>> things, it kept shutting down the system,

Another lie.

>> so they had to take it out again.

> Hahaha. That's funny when Linux does it fine. Is it because
> of their file systems/FS' compared to EXT3 which I am using?

Nope, he lied about file system corruption.

[Ant]

Interesting. I will tell Debian to unmount the drive (sdb) after doing a
backup of it in case it is going bad. However, I have had any new
incidents since yesterday morning. Weird.

[Ant]

> >>> This is easily 100% reproducable. Is that a sign of a dying HDD?

> >> A few drives do beep when they are dying, pretty sure
> >> the fireball did beep, but its been too long now.

> > Interesting. I have never knew they do that.
> > How come newer/modern HDDs don't do that?

> They moved on to more sophisticated ways of telling
> the system that there is a problem like with SMART.

> >> You'd have to check where the beeps are coming
> >> from with the drive loose on the desktop to be sure.

> > OK.

Hmm, I will have to figure out which drive is making that noise. It is
probably from hda/Seagate HDD since its smartctl results shows:
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 43207 -
# 2 Extended offline Interrupted (host reset) 90% 43201 -
# 3 Extended offline Completed without error 00% 39844 -
# 4 Extended offline Interrupted (host reset) 20% 38502 -
...

Or maybe those interrupted errors were doing the long tests I manaually
ran when both of my HDDs went crazy?

[Ant]

> > That could be. Shouldn't other hardwares be failing too or showing symptoms?

> Not necessarily, there is usually something that shows symptoms first when
> the rail sags, or when there is a lot more noise on the rail than there should be.

> > I did try hitting on my case to see if there was anything loose

> You're sposed to take to it with the largest waddy you can find.
> http://en.wiktionary.org/wiki/waddy

Ah, it looks like one of those stone age clubs.

> > (can't open my PC case due to my disabilities).

> Guess you'd have a problem with a waddy too then.

More like I don't have one. :) I have a hammer though. [grin]

> > Still no errors from that.

> > I wonder if my computer was too hot?

> Yes, you can get symptoms like that if its too hot.

So 80F degrees room temperature and 100F degrees inside from motherboard
is hot? Geez, I don't want to know how bad they will be in the heat
waves when my room temperatures go over 85F degrees. :(

> > it was about 80F degrees in my room and CMOS' sensors show 100+F degrees.

> Thats not too bad tho.

Oh.

> > I wished these old HDDs showed their temperatures.

> Yeah, thats just one of their deficiencys.

> >> You can resolve that by diagnosing it systematically, by trying
> >> a new ribbon cable first, then a spare power supply etc.

> > OK. I still haven't seen the issue come back. Weird stuff!

> Thats not that uncommon with a bad cable, connector not plugged in
> properly or a failing power supply.

> Hard to diagnose when its intermittent tho.

Yeah, I was hoping it would come back so I can try more stuff with it.
Ugh! I want to try unmounting/disabling that HDD in Debian to see if it
still will go crazy.

> >>> One time, BIOS saw the HDDs, but said an error
> >>> about SMART, but I didn't see anything in smartctl?

> >> Yes you did with the report you posted.

> > Uhh, which one? The lines with interrupted?

> >>> One of my hardware friends said if one drive goes crazy on
> >>> the IDE channel, it can affect both. Is that right/correct?

> >> Yes, and you can get that effect with a controller
> >> going bad and even a cable going bad too.

> > Hmm. Now, I need to figure if it is the drive, cables, controller, or PSU. Ugh.

> Yeah, and intermittent makes it even harder.

> Particularly when its not easy to change the cable and power supply.

Yep.

> >>> It's nice that Debian/Linux stops writing and makes my HDD read only
> >>> if too many errors. I wished Windows did that too if things get very bad.

> >> It isnt practical when there is only one drive.

> > Uh, why?

> Because Win uses the swap file extensively and there is no place to
> write the log to either.

Interesting. Then, where is Debian writing its log? I don't see it after
it sets all my HDDs to read only. I can't even run basic commands. Hah.

> > Wouldn't still make sense for the software to stop writing to
> > avoid more data losses/corruptions from too many errors?

> You dont normally see much data loss/corruption. It can happen, but
> the system will just stop completely when it cant write to the swap file.

> When things get bad, the BSOD does stop everything completely.

Which errors would those be? I have had seen Windows given me those
balloon errors about HDD's SMART sensor results.

[Ant]

> >>> It would have been handy to keep data corruptions low.

> >> Not with single drive systems. Win normally swaps to the system drive
> >> and you cant stop that from happening by making the drive read only.

> > Ah. Interesting. So if Debian/Linux had one drive,
> > it would not put in read only either like Windows?

> Dunno, I dont use it enough like that to be sure, have a look at the code.

> > I noticed both drives went read only when things went crazy.

> They cant have both been completely read only otherwise you wouldnt have had the log.

I think the written logs were before Debian/Linux decided to make HDDs
read only. There seems to be limits on how many problems before saying
enough is enough.

[Ant]

In alt.comp.periphs.hdd Arno <m...@privacy.net> wrote:
> From the absence of any disk problem visible in the SMART data,
> I would conclude that your disk controller is dying, not the disks.

Are you referring to the disk controller on my HDDs or on my 2+ years
old motherboard with the latest firmware/BIOS?

> Could also be a random bug that put the disk controller/disk in
> an inconsistent state. I have that about once a year in my
> fileserver, although I think I have tracked it down to yet
> another bad ASUS mainboard. ASUS engineering has sucked badly
> for the last few years.

Ah, MSI for this motherboard. Ugh.

> In comp.sys.ibm.pc.hardware.storage Ant <a...@zimage.comant> wrote:
> > Hello.

> > I woke up overnight (about six hours since I last used my computer
> > without any problems) and noticed my old Debian/Linux box was acting
> > weird (IRC chat bot/rbot gave errors about corrupted database, detached
> > screen logged me out, could not log back in through SSH2 from a Windows
> > box on LAN, Xscreensaver wouldn't let me back in locally (PAM errors),
> > could not ctrl-alt-backspace on local PC, etc.). I did a hard reset to
> > reboot. I went back to KDE v3.5.10, and noticed it took longer than
> > usual to boot up and a pause. Then, I noticed scary errors in dmesg:
> [...]
> > Am I reading correctly that my Quantum 15 GB IDE/PATA HDD is dying since
> > it can't seem to connect to it and stuff? Or is it somethign else?

> I suspedt the controller. Did a power-cycle fix things?

No at first. :( Then, they started working after idling in BIOS and
CMOS. I did notice before things calmed down, BIOS and CMOS could not
find one or both my HDDs. It was freaky.

> > Assuming my storage Quantum IDE/PATA drive is dying and I can't replace
> > it right away, I guess I can live without it for a bit for now. I have
> > three questions:
> > 1. How do I tell Linux/Debian to enable write again without
> > rebooting/restarting the computer?

> Basically you cannot. Especially if the controller or disk is
> sort-of crashed.

Ah, the hardware crashed. I thought Debian/Linux disabled the write
access.

> > 2. How can I tell Linux/Debian to stop using/ignore that drive or do I
> > have to physically disconnect/unplug it? I am disabled and can't even
> > open my PC case and reach inside so I am hoping I can just tell computer
> > with commands or something. :(

> For SATA this would be easer, there are drive removal scripts.
> For ATA, maybe you can send it to sleep woth hdparm. But I
> am not sure.

I think I can unmount it and tell fstab not to mount it during
Debioan's boot up?

> > 3. What's the best way to copy all the datas from this one to another
> > HDD (have two old IDE/PATA HDDs in my drawer)? Is it still drescue or
> > something like that command in KNOPPIX's boot liveCD? Or is there
> > something better now since I last used was over five years or so.

> If the drive is inaccessible, then nothing software-only will
> help. If this is indeed just an inconsistent state, try a reboot
> and then copy with the copy utility of your choice (cp, tar, etc.)

Well, it is working NOW for who knows how long.

[Ant]

> > > I woke up overnight (about six hours since I last used my computer
> > > without any problems) and noticed my old Debian/Linux box was acting
> > > weird (IRC chat bot/rbot gave errors about corrupted database, detached
> > > screen logged me out, could not log back in through SSH2 from a Windows
> > > box on LAN, Xscreensaver wouldn't let me back in locally (PAM errors),
> > > could not ctrl-alt-backspace on local PC, etc.). I did a hard reset to
> > > reboot. I went back to KDE v3.5.10, and noticed it took longer than
> > > usual to boot up and a pause. Then, I noticed scary errors in dmesg:
> > [...]
> > > Am I reading correctly that my Quantum 15 GB IDE/PATA HDD is dying since
> > > it can't seem to connect to it and stuff? Or is it somethign else?

> > I suspedt the controller. Did a power-cycle fix things?

> No at first. :( Then, they started working after idling in BIOS and
> CMOS. I did notice before things calmed down, BIOS and CMOS could not
> find one or both my HDDs. It was freaky.

Now to think about it. I think I used the reset button to reboot
since my PC was not responding and I couldn't send a shutdown
command, and not actually power off and on. I think I did the shut down
off and on later on before things settled down. Does reset button not
reset the crashed hardwares?

[Trevor Hemsley]

On Tue, 25 Jan 2011 02:07:36 UTC in comp.os.linux.hardware, ANT...@zimage.com
(Ant) wrote:

> > And their replacements are so cheap that it makes no sense to do
> > anything but bin them when they waste your time so comprehensively.
>
> Bah, I don't want to waste them. I will get new ones when motherboards
> don't use IDE/PATA anymore or I don't have any left.

But it's false economy. That drive is 11 years old and the only benchmark I
could find for it said it pulled a maximum of 23MB/s on sequential reads. The
cheapest drive (£30) I can find on my local etailer is a Seagate ST3320418AS and
the sequential transfer rate on that is 114MB/s. It's also native SATA and
supports NCQ - not to mention having 21 times as much space and being ~5 times
as fast. At the moment a drive like that Fireball in a machine like yours is
most likely the biggest bottleneck you have.

--
Trevor Hemsley, Brighton, UK
Trevor dot Hemsley at ntlworld dot com

[Rod Speed]

Ant <ANT...@zimage.com> wrote

>>>>> This is easily 100% reproducable. Is that a sign of a dying HDD?

>>>> A few drives do beep when they are dying, pretty sure
>>>> the fireball did beep, but its been too long now.

>>> Interesting. I have never knew they do that.
>>> How come newer/modern HDDs don't do that?

>> They moved on to more sophisticated ways of telling
>> the system that there is a problem like with SMART.

>>>> You'd have to check where the beeps are coming
>>>> from with the drive loose on the desktop to be sure.

>>> OK.

> Hmm, I will have to figure out which drive is making that noise.

Yes, and the best way to do that is to have the drive loose on the desktop.

Unfortunately that isnt that easy for you to do personally.

> It is probably from hda/Seagate HDD

Dunno, I dont believe the Barracudas ever did beep.

You sure its a real beep and not just the drive recalibrating ?

> since its smartctl results shows:
> SMART Self-test log structure revision number 1
> Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
> # 1 Extended offline Completed without error 00% 43207 -
> # 2 Extended offline Interrupted (host reset) 90% 43201 -
> # 3 Extended offline Completed without error 00% 39844 -
> # 4 Extended offline Interrupted (host reset) 20% 38502 -

I've never like smartctl, it isnt at all clear what its actually saying there.

> Or maybe those interrupted errors were doing the long tests
> I manaually ran when both of my HDDs went crazy?

Probably.

> Quote of the Week: "A coconut shell full of water is a(n) sea/ocean to an ant." --Indians

Nope, just a pond at most. And Red Indians never had coconuts anyway.

[Rod Speed]

Ant wrote

>>> That could be. Shouldn't other hardwares be failing too or showing symptoms?

>> Not necessarily, there is usually something that shows symptoms first when
>> the rail sags, or when there is a lot more noise on the rail than there should be.

>>> I did try hitting on my case to see if there was anything loose

>> You're sposed to take to it with the largest waddy you can find.
>> http://en.wiktionary.org/wiki/waddy

> Ah, it looks like one of those stone age clubs.

Yeah, they never made it out of the stone age till the white man showed up.

They didnt even manage to invent clothes or houses
in a place like Tasmania which can be frigid in winter.

>>> (can't open my PC case due to my disabilities).

>> Guess you'd have a problem with a waddy too then.

> More like I don't have one. :)

They're easy enough to make.

> I have a hammer though. [grin]

You need something like a sledge hammer, not just a normal carpenters hammer.

What bricklayers call a mash hammer would be fine.

>>> Still no errors from that.

>>> I wonder if my computer was too hot?

>> Yes, you can get symptoms like that if its too hot.

> So 80F degrees room temperature and 100F degrees inside from motherboard is hot?

Nope, like I said below, thats not too bad at all.

> Geez, I don't want to know how bad they will be in the heat
> waves when my room temperatures go over 85F degrees. :(

>>> it was about 80F degrees in my room and CMOS' sensors show 100+F degrees.

>> Thats not too bad tho.

> Oh.

>>> I wished these old HDDs showed their temperatures.

>> Yeah, thats just one of their deficiencys.

>>>> You can resolve that by diagnosing it systematically, by trying
>>>> a new ribbon cable first, then a spare power supply etc.

>>> OK. I still haven't seen the issue come back. Weird stuff!

>> Thats not that uncommon with a bad cable, connector
>> not plugged in properly or a failing power supply.

>> Hard to diagnose when its intermittent tho.

> Yeah, I was hoping it would come back so I can try more stuff with it.
> Ugh! I want to try unmounting/disabling that HDD in Debian to see if it
> still will go crazy.

Its illegal to mount your hard drive, you depraved person you.

Stick to sheep.

>>>>> One time, BIOS saw the HDDs, but said an error
>>>>> about SMART, but I didn't see anything in smartctl?

>>>> Yes you did with the report you posted.

>>> Uhh, which one? The lines with interrupted?

>>>>> One of my hardware friends said if one drive goes crazy
>>>>> on the IDE channel, it can affect both. Is that right/correct?

>>>> Yes, and you can get that effect with a controller
>>>> going bad and even a cable going bad too.

>>> Hmm. Now, I need to figure if it is the drive, cables, controller, or PSU. Ugh.

>> Yeah, and intermittent makes it even harder.

>> Particularly when its not easy to change the cable and power supply.

> Yep.

>>>>> It's nice that Debian/Linux stops writing and makes my HDD read only
>>>>> if too many errors. I wished Windows did that too if things get very bad.

>>>> It isnt practical when there is only one drive.

>>> Uh, why?

>> Because Win uses the swap file extensively and there is no place to write the log to either.

> Interesting. Then, where is Debian writing its log?

Presumably it isnt read only for itself.

> I don't see it after it sets all my HDDs to read only.
> I can't even run basic commands. Hah.

>>> Wouldn't still make sense for the software to stop writing to
>>> avoid more data losses/corruptions from too many errors?

>> You dont normally see much data loss/corruption. It can happen, but
>> the system will just stop completely when it cant write to the swap file.

>> When things get bad, the BSOD does stop everything completely.

> Which errors would those be?

Almost anything can produce a BSOD with Win.

> I have had seen Windows given me those balloon errors about HDD's SMART sensor results.

BSODs are Blue Screen of Death.

[Rod Speed]

>>>>> It would have been handy to keep data corruptions low.

>>>> Not with single drive systems. Win normally swaps to the system drive
>>>> and you cant stop that from happening by making the drive read only.

>>> Ah. Interesting. So if Debian/Linux had one drive,
>>> it would not put in read only either like Windows?

>> Dunno, I dont use it enough like that to be sure, have a look at the code.

>>> I noticed both drives went read only when things went crazy.

>> They cant have both been completely read only otherwise you wouldnt have had the log.

> I think the written logs were before Debian/Linux decided to make HDDs read only.

Cant be, those werent the last lines in the log.

> There seems to be limits on how many problems before saying enough is enough.

Sure, it wouldnt be useable if any error like a CRC error saw the drive marked read only.

[Rod Speed]

Ant wrote
> Arno <m...@privacy.net> wrote

>> From the absence of any disk problem visible in the SMART data,
>> I would conclude that your disk controller is dying, not the disks.

> Are you referring to the disk controller on my HDDs

Nope. Thats called a logic card.

> or on my 2+ years old motherboard with the latest firmware/BIOS?

Yep.

Until its going to cause you the maximum problem, silly.

[Ant]

> > > And their replacements are so cheap that it makes no sense to do
> > > anything but bin them when they waste your time so comprehensively.
> >
> > Bah, I don't want to waste them. I will get new ones when motherboards
> > don't use IDE/PATA anymore or I don't have any left.

> But it's false economy. That drive is 11 years old and the only benchmark I
> could find for it said it pulled a maximum of 23MB/s on sequential reads. The
> cheapest drive (£30) I can find on my local etailer is a Seagate ST3320418AS and
> the sequential transfer rate on that is 114MB/s. It's also native SATA and
> supports NCQ - not to mention having 21 times as much space and being ~5 times
> as fast. At the moment a drive like that Fireball in a machine like yours is
> most likely the biggest bottleneck you have.

I rarely use that drive too. It is mainly my storage drive where I dump
my music, backups, etc. I am currently use about 3.7 GB of it. That's
all it does. I don't use as my main system and OS stuff. :) It's just
there to act like an archive area.
--

Quote of the Week: "A coconut shell full of water is a(n) sea/ocean to an ant." --Indians

[Ant]

> >>>>> This is easily 100% reproducable. Is that a sign of a dying HDD?

> >>>> A few drives do beep when they are dying, pretty sure
> >>>> the fireball did beep, but its been too long now.

> >>> Interesting. I have never knew they do that.
> >>> How come newer/modern HDDs don't do that?

> >> They moved on to more sophisticated ways of telling
> >> the system that there is a problem like with SMART.

> >>>> You'd have to check where the beeps are coming
> >>>> from with the drive loose on the desktop to be sure.

> >>> OK.

> > Hmm, I will have to figure out which drive is making that noise.

> Yes, and the best way to do that is to have the drive loose on the desktop.

> Unfortunately that isnt that easy for you to do personally.

Yeah. Hence, why I was hoping to do it virtually as in unmount and tell
Debian not to use it on startup.

> > It is probably from hda/Seagate HDD

> Dunno, I dont believe the Barracudas ever did beep.

> You sure its a real beep and not just the drive recalibrating ?

> > since its smartctl results shows:
> > SMART Self-test log structure revision number 1
> > Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
> > # 1 Extended offline Completed without error 00% 43207 -
> > # 2 Extended offline Interrupted (host reset) 90% 43201 -
> > # 3 Extended offline Completed without error 00% 39844 -
> > # 4 Extended offline Interrupted (host reset) 20% 38502 -

> I've never like smartctl, it isnt at all clear what its actually saying there.

Really? What do you use then? Everest in Windows? Anything not Windows?
;)

> > Or maybe those interrupted errors were doing the long tests
> > I manaually ran when both of my HDDs went crazy?

> Probably.

OK.
--

Quote of the Week: "A coconut shell full of water is a(n) sea/ocean to an ant." --Indians

[Ant]

> >>> I wonder if my computer was too hot?

> >> Yes, you can get symptoms like that if its too hot.

> > So 80F degrees room temperature and 100F degrees inside from motherboard is hot?

> Nope, like I said below, thats not too bad at all.

OK.

> > Geez, I don't want to know how bad they will be in the heat
> > waves when my room temperatures go over 85F degrees. :(

> >>> it was about 80F degrees in my room and CMOS' sensors show 100+F degrees.

> >> Thats not too bad tho.

> > Oh.

> >>> I wished these old HDDs showed their temperatures.

> >> Yeah, thats just one of their deficiencys.

> >>>> You can resolve that by diagnosing it systematically, by trying
> >>>> a new ribbon cable first, then a spare power supply etc.

> >>> OK. I still haven't seen the issue come back. Weird stuff!

> >> Thats not that uncommon with a bad cable, connector
> >> not plugged in properly or a failing power supply.

> >> Hard to diagnose when its intermittent tho.

> > Yeah, I was hoping it would come back so I can try more stuff with it.
> > Ugh! I want to try unmounting/disabling that HDD in Debian to see if it
> > still will go crazy.

> Its illegal to mount your hard drive, you depraved person you.

Not me, perv.! Debian. They like to use dirty words like fsck, mount,
unmount, etc.

> Stick to sheep.

Eww! No thanks. I will stick with female humans. :P

> >>>> It isnt practical when there is only one drive.

> >>> Uh, why?

> >> Because Win uses the swap file extensively and there is no place to write the log to either.

> > Interesting. Then, where is Debian writing its log?

> Presumably it isnt read only for itself.

Hm.

> > I don't see it after it sets all my HDDs to read only.
> > I can't even run basic commands. Hah.

> >>> Wouldn't still make sense for the software to stop writing to
> >>> avoid more data losses/corruptions from too many errors?

> >> You dont normally see much data loss/corruption. It can happen, but
> >> the system will just stop completely when it cant write to the swap file.

> >> When things get bad, the BSOD does stop everything completely.

> > Which errors would those be?

> Almost anything can produce a BSOD with Win.

Hmmph, generic errors. :/

> > I have had seen Windows given me those balloon errors about HDD's SMART sensor results.

> BSODs are Blue Screen of Death.

I know. I was referring when there are disk errors. I have seen balloon
types.

[Ant]

> >> From the absence of any disk problem visible in the SMART data,
> >> I would conclude that your disk controller is dying, not the disks.

> > Are you referring to the disk controller on my HDDs

> Nope. Thats called a logic card.

Ah, darn. If it was, then easy to replace it.

> > or on my 2+ years old motherboard with the latest firmware/BIOS?

> Yep.

Crap. :( I wonder if this was just a random motherboard hiccup and not a
really a real HDD failure? Hmm.

[Rod Speed]

Ant <ANT...@zimage.com> wrote

>>>>>>> This is easily 100% reproducable. Is that a sign of a dying HDD?

>>>>>> A few drives do beep when they are dying, pretty sure
>>>>>> the fireball did beep, but its been too long now.

>>>>> Interesting. I have never knew they do that.
>>>>> How come newer/modern HDDs don't do that?

>>>> They moved on to more sophisticated ways of telling
>>>> the system that there is a problem like with SMART.

>>>>>> You'd have to check where the beeps are coming
>>>>>> from with the drive loose on the desktop to be sure.

>>>>> OK.

>>> Hmm, I will have to figure out which drive is making that noise.

>> Yes, and the best way to do that is to have the drive loose on the desktop.

>> Unfortunately that isnt that easy for you to do personally.

> Yeah. Hence, why I was hoping to do it virtually as
> in unmount and tell Debian not to use it on startup.

Yeah, but the problem affected both drives.

>>> It is probably from hda/Seagate HDD

>> Dunno, I dont believe the Barracudas ever did beep.

>> You sure its a real beep and not just the drive recalibrating ?

>>> since its smartctl results shows:
>>> SMART Self-test log structure revision number 1
>>> Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
>>> # 1 Extended offline Completed without error 00% 43207 -
>>> # 2 Extended offline Interrupted (host reset) 90% 43201 -
>>> # 3 Extended offline Completed without error 00% 39844 -
>>> # 4 Extended offline Interrupted (host reset) 20% 38502 -

>> I've never like smartctl, it isnt at all clear what its actually saying there.

> Really? What do you use then? Everest in Windows?

Yep.

> Anything not Windows?

Yeah, smartctl, because thats about all there is.

[Ant]

> >>>>>>> This is easily 100% reproducable. Is that a sign of a dying HDD?

> >>>>>> A few drives do beep when they are dying, pretty sure
> >>>>>> the fireball did beep, but its been too long now.

> >>>>> Interesting. I have never knew they do that.
> >>>>> How come newer/modern HDDs don't do that?

> >>>> They moved on to more sophisticated ways of telling
> >>>> the system that there is a problem like with SMART.

> >>>>>> You'd have to check where the beeps are coming
> >>>>>> from with the drive loose on the desktop to be sure.

> >>>>> OK.

> >>> Hmm, I will have to figure out which drive is making that noise.

> >> Yes, and the best way to do that is to have the drive loose on the desktop.

> >> Unfortunately that isnt that easy for you to do personally.

> > Yeah. Hence, why I was hoping to do it virtually as
> > in unmount and tell Debian not to use it on startup.

> Yeah, but the problem affected both drives.

Hmm. Man, this issue is weird/odd one. Still new incidents. I even tried
to use both drives last night for kicks.

> >>> It is probably from hda/Seagate HDD

> >> Dunno, I dont believe the Barracudas ever did beep.

> >> You sure its a real beep and not just the drive recalibrating ?

> >>> since its smartctl results shows:
> >>> SMART Self-test log structure revision number 1
> >>> Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
> >>> # 1 Extended offline Completed without error 00% 43207 -
> >>> # 2 Extended offline Interrupted (host reset) 90% 43201 -
> >>> # 3 Extended offline Completed without error 00% 39844 -
> >>> # 4 Extended offline Interrupted (host reset) 20% 38502 -

> >> I've never like smartctl, it isnt at all clear what its actually saying there.

> > Really? What do you use then? Everest in Windows?

> Yep.

Too bad, no Linux version. I wonder how easy it is to make it for
Windows PE. Can I just copy or do I have to install it to run it?

> > Anything not Windows?

> Yeah, smartctl, because thats about all there is.

Hmmph. I thought smartctl would be good for all its technical details
for you guys. Oh well.

[Trevor Hemsley]

On Wed, 26 Jan 2011 02:48:54 UTC in comp.os.linux.hardware, ANT...@zimage.com
(Ant) wrote:

> I rarely use that drive too. It is mainly my storage drive where I dump
> my music, backups, etc. I am currently use about 3.7 GB of it.

External USB cases are useful for this sort of thing and also let you change
disks and move them elsewhere, unplug them from the mains so everything doesn't
get fried at once etc.

[Rod Speed]

>>>> From the absence of any disk problem visible in the SMART data,
>>>> I would conclude that your disk controller is dying, not the disks.

>>> Are you referring to the disk controller on my HDDs

>> Nope. Thats called a logic card.

> Ah, darn. If it was, then easy to replace it.

>>> or on my 2+ years old motherboard with the latest firmware/BIOS?

>> Yep.

> Crap. :( I wonder if this was just a random motherboard hiccup and
> not a really a real HDD failure? Hmm.

Like I said, it can be the controller, the ribbon cable, the power supply etc.

[Rod Speed]

>>>>>>>>> This is easily 100% reproducable. Is that a sign of a dying HDD?

>>>>>>>> A few drives do beep when they are dying, pretty sure
>>>>>>>> the fireball did beep, but its been too long now.

>>>>>>> Interesting. I have never knew they do that.
>>>>>>> How come newer/modern HDDs don't do that?

>>>>>> They moved on to more sophisticated ways of telling
>>>>>> the system that there is a problem like with SMART.

>>>>>>>> You'd have to check where the beeps are coming
>>>>>>>> from with the drive loose on the desktop to be sure.

>>>>>>> OK.

>>>>> Hmm, I will have to figure out which drive is making that noise.

>>>> Yes, and the best way to do that is to have the drive loose on the desktop.

>>>> Unfortunately that isnt that easy for you to do personally.

>>> Yeah. Hence, why I was hoping to do it virtually as
>>> in unmount and tell Debian not to use it on startup.

>> Yeah, but the problem affected both drives.

> Hmm. Man, this issue is weird/odd one. Still new incidents.

Presumably you mean no new incidents.

> I even tried to use both drives last night for kicks.

You have to use the system for something absolutely crucial
with no backups to get a fault like that to show up again.

>>>>> It is probably from hda/Seagate HDD

>>>> Dunno, I dont believe the Barracudas ever did beep.

>>>> You sure its a real beep and not just the drive recalibrating ?

>>>>> since its smartctl results shows:
>>>>> SMART Self-test log structure revision number 1
>>>>> Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
>>>>> # 1 Extended offline Completed without error 00% 43207 -
>>>>> # 2 Extended offline Interrupted (host reset) 90% 43201 -
>>>>> # 3 Extended offline Completed without error 00% 39844 -
>>>>> # 4 Extended offline Interrupted (host reset) 20% 38502 -

>>>> I've never like smartctl, it isnt at all clear what its actually saying there.

>>> Really? What do you use then? Everest in Windows?

>> Yep.

> Too bad, no Linux version. I wonder how easy it is to make it for Windows PE.

Its a non trivial exercise, you basically have to do a build of the Win PE CD.

> Can I just copy

Nope.

> or do I have to install it to run it?

You cant just install it with PE either.

From memory someone has already done it, but I cant remember who.

Might be Hiren's CD

Cant find it on a quick google.

>>> Anything not Windows?

>> Yeah, smartctl, because thats about all there is.

> Hmmph. I thought smartctl would be good for all its technical details for you guys.

Yes it is in theory, but I find its output very hard to read, much too cryptic.

> Oh well.

[Rod Speed]

Rod Speed <rod.sp...@gmail.com> wrote

>>>>>>>> OK.

>>> Yep.

>> Can I just copy

> Nope.

You have to use the everest plugin in PE Builder, its not that hard.

> From memory someone has already done it, but I cant remember who.

> Might be Hiren's CD

> Cant find it on a quick google.

Have now, yes its done on Hiren's Boot CD.

[Ant]

On 1/25/2011 8:32 PM PT, Trevor Hemsley typed:

>> I rarely use that drive too. It is mainly my storage drive where I dump
>> my music, backups, etc. I am currently use about 3.7 GB of it.
>
> External USB cases are useful for this sort of thing and also let you change
> disks and move them elsewhere, unplug them from the mains so everything doesn't
> get fried at once etc.

I do that too. I like to keep them internally so I don't have to
unplug/replug, move, etc. Remember, I am disabled.
--
"The tiny ant dares to enter the lion's ear." --Armenian
/\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)

/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |

\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) If e-mailing, then axe ANT from its address if needed.
Ant is currently not listening to any songs on this computer.

[Ant]

On 1/25/2011 9:44 PM PT, Rod Speed typed:

>> Hmm. Man, this issue is weird/odd one. Still new incidents.
>
> Presumably you mean no new incidents.

OOOOOPS! Yep, I left out a word. Still true as of this post.

>> I even tried to use both drives last night for kicks.
>
> You have to use the system for something absolutely crucial
> with no backups to get a fault like that to show up again.

:P It was mostly idled overnight this time. I might use it more tonight.

>>>>> Dunno, I dont believe the Barracudas ever did beep.
>>>>> You sure its a real beep and not just the drive recalibrating ?

Ooops, I miss this question. I don't know. It was a very low beep sound.
Is there an audio recording of one so I can compare?

>>>>>> since its smartctl results shows:
>>>>>> SMART Self-test log structure revision number 1
>>>>>> Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
>>>>>> # 1 Extended offline Completed without error 00% 43207 -
>>>>>> # 2 Extended offline Interrupted (host reset) 90% 43201 -
>>>>>> # 3 Extended offline Completed without error 00% 39844 -
>>>>>> # 4 Extended offline Interrupted (host reset) 20% 38502 -
>
>>>>> I've never like smartctl, it isnt at all clear what its actually saying there.
>
>>>> Really? What do you use then? Everest in Windows?
>
>>> Yep.
>
>> Too bad, no Linux version. I wonder how easy it is to make it for Windows PE.
>
> Its a non trivial exercise, you basically have to do a build of the Win PE CD.
>
>> Can I just copy
>
> Nope.

So I can't boot a WinPE CD, and run a copied Everest that was installed
from another Windows machine. Everest needs a portable version. I should
contact the company to suggest it! :/

>> or do I have to install it to run it?
>
> You cant just install it with PE either.

Dang it.

> From memory someone has already done it, but I cant remember who.
>
> Might be Hiren's CD
>
> Cant find it on a quick google.

http://www.hiren.info/pages/bootcd doesn't show it, but has other
utlities. Maybe we can try one of those?

>>>> Anything not Windows?
>
>>> Yeah, smartctl, because thats about all there is.
>
>> Hmmph. I thought smartctl would be good for all its technical details for you guys.
>
> Yes it is in theory, but I find its output very hard to read, much too cryptic.

Bummer. I also noticed my hardware friend couldn't understand the
results. Who can?
--
"Only two great groups of animals, men and ants, indulge in highly
organized mass warfare." --Charles H. Maskins
/\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)

/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |

[Ant]

On 1/25/2011 9:48 PM PT, Rod Speed typed:

Ah OK. I used Ultimate BootCD for Windows before, but with defaults. I
hope it has Everest plugin.

>> From memory someone has already done it, but I cant remember who.
>
>> Might be Hiren's CD
>
>> Cant find it on a quick google.
>
> Have now, yes its done on Hiren's Boot CD.

Really? Where? It is not in http://www.hiren.info/pages/bootcd list. If
it is there, then I will download and use that one instead instead of
making my own.

--
"The tiny ant dares to enter the lion's ear." --Armenian

/\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)

/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |

[Ant]

On 1/25/2011 9:32 PM PT, Rod Speed typed:

>> Crap. :( I wonder if this was just a random motherboard hiccup and
>> not a really a real HDD failure? Hmm.
>
> Like I said, it can be the controller, the ribbon cable, the power supply etc.

Yeah, I will have to figure out. I guess I will do the easy part:
Replace the ribbon cable and disconnect the Quantum HDD. I will wait for
the problem to return which hasn't since Monday's early morning hours.
And yes, I made a backup of it (only 3.7 GB).
--
"I'm not a worker ant. I'm like a queen. Or maybe a king. But you never
hear of king ants." --Sean Bentley
/\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)

/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |

[Rod Speed]

Ant wrote
> Rod Speed wrote

>>> Hmm. Man, this issue is weird/odd one. Still new incidents.

>> Presumably you mean no new incidents.

> OOOOOPS! Yep, I left out a word. Still true as of this post.

>>> I even tried to use both drives last night for kicks.

>> You have to use the system for something absolutely crucial
>> with no backups to get a fault like that to show up again.

> P It was mostly idled overnight this time. I might use it more tonight.

>>>>>> Dunno, I dont believe the Barracudas ever did beep.
>>>>>> You sure its a real beep and not just the drive recalibrating ?

> Ooops, I miss this question.

Yeah, I meant to ask it again, and managed to forget, twice.

> I don't know. It was a very low beep sound.

Yeah, probably is just the drive recalibrating.

> Is there an audio recording of one so I can compare?

There are a few around, but the sound is VERY drive specific.
Cant find any on those two drives with a quick look.

>>>>>>> since its smartctl results shows:
>>>>>>> SMART Self-test log structure revision number 1
>>>>>>> Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
>>>>>>> # 1 Extended offline Completed without error 00% 43207 -
>>>>>>> # 2 Extended offline Interrupted (host reset) 90% 43201 -
>>>>>>> # 3 Extended offline Completed without error 00% 39844 -
>>>>>>> # 4 Extended offline Interrupted (host reset) 20% 38502 -

>>>>>> I've never like smartctl, it isnt at all clear what its actually saying there.

>>>>> Really? What do you use then? Everest in Windows?

>>>> Yep.

>>> Too bad, no Linux version. I wonder how easy it is to make it for Windows PE.

>> Its a non trivial exercise, you basically have to do a build of the Win PE CD.

>>> Can I just copy

>> Nope.

> So I can't boot a WinPE CD, and run a copied Everest that was installed from another Windows machine.

Dont think so.

> Everest needs a portable version. I should contact the company to suggest it! :/

They do have a PE plugin.

>>> or do I have to install it to run it?

>> You cant just install it with PE either.

> Dang it.

>> From memory someone has already done it, but I cant remember who.

>> Might be Hiren's CD

>> Cant find it on a quick google.

> http://www.hiren.info/pages/bootcd doesn't show it,

Yeah, fucked that up did the search too quickly, the hit I used just had hirens and everest in the same hit.

> but has other utlities. Maybe we can try one of those?

Makes more sense to just use PE Builder and make one yourself.

>>>>> Anything not Windows?

>>>> Yeah, smartctl, because thats about all there is.

>>> Hmmph. I thought smartctl would be good for all its technical details for you guys.

>> Yes it is in theory, but I find its output very hard to read, much too cryptic.

> Bummer. I also noticed my hardware friend couldn't understand the results. Who can?

Arno claims to, but I have my doubts.

[Rod Speed]

Ant <a...@zimage.comANT> wrote
> Rod Speed wrote
>> Rod Speed<rod.sp...@gmail.com> wrote

>>>>>>>>>> OK.

>>>>> Yep.

>>>> Can I just copy

>>> Nope.

One of them definitely does.

>>> From memory someone has already done it, but I cant remember who.

>>> Might be Hiren's CD

>>> Cant find it on a quick google.

>> Have now, yes its done on Hiren's Boot CD.

> Really? Where? It is not in http://www.hiren.info/pages/bootcd list.

Yeah, I fucked that up. Didnt look at the google hit, just used the google list.
The hit has both Hirens and Everest in it, one of the pirate sites.

> If it is there, then I will download and use that one instead instead of making my own.

It isnt that hard to make, but certainly one of them has done it already.

[Charlie Gibbs]

In article <8q72nd...@mid.individual.net>, rod.sp...@gmail.com
(Rod Speed) writes:

>>>>> It's a property of Linux. There is code to disable
>>>>> the drive but as far as I can see, none to re-enable it.
>>>>
>>>> Ah. I wonder why MS didn't implement this in Windows and DOS.

>>>> It would have been handy to keep data corruptions low.
>>>

>>> They tried.
>
> Thats a lie.
>
>>> But the way their file system keeps corrupting
>>> things, it kept shutting down the system,
>
> Another lie.
>
>>> so they had to take it out again.
>>
>> Hahaha. That's funny when Linux does it fine. Is it because
>> of their file systems/FS' compared to EXT3 which I am using?
>
> Nope, he lied about file system corruption.

Sheesh. "That's a joke, son." -- Foghorn Leghorn

--
/~\ cgi...@kltpzyxm.invalid (Charlie Gibbs)
\ / I'm really at ac.dekanfrus if you read it the right way.
X Top-posted messages will probably be ignored. See RFC1855.
/ \ HTML will DEFINITELY be ignored. Join the ASCII ribbon campaign!

[Ant]

> >> You have to use the everest plugin in PE Builder, its not that hard.

> > Ah OK. I used Ultimate BootCD for Windows before, but with defaults. I hope it has Everest plugin.

> One of them definitely does.

OK. I tried v3.60 and don't see it unless I am blind. Where is it?

> >>> Might be Hiren's CD

> >>> Cant find it on a quick google.

> >> Have now, yes its done on Hiren's Boot CD.

> > Really? Where? It is not in http://www.hiren.info/pages/bootcd list.

> Yeah, I fucked that up. Didnt look at the google hit, just used the google list.
> The hit has both Hirens and Everest in it, one of the pirate sites.

Ah OK.

> > If it is there, then I will download and use that one instead instead of making my own.

> It isnt that hard to make, but certainly one of them has done it already.

OK.

--
Quote of the Week: "A coconut shell full of water is a(n) sea/ocean to an ant." --Indians

/\___/\ Ant @ http://antfarm.home.dhs.org (Personal Web Site)

/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |

\ _ / Please nuke ANT if replying by e-mail. If crediting,

( ) then please kindly use Ant nickname and AQFL URL/link.

[Rod Speed]

Charlie Gibbs wrote
> rod.sp...@gmail.com (Rod Speed) wrote

>>>>>> It's a property of Linux. There is code to disable
>>>>>> the drive but as far as I can see, none to re-enable it.

>>>>> Ah. I wonder why MS didn't implement this in Windows and DOS.
>>>>> It would have been handy to keep data corruptions low.

>>>> They tried.

>> Thats a lie.

>>>> But the way their file system keeps corrupting
>>>> things, it kept shutting down the system,

>> Another lie.

>>>> so they had to take it out again.

>>> Hahaha. That's funny when Linux does it fine. Is it because
>>> of their file systems/FS' compared to EXT3 which I am using?

>> Nope, he lied about file system corruption.

> Sheesh. "That's a joke, son." -- Foghorn Leghorn

You're a pathetic joke.

[Rod Speed]

Ant wrote:

>>>> You have to use the everest plugin in PE Builder, its not that hard.

>>> Ah OK. I used Ultimate BootCD for Windows before,
>>> but with defaults. I hope it has Everest plugin.

>> One of them definitely does.

> OK. I tried v3.60 and don't see it unless I am blind. Where is it?

I didnt mean one version of that, I meant one of those boot CDs does.

>>>>> Might be Hiren's CD

>>>>> Cant find it on a quick google.

>>>> Have now, yes its done on Hiren's Boot CD.

>>> Really? Where? It is not in http://www.hiren.info/pages/bootcd list.

>> Yeah, I fucked that up. Didnt look at the google hit, just used the google
>> list. The hit has both Hirens and Everest in it, one of the pirate sites.

> Ah OK.

>>> If it is there, then I will download and use that one instead instead of making my own.

>> It isnt that hard to make, but certainly one of them has done it already.

> OK.

Hard to google, too many hits on boot and everest just involve that stupid mountain.

[Ant]

> >>> Hmm. Man, this issue is weird/odd one. Still new incidents.

> >> Presumably you mean no new incidents.

> > OOOOOPS! Yep, I left out a word. Still true as of this post.

Still true now. :P

> >>>>>> Dunno, I dont believe the Barracudas ever did beep.
> >>>>>> You sure its a real beep and not just the drive recalibrating ?

> > Ooops, I miss this question.

> Yeah, I meant to ask it again, and managed to forget, twice.

Haha, we both frakked up!

> > I don't know. It was a very low beep sound.

> Yeah, probably is just the drive recalibrating.

> > Is there an audio recording of one so I can compare?

> There are a few around, but the sound is VERY drive specific.
> Cant find any on those two drives with a quick look.

Oh OK. I thought they all had similiar sounds.

> >>>>>>> since its smartctl results shows:
> >>>>>>> SMART Self-test log structure revision number 1
> >>>>>>> Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
> >>>>>>> # 1 Extended offline Completed without error 00% 43207 -
> >>>>>>> # 2 Extended offline Interrupted (host reset) 90% 43201 -
> >>>>>>> # 3 Extended offline Completed without error 00% 39844 -
> >>>>>>> # 4 Extended offline Interrupted (host reset) 20% 38502 -

> >>>>>> I've never like smartctl, it isnt at all clear what its actually saying there.

> >>>>> Really? What do you use then? Everest in Windows?

> >>>> Yep.

> >>> Too bad, no Linux version. I wonder how easy it is to make it for Windows PE.

> >> Its a non trivial exercise, you basically have to do a build of the Win PE CD.

> >>> Can I just copy

> >> Nope.

> > So I can't boot a WinPE CD, and run a copied Everest that was installed from another Windows machine.

> Dont think so.

Hey, I got Everest Home Edition v1.10.106 (is this the latest version
[very old and not updated anymore]?) to run in a WinPE CD. It can be
either from the installed HDD copy or install into WinPE session (X:
drive). I will have to try that next time. IIRC, I can use USB flash
drives.

> > Everest needs a portable version. I should contact the company to suggest it! :/

> They do have a PE plugin.

I don't see it. :(

> >>> or do I have to install it to run it?

> >> You cant just install it with PE either.

> > Dang it.

> >> From memory someone has already done it, but I cant remember who.

> >> Might be Hiren's CD

> >> Cant find it on a quick google.

> > http://www.hiren.info/pages/bootcd doesn't show it,

> Yeah, fucked that up did the search too quickly, the hit I used just had hirens and everest in the same hit.

OK.

> > but has other utlities. Maybe we can try one of those?

> Makes more sense to just use PE Builder and make one yourself.

OK.

> >>>>> Anything not Windows?

> >>>> Yeah, smartctl, because thats about all there is.

> >>> Hmmph. I thought smartctl would be good for all its technical details for you guys.

> >> Yes it is in theory, but I find its output very hard to read, much too cryptic.

> > Bummer. I also noticed my hardware friend couldn't understand the results. Who can?

> Arno claims to, but I have my doubts.

OK.

--
Quote of the Week: "A coconut shell full of water is a(n) sea/ocean to an ant." --Indians

/\___/\ Ant @ http://antfarm.home.dhs.org (Personal Web Site)

/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |

\ _ / Please nuke ANT if replying by e-mail. If crediting,

( ) then please kindly use Ant nickname and AQFL URL/link.

[Ant]

> >>>> You have to use the everest plugin in PE Builder, its not that hard.

> >>> Ah OK. I used Ultimate BootCD for Windows before,
> >>> but with defaults. I hope it has Everest plugin.

> >> One of them definitely does.

> > OK. I tried v3.60 and don't see it unless I am blind. Where is it?

> I didnt mean one version of that, I meant one of those boot CDs does.

Uhh, do you know which one it is?

> >>>>> Might be Hiren's CD

> >>>>> Cant find it on a quick google.

> >>>> Have now, yes its done on Hiren's Boot CD.

> >>> Really? Where? It is not in http://www.hiren.info/pages/bootcd list.

> >> Yeah, I fucked that up. Didnt look at the google hit, just used the google
> >> list. The hit has both Hirens and Everest in it, one of the pirate sites.

> > Ah OK.

> >>> If it is there, then I will download and use that one instead instead of making my own.

> >> It isnt that hard to make, but certainly one of them has done it already.

> > OK.

> Hard to google, too many hits on boot and everest just involve that stupid mountain.

Oh well, I got it to work on a diffeent WinPE CD so I can use that
method. I just don't know if Everest Home Edition version is the latest
and acceptable to use.

[Rod Speed]

Ant <ANT...@zimage.com> wrote

>>>>> Hmm. Man, this issue is weird/odd one. Still new incidents.

>>>> Presumably you mean no new incidents.

>>> OOOOOPS! Yep, I left out a word. Still true as of this post.

> Still true now. :P

Time to give it a good kicking.

>>>>>>>> Dunno, I dont believe the Barracudas ever did beep.
>>>>>>>> You sure its a real beep and not just the drive recalibrating ?

>>> Ooops, I miss this question.

>> Yeah, I meant to ask it again, and managed to forget, twice.

> Haha, we both frakked up!

True.

>>> I don't know. It was a very low beep sound.

>> Yeah, probably is just the drive recalibrating.

>>> Is there an audio recording of one so I can compare?

>> There are a few around, but the sound is VERY drive specific.
>> Cant find any on those two drives with a quick look.

> Oh OK. I thought they all had similiar sounds.

>>>>>>>>> since its smartctl results shows:
>>>>>>>>> SMART Self-test log structure revision number 1
>>>>>>>>> Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
>>>>>>>>> # 1 Extended offline Completed without error 00% 43207 -
>>>>>>>>> # 2 Extended offline Interrupted (host reset) 90% 43201 -
>>>>>>>>> # 3 Extended offline Completed without error 00% 39844 -
>>>>>>>>> # 4 Extended offline Interrupted (host reset) 20% 38502 -

>>>>>>>> I've never like smartctl, it isnt at all clear what its actually saying there.

>>>>>>> Really? What do you use then? Everest in Windows?

>>>>>> Yep.

>>>>> Too bad, no Linux version. I wonder how easy it is to make it for Windows PE.

>>>> Its a non trivial exercise, you basically have to do a build of the Win PE CD.

>>>>> Can I just copy

>>>> Nope.

>>> So I can't boot a WinPE CD, and run a copied Everest that was installed from another Windows machine.

>> Dont think so.

> Hey, I got Everest Home Edition v1.10.106 (is this the latest version

Nope
http://www.majorgeeks.com/download.php?det=4181

> [very old and not updated anymore]?)

The commercial versions are.

> to run in a WinPE CD. It can be either from the installed HDD copy or install into WinPE
> session (X: drive). I will have to try that next time. IIRC, I can use USB flash drives.

>> > Everest needs a portable version. I should contact the company to suggest it! :/

>> They do have a PE plugin.

> I don't see it. :(

Google it.

[Rod Speed]

>>>>>> You have to use the everest plugin in PE Builder, its not that hard.

>>>>> Ah OK. I used Ultimate BootCD for Windows before,
>>>>> but with defaults. I hope it has Everest plugin.

>>>> One of them definitely does.

>>> OK. I tried v3.60 and don't see it unless I am blind. Where is it?

>> I didnt mean one version of that, I meant one of those boot CDs does.

> Uhh, do you know which one it is?

Fraid not, cant remember.

>>>>>>> Might be Hiren's CD

>>>>>>> Cant find it on a quick google.

>>>>>> Have now, yes its done on Hiren's Boot CD.

>>>>> Really? Where? It is not in http://www.hiren.info/pages/bootcd list.

>>>> Yeah, I fucked that up. Didnt look at the google hit, just used the google
>>>> list. The hit has both Hirens and Everest in it, one of the pirate sites.

>>> Ah OK.

>>>>> If it is there, then I will download and use that one instead instead of making my own.

>>>> It isnt that hard to make, but certainly one of them has done it already.

>>> OK.

>> Hard to google, too many hits on boot and everest just involve that stupid mountain.

> Oh well, I got it to work on a diffeent WinPE CD so I can use that method.

True.

> I just don't know if Everest Home Edition version is the latest

Yours isnt, but
http://www.majorgeeks.com/download.php?det=4181
is.

> and acceptable to use.

Any should be fine, the main thing that the commercial versions added to the SMART report
is being able to do a SMART report on external USB drives which yours arent anyway.

[Ant]

> >>> OK. I tried v3.60 and don't see it unless I am blind. Where is it?

> >> I didnt mean one version of that, I meant one of those boot CDs does.

> > Uhh, do you know which one it is?

> Fraid not, cant remember.

Oh well, thanks anyways. :)

> > I just don't know if Everest Home Edition version is the latest

> Yours isnt, but
> http://www.majorgeeks.com/download.php?det=4181
> is.

Thanks. Still old from 2005, but oh well. Is there no free edition of
AIDA that took over Everest Home? Do I assume Everest works in 64-bit W7
too?

> > and acceptable to use.

> Any should be fine, the main thing that the commercial versions added to the SMART report
> is being able to do a SMART report on external USB drives which yours arent anyway.

Ah OK.

[Ant]

> >>>>> Hmm. Man, this issue is weird/odd one. Still new incidents.

> >>>> Presumably you mean no new incidents.

> >>> OOOOOPS! Yep, I left out a word. Still true as of this post.

> > Still true now. :P

> Time to give it a good kicking.

I will kick when it goes crazy again. :P

> >>>>>>>> Dunno, I dont believe the Barracudas ever did beep.
> >>>>>>>> You sure its a real beep and not just the drive recalibrating ?

> >>> Ooops, I miss this question.

> >> Yeah, I meant to ask it again, and managed to forget, twice.

> > Haha, we both frakked up!

> True.

:)

> > Hey, I got Everest Home Edition v1.10.106 (is this the latest version

> Nope
> http://www.majorgeeks.com/download.php?det=4181

Thanks.

> > [very old and not updated anymore]?)

> The commercial versions are.

And no free version. Not even a trial/shareware. Bah.

[Rod Speed]

>>> I just don't know if Everest Home Edition version is the latest

>> Yours isnt, but
>> http://www.majorgeeks.com/download.php?det=4181
>> is.

> Thanks. Still old from 2005, but oh well.

> Is there no free edition of AIDA that took over Everest Home?

Dunno. I just use the one above except where I need SMART on an external drive.

> Do I assume Everest works in 64-bit W7 too?

Yes it does.

[Ant]

> >>> I just don't know if Everest Home Edition version is the latest

> >> Yours isnt, but
> >> http://www.majorgeeks.com/download.php?det=4181
> >> is.

> > Thanks. Still old from 2005, but oh well.

> > Is there no free edition of AIDA that took over Everest Home?

> Dunno. I just use the one above except where I need SMART on an external drive.

> > Do I assume Everest works in 64-bit W7 too?

> Yes it does.

OK good.

[John Turco]

Rod Speed wrote:
>
> Ant <ANT...@zimage.com> wrote

>
> >>>>> This is easily 100% reproducable. Is that a sign of a dying HDD?
>
> >>>> A few drives do beep when they are dying, pretty sure
> >>>> the fireball did beep, but its been too long now.
>
> >>> Interesting. I have never knew they do that.
> >>> How come newer/modern HDDs don't do that?
>
> >> They moved on to more sophisticated ways of telling
> >> the system that there is a problem like with SMART.
>
> >>>> You'd have to check where the beeps are coming
> >>>> from with the drive loose on the desktop to be sure.
>
> >>> OK.
>
> > Hmm, I will have to figure out which drive is making that noise.
>
> Yes, and the best way to do that is to have the drive loose on the
> desktop.
>
> Unfortunately that isnt that easy for you to do personally.
>

> > It is probably from hda/Seagate HDD
>

> Dunno, I dont believe the Barracudas ever did beep.
>
> You sure its a real beep and not just the drive recalibrating ?
>

> > since its smartctl results shows:
> > SMART Self-test log structure revision number 1
> > Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
> > # 1 Extended offline Completed without error 00% 43207 -
> > # 2 Extended offline Interrupted (host reset) 90% 43201 -
> > # 3 Extended offline Completed without error 00% 39844 -
> > # 4 Extended offline Interrupted (host reset) 20% 38502 -
>
> I've never like smartctl, it isnt at all clear what its actually saying there.
>

> > Or maybe those interrupted errors were doing the long tests
> > I manaually ran when both of my HDDs went crazy?
>
> Probably.
>

> > Quote of the Week: "A coconut shell full of water is a(n) sea/ocean to an
> > ant." --Indians
>

> Nope, just a pond at most. And Red Indians never had coconuts anyway.

What about those "Red Indians" of South America, though?

--
Cordially,
John Turco <jt...@concentric.net>

Marie's Musings <http://fairiesandtails.blogspot.com>

[John Turco]

Rod Speed wrote:
>
> Ant wrote
>
> >>> That could be. Shouldn't other hardwares be failing too or showing
> >>> symptoms?
>
> >> Not necessarily, there is usually something that shows symptoms
> >> first when the rail sags, or when there is a lot more noise on
> >> the rail than there should be.
>
> >>> I did try hitting on my case to see if there was anything loose
>
> >> You're sposed to take to it with the largest waddy you can find.
> >> http://en.wiktionary.org/wiki/waddy
>
> > Ah, it looks like one of those stone age clubs.
>
> Yeah, they never made it out of the stone age till the white man
> showed up.
>
> They didnt even manage to invent clothes or houses in a place like
> Tasmania which can be frigid in winter.

<heavily edited for brevity>

Even the denizens of "Darkest Africa" aren't quite >that< backward!

(Please, Rod...excuse my major snipping.)

[Rod Speed]

John Turco <jt...@concentric.net> wrote

>>>>> OK.

>> Probably.

They didnt either.

[Rod Speed]

John Turco wrote

> Rod Speed wrote
>> Ant wrote

>>>>> That could be. Shouldn't other hardwares be failing too or showing symptoms?

>>>> Not necessarily, there is usually something that shows symptoms
>>>> first when the rail sags, or when there is a lot more noise on
>>>> the rail than there should be.

>>>>> I did try hitting on my case to see if there was anything loose

>>>> You're sposed to take to it with the largest waddy you can find.
>>>> http://en.wiktionary.org/wiki/waddy

>>> Ah, it looks like one of those stone age clubs.

>> Yeah, they never made it out of the stone age till the white man showed up.

>> They didnt even manage to invent clothes or houses in
>> a place like Tasmania which can be frigid in winter.

> <heavily edited for brevity>

> Even the denizens of "Darkest Africa" aren't quite >that< backward!

True. Those of Tierra del Feugo were tho.

> (Please, Rod...excuse my major snipping.)

No way, its completely inexcusible.