Tryng to format Raid 1 (Mirror) array on Promise controller

Ok, I installed the two brand-new, indentical hard drives, booted up the computer, the promise utility noticed that I had two drives plugged in with the promise controller set to RAID mode, so it ran the thing and I set the array to security (aka: Raid 1) so then it does it, and says I can reboot. Now, the manual said that the only step I have to complete now to finish it is to run FDISk or whatever to format the "drive" (Since the array is treated as one drive). I do have to do this, but hwo do I do it? I run Win 2000 Pro if that helps at all. I am trying to make it an NTFS filesystem however, so would FDISk even work? I thought FDISk only makes FAT32 file systems... Anyway, what do I do to finish setting up my RAID 1 array and get to finally use it?
Doggonit

I use Win 2000 Pro and there is no Maintenance or Performance in the Control Panel. I tried reinstalling the drivers and even uninstalling the drive as it showed up in the Device Manager under drisk drives. It simply came back the same way as before, as some 1x2 Promise RAID1 SCSI drive that was functional etc, but I dont know hot to format it and I can't see it in Windows Explorer, or in the BIOS, altough during bootup it shows the Array every time and if I check out the Promise array manager (Ctrl+F) I can see it and it is functional and all that.
Ok, this is it:
In the device manager (Control Panel->System->Hardware->Device Manager) under the disk drives menu I see my working 80Gb drive that the OS is on, and has its "Location" as: " Location 0 (0) " and then there is the:
Promise 1X2 Mirror/RAID1 SCSI Disk Drive Device
In the properties of this it says: Bus Number 0, Target ID 0, LUN 0
Also, for the Write cache, the box is unchecked, as in not enabled, and it is grayed over, so I can't even change it. I guess this is beacuse the drive is not yet formatted and cannot be written to yet, right?
Is there a conflict between the 80GB drive and the RAID1 Array on the BIOS level that I should fix somehow? Is the Location of the 80GB one be 1 or do those numbers for the array have to be 1 ?
I think I really wont be able to get this to work without some major help. Now I see why IDE drives still rule. They are more accesible from the BIOS.
Doggonit

Similar Messages

Raid 0 SATA on Promise Controller, Sata drive on Intel?

Hi all, wondering if I can run this setup:
(Specs in my Sig)
2 SATA WD Raptors, RAID 0 on the Promise controller
1 Maxtor 80Gig SATA on the Intel Controller
Is this an option or not?
I am setup on the Raptor's already and would like to install another HD on the Intel if it can be done like mentioned.
Thx for the help!
/D

Ok, I connected to the Intel SATA 1 plug and all is fine. WinXP found the drive, installed it and away I go.
Only other question I have..Is there a specific driver I should use for it now?
It shows up in the Device Manager as Follows in 2 places:
Disk Drives
Maxtor 6Y080M0
and
IDE ATA/ATAPI Controllers
Intel(R) 82801EB Ultra ATA Storeage Controllers
Intel(R) 82801EB Ultra ATA Storeage Controllers
Primary IDE Channel
Primary IDE Channel
Secondary IDE Channel
Secondary IDE Channel
I'm not sure if it should show under SCSI and RAID Controllers.
Blazer: That link is dead. I would like to read the article if ya can find it again. Thx
Dirtnapper: I read another post here somewhere about what you are looking to do. It can't be too far back in the pages, possible in a link in the RAID guide at the top.
/D

RAID Mirror using partitions

Hi all,
I've got 3 Samsung Spinpoint F1 1TB drives in my MacPro. One is dedicated entirely to Time Machine backup. The other two I would like to split into two equal partitions and then setup RAID (mirror) arrays using Disk Utility like this:
RAID 1 = Disk1,Partition1 + Disk2,Parition1
RAID 2 = Disk1,Partiton2 + Disk2,Partition2
The first RAID gets created without a hitch... but then the second RAID fails and won't create/mount.
Is this even possible on OS X 10.5.8? If so... I'd really appreciate any help, as it seems like this SHOULD work, but it just WON'T.
Thanks!
- John

Kappy,
Thanks for the additional info. I've got scads of backup going on... I regularly (like, hourly) use Chronosync to synchronize all of my important files between my Mac Pro and my MacBook Pro so there's one... I also user SuperDuper to maintain bootable backups on separate external drives for both computers... AND I've got two separate external backups of my important client files (backed up into a secure sparse disk image on two different external drives).
So... I came up with the scheme of having the RAID on the boot disk while I was trying to re-allocate some new drives from my MacPro and external drive enclosures. I realized that the original, 320GB drive that came in the MacPro was a dog and was significantly hampering performance (the MacBook Pro is actually faster at performing disk-related tasks!). So... I had a Samsung SpinPoint F1 1TB drive that I was planning to put into an OWC FW800/400/USB2.0/eSATA drive enclosure to use as part of my external backup scheme that I thought would serve me better as my boot disk. But, since I've only got about 200GB of the 320GB filled on the current drive, I figured I had a lot of space on the 1TB drive that would go to waste.
Hence... I hatched the "brilliant scheme" of partitioning 2 of the 1TB drives in the MacPro equally and then creating a RAID... figuring that would provide at least some reason for having the overly-large drive for my boot disk. RAID mirroring would give me a level of protection against disk failure and would reduce the "clutter" of having too many drives/partitions showing up on the desktop and in Finder.
But... all of your comments are excellent ones. So, I'm sticking with the interim solution I posted earlier. No RAID on the boot disk partition, but a RAID on the important client files partition to provide drive-failure protection above-and-beyond my existing backup schemes.
Thanks, again, for all of your input.
Regards,
- John

Problems getting my Promise RAID 0 array to boot

I just picked up two new WD 320gb SATA drives to run in RAID 0 on my K7N2-ILSR. I used the auto setup in the Promise utility and everything ran peachy-keen. Loaded up my XP install CD, jammed on F6, selected the Promise 376 XP drivers I got off of the MSI drivers site, formatted the drive NTFS, windows installed, rebooted.
I got the dreaded "Disk read error. Press CTRL-ALT-DELETE". The bios boot order is CDROM, SCSI, and SCSI again just to be sure. I've tried dozens of combinations and nothing works; always the same error. Now, when I load up my XP cd again, and go to the Recover Console, it actually has Windows there. I even ran the MBR recovery tool from the recovery console with no luck. The WD Data Lifeguard cd shows one 640gig drive formatted in NTFS.
Do I need to update my bios? The version I'm running (according to the boot screen) is 08/02/2004-nVidia-nForce-6A61BM4CC-00. I mean, it seems to me like a bios problem and not a windoze install problem (especially if all my diag tools say the raid array is fine and perfectly bootable).
Thanks, I appreciate any help you might offer! (and, yes, I searched all over the net, including this forum, for answers with no luck :( )
~V~

Quote from: Richard on 17-March-06, 22:33:30
variableresults,
Use these Drivers when you hit F6:
Promise Serial-ATA RAID Drivers
Take Care,
Richard
Thanks for the reply;
I'm pretty sure those are the same drivers I was using (I recognize the setup file). Like I said, the Promise driver seems to be working fine since windows recognizes and copies all the files to the raid array. In fact, I'm in windows now on my old drive, and it sees a 600gig D drive that I can copy to, format, etc etc. It seems to me like the BIOS isn't finding my Promise controller when I select SCSI as the boot option.

Need help with formatting a software RAID 5 array with xfs

Hi,
i'm tying to format a software RAID 5 array, using the xfs filesystem with the following command:
# mkfs.xfs -v -m 0.5 -b 4096 -E stride=64,stripe-width=128 /dev/md0
but all I get is the attached error message. It works fine when I use the ext4 filesystem. Any ideas?
Thanks!
http://i.imgur.com/cooLBwH.png
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --

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?

Advice needed installing XP Pro onto RAID Mirror with XP Home on IDE already

Hi Y'all,
I have the rig described below.
Currently, I'm running Win XP Home SP2 booting on the 80gig IDE drive, with another partition on it holding my files.
I want to clean install XP Professional SP2 (slipstreamed) onto the 120gig SATA Mirror RAID array and use that as the boot drive. This is empty but has been formatted and partitioned so the system recognises it as a drive.
Once that's done I want to wipe off XP Home and use the IDE drive as a pagefile and backup drive.
I had thought of doing it this way:
1. Prepare floppy with SATA RAID drivers v1.0.0.19 (Files: fasttx2k; txtsetup.oem; Fasttx2k.cat; fasttx2k.INF; fasttx2k.sys; README.TXT)
2. Erase all partitions on the RAID mirror but leave both physical drives installed
3. Remove the IDE drive
4. Boot from Win XP Pro SP2 CD ROM and install the SATA drivers at the F6 prompt
5. Continue WinXP install as normal onto the RAID drive
6. Reconnect the IDE drive after OS has installed
7. Select Win XP Pro as the OS to boot
8. After bootup erase Win XP Home partition
9. Partition the RAID drive to have 2 partitions, one (C:) for the OS, the other (D:) for my files
10. Use Files & Settings Transfer Wizard to repopulate the OS with my stuff (previously exported to a safe place).
11. Get on with life...
Can anyone please advise if they forsee any problems doing it this way.
Just to show that I am really confused, advice I've read in the Windows XP Forum says I should break the mirror before doing trying to install any OS to a RAID array and use just one of the physical 120gig SATA drives to install XP Pro onto. Once this has been done I should rebuild the mirror and the drives will automatically become mirrored once the data has been duplicated to the 2nd SATA.
Is this the only way to do this? Is this the best way to do this (does WinXP install badly to a mirror RAID that has already been created)?
Advice I've already read on the forum here has only confused me further because:
a) it assumes a level of knowledge that I don't seem to have
b) it doesn't deal with my exact circumstances.
All help gratefully received.

An update on the situation.....
I am trying to install Win XP Pro SP2 (slipstreamed) onto a RAID Mirror of 2 Hitachi Deskstar SATA drives on my MSI K7N2G-ILSR. This is the exact procedure I've followed:
1. Formatted (both SATA drives) as drive I: using Windows Disk Management tool in WinXP (The mirror is seen by the BIOS & Fastrak BIOS)
2. Started Win XP Pro install via CD in d:\
3. Pressed F6 when requested
4. Windows Setup loads normally
5. Options to install 3rd party drivers for mass storage devices & other things appear
6. Press S to start installing RAID drivers
7. Insert floppy into A:\ & press Enter
8. Select Promise Fastrak 376 Win XP driver
9. Get following error message:
File \WINXP\fasttx2k.sys caused an unexpected error (18) at line 2113 in d:\xpsprtm\base\boot\oemdisk.c.
10. Press Enter to continue
11. Setup doesn't recognise the SATA drive I: so it doesn't appear in the list of partitions on which to install XP Pro
I've tried it every which way.
The following with IDE1 HDD disconnected, i.e. no operating system installed:
1 SATA drive only (mirror broken)
1 SATA drive striped array
Both SATA drives (mirror functional)
The same with IDE1 HDD connected and starting Windows Setup from within XP Home...
The only difference is if I use the original Win XP Pro disc (without SP2 slipstreamed) when the error message changes to:
File \WINXP\fasttx2k.sys caused an unexpected error (18) at line 2108 in d:\xpsp1\base\boot\oemdisk.c.
In a thread here there is mention of an error in a file but it isn't directly related to my mobo, so I am reluctant to fiddle with the file unless someone can explain clearly what needs changing. I'm just trying to find the thread at the moment.....
This is the text contained within txtsetup.oem:
[Disks]
d1 = "Promise FastTrak 376 Driver Diskette", \fasttx2k, \
d2 = "Promise FastTrak 376 Driver Diskette", \fasttx2k, \nt4
d3 = "Promise FastTrak 376 Driver Diskette", \fasttx2k, \Win2000
d4 = "Promise FastTrak 376 Driver Diskette", \fasttx2k, \WinXP
[Defaults]
scsi = FastTrak_TX2K_xp
[scsi]
FastTrak_TX2K_xp = "WinXP Promise FastTrak 376 (tm) Controller", fasttx2k
FastTrak_TX2K_nt5 = "Win2000 Promise FastTrak 376 (tm) Controller", fasttx2k
FastTrak_TX2K_nt4 = "WinNT Promise FastTrak 376 (tm) Controller", fasttx2k
[Files.scsi.FastTrak_TX2K_xp]
driver = d4, fasttx2k.sys, fasttx2k
inf = d4, fasttx2k.inf
catalog= d4, fasttx2k.cat
[HardwareIds.scsi.FastTrak_TX2K_xp]
id="PCI\VEN_105A&DEV_3376", "fasttx2k"
[Files.scsi.FastTrak_TX2K_nt5]
driver = d3, fasttx2k.sys, fasttx2k
inf = d3, fasttx2k.inf
catalog= d3, fasttx2k.cat
[HardwareIds.scsi.FastTrak_TX2K_nt5]
id="PCI\VEN_105A&DEV_3376", "fasttx2k"
[Files.scsi.FastTrak_TX2K_nt4]
driver = d2, fasttx2k.sys, fasttx2k
inf = d2, fasttx2k.inf
[Config.fasttx2k]
value = "", Tag, REG_DWORD, 1
I've also tried the following:
Change Boot sequence to CD-ROM> SCSI> HDD-0
Delete txtsetup.oem from floppy - Setup then says it's missing
Copied original drivers from nVidia driver & utility disk
None of these things has made the slightest difference
Need further help please!

Can I set up a RAID 1 Array by adding a drive to an existing install?

Hi All:
I have a K8N Neo2 with a 160GB Seagate SATA drive on it, and just bought an identical drive that I want to use for a RAID 1 array. My question is this: Do I need to do a complete reformat with the OS in order to setup RAID 1? With my old system and Ultra ATA drives, you could always add a drive, but I don't see any way to load the nVidia RAID driver after Windows has already been loaded.
Is this possible, and if so, what are the steps? I've enabled RAID for both SATA drives and can get into the RAID Bios, but beyond that, I'm lost. Also, I must have inadvertently setup an array, because it shows that I have one. I can boot into Windows if I turn off RAID in the BIOS, but would love to be able to install without a clean format.
Any help would be greatly appreciated!
Thanks,
Michael Tschirret

Michael,
You can create a RAID 1 Array, just make sure that the Drive with the Data is the Master and not the Mirror. You can have the RAID Controller build the image (Sync the Drives), and then you should be mirrored before you even boot back into Windows. The OS will not know the difference.
Take Care,
Richard

RAID mirror with software utility caused kernel panic every time

Using disc utility to make a mirror of 2 drives, click create and i get kernel panic and have to power off machine. if i try to start the machine with either of the two disks in it (together or individually) i get same kernel panic and have to power off.
The disks are in an external storage array (sonnet d500). I have a second storage array with raided disks in and i have raided disk inside the mac too. these all work fine..
originally 2 weeks ago i had the 2 disks working in a group of 4 disks set as a mirror of 2 striped disks. One disk in this setup failed and with this config you can never 'recover'or rebuild it - you get a degraded mirror and you can backup the data, but you must completely rebuild the raid again as the mirror of stripes never lets you add a new disk in again.period. not good.
I replaced the failed disk and rebuilt the mirror of stripes. this lasted a day until a second disk failed (all 4 were bought at same time so i was kind of expecting that to happen once one failed).
i replaced the second faulty hdd and thought about my disk usage and decided i would not make another mirror of stripes and i would make 2 mirrors instead for safe-ish storage and then transfer data to a striped raid set for editing from instead of direct from the mirror of stripes volume.
i tried to delete the raid but got a kernel panic
if i started the machine with any of the 4 disks i would get a kernel panic.
i moved the disks one by one into an older G5 running Tiger and managed to erase the raid info on 2 of them. The two new ones had some strange raid info and the Tiger machien thought there was an extra disk in the machine and would not erase or partition or allow me to destroy the raid whatever i tried.
I will be moving these now into an old XP PC to try to erase the boot records etc and erase them to be able to use them again in either mac pro or G5. painful..
so.. i ended up with 2 erased drives and have 2 new drives with dodgy raid info that causes kernel panics on the leopard machine and wont go in the Tiger machine.
The two erased drives are what ive now been trying to use in the mac pro to create a mirror - this now caused kernel panics when creating the mirror to start with and when installed in the machine at all. so i will be erasing them again in the tiger machine soon (its busy erasing with zeros another new disk that i added to the Tiger machine 2 weeks ago which seems to have some fault when raided!!! but thats another story).
so.. is anyone else having problems with creating basic mirror in 10.5.4 or is it just me??
i have a sonnet tempo e4p card with 2 external sata disk enclosures, latest firmware for the e4p card. all other previously existing raid volumes are working fine. i have one set of 2 striped disks, one set of 3 striped disks and one set of 2 stripes which are mirrored - all happy and working fine. but i cant make a new mirror of 2 disks...
I phoned Apple support and they said all raid info was kept on the disk itself and nothing on the actual machine and suggested i take the machine to an apple care centre for some tlc (although its disk i am having a problem with). since all my other disk arrays work fine i don't really want to rebuild the whole machine from scratch if i can avoid it.
Any suggestions of what i can try ??

well it turns out the new disk i bought just werent any good. my g5 powermac raid mirror issue was related to one new disk with lots of bad blocks (speed tools showed that up) so i have learnt my lesson on cheap non raid disks for raid..
am waiting on a couple of new ultrastar enterprise disks to tuen up so i can go back to the macpro and try to add a mirror again.
i am still stuck wih several new disks that i cannot format now in the macpro on leopard or on the g5 powermac with tiger.
ive tried softraid and that cant do it, speedtools pcformat util cant do it, disk utility crashes when i try to eras them and diskutil from termianl starts then doenst get anywhere and my pc sata card doesnt work so my last resort pc option still doesnt help me clear the partition map on these drives - ones that diskutility on leopard made for me - and drives which still cause kernel panics on the macpro if i put them in it..
here is what diskutil says on my g5:
/dev/disk0
#: type name size identifier
0: GUIDpartitionscheme *465.8 GB disk0
1: EFI 200.0 MB disk0s1
2: Apple_RAID 465.4 GB disk0s2
3: Apple_Boot 128.0 MB disk0s3
/dev/disk1
#: type name size identifier
0: Applepartitionscheme *233.8 GB disk1
1: Applepartitionmap 31.5 KB disk1s1
2: Apple_HFS Macintosh HD 233.6 GB disk1s3
/dev/disk2
#: type name size identifier
0: *465.4 GB disk2
/dev/disk3
#: type name size identifier
0: Applepartitionscheme *931.5 GB disk3
1: Applepartitionmap 31.5 KB disk3s1
2: Apple_HFS backup1T 931.4 GB disk3s3
/dev/disk4
#: type name size identifier
0: Applepartitionscheme *931.5 GB disk4
1: Applepartitionmap 31.5 KB disk4s1
2: Apple_HFS tempi 931.4 GB disk4s3
disk0 is the one with the bad partition info.
it thinks it has a double raid as the console shows on startup:
(both store45 and cache it thinks are on this disk - cache was my old mirror of stripes set on other machine, store45 was new name for my mirror, so seems like it hadnt deleted the original raid partition info before making new info which now kernel panics)
Jul 18 18:48:05 localhost kernel[0]: AppleRAID::degradeSet - starting the set "STORE45" (B9C48619-6B2C-4547-A01E-4864754EA7E2).
Jul 18 18:48:35 localhost kernel[0]: AppleRAID::degradeSet - starting the set "CACHE" (64F914A5-5556-4A44-AEE2-DC437868766B).
Jul 18 18:48:35 localhost kernel[0]: AppleRAID::completeRAIDRequest - error 0xe00002c2 detected for set "STORE45" (C0E139A4-2A6D-49C6-8F77-202AF7F9285D), member 50207BE5-E487-410E-8E8E-C4C4DCD2687B, set byte offset = 999527018496.
Jul 18 18:48:35 localhost kernel[0]: AppleRAID::completeRAIDRequest - error 0xe00002c2 detected for set "CACHE" (64F914A5-5556-4A44-AEE2-DC437868766B), member C0E139A4-2A6D-49C6-8F77-202AF7F9285D, set byte offset = 999527018496.
so currently i have 2 new 500gb disks which cant be partitioned back to anything at all on either machine. looks like i will have to buy a new pc to reformat them..
any suggestions of how to clear the partition map info and get them back to freespace ??

RAID 0+1 using Promise 378 Controller

I'm having trouble installing two SATA drives in my system and the problem is driving me nuts
I have two existing PATA drives on the Promise controller configured as a RAID0 array, which is working fine with XP SP2. I want to add the two SATA drives (Seagate Barracuda 200Gb SATAs) to the array and configure it to sripe across like drives and mirror across the dissimilar drives. So the two PATA drives are striped and that striped array is mirrored across to the striped pair of SATA drives.
The manuals all state that it's possible to configure the promise controller for 0+1 (which is what I think I need, but when I power up the PC with the SATA drives connected to SER3 & 4, the promise controller doesn't recognise them when configured in bios "as raid". It sees the drives when the controller is configured "as sata", but then the raid bios is bypassed at POST and obviously the boot doesn't happen.
So my question is, am I missing something with the Promise Controller setup, or does the bios version I have not support Raid 0+1. I guess I need an option that says "as sata with raid", which isn't there. Which BIOS version do I need to do this? or is it something else?
Am I being dumb or do I have to delete everything and start again using the intel ICH5R controller?
The two recordable drives are connected as primaries on the two non-raid IDE controllers.
I'm new here, so any help anyone can lend a hand would be greatly appreciated
Cheers
Tony

Hi Danny,
Yes, I did read it, but it did not address my particular situation - i.e. all four drives connected to the promise controller. The bits that do seemed to be saying "look at the manual", which isn't helping me. Last night, I updated the mainboard bios to 2.4, which didn't make any difference, so I'm still stuck.
Thanks for taking the time to reply
Tony

Xserve SSD OS drive Raid 5 array - What if SSD OS drive is corrupt or fails

Xserve SSD OS Drive option with Raid 5 array - What if SSD OS drive fails or the OS becomes corrupted? Could you just re install the os and then upload all of your server settings and it would be able to talk to the raid array and be good to go?
Additionally if the os is in the raid 5 and becomes corrupted and you are not able to get the os to boot would the raid 5 data not be able to be accessed? Or could you just reinstall the os on the array and be ok?
This would be the same if the os is inside a software mirror set?
Thanks in advance!!!

Hi
If you're asking can OSX Server be reinstalled without a reformat the answer would be no. This assumes you're using the OSX Server Installer DVD. Assuming no other hardware issues you should be able to access any/all data on any of the Drives using Target Disk Mode and another mac. This will at least allow a transfer of important data to another source. Having said that you should be keeping back-ups anyway.
You can export Server Admin's configuration as a series of property lists. You can export Users, Groups and Computer Lists from WorkGroup Manager. You can archive the whole of the LDAP database - which will contain everything except home folder information - using Server Admin.
I'm not sure if this is still the case but one of Apple's Best Practice tips was to setup and configure the Server exactly as you wanted it first. Once you're happy use any one of probably half a dozen methods to make a Bootable cloned backup. A free built-in method would be to boot from an appropriate Installer Disk and save the Server OS as a .dmg to a connected USB or Firewire disk. Or use something like CarbonCopyCloner to do regular scheduled clones to an externally attached drive.
My 2p.
Tony

Dirve dropped out of RAID 5 Array?

I had a drive "Fail" and drop out of our raid 5 array... After reboot the drive came back up, but its "Roaming". How do I re-integrate it back into the RAID 5? Right now I have no redundancy with only 2 disks in the array.
The migrate RAID Set feature of RAID Utility seems to want to crate a RAID 0 only?
I have provided links to some screen caps.
http://i143.photobucket.com/albums/r133/bliesveld/Server/fig1-1.jpg
http://i143.photobucket.com/albums/r133/bliesveld/Server/fig2.jpg
http://i143.photobucket.com/albums/r133/bliesveld/Server/fig3-1.jpg
Any help would be appreciated.
Thanks
Updated Images: Message was edited by: bTesla

Yes, there are issues with having your operating system on a storage array. Were there a drive failure you would lose everything on the array including the ability to boot the system. Keep the OS where it is, and use the array for its intended purpose - storage.
You should also consider another array that you can use as backup for the existing one. Perhaps a mirrored array so your backup has a backup.

[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?

Recover RAID 5 array with new root drive

Ok, I have a root mirror and a 4 drive RAID 5 array on an E250. The linker got hosed on the root partition and mount fails as a result. I've tried repairing the linker to no avail. So I replaced c0t0d0 with a brand new drive and put a fresh install on it. The second half of the mirror is still there and can be mounted now. The question is how to I restore the RAID 5 array to get to that data without losing data on the RAID 5 array ?
lidavidson

Ok, here's what I got:
From the new, fresh, root partition c0t0d0s0 the first 6 lines are the old root mirror that I copied over:
bash-2.05# more md.tab
# metadevice configuration file
# do not hand edit
d2 -m d0 d3 1
d0 1 1 c0t0d0s0
d3 1 1 c0t8d0s0
d5 -m d4 d1 1
d4 1 1 c0t0d0s1
d1 1 1 c0t8d0s1
d6 -r c0t9d0s1 c0t10d0s1 c0t11d0s1 c0t12d0s1 -k -i 32b
bash-2.05# metainit d6 -r c0t9d0s1 c0t10d0s1 c0t11d0s1 c0t12d0s1 -k -i 32b
metainit: tempest: there are no existing databases
bash-2.05# pwd
/etc/lvm
bash-2.05# cd ..
bash-2.05# more system
* Begin MDD root info (do not edit)
forceload: misc/md_trans
forceload: misc/md_raid
forceload: misc/md_hotspares
forceload: misc/md_sp
forceload: misc/md_stripe
forceload: misc/md_mirror
forceload: drv/pcipsy
forceload: drv/glm
forceload: drv/sd
*rootdev:/pseudo/md@0:0,2,blk
* End MDD root info (do not edit)
* Begin MDD database info (do not edit)
set md:mddb_bootlist1="sd:3:16 sd:59:16 sd:64:16 sd:72:16 sd:80:16 sd:88:16"
* End MDD database info (do not edit)
I also rebooted after copying the entries in /etc/system.

Lost RAID 5 Array...

I have, er... had, a RAID 5 array comprised of six 180GB Apple Drive modules. The Xserve RAID had cache battery backups installed and was on a UPS, but I had disabled the drive cache for all drives quite some time ago as I wasn't sure how reliable the cache battery backups were anymore. This wasn't performance intensive, it was mainly a second repository for backups.
Unfortunately, I came in to work Friday morning to find the RAID powered down (in standby mode). I powered it back up (it was still shown as being mounted on the file server which is running Mac OS X Server 10.3.9, but the volume was empty and listed the correct amount free). Of course, that didn't bring up and data, so I rebooted both the Xserve and the Xserve RAID.
Disk Utility showed no array and neither did RAID Admin.
No luck. I've swapped controllers, upgraded the controllers to the latest firmware. Nothing.
I've searched through this discussion forum's history and tried everything I ran across (power up order of the Xserve and Xserve RAID, powering down the RAID, pulling the cache battery backups, and waiting five minutes, the "Recognize Array" feature in RAID Admin, DiskWarrior, etc). Nada.
Any additional suggestions? Most of the "lost array" discussions are from last year, so I'm surprised this happened to me (maybe because the Xserve RAID was still running old firmware). Also, what is the "Recognize Array" feature really for if it won't allow you to select drives to try to recognize?
I still have not tracked down how the RAID was powered down (it's in a private server room and I'm the only admin that manages the servers in there).
Thanks for any help or insight anyone can provide.
Dual 1.33Ghz Xserve G4 w/Xserve RAID Mac OS X (10.3.9)

Shane: Yes. I tried Disk Warrior, but as there's no RAID Set, there's no volume even available to try to repair.
Dave: Unfortunately, I came to the same conclusion that you have. Very odd that this issue seems so prevalent on the pre-1.5 firmware.
I've kissed my data goodbye (it was all backups, so not vital, but I would have liked to keep it), recreated the set and we'll see how it goes with the new firmware. I'm also setting up a second RAID to mirror the data to for more redundancy in the future.
Andrew: I'm sorry to hear you're having the same issue, but glad you've got a backup. This issue definitely is a big time waster in the least.
Unfortunately, it appears (from my experience, unless I too was missing some undocumented modifier key combo) that you have to have atleast one drive that still remembers what set it belongs to in order to use the "Recognize Array" feature.
From past discussions, I've gained that Apple can actually recover/rebuild the RAID set from drives sent to them, but in my case it wasn't worth spending any additional amount of money on getting the RAID set back up (my time was costly enough).

Kernel Panic when using a new RAID 5 array

I recently set up a new Sans Digital 5 disk 7.2TB hardware RAID 5 array that's connected to a Sonnet Tempo-X eSATA 4+4 PCI-X card which has been updated to the latest drivers. The same card supports a number of JBOD enclosures that run as mirrored RAIDs under SoftRAID 4.0. My system is a 2.7Ghz DP Tower.
Upon trying to copy to the new RAID 5 volume I encountered a kernel panic and system freeze complete with wailing fans. After a few system restarts and a call to Sans Digital I tried to connect the RAID via USB upon the recommendation of tech support. Rather than causing a crash while copying I received an error message in the copy progress window that said that some files were locked and the process could not be completed and the RAID was no longer mounted in the finder.
I called Sans Digital back and they said it was probably a defective enclosure. I have just received a new one and have put that into service. All seemed fine until, when I was 30GB into a 900GB copy, the system froze. I have also tried to copy fewer files (400GB) and still get a Panic. When the RAID is idle there does not seem to be a problem. The last time the problem occurred the copy progress bar hung but the system did not fully lock up. The LEDs on the front panel of the RAID enclosure were flickering rapidly but no data was copying from my other drive. I turned off the RAID and was able to use my mouse again and restart my machine with a normal restart.
My system is running OS 10.5.8. When the RAID is off my computer runs fine.
Not sure what to try next. Any help would be appreciated - Thank you.

Hi-
I'd be interested to know if Sonnet has any comments regarding the issue.
In Utilities/Console/Logs, there should be some indication of what is occurring when the crashes occur.

Tryng to format Raid 1 (Mirror) array on Promise controller

Similar Messages

Maybe you are looking for