10.6.2 Killed My RAID

I just updated my MacPro to 10.6.2 and in the process it destroyed the partition table on my RAID.
Now on startup OSX prompts me to either format, ignore, or eject the RAID.
The RAID Configuration software says all the drives are ok, and the unit is ok, but Disk Utility says there is no partition map.
The RAID is only 2 weeks old. Worked fine this morning, updated to 10.6.2 at lunch and has not worked since.

You have to enter the password "x" twice as well... Something strange with mobileme there.

Similar Messages

10.6.2 upgrade killed software RAID 0 for my Mac Pro - can it be recovered?

I have 4 internal SATA drives in my Mac Pro, one is the boot device, one is the time machine device, the remaining two drives are set up as striped disks (RAID0).
When upgrading from 10.6.1 to 10.6.2, my RAID set was killed by the upgrade process.
I now have very strange output in disk utility, I can see:
1. 750 GB (disk icon) with one volume called "RAID Slice for "RAID""
2. My Time Machine disk (750 GB)
3. My startup disk (750 GB)
Selecting disk "1.", I get the tabs Erase and RAID, selecting RAID shows strange things, see screenshot:
http://files.me.com/joj/fk64zx
(the password is "x", could not get it to work without a password).
Of course, my latest Aperture library was located there which is a bit painful.....
Any ideas?
Joakim

You have to enter the password "x" twice as well... Something strange with mobileme there.

Shared volume file transfers fail and kill my RAID. Help!

Hi all,
I'm not an IT expert by any stretch, so please go easy if my questions are stupid. First, a quick rundown of my setup:
Xserve Quad with 10.5.2
Areca 1220ML RAID card (this is a hardware RAID card with 256MB)
NORCO 1220DS 8-drive RAID box
Multiple sharepoints all coming from RAID box (one 4-drive RAID5 and several single drive passthroughs)
Trunked 2GB connections to most client machines, client connect using AFP
I have been experiencing potential signs of the issues others are having here (AFP etc.) but the most troubling is that occasionally, when attempting to move a folder from one sharepoint to another (whether doing this from a client machine or on the server directly) or when moving files from a client machine to the sharepoint, finder will hang after moving 84kb or so, I get the beachball, and end up having no choice but to force reboot the system. Upon restart, sometimes the RAID volumes are all present and working, but several times the drives just disappeared outright and the admin tool for the RAID card says the RAID volume/passthrough drive has failed. I have to rebuild them and lose every ounce of data. Yay!
Is this a familiar/known type of problem to anyone out there? I am not quick to assume the card is at fault, as it is a reasonably expensive hardware-based RAID card and its drivers are built in to with Leopard Server 10.5 (there is even speculation that Apple's own RAID card is based on Areca's) which tells me they've passed a quality test to some degree.
This problem doesn't always happen, and there are times where it will happily transfer large quantities of giant files with no problems. It usually seems to glitch out when some time has passed since the last attempted file transfer, which makes me wonder if this might be part of the dreaded AFP disconnect issues.

I just wanted to close this question out and let the community know that I isolated the problem down to my RAID box, the NORCO DS-1240. These things have been noted to have build issues, including the excessive use of solder and other issues that lead to shorting out etc.
After hours in tech support land, I replaced it with a Enhance Technologies EnhanceBox and everything now works beautifully.

Retina macbook pro, worst purchase experience ever

I bought my Macbook pro at the beginning of July. Specs were 2.6ghz processor, 512 drive with 16 gb of ram. First mac I ever purchased. Sold my windows laptop which had similar specs and had worked a charm but the enticement of the new pro was too tempting.
It took about 3 weeks for it to reach me.. not bad...
<That is where the nightmare began.>
Before I use a computer, before i trust it i like to stress test it. On a PC this is easy you just run pcmark for a few days if no fail, everything is great.
On a mac you run hardware test.. Ok... so I run it. Low and behold.. it freezes after a bit... Hmmm.. not much on the net about that... Try it again and it passed for 14 hours... ok..
That evening.. Go to use one of my hard drive.. The OS claims it failed.. Un repairable, copy what files you can... But.. 50% of the files are missing.
Ok.. well Im in good shape. I run 4 hard drives one is a raid 1 array. 90% of my files were backed up.
<This is where the monster comes in>
Suspicious I take my mac in to be looked at by a genius. The genius is astute and says.. well It passes all our tests if this keeps occuring we will replace it since it is brand new.
I go home.. And start using it... It eats another hard drive and fails the hardware test again. Ok.. I still have my raid array. I call them. Please replace this POS. Sure they say.. no problem its just going to take three weeks...
Three weeks.. But I work with my computer it is my life line.. Well it seems to work fine except it has assainated another hard drive.. But it couldnt take down the raid.. It tried, but the raid rebuilt itself. Safe.. I thought.
Fast forward one day. It killed my raid disk,
This computer, this peice of aluminum garbage is toxic. It is trying to destroy my life and I have to life with this thing for 3 weeks while I try desperately to juggle my hard drives reformatting and only leaving one online in hopes it will last a day, maybe two.
This computer is ruining my life.. Time to order a new one from the mac store? 7 days.. Time for me who waited a month only to get a destructive non-functional tool? 3 weeks.
Thank you apple for ruining my life with your assembled in china non-QC controlled data assassin.

There are some good points here.. thank you for the assessments ha ha...
Unfortunately I cannot go back to a Windows PC. It was a long drawn out decision to go to Mac and the reason why was.. Efficency. Even with lesser hardware the Mac offeres a smoother operator experience. And once you learn to navigate it it is quite user friendly.
It is true I am a Mac newbie but by no means am I a computer newbie. Macs have a huge amount in common with a windows PC and any/all operations I do I researched first. So - yes my initial drives were NTFS, but I installed an appropriate third party plug in to allow my Mac to read them, I then formatted the Raid array to a nonencrypted Journal format and one external to exfat just in case.
It is not a problem with mountain lion or mac usage. This notebook is a destroyer. A informational anarchist, firebombing storehouses of information. It kills drives swiftly and efficiently and if you try to repair them it garbles them.
One poster mentioned it was sheer folly to switch over to a new computer system without keeping my old one as backup. This seems par for the course because you shodl always have a back up however there were two reasons I did not do so
1) I got a good offer on my PC, tech changes so quick that the value drops monthly, not annually, to wait was to lose money and the macbook was expensive so wanted to cover some of the cost
2) I have NEVER had this computing experience before. I have had computers that acted funny, blue screened or otherwise failed and there was always the potential that such could corrupt a hardrive or a portion of the data if it was writing to the drive but I coudl not anticiapte actually been locked in a room with a cat that almost seems intent on eviscerating my data. The experience feels like I am literally under assualt. I also would not have expected that Apple, having shipped me a dysfunctional unit (Don't they run hardware test before shipping? Seems criminal to have this kind of QC failure) would make me wait three weeks to replace it. How is that justified when they ship new units in 1 week? I foudn the same experience previaled when I ordered my Macbook, because I ordered it earlier and they later updated shipping dates to 1-2 weeks form 3-4 weeks people who ordered after me were getting their computers before me even though I paid for priority shipping. It seems to me that their policies are more bent on making new customers happy rather then ensuring people who already purchased are happy.
That said with "generic" mac items its being great. My service with iphones and ipads have been excellent when they can just substituted things. It seems to be the customization process that causes the difficulties.

Pacman -Syu dmraid kernel panic!

Please help!
I ran a system upgrade today, everything went fine, rebooted. it caused kernel panic, then it killed my raid setup. now in nvidia raid tool, it says error. I am using fakeraid, lost about 2TB of data!!!
Last edited by kaizoku (2010-08-20 09:55:40)

.:B:. wrote:
kaizoku wrote:Isn't RAID meant to provide "redundancy" in the first place? And incremental backups wont work for me, I thought thats only good for programming stuff, because it changes and you can have versions.
Backups and redundancy aren't synonyms. RAID is about availability, never about data security.
+100
Incremental backups are good for anything that changes just a bit every day, like my personal docs. Instead of backing up my music collection every day, I have an additional 50KB of compressed txt files to back up.

X58 Pro BIOS 7.3

MSI tech support sent me BIOS 7.3 version for the MSI Pro X58. Doing the upgrade from 7.1 to 7.3 will kill the RAID config. Seems like JBOD is missing as an RAID option in 7.3. In 7.1 I had a single drive JBOD as my boot drive and 5x500GB drives in RAID-0. The RAID 0 drive was not accessible under 7.3 and I had to recreate and restore. the JOB drive was accessible as a non-RAID Drive.

Quote from: sangster on 02-May-09, 23:02:25
MSI tech support sent me BIOS 7.3 version for the MSI Pro X58. Doing the upgrade from 7.1 to 7.3 will kill the RAID config. Seems like JBOD is missing as an RAID option in 7.3. In 7.1 I had a single drive JBOD as my boot drive and 5x500GB drives in RAID-0. The RAID 0 drive was not accessible under 7.3 and I had to recreate and restore. the JOB drive was accessible as a non-RAID Drive.
I just updated mine from 7.1 to 7.3. No proble like that. Once the bios is updated, I did load optimized, then do RAID mode. I have a disk set up as boot disk, and two drives as RAID 0. Works.

Primary drive on a Mac Mini server ?

Hi all: When I first picked up my 2011 mac mini server I immediately reformatted the drives and created a Riad 1 array. After a while, I decided to go back to a two disk arrangement. Since then my mini have worked OK but sometimes drops connections to client machines (all OS X ML) and generally seems a bit slow. When I did the second moved back to a two drive setup, I did not know which drive should be the primary OR if it even mattered. So that is my question: Does it matter which drive is primary? and if so, how do I identify the primary?
Thanks a bunch, Chris.

moseman wrote:
When I killed the RAID I reformatted both drives and started from scratch. It was at this point that I was faced with picking one drive to hold the OS. I did not know which drive to use, or if it even made a difference.
As I mentioned, immediately after spliting the RAID both drives will be 100% identical so it would not matter which you made the OS one. There would be no difference in content or performance (assuming they are the same model drive).
As soon as you start using one of the split drives you would then be making changes compared to the other.

Crackle/Pop on VIA (Asus A8V) MOBO - Possible Soluti

I've been trying to fix my crackle and pop for about a year and a half. If you're not familiar with the problem.. the sound card crackles even on the digital outputs when you drag windows around. In my situation, it didn't start until I had the card for a few months which seemed strange. I tried a new motherboard, and returned my sound card for another with no change. Recently, I upgraded to vista and the popping/crackling went away!!
However, when I upgraded the VIA all in one drivers to the latest 'vista compatible' version it returned. I did a system restore to the previous drivers which seemed to kill my raid (which was working until then) but the crackling went away. Upgraded to the new drivers, the crackling return again. My Via CPU to AGP drivers say 2006-06-2 V 6.0.6000.6386 Driver Provider : MicrosoftVIA VT8237 RAID Controller - Provider: VIA Technologies, Inc. 2006-09-30 Version: 6.0.5600.63?Anyways the crackling may return again and if it does I will post a followup but I hope this helps someone.

Meh.. ok that lasted all of about 8 hours. Nevermind ?

K8N Neo4 Platinum - Sata Issue

My problem has a long story behind it, so if you want to read the full story look here http://www.hardforum.com/showthread.php?t=1254531
Long story short, my psu died and when I got the new one back it killed my raid 0 array. I bought a brand new Western Digital 250 gb sata drive, plug it in and when I try to install Windows it doesn't detect it. Tried different sata drivers, updating bios, enabling / disabling raid in bios, different ports, different cables. Popped the HDD is another computer and it didn't pick it up. I am thinking my X-connect 500 watt psu is frying hard drives, but I am not quite sure. I bought an Antec psu tester which only tested the main 24 pin connector and it checked out fine.

Never been able to see individual sata drives in the bios. Before this problem started I was running a raid 0 array which I was able to set as my first boot priority in the bios.
I have tried many different combinations with the sata drivers. I have pressed f6 during the Windows install and used the NV raid sata drivers from the driver disk that came with the motherboard. Even though I am not running raid I tried it anyway. I know these drivers worked since I used them when I setup my raid 0 array when I first bought the system. Of course it didn't work so I tried downloading the latest sata raid drivers from the msi site, loaded them on a floppy and used them during the Windows install which did not work. Tried the same with the Silicon raid controller both the disk that came with the motherboard and the updated ones from the site. Nothing works. Tried without loading any sata raid drivers and same thing...no disk detected.
I am pretty convinced this Ultra psu is screwing up my hard drives. I bought an Antec psu tester today, although it only checks my 24 pin connection and it checked out fine. I might return this Antec psu tester and buy a better one that allows me to test the molex and sata power connections.
Thinking about buying this ocz psu http://www.newegg.com/Product/Product.aspx?Item=N82E16817139001

Disk Utility - delete RAID killed data on drives before server install

OK. Here's the scenario.
I had a Dual 1G G4 with a fully functioning RAID 1 installed. So I attempted to do an install of Leopard Server. It came up with a message that said something like "OS X could not prepare disk for installation." After reading some forum posts, one guy said that he was able to install Leopard by deleting the RAID, thus splitting the RAID into two volumes. So I booted from the DVD again, and this time it reports that the RAID is degraded, and that the second drive in the RAID set is a "spare."
This seemed odd, but I figured if I delete the RAID set it would keep the section that had all the good data on it. That's when my world went to ****.
Once it deleted the RAID set, and the message came up prompting me that I would NOT lose my data, it went ahead and deleted all my data. Perhaps replacing the good volume with the so-called spare. So I have been trying in vain to get the data back. The one product that I own, DiskWarrior, does not see the drives as volumes. So it won't work. Anyone have any ideas?
There was not a LOT of data on the drive, but there was a lot of complicated web shares and a few IMPORTANT websites that I need to get back. And, yes, I do not have a current backup of the volume. I was riding the RAID 1 cushion way too hard.

It would seem that I have the answer, and I believe that this is a MAJOR problem that Apple should address with some kind of warning to its customers. The RAID set I deleted was an Apple RAID 1.0 set. Upon reading further into the documentation, I see that RAID 2.0 sets can be deleted, and the volumes split into two. But with RAID 1.0 sets, the data is lost when you delete a volume.
So, even though I was deleting the set in 10.5, it seems to have applied the rules for RAID 1.0.
http://docs.info.apple.com/article.html?path=RaidUtility/1.0/en/s1ru11.html
I am hoping that there is a way to recover my data, but i'm not too hopeful.

How to kill your hardrives with RAID - fast and easy

Here is the story:
I created a RAID 1 array with two maxtor diamondmax 10 250Gig 16 Mo cache
on sata 3 and 4 of my new K8N Neo2.
First problem was a systematic crash during windows install (blue screen with error in ntfs.sys). I sorted that out by removing the second drive (so I'm still in RAID1 mode but with only one disk).
Then windows installs smoothly in less than 10 minutes.
Second problem after the install: windows is really slooow to boot . I reconnected
the second drive in the array... no change.
At that point I thought: why not try with sata 1 and 2? So I shutdown, move the
sata cables, power on, goes into the bios, disable raid on sata 3 and 4, enable it on sata 1 and 2, save settings.
The box resets and I'm ready to press F10 to enter into the raid bios and define a
new array... but the two drives start to make a scary dying noise (a bit like the one of a 56k modem ...). I quickly power off. But at the restart: no more hardrive detected, even with raid disabled.

Quote
Originally posted by Tiresmoke
For one... That PSU is a bit light for your rig. However I don't think it is the problem. Which Drivers are you using. There have been some weird issues with some of the NForce drivers noted and there is also the issue with Windows XP SP1 and larger drives. I would stay to Sata 3/4 at least for now and see if things get resolved otherwise.
Oups, typo ... this is a 480W PSU.
I'm definitely giving up RAID1. I'll use the second drive to store ghost images.
Now it's time to test the stability of this box with some doom3 and HL2

Kernel Panic - not syncing: Attempted to kill init!

OK, a new issue that I can't resolve...
Having made my new kernel without any hiccups, I then installed it by using pacman -A kernel2.6.12.pkg.tar.gz. However, on boot-up it only gets so far, then gives me an error:
<0>Kernel Panic - not syncing: Attempted to kill init!
I've looked around on the 'net, and it seems this usually occurs when there's some problem with the hardware. However, I've used the config file from the 2.6.10 kernel I'm currently in as I type, so there shouldn't be any problems support-wise :?
What could be wrong?
My fstab and config for the 2.6.12 kernel are below (I've included the fstab so you can see I've got support for my filesystems compiled into the kernel):
FSTAB:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
tmpfs /tmp tmpfs defaults 0 0
usbfs /proc/bus/usb usbfs defaults 0 0
/dev/cdroms/cdrom0 /mnt/cd iso9660 ro,user,noauto,unhide 0 0
/dev/cdroms/cdrom0 /mnt/dvd udf ro,user,noauto,unhide 0 0
/dev/floppy/0 /mnt/fl vfat user,noauto 0 0
/dev/discs/disc0/part2 swap swap defaults 0 0
/dev/discs/disc0/part3 / reiserfs defaults 0 0
/dev/discs/disc0/part1 /boot reiserfs defaults 0 0
/dev/discs/disc0/part4 /home reiserfs defaults 0 0
/dev/sda3 /mnt/warehouse vfat defaults 0 0
CONFIG:
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.10
# Sun Sep 4 11:39:06 2005
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
# Code maturity level options
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_LOCK_KERNEL=y
# General setup
CONFIG_LOCALVERSION="-ARCH"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
CONFIG_LOG_BUF_SHIFT=14
CONFIG_HOTPLUG=y
CONFIG_KOBJECT_UEVENT=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_FUTEX=y
CONFIG_EPOLL=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SHMEM=y
CONFIG_CC_ALIGN_FUNCTIONS=0
CONFIG_CC_ALIGN_LABELS=0
CONFIG_CC_ALIGN_LOOPS=0
CONFIG_CC_ALIGN_JUMPS=0
# CONFIG_TINY_SHMEM is not set
# Loadable module support
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y
# Processor type and features
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
CONFIG_MK7=y
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_USE_3DNOW=y
CONFIG_HPET_TIMER=y
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
# CONFIG_X86_UP_APIC is not set
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
# CONFIG_X86_MCE_NONFATAL is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
# Firmware Drivers
# CONFIG_EDD is not set
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_HIGHMEM=y
# CONFIG_HIGHPTE is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_HAVE_DEC_LOCK=y
# CONFIG_REGPARM is not set
# Power management options (ACPI, APM)
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
# CONFIG_SOFTWARE_SUSPEND is not set
# ACPI (Advanced Configuration and Power Interface) Support
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
# CONFIG_ACPI_SLEEP is not set
# CONFIG_ACPI_AC is not set
# CONFIG_ACPI_BATTERY is not set
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_VIDEO=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_IBM is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_X86_PM_TIMER is not set
# APM (Advanced Power Management) BIOS Support
# CONFIG_APM is not set
# CPU Frequency scaling
# CONFIG_CPU_FREQ is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
# CONFIG_PCI_LEGACY_PROC is not set
CONFIG_PCI_NAMES=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
# PCCARD (PCMCIA/CardBus) support
# CONFIG_PCCARD is not set
# PC-card bridges
# PCI Hotplug Support
# CONFIG_HOTPLUG_PCI is not set
# Executable file formats
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_MISC=y
# Device Drivers
# Generic Driver Options
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
# Memory Technology Devices (MTD)
# CONFIG_MTD is not set
# Parallel port support
# CONFIG_PARPORT is not set
# Plug and Play support
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set
# Protocols
CONFIG_PNPACPI=y
# Block devices
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_LOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
# CONFIG_BLK_DEV_RAM is not set
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_LBD is not set
# CONFIG_CDROM_PKTCDVD is not set
# IO Schedulers
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
# CONFIG_IOSCHED_DEADLINE is not set
# CONFIG_IOSCHED_CFQ is not set
# ATA/ATAPI/MFM/RLL support
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
# Please see Documentation/ide.txt for help/info on IDE drives
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
CONFIG_BLK_DEV_IDEFLOPPY=y
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set
# IDE chipset support/bugfixes
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
CONFIG_BLK_DEV_AMD74XX=y
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_ARM is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set
# SCSI device support
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y
# SCSI support type (disk, tape, CD-ROM)
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
# CONFIG_CHR_DEV_SG is not set
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
# SCSI Transport Attributes
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# SCSI low-level drivers
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
CONFIG_SCSI_SATA=y
# CONFIG_SCSI_SATA_AHCI is not set
# CONFIG_SCSI_SATA_SVW is not set
# CONFIG_SCSI_ATA_PIIX is not set
CONFIG_SCSI_SATA_NV=y
# CONFIG_SCSI_SATA_PROMISE is not set
# CONFIG_SCSI_SATA_SX4 is not set
CONFIG_SCSI_SATA_SIL=y
# CONFIG_SCSI_SATA_SIS is not set
# CONFIG_SCSI_SATA_ULI is not set
# CONFIG_SCSI_SATA_VIA is not set
# CONFIG_SCSI_SATA_VITESSE is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX=y
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 is not set
# CONFIG_SCSI_QLA6322 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
# Multi-device support (RAID and LVM)
# CONFIG_MD is not set
# Fusion MPT device support
# CONFIG_FUSION is not set
# IEEE 1394 (FireWire) support
# CONFIG_IEEE1394 is not set
# I2O device support
# CONFIG_I2O is not set
# Networking support
CONFIG_NET=y
# Networking options
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
# CONFIG_NETLINK_DEV is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_TUNNEL is not set
CONFIG_IP_TCPDIAG=y
# CONFIG_IP_TCPDIAG_IPV6 is not set
# IP: Virtual Server Configuration
CONFIG_IP_VS=m
# CONFIG_IP_VS_DEBUG is not set
CONFIG_IP_VS_TAB_BITS=12
# IPVS transport protocol load balancing support
CONFIG_IP_VS_PROTO_TCP=y
CONFIG_IP_VS_PROTO_UDP=y
CONFIG_IP_VS_PROTO_ESP=y
CONFIG_IP_VS_PROTO_AH=y
# IPVS scheduler
CONFIG_IP_VS_RR=m
CONFIG_IP_VS_WRR=m
CONFIG_IP_VS_LC=m
CONFIG_IP_VS_WLC=m
CONFIG_IP_VS_LBLC=m
CONFIG_IP_VS_LBLCR=m
CONFIG_IP_VS_DH=m
CONFIG_IP_VS_SH=m
CONFIG_IP_VS_SED=m
CONFIG_IP_VS_NQ=m
# IPVS application helper
CONFIG_IP_VS_FTP=m
# CONFIG_IPV6 is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
# IP: Netfilter Configuration
CONFIG_IP_NF_CONNTRACK=m
# CONFIG_IP_NF_CT_ACCT is not set
# CONFIG_IP_NF_CONNTRACK_MARK is not set
# CONFIG_IP_NF_CT_PROTO_SCTP is not set
CONFIG_IP_NF_FTP=m
CONFIG_IP_NF_IRC=m
CONFIG_IP_NF_TFTP=m
CONFIG_IP_NF_AMANDA=m
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_IPRANGE=m
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_PKTTYPE=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
CONFIG_IP_NF_MATCH_RECENT=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_DSCP=m
CONFIG_IP_NF_MATCH_AH_ESP=m
CONFIG_IP_NF_MATCH_LENGTH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_TCPMSS=m
CONFIG_IP_NF_MATCH_HELPER=m
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_CONNTRACK=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_MATCH_ADDRTYPE=m
CONFIG_IP_NF_MATCH_REALM=m
CONFIG_IP_NF_MATCH_SCTP=m
CONFIG_IP_NF_MATCH_COMMENT=m
# CONFIG_IP_NF_MATCH_HASHLIMIT is not set
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_IP_NF_TARGET_TCPMSS=m
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_IP_NF_TARGET_NETMAP=m
CONFIG_IP_NF_TARGET_SAME=m
CONFIG_IP_NF_NAT_LOCAL=y
CONFIG_IP_NF_NAT_SNMP_BASIC=m
CONFIG_IP_NF_NAT_IRC=m
CONFIG_IP_NF_NAT_FTP=m
CONFIG_IP_NF_NAT_TFTP=m
CONFIG_IP_NF_NAT_AMANDA=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_DSCP=m
CONFIG_IP_NF_TARGET_MARK=m
CONFIG_IP_NF_TARGET_CLASSIFY=m
CONFIG_IP_NF_RAW=m
CONFIG_IP_NF_TARGET_NOTRACK=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m
# CONFIG_IP_NF_COMPAT_IPCHAINS is not set
# CONFIG_IP_NF_COMPAT_IPFWADM is not set
# SCTP Configuration (EXPERIMENTAL)
CONFIG_IP_SCTP=m
# CONFIG_SCTP_DBG_MSG is not set
# CONFIG_SCTP_DBG_OBJCNT is not set
# CONFIG_SCTP_HMAC_NONE is not set
CONFIG_SCTP_HMAC_SHA1=y
# CONFIG_SCTP_HMAC_MD5 is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# QoS and/or fair queueing
# CONFIG_NET_SCHED is not set
# CONFIG_NET_SCH_CLK_JIFFIES is not set
# CONFIG_NET_SCH_CLK_GETTIMEOFDAY is not set
# CONFIG_NET_SCH_CLK_CPU is not set
CONFIG_NET_CLS_ROUTE=y
# Network testing
# CONFIG_NET_PKTGEN is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_NET_SB1000 is not set
# ARCnet devices
# CONFIG_ARCNET is not set
# Ethernet (10 or 100Mbit)
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
CONFIG_NET_VENDOR_3COM=y
CONFIG_VORTEX=y
# CONFIG_TYPHOON is not set
# Tulip family network device support
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
# CONFIG_NET_PCI is not set
# Ethernet (1000 Mbit)
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set
# Ethernet (10000 Mbit)
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set
# Token Ring devices
# CONFIG_TR is not set
# Wireless LAN (non-hamradio)
# CONFIG_NET_RADIO is not set
# Wan interfaces
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set
# ISDN subsystem
# CONFIG_ISDN is not set
# Telephony Support
# CONFIG_PHONE is not set
# Input device support
CONFIG_INPUT=y
# Userland interfaces
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set
# Input I/O drivers
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
# CONFIG_SERIO_RAW is not set
# Input Device Drivers
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set
# Character devices
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set
# Serial drivers
CONFIG_SERIAL_8250=y
# CONFIG_SERIAL_8250_CONSOLE is not set
# CONFIG_SERIAL_8250_ACPI is not set
CONFIG_SERIAL_8250_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set
# Non-8250 serial port support
CONFIG_SERIAL_CORE=y
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
# IPMI
# CONFIG_IPMI_HANDLER is not set
# Watchdog Cards
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
# Ftape, the floppy tape device driver
# CONFIG_FTAPE is not set
CONFIG_AGP=y
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_INTEL_MCH is not set
CONFIG_AGP_NVIDIA=y
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_AGP_EFFICEON is not set
CONFIG_DRM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=y
# CONFIG_DRM_I830 is not set
# CONFIG_DRM_I915 is not set
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HPET is not set
# CONFIG_HANGCHECK_TIMER is not set
# I2C support
CONFIG_I2C=y
# CONFIG_I2C_CHARDEV is not set
# I2C Algorithms
CONFIG_I2C_ALGOBIT=y
# CONFIG_I2C_ALGOPCF is not set
# CONFIG_I2C_ALGOPCA is not set
# I2C Hardware Bus support
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_I810 is not set
CONFIG_I2C_ISA=y
CONFIG_I2C_NFORCE2=y
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
# CONFIG_I2C_VOODOO3 is not set
# CONFIG_I2C_PCA_ISA is not set
# Hardware Sensors Chip support
# CONFIG_I2C_SENSOR is not set
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_FSCHER is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_LM63 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM87 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83627HF is not set
# Other I2C Chip support
# CONFIG_SENSORS_EEPROM is not set
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_RTC8564 is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set
# Dallas's 1-wire bus
# CONFIG_W1 is not set
# Misc devices
# CONFIG_IBM_ASM is not set
# Multimedia devices
CONFIG_VIDEO_DEV=m
# Video For Linux
# Video Adapters
# CONFIG_VIDEO_BT848 is not set
# CONFIG_VIDEO_CPIA is not set
# CONFIG_VIDEO_SAA5246A is not set
# CONFIG_VIDEO_SAA5249 is not set
# CONFIG_TUNER_3036 is not set
# CONFIG_VIDEO_STRADIS is not set
# CONFIG_VIDEO_ZORAN is not set
# CONFIG_VIDEO_SAA7134 is not set
# CONFIG_VIDEO_MXB is not set
# CONFIG_VIDEO_DPC is not set
# CONFIG_VIDEO_HEXIUM_ORION is not set
# CONFIG_VIDEO_HEXIUM_GEMINI is not set
# CONFIG_VIDEO_CX88 is not set
# CONFIG_VIDEO_OVCAMCHIP is not set
# Radio Adapters
# CONFIG_RADIO_GEMTEK_PCI is not set
# CONFIG_RADIO_MAXIRADIO is not set
# CONFIG_RADIO_MAESTRO is not set
# Digital Video Broadcasting Devices
# CONFIG_DVB is not set
# Graphics support
# CONFIG_FB is not set
# CONFIG_VIDEO_SELECT is not set
# Console display driver support
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
# Sound
CONFIG_SOUND=y
# Advanced Linux Sound Architecture
CONFIG_SND=y
CONFIG_SND_TIMER=y
CONFIG_SND_PCM=y
CONFIG_SND_HWDEP=y
CONFIG_SND_RAWMIDI=y
CONFIG_SND_SEQUENCER=y
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
CONFIG_SND_SEQUENCER_OSS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
# Generic devices
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set
# PCI devices
CONFIG_SND_AC97_CODEC=y
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
CONFIG_SND_EMU10K1=y
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
CONFIG_SND_INTEL8X0=y
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VX222 is not set
# USB devices
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_USX2Y is not set
# Open Sound System
# CONFIG_SOUND_PRIME is not set
# USB support
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
# Miscellaneous USB options
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_SUSPEND is not set
# CONFIG_USB_OTG is not set
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
# USB Host Controller Drivers
CONFIG_USB_EHCI_HCD=y
# CONFIG_USB_EHCI_SPLIT_ISO is not set
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
CONFIG_USB_OHCI_HCD=y
# CONFIG_USB_UHCI_HCD is not set
# CONFIG_USB_SL811_HCD is not set
# USB Device Class drivers
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_BLUETOOTH_TTY is not set
# CONFIG_USB_MIDI is not set
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=y
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support' may also be needed; see USB_STORAGE Help for more information
CONFIG_USB_STORAGE=y
# CONFIG_USB_STORAGE_DEBUG is not set
CONFIG_USB_STORAGE_RW_DETECT=y
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_HP8200e is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# USB Input Devices
CONFIG_USB_HID=y
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
CONFIG_USB_HIDDEV=y
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_MTOUCH is not set
# CONFIG_USB_EGALAX is not set
# CONFIG_USB_XPAD is not set
# CONFIG_USB_ATI_REMOTE is not set
# USB Imaging devices
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_HPUSBSCSI is not set
# USB Multimedia devices
# CONFIG_USB_DABUSB is not set
# CONFIG_USB_VICAM is not set
# CONFIG_USB_DSBR is not set
# CONFIG_USB_IBMCAM is not set
# CONFIG_USB_KONICAWC is not set
# CONFIG_USB_OV511 is not set
# CONFIG_USB_SE401 is not set
# CONFIG_USB_SN9C102 is not set
# CONFIG_USB_STV680 is not set
# USB Network Adapters
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
# USB port drivers
# USB Serial Converter support
# CONFIG_USB_SERIAL is not set
# USB Miscellaneous drivers
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_TIGL is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGETKIT is not set
# CONFIG_USB_PHIDGETSERVO is not set
# CONFIG_USB_TEST is not set
# USB ATM/DSL drivers
# USB Gadget Support
# CONFIG_USB_GADGET is not set
# CONFIG_USB_GADGET_NET2280 is not set
# CONFIG_USB_GADGET_PXA2XX is not set
# CONFIG_USB_GADGET_GOKU is not set
# CONFIG_USB_GADGET_SA1100 is not set
# CONFIG_USB_GADGET_LH7A40X is not set
# CONFIG_USB_GADGET_DUMMY_HCD is not set
# CONFIG_USB_GADGET_OMAP is not set
# CONFIG_USB_ZERO is not set
# CONFIG_USB_ETH is not set
# CONFIG_USB_GADGETFS is not set
# CONFIG_USB_FILE_STORAGE is not set
# CONFIG_USB_G_SERIAL is not set
# MMC/SD Card support
# CONFIG_MMC is not set
# File systems
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_REISERFS_FS_XATTR is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y
# CD-ROM/DVD Filesystems
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
CONFIG_UDF_FS=y
CONFIG_UDF_NLS=y
# DOS/FAT/NT Filesystems
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_NTFS_FS=y
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set
# Pseudo filesystems
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
CONFIG_DEVFS_FS=y
CONFIG_DEVFS_MOUNT=y
# CONFIG_DEVFS_DEBUG is not set
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_TMPFS_XATTR is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
# Miscellaneous filesystems
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
CONFIG_HFS_FS=y
CONFIG_HFSPLUS_FS=y
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
# Network File Systems
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_EXPORTFS is not set
CONFIG_SMB_FS=y
# CONFIG_SMB_NLS_DEFAULT is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
# Partition Types
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
# Native Language Support
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set
# Profiling support
# CONFIG_PROFILING is not set
# Kernel hacking
# CONFIG_DEBUG_KERNEL is not set
# CONFIG_FRAME_POINTER is not set
CONFIG_EARLY_PRINTK=y
CONFIG_4KSTACKS=y
# Security options
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
# Cryptographic options
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_MD4 is not set
# CONFIG_CRYPTO_MD5 is not set
CONFIG_CRYPTO_SHA1=y
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_WP512 is not set
# CONFIG_CRYPTO_DES is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_AES_586 is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_TEST is not set
# Library routines
CONFIG_CRC_CCITT=m
CONFIG_CRC32=y
CONFIG_LIBCRC32C=m
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y
Arch is running on an Athlon-XP 3000+, with an Audigy 2 Value sound card, ASUS NF7 mobo (nforce2), 2 IDE hdds, 1 SATA hdd, a floppy drive, 3com Boomerang ethernet PCI card, and an ATI Radeon 9800SE.
I thought that I might have enabled both APM and APCI in the kernel by accident, but that's not the case :cry:
I know, as I've mentioned earlier in the thread, that there's an issue with the emu10k1 drivers used by my audigy in this kernel, but I've compiled that as a module under ALSA, and I assume it wouldn't have an extreme effect like this even if it were statically compiled.
Any ideas???

Problem was resolved by self; I recompiled the kernel, again using ABS... I think I may have not incorporated an I/O Scheduler into the kernel, lol. Cheers anyway.

Windows 8 64-bit, failed installations and RAID 1 resync on HP ENVY h8-1520z

I recently purchased an HP Envy h8-1520z with a single SSD and 8 GB RAM running Windows 8 Pro 64-bit. I installed 2 Western Digital 500 GB WDC WD5000AAKX-001CA0 HDDs on SATA ports 5 & 6 and configured them as RAID 1 in the BIOS. I have started installing apps on the RAID 1 array (E since the SSD is only 256 GB.
While installing software, some install fine, but often the installation hangs with no errors indicated and I have to kill the installer task through task manager. I usually follow that with a system shutdown or restart and almost every time that results in a resync of the RAID array. Sometimes the shutdown or restart is quick, and other times it takes several minutes with intermittent disk activity as indicated by the drive light. I have sometimes given up after 10 minutes or so and powered down by holding down the power button. I can understand a resync after the forced power down, but it seems that all it takes to cause a resync is a failed installation, and that seem to happen a lot, even with software that explicitly says it is Windows 8 compatible. Sometimes the applications run fine even after an apparently failed installation and other times not so much.
Has anybody else seen this behavior or have any suggestions? I’d like to get this sorted out before I load any more software.

Hi,
Did you check each hard drive for straps? There should not be any straps installed on the hard drive. These drives do have strapping posts.
Did you use the AMD RaidExpert to create the array volume? Did you wait until the RAID migration was complete before using the array volume?
Check the AMD RaidExpert for errors. It's possible that you have a bad hard drive(s).
Many applications want to be installed on the C drive. Your SSD is 256GB so you should have plenty of space for most applications and the application performance will be improved. Use the RAID 1 array to keep and store your data. The mirroring process of RAID 1 will protect it in case one hard drive fails.
You might want to consider removing all of the data etx.. from the array, use the AMD RAIDExpert to delete out the array volume. I would then run for hard drive diagnostics. If the hard drives are free from errors then use disk management to separately reformat each hard drive. Now go back to the AMD RaidExpert and create your new array volume.
Be sure to review the software and bios updates for your PC.
HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
HP Photosmart Premium C309G, HP Photosmart 6520
HP Touchpad, HP Chromebook 11
Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
Windows 7/8 UEFI/Legacy mode, MBR/GPT

Disaster RAID on MS 6702

Help:
This week end I updated my Bios, with "live update" as I have done many times previously.
However this time after the update the PC would not boot to Windows...giving me the Error message
" system32\hal.dll file missing"
re install this file.
Well I could not mange to do this no matter what I tried !.As I had no access to "Windows' I had to work in DOS mode which I am noy very familiar with but following instructions I found by searching the net I used the Recovery console and typed in the respective commands to re install the hal.dll file.
I typed :
F:\i386\hal.dll_c:\windows\system32\hal.dll
And similar variations to try to get it to work but it was never going to work as I found that I could not access my "Windows" files as they were all in my RAID array and the recovey console did not "see" them ..it would not detect the Raid drives at all when I tried !.
I have anothe HD installed on the "normal ATA IDE sockets and was able to see this drive and contents OK also my CD & DVD drives,!.
Does anyone know what I could have done in case it happens again.
I had a thought that I would install a second copy of Windows on my other ATA IDE drive and if I had problems with my RAID windows setup I would boot to the copy and copy the "lost" files over to the respective Raid drive.
However this didn't wotk either as the second copy of windows booted Ok but in Explorer it does not recognose the raid setup ..it does "see" the drive but no contents and if i try to access it it just says it wants to Format it.
is there a way of fixing these type of problems with my setup
Thanks
Pete
SYSTEM SPECIFICATION as at 28 February 2004
MSI K8T Neo Motherboard (MS6702 (v1)
ON BOARD AC-97 Realtek SOUND
MOTHERBOARD BIOS VERSION AWARD AWD 1.2
AMD XP 64 BIT 3200 PROCESSOR
ADAPTEC 2940U2W SCSI CONTROLLER CARD
BIOS VERSION ADAPTEC 2.57.2
WESTERN DIGITAL WD1000JB 7200rpm ATA133 100GB HARD DRIVE
RAID SETUP: 0 STRIPPING (for Performance)
WESTERN DIGITAL WD12000 7200rpm SERIAL ATA 120GB HARD DRIVE
WESTERN DIGITAL WD12000 7200rpm SERIAL ATA 120GB HARD DRIVE
1G (2x 512 MB) PC3200 DDR CORSAIR MEMORY
ASUS V8170 NVIDIA G-FORCE 4 64MB GRAPHICS CARD
LG 4040B DVD WRITER DVD+R, DVD-R, DVD+RW, DVD-RW DVD-RAM
LITON XJ-HD 116S 48Wx24xRW48R CD WRITER-SMART BURN/SMART X
LITEON 48246S DVD ROM
STANDARD 1.4MB FLOPPY DRIVE
MITSUBISHI DIAMOND VIEW DV-172 17 INCH LCD FLAT SCREEN MONITOR
EPSON PERFECTION 1200 SCSI SCANNER
CANON S820 COLOUR PRINTER
CANON S520 COLOUR PRINTER
AOPEN HX-08 FULL TOWER CASE
DYNALINK V1456VQE-R1 EXTERNAL MODEM
ASPI LAYER 4.17.2

when you update bios, it kills all old settings.like boot order,custom mem settings, everthing goes back to defualt.
so if it couldn't see your raid, and os was on raid, there in lies the problem.
....if not, remember that floppy disk you made with old biossettings put it in, boot with ctrl+h.

Software RAID Failure - my experience and solution

I just wanted to share this information with the iCloud community.
I searched a bit and did not find much information that was useful with regard to my software RAID issue.
I have 27 inch Mid 2011 iMac with SSD and Hard drive which has been great.
I added an external hard drive (I think if I mention any brand name the moderator will delete this post) which includes an nice aluminum case with two 3 TB hard drives within it, and it has a big blue light on the front and is connected via Thunderbolt. This unit is about 2 years old and I have it configured in a 3 TB mirrored RAID (RAID 1) via a software RAID configured via Mac OS Disk Utility.
I had at one point a minor glitch which was fixed using another piece of software (again if I mention a brand the moderator will delete this post) which is like a 'Harddrive Fighter' or similar type name LOL.   So otherwise that RAID has served me well as a site for my Time Machine back up and Aperture Vault, etc. (I created a 1.5 TB Sparse bundle for Time Machine so that the backup would not use the entire 3 TBs)
I recently purchased a second aluminum block of drives, and set that up as a 4 TB RAID 1.
Each of the two RAIDs are set with the option of “Automatically rebuild RAID mirror sets” checked.
I put only about 400 gb on the new RAID to let it sit for a ‘burning in period.’
A few days ago the monitoring software from the vendor who sells the aluminum block of drives told me I had a problem. One of the drives had “Failed.”   The monitoring software strangely enough does not distinguish the drives so you can figure out which pair had the issue, so I assumed it was the New 8 TB model. Long story short, it was the older 6 TB model, but that does not matter for this discussion.
I contacted the vender and this is part of their response.
“This is an indication that the Disk Utility application in Mac had a momentary problem communicating with the drive mechanism. As a result, it marked that drive as "failed" in the header information. Unfortunately, once this designation is applied to a drive by the OS, the Disk Utility will thereafter refuse to attempt any further operations with that disk until the incorrect "failed" marker is manually cleared off the drive.”
That did not sound very good to me…..back up killed by a SOFTWARE GLITCH?
“The solution is to remove the corrupted volume header, and allow the generation of a new one….This command will need to be done for each disk in the array… (using Terminal)…
diskutil zerodisk (identifier)
…3. After everything is finished, you should be able to exit Terminal, and go back into the Disk Utility Application to re-configure the RAID array on the device.”
Furthermore they said.
“If the Disk Utility has placed a flag into the RAID array header (which exists on both drives) then performing this procedure on a single drive will not correct anything.”
And…
“When a drive actually does fail, it typically stops appearing in the Disk Utility application altogether. In that circumstance, it will never be marked "failed" by the Disk Utility, so the header erase operation is not needed.”
This all sounded like a bad idea to me. And what does the Vendors RAID monitor software say then? “Disk Really Really FAILED, check for a fire.”
As I tried to figure out which drive was actually the bad RAID pair I stumbled on a solution.
First I noted that the OS Disk Utility did NOT show a fault in the RAID. It listed both RAIDS as “Online.’ Thus no rebuilding was needed and it did not begin the rebuild process.
The Vendors disk monitor software saw some fault, but Mac was still able to read and write to the RAID, both disks in the mirror. I wrote a folder to the RAID and with various rebooting steps I pulled the “Bad” drive and looked at the “Good” Drive….the folder was there…I put the Bad drive back in and pulled the Good Drive and the folder was there on the “bad” drive. So it wrote to both drives. AND THE VENDORS MONITORING SOFTWARE SHOWED THE PREVIOUSLY LABELED ‘BAD’ DRIVE AS ‘GOOD’ AND THE MISSING DRIVE SLOT AS ‘BAD’.
My stumbled FIX.   I moved a bunch of files off the failed RAID to the new RAID but before I moved the sparse bundle, a folder of 500 gigs movies and some other really big folders the DISK UTILITY WINDOW (which I still had open) now showed that the RAID had a Defect and began rebuilding the mirror set itself, out of the blue!   I don't know why this happened. But moving about 1/2 of the data off of it perhaps did something? Any Ideas?
This process took a few hours as best I can tell (let it run overnight) and the next day the RAID was fine and the Vendors RAID monitor did not show a fault any longer.
So, the Vendors RAID monitoring software reporting a “FAILED” drive without any specific error codes to look up. Perhaps they could have more info for the user on the specific fault? The support line of the the Vendor said with certainty “the Volume Header is corrupted” and THE ONLY FIX is to completely ZERO THE DRIVE! This was not necessary as it turns out.
And the stick in the eye to me…..
“I've also sometimes seen the drives get marked as "failed" by the disk utility due to a shaky connection. In some cases, swapping the ends of the Thunderbolt cable will help with this. Something to try, perhaps, if your problems come back. “
Ya Right…..
Mike

Follow up.
After going through the Zeroing process and rebuilding the RAID set three times, with various configurations, LaCie finally agreed to repair the unit under warrantee.
I tried swapping the power supplies and thunderbolt wires, tried taking the drive out of series with the newer big brother of it. And it still failed after a few days.
I just wanted to share more of what I learned with regard to rebuilding the RAID sets via the Terminal. The commands can be typed partially and a help paragraph will come up to give VERY cryptic descriptions of the proper use of the commands.
First Under terminal you can used the command "diskutil appleRAID list" to list those drives which are in the RAID. This gives you the ID number for each physical drive. For example:
AppleRAID sets (1 found)
===============================================================================
Name:                 LaCie RAID 3TB
Unique ID:            84A93ADF-A7CA-4E5A-B8AE-8B4A8A6960CA
Type:                 Mirror
Status:               Online
Size:                 3.0 TB (3000248991744 Bytes)
Rebuild:              manual
Device Node:          disk4
# DevNode   UUID                                  Status     Size
0 disk3s2   D53F6A81-89F1-4FB3-86A9-8808006683C2 Online     3000248991744
- disk2s2   E58CA8F5-1D2C-423A-B4BE-FBAA80F85879 Spare      3000248991744
===============================================================================
In my situation with the failed RAID, I had an extra disk in this with the status of Missing/Failed.
The command is "diskutil appleRAID remove" and the cryptic help paragraph says:
Usage: diskutil appleRAID remove MemberDeviceName|MemberUUID
        RAIDSetVolumePath|RAIDSetDeviceName|RAIDSetUUID
MemberDeviceName|MemberUUID is the number listed in the "diskutil appleRAID List" command, and
RAIDSetVolumePath|RAIDSetDeviceName|RAIDSetUUID is the Device Node for the RAID which here is /dev/disk4.
I used this command to remove the third entry (missing/failed), I did not copy the terminal window text on that one, so I cannot show the list of three disks.
I could not get to remove the disk2s2 disk listed as SPARE, as it gave an error message:
Michaels-iMac:~ mike_aronis$ diskutil appleraid remove E58CA8F5-1D2C-423A-B4BE-FBAA80F85879 /dev/disk4
Started RAID operation on disk4 LaCie RAID 3TB
Removing disk from RAID
Changing the disk type
Can't resize the file system on the disk "disk2s2"
Error: -69827: The partition cannot be resized
But I was able to remove it using the graphical interface Disk Utility program using the delete key.
I then rebuilt the RAID set by dragging the second drive back into the RAID set.
I could not get the command: "diskutil appleRAID update AutoRebuild 1 /dev/disk4" to work, because even though it was trying to execute it HUNG. I put the two drives into my newer LaCie 2big as my attempt at further trouble shooting the RAID (this was not suggested by LaCie tech), rebuild the RAID and now I am going to leave it setup that way for a few days before I ship it back to just see if the old drives work fine in the new RAID box (thus proving the RAID box is the problem). I tried the AutoRebuild 1 command just now and it gave an error.
Michaels-iMac:~ mike_aronis$ diskutil appleraid update autorebuild 1 /dev/disk4
Error updating RAID: Couldn't modify RAID (-69848)
Michaels-iMac:~ mike_aronis$
In my haste to rebuild the RAID set for the third or forth time as LaCie led me through the testing this and test that phase, I forgot to click the "Auto Rebuild" option in the Disk Utility program.
Question for the more experienced:
As I was working on this issue, I notice that each time I rebooted and did work in the Terminal (with and without the RAID plugged in to the thunderbolt connection) I notice that the list of drives would change and my main boot drive would not stay listed as drive 0! Some times it would be drive 0, sometimes the RAID would be listed as Drive 0. It's strange to me...I would have thought the designation for Drive0 and Drive1 would always be my two build in drives (SSD and spinning drive).
Mike

10.6.2 Killed My RAID

Similar Messages

Maybe you are looking for