If i recreate the RAID array with 2 SSDs, make a partition of 300GB, and then restore the image to that array- the software initializes the array and I am able to see it as a 300GB array in the Acronis software restore.
Of course, before doing this, try some of the free or paid recovery software to get your data out of it. When I get into the program the RAID array is not there (duh) and if I go to initialize disks, the disks that make up the array show up as individual disks not as a RAID array of 500GB. Note: Finally, if you’re unable to initialize the drive, the only thing you can do is format the drive and start from scratch. When I boot with the Acronis True Image 2012 (w/Plus Pack) recovery CD, I see (right before it gets into the Acronis program) that the RAID array was NOT INITIALIZED. I know that once I have a third drive in the array the speed will drop to SATA3 speeds.
I created the array(s) with a 500GB partition and leaving the rest unpartitioned for reserve space for the health of the SSDs. Same problem 9/24 14:13:33.027 Prism/4 <>:0: Unsupported API Backend 9/24 14:13:33.027 D2Prism/5 <>:0: Fatal: failed to create device.I deleted the array and created a 4 x 256GB RAID 0 (and a 3 x 256GB RAID 0 array to see if that was the cause). I have made a backup of the existing RAID array using Acronis True Image Home 2012. Ok, I recently acquired 2 x 256GB Crucial M4s, and I already have an existing RAID 0 array of 2 x 256GB M4s on the 2 Intel SATA6 ports. Previous message: Adrian Bunk: "Re: update.The body of a message to majordomo info at To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > cause, or whether this is a known bug and you don't need any help > Let me know, if there is anything I can do to help you diagnose the root
> for the array to rebuild itself after I am done experimenting. The worst case scenario is that I need to wait a couple of hours > independent controllers, it is relatively easy for me to do some testing ii) Used USB connection - device manger can now recognise the drive. i) Used eSATA connection - device manager did not find the drive. Inserted the drive (Western Digital WD5000AKS - WD Caviar) into an Akasa e/SATA caddy.
> As I have two of those disks (in a RAID-1 array) and multiple Cracked open the case (data is more important than a 60 drive). > the other controllers (JMicron AHCI, or NVidia sata_nv) on this motherboard. > whereas everything appears to work fine, if I connect the disk to one of > The kernel never even registers the drive as an available disk device, > kernel: ata4: SATA link down (SStatus 0 SControl 300) > kernel: ata3: SATA link down (SStatus 0 SControl 300) > kernel: ata2: SATA link down (SStatus 0 SControl 300) > kernel: ata1: EH pending after completion, repeating EH (cnt=4) Select the unallocated disk, right-click on it and click Initialize Disk. ( see Image 5) Image 5: The device appears as unallocated. > kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Open Disk Management and locate the drive, which is not initialized.
Mac OSX detects a drive that needs to be initialized and automatically prompts you to initialize the drive. The partition uses a file system (for example, HFS+, ex-FAT, NTFS, and so on). > kernel: ata4: SATA max UDMA/133 cmd 0x0000000000000000 ctl 0xffffc20003528120 bmdma 0x0000000000000000 irq 16 A partition defines an area of the drive to use for storing data. The hard disk has a non-standard partition configuration that causes migration between different storage controllers. > kernel: sata_mv 0000:06:00.0: Gen-IIE 32 slots 4 ports SCSI mode IRQ via INTx
Initialize the SSD with these steps: In Windows 7, 8, 8. > kernel: sata_mv 0000:06:00.0: Applying 60X1C0 workarounds to unknown rev The drive must be initialized first in the operating system in order to be seen by it and open the wizard. > kernel: ACPI: PCI Interrupt Link enabled at IRQ 16
> based controller, and the most recent Linux kernel (2.6.23-rc1) fails to > I just tried hooking up a Hitachi 1TB SATA-II drive to a Marvell 7042
Next message: Andi Kleen: "Re: Simple Performance Counters: x86_64 support".Linux-Kernel Archive: Re: Marvell 7042 (sata_mv) fails to initialize drive Re: Marvell 7042 (sata_mv) fails to initialize drive From: Michal Piotrowski