Moving RAID- drives to new motherboard

I am very likely going to upgrade my K8T Neo to the newer K8T800 Pro with a 3800+ when both are available.
Anyone offer advice on how to move my currently RAID0 drives to this new motherboard? The controller is still the 8237 so I'm assuming it will be OK?
What would happen if I wanted to move this drive to a different controller - like a board based on the Nforce controller? Would it work or would I have to start over and lose my RAID0 contents?
Sure wish someone had a 4 device SATA controller on the motherboard so I didn't have to deal with the Promise stuff. Was disappointed this wasn't included in the K8T800 Pro.

The same era (early 2005) 2.3 might be a good option.
If you don't have PCI/PCI-X cards that need transferred, a 2.3 GHz dual core (Late 2005) would be an option.
A Late 2005 dual core machine, however, wouldn't be able to use existing RAM or graphics cards, either.
All other models can use existing RAM, PCI and graphics cards.
As I said, the drives should not be a worry in any other G5.
They would probably boot just fine in a G4 as well.
With a retail OS installation, there is no reason to worry about compatibility.
As for LCS, like I said, all 2.5 and 2.7 GHz machines.
Here is a list of G5 models:
http://www.everymac.com/systems/apple/powermac_g5/index-powermac-g5.html

Similar Messages

Moving TM Drive to New Mac

I've been backing up from my MacBook Pro to a wired drive for a while. I've just got myself a Mac Mini and plugged the drive in there instead. I'm trying to carry on using the same Time Machine backup for the MBP wirelessly, with mixed success so far.
I've shared the drive and pointed the MBP to its new place, and it's accepted it, although I haven't allowed it to start a backup yet as I wanted to make sure I could access the old ones first. When I enter Time Machine it says the current backup can't be found and gives me the option to select either the "old" one for the MBP, or the new mini's backup. So I'm sort of half way there, but I'm worried about this step of having to point it to the old one because the "current one can't be found." I'm wondering if this means it will insist on starting a new backup for the MBP from scratch, which will take a long time over wireless, not to mention taking up several dozen gigabytes somewhat unnecessarily.
Any advice will be appreciated

I got started with a solution from your article, perhaps someone can help me get over the next hurdle!
By starting a new backup over the network and cancelling it after "preparing," I got my blank sparsebundle, and decided to try moving my old backups to the sparsebundle ... simple idea in theory, but I'm getting help up by an "error code -50". I've seen solutions to this error when you want to copy it from one HD to another HD, but nothing for copying from a folder to a sparsebundle disk image. Can I get any help getting over it?
The other problem is I've found that if I decide to start a new one from scratch (which is a giant pain), plugging back in via USB to finish the first backup in good time won't work because it'll default to the old backup on in the Backups folder rather than the sparsebundle. I don't under any circumstances want to delete the old backup, it still needs to be accessible.
So I seem a bit stuck whatever I do... any help is as appreciated as ever

Getting new motherboard to recognise previously Striped drives

Hi
I've ordered a new 6758 PCB2.0 motherboard to replace my 6758 PCBPCB1.0 (875P Neo-FIS2R) which has ceased working. Can anyone tell me how I can ensure that when I connect all my drives to the new board the existing stripe config on the boot drive and a 2nd identical drive is maintained? They are striped using the onboard Promise controller - naturally when I power on the new box the Promise config will not be present and I definitely don't want to lose my data - losing the 1st board was enough for one week.
Thanks
egd

Bad news,your new board does not have promise.
windows will say so you would have to do a repair install.
you will have to remember the exact settings for a alike raid sys [intel vs promise]
when you load new sys preload a raid driver and load OS to a single HD,then setup your other HDs and create a raid and see if you can recover any data.

New motherboard w/old Hard drive?

I have another thread titled Kt7 pro video turns off"
but this would apply to all.
Gave up on M.B. and tried a new one. It works fine. However!!!!!
How do you get the old Hard Drive with windows already installed to work properly with the a new Mother Board?
I know most would say reinstall windows from scratch, but this is not my computer and I don't have another Hard Drive etc etc.
I know people do do this by going into safe mode and deleting everything in the Divice Manager but how do you delete the Hard Disk Controllers. I remember someone said to delete the Num something in the registry?
Any input would be nice. cause for some reason windows won't recognize my Cd. so I can't install the controllers for the new motherboard.
Old M.B. KT7 Pro 2
New M.B. KT2

i have never had that work successfully with a system for more than 3 months. You can go into safe mode and uninstall every device driver you see, that might work. But don't expect a perfectly stable system.
My advice is to just re-install. I know you don't want to, but I would rather do it right the first time, then have to deal with it a couple of weeks later when something goes wrong.
The best success I had with moving a 98se installation to a new mobo was a KT133a based board to a KT333 based board. It lasted for about 2.5 months before it finally crapped out, and most of the hardware is pretty much the same if not identical.
Good luck

Moving XP drive to a new Mac Pro

I have an install of XP via Boot Camp on an old Mac Pro. It exists on it's own hard drive installed in the machine.
I'd like to move it to a new Mac Pro.
Is it as simple as moving the drive to the new machine?
When I run boot camp on the new machine will it recognize the previous install? Or will I need to do a new install?
Thanks
Dj

It 'should' work, but XP will see it is on different hardware and require activation or something. And, you always need to boot from XP CD once when moving it to do some system repair from what I heard.
If you want to address 4-8GB RAM; use both cpus, have better multi-core support, I wouldn't even use XP.
So depends on if this is retail or system builder whether you can deactivate and move the license.

Need assistance moving images to a new hard drive. can you help?

1. My images are stored on an Apple Airport drive, connected wirelessly.
2. I have moved them to a new USB connected External HD.
3 should I also copy the IRDATA and IRCAT Lightroom directory to the new drive before I synch the new directory within lightroom?

Lightroom catalog FAQ
how do I move a catalog?
You can move your catalog to a different location on your computer's hard drive, to an external disk, or to another computer altogether. Simply use the Explorer (Windows) or Finder (Mac OS) to drag or copy the following files to the new location:
Catalog: [catalog name].lrcat
Previews: [catalog name] Previews.lrdata
Smart Previews (Lightroom 5 only): [catalog name] Smart Previews.lrdata
Notice that you're not moving any photos, nor are you moving the Lightroom application itself. If Lightroom can't find the catalog or your photos after you move a catalog, see Lightroom can't find my catalog. How do I find it? Or, My catalog can't find my photos. How do I find them?
To transfer a catalog between a Windows computer and a Mac, copy your catalog, preview, and image files from the original computer onto a flash or other external drive. Then, attach that drive to the second computer and copy the files to the desired location on the second computer.
For a video on how to move a catalog between two computers, watch Julieanne Kost's How to migrate Lightroom to another computer on Adobe TV.

Trying to setup RAID 1 with new SATA drives on xserve 2009 model

Trying to setup RAID 1 with new SATA drives on xserve 2009 model
I have an Xserve rack mount model Xserve 2.26 Quad Core (EMC# 2279) with an Apple RAID card, 24GB RAM (running 10.9 Server software)
Purchased two Western Digital 1TB SATA III 7200 RPM 64MB Cache Black WD1003FZEX drives
It came with three 160GB SATA drives. I'm leaving one of the original 160GB drives for the OS, but I want to replace the 2 other drives and set it up with RAID 1 (mirrored). I bought 2 brand new Western Digital 1TB SATA drives and formatted them on another Mac through Disk Utility with Mac OS Extended (Journaled) formatting. I then placed the new drives in the Xserve and booted it up. After I login it immediately gives me 2 error windows saying...
"Apple RAID Card
The Apple RAID Card installed in your system requires your attention."
It has two buttons underneath this message allowing me to either select 'Ignore' or 'Open RAID Utility'
I've tried to RAID the drives the Disk Utility and through the RAID Utility with no success.
I have both drives mounted on the desktop, as separate drives, but I really need to set these up as a RAID 1.
I've been reading other forums, where others have been able to get this to work by using a jumper on certain pins (5 & 6)of the drive to back down the transfer rate to 1.5 Gb per second. I tried that and it didn't work for me. Maybe I used the wrong pins -- I just don't know. I'm also wondering if there is some Apple firmware that is required on these drives? I'm asking for help from anyone who has gone through this same issue. Thanks in advance.

UPDATE -- I had an issue with the RAID card battery, it was dead and I have since replaced it. But I am still unable to setup the RAID 1 drive configuration. Does anyone know if it has something to do with the faster transfer rates on these new drives. Maybe they need to be clocked down with certain jumper settings on these Western Digital drives? Or am I fighting a losing battle because these drives don't have Apple firmware? Any help would be appreciated. Thanks.

Partitioning a new laptop's RAID drive for scratch disc

I've now set my heart on getting a laptop. I'm doing to much on my old desktop, and getting a laptop is hopefully going to ease the burden & open up some possibilities. Certainly the specs will way better.
I'm seriously thinking about getting a Sony VAIO AR71ZU.
http://vaio.sony.co.uk/view/ShowProduct.action?product=VGN-AR71ZU&site=voe_en_GB_cons&cate gory=VN+AR+Series&assetid=1218032875460
It has a lot f features I like & has 4GB of RAM. Unfortunately it's Vista (Ultimate), but that's what things are coming with now, so that's that.
It has 640GB of HDD space:
Hard Drive Type Serial ATA RAID 0 (0 and 1 supported) 2x320GB
Hard Drive Capacity (GB) 640
Hard Drive Speed (rpm) 5400
The two 320 GB drives look are joined -"con.... something" ! sorry I've forgotten the name for this- the opposite of partitioning. Hence it the drives are seen as one drive. Well for Photoshop one wants a second drive for scratch disc purposes doesn't one. Can I partition this 640GB (320+320GB) drive ? Anyone out there know ? Is it an ok thing to do ?
[One of the added features is "HDD recovery (hidden partition)". I assume this is the backup /recovery facility that comes with Vista Ultimate ? Anyway, it may be of note, as it mentions "hidden partition. Would this interfere with any partitioning ? ]
If I can partition then would it be wise to go for three partitions: one as the main program drive; one for most documents & files; and one for back-up/ other stuff including for use as first scratch disc ?
Anyone wise?
Any advice greatly appreciated.
[I'm also been looking at the possibility of an Alienware laptop, but really I'd rather put that money elsewhere. (Eventually a new desktop but not yet.)]

Thanks, most informative.
I'm considering an Alienware laptop.(Though, expensive!) One can have the double RAID drive, and there is something called SMART BAY which bascially is 3rd drive. Maybe this is a way around things- perhaps get that & make that for the scratch disc...an expensive way around things!

870S-G54 motherboard, not using raid, do I need ATI SB7xx/SB8xx RAID Driver

I have a 870S-G54 motherboard and I am not using raid. Do I need the "ATI SB7xx/SB8xx RAID Driver" from http://www.msi.com/product/mb/870S-G54.html#/?div=Driver&os=All ?
I assumed that driver did not apply at all if I'm not using raid and I haven't installed it, but since the description includes "On-Board PIDE/SATA Drivers" and I'm trying to track down a corrupted file copy issue, I just wanted to double-check that I'm not missing something necessary by accident. Thanks!

If your not using raid, Than no you dont need the raid drivers.

Move Windows 8.1 Pro Hard Drive, Graphics Card and Programs to New Motherboard and CPU

Want to move everything, hard drive, installed programs, video card, network adapter, ram drive, DVD, from one computer to another, nothing will change except motherboard and CPU. Old motherboard and CPU will be installed in a new computer case which
will revert back to a Windows 7 Pro computer with a fresh install and no programs to be used as a dedicated CAD work station. Motherboard and CPU swap will be the only change, even the RAM will be the same. What activation problems will I encounter,
I do not want to re-install anything, if possible.

Hi,
I would like to confirm what kind of licensing you used on Windows 8.1, the OEM or the retailed.
For the OEM one, the Windows 8.1 transferred to another new Motherboard will not be activated.
For the retailed one, you should find that the system will boot with the new motherboard, install some drivers then boot successfully.
You will need to use telephone activation for the updated system, but should not need to re-install. When warned that you need to activate, select the "Contact Microsoft Customer Support" option and follow the instructions. With a tone dial phone
you can do this without speaking to anyone. See http://www.eightforums.com/tutorials/24636-activate-windows-8-phone.html
Kate Li
TechNet Community Support

MOVED: K8N Neo2 - WinXP and Raid driver problem

This topic has been moved to AMD64 nVidia Based board.
K8N Neo2 - WinXP and Raid driver problem

Quote from: SillySider03 on 18-June-05, 22:18:50
Try This.
Yes it worked... I did it a bunch of mins ago, ty a lot anyway

Failed boot after moving hard drive (IDE not SATA)

Greetings all.
I am attempting to setup a headless box, and in doing so I am installing Arch on one system (Sapphire Axion A3-M275 Motherboard), then moving the hard drive to the new system (SGS1660, a VIA CLE266/VT8235 based headless rack-solution). After moving the drive into the SGS1660, the system fails to boot. Attached output from the Serial Console:
Booting 'Arch Linux'
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /vmlinuz26 root=/dev/disk/by-uuid/93df0562-c6e6-4583-9a79-51cd2091247b r
o console=ttyS0,115200
[Linux-bzImage, setup=0x3600, size=0x1ad6d0]
initrd /kernel26.img
[Linux-initrd @ 0x2ff21000, 0x9e7a5 bytes]
Linux version 2.6.30-ARCH (root@T-POWA-LX) (gcc version 4.4.0 20090630 (prerelease) (GCC) ) #1 SMP PREEMPT Mon Jul 20 11:20:32 UTC 2009
KERNEL supported cpus:
Intel GenuineIntel
AMD AuthenticAMD
NSC Geode by NSC
Cyrix CyrixInstead
Centaur CentaurHauls
Transmeta GenuineTMx86
Transmeta TransmetaCPU
UMC UMC UMC UMC
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000002ffd0000 (usable)
BIOS-e820: 000000002ffd0000 - 000000002ffde000 (ACPI data)
BIOS-e820: 000000002ffde000 - 0000000030000000 (ACPI NVS)
BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
BIOS-e820: 00000000ff780000 - 0000000100000000 (reserved)
DMI 2.3 present.
AMI BIOS detected: BIOS may corrupt low RAM, working around it.
last_pfn = 0x2ffd0 max_arch_pfn = 0x100000
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Scanning 0 areas for low memory corruption
modified physical RAM map:
modified: 0000000000000000 - 0000000000010000 (reserved)
modified: 0000000000010000 - 000000000009fc00 (usable)
modified: 000000000009fc00 - 00000000000a0000 (reserved)
modified: 00000000000e0000 - 0000000000100000 (reserved)
modified: 0000000000100000 - 000000002ffd0000 (usable)
modified: 000000002ffd0000 - 000000002ffde000 (ACPI data)
modified: 000000002ffde000 - 0000000030000000 (ACPI NVS)
modified: 00000000fec00000 - 00000000fec01000 (reserved)
modified: 00000000ff780000 - 0000000100000000 (reserved)
init_memory_mapping: 0000000000000000-000000002ffd0000
RAMDISK: 2ff21000 - 2ffbf7a5
ACPI: RSDP 000f6ad0 00014 (v00 ACPIAM)
ACPI: RSDT 2ffd0000 0002C (v01 A M I OEMRSDT 09000521 MSFT 00000097)
ACPI: FACP 2ffd0200 00084 (v02 A M I OEMFACP 09000521 MSFT 00000097)
ACPI: DSDT 2ffd0390 03270 (v01 MiniV MiniV080 00000080 INTL 02002026)
ACPI: FACS 2ffde000 00040
ACPI: OEMB 2ffde040 00046 (v01 A M I AMI_OEM 09000521 MSFT 00000097)
0MB HIGHMEM available.
767MB LOWMEM available.
mapped low ram: 0 - 2ffd0000
low ram: 0 - 2ffd0000
node 0 low ram: 00000000 - 2ffd0000
node 0 bootmap 00011000 - 00016ffc
(9 early reservations) ==> bootmem [0000000000 - 002ffd0000]
#0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
#1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000]
#2 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000]
#3 [0000100000 - 0000626e44] TEXT DATA BSS ==> [0000100000 - 0000626e44]
#4 [002ff21000 - 002ffbf7a5] RAMDISK ==> [002ff21000 - 002ffbf7a5]
#5 [0000099c00 - 0000100000] BIOS reserved ==> [0000099c00 - 0000100000]
#6 [0000627000 - 0000629230] BRK ==> [0000627000 - 0000629230]
#7 [0000010000 - 0000011000] PGTABLE ==> [0000010000 - 0000011000]
#8 [0000011000 - 0000017000] BOOTMAP ==> [0000011000 - 0000017000]
Zone PFN ranges:
DMA 0x00000010 -> 0x00001000
Normal 0x00001000 -> 0x0002ffd0
HighMem 0x0002ffd0 -> 0x0002ffd0
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
0: 0x00000010 -> 0x0000009f
0: 0x00000100 -> 0x0002ffd0
Using APIC driver default
ACPI: PM-Timer IO Port: 0x808
SMP: Allowing 1 CPUs, 0 hotplug CPUs
No local APIC present or hardware disabled
PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
Allocating PCI resources starting at 40000000 (gap: 30000000:cec00000)
NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:1 nr_node_ids:1
PERCPU: Embedded 11 pages at c1606000, static data 24444 bytes
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 194911
Kernel command line: root=/dev/disk/by-uuid/93df0562-c6e6-4583-9a79-51cd2091247b ro console=ttyS0,115200
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
NR_IRQS:512
PID hash table entries: 4096 (order: 12, 16384 bytes)
Fast TSC calibration using PIT
Detected 1326.894 MHz processor.
Console: colour dummy device 80x25
console [ttyS0] enabled
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Initializing HighMem for node 0 (00000000:00000000)
Memory: 772708k/786240k available (2905k kernel code, 12976k reserved, 1052k data, 392k init, 0k highmem)
virtual kernel memory layout:
fixmap : 0xfff4e000 - 0xfffff000 ( 708 kB)
pkmap : 0xff800000 - 0xffc00000 (4096 kB)
vmalloc : 0xf07d0000 - 0xff7fe000 ( 240 MB)
lowmem : 0xc0000000 - 0xeffd0000 ( 767 MB)
.init : 0xc04e3000 - 0xc0545000 ( 392 kB)
.data : 0xc03d647f - 0xc04dd6a8 (1052 kB)
.text : 0xc0100000 - 0xc03d647f (2905 kB)
Checking if this processor honours the WP bit even in supervisor mode...Ok.
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Calibrating delay loop (skipped), value calculated using timer frequency.. 2654.36 BogoMIPS (lpj=4422980)
Security Framework initialized
Mount-cache hash table entries: 512
CPU: L1 I Cache: 64K (32 bytes/line), D cache 64K (32 bytes/line)
CPU: L2 Cache: 64K (32 bytes/line)
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 10k freed
ACPI: Core revision 20090320
ACPI: setting ELCR to 0200 (from 8c20)
weird, boot CPU (#0) not listed by the BIOS.
SMP motherboard not detected.
Local APIC not detected. Using dummy APIC emulation.
SMP disabled
Brought up 1 CPUs
Total of 1 processors activated (2654.36 BogoMIPS).
net_namespace: 1056 bytes
Booting paravirtualized kernel on bare hardware
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=1
PCI: Using configuration type 1 for base access
bio: create slab <bio-0> at 0
ACPI: Interpreter enabled
ACPI: (supports S0 S1 S3 S4 S5)
ACPI: Using PIC for interrupt routing
ACPI: Power Resource [URP1] (off)
ACPI: Power Resource [URP2] (off)
ACPI: Power Resource [FDDP] (off)
ACPI: Power Resource [LPTP] (off)
ACPI: No dock devices found.
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci 0000:00:07.0: PME# supported from D0 D3hot D3cold
pci 0000:00:07.0: PME# disabled
pci 0000:00:10.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:10.0: PME# disabled
pci 0000:00:10.1: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:10.1: PME# disabled
pci 0000:00:10.2: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:10.2: PME# disabled
HPET not enabled in BIOS. You might try hpet=force boot option
pci 0000:00:11.0: quirk: region 0800-087f claimed by vt8235 PM
pci 0000:00:11.0: quirk: region 0400-040f claimed by vt8235 SMB
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11 12 14 *15)
PCI: Using ACPI for IRQ routing
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 10 devices
ACPI: ACPI bus type pnp unregistered
system 00:05: ioport range 0xe900-0xe90f has been reserved
system 00:05: ioport range 0xea00-0xea0f has been reserved
system 00:05: ioport range 0xeb00-0xeb2f has been reserved
system 00:05: ioport range 0xec00-0xec7f has been reserved
system 00:05: ioport range 0xe800-0xe83f has been reserved
system 00:07: ioport range 0x3e0-0x3e7 has been reserved
system 00:07: ioport range 0x4d0-0x4d1 has been reserved
system 00:07: ioport range 0x800-0x87f has been reserved
system 00:07: ioport range 0x400-0x41f could not be reserved
system 00:09: iomem range 0x0-0x9ffff could not be reserved
system 00:09: iomem range 0xe0000-0xfffff could not be reserved
system 00:09: iomem range 0x100000-0x2fffffff could not be reserved
pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
pci 0000:00:01.0: IO window: disabled
pci 0000:00:01.0: MEM window: 0xddd00000-0xdfdfffff
pci 0000:00:01.0: PREFETCH window: 0x000000d5c00000-0x000000ddbfffff
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
NET: Registered protocol family 1
Unpacking initramfs...
Freeing initrd memory: 633k freed
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: overridden by ACPI.
Scanning for low memory corruption every 60 seconds
audit: initializing netlink socket (disabled)
type=2000 audit(1248948860.509:1): initialized
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
msgmni has been set to 1510
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci 0000:00:01.0: disabling DAC on VIA PCI bridge
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:06: 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.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
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
Using IPI No-Shortcut mode
registered taskstats version 1
Initalizing network drop monitor service
Freeing unused kernel memory: 392k freed
:: Loading Initramfs
:: Running Hook [udev]
:: Loading udev...SCSI subsystem initialized
pata_acpi 0000:00:11.1: can't derive routing for PCI INT A
pata_acpi 0000:00:11.1: can't derive routing for PCI INT A
done.
Waiting 10 seconds for device /dev/disk/by-uuid/93df0562-c6e6-4583-9a79-51cd2091247b ...
Root device '/dev/disk/by-uuid/93df0562-c6e6-4583-9a79-51cd2091247b' doesn't exist, attempting to create it
ERROR: Failed to parse block device ids for '/dev/disk/by-uuid/93df0562-c6e6-4583-9a79-51cd2091247b'
ERROR: Unable to detect or create root device '/dev/disk/by-uuid/93df0562-c6e6-4583-9a79-51cd2091247b'
You are being dropped to a recovery shell
Type 'reboot' to reboot
Type 'exit' to try and continue booting
NOTE: klibc contains no 'ls' binary, use 'echo *' instead
If the device '/dev/disk/by-uuid/93df0562-c6e6-4583-9a79-51cd2091247b' gets created while you are here,
try adding 'rootdelay=10' or higher to the kernel command-line
ramfs$
I think what is happening is that the kernel does not have the drivers for the IDE controller on the board for the CLE266/VT8235. Does this seem accurrate? And if so, how can I verify the current kernel config, then compile a kernel with everything else Arch needs to boot properly? I am familiar with the old means of setting up a kernel using the 'make menuconfig; make; make modules_install' etc method.
Thanks for the help in advance!

Hi, not sure if this is still causing you an issue, but I just ran into the same problem.
For me, I have a Sharp PC=MM1110 which has no cd drive and doesn't like to boot from USB. To get Arch installed on it, I had to attach it to another PC (via it's docking cradle, which lets it show up as a USB hard drive), then boot the other PC from an Arch install cd and select the USB hdd for all of the partitioning etc.
When I rebooted after the installation, the Sharp wouldn't boot.
First, I had to edit the grub menu entry to point to (hd0,0), at which point I got the error listed in the first post... Failed to parse block device id's.
If i booted into fallback mode, it booted without a problem.
For me, the solution to finally get it working was to boot into fallback mode, remount the filesystem as r/w, and run mkinitcpio -g filename to rebuild the kernel. Once completed all I had to do was point grub to the new kernel image and it booted ok.
Hope this is useful to someone

Why no RAID options for new disks?

Hi support group,
"My name is Shaun, and I am a mac-aholic"
I inserted 4 new 3TB disks into the bays of my Mac Pro (2012), and there is no RAID option for them.
How I got here:
Inserted the WD Red drives, and they were not initiated.
I "erased" the drives, gave them names, and they appear in Disk Utility in grey drives.
Went to set up the RAID, and move the drives into the RAID, but got an error that they could not be used.
It appears to me that disk utility is not allowing me to fully use those drives. I Have created RAID drives before with no issue in RAID1 with 3TB drives before on this machine. Am perplexed, I thought this to be the easy and simple part of my upgrade odyssey! Did I screw up the initialization? On all FOUR drives?
Now, if I click on the drives, the RAID option does not present itself.
FWIW, I am using OS X 10.9.5, on Mac Pro 5,1. I boot from PCIe card. My end goal is to create a 4-disk RAID 10 using the four SATA connections on the MP.

It was really pretty simple based on your feedback, I powered down, removed the drives from the SATA backplane, moved each drive separately to the USB enclosure, then re-"erased" in OSX-Etended. I ejected each drive when finished, and moved to the next one until all four were re-"erased". Then I restarted the Mac with all four in the SATA connections, and all four were visible and had the RAID option tab. I created the three RAID schemes (two stripe and one mirror), and dragged the drives into the RAID option. Then I hit "create" or some other command to finish the RAID.
Note that I did get an error on the RAID creation. From memory, this was "cannot create RAID without an unmounted disk" or something like that. I cleared the error, and then opened back up Disk Utility. All the RAIDs were listed, and were operational with the green "On" signal. I could read/write/transfer from the RAID. Once I transfer the data to this RAID, I will work on a way to test it, but if any risk to the data, I might just leave well enough alone.
For now, it seems I have a fully functional RAID 1+0 using the four HDD on the SATA connections in my Mac Pro 5,1.

I cannot install windows 7 x64 with AMD/ASUS RAID driver

Trying to install Windows 7 Ultimate x64 on an ASUS M5A97 mobo with AMD SB850 RAID, two WD 750GB drives configured as RAID 0. No drives are recognized by W7 install, so I choose Load Drivers. I put the drivers on a USB stick. Install finds the drivers there,
starts loading them, then comes back with "Installing an unsigned 64 bit driver is not supported and may result in an unstable Windows installation." I downloaded the latest drivers from ASUS website which are WHQL certified (as are the one's on the motherboard
disk). I saw other posts that recommend clicking Repair instead of Install, but I don't see where that option is. All I am given as options are Upgrade or Install. Choosing Upgrade tells me to boot Windows first. But this is a brand new install so...
I tried pressing F8 as setup was booting and chose "Disable Signed Driver Requirement" but that had no effect at all. If I turn off the RAID W7 sees both disks and happily installs. I see related posts going back to 2009; surely someone has
a solution for this issue?
Da Bomb

Hi guys,
I have been struggling with the same issue.
Win7 x64. Gigabyte GA-X79-UD3 Mobo with Intel core i7-3930K at 3.20 GHz
Marvell 88SE9172 SATA RAID controller with two Hitachi 500 GB spinning disks configured as RAID1
Windows would get to the point of asking for a mass storage drive. It would not see the RAID I had created.
Tried every driver I could find. Tried drivers from the "Station Drivers" website. Tried Marvell drivers for the same chip from the ASUS website. No luck. Tried loading from CD as well as USB flash drive. Always the same result... Windows would find
the drivers appropriate for the hardware found, I would select the RAID version, and after a few seconds, would report that the drivers were unsigned, and the installation was not supported for 64-bit drivers. Clicking OK would take me back to the load drivers
display with no new drives listed in the available drives window.
I tried hitting F8 during startup, and selected the "allow install of unsigned drivers option". That didn't do ANYTHING. Still the same error.
Someone suggested putting the drivers in the root directory. That didn't work. I also disabled all other drives except one CD rom and a USB drive and made sure that my RAID array was the first drive in the boot list.
Tried doing a windows repair, as someone else suggested. (This is an option that is available on the install disk I am using. It's enabled as part of EMS (emergency management services) in setup. Anyway, this was reported to be a workaround
to the signed driver issue. It would allow me to browse to the individual files, but no matter which one I selected, the response was "cannot find hardware appropriate to the driver selected" or some such nonesense. So I gave up on that.
Doing the install with the controller in IDE mode with just one drive connected, would result is Windows installing without a hitch. The problem was clearly when I presented 64-bit windows with a controller in RAID mode.
Long story less long, here's what worked for me....
Out of desperation, I began trying other subfolders in the driver lists. The Gigabyte manual indicated that the AMD64 subfolder was the correct one for the Marvell controller, when using RAID mode with 64-bit Windows. After trying every subfolder of
every driver I could find, the driver in the i386 folder actually worked. It initially came back with the same error about unsigned drivers, but after clicking OK, my RAID drive showed up in the list. I have been able to partition and format
the drive from within Windows setup, and am continuing with the install now. Hopefully won't be any problems booting from the drive post install, but so far it looks good, and I'm relieved that I was able to get it this far.
The whole process has been one of the most frustrating computing experiences I've ever had. This is what it was like back in the 90's when building PCs from scratch. I'm amazed that in this day and age the process is still so poorly documented
and filled with potholes, traps and caveats. Shame on the entire PC industry for allowing this to continue. I'm not asking that they jump in and try to automate it and do all the thinking for me (their solution for everything lately)...all I'm asking for it
clear, concise and accurate INFORMATION.
With the right information, and software that provides accurate feedback, this would all be easy...and even fun.
Hope this helps someone faced with the same problem.

Windows 8.1 fails to boot with error code 0x5c after moving physical drives

Hi,
i just rearranged hard drives on my desktop PC. I removed 4 RAID drives, installed a single drive and reattached all drives into different SATA connectors on the motherboard.
After this, my PC doesn't boot. IT always fails with errorcode 0x5c. My OS is on SSD drive, which was not part of the RAID drive so it should boot up just fine - except it doesn't.
I've tried safe mode, I've tried starting with driver signature enforcement disabled - but it never does boot up properly.
What else do i do apart from reinstalling the OS?

Hi,
This error 0x5c indicates that the HAL initialization failed. A hardware abstraction layer (HAL) is an abstraction layer, implemented in software, between the physical hardware of a computer and the software that runs on that computer.
It seems that the issue can be cause by interface compatible. Please enter BIOS and change SATA to AHCI to see what’s going on.
Also, I suggest you arrange your 4 RAID drives back to original SATA connector and connect the new single drive to another to check the results.
Hope this could be helpful.
Kate Li
TechNet Community Support

Moving RAID- drives to new motherboard

Similar Messages

Maybe you are looking for