Upgrading QT caused my RAID array to drop frames again!

FCP 5.1.4. Upgraded QT today as per software upgrade. Repaired DPs after. Just as last time, now my RAID array drops frames on PB. Last time, I thought it was a controller card problem, but a student said to just reinstall QT using steps from Michael Eilers' March 18, 2007 post. It worked. I can try this again, but my question is: Do I have to do this everytime I upgrade QT? Am I doing something wrong? This can't be the SOP for upgrading QT, can it? Maybe I should look at LaCie for updates to the RAID? Advise and help to answer this would be greatly appreciated.

REPEAT AFTER ME: WHEN YOU HAVE A STABLE OS AND APPLICATION COMBO, CLONE YOUR STARTUP DRIVE. This is the only way, I repeat, THE ONLY WAY to work if you depend on your system for your livelihood. I clone to a second internal drive and I can be back to work in a matter of minutes if things go south after an update or upgrade. There is no way that Apple can thoroughly test every possible hardware and software combination. And do not expect a third party supplier to have updates immediately ready.

Similar Messages

Upgrade to FCE 4.0 results in dropped frames

I just upgraded to FCE 4.0 from 3.5HD and now key-framed motion clips that worked fine before die repeatedly with dropped frames. I've set RT to safe and dynamic and the memory cache to 80%, and while FCE is resident on my hard drive the files are on the G-Raid linked by firewire (not USB) where the scratch disks, waveform and thumbnail caches, and autosave vault are pointed.
Will upgrading RAM to 4 GB help? How about a new 7200 rpm hard drive with 16 meg cache?
What else should I do?

Hi(Bonjour)!
Install the FCE 4.0.1 update via software update.
Try to render for playback.
Michel Boissonneault

MOVED: Upgrading system with existing RAID Array

This topic has been moved to Vista problems.
https://forum-en.msi.com/index.php?topic=106509.0

The only issue I can foresee is a permissions one. Make sure it is set to "Ignore permissions…" before doing anything. If the drive has specific ownership when you reinstall and you fail to have a matching account to the onwer you'll need to mess with the root account to potentially get back into the drive.
Most unknowingly avoid this issue though using the same username and short username on the reinstalled system.

Dropped Frames w/Xserve RAID: Solution

We were having problems with capturing DV footage onto our new Xserve RAID and having dropped frames or even image freeze during the capture. Found some threads on the Xserve RAID forum regarding the issue and after following some of the suggestions (summed up in the article below) we can now report the problem has been solved. However, there are some reports the remedy may need to be reimplemented if the Xserve RAID is powered down. But I hope this helps those out there experiencing similar problems between FCP and Xserve RAID.
http://docs.info.apple.com/article.html?artnum=302780

every night I shut down my xraid unless it's rendering or copy ing. I use raid admin to shut it down. Every morning I start the array from the button on the back, boot the G5, and launch raid admin and uncheck "allow host cache flushing" It's like brushing your teeth and having a shower tho those personal habits don't have to follow the same order

Quick RAID array setup question

I had to upgrade one of the RAID arrays of one of my clients the other day. I had not setup the RIAD previously, but when I looked at how it was setup before it had 6 disc's in the array and one not part of the array.
Now I assume who ever set it up before assumed that the 7th disc would be the redundant disc. After looking at the way it worked and doing some calculations from what info RAID admin provided me with I came to the conclusion that the way it was set up would be 6 disc's used as the array with one being a parity drive so if a drive failed that one would take over. On top of that they had another disc that was basically useless as it was not incorporated into the raid at all.
The way I have set it up is that all 7 discs are part of the array so they have 6 disc's working with one fail over that would be the 7th meaning no disc's are wasted.
Which way is correct is my question.

I assume your predesessor left one disk as a hot spare.
Whenever a disk from a raid set fails, the raid set will be rebuild with the hot spare disk. The bad disk can be swapped and will be the hot spare from then.
Configuarions like this will give you the highest availability, but will cost you the most. Netto you will have the amount of 5 out of 7 disks. (1 for parity and 1 for hot spare).
Note that in a raid5 set the parity is spread over all raid disks. There is not such a thing as a 'paritydisk'. The term paritydisk is hust for mathmatics purposes.
Regards
Donald

Final Cut Pro and EditShare - Dropped Frames

Hey,
My Company just got a new EditShare File Sharing server. It's a 5 Rack with 24 drives, for a total of 18TB of space. The problem is, when we're trying to capture straight to the ES (which has 8 RAIDS) there are Dropped Frame Errors appearing. We've tried turning the Internet off, and even re-organized the connection preferences so the ES is the first to be refreshed, but we're still having dropped frames. Info:
Final Cut Pro - 5.1.2
Capturing from a DVCPRO 50 Deck thru Firewire
EditShare - 4.0.2
G5 Mac with OS 10.4.7
note Didn't get so many dropped frames when using LaCie Drives. Could be connection speed or not enough broadband. Any Suggestions? Thanks.
FraserPost

I believe it's fiber, but not sure. We're also checking because the Gigabit switch has 3 settings, 10/100/1000 gigabits, so it could be at a lower setting, and that's causing a backup in the broadband speed. We're also noticing that the transfer rate from our External HDs (which we were capturing to before) to the ES was slower than anticipated.
Anyone else find this problem with an EditShare or File Sharing server?
Just checked, it's CAT6 cables.
Fraser

Dropped frames on Xserve RAID upgraded w/750GB drives.

I'm capturing in 10-bit uncompressed standard definition 720x480. I just upgraded one side of my Apple XRAID, (connected directly via fibre channel) with seven, 750GB hard drives from Apple, drives designed for the XRAID, (came with there own sleds.)
Current Xserve RAID firmware version is at version 1.5.1/1.51c
Before the upgraded drives, no issues with dropped frames, (drives 1-7) the other side of the same RAID has no problems, (currently running 250GB drives, drives 8-14.) All sleds are populated with drives of the same capacity, (respective to each side.)
The drives were formated using the Xserve RAID Admin software and mounted using Apples Disk Utilities, Journaling turned off. The final formated capacity of the RAID on drives 1-7 is 4.1TB.
When I capture to the drives on the upgrade side, I get dropped frames. When capturing to the other side, no issues, works great. I checked the settings for performance and they are the same for both sides, as follows:
Use Controller Write Cashe - ON
Allow Host Cashe Flushing - OFF
Use Drive Write Cashe - ON
Use Steady Streaming Mode - OFF
Read Prefetch: 128 stripes (8 MB/disk)
My capture box is an AJA I/o and has never given me dropped frames till now, but only on the side of the RAID that has the new 750GB drives. I also have another RAID that uses 500GB drives on both sides and it work just fine as well, (no dropped frames) using the same performance settings in XRAID utilities.
Any suggestion on why these new Apple drives modules are dropping frame would be very much appreciate. Again 7 new 750GB drives from Apple w/sleds having dropped frame issues.

I'm capturing in 10-bit to avoid loss of quality from analog sources like BetaCam SP as well as line 21 must be part of the captured file, because it contains line 21 for captioning. Eight bit has a banding issue that I can't have in the final product and 10-bit doesn't have this issue.
Source quality is maintained completely when working in 10-bit uncompressed, as well as the captioning data that I need, which is stripped out of the captured video latter. Captioning software can read line 21 of the raster area, of the captured file.
Source video is from BetaCam SP, DVC Pro and DVCam.
The RAID is an Apple Xserve RAID, connected via Fibre channel directly, (no xsan.)
I also create high quality QuickTime Streaming files from these source files, the higher the quality of the source video the the better the streaming files look when created.
I have never had any problem capturing till I installed these new drives from Apple.
The RAID is as stated above, is an Apple Xserve RAID, connect via a fibre channel card in a Mac Pro 3.0GHz tower, (no xsan is used, due to connecting directly to the XRAID.)

K8N Neo2 Platinum - RAID Array Causes CPU Spikes!

I got my RAID array set up.
When I transfer files to it, my CPU usage (kernerl level) shoot up. It's around 100%, and it slows my system way down.
MSI K8N Neo2 Platinum.
RAID 0 using SATA ports 3 and 4.
I'm transferring files from my current windows installation to partitions on the raid array, so I can install windows on the array after removing the old drives.
I can transfer data fine, but using the array causes huge cpu usage which slows the rest of my system down a LOT.

Quote from: MurdoK on 19-April-06, 16:40:06
Hello !
Which SATA / Raid Driver did you install ? The ones from the nforce driver package provided by nvidia, or the original MSI driver ?
Go here:
http://www.msi.com.tw/program/support/driver/dvr/spt_dvr_detail.php?UID=607&kind=1
And download and install the SATA RAID Driver, make a backup of your Data first.
Greetz
Well, I have seen this post and it makes me wonder what are the differences between nforce chipset driver packages and the MSI ones if any? Thanks in advance.

Lag/Pause believed to be caused by RAID [SOLVED]

I have installed arch about 4 months back and ever since been experience and Lag/Freezing issue which occurs anywhere from 1-30 seconds at a time. I have been looking for solutions and fixing issues I have found with my system in order to find a solution. It does not seem to be any issue with the hardware, everything is new. I have even gone so far as to swapping out certain parts such as the memory and have even updated the bios firmware.
I believe this is an issue with the way the raid is setup, as harddrive I/O will cease when this happens. If there is something else that may be causeing this issue then I am unsure what it could be.
I have posted my dmesg, mdstat and mdadm.conf files below. Also my system is still experience two bugs. The first one is the RAID initalization failed message durring systm initialization even though the raid array was assembled fine by the kernel. And the other on is the error message from LVM2 durring initalization "File-based locking initialisation failed". That error has supposively been fixed from an update though I am still getting it.
dmesg
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 2.6.33-ARCH (thomas@evey) (gcc version 4.5.0 (GCC) ) #1 SMP PREEMPT Mon Apr 26 19:31:00 CEST 2010
Command line: root=/dev/array/root ro
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 00000000cfbe0000 (usable)
BIOS-e820: 00000000cfbe0000 - 00000000cfbe1000 (ACPI NVS)
BIOS-e820: 00000000cfbe1000 - 00000000cfbf0000 (ACPI data)
BIOS-e820: 00000000cfbf0000 - 00000000cfc00000 (reserved)
BIOS-e820: 00000000f4000000 - 00000000f8000000 (reserved)
BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
BIOS-e820: 0000000100000000 - 0000000130000000 (usable)
NX (Execute Disable) protection: active
DMI 2.4 present.
No AGP bridge found
last_pfn = 0x130000 max_arch_pfn = 0x400000000
MTRR default type: uncachable
MTRR fixed ranges enabled:
00000-9FFFF write-back
A0000-BFFFF uncachable
C0000-CCFFF write-protect
CD000-EFFFF uncachable
F0000-FFFFF write-through
MTRR variable ranges enabled:
0 base 000000000 mask F00000000 write-back
1 base 0E0000000 mask FE0000000 uncachable
2 base 0D0000000 mask FF0000000 uncachable
3 base 100000000 mask FC0000000 write-back
4 base 130000000 mask FF0000000 uncachable
5 disabled
6 disabled
7 disabled
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
e820 update range: 00000000d0000000 - 0000000100000000 (usable) ==> (reserved)
last_pfn = 0xcfbe0 max_arch_pfn = 0x400000000
e820 update range: 0000000000001000 - 0000000000010000 (usable) ==> (reserved)
Scanning 1 areas for low memory corruption
modified physical RAM map:
modified: 0000000000000000 - 0000000000001000 (usable)
modified: 0000000000001000 - 0000000000010000 (reserved)
modified: 0000000000010000 - 000000000009f800 (usable)
modified: 000000000009f800 - 00000000000a0000 (reserved)
modified: 00000000000f0000 - 0000000000100000 (reserved)
modified: 0000000000100000 - 00000000cfbe0000 (usable)
modified: 00000000cfbe0000 - 00000000cfbe1000 (ACPI NVS)
modified: 00000000cfbe1000 - 00000000cfbf0000 (ACPI data)
modified: 00000000cfbf0000 - 00000000cfc00000 (reserved)
modified: 00000000f4000000 - 00000000f8000000 (reserved)
modified: 00000000fec00000 - 0000000100000000 (reserved)
modified: 0000000100000000 - 0000000130000000 (usable)
initial memory mapped : 0 - 20000000
found SMP MP-table at [ffff8800000f5630] f5630
init_memory_mapping: 0000000000000000-00000000cfbe0000
0000000000 - 00cfa00000 page 2M
00cfa00000 - 00cfbe0000 page 4k
kernel direct mapping tables up to cfbe0000 @ 16000-1c000
init_memory_mapping: 0000000100000000-0000000130000000
0100000000 - 0130000000 page 2M
kernel direct mapping tables up to 130000000 @ 1a000-20000
RAMDISK: 37d4d000 - 37feff2b
ACPI: RSDP 00000000000f6ff0 00014 (v00 GBT )
ACPI: RSDT 00000000cfbe1040 00040 (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
ACPI: FACP 00000000cfbe10c0 00074 (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
ACPI: DSDT 00000000cfbe1180 042C4 (v01 GBT GBTUACPI 00001000 MSFT 0100000C)
ACPI: FACS 00000000cfbe0000 00040
ACPI: HPET 00000000cfbe55c0 00038 (v01 GBT GBTUACPI 42302E31 GBTU 00000098)
ACPI: MCFG 00000000cfbe5640 0003C (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
ACPI: EUDS 00000000cfbe5680 00560 (v01 GBT 00000000 00000000)
ACPI: TAMG 00000000cfbe5be0 00A32 (v01 GBT GBT B0 5455312E BG?? 53450101)
ACPI: APIC 00000000cfbe54c0 000BC (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
ACPI: SSDT 00000000cfbe6640 02F8C (v01 INTEL PPM RCM 80000001 INTL 20061109)
ACPI: Local APIC address 0xfee00000
(13 early reservations) ==> bootmem [0000000000 - 0130000000]
#0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
#1 [0001000000 - 00016d6b38] TEXT DATA BSS ==> [0001000000 - 00016d6b38]
#2 [0037d4d000 - 0037feff2b] RAMDISK ==> [0037d4d000 - 0037feff2b]
#3 [00016d7000 - 00016d70f6] BRK ==> [00016d7000 - 00016d70f6]
#4 [00000f5640 - 0000100000] BIOS reserved ==> [00000f5640 - 0000100000]
#5 [00000f5630 - 00000f5640] MP-table mpf ==> [00000f5630 - 00000f5640]
#6 [000009f800 - 00000f0d00] BIOS reserved ==> [000009f800 - 00000f0d00]
#7 [00000f0edc - 00000f5630] BIOS reserved ==> [00000f0edc - 00000f5630]
#8 [00000f0d00 - 00000f0edc] MP-table mpc ==> [00000f0d00 - 00000f0edc]
#9 [0000010000 - 0000012000] TRAMPOLINE ==> [0000010000 - 0000012000]
#10 [0000012000 - 0000016000] ACPI WAKEUP ==> [0000012000 - 0000016000]
#11 [0000016000 - 000001a000] PGTABLE ==> [0000016000 - 000001a000]
#12 [000001a000 - 000001b000] PGTABLE ==> [000001a000 - 000001b000]
[ffffea0000000000-ffffea00043fffff] PMD -> [ffff880001800000-ffff8800051fffff] on node 0
Zone PFN ranges:
DMA 0x00000000 -> 0x00001000
DMA32 0x00001000 -> 0x00100000
Normal 0x00100000 -> 0x00130000
Movable zone start PFN for each node
early_node_map[4] active PFN ranges
0: 0x00000000 -> 0x00000001
0: 0x00000010 -> 0x0000009f
0: 0x00000100 -> 0x000cfbe0
0: 0x00100000 -> 0x00130000
On node 0 totalpages: 1047408
DMA zone: 56 pages used for memmap
DMA zone: 107 pages reserved
DMA zone: 3821 pages, LIFO batch:0
DMA32 zone: 14280 pages used for memmap
DMA32 zone: 832536 pages, LIFO batch:31
Normal zone: 2688 pages used for memmap
Normal zone: 193920 pages, LIFO batch:31
ACPI: PM-Timer IO Port: 0x408
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x02] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x04] enabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x06] enabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x01] enabled)
ACPI: LAPIC (acpi_id[0x05] lapic_id[0x03] enabled)
ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled)
ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled)
ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x04] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x05] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x8086a201 base: 0xfed00000
SMP: Allowing 8 CPUs, 0 hotplug CPUs
nr_irqs_gsi: 24
PM: Registered nosave memory: 0000000000001000 - 0000000000010000
PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
PM: Registered nosave memory: 00000000cfbe0000 - 00000000cfbe1000
PM: Registered nosave memory: 00000000cfbe1000 - 00000000cfbf0000
PM: Registered nosave memory: 00000000cfbf0000 - 00000000cfc00000
PM: Registered nosave memory: 00000000cfc00000 - 00000000f4000000
PM: Registered nosave memory: 00000000f4000000 - 00000000f8000000
PM: Registered nosave memory: 00000000f8000000 - 00000000fec00000
PM: Registered nosave memory: 00000000fec00000 - 0000000100000000
Allocating PCI resources starting at cfc00000 (gap: cfc00000:24400000)
Booting paravirtualized kernel on bare hardware
setup_percpu: NR_CPUS:16 nr_cpumask_bits:16 nr_cpu_ids:8 nr_node_ids:1
PERCPU: Embedded 29 pages/cpu @ffff880005400000 s89176 r8192 d21416 u262144
pcpu-alloc: s89176 r8192 d21416 u262144 alloc=1*2097152
pcpu-alloc: [0] 0 1 2 3 4 5 6 7
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1030277
Kernel command line: root=/dev/array/root ro
PID hash table entries: 4096 (order: 3, 32768 bytes)
Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Checking aperture...
No AGP bridge found
Calgary: detecting Calgary via BIOS EBDA area
Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Memory: 4046176k/4980736k available (3449k kernel code, 791104k absent, 142528k reserved, 1818k data, 480k init)
SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:768
Console: colour VGA+ 80x25
console [tty0] enabled
allocated 41943040 bytes of page_cgroup
please try 'cgroup_disable=memory' option if you don't want memory cgroups
hpet clockevent registered
Fast TSC calibration using PIT
Detected 1998.531 MHz processor.
Calibrating delay loop (skipped), value calculated using timer frequency.. 3998.60 BogoMIPS (lpj=6661770)
Security Framework initialized
Mount-cache hash table entries: 256
Initializing cgroup subsys ns
Initializing cgroup subsys cpuacct
Initializing cgroup subsys memory
Initializing cgroup subsys devices
Initializing cgroup subsys freezer
Initializing cgroup subsys net_cls
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
mce: CPU supports 9 MCE banks
CPU0: Thermal monitoring enabled (TM1)
CPU 0 MCA banks CMCI:2 CMCI:3 CMCI:5 CMCI:6 CMCI:8
using mwait in idle threads.
Performance Events: Nehalem/Corei7 events, Intel PMU driver.
... version: 3
... bit width: 48
... generic registers: 4
... value mask: 0000ffffffffffff
... max period: 000000007fffffff
... fixed-purpose events: 3
... event mask: 000000070000000f
ACPI: Core revision 20091214
Setting APIC routing to flat
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
CPU0: Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz stepping 05
Booting Node 0, Processors #1
CPU 1 MCA banks CMCI:2 CMCI:3 CMCI:5 SHD:6 SHD:8
#2
CPU 2 MCA banks CMCI:2 CMCI:3 CMCI:5 SHD:6 SHD:8
#3
CPU 3 MCA banks CMCI:2 CMCI:3 CMCI:5 SHD:6 SHD:8
#4
CPU 4 MCA banks SHD:2 SHD:3 SHD:5 SHD:6 SHD:8
#5
CPU 5 MCA banks SHD:2 SHD:3 SHD:5 SHD:6 SHD:8
#6
CPU 6 MCA banks SHD:2 SHD:3 SHD:5 SHD:6 SHD:8
#7 Ok.
CPU 7 MCA banks SHD:2 SHD:3 SHD:5 SHD:6 SHD:8
Brought up 8 CPUs
Total of 8 processors activated (31988.63 BogoMIPS).
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf4000000-0xf7ffffff] (base 0xf4000000)
PCI: MMCONFIG at [mem 0xf4000000-0xf7ffffff] reserved in E820
PCI: Using configuration type 1 for base access
bio: create slab <bio-0> at 0
ACPI: EC: Look up EC in DSDT
ACPI: Interpreter enabled
ACPI: (supports S0 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI Warning: Incorrect checksum in table [TAMG] - 10, should be 0F (20091214/tbutils-314)
ACPI: No dock devices found.
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci_root PNP0A03:00: ignoring host bridge windows from ACPI; boot with "pci=use_crs" to use them
pci_root PNP0A03:00: host bridge window [io 0x0000-0x0cf7] (ignored)
pci_root PNP0A03:00: host bridge window [io 0x0d00-0xffff] (ignored)
pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff] (ignored)
pci_root PNP0A03:00: host bridge window [mem 0x000c0000-0x000dffff] (ignored)
pci_root PNP0A03:00: host bridge window [mem 0xcfc00000-0xfebfffff] (ignored)
pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
pci 0000:00:03.0: PME# disabled
pci 0000:00:1a.0: reg 20: [io 0xff00-0xff1f]
pci 0000:00:1a.1: reg 20: [io 0xfe00-0xfe1f]
pci 0000:00:1a.2: reg 20: [io 0xfd00-0xfd1f]
pci 0000:00:1a.7: reg 10: [mem 0xfbfff000-0xfbfff3ff]
pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1a.7: PME# disabled
pci 0000:00:1b.0: reg 10: [mem 0xfbff8000-0xfbffbfff 64bit]
pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1b.0: PME# disabled
pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.0: PME# disabled
pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.1: PME# disabled
pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.2: PME# disabled
pci 0000:00:1d.0: reg 20: [io 0xfc00-0xfc1f]
pci 0000:00:1d.1: reg 20: [io 0xfb00-0xfb1f]
pci 0000:00:1d.2: reg 20: [io 0xfa00-0xfa1f]
pci 0000:00:1d.3: reg 20: [io 0xf900-0xf91f]
pci 0000:00:1d.7: reg 10: [mem 0xfbffe000-0xfbffe3ff]
pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1d.7: PME# disabled
pci 0000:00:1f.2: reg 10: [io 0xf800-0xf807]
pci 0000:00:1f.2: reg 14: [io 0xf700-0xf703]
pci 0000:00:1f.2: reg 18: [io 0xf600-0xf607]
pci 0000:00:1f.2: reg 1c: [io 0xf500-0xf503]
pci 0000:00:1f.2: reg 20: [io 0xf400-0xf40f]
pci 0000:00:1f.2: reg 24: [io 0xf300-0xf30f]
pci 0000:00:1f.3: reg 10: [mem 0xfbffd000-0xfbffd0ff 64bit]
pci 0000:00:1f.3: reg 20: [io 0x0500-0x051f]
pci 0000:00:1f.5: reg 10: [io 0xf100-0xf107]
pci 0000:00:1f.5: reg 14: [io 0xf000-0xf003]
pci 0000:00:1f.5: reg 18: [io 0xef00-0xef07]
pci 0000:00:1f.5: reg 1c: [io 0xee00-0xee03]
pci 0000:00:1f.5: reg 20: [io 0xed00-0xed0f]
pci 0000:00:1f.5: reg 24: [io 0xec00-0xec0f]
pci 0000:01:00.0: reg 10: [mem 0xf9000000-0xf9ffffff]
pci 0000:01:00.0: reg 14: [mem 0xd0000000-0xdfffffff 64bit pref]
pci 0000:01:00.0: reg 1c: [mem 0xee000000-0xefffffff 64bit pref]
pci 0000:01:00.0: reg 24: [io 0xcf00-0xcf7f]
pci 0000:01:00.0: reg 30: [mem 0x00000000-0x0007ffff pref]
pci 0000:01:00.1: reg 10: [mem 0xfaffc000-0xfaffffff]
pci 0000:00:03.0: PCI bridge to [bus 01-01]
pci 0000:00:03.0: bridge window [io 0xc000-0xcfff]
pci 0000:00:03.0: bridge window [mem 0xf9000000-0xfaffffff]
pci 0000:00:03.0: bridge window [mem 0xd0000000-0xefffffff 64bit pref]
pci 0000:02:00.0: reg 10: [io 0xaf00-0xaf07]
pci 0000:02:00.0: reg 14: [io 0xae00-0xae03]
pci 0000:02:00.0: reg 18: [io 0xad00-0xad07]
pci 0000:02:00.0: reg 1c: [io 0xac00-0xac03]
pci 0000:02:00.0: reg 20: [io 0xab00-0xab0f]
pci 0000:02:00.0: reg 24: [mem 0xfbcff000-0xfbcff7ff]
pci 0000:02:00.0: reg 30: [mem 0x00000000-0x0000ffff pref]
pci 0000:02:00.0: PME# supported from D3hot
pci 0000:02:00.0: PME# disabled
pci 0000:00:1c.0: PCI bridge to [bus 02-02]
pci 0000:00:1c.0: bridge window [io 0xa000-0xafff]
pci 0000:00:1c.0: bridge window [mem 0xfbc00000-0xfbcfffff]
pci 0000:03:00.0: reg 10: [io 0xde00-0xdeff]
pci 0000:03:00.0: reg 18: [mem 0xfbeff000-0xfbefffff 64bit pref]
pci 0000:03:00.0: reg 20: [mem 0xfbef8000-0xfbefbfff 64bit pref]
pci 0000:03:00.0: reg 30: [mem 0x00000000-0x0001ffff pref]
pci 0000:03:00.0: supports D1 D2
pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:03:00.0: PME# disabled
pci 0000:00:1c.1: PCI bridge to [bus 03-03]
pci 0000:00:1c.1: bridge window [io 0xd000-0xdfff]
pci 0000:00:1c.1: bridge window [mem 0xfbb00000-0xfbbfffff]
pci 0000:00:1c.1: bridge window [mem 0xfbe00000-0xfbefffff 64bit pref]
pci 0000:04:00.0: reg 10: [mem 0xfbdfe000-0xfbdfffff 64bit]
pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
pci 0000:04:00.0: PME# disabled
pci 0000:00:1c.2: PCI bridge to [bus 04-04]
pci 0000:00:1c.2: bridge window [mem 0xfbd00000-0xfbdfffff]
pci 0000:05:05.0: reg 10: [io 0xbf00-0xbf07]
pci 0000:05:05.0: reg 14: [io 0xbe00-0xbe03]
pci 0000:05:05.0: reg 18: [io 0xbd00-0xbd07]
pci 0000:05:05.0: reg 1c: [io 0xbc00-0xbc03]
pci 0000:05:05.0: reg 20: [io 0xbb00-0xbb0f]
pci 0000:00:1e.0: PCI bridge to [bus 05-05] (subtractive decode)
pci 0000:00:1e.0: bridge window [io 0xb000-0xbfff]
pci_bus 0000:00: on NUMA node 0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX1._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 11 *12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs *3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
vgaarb: loaded
PCI: Using ACPI for IRQ routing
PCI: pci_cache_line_size set to 64 bytes
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
HPET: 8 timers in total, 5 timers will be used for per-cpu timer
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 24, 25, 26, 27, 28, 0
hpet0: 8 comparators, 64-bit 14.318180 MHz counter
hpet: hpet2 irq 24 for MSI
hpet: hpet3 irq 25 for MSI
hpet: hpet4 irq 26 for MSI
hpet: hpet5 irq 27 for MSI
hpet: hpet6 irq 28 for MSI
Switching to clocksource tsc
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 14 devices
ACPI: ACPI bus type pnp unregistered
system 00:01: [io 0x04d0-0x04d1] has been reserved
system 00:01: [io 0x0290-0x029f] has been reserved
system 00:01: [io 0x0800-0x087f] has been reserved
system 00:01: [io 0x0290-0x0294] has been reserved
system 00:01: [io 0x0880-0x088f] has been reserved
system 00:0a: [io 0x0400-0x04cf] has been reserved
system 00:0a: [io 0x04d2-0x04ff] has been reserved
system 00:0b: [mem 0xf4000000-0xf7ffffff] has been reserved
system 00:0c: [mem 0x000cd600-0x000cffff] has been reserved
system 00:0c: [mem 0x000f0000-0x000f7fff] could not be reserved
system 00:0c: [mem 0x000f8000-0x000fbfff] could not be reserved
system 00:0c: [mem 0x000fc000-0x000fffff] could not be reserved
system 00:0c: [mem 0xcfbe0000-0xcfbeffff] could not be reserved
system 00:0c: [mem 0x00000000-0x0009ffff] could not be reserved
system 00:0c: [mem 0x00100000-0xcfbdffff] could not be reserved
system 00:0c: [mem 0xcfbf0000-0xcfbfffff] has been reserved
system 00:0c: [mem 0xfec00000-0xfec00fff] could not be reserved
system 00:0c: [mem 0xfed10000-0xfed1dfff] has been reserved
system 00:0c: [mem 0xfed20000-0xfed8ffff] has been reserved
system 00:0c: [mem 0xfee00000-0xfee00fff] has been reserved
system 00:0c: [mem 0xffb00000-0xffb7ffff] has been reserved
system 00:0c: [mem 0xfff00000-0xffffffff] has been reserved
system 00:0c: [mem 0x000e0000-0x000effff] has been reserved
pci 0000:00:1c.0: BAR 15: assigned [mem 0xf0000000-0xf01fffff pref]
pci 0000:00:1c.2: BAR 15: assigned [mem 0xf0200000-0xf03fffff 64bit pref]
pci 0000:00:1c.2: BAR 13: assigned [io 0x1000-0x1fff]
pci 0000:01:00.0: BAR 6: assigned [mem 0xe0000000-0xe007ffff pref]
pci 0000:00:03.0: PCI bridge to [bus 01-01]
pci 0000:00:03.0: bridge window [io 0xc000-0xcfff]
pci 0000:00:03.0: bridge window [mem 0xf9000000-0xfaffffff]
pci 0000:00:03.0: bridge window [mem 0xd0000000-0xefffffff 64bit pref]
pci 0000:02:00.0: BAR 6: assigned [mem 0xf0000000-0xf000ffff pref]
pci 0000:00:1c.0: PCI bridge to [bus 02-02]
pci 0000:00:1c.0: bridge window [io 0xa000-0xafff]
pci 0000:00:1c.0: bridge window [mem 0xfbc00000-0xfbcfffff]
pci 0000:00:1c.0: bridge window [mem 0xf0000000-0xf01fffff pref]
pci 0000:03:00.0: BAR 6: assigned [mem 0xfbe00000-0xfbe1ffff pref]
pci 0000:00:1c.1: PCI bridge to [bus 03-03]
pci 0000:00:1c.1: bridge window [io 0xd000-0xdfff]
pci 0000:00:1c.1: bridge window [mem 0xfbb00000-0xfbbfffff]
pci 0000:00:1c.1: bridge window [mem 0xfbe00000-0xfbefffff 64bit pref]
pci 0000:00:1c.2: PCI bridge to [bus 04-04]
pci 0000:00:1c.2: bridge window [io 0x1000-0x1fff]
pci 0000:00:1c.2: bridge window [mem 0xfbd00000-0xfbdfffff]
pci 0000:00:1c.2: bridge window [mem 0xf0200000-0xf03fffff 64bit pref]
pci 0000:00:1e.0: PCI bridge to [bus 05-05]
pci 0000:00:1e.0: bridge window [io 0xb000-0xbfff]
pci 0000:00:1e.0: bridge window [mem disabled]
pci 0000:00:1e.0: bridge window [mem pref disabled]
pci 0000:00:03.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:03.0: setting latency timer to 64
pci 0000:00:1c.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:1c.0: setting latency timer to 64
pci 0000:00:1c.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
pci 0000:00:1c.1: setting latency timer to 64
pci 0000:00:1c.2: enabling device (0006 -> 0007)
pci 0000:00:1c.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
pci 0000:00:1c.2: setting latency timer to 64
pci 0000:00:1e.0: setting latency timer to 64
pci_bus 0000:00: resource 0 [io 0x0000-0xffff]
pci_bus 0000:00: resource 1 [mem 0x00000000-0xffffffffffffffff]
pci_bus 0000:01: resource 0 [io 0xc000-0xcfff]
pci_bus 0000:01: resource 1 [mem 0xf9000000-0xfaffffff]
pci_bus 0000:01: resource 2 [mem 0xd0000000-0xefffffff 64bit pref]
pci_bus 0000:02: resource 0 [io 0xa000-0xafff]
pci_bus 0000:02: resource 1 [mem 0xfbc00000-0xfbcfffff]
pci_bus 0000:02: resource 2 [mem 0xf0000000-0xf01fffff pref]
pci_bus 0000:03: resource 0 [io 0xd000-0xdfff]
pci_bus 0000:03: resource 1 [mem 0xfbb00000-0xfbbfffff]
pci_bus 0000:03: resource 2 [mem 0xfbe00000-0xfbefffff 64bit pref]
pci_bus 0000:04: resource 0 [io 0x1000-0x1fff]
pci_bus 0000:04: resource 1 [mem 0xfbd00000-0xfbdfffff]
pci_bus 0000:04: resource 2 [mem 0xf0200000-0xf03fffff 64bit pref]
pci_bus 0000:05: resource 0 [io 0xb000-0xbfff]
pci_bus 0000:05: resource 3 [io 0x0000-0xffff]
pci_bus 0000:05: resource 4 [mem 0x00000000-0xffffffffffffffff]
NET: Registered protocol family 2
IP route cache hash table entries: 131072 (order: 8, 1048576 bytes)
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
UDP hash table entries: 2048 (order: 4, 65536 bytes)
UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
NET: Registered protocol family 1
pci 0000:01:00.0: Boot video device
PCI: CLS 64 bytes, default 64
Unpacking initramfs...
Freeing initrd memory: 2699k freed
PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Placing 64MB software IO TLB between ffff880005bdd000 - ffff880009bdd000
software IO TLB at phys 0x5bdd000 - 0x9bdd000
Scanning for low memory corruption every 60 seconds
audit: initializing netlink socket (disabled)
type=2000 audit(1272807521.273:1): initialized
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
msgmni has been set to 7909
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
pcieport 0000:00:03.0: setting latency timer to 64
pcieport 0000:00:03.0: irq 29 for MSI/MSI-X
pcieport 0000:00:1c.0: setting latency timer to 64
pcieport 0000:00:1c.0: irq 30 for MSI/MSI-X
pcieport 0000:00:1c.1: setting latency timer to 64
pcieport 0000:00:1c.1: irq 31 for MSI/MSI-X
pcieport 0000:00:1c.2: setting latency timer to 64
pcieport 0000:00:1c.2: irq 32 for MSI/MSI-X
aer 0000:00:03.0:pcie02: AER service couldn't init device: no _OSC support
Linux agpgart interface v0.103
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
input: Macintosh mouse button emulation as /devices/virtual/input/input0
PNP: No PS/2 controller found. Probing ports directly.
Failed to disable AUX port, but continuing anyway... Is this a SiS?
If AUX port is really absent please use the 'i8042.noaux' option.
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
cpuidle: using governor ladder
cpuidle: using governor menu
TCP cubic registered
NET: Registered protocol family 17
PM: Resume from disk failed.
registered taskstats version 1
Initalizing network drop monitor service
Freeing unused kernel memory: 480k freed
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.17.0-ioctl (2010-03-05) initialised: [email protected]
SCSI subsystem initialized
libata version 3.00 loaded.
pata_it8213 0000:05:05.0: version 0.0.3
pata_it8213 0000:05:05.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
pata_it8213 0000:05:05.0: setting latency timer to 64
scsi0 : pata_it8213
scsi1 : pata_it8213
ata1: PATA max UDMA/66 cmd 0xbf00 ctl 0xbe00 bmdma 0xbb00 irq 19
ata2: DUMMY
ata_piix 0000:00:1f.2: version 2.13
ata_piix 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
ata_piix 0000:00:1f.2: setting latency timer to 64
scsi2 : ata_piix
scsi3 : ata_piix
ata3: SATA max UDMA/133 cmd 0xf800 ctl 0xf700 bmdma 0xf400 irq 19
ata4: SATA max UDMA/133 cmd 0xf600 ctl 0xf500 bmdma 0xf408 irq 19
ata_piix 0000:00:1f.5: PCI INT B -> GSI 19 (level, low) -> IRQ 19
ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ]
ata_piix 0000:00:1f.5: setting latency timer to 64
scsi4 : ata_piix
scsi5 : ata_piix
ata5: SATA max UDMA/133 cmd 0xf100 ctl 0xf000 bmdma 0xed00 irq 19
ata6: SATA max UDMA/133 cmd 0xef00 ctl 0xee00 bmdma 0xed08 irq 19
ata6: SATA link down (SStatus 0 SControl 300)
ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata5.00: ATAPI: HL-DT-ST BDDVDRW CH08LS10, 1.00, max UDMA/133
ata5.00: configured for UDMA/133
ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.01: SATA link down (SStatus 0 SControl 300)
ata4.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata4.01: SATA link down (SStatus 0 SControl 300)
ata3.00: ATA-8: WDC WD15EARS-00Z5B1, 80.00A80, max UDMA/133
ata3.00: 2930277168 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata3.00: configured for UDMA/133
scsi 2:0:0:0: Direct-Access ATA WDC WD15EARS-00Z 80.0 PQ: 0 ANSI: 5
ata4.00: ATA-8: WDC WD15EARS-00Z5B1, 80.00A80, max UDMA/133
ata4.00: 2930277168 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata4.00: configured for UDMA/133
scsi 3:0:0:0: Direct-Access ATA WDC WD15EARS-00Z 80.0 PQ: 0 ANSI: 5
scsi 4:0:0:0: CD-ROM HL-DT-ST BDDVDRW CH08LS10 1.00 PQ: 0 ANSI: 5
sd 2:0:0:0: [sda] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
sd 3:0:0:0: [sdb] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
sd 3:0:0:0: [sdb] Write Protect is off
sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdb:
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1 sda2 sda3
sd 2:0:0:0: [sda] Attached SCSI disk
sdb1 sdb2 sdb3
sd 3:0:0:0: [sdb] Attached SCSI disk
sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 4:0:0:0: Attached scsi CD-ROM sr0
md: md0 stopped.
md: bind<sdb1>
md: bind<sda1>
md: raid1 personality registered for level 1
raid1: raid set md0 active with 2 out of 2 mirrors
md0: detected capacity change from 0 to 295960576
md0: unknown partition table
md: md1 stopped.
md: bind<sdb2>
md: bind<sda2>
raid1: raid set md1 active with 2 out of 2 mirrors
md1: detected capacity change from 0 to 1497954975744
md1: unknown partition table
md: md2 stopped.
md: bind<sdb3>
md: bind<sda3>
raid1: raid set md2 active with 2 out of 2 mirrors
md2: detected capacity change from 0 to 2048000000
md2: unknown partition table
EXT4-fs (dm-0): mounted filesystem with ordered data mode
rtc_cmos 00:04: RTC can wake from S4
rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one month, 242 bytes nvram, hpet irqs
udev: starting version 151
sd 2:0:0:0: Attached scsi generic sg0 type 0
sd 3:0:0:0: Attached scsi generic sg1 type 0
sr 4:0:0:0: Attached scsi generic sg2 type 5
iTCO_vendor_support: vendor-support=0
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.05
iTCO_wdt: Found a P55 TCO device (Version=2, TCOBASE=0x0460)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
Monitor-Mwait will be used to enter C-1 state
Monitor-Mwait will be used to enter C-2 state
Monitor-Mwait will be used to enter C-3 state
ahci 0000:02:00.0: version 3.0
ahci 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
ahci 0000:02:00.0: irq 33 for MSI/MSI-X
ahci 0000:02:00.0: AHCI 0001.0200 32 slots 8 ports 6 Gbps 0xff impl SATA mode
ahci 0000:02:00.0: flags: 64bit ncq pio
ahci 0000:02:00.0: setting latency timer to 64
scsi6 : ahci
scsi7 : ahci
scsi8 : ahci
scsi9 : ahci
scsi10 : ahci
scsi11 : ahci
scsi12 : ahci
scsi13 : ahci
ata7: SATA max UDMA/133 abar m2048@0xfbcff000 port 0xfbcff100 irq 33
ata8: SATA max UDMA/133 abar m2048@0xfbcff000 port 0xfbcff180 irq 33
ata9: SATA max UDMA/133 abar m2048@0xfbcff000 port 0xfbcff200 irq 33
ata10: SATA max UDMA/133 abar m2048@0xfbcff000 port 0xfbcff280 irq 33
ata11: SATA max UDMA/133 abar m2048@0xfbcff000 port 0xfbcff300 irq 33
ata12: SATA max UDMA/133 abar m2048@0xfbcff000 port 0xfbcff380 irq 33
ata13: SATA max UDMA/133 abar m2048@0xfbcff000 port 0xfbcff400 irq 33
ata14: SATA max UDMA/133 abar m2048@0xfbcff000 port 0xfbcff480 irq 33
input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
ACPI: Power Button [PWRB]
input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
ACPI: Power Button [PWRF]
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
ata13: SATA link down (SStatus 0 SControl 300)
ata8: SATA link down (SStatus 0 SControl 300)
ata10: SATA link down (SStatus 0 SControl 300)
ata14: SATA link up <unknown> (SStatus FFFFFF93 SControl 300)
ata9: SATA link down (SStatus 0 SControl 300)
ata12: SATA link down (SStatus 0 SControl 300)
ata11: SATA link down (SStatus 0 SControl 300)
ata7: SATA link down (SStatus 0 SControl 300)
ata14.00: ATAPI: MARVELL VIRTUALL, 1.09, max UDMA/66
ata14.00: configured for UDMA/66
scsi 13:0:0:0: Processor Marvell 91xx Config 1.01 PQ: 0 ANSI: 5
scsi 13:0:0:0: Attached scsi generic sg3 type 3
nvidia: module license 'NVIDIA' taints kernel.
Disabling lock debugging due to kernel taint
parport_pc 00:09: reported by Plug and Play ACPI
parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
Floppy drive(s): fd0 is 1.44M
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18
ehci_hcd 0000:00:1a.7: setting latency timer to 64
ehci_hcd 0000:00:1a.7: EHCI Host Controller
ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1a.7: debug port 2
ehci_hcd 0000:00:1a.7: cache line size of 64 is not supported
ehci_hcd 0000:00:1a.7: irq 18, io mem 0xfbfff000
xhci_hcd 0000:04:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
xhci_hcd 0000:04:00.0: setting latency timer to 64
xhci_hcd 0000:04:00.0: xHCI Host Controller
xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 2
xhci_hcd 0000:04:00.0: irq 18, io mem 0xfbdfe000
usb usb2: config 1 interface 0 altsetting 0 endpoint 0x81 has no SuperSpeed companion descriptor
xHCI xhci_add_endpoint called for root hub
xHCI xhci_check_bandwidth called for root hub
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 4 ports detected
r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
r8169 0000:03:00.0: setting latency timer to 64
r8169 0000:03:00.0: irq 34 for MSI/MSI-X
eth0: RTL8168d/8111d at 0xffffc90000068000, 6c:f0:49:02:e2:c1, XID 083000c0 IRQ 34
FDC 0 is a post-1991 82077
lp: driver loaded but no devices found
ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
ehci_hcd 0000:00:1d.7: setting latency timer to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 3
ehci_hcd 0000:00:1d.7: debug port 2
ehci_hcd 0000:00:1d.7: cache line size of 64 is not supported
ehci_hcd 0000:00:1d.7: irq 23, io mem 0xfbffe000
uhci_hcd: USB Universal Host Controller Interface driver
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 8 ports detected
i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
uhci_hcd 0000:00:1a.0: setting latency timer to 64
uhci_hcd 0000:00:1a.0: UHCI Host Controller
uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1a.0: irq 16, io base 0x0000ff00
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
uhci_hcd 0000:00:1a.1: setting latency timer to 64
uhci_hcd 0000:00:1a.1: UHCI Host Controller
uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1a.1: irq 21, io base 0x0000fe00
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
uhci_hcd 0000:00:1a.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
uhci_hcd 0000:00:1a.2: setting latency timer to 64
uhci_hcd 0000:00:1a.2: UHCI Host Controller
uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 6
uhci_hcd 0000:00:1a.2: irq 18, io base 0x0000fd00
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
uhci_hcd 0000:00:1d.0: setting latency timer to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 7
uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000fc00
hub 7-0:1.0: USB hub found
hub 7-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
uhci_hcd 0000:00:1d.1: setting latency timer to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 8
uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000fb00
hub 8-0:1.0: USB hub found
hub 8-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
uhci_hcd 0000:00:1d.2: setting latency timer to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 9
uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000fa00
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.3: PCI INT D -> GSI 16 (level, low) -> IRQ 16
uhci_hcd 0000:00:1d.3: setting latency timer to 64
uhci_hcd 0000:00:1d.3: UHCI Host Controller
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 10
uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000f900
hub 10-0:1.0: USB hub found
hub 10-0:1.0: 2 ports detected
ppdev: user-space parallel port driver
lp0: using parport0 (interrupt-driven).
HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
HDA Intel 0000:00:1b.0: irq 35 for MSI/MSI-X
HDA Intel 0000:00:1b.0: setting latency timer to 64
input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input3
HDA Intel 0000:01:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
hda_intel: Disable MSI for Nvidia chipset
HDA Intel 0000:01:00.1: setting latency timer to 64
usb 9-2: new low speed USB device using uhci_hcd and address 2
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nvidia 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
nvidia 0000:01:00.0: setting latency timer to 64
vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
NVRM: loading NVIDIA UNIX x86_64 Kernel Module 195.36.15 Fri Mar 12 00:29:13 PST 2010
input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.2/usb9/9-2/9-2:1.0/input/input4
logitech 0003:046D:C517.0001: input,hidraw0: USB HID v1.10 Keyboard [Logitech USB Receiver] on usb-0000:00:1d.2-2/input0
logitech 0003:046D:C517.0002: fixing up Logitech keyboard report descriptor
input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.2/usb9/9-2/9-2:1.1/input/input5
logitech 0003:046D:C517.0002: input,hiddev0,hidraw1: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:1d.2-2/input1
kjournald starting. Commit interval 5 seconds
EXT3-fs (md0): using internal journal
EXT3-fs (md0): mounted filesystem with writeback data mode
Adding 1999992k swap on /dev/md2. Priority:-1 extents:1 across:1999992k
r8169: eth0: link up
r8169: eth0: link up
it87: Found IT8720F chip at 0x290, revision 8
it87: VID is disabled (pins used for GPIO)
it87: in3 is VCC (+5V)
fuse init (API version 7.13)
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
/etc/mdadm.conf
ARRAY /dev/md0 metadata=0.90 UUID=d3dade34:d68c8182:644d3026:471d4918
ARRAY /dev/md1 metadata=0.90 UUID=c8e3ea5d:7be896ac:a45d145b:781c14fa
ARRAY /dev/md2 metadata=0.90 UUID=5c868358:21748aa6:5b20e486:491c0ca6
# Emails sent on faults
MAILADDR [myemailaddress]
/proc/mdstat
Personalities : [raid1]
md2 : active raid1 sda3[0] sdb3[1]
2000000 blocks [2/2] [UU]
md1 : active raid1 sda2[0] sdb2[1]
1462846656 blocks [2/2] [UU]
md0 : active raid1 sda1[0] sdb1[1]
289024 blocks [2/2] [UU]
unused devices: <none>
Also I am not sure about the "unknown partition table" messages in the dmesg output. I am not sure if they are somthing I should be concerned about or could be a contributing factor.
If you need more information about my problem just ask an I will post it.
Last edited by KrimReaper (2010-08-05 18:44:01)

I have been doing some searching around and have found some new information.
https://raid.wiki.kernel.org/index.php/Performance
I found there were some fixes for the "apparent pauses in the stream of IO" that I believed I was experiencing as well. I had in the meantime changed my raid array to raid 5 to increase the read performance which had helped with my lag issue but it was still apparent. So I did two of the optimizations listed on the page. But before I did I ran a benchamark on my current raid 5 array.
Unoptimized Raid 5 array
Version 1.03e ------Sequential Output------ --Sequential Input- --Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
media 8G 43161 66 34106 4 19897 1 48765 65 156367 7 412.4 1
------Sequential Create------ --------Random Create--------
-Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP
16 +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++
media,8G,43161,66,34106,4,19897,1,48765,65,156367,7,412.4,1,16,+++++,+++,+++++,+++,+++++,+++,+++++,+++,+++++,+++,+++++,+++
Set read-ahead from 512 to 65536 on all md devices, seems to be a minor improvement
Version 1.03e ------Sequential Output------ --Sequential Input- --Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
media 8G 38289 58 36708 4 22971 2 70054 93 185402 5 407.9 1
------Sequential Create------ --------Random Create--------
-Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP
16 +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++
media,8G,38289,58,36708,4,22971,2,70054,93,185402,5,407.9,1,16,+++++,+++,+++++,+++,+++++,+++,+++++,+++,+++++,+++,+++++,+++
Set stripe-cache_size for RAID5 from 512 to 16384, massive improvement
Version 1.03e ------Sequential Output------ --Sequential Input- --Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
media 8G 65835 98 126321 11 48050 4 70850 95 184347 5 370.4 1
------Sequential Create------ --------Random Create--------
-Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP
16 +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++
media,8G,65835,98,126321,11,48050,4,70850,95,184347,5,370.4,1,16,+++++,+++,+++++,+++,+++++,+++,+++++,+++,+++++,+++,+++++,+++
After changing the stripe cache size it looks like there has been a massive improvement in output speeds. Though I have not used the desktop environment of the computer yet nor have I been watching movies/downloading or doing anything I/O heavy yet of this change. I think this may have been the root of my problem. When I have used the computer for a few more weeks I will report here again whether or not lag/pause problem has been solved.

WinXP-64 bit corrupts existing RAID array

I've got an MSI K8N Neo2 Platinum motherboard running Win XP Pro SP2 on two 36 gig SATA Raptors. Everything was working fine, but I wanted to try the 64 bit version of XP. Grabbed an old 80 gig PATA drive and threw that in the case. Unplugged the SATA drives so as not to risk messing with the existing working OS. Installed the latest 1218 x64 beta and it worked well.
The problem was that when I shut down and reconnected my old RAID array, windows wouldn't boot from it. I lost everything and had to rebuild Windows from scratch. So now I know to never unplug the SATA drives
Rebuilt WinXP on the RAID array and then tried rebooting with the PATA drive with the 64 bit OS. Came up with the "drive needs checking" screen, and proceeds to "fix" the RAID array while ignoring my frantic pounding on the Logitech USB keyboard to stop. Rebooted and yes, the new install was nuked. Okay, since it's gone anyway, reboot to the 64 bit OS and make sure it's got the 64 bit RAID drivers installed.
Reinstall WinXP on the RAID array, reboot to the 64 bit OS on the other drive and the same old scandisk comes and nukes it AGAIN!
So now the PATA drive is sitting on the shelf again, unless someone here can suggest what is causing this problem.
System Specs
Athlon64 3500
gig of PQI 3200 at 2-2-2-5 2.6
2x36 gig Raptors on ports 3-4
Plextor PX-716a DVD+_RW
Visiontek X800 Pro.

The first time you re-installed Win 32 on the raid that was a bit drastic. A repair ought to have done the job.
The problem was probably that you disconnected the array but that's where the boot.ini was and that file needed to be modified to add the path to the Win64 install.
Since you took out the array the Win64 install created a new boot.ini on the PATA drive. Even when you tell BIOS to boot off the array, Windows has a bad habit of looking at the IDE channels & using the boot.ini if it finds one there - but the file it found didn't point to the array of course.
So basically if you already have Win32 on the array I would leave that array connected normally when installing Win64 on the PATA drive and all should be well.
I've installed Win64 on the same array as my Win32 install and they co-exist happily. I reckon that's the most efficient way to do it. The main thing is to make separate partitions for Win32, Win64 and data files when you install Win32 in the first place. The two OSs can share the same data files, incuding stuff like email.

Is It Possible to Clone RAID Array in a Safe and Easy Way?

Why do computer users need to clone RAID array, especially Windows Server users need to do RAID cloning? Generally speaking, they need to clone RAID array regularly in order to upgrade disk or migrate data from small disk to a larger one. A typical
example is that when the partitions on the hardware RAID runs out of space, you may prefer to rebuild the hardware RAID with larger hard disks. Then, you need to backup the data to another place, rebuild the hardware RAID and restore data again.
What a time-consuming task!
Is it possible to clone RAID array in a safe and easy way? The answer is yes and this article will introduce a RAID cloning software.

Hi jiangchunli,
Were you looking to post this question in some other forum? This looks like related to RAID and Disk upgrades.
This forum is meant for
http://www.windowsazure.com/en-us/services/recovery-manager/
Please let us know if this is indeed Hyper-V Recovery Manager related so we can help better.
Thanks
Praveen
Praveen/ www.PraveenKumar.in

RAID Arrays and WinXP Home

OK... I tried upgrading to Win XP 64-bit, but found there were games and applications that were screwy there and some items without 64-bit drivers, etc. So, I rolled back to a clean install of XP Home (32-bit).
After much effort, I was told today at a local techie-store that XP Home "doesn't allow for RAID arrays."
True?
I have 2 Hitachi 160GB drives I got last week at the afore-mentioned store for $112 US total! So, I am trying to make it all work, but am having no luck.
Any thoughts?
Scott in Los Angeles

There is a way to make some versions of windows do a software RAID, but the MSI board has a VIA and a Promise hardware array. Don't worry about what the 'techie' said.
Enable Promise controller in BIOS and set it for RAID.
Press Ctrl & F when prompted to set up your RAID array.
Boot to Windows CD
Press F6 when prompted and insert your Promise RAID disk.
Enjoy!

KT4 Ultra: problem config. raid array IDE3

I owe the MSI 6590 KT4 Ultra BSR mainboard and I have difficulties configurring the RAID array in striping mode, on the IDE3 controller.
The manual describes on page 2-18 it's possible to connect up to 2 hard drives, cdrom, 120mb fd and other devices to the IDE3 controller.
Unfortunately only one of my two MAXTOR D740X-6L (6L080J4) 80gig drives is recognized by the array.
One Maxtor hard drive is jumpered as MASTER and the other is set up as SLAVE.
When I hook up the cable to an ordinary IDE port (eg IDE1) the two drives are properly recognized.
Both drives can be formatted using the regular IDE ports, this means without any cluster errors or other errors so the drives are physically OK.
Before I wrote this post I checked the support section again to make sure I am using the latest BIOS which is 1.1. I also downgraded to 1.0, but that didn't solve my problem either.
Since I work in a computer shop now and then I had the opportunity to check two Maxtor Fireball3 30gig drives on a different MS-6590 RAID board (BIOS 1.1.) and exactly the same problem occurs: the 2nd drive won't be recognized in the ARRAY on IDE3.
Please tell me what to do to make the striping option fully work on my two IDENTICAL Maxtor hard drives since MSI support came up with a standard email, which didn't cheer me up at all. Hopefully this time they will investigate this matter since no doubt more people will experience this.

Thanks for the quick response, though it's not satisfactory for me (of course).
Actually before installing the new KT4 Ultra I owed the KT266 Pro RAID motherboard. It's true this board has two controllers for the RAID option. Nevertheless because after reading the manual of this new board I was convinced I could connect two hard drives on the IDE3-channel. This is the reason I decided to go ahead and to upgrade to this new mainboard.
I guess I have to go back to my employer and fall back again to my KT266 (MS6380).

New Builder needs some info K9A Plat. RAID Array help

This is a new build AMD 64x2 6000+, K9A platinum, Lite On DVD Re Writeable SATA, 2x74Gig WD Raptors in Raid 0, Asus X1950 pro Thermaltake 700 W PSU Crossfire cert.
BIOS registered my drives, Built array PC Rebooted, Installing Win XP pro Hit F6 install drivers, Format drives, Then before Install It says that :setup cannot copy the file ahcix86.inf.
If I skip it, it will install XP but when I try to boot from the hard drive It starts to load XP but crashes to the blue screen of death
*** Stop: 0x0000007BC ( 0xF78A2524, 0xC0000034, 0x00000000, 0x00000000)
Has anyone got this error string?
First RAID array I would very much appreciate any help given.

Hi!
Looking at some info on Google and Microsoft site, I cannot find the BC error code, only the error code ending with B. It indicates an error with the boot device. It can be caused by several things.
Check that you are using the correct device drivers to install Windows
Also, check the installation CD. It could be that the disk was damaged and that you are missing a crucial file because of that
You can also try installing Windows again and choose to recover the previous installation.
If this all does not help, try installing Windows on a single HDD (no raid) to see if that will work.

Updating a Hardware RAID array

I'm running a recent Mac Pro model with Hardware RAID and four 1TB SATA drives.
Seagate 1.5TB drives are now available, and they're cheaper than the 1TB drives were just a few months ago.
My Infrant/Netgear ReadyNAS NV+ implements a proprietary form of RAID that they called X-RAID, similar to RAID-5 but with the feature that you can swap larger drives into the array one at a time, and when you're done, the RAID will be re-synced to make use of the additional storage without requiring that you dump and restore the contents of the array. The final re-sync is an admittedly long process (it took three days for mine to update from 4x750GB to 4x1TB) but it's still a very convenient feature.
Does Hardware RAID on Mac OS X have anything like this, i.e. can I replace 1TB drives one at a time with 1.5TB drives and preserve my data? And when I'm done, will the system recognize and use the new storage?
If not, could someone please describe the procedure that I would need to go through in order to achieve this? I presume that I would need to recreate the RAID array entirely, re-install the OS, and then restore the system from my Time Machine backup. But I'm not sure of the details.
I'd appreciate any help with this. Thanks.
An aside: I was more than a little upset a few months ago when I called Apple Support for help with initial setup of my RAID array (I have Apple Care) and was told "Sorry, we don't support Hardware RAID." So Apple was quite happy to sell me an $800 piece of hardware for my lavish new system but didn't bother to tell me at time of purchase that my configuration was "unsupported." It seems a little outrageous to me.
Given Apple's refusal to help me I need to ask the community for help with problems like this.

Hi rrgomes;
Never having heard of X-RAID but going by your comment that is similar to RAID5 I would have to say that you will not be able to upgrade by replacing one disk at a time.
As to no support for the RAID card, I personally would not have taken his word for that. Instead I would have escalated it up through Customer Service just to be sure before I gave up on that point. To me the response you got there sounds bogus.
Allan

Upgrading QT caused my RAID array to drop frames again!

Similar Messages

Maybe you are looking for