Unable to move existing installation to software RAID-1 setup

I have an existing Arch Linux amd64 installation which I want to move to a RAID-1 setup.
I followed the following Wiki article:
Arch Linux Wiki - Installing with Software RAID or LVM
with necesary changes applied and some supplemental advice from the equivalent Gentoo Wiki article:
Gentoo Linux Wiki - HOWTO Install on Software RAID
mainly for the "--assume-clean" command-line switch to mdadm.
With a Larch live CD I took a tarball backup of each partition.
Then with cfdisk partitioned the disks.
And copied their partition tables to their RAID-1 mirrors:
sfdisk -d /dev/sda | sfdisk /dev/sdb
Now, I cannot boot Arch on the RAID-1 setup.
After initramfs is finished, I get a kernel panic as the "/" partition cannot be mounted.
The mkinitcpio.conf that created my kernel is this:
MODULES="ahci pata_amd ata_generic sata_nv sata_sil"
HOOKS="base udev autodetect pata scsi sata usbinput keymap raid lvm2 filesystems"
My rc.conf is this:
MODULES=(raid1 powernow-k8 fuse forcedeth ac battery button fan thermal loop)
My fstab ("/" and "/boot" lines) is this:
/dev/md0 /boot ext3 noatime 0 1
/dev/md1 / ext3 noatime 0 1
And my menu.lst is this:
timeout 5
default 0
color light-blue/black light-cyan/blue
title Arch Linux
root (hd0,0)
kernel /vmlinuz26 root=/dev/md1 ro swncq=1 md=0,/dev/sda1,/dev/sdb1 md=1,/dev/sda2,/dev/sdb2
initrd /kernel26.img
I even tried another shot by passing all ten RAID-1 arrays (md0 to md9) as kernel parameters, but still, no effect.
Any help would be greatly appreciated.
PS: I have created a correct mdadm.conf file with:
mdadm -D --scan >>/etc/mdadm.conf
Last edited by wantilles (2008-09-08 08:28:20)

My experience with raid suggests that mdadm setups work after boot-up as "software raid". The array is assembled and "ID'd" with mdadm --assemble command.
IMHO In order to utilize mdadm for boot-up, how does the user "assemble" before the elements needed for mdadm --assemble are accessible?
IMHO My understanding of booting with raid involves the use of dmraid, a "software" raid program which can be adapted to boot use. It involves changes to the boot sequence to prevent loss of dmraid params during the boot processes such as hardware detect AFAIK.

Similar Messages

[Solved] Move Software RAID 5 Array From NAS To Arch

Edit: I probably never had a problem at all, the error in dmesg probably just scared me, because after I disconnected it I noticed that /dev/d127 was 8.1 TB, the exact size of my RAID array node in my NAS which was /dev/md0, I just overlooked it. I reconnected it to my pc and mounted /dev/md127 to /mnt/raid and got this wonderful sight!
[bran@ra ~]$ ls /mnt/raid
data lost+found meta sys
[bran@ra ~]$ ls /mnt/raid/data/
data ftproot module _NAS_Media _NAS_Piczza_ _NAS_Recycle_RAID _P2P_DownLoad_ stackable _SYS_TMP TV USBHDD
download htdocs Movies _NAS_NFS_Exports_ NAS_Public nzbget-downloads PLEX_CONFIG sys tmp USBCopy
I bought a Thecus N4520 a few months ago and it's ok but programs crash a lot and they're hard to debug, apps have to be updated manually and the whole thing is moderately underpowered. I'm trying to move the software RAID 5 array from the NAS to my desktop, the kernel seems to detect that there is a RAID array but all these drives aren't part of it. I'm pretty new to RAID and I'm just getting my feet wet with it.
When I try to assemble the RAID array, it just tells me that it isn't an md array. How can I get it to build my array?
[bran@ra ~]$ sudo mdadm --assemble /dev/sdb /dev/sdc /dev/sdd /dev/sde
mdadm: device /dev/sdb exists but is not an md array.
Found this little chunk of info in dmesg, it says that the md devices have unknown partition tables.
[ 3.262225] md: raid1 personality registered for level 1
[ 3.262483] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
[ 3.262508] iTCO_wdt: Found a Patsburg TCO device (Version=2, TCOBASE=0x0460)
[ 3.262585] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[ 3.262933] md/raid1:md126: active with 4 out of 4 mirrors
[ 3.262961] md126: detected capacity change from 0 to 536850432
[ 3.263272] RAID1 conf printout:
[ 3.263274] --- wd:4 rd:4
[ 3.263276] disk 0, wo:0, o:1, dev:sdc3
[ 3.263276] disk 1, wo:0, o:1, dev:sdb3
[ 3.263277] disk 2, wo:0, o:1, dev:sdd3
[ 3.263278] disk 3, wo:0, o:1, dev:sde3
[ 3.263501] md: bind<sde4>
[ 3.264810] md: bind<sdb2>
[ 3.268262] async_tx: api initialized (async)
[ 3.272632] md: raid6 personality registered for level 6
[ 3.272636] md: raid5 personality registered for level 5
[ 3.272637] md: raid4 personality registered for level 4
[ 3.272905] md/raid:md127: device sdb2 operational as raid disk 1
[ 3.272908] md/raid:md127: device sde2 operational as raid disk 3
[ 3.272910] md/raid:md127: device sdd2 operational as raid disk 2
[ 3.272911] md/raid:md127: device sdc2 operational as raid disk 0
[ 3.273211] md/raid:md127: allocated 0kB
[ 3.273241] md/raid:md127: raid level 5 active with 4 out of 4 devices, algorithm 2
[ 3.273243] RAID conf printout:
[ 3.273244] --- level:5 rd:4 wd:4
[ 3.273245] disk 0, o:1, dev:sdc2
[ 3.273246] disk 1, o:1, dev:sdb2
[ 3.273247] disk 2, o:1, dev:sdd2
[ 3.273248] disk 3, o:1, dev:sde2
[ 3.273273] md127: detected capacity change from 0 to 8929230716928
[ 3.273322] RAID conf printout:
[ 3.273326] --- level:5 rd:4 wd:4
[ 3.273329] disk 0, o:1, dev:sdc2
[ 3.273331] disk 1, o:1, dev:sdb2
[ 3.273332] disk 2, o:1, dev:sdd2
[ 3.273360] disk 3, o:1, dev:sde2
[ 3.283617] md126: unknown partition table
[ 3.309239] md127: unknown partition table
[ 3.312660] md: bind<sdb4>
[ 3.318291] md/raid1:md124: not clean -- starting background reconstruction
[ 3.318296] md/raid1:md124: active with 4 out of 4 mirrors
[ 3.318333] md124: detected capacity change from 0 to 10736291840
[ 3.318385] RAID1 conf printout:
[ 3.318391] --- wd:4 rd:4
[ 3.318395] disk 0, wo:0, o:1, dev:sdc4
[ 3.318398] disk 1, wo:0, o:1, dev:sdb4
[ 3.318402] disk 2, wo:0, o:1, dev:sdd4
[ 3.318405] disk 3, wo:0, o:1, dev:sde4
[ 3.319890] md124: unknown partition table
[ 3.323462] md: bind<sde1>
[ 3.338094] md/raid1:md125: active with 4 out of 4 mirrors
[ 3.338225] md125: detected capacity change from 0 to 2146414592
[ 3.338253] RAID1 conf printout:
[ 3.338258] --- wd:4 rd:4
[ 3.338262] disk 0, wo:0, o:1, dev:sdc1
[ 3.338266] disk 1, wo:0, o:1, dev:sdb1
[ 3.338268] disk 2, wo:0, o:1, dev:sdd1
[ 3.338271] disk 3, wo:0, o:1, dev:sde1
Here's my full dmesg
mdadm.conf
# The designation "partitions" will scan all partitions found in /proc/partitions
DEVICE partitions
ARRAY /dev/md127 metadata=1.2 name=(none):0 UUID=d1d14afc:23490940:a0f7f996:d7b87dfb
ARRAY /dev/md126 metadata=1.2 name=(none):50 UUID=d43d5dd6:9446766e:1a7486f4:b811e16d
ARRAY /dev/md125 metadata=1.2 name=(none):10 UUID=f502437a:d27d335a:d11578d5:6e119d58
ARRAY /dev/md124 metadata=1.2 name=(none):70 UUID=ea980643:5c1b79e8:64f1b4cb:2462799b
Last edited by brando56894 (2014-04-21 22:51:01)

Sorry I numbered them to show the flow of information, this was also just a place for me to store info as I worked through it. I managed to get it to work by creating a partition that takes up the whole drive and is actually 22 GB larger than all the other drives (since I found out that the had root, swap and home partitions that are no longer needed).
I should be able to resize the other partitions without a problem, correct? They're EXT4. Should I unmount the raid array and do them individually, remount the array, let it sync and do the next? Or just unmount the array, resize all of them, mount it and let it sync?

Can you move a software raid 1 from one mac to another

I have a 2 disc software raid 1 on my powermac and I want to move it to my mac pro. Does anyone know if I can do this?

It appears that in Mac OS X 10.4, and again in the transition to 10.7, RAID format may have undergone dramatic changes. If you are trying to move a RAID array across those boundaries, you may not have the best results moving the drives directly.

TS4148 i update my 3gs to 6.1 from 4.1 after installation of software it shows connect to itunes or connect to wi-fi when i connect it to itunes it shows the iphone tab in itunes bt after some times it say we are unable to complete your request please he

i update my 3gs to 6.1 from 4.1 after installation of software it shows connect to itunes or connect to wi-fi when i connect it to itunes it shows the iphone tab in itunes bt after some times it say we are unable to complete your request please help me

That would be the wireless number assigned by AT&T when the purchaser of the iPhone signed up as a customer with AT&T. If neither you nor your uncle ever activated the iPhone with AT&T, click the "non customer" button.
Note that jailbreaking often renders it impossible to get an iPhone officially unlocked, so don't be surprised if it fails. If it does, then you may have to buy a new iPhone, this time one that is officially unlocked.
Regards.

Software raid won't boot after updating to "mdadm" in mkinitcpio.conf

After a power outage I've discovetred the config I was using (with raid in mkinitcpio.conf) no longer works, it's mdadm now - that's fine. I've updated that and re-run mkinitcpio successfully, however my system is unable to boot from the root filesystem /dev/md2 like so:
Waiting for 10 seconds for device /dev/md2 ...
Root device '/dev/md2' doesn't exist. Attempting to create it.
ERROR: Unable to determine major/minor number of root device '/dev/md2'.
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
/bin/sh: can't access tty; job control turned off
[ramfs /]#
As far as I can see from reading various threads and http://wiki.archlinux.org/index.php/Ins … AID_or_LVM I'm doing the right things now (although I'm not using lvm at all, which makes the installation document a little confusing).
I think I've included all the appropriate bits of config here that should be working. I assume I've missed something fundamental - any ideas?
menu.lst:
# (0) Arch Linux
title Arch Linux [/boot/vmlinuz26]
root (hd0,0)
kernel /vmlinuz26 root=/dev/md2 ro
initrd /kernel26.img
mkinitcpio.conf:
HOOKS="base udev autodetect pata scsi mdadm sata filesystems"
fstab:
/dev/md1 /boot ext3 defaults 0 1
/dev/md2 / ext3 defaults 0 1
mdadm.conf
ARRAY /dev/md1 level=raid1 num-devices=2 metadata=0.90 UUID=7ae70fa6:9f54ba0a:21
47a9fe:d45dbc0c
ARRAY /dev/md2 level=raid1 num-devices=2 metadata=0.90 UUID=20560268:8a089af7:e6
043406:dbdabe38
Thanks!

Hi magec, that's quite helfpul - I've certainly got further.
Before I was doing this to set up the chroot (which is what is suggested in the wiki article about setting up software raid):
mdadm -A /dev/md1 /dev/sda1 /dev/sdb1
mdadm -A /dev/md2 /dev/sda2 /dev/sdb2
mount /dev/md2 /mnt
mount /dev/md1 /mnt/boot
mount -o bind /dev /mnt/dev
mount -t proc none /mnt/proc
chroot /mnt /bin/bash
But based on your suggestion it's working better
mdadm -A /dev/md1 /dev/sda1 /dev/sdb1
mdadm -A /dev/md2 /dev/sda2 /dev/sdb2
mount /dev/md2 /mnt
mount /dev/md1 /mnt/boot
mount -t proc none /mnt/proc
mount -t sysfs none /mnt/sys
mount -n -t ramfs none /mnt/dev
cp -Rp /dev/* /mnt/dev
chroot /mnt /bin/bash
The boot is now getting further, but now I'm getting:
md: md2 stopped.
md: bind<sdb2>
md: bind<sda2>
raid1: raid set md2 active with 2 out of 2 mirrors
md2: detected capacity change from 0 to 32218349568
mdadm: /dev/md2 has been started with 2 drives.
md2: Waiting 10 seconds for device /dev/md2 ...
unknown partition table
mount: mounting /dev/md2 on /new_root failed: No such device
ERROR: Failed to mount the real root device.
Bailing out, you are on your own. Good luck.
/bin/sh: can't access tty; job contol turned off
[ramfs /]#
The bit that really confuses me is this:
[ramfs /]# cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 sda2[0] sdb2[1]
31463232 blocks [2/2] [UU]
md1 : active raid1 sda1[0] sdb1[1]
208704 blocks [2/2] [UU]
unused devices: <none>
[ramfs /]# mount /dev/md2 /new_root
mount: mounting /dev/md2 on /new_root failed: No such file or directory
[ramfs /]# ls /dev/md2
/dev/md2
[ramfs /]#
So the array is up, the device node is there but it can't be mounted? Very strange.
Last edited by chas (2010-05-02 11:24:09)

I have some questions regarding setting up a software RAID 0 on a Mac Pro

I have some questions regarding setting up a software RAID 0 on a Mac pro (early 2009).
These questions might seem stupid to many of you, but, as my last, in fact my one and only, computer before the Mac Pro was a IICX/4/80 running System 7.5, I am a complete novice regarding this particular matter.
A few days ago I installed a WD3000HLFS VelociRaptor 300GB in bay 1, and moved the original 640GB HD to bay 2. I now have 2 bootable internal drives, and currently I am using the VR300 as my startup disk. Instead of cloning from the original drive, I have reinstalled the Mac OS, and all my applications & software onto the VR300. Everything is backed up onto a WD SE II 2TB external drive, using Time Machine. The original 640GB has an eDrive partition, which was created some time ago using TechTool Pro 5.
The system will be used primarily for photo editing, digital imaging, and to produce colour prints up to A2 size. Some of the image files, from scanned imports of film negatives & transparencies, will be 40MB or larger. Next year I hope to buy a high resolution full frame digital SLR, which will also generate large files.
Currently I am using Apple's bundled iPhoto, Aperture 2, Photoshop Elements 8, Silverfast Ai, ColorMunki Photo, EZcolor and other applications/software. I will also be using Photoshop CS5, when it becomes available, and I will probably change over to Lightroom 3, which is currently in Beta, because I have had problems with Aperture, which, until recent upgrades (HD, RAM & graphics card) to my system, would not even load images for print. All I had was a blank preview page, and a constant, frozen "loading" message - the symbol underneath remained static, instead of revolving!
It is now possible to print images from within Aperture 2, but I am not happy with the colour fidelity, whereas it is possible to produce excellent, natural colour prints using its "minnow" sibling, iPhoto!
My intention is to buy another 3 VR300s to form a 4 drive Raid 0 array for optimum performance, and to store the original 640GB drive as an emergency bootable back-up. I would have ordered the additional VR300s already, but for the fact that there appears to have been a run on them, and currently they are out of stock at all, but the more expensive, UK resellers.
I should be most grateful to receive advice regarding the following questions:
QUESTION 1:
I have had a look at the RAID setting up facility in Disk Utility and it states: "To create a RAID set, drag disks or partitions into the list below".
If I install another 3 VR300s, can I drag all 4 of them into the "list below" box, without any risk of losing everything I have already installed on the existing VR300?
Or would I have to reinstall the OS, applications and software again?
I mention this, because one of the applications, Personal accountz, has a label on its CD wallet stating that the Licence Key can only be used once, and I have already used it when I installed it on the existing VR300.
QUESTION 2:
I understand that the failure of just one drive will result in all the data in a Raid 0 array being lost.
Does this mean that I would not be able to boot up from the 4 drive array in that scenario?
Even so, it would be worth the risk to gain the optimum performance provide by Raid 0 over the other RAID setup options, and, in addition to the SE II, I will probably back up all my image files onto a portable drive as an additional precaution.
QUESTION 3:
Is it possible to create an eDrive partition, using TechTool Pro 5, on the VR300 in bay !?
Or would this not be of any use anyway, in the event of a single drive failure?
QUESTION 4:
Would there be a significant increase in performance using a 4 x VR300 drive RAID 0 array, compared to only 2 or 3 drives?
QUESTION 5:
If I used a 3 x VR300 RAID 0 array, and installed either a cloned VR300 or the original 640GB HD in bay 4, and I left the Startup Disk in System Preferences unlocked, would the system boot up automatically from the 4th. drive in the event of a single drive failure in the 3 drive RAID 0 array which had been selected for startup?
Apologies if these seem stupid questions, but I am trying to determine the best option without foregoing optimum performance.

Well said.
Steps to set up RAID
Setting up a RAID array in Mac OS X is part of the installation process. This procedure assumes that you have already installed Mac OS 10.1 and the hard drive subsystem (two hard drives and a PCI controller card, for example) that RAID will be implemented on. Follow these steps:
1. Open Disk Utility (/Applications/Utilities).
2. When the disks appear in the pane on the left, select the disks you wish to be in the array and drag them to the disk panel.
3. Choose Stripe or Mirror from the RAID Scheme pop-up menu.
4. Name the RAID set.
5. Choose a volume format. The size of the array will be automatically determined based on what you selected.
6. Click Create.
Recovering from a hard drive failure on a mirrored array
1. Open Disk Utility in (/Applications/Utilities).
2. Click the RAID tab. If an issue has occurred, a dialog box will appear that describes it.
3. If an issue with the disk is indicated, click Rebuild.
4. If Rebuild does not work, shut down the computer and replace the damaged hard disk.
5. Repeat steps 1 and 2.
6. Drag the icon of the new disk on top of that of the removed disk.
7. Click Rebuild.
http://support.apple.com/kb/HT2559
Drive A + B = VOLUME ONE
Drive C + D = VOLUME TWO
What you put on those volumes is of course up to you and easy to do.
A system really only needs to be backed up "as needed" like before you add or update or install anything.
/Users can be backed up hourly, daily, weekly schedule
Media files as needed.
Things that hurt performance:
Page outs
Spotlight - disable this for boot drive and 'scratch'
SCRATCH: Temporary space; erased between projects and steps.
http://en.wikipedia.org/wiki/StandardRAIDlevels
(normally I'd link to Wikipedia but I can't load right now)
Disk drives are the slowest component, so tackling that has always made sense. Easy way to make a difference. More RAM only if it will be of value and used. Same with more/faster processors, or graphic card.
To help understand and configure your 2009 Nehalem Mac Pro:
http://arstechnica.com/apple/reviews/2009/04/266ghz-8-core-mac-pro-review.ars/1
http://macperformanceguide.com/
http://www.macgurus.com/guides/storageaccelguide.php
http://www.macintouch.com/readerreports/harddrives/index.html
http://macperformanceguide.com/OptimizingPhotoshop-Configuration.html
http://kb2.adobe.com/cps/404/kb404440.html

Problem description: My iMac (early 2008) with OS 10.10.2 runs slow. I have run EtreCheck several times, and I am unable to move beyond Problem System Launch Agents (11 processes killed due to memory pressure) and Launch Daemons (12 processes killed

Problem description:
My iMac (early 2008) with OS 10.10.2 runs slow. I have run EtreCheck several times, and I am unable to move beyond Problem System Launch Agents (11 processes killed due to memory pressure) and Launch Daemons (12 processes killed).
EtreCheck version: 2.1.8 (121)
Report generated April 14, 2015 at 9:50:48 AM EDT
Download EtreCheck from http://etresoft.com/etrecheck
Click the [Click for support] links for help with non-Apple products.
Click the [Click for details] links for more information about that line.
Hardware Information: ℹ️
    iMac (24-inch, Early 2008) (Verified)
    iMac - model: iMac8,1
    1 3.06 GHz Intel Core 2 Duo CPU: 2-core
    4 GB RAM Upgradeable
        BANK 0/DIMM0
            2 GB DDR2 SDRAM 800 MHz ok
        BANK 1/DIMM1
            2 GB DDR2 SDRAM 800 MHz ok
    Bluetooth: Old - Handoff/Airdrop2 not supported
    Wireless: en1: 802.11 a/b/g/n
Video Information: ℹ️
    NVIDIA GeForce 8800 GS - VRAM: 512 MB
        iMac 1920 x 1200
System Software: ℹ️
    OS X 10.10.2 (14C1510) - Time since boot: 4 days 20:29:22
Disk Information: ℹ️
    Hitachi HDS721010KLA330 disk0 : (1 TB)
        EFI (disk0s1) <not mounted> : 210 MB
        Mac iBook HD (disk0s2) / : 999.35 GB (521.60 GB free)
        Recovery HD (disk0s3) <not mounted> [Recovery]: 650 MB
USB Information: ℹ️
    Apple Inc. Built-in iSight
    Apple, Inc. Keyboard Hub
        Apple, Inc Apple Keyboard
    Apple Computer, Inc. IR Receiver
    Apple Inc. BRCM2046 Hub
        Apple Inc. Bluetooth USB Host Controller
Configuration files: ℹ️
    /etc/sysctl.conf - Exists
Gatekeeper: ℹ️
    Mac App Store and identified developers
Problem System Launch Agents: ℹ️
    [killed]    com.apple.CallHistoryPluginHelper.plist
    [killed]    com.apple.CallHistorySyncHelper.plist
    [killed]    com.apple.coreservices.appleid.authentication.plist
    [killed]    com.apple.icloud.fmfd.plist
    [killed]    com.apple.Maps.pushdaemon.plist
    [killed]    com.apple.printtool.agent.plist
    [killed]    com.apple.SafariNotificationAgent.plist
    [killed]    com.apple.sbd.plist
    [killed]    com.apple.scopedbookmarkagent.xpc.plist
    [killed]    com.apple.telephonyutilities.callservicesd.plist
    [killed]    com.apple.warmd_agent.plist
    11 processes killed due to memory pressure
Problem System Launch Daemons: ℹ️
    [killed]    com.apple.AssetCacheLocatorService.plist
    [killed]    com.apple.ctkd.plist
    [killed]    com.apple.emond.aslmanager.plist
    [killed]    com.apple.icloud.findmydeviced.plist
    [killed]    com.apple.ifdreader.plist
    [killed]    com.apple.nehelper.plist
    [killed]    com.apple.nesessionmanager.plist
    [killed]    com.apple.periodic-daily.plist
    [killed]    com.apple.periodic-weekly.plist
    [killed]    com.apple.softwareupdate_download_service.plist
    [killed]    com.apple.wdhelper.plist
    [killed]    org.cups.cupsd.plist
    12 processes killed due to memory pressure
Launch Agents: ℹ️
    [not loaded]    com.adobe.AAM.Updater-1.0.plist [Click for support]
    [running]    com.adobe.AdobeCreativeCloud.plist [Click for support]
Launch Daemons: ℹ️
    [loaded]    com.adobe.fpsaud.plist [Click for support]
    [loaded]    com.adobe.SwitchBoard.plist [Click for support]
    [running]    com.arubanetworks.via.NetworkMonitorLaunchd.plist [Click for support]
    [loaded]    com.microsoft.office.licensing.helper.plist [Click for support]
User Launch Agents: ℹ️
    [loaded]    com.adobe.AAM.Updater-1.0.plist [Click for support]
    [loaded]    com.adobe.ARM.[...].plist [Click for support]
    [loaded]    com.adobe.ARM.[...].plist [Click for support]
    [loaded]    com.google.keystone.agent.plist [Click for support]
    [running]    com.spotify.webhelper.plist [Click for support]
User Login Items: ℹ️
    ChronoSyncBackgrounder    Application (/Library/Application Support/ChronoSync/ChronoSyncBackgrounder.app)
    Dropbox    Application (/Applications/Dropbox.app)
    Canon IJ Network Scanner Selector2    Application Hidden (/Library/Printers/Canon/IJScanner/Utilities/Canon IJ Network Scanner Selector2.app)
    Google Drive    Application (/Applications/Google Drive.app)
Internet Plug-ins: ℹ️
    Google Earth Web Plug-in: Version: 6.1 [Click for support]
    Default Browser: Version: 600 - SDK 10.10
    AdobeExManDetect: Version: AdobeExManDetect 1.1.0.0 - SDK 10.7 [Click for support]
    Flip4Mac WMV Plugin: Version: 3.1.0.24   - SDK 10.8 [Click for support]
    OVSHelper: Version: 1.1 [Click for support]
    AdobeAAMDetect: Version: AdobeAAMDetect 2.0.0.0 - SDK 10.7 [Click for support]
    AdobePDFViewerNPAPI: Version: 11.0.10 - SDK 10.6 [Click for support]
    DivX Web Player: Version: 3.2.4.1250 - SDK 10.6 [Click for support]
    FlashPlayer-10.6: Version: 17.0.0.134 - SDK 10.6 [Click for support]
    Flash Player: Version: 17.0.0.134 - SDK 10.6 Outdated! Update
    iPhotoPhotocast: Version: 7.0
    QuickTime Plugin: Version: 7.7.3
    SharePointBrowserPlugin: Version: 14.4.8 - SDK 10.6 [Click for support]
    AdobePDFViewer: Version: 11.0.10 - SDK 10.6 [Click for support]
    Silverlight: Version: 5.1.20913.0 - SDK 10.6 [Click for support]
    JavaAppletPlugin: Version: 15.0.0 - SDK 10.10 Check version
User internet Plug-ins: ℹ️
    WebEx: Version: 1.0 [Click for support]
    Google Earth Web Plug-in: Version: 7.1 [Click for support]
3rd Party Preference Panes: ℹ️
    Adobe Version Cue CS2 [Click for support]
    Flash Player [Click for support]
    Flip4Mac WMV [Click for support]
    VIA PrefPane [Click for support]
Time Machine: ℹ️
    Time Machine not configured!
Top Processes by CPU: ℹ️
         3%    WindowServer
         3%    Mail
         2%    com.apple.iCloudHelper
         1%    Creative Cloud
         1%    Google Chrome
Top Processes by Memory: ℹ️
    223 MB    Google Chrome
    150 MB    Finder
    129 MB    Google Chrome Helper
    112 MB    Mail
    69 MB    Google Drive
Virtual Memory Information: ℹ️
    35 MB    Free RAM
    1.45 GB    Active RAM
    1.45 GB    Inactive RAM
    888 MB    Wired RAM
    27.01 GB    Page-ins
    851 MB    Page-outs

When you see a beachball cursor or the slowness is especially bad, note the exact time: hour, minute, second.
These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
The title of the Console window should be All Messages. If it isn't, select
          SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
          View ▹ Show Log List
from the menu bar at the top of the screen.
Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above.
Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first.
Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
Some private information, such as your name, may appear in the log. Anonymize before posting.

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

Unable to install SQL 2005 Service Pack 3 (Unable to install Windows Installer MSI file)

I'm unable to install SQL 2005 Service Pack 3. This results in the following error message: Unable to install Windows Installer MSI file.
Could someone please help me. Thanks in advance!
=== Verbose logging started: 3-4-2009 9:33:00 Build type: SHIP UNICODE 4.05.6001.00 Calling process: d:\5ddfa356349ddf2e676c336d95c5\hotfix.exe ===
MSI (c) (E0:88) [09:33:00:404]: Resetting cached policy values
MSI (c) (E0:88) [09:33:00:404]: Machine policy value 'Debug' is 0
MSI (c) (E0:88) [09:33:00:404]: ******* RunEngine:
           ******* Product: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
           ******* Action:
           ******* CommandLine: **********
MSI (c) (E0:88) [09:33:00:404]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (E0:88) [09:33:00:404]: Grabbed execution mutex.
MSI (c) (E0:88) [09:33:00:419]: Cloaking enabled.
MSI (c) (E0:88) [09:33:00:419]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (E0:88) [09:33:00:419]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (28:28) [09:33:01:747]: Running installation inside multi-package transaction C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
MSI (s) (28:28) [09:33:01:747]: Grabbed execution mutex.
MSI (s) (28:CC) [09:33:02:029]: Resetting cached policy values
MSI (s) (28:CC) [09:33:02:029]: Machine policy value 'Debug' is 0
MSI (s) (28:CC) [09:33:02:029]: ******* RunEngine:
           ******* Product: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
           ******* Action:
           ******* CommandLine: **********
MSI (s) (28:CC) [09:33:02:685]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (28:CC) [09:33:03:450]: File will have security applied from OpCode.
MSI (s) (28:CC) [09:33:03:841]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi' against software restriction policy
MSI (s) (28:CC) [09:33:03:841]: SOFTWARE RESTRICTION POLICY: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi has a digital signature
MSI (s) (28:CC) [09:33:04:841]: SOFTWARE RESTRICTION POLICY: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi is permitted to run at the 'unrestricted' authorization level.
MSI (s) (28:CC) [09:33:04:888]: End dialog not enabled
MSI (s) (28:CC) [09:33:04:888]: Original package ==> C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
MSI (s) (28:CC) [09:33:04:888]: Package we're running from ==> C:\WINDOWS\Installer\3d3a713.msi
MSI (s) (28:CC) [09:33:05:497]: APPCOMPAT: looking for appcompat database entry with ProductCode '{53F5C3EE-05ED-4830-994B-50B2F0D50FCE}'.
MSI (s) (28:CC) [09:33:05:497]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (28:CC) [09:33:05:685]: MSCOREE not loaded loading copy from system32
MSI (s) (28:CC) [09:33:05:825]: Note: 1: 2203 2: C:\WINDOWS\Installer\2f1994e.msi 3: -2147287038
MSI (s) (28:CC) [09:33:05:825]: Opening existing patch 'C:\WINDOWS\Installer\e6ba0.msp'.
MSI (s) (28:CC) [09:33:05:825]: Note: 1: 2203 2: C:\WINDOWS\Installer\e6ba0.msp 3: -2147287038
MSI (s) (28:CC) [09:33:05:825]: Couldn't find local patch 'C:\WINDOWS\Installer\e6ba0.msp'. Looking for it at its source.
MSI (s) (28:CC) [09:33:05:825]: Resolving Patch source.
MSI (s) (28:CC) [09:33:05:825]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (28:CC) [09:33:05:825]: User policy value 'DisableMedia' is 0
MSI (s) (28:CC) [09:33:05:825]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Looking for sourcelist for product {EE92F683-5F5C-4970-BB0B-9AC591B60268}
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Adding {EE92F683-5F5C-4970-BB0B-9AC591B60268}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Now checking product {EE92F683-5F5C-4970-BB0B-9AC591B60268}
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Media is enabled for product.
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Trying source \\NF04\d$\3db7739bf5c1bb9c50076c418420\HotFixSqlSupport\Files\.
MSI (s) (28:CC) [09:33:06:607]: Note: 1: 2203 2: \\NF04\d$\3db7739bf5c1bb9c50076c418420\HotFixSqlSupport\Files\SqlSupport.msp 3: -2147287037
MSI (s) (28:CC) [09:33:06:607]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (28:CC) [09:33:06:607]: Note: 1: 1706 2: -2147483647 3: SqlSupport.msp
MSI (s) (28:CC) [09:33:06:607]: SOURCEMGMT: Processing net source list.
MSI (s) (28:CC) [09:33:06:607]: Note: 1: 1706 2: -2147483647 3: SqlSupport.msp
MSI (s) (28:CC) [09:33:06:607]: SOURCEMGMT: Processing media source list.
MSI (s) (28:CC) [09:33:07:654]: SOURCEMGMT: Resolved source to: 'SqlSupport.msp'
MSI (s) (28:CC) [09:33:37:732]: Note: 1: 1314 2: SqlSupport.msp
MSI (s) (28:CC) [09:33:37:732]: Unable to create a temp copy of patch 'SqlSupport.msp'.
MSI (s) (28:CC) [09:33:37:732]: Searching provided command line patches for patch code {EE92F683-5F5C-4970-BB0B-9AC591B60268}
MSI (s) (28:CC) [09:33:37:763]: Note: 1: 1708
MSI (s) (28:CC) [09:33:37:763]: Product: Microsoft SQL Server Setup Support Files (English) -- Installation failed.
MSI (s) (28:CC) [09:33:37:763]: Windows Installer installed the product. Product Name: Microsoft SQL Server Setup Support Files (English). Product Version: 9.00.4035.00. Product Language: 1033. Installation success or error status: 1635.
MSI (s) (28:CC) [09:33:37:779]: MainEngineThread is returning 1635
MSI (s) (28:28) [09:33:37:888]: No System Restore sequence number for this installation.
This patch package could not be opened. Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
MSI (s) (28:28) [09:33:37:888]: User policy value 'DisableRollback' is 0
MSI (s) (28:28) [09:33:37:888]: Machine policy value 'DisableRollback' is 0
MSI (s) (28:28) [09:33:37:888]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (28:28) [09:33:37:904]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (28:28) [09:33:37:919]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (28:28) [09:33:37:919]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (28:28) [09:33:37:919]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (28:28) [09:33:37:919]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (28:28) [09:33:37:919]: Restoring environment variables
MSI (c) (E0:88) [09:33:37:935]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (E0:88) [09:33:37:935]: MainEngineThread is returning 1635
=== Verbose logging stopped: 3-4-2009 9:33:37 ===

This post should definitely help you
http://blogs.msdn.com/sqlserverfaq/archive/2009/01/30/part-1-sql-server-2005-patch-fails-to-install-with-an-error-unable-to-install-windows-installer-msp-file.aspx?CommentPosted=true
Feroz
Mark as Answer if it helps. This posting is provided "AS IS" with no warranties and confers no rights.

[SOLVED] how to install ArchLinux on a simple software raid 0

I have two 256GB disks and I want them to be in raid 0.
I tried following this tutorial: https://wiki.archlinux.org/index.php/In … AID_or_LVM
but this tutorial has the added complication of LVM and raid 1 which I don't need.
I made 3 partitions on each of the disks:
sda1 - 100MB for /boot
sda2 - 2048MB for swap
sda3 - raid 0 md0
sdb1 - unused
sdb2 - 2048 for swap
sdb3 - raid 0 md0 for /
I can assemble and format the sda1(ext4), sda2(swap), sdb2(swap) md0 (ext4) and install all the packages
I also configured mdadm.conf by Alt F2 at the installer and executing: mdadm --examine --scan > /mnt/etc/mdadm.conf
and added mdadm hook to the HOOKS list in /etc/mkinitcpio.conf (before 'filesystems')
configured the boot with grub outside of the installer as indicated in the tutorial
But when I boot I get:
md0: unknown partition table
Error: Unable to determine the file system of /dev/sda3
please help.
Last edited by 99Percent (2011-06-29 20:21:52)

fyi this is how I finally set up my simple 2 drive raid 0:
1. Create a bootable USB ArchLinux with UNetBootin
2. Boot with the USB
3. # /arch/setup
3. Select source: internet (highly recommended because i found out UNetBootin sources are not 100% reliable though not necessarily so, IOW just to be sure)
3. partition the two drives with 100mb for /boot and 100mb for swap (setup requires it - I have 8GB memory, I decided I don't need much swap space) and the rest of both sda and sdb which will make your raid 0.
4. ALT F2 to another terminal and create the the raid like this:
# modprobe raid0 (not sure if this is actually necessary)
# mdadm --create /dev/md0 --level=0 --raid-devices=2 /dev/sda2 /dev/sdb2
5. go back to the setup screen with CTRL-ALT-F1
6. go to Prepare Hard Drives>Manually configure block devices, filesystems and mountpoints. Add the /boot (ext2) for sda1 swap for sdb1 and desired filesystem for md0 (I chose reiserfs). Ignore the rest of the devices.
7. Select packages. Add the base-devel just in case, but nothing else and install packages
8. ALT F2 again to the terminal and run:
# mdamd --examine --scan > /mnt/etc/mdadm.conf
(this will configure the mdadm.conf to use your raid as created)
9. go back to the setup screen again with CTRL-ALT-F1
10. Select configure system
11. Edit /etc/rc.conf adding: raid0 to MODULES= like this:
MODULES=(raid0)
again not sure if necessary but it works for me
12. Edit /etc/mkinitcpio.conf adding dm_mod to the MODULES= like this:
MODULES="dm_mod"
13. also add to /etc/mkinitcpio.conf HOOKS= mdadm but before filesystems in my case it went like this:
HOOKS="base udev autodetect pata scsi sata mdadm filesystems"
14. I went ahead and uncommented a few mirrors in the mirrorlist file so I wouldn't have to deal with that later (and maybe it helps on the way).
15. Also set a root password. Not sure if it is even necessary but maybe some components require it.
16, Go to configure bootloader and select Grub
17. When asked "Do you have your system installed on software raid? answer Yes
18. When asked to edit the menu.lst file don't edit anything, just exit
19. When asked "Do you want to install grub to the MBR of each harddisk from your boot array? answer Yes
20. You will get "Error: Missing/Invalid root device:" and "GRUB was NOT successfully installed." Ignore those messages.
21. Exit the install
22. remove the USB stick and:
# reboot
23. the boot will fail and you will get a grub> prompt type the following commands:
grub> root (hd0,0)
grub> setup (hd0)
grub> reboot
Thats it!
Last edited by 99Percent (2011-06-28 18:51:59)

Encrypted root on software RAID with 2.6.33

Hi,
I ran an update earlier today on my HTPC, hoping for mantis included in the 2.6.33 kernel to work with my TV-Tuner card, when I recognized that the configuration for software-raids changed.
So I followed the instructions on: Installing with Software RAID or LVM and added the dm_mod module to the MODULES list and replaced raid with mdadm in the HOOKS list resulting in
HOOKS="base udev autodetect sata mdadm usbinput ecrypt filesystems"
After that I successfully rebuilt the kernel and decided it was time for a reboot, but after running the hooks udev, mdadm and encrypt, the screen shows:
Waiting 10 seconds for device /dev/mapper/root ...
root device '/dev/mapper/root' doesn't exist. Attempting to create it.
ERROR: Unable to determine major/minor number of root device '/dev/mapper/roo'.
You are being dropped to a recovery shell.
cat /proc/mdstat shows no configured raid arrays, while assembling them with mdassemble works.
I've tried to boot with and without specifying the raid arrays in grub's kernel line, always with the same result.
Even after booting from a live CD an chrooting in the system to rebuild the kernel - same error message.
Any ideas what I've done wrong?
Best regards

I just checked my mdadm.conf again and compared it with the commands listed here and on the wiki-page.
# cat /etc/mdadm.conf
ARRAY /dev/md0 level=raid1 num-devices=2 metadata=0.90 UUID=13db5ec4:4d02ad99:5be3d20e:87599807
ARRAY /dev/md1 level=raid1 num-devices=2 metadata=0.90 UUID=dda2a7de:a998f117:3f649c17:a7325bd1
ARRAY /dev/md2 level=raid1 num-devices=2 metadata=0.90 UUID=26a15bc5:2345a817:f8c460fb:3d47969b
ARRAY /dev/md3 level=raid1 num-devices=2 metadata=0.90 UUID=be48517f:ebc6eabb:f8463e19:ac167733
# mdadm -D --scan
ARRAY /dev/md0 metadata=0.90 UUID=13db5ec4:4d02ad99:5be3d20e:87599807
ARRAY /dev/md1 metadata=0.90 UUID=dda2a7de:a998f117:3f649c17:a7325bd1
ARRAY /dev/md2 metadata=0.90 UUID=26a15bc5:2345a817:f8c460fb:3d47969b
ARRAY /dev/md3 metadata=0.90 UUID=be48517f:ebc6eabb:f8463e19:ac167733
# mdadm --detail --scan
ARRAY /dev/md0 metadata=0.90 UUID=13db5ec4:4d02ad99:5be3d20e:87599807
ARRAY /dev/md1 metadata=0.90 UUID=dda2a7de:a998f117:3f649c17:a7325bd1
ARRAY /dev/md2 metadata=0.90 UUID=26a15bc5:2345a817:f8c460fb:3d47969b
ARRAY /dev/md3 metadata=0.90 UUID=be48517f:ebc6eabb:f8463e19:ac167733
I'm going to change this and rebuild the kernel image.
Don't know where the difference comes from :/
Okay - the difference comes from running the command in the arch livecd system and in the chrooted environment
But both somehow don't seem to work for me.
When running "mkinitcpio -p kernel26", this is the output:
==> Building image "default"
==> Running command: /sbin/mkinitcpio -k 2.6.33-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
find: "/sys/devices/": Datei oder Verzeichnis nicht gefunden
:: Parsing hook [sata]
:: Parsing hook [mdadm]
Custom /etc/mdadm.conf file will be used in initramfs for assembling arrays.
:: Parsing hook [usbinput]
:: Parsing hook [encrypt]
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/kernel26.img'...SUCCESS
==> SUCCESS
So /etc/mdadm.conf should be used?
lilsirecho wrote:When using mdadm for a raid0 in my machine, the assembly of the raid md0 is made during initrd. A statement for md0 and its 2 drives appears during boot-up.
I can't see any statement about creating any of my mdX devices.
It's just
Running Hook [udev]
Triggering udev uevents ... done
Running hook [mdadm]
Running hook [enrypt]
Waiting 10 seconds for device /dev/md2 ...
Waiting 10 seconds for device /dev/mapper/root ...
Root device '/dev/mapper/root' doesn't exist. Attempting to create it.
ERROR: Unable to determine majo/minor number of root device '/dev/mapper/root'.
You are being dropped to a recovery shell
Last edited by flo (2010-04-21 19:25:03)

Incomplete installation of software

after losing my cd for my product I have been trying to down my software from HP Care.com. Only part of the software gets downloaded. So I follow the instructions to uninstall and then re-install the latest full version for my product. After several attempts of doing this I haven't had any success with a complete download of the software. Therefore I am unable to scan because the solution center doesn't detect my printer it will not open for access. Some one please HELP!

@seagull104, I hope you are well!
I saw your message about the installation troubles you are facing and the error code 2753 you are prompted with. Please let me know some more info below and try out any steps you may not have attempted and get back to me with the results and we can go from there.
What printer(s) are installed on the computer?
How is the printer connected to the network (Wireless or Ethernet)?
What is the Operating System of the computer?
Have you tested hardware functionality (made copies)?
What Firewalls and Anti-virus software are installed?
Have you tried disabling or uninstalling them?
If you're running Windows, run the Print and Scan Doctor and include the results in your reply please.
Did you make any recent changes to your set up (physical move, upgrade, downgrade, new software installed, new router, etc)?
Is the printer plugged directly into the wall outlet (avoiding power bars and surge protectors)?
Have you completed all Windows/Mac OS Updates?
Have you tried using a different USB/Ethernet cable?
I hope to hear from you again
R a i n b o w 7000I work on behalf of HP
Click the “Kudos Thumbs Up" at the bottom of this post to say
“Thanks” for helping!
Click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution!

Setup was unable to use existing system partition because it does now contain the requiered free space.

I try to install it, but i select my free (fresh formated) partition with 35GB free space and i see:
Setup was unable to use existing system partition because it does now contain the required free space.
if i select partition with partition that does not contain the required i see
"Windows cannot be installed to Disk 0 Partition 1. (show details)"
so what is it? what can i test?
My Disk has 250GB, my partitions:
C: 8MB - Boot (7MB Free) - FAT
D: 37,5GB - WINXP (27,9GB Free space) - NTFS
E: 35,3GB - New (35,2GB Free) - NTFS - i want to install on it
F: 160GB - Data (6GB Free) - ntfs

kolorafa_ said:
I try to install it, but i select my free (fresh formated) partition with 35GB free space and i see:
Setup was unable to use existing system partition because it does now contain the required free space.
if i select partition with partition that does not contain the required i see
"Windows cannot be installed to Disk 0 Partition 1. (show details)"
so what is it? what can i test?
My Disk has 250GB, my partitions:
C: 8MB - Boot (7MB Free) - FAT
D: 37,5GB - WINXP (27,9GB Free space) - NTFS
E: 35,3GB - New (35,2GB Free) - NTFS - i want to install on it
F: 160GB - Data (6GB Free) - ntfs
Is this 8MB "Boot" partition (formatted as FAT???) something you created when you partitioned this disk for the Windows XP installation, or is this an 8MB OEM partition that you've somehow assigned drive letter C: to?
I wouldn't be surprised at all that your error message is being generated because thsi "BOOT" partition, labelled as drive C:, is only 8MB in size, and you can be absolutely positive that an 8MB partition is going to generate this error: "Setup was unable to use existing system partition because it does not contain the required free space."
The correct answer really depends on whether that drive C: is the boot (sic) (the proper terminology is to call it the system partition) partition for the Windows XP installation. If it is, then you're going to have some repair work to do on your Windows XP installation first, so that you can free up that 8MB partition.
In any event, I'm fairly certain that the solution is going to require the removal of that 8MB partition, as you've suggested in your most recent post.
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

Panther server, move from single drive to RAID 1

Hello,
I am trying to find out if this can be done on a system (Xserve G3) with Panther server running on it. I know this is old, but right now the school will not upgrade the server.
It has the original 60GB hard drive and is running out of space. I would like to replace it with two 500GB HD's using software RAID.
In Panther, can you clone or CCC the OS and move it to a RAID1 from a single drive, or do we need to install and configure a new installation on the RAID set?
Any help would be greatly appreciated.
Mike

There were major changes in Disk format from 10.3 Panther to 10.4 Tiger, especially in RAID drives. I believe the 10.4 Server Installer converts your Boot RAID (if applicable) but does not deal with your data-only RAID drives. In the case you are proposing, the upgrade from 10.3 to 10.4 may require you to copy your data-only RAID drives yet again.
My older SCSI RAID drives which ran fine in 10.3 were not recognized as having a valid Driver (of any description) in 10.4. The old drives could not be mounted, and therefore could not be "promoted" to 10.4 RAID Drives. Luckily, RAID tools in 10.4 Tiger are much improved.
Using only one additional full-size drive, I was able to move the array to a spare Mac, install 10.3 to get them recognized, then Network-mount and copy them onto a single-member RAID array in 10.4 Server. Creating a single member of a Mirrored Array required some fancy command-line work in 10.4 Server.
The bottom line: If you can upgrade to 10.4 Server first, it will be much less work (and much less risk).

ITunes 11.1.4 "upgrade" is broken. It ruins existing installations. Others have this problem. Please withdraw this release ASAP!

iTunes 11.1.4 "upgrade" is broken. It ruins existing installations. Others have this problem. Please withdraw this release ASAP, and please fix whatever is broken. Thank you for an otherwise excellent product.

Solving MSVCR80 issue and Windows iTunes install issues.
Thanks to user turingtest2 for this solution.
iTunes 11.1.4 for Windows- Unable to install or open - MSVCR80 issue
Solving MSVCR80 issue and Windows iTunes install issues.
If the above doesn’t do the trick entirely, then use the instructions in the following as it applies to the version of Windows you are using:
HT1925: Removing and Reinstalling iTunes for Windows XP
HT1923: Removing and reinstalling iTunes for Windows Vista, Windows 7, or Windows 8
You may be required to boot into safe mode to complete the folder deletion process.

Unable to move existing installation to software RAID-1 setup

Similar Messages

Maybe you are looking for