6380 mb raid failing

i have the 6380 motherboard w/raid controller. The raid controller stopped working last night. First it would not detect any hard drives connected to it. I tried moving cables around and i tried hooking up a 3rd hard drive instead of the 2 that are nornally connected and it still failed to detect it.
now, the raid controller doesnt even show up. The screen where the raid controller normally goes through the detection never shows up. I've tried flashing the bios twice already, including clearing the CMOS.
Also, my network card does not work as well. Either hardware manager says the network card failed to start, or it starts but is unable to communicate with the router. Only once did it actually work, but only for 2 minutes and then it failed.
Anyone have any suggestions?
Ian

I had a similar problem and this helped. In my case, my MB kept dropping my network and connecting with the neighbors! You may also need to change the channel you router is transmitting on, go to About This Mac/More Info... and click on Airport under Network and check to see if your router is transmitting on the same channel.

Similar Messages

No event logs when RAID fails in Server 2008 and R2

From what I'm finding out (by web searching) they forgot to include event logging in Server 2008 for when a Windows software RAID fails in some way such as missing disk, failed redundancy, etc. This is REALLY annoying as I was trying to setup email notifications
for when this happens so I can fix it. I'm just using this on my servers at home, so I'm not big on the idea of spending a lot of money on a hardware RAID, it just does some simple network file sharing and streaming and software RAID is fine. Is there anyway
to get this to work properly, like it used to?! Hotfix? Sacrifice a small animal? Free third-party tools that would work if nothing else? Would a MOM server be able to notify me? (been considering setting up one of those and SCCM to mess with)

Thanks guys for chiming in. The only way Microsoft will know this is a big deal (you would think they would, but apparently not), is for people to complain. I found this out myself when I was trying to set up event triggered tasks to email on low disk space
and RAID failure, only to find no events are created on RAID failures!
I have setup a SCOM 2007 R2 server in my testing environment. It registers and alerts me for low disk space just fine, but the availability monitor is not tripped when I break a RAID volume. I have tried offlining a disk, which results in failed redundancy,
and also shutting down the VM and removing a drive, and neither seems to trip an alert. Do I have to do something to get it to monitor correctly?

RAID failed - Can't find status in disk utility

I have an Xserve G5 with 3 hitachi 80GB SATA hard drives with a RAID 5 (I think) running 10.4.6. A couple of days ago, the server was running really slow and the afp was taking up alot of cpu time, so we rebooted the server as we haven't had a problem with afp before. However, the server would no longer boot up and the RAID alarm started going off. Now when booting the server I get the apple screen and after a couple of minutes, the server's fan would start going faster and faster until they would be going full blast. So I tried to check the status using disk utility of the RAID, but I can't see any status. I admit that I have only been working with the xserve for almost a year and I don't know alot, but all I see on the left of the disk utility is xserve megaraid and below that Server HD. I checked both of these and clicked on all of the tabs (first aid, RAID, partition, restore, etc), but I can't find a place to check the status of the RAID. All I can find about RAID is how to create another one. I finally found that I can run megaraid -showstatus and it said that the first hard drive failed and the other 2 were online. I also took out the hard drive and ran hitachi's test drive software using the advanced test and it said everything was fine. So I'm not sure if there is just something wrong with the RAID or what.
I did order another hard drive that is exactly the same and it should be here in a couple of days. I also know that this is the hard drive that was accidentally ejected while the server was running before, but when the hard drive was put back in, the RAID rebuilt it and has been running fine till now. I am pretty sure that I shut the server off before when the hard drive got ejected and it would boot, so I'm just not sure exactly what this all means as the Hitachi software tells me there is nothing wrong with the drive.
Help please

I checked the status of the server and hard drive by booting off of the 10.4 installation disk, select utilities and disk utility.
I know very little about terminal, however I'm pretty good at dos so I can figure some things out if given some commands.
Anyway, I ran some commands and here are the results:
megaraid -showstatus
MEGARAID CLI version 1.0.12
No cmd argument
Um, so I think I remebered the command incorrectly and I did -showdevices instead. Sorry.
megaraid -showdevices
Physical devices Available = 3
Drive ID Identification Size(MB) Status
0 Hitachi HDS722580VLSA80 78529 Failed
1 Hitachi HDS722580VLSA80 78529 Online
2 Hitachi HDS722580VLSA80 78529 Online
diskutil list
/dev/disk0
#: type name size identifier
0: Applepartitionscheme *153.3GB disk0
1: Applepartitionmap 31.5KB disk0s1
2: AppleHFSServer HD 153.2GB disk0s3
/dev/disk1
#: type name size identifier
0: Applepartitionscheme *2.6GB disk1
1: Applepartitionmap 31.5KB disk1s1
2: AppleDriveATAPI 4.0KB disk1s2
/dev/disk2
#: type name size identifier
0: untitled *467.0KB disk2
/dev/disk3
#: type name size identifier
0: untitled *95.0KB disk3
/dev/disk4
#: type name size identifier
0: untitled *95.0KB disk4
/dev/disk5
#: type name size identifier
0: untitled *95.0KB disk5
/dev/disk6
#: type name size identifier
0: untitled *219.0KB disk6
megaraid -showconfig
Logical Drive RAID Level Stripe Size(KB) Size(MB) Status
0 5 64 156958 Degraded
megaraid -showapater
FW Version = A130
Bios Version = G117
Product Name = MegaRAID SATA 150-4D
Cache Size = 64MB
diskutil checkRAID
No RAID sets found
Thank you for your help. I really appreciate it and so do the teachers and the students!

Software RAID failing constantly

Dear all,
I need help as I cannot work out what is going wrong the the Mirrored RAID i set up.
I bought 2 x 1TB drives and setup Mirrored RAID (software) through the GUI Disk Utility Application. I assumed it would all "just work".
After about a month the RAID failied. It happened after I ran TechTool Pro 5. Could this have caused permanent damage which leads me to where I am today (see below)? I unplugged the drives and plugged into my laptop (I don't know why I didn't just unplug and plug them into the Mac Mini they were in). Anyway it came up saying "Rebuilding" and it took about 9 hours. All was good again.
Until early October 2009 when Disk Utility reported that the RAID was "degraded" and one of the drives had "failed".
I was pretty shocked as it was a new drive. I thought the best thing to do would be to get a new 1TB drive to rebuild the RAID and then deal with the failed drive.
It took over 2 weeks to get the new drive and enclosure (long story). I setup the new drive last night, plugged it in and the "Rebuilding" message came up with the same "it will take 9 hours message".
I left it over night and when I got up Disk Utility told me that the older drive of the two has "failed". There has to be something weird going on here and this is where I need your help.
Configuration
1. The drives are 1TB Hitachi 3200rpm SATA I/II, 32 MB Cache drives
2. The 'old' enclosure is an Icecube G2 SuperS 800/400/USB2/eSata 3.5" Enclosure
3. The 'new' enclosure is an OWC Mercury Elite-AL, Quad Interface eSata/FW 400/FW 800/USB 2/USB 1
4. The Mac Mini only has one FW800 port and I connect the 2 drives up in serial.
<hr />
Here is the behaviour I'm seeing now.
I'll start with both drives off and turn both on.
1. Both drives mount in Disk Util
2. 20 seconds later a message comes up about rebuilding slices for "disk1 ... ?" and "disk (null)" and disk util crashed 2 seconds later (thus why didn't catch all of the message)
3. I turn to the terminal:
bsmith@kanga ~ $ diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *298.1 Gi disk0
1: EFI 200.0 Mi disk0s1
2: Apple_HFS Mini 297.8 Gi disk0s2
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *931.5 Gi disk1
1: EFI 200.0 Mi disk1s1
2: Apple_RAID 931.2 Gi disk1s2
3: Apple_Boot Boot OSX 128.0 Mi disk1s3
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *931.5 Gi disk2
1: EFI 200.0 Mi disk2s1
2: Apple_RAID 931.2 Gi disk2s2
3: Apple_Boot Boot OSX 128.0 Mi disk2s3
/dev/disk3
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS terra *931.2 Gi disk3
bsmith@kanga ~ $
bsmith@kanga ~ $ sudo diskutil listRAID
Password:
RAID SETS
===============================================================================
Name: terra
Unique ID: 2AC46C49-5F0B-4BD5-B1FE-C322A6F51DD9
Type: Mirror
Status: Degraded
Size: 999860895744 B
Rebuild: automatic
Device Node: disk3
Apple RAID Version: 2
# Device Node UUID Status
0 disk1s2 A12D748F-0779-4217-8C75-B31D9AE45B4E 0% (Rebuilding)
1 disk2s2 CF03D24E-AB5D-4F86-A7B1-26A1F4589CB7 Online
===============================================================================
bsmith@kanga ~ $
Run it again 10 seconds later:
bsmith@kanga ~ $ diskutil list
It just hangs.
bsmith@kanga ~ $ sudo diskutil listRAID
It just hangs.
4. Now I turn off the 'old' drive and look at the terminal (that was hanging). When I turn it off I'm told (through the Hardware Growler Growl extension to show the status of hardware) that the old drive ("Macpower"), the new drive ("OWC") and the RAID disk ("terra") have all unmounted. The diskutil commands follow.
bsmith@kanga ~ $ diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *298.1 Gi disk0
1: EFI 200.0 Mi disk0s1
2: Apple_HFS Mini 297.8 Gi disk0s2
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *0.0 B disk1
1: EFI 200.0 Mi disk1s1
2: Apple_RAID 931.2 Gi disk1s2
3: Apple_Boot Boot OSX 128.0 Mi disk1s3
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *931.5 Gi disk2
/dev/disk3
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS terra *931.2 Gi disk3
bsmith@kanga ~ $
bsmith@kanga ~ $ sudo diskutil listRAID
RAID SETS
===============================================================================
Name: terra
Unique ID: 2AC46C49-5F0B-4BD5-B1FE-C322A6F51DD9
Type: Mirror
Status: Degraded
Size: 319728959488 B
Rebuild: automatic
Device Node: disk3
Apple RAID Version: 2
# Device Node UUID Status
0 disk1s2 A12D748F-0779-4217-8C75-B31D9AE45B4E 0% (Rebuilding)
1 -none- CF03D24E-AB5D-4F86-A7B1-26A1F4589CB7 Online
===============================================================================
bsmith@kanga ~ $
I don't know alot about this output, though its weird that disk2 is still in the list but only shows the GUIDpartitionscheme. And its interesting that disk1 is also in the list but shows 0.0B against the GUIDpartitionscheme for it.
5. Just for kicks I turn off the 'new' drive aswell and run the commands again. When i do it Hardware Growler doesn't say anything has unmounted (I guess since they all did so before).
bsmith@kanga ~ $ diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *298.1 Gi disk0
1: EFI 200.0 Mi disk0s1
2: Apple_HFS Mini 297.8 Gi disk0s2
bsmith@kanga ~ $ sudo diskutil listRAID
Password:
No RAID sets found
As expected I guess.
6. Now I'll turn both drives back on and confirm I get back to the same state I was in before after both drives were turned on.
This time I get the Hardware Growler message that both drives have mounted followed by the RAID drive about 20 seconds later.
bsmith@kanga ~ $ diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *298.1 Gi disk0
1: EFI 200.0 Mi disk0s1
2: Apple_HFS Mini 297.8 Gi disk0s2
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *931.5 Gi disk1
1: EFI 200.0 Mi disk1s1
2: Apple_RAID 931.2 Gi disk1s2
3: Apple_Boot Boot OSX 128.0 Mi disk1s3
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *931.5 Gi disk2
1: EFI 200.0 Mi disk2s1
2: Apple_RAID 931.2 Gi disk2s2
3: Apple_Boot Boot OSX 128.0 Mi disk2s3
/dev/disk3
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS terra *931.2 Gi disk3
bsmith@kanga ~ $
bsmith@kanga ~ $ sudo diskutil listRAID
RAID SETS
===============================================================================
Name: terra
Unique ID: 2AC46C49-5F0B-4BD5-B1FE-C322A6F51DD9
Type: Mirror
Status: Degraded
Size: 999860895744 B
Rebuild: automatic
Device Node: disk3
Apple RAID Version: 2
# Device Node UUID Status
0 disk1s2 A12D748F-0779-4217-8C75-B31D9AE45B4E 0% (Rebuilding)
1 disk2s2 CF03D24E-AB5D-4F86-A7B1-26A1F4589CB7 Online
===============================================================================
bsmith@kanga ~ $
Now let me run the commands again:
MMM, the exact same result is returned - it didn't hang this time.
It's 21:44, I'll leave this a while and see if the rebuilding continues.
Its 13 mins later and this time the commands are just hanging. Before I went away at 21:44 the lights on the front of the drives where flashing showing something was happening. They had stopped by the time I returned.
7. Now I turn off the 'new' drive and run the terminal commands again. When I turn it off I'm told by Hardware Growler that the new drive ("OWC") and the RAID disk ("terra") have both unmounted. Last time (when the 'old' drive was turned off) Growler told me all 3 drives unmounted. The diskutil commands now show.
bsmith@kanga ~ $ diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *298.1 Gi disk0
1: EFI 200.0 Mi disk0s1
2: Apple_HFS Mini 297.8 Gi disk0s2
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUIDpartitionscheme *931.5 Gi disk1
It hangs at this point and hasn't completed yet.
bsmith@kanga ~ $ sudo diskutil listRAID
Password:
RAID SETS
===============================================================================
Name: terra
Unique ID: 2AC46C49-5F0B-4BD5-B1FE-C322A6F51DD9
Type: Mirror
Status: Offline
Size: 999860895744 B
Rebuild: automatic
Apple RAID Version: 2
# Device Node UUID Status
0 disk1s2 A12D748F-0779-4217-8C75-B31D9AE45B4E Failed
0 -none- CF03D24E-AB5D-4F86-A7B1-26A1F4589CB7 Missing/Damaged
===============================================================================
bsmith@kanga ~ $
So HELP PLEASE!. Does the above provide enough information to suggest to someone with more knowledge than me about this, what is going on and what can I do to fix this? Let me know if there are any more tests I can run.
I have a backup of the data so can erase and recreate the RAID drive. But what would stop this happening again? Could it have been TechTools Pro 5 which was running when the problem first happened that caused some permanent damage?
Any and all help appreciated.
Thank you,
Brooke

Thanks ridogi and Antonio for your replies,
For clarification, both drives have dual FW 800 to allow them to be connected. No FW 400 involved (I'm not that silly .
I can't say i've done extensive research into setting up RAID drives but I've never come across advice to not use multiple external drives. Here is an extract from a Nov 2007 MacTech article on using RAID for backup:
{quote}
The Desktop Mac User:
The second user I want to look at is the professional who relies on his desktop Mac for his business. He is a lawyer, developer, architect or other professional whose business relies totally on the contents of his computer. If he loses the files on his computer, his business will really suffer. In addition, the time lost when dealing with a failed hard disk is money down the drain. This user relies on a three disk mirror volume. His Mac has two internal SATA disks which are used as the primary and secondary disks of a mirror volume. If one of the disks fails at any given point, the other one will take over and become the new primary disk, so his files are always protected from a hard disk failure. The third disk is an external FireWire disk which is also a secondary disk. It is stored offsite (either at home in a fireproof safe or at another safe location). Every Friday, he brings this third disk into his office and connects it to his desktop Mac. Once this disk is connected, a mirror rebuild starts automatically. He can perform this rebuild as he continues to use his Mac during the day. At the end of the day, when he shuts his Mac down, he disconnects his external secondary disk and returns it to its offsite location. This offsite secondary disk becomes his insurance against his building getting broken into or his building burning down. Like the laptop user, if his Mac gets destroyed, he can just purchase a replacement Mac and then boot up from his external secondary disk. At most, he will use one week's worth of work.
{quote}
So I just assumed it is ok to use external drives. This is discussing a software product called SoftRAID and perhaps that is able to handle the situation. Or perhaps one external drive is ok???
My plan, developed when deciding to buy the Mac Mini April 2009 was to amortize costs by buying external drives first for doing backups and then buying a NAS within 12 months. I guess I should have just gone the NAS.
However ridogi I see you've recommended WiebeTech which don't seem to have NAS devices but DAS (direct attached storage) as the devices are connected directly to a network machine via Firewire etc. (Whereas NAS connects via the Network - I'd connect such a device to the Airport wireless router). Do you prefer DAS over NAS? I guess the downside of NAS is that the complexity is somewhat greater.
And reading http://www.wiebetech.com/just-say-no-to-nas/ they say:
{quote}
Let's face it - Networked or "shared" storage is a great feature but most NAS devices are just too slow for many applications. 3MB/s for a NAS device is common and 10MB/s is considered fast. Direct Attached Storage (DAS) performs much faster while still having the ability to be "shared". The RTX400-QR can transfer data to your computer at speeds exceeding 100MB/s.
{quote}
How can this be? If connected via Gigabit ethernet (128MB/s) then isn't that faster?
Though it is true that if you connect via Wifi then the best speeds you are going to achieve is 6.75 MB/s (802.11g) or 17.5 MB/s (802.11n).
Of course the speed advantages for DAS are only going to be on the machine its connected to as the other machines will connect to it (via the machine its on) over the network anyway!
Why I like the idea of NAS is to move the drives away from the Mini (noise and powerpoint reasons), make it easier to share with other Macs/PCs in the house (including via SMB) and I have a vague hope that this might stop the delay caused by the connected external drives spinning up when an open/save dialog box is activated (or is this just me?!).
Your thoughts appreciated! And thanks for the help so far.
Cheers,
Brooke

Mirrored RAID Failed

I have an xserve with three drives. Bay one is a regular single boot volume but bays 2 & 3 are a mirrored RAID pair. I got a flashing yellow light yesterday and ran Disk Utility. It showed the RAID pair as having an error. I ran First Aid and it now reports that the volume is OK but when I look at the RAID panel only one physical disk is listed. The volume still functions ok, the server is working fine and the yellow light is not flashing now - but I guess this means that I do not have a mirrored RAID pair anymore.
How should I go about returning my RAID to a mirrored pair? How can I identify which of the two physical disks has failed? (I don't want to pull out the wrong one!) Can I slot in a new disk and have it added into the RAID as a replacement?

Do you have a backup of that RAID?
If yes I would rebuild the RAID. From what you are saying I would not trust it any more. When you do that then you can test each disk by formating it and then trying to copy data to the drive. You can then see if one is not working right or if they both are fine.

Xserve - Mirrored RAID Failed? Degraded? Confused...

Hi,
Can anyone shed some light on this situation please? Disk utility tells me one thing and Server Monitor tells me another.
I have an X-Serve with 3 drives and a Mirrored RAID Set running 10.5.8.
Server Monitor is showing a yellow status for disk 1 and disk 2. Raid Status: Degraded (Mirror) Pre-failure Warning: No Warnings
Disk Utility on the other hand shows that the Mirrored RAID sets are Degraded because disk2s4 = Failed and disk2s2 = Failed.
Running disk utility commands in terminal also show disk2s4 and disk2s2 as Failed.
I have not yet tried to Rebuild or eject / reconnect the disk. The only thing I've really done is some research and rebooted the server.
It sounds like disk 2 has failed. Is there any way to confirm it's dead? Are there any serious risks of trying to rebuild?
Thanks.
- F4st

I'm not sure why you think you're seeing conflicting information…
Server Monitor is showing a yellow status for disk 1 and disk 2. Raid Status: Degraded (Mirror) Pre-failure Warning: No Warnings
OK, So Server Monitor says the RAID is in a degraded state…
Disk Utility […] shows that the Mirrored RAID sets are Degraded because disk2s4 = Failed and disk2s2 = Failed
Running disk utility commands in terminal also show disk2s4 and disk2s2 as Failed
I don't see this is anything different. All three methods are telling you disk2 has failed and your mirror is relying on disk1 for all activity.
Is there any way to confirm it's dead?
Umm.. you mean other than Server Monitor, Disk Utility.app and diskutil?
Face it, it's dead. It's had it.
Are there any serious risks of trying to rebuild?
Sure. If the disk is dead, it's entirely possible that rebuilding the array on that disk will fail. You run the risk of a problem on disk1 and then all your data is gone.
My advice: Replace disk2 as soon as possible. If not sooner.

Mounting lvm (on raid) fails every few boots

Hi,
as the title says, every few boots (probably every 5th boot or so) I get dropped to an emergency console because mounting one of my logical volumes (not always the same one) fails.
I have attached the logs form a successful and unsuccessful boot. The relevant lines I could find are:
Job dev-mapper-raidvg\x2dlvimages.device/start timed out.
Nov 01 07:58:01 mythbackend systemd[1]: Timed out waiting for device dev-mapper-raidvg\x2dlvimages.device.
Nov 01 07:58:01 mythbackend systemd[1]: Dependency failed for /home/laffi/media/images.
Nov 01 07:58:01 mythbackend systemd[1]: Dependency failed for Local File Systems.
Nov 01 07:58:01 mythbackend systemd[1]: Triggering OnFailure= dependencies of local-fs.target.
Nov 01 07:58:01 mythbackend systemd[1]: Dependency failed for File System Check on /dev/mapper/raidvg-lvimages.
Another thing I noticed is that a filesystem check gets started for that particular lv (lvimages) during the successful boot, but not the unsuccessful one. No idea if that means anything.
As you can see from the full log other lv's get mounted successful during the same boot.
The raid also seems to get started fine. I noticed this line in the logs, but it's in both the successful and unsuccessful boots so it probably is not the issue.
Nov 01 07:56:31 mythbackend systemd[1]: Cannot add dependency job for unit lvm.service, ignoring: Unit lvm.service failed to load: No such file or directory.
This is my fstab
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
# /dev/sda1 /boot ext4 defaults 0 1
/dev/sda2 swap swap defaults 0 0
/dev/sda5 / ext4 defaults 0 1
#/dev/VolGroup01/lvolhome /home ext4 defaults 0 1
#/dev/raidvg/lvhome /home ext4 defaults 0 2
/dev/sda7 /home ext4 defaults 0 2
/dev/mapper/raidvg-lvmusic /home/laffi/media/music ext4 defaults 0 2
/dev/mapper/raidvg-lvphotos /home/laffi/media/photos ext4 defaults 0 2
/dev/mapper/raidvg-lvvideos /home/laffi/media/videos xfs defaults 0 2
/dev/mapper/raidvg-lvmovies /home/laffi/media/movies xfs defaults 0 2
/dev/mapper/raidvg-lvcamcorder /home/laffi/media/camcorder ext4 defaults 0 2
/dev/mapper/raidvg-lvrecordings /home/laffi/media/recordings xfs defaults 0 2
/dev/mapper/raidvg-lvlivetv /home/laffi/media/livetv xfs defaults 0 2
/dev/mapper/raidvg-lvrecarchive /home/laffi/media/recarchive xfs defaults 0 2
/dev/mapper/raidvg-lvbooks /home/laffi/media/books ext4 defaults 0 2
/dev/mapper/raidvg-lvimages /home/laffi/media/images ext4 defaults 0 2
# /dev/mapper/raidvg-lvbackhome /home/laffi/media/backhome ext4 defaults 0 2
/dev/sda6 /home/laffi/media/backup ext4 defaults 0 1
/dev/sdf1 /home/laffi/usbdrive ntfs defaults,nofail 0 2
Any help will be much appreciated. Thank you.u
Log of successful boot:
http://pastebin.com/raw.php?i=ZE9k76PW
Log of unsuccessful boot
http://pastebin.com/raw.php?i=12FH8S1B

WonderWoofy wrote:If you vgchange -ay when it drops you into the initramfs shell, can you then exit out and continue the boot?
Ok, finally managed to try this.
vgchange -ay results in a "volume group with 11 logical volumes now active" or something along those line.
I then pressed CTRL+D to exit the emergency console. After that, nothing happened. Waited a few minutes, just in case, then rebooted (via ctrl+alt+del).
Something maybe worth noting: in the meantime I had enabled the lvm-monitoring service to see if that makes a difference (seems like it doesn't, since I still have the same problem). I found the following line(s) in this unsuccessful boot (with lvm-monitoring service enabled):
Nov 07 09:00:29 mythbackend lvm[164]: 11 logical volume(s) in volume group "raidvg" monitored
Nov 07 09:00:29 mythbackend systemd[1]: Started Load/Save Random Seed.
Nov 07 09:00:29 mythbackend systemd[1]: Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
And then further down the following familiar lines:
Nov 07 09:00:32 mythbackend systemd[1]: Starting File System Check on /dev/sda7...
Nov 07 09:00:32 mythbackend systemd-fsck[305]: /dev/sda7: clean, 57416/640848 files, 1091272/2559488 blocks
Nov 07 09:00:32 mythbackend systemd[1]: Started File System Check on /dev/sda7.
Nov 07 09:00:32 mythbackend systemd[1]: Mounting /home...
Nov 07 09:00:32 mythbackend systemd[1]: home.mount: Directory /home to mount over is not empty, mounting anyway.
Nov 07 09:00:32 mythbackend kernel: EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null)
Nov 07 09:00:32 mythbackend systemd[1]: Mounted /home.
Nov 07 09:00:32 mythbackend systemd[1]: Mounting /home/laffi/media/backup...
Nov 07 09:00:32 mythbackend kernel: EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
Nov 07 09:00:32 mythbackend systemd[1]: Mounted /home/laffi/media/backup.
Nov 07 09:01:57 mythbackend systemd[1]: Job dev-mapper-raidvg\x2dlvrecarchive.device/start timed out.
Nov 07 09:01:57 mythbackend systemd[1]: Timed out waiting for device dev-mapper-raidvg\x2dlvrecarchive.device.
Nov 07 09:01:57 mythbackend systemd[1]: Dependency failed for /home/laffi/media/recarchive.
Nov 07 09:01:57 mythbackend systemd[1]: Dependency failed for Local File Systems.
Nov 07 09:01:57 mythbackend systemd[1]: Triggering OnFailure= dependencies of local-fs.target.
Nov 07 09:01:57 mythbackend systemd[1]: Dependency failed for File System Check on /dev/mapper/raidvg-lvrecarchive.
Any thoughts ? Thank you very much.
Last edited by dafrizz (2013-11-07 06:45:09)

RAID Fails to find the first device

Hello all.
This is my first post to the forum. I did a brief search but i couldn't find any good results, so i tought i'd post my prob here.
I have an MSI K7N2 Delta2-LSR motherboard, with a 450W PSU (i don't have any more info on that yet), 2x512MB RAM DDR 400 (no more info on that one yet either), 2x120GB SATA WD HD, 1xDVD TEAC, 1xDVD+-RW SONY DL, 1x1.44MB FDD, an ATI RADEON 9600 PRO ALL-IN-WONDER VGA card on an nForce chipset.
The first HD has WinXP installed on it with the raid drivers installed properly. The second HD has Mandrake 10.1 Linux installed on it. They are installed as separate arrays.
The problem I'm having is that while I'm working in Windows, after a while the computer completely freezes. The only possible way out of it is to reset the machine. After I do that, at the boot screen, it fails to find the first HD (the one with WinXP on it). If i turn it off for let's say 5 minutes, and boot up, it detects the HD again and goes on loading windows. After I log in i have at maximum 5 minutes before it freezes again.
It does this every time. The more time I leave my PC turned off, the longer time it will take to freeze again when I'm logged in WinXP. I formatted the HD many times, installing every possible combination of my drivers but the problerm persists. Although it has never happened anything like that in Linux.
Could it be the RAID Controller (onboard), the WD HDD, or the Motherboard in general?
What can I do to find out what the problem is? And if possible, how to solve it?
If more info is needed, I will update the info of my pc as soon as I get back home.
P.S. I cheched the WD HDD, using WD tools like Disk Diag, etc. It never gave me any problems. I also used UBCD for win, and cheked the disk, to dicover once again, that the disk supposingly has no problems.
Any help would be appreciated.
Thanks in advance.

of its label Power Supply Guide
i suspect the drives bad
go to wd site and look for their drive tester

K9A2 Platinum bios 1.4 or 1.5 Promise RAID fail Boot.

Ok I have BIOS version 1.3 running fine. I want to upgrade to a bios that officially support the phenom and its power usage. So back in may I try to upgrade to bios 1.4. No good the machine will not boot the RAID set that contains window XP. :( Reverted back. Contacted support. Not much help... a few weeks pass. Contact support again they send me bios version 1.51. Same issue. Reverted back to 1.3. Recently I tried the final release of 1.5 with the same issue.
Anyone out there using a phenom on the K9A2 and booting with the Promise RAID controller in a striped 0 set ? How did you get it to work with the current bios version. Tech support 'claims' they have no problem with the bios and that they have tested it with the promise controller booting to XP.
Thanks,
Jon Harrell

Considering the very large files that regularly run through the system and the extra cpus that windows inefficiently uses I doubt a software controller would impact the performance gains significantly. The units we have prep large format presentations and regularly handle very large files. Bandwidth is key. If this was the average desktop or even a web server yes 1 drive would most definitely be faster. But that would be a different subject.
Although now we might just be considering scraping the whole MSI created mess, and purchasing a hardware solution like that of the quad sata raid in our server.
But for now:
Does any one know the perfect combination?
e.g. Promise driver 1.1.1030.47 !work with Bios 1.50 (promise 2.8.1030.0032)
Thanks,
jh

Disk Utility RAID Issue

I'm trying to determine if the problems that I'm encountering are a software issue or a hardware issue.
I'm setting up a Mac Pro with Leopard and have four Maxtor 6G160E0 160GB hard drives that I'm trying to set up as two Mirrored drive sets. Everything seemed to go fine, created the two mirror sets, installed Leopard, configured and tested two user accounts and Office 2004, then updated everything to the latest version. When done I shut it down planning on moving it to it's final home tonight.
But, when I turned it on both mirror sets were degraded - all four drives were still recognized as RAID slices but came up as failed in the RAID tab. I saw no errors reported in the log so I assumed that those two drives were faulty. I shut down, moved the good drives to bays 1 & 2 and rebooted.
First reboot gave me a prohibition symbol instead of the usual Apple. Powered down and on and it booted fine but the second drive came up as a failed RAID slice. Rebooted again and both were fine.
I reinstalled the two "failed" drives and reformatted them - both reformatted fine and mounted without problems. I unmounted the new partition just in case, but, when I tried to rebuild the RAIDs I get the following in the error log:
11/1/07 7:26:00 PM Disk Utility[141] Preparing to erase : “Untitled”
11/1/07 7:26:00 PM Disk Utility[141] Partition Scheme: GUID Partition Table
11/1/07 7:26:00 PM Disk Utility[141] 1 volume will be created
11/1/07 7:26:00 PM Disk Utility[141] Name : “Untitled”
11/1/07 7:26:00 PM Disk Utility[141] Size : 149.1 GB
11/1/07 7:26:00 PM Disk Utility[141] Filesystem : Mac OS Extended (Journaled)
11/1/07 7:26:00 PM Disk Utility[141] Creating partition map.
11/1/07 7:26:03 PM Disk Utility[141] Formatting disk1s2 as Mac OS Extended (Journaled) with name Untitled.
11/1/07 7:26:06 PM Disk Utility[141] Erase complete.
11/1/07 7:26:12 PM Disk Utility[141] Unmount of “Untitled” succeeded
11/1/07 7:26:31 PM Disk Utility[141] Rebuilding RAID
11/1/07 7:26:31 PM Disk Utility[141] Filesystem: Mac OS Extended (Journaled)
11/1/07 7:26:31 PM Disk Utility[141] RAID type: Mirrored RAID Set
11/1/07 7:26:31 PM Disk Utility[141] RAID set name: “Yorktown”
11/1/07 7:26:31 PM Disk Utility[141] RAID set status before rebuild: “”
11/1/07 7:26:31 PM Disk Utility[141] RAID chunk size: 32K (default)
11/1/07 7:26:31 PM Disk Utility[141] Mirror Auto Rebuild: Disabled (default)
11/1/07 7:26:31 PM Disk Utility[141] 2 members
11/1/07 7:26:31 PM Disk Utility[141] RAID Slice (disk0s2) - Online
11/1/07 7:26:31 PM Disk Utility[141] Maxtor 6G160E0 Media (disk1) - New
11/1/07 7:26:32 PM Disk Utility[141] Error rebuilding RAID: Unrecognized Filesystem.
11/1/07 7:26:33 PM Disk Utility[141] RAID failed: Unrecognized Filesystem.
I'm at a loss at the moment. I am leaning towards bad drives, but FOUR bad drives all at once is suspicious.
I've searched for similar issues and found none so I thought I'd check here and see if anyone had any ideas.

G'day Zeekm,
Thank you for that. I did this and it seems to work. The Disk Utility GUI does not seem to work.
Hope this helps some one,
#Checked the RAID status
root# diskutil checkRAID
RAID SETS
===============================================================================
Name: Server_HD
Unique ID: 7E31E20E-F53D-4D76-AD37-139C4E1440AB
Type: Mirror
Status: Degraded
Size: 1000070610944 B
Device Node: disk2
Apple RAID Version: 2
# Device Node UUID Status
0 disk1s3 BAC72F86-B05F-4B0F-97D3-58A6207E7DFA Failed
1 disk0s3 2BFB55BB-EFF9-438C-A1F9-A8ED7A93D385 Online
===============================================================================
#Told it to resync
root# diskutil repairMirror disk2 disk1s3
Note: Syncing data between mirror partitions can take a very long time.
Note: The mirror should now be repairing itself. You can check its status using 'diskutil listRAID'.
temp:~ root# diskutil listRAID
RAID SETS
===============================================================================
Name: Server_HD
Unique ID: 7E31E20E-F53D-4D76-AD37-139C4E1440AB
Type: Mirror
Status: Degraded
Size: 1000070610944 B
Device Node: disk2
Apple RAID Version: 2
# Device Node UUID Status
0 disk1s3 9D955C85-7EC0-4E92-848A-62D9F7C12EED 0% (Rebuilding)
1 disk0s3 2BFB55BB-EFF9-438C-A1F9-A8ED7A93D385 Online
===============================================================================
Hope this helps,
Cheers,
Arthur

Software RAID setup by partition or by drive?

I've outgrown my ext FW drive that has served me well. May I still use it in a RAID 1 with a partition from a larger drive I am going to get?
I've spent the last few years backing up a TiBook to an ext FW 120GB Maxtor drive, which has worked well. I use SuperDuper to create the bootable backup every week or two and usually keep one or two old versions. It also holds my music and photo libraries, which are multi-GB.
With that said, I now have a MBP w/100GB int HD, so the 20GB partitions will no longer suffice. I've been thinking of getting a Maxtor 600GB RAID 0 as an upgrade. I like the speed but remain concerned about the risk of RAID 0. If SW RAID is by partition, it recently occurred to me that I can RAID 1 mirror the ext FW 120 GB drive and one 120 GB partition of the RAID 0 600GB dirve. Is that possible?
These appear to be the advantages: 1. RAID 1 on the backup, so if either the old drive fails or one of the drive in the RAID fails, the data is still fine. 2. Still get speed on the new RAID 0 ext. drive.
Please advise.
fellow

Hi fellow;
With the experience I have had supporting servers with RAID for IBM, I personally would try to find a different solution. I see too many variables, such as the buses and drives, to make me think it is going to be worth the effort. About the only RAID solution that were worthwhile were those that followed the rules.
Allan

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

RAIDS and Time Machine?

I want to get a Mac Pro with 4 500 GB HDs. I want to stripe two of the HDs together, and then stripe the other 2 together giving me two RAID 0's of 1 Terabyte each.
Then can I use Time Machine when it is released to backup the primary RAID to the secondary RAID.
Would this be a good solution?

Assuming your RAID setup is as follows:
Drive 1 and Drive 2 are Striped into a RAID 0 (Logical Disk 1)
Drive 3 and Drive 4 are Striped into a RAID 0 (Logical Disk 2)
Logical Disk 1 and Logical Disk 2 are Mirrored into a RAID 1
You can remove Logical Disk 2 from your Mirrored RAID array with no noticeable difference in your system. You could then use Drive 3 and Drive 4 separately or Re-Stripe them into a RAID 0 Logical Disk 2 which could then be used as the backup disk for Time Machine.
If your Logical Disk 1 RAID fails and it is mirrored with Logical Disk 2 all your data will be safe though running/existing exclusively on Logical Disk 2 until you replace the faulty drive in Logical Disk 1.
If your Logical Disk 1 RAID fails and it is not mirrored with Logical Disk 2 then you will lose all the data on Logical Disk 1 even though only one of the two drives failed.
If your Logical Disk 1 RAID fails and you have been using Logical Disk 2 as your Time Machine drive you will (in most circumstances) be able to replace the failed drive, recreate a Striped RAID 0 Logical Disk 1 from Drive 1 and Drive 2 and then use Time Machine to restore your files and applications. As I do not have the Leopard Preview I cannot tell you how this will work in practice but it is part of Time Machine's prerogative to aid in situations like this.
There is a caveat to keep in mind concerning Time Machine that may or may not affect you depending on how you use your computer. John Siracussa at ArsTechnica explains it very well so I'll just copy and paste from his recent article on Time Machine:
"There's still plenty of room for legitimate Time Machine criticism, however. While the hard link trees are a clever solution, given the constraints of HFS+, the strategy dictates a file-level granularity for all backups. In other words, if you change a single byte of a 500MB file, the entire 500MB file will be copied to the backup volume during the next Time Machine backup. Frequent modifications to large files will fill your backup volume very quickly."
"Worse, there does not appear to be a way to prioritize backup retention. When space runs out on the backup volume, presumably Time Machine will recycle old space. But if it does so based on date rather than (user-specified) "importance", a relatively unimportant change to a large file could necessitate the loss of hundreds of small files from the backup volume. Where once a small text file may have had an entire year's worth of revisions on the backup volume, now only the past month's revisions may exist due to the need to reclaim space for a few recently modified large files."
So just keep in mind that if you want Time Machine to keep a backup of your entire system throughout it's use you will in all likelihood need considerably more storage space than the amount available on the drive(s) Time Machine is monitoring.
-Berylium
Mac OS X (10.4.7)

RAID Logs

Hi,
We have a late 2009 Intel Xserve with hardware RAID configured with 3 disks in RAID 5 configuration.
Our disk 1 (bay 1) failed. Initially when we noticed this the disk was detected in the RAID utility but before we could do anything else the rest of the RAID seemed to fail.
We booted the server from the CD and the RAID utility then showed no Bay 1 but did show Bays 2 and 3 but they were in a roaming state.
We replaced Bay 1 and RAID util saw the new drive but the only thing it would let us do was create a new RAID set so we have invariably lost the RAID. We have now restored the server and are up and running again, but I was wondering if there are any hardware logs that are independent of the OS that I can look at to check what happened. In the restored OS RAID util logs I have the following:
Wednesday, 16 March 2011 10:46:54 GMT The "RedundancyScrub" command could not be executed. (Invalid request or invalid parameter in the request.) warning
Tuesday, 15 March 2011 22:20:09 GMT Drive carrier 00:01 inserted informational
Tuesday, 15 March 2011 22:09:48 GMT Drive carrier 00:01 removed informational
Tuesday, 15 March 2011 22:09:47 GMT Drive 3:50014ee1ac5d533f missing - Previous drive status was unassigned critical
Tuesday, 15 March 2011 22:09:47 GMT Drive 3:50014ee1ac5d533f failure detected - Primary disk port unusable, previous drive status was unassigned warning
Tuesday, 15 March 2011 12:40:28 GMT Drive carrier 00:01 inserted informational
Tuesday, 15 March 2011 12:40:12 GMT Drive carrier 00:01 removed informational
Tuesday, 15 March 2011 12:37:21 GMT Degraded RAID set RS1 - No spare available for rebuild critical
Tuesday, 15 March 2011 11:14:02 GMT Drive 3:50014ee1ac5d533f missing - Previous drive status was unassigned critical
Tuesday, 15 March 2011 11:14:02 GMT Drive 3:50014ee1ac5d533f failure detected - Primary disk port unusable, previous drive status was unassigned warning
Tuesday, 15 March 2011 11:13:47 GMT Degraded RAID set RS1 - No spare available for rebuild critical
Tuesday, 15 March 2011 11:13:47 GMT Degraded RAID set RS1 warning
Tuesday, 15 March 2011 11:13:46 GMT Drive carrier 00:01 removed informational
Wednesday, 23 February 2011 15:09:18 GMT Battery finished conditioning informational
Wednesday, 23 February 2011 09:19:58 GMT Battery started scheduled conditioning cycle (write cache disabled) informational
Thursday, 25 November 2010 09:19:49 GMT Battery finished conditioning informational
Thursday, 25 November 2010 03:31:13 GMT Battery started scheduled conditioning cycle (write cache disabled) informational
We are currently running a RAID verify after the RedundancyScrub failure which happened during the restore process.
I can see that the drive has been reported as being removed and reinserted, however this would have been physically impossible as I am assured there was no-one on site at these times.
I am assuming that the disk itself failed as I tried this in an external closure and it didn't work, just clicked.
I am really trying to see if I can get logs to determine why the rest of the RAID failed, as I think this can be done on Dell servers as the hardware has it's own logs. Is this true of the Xserve?

Initially it was. However I was not on site and my junior engineer has only a little Mac experience so I didn't want him to do anything until I arrived. By the time I did the server had just restarted and was showing the Broken Folder Icon. I booted from the CD and in the RAID utility it did not detect the drive in Bay 1 and Bay 2 and 3 were showing as roaming.
Like I said, I am all up and running again with a spare disk and a complete reinstall, but I have been asked why this happened and wanted to produce some logs to try and explain why the RAID failed and also to see if there is anything that I can implement in order to prevent a recurrence in the future.
Thanks for the reply.

Raid not connecting

Ok, I'll try to give the best info i can. Everything was working fine but I had to move the xserve to the botton of the cabinet.
So I unmounted all the rais and drives and shut it down. Disconnected eveything put it back were it needed to go and the server
is fine but I get a networ errror message in Server"The network configuration has changed" In raid admin it shows the 3 raids failed to connect.
I reset the controller on each raid but nothing has changes. I can see and open all the drives inn finder and see the files.
What am I missing?
Thanks
Martin

Hi Martin,
On the xserve do you have the FQDN fully qualified domain name in server admin? You should be able to connect by clicking Add server and entering 127.0.0.1.
As for RAID Admin it only works if the RAID is connected via ethernet. It sounds as if you either haven't connected the ethernet, your network config has changed or you had them on DHCP. Try clicking Add on RAID admin then seeing if it sees the 3 RAIDS. It's always best to set these to a fixed IP.
Hope that helps
Beatle

6380 mb raid failing

Similar Messages

Maybe you are looking for