Rebuilding Raid Set Failed With The Error Unrecognized Filesystem
Contents |
enter a title. You can not post a blank message. Please type your message and try again. This discussion is locked gsfunkarch Level 1 (0 points) Q: Rebuilding RAID set failed with the error: Unrecognized Filesystem. I have a mirrored RAID on our small office server. disk erase failed with the error couldn t open device One of the drives had an error, so I removed it, and am replacing it with partition failed with the error unable to write to the last block of the device a new drive.However, when I try to rebuild the RAID with the new disk, I get the following error:"Rebuilding RAID set failed with the disk erase failed unable to write to the last block of the device error: Unrecognized Filesystem."I have tried all sorts of ways of erasing, partitioning, etc. to Mac OS Extended (Journaled) - which is what the RAID set is - but with no success. Does anyone have ideas? Thanks. Mac Pro, Mac OS
Disk Erase Failed Couldn't Open Disk
X (10.5), Server / Workstation Posted on Apr 25, 2008 7:58 AM I have this question too Close Q: Rebuilding RAID set failed with the error: Unrecognized Filesystem. All replies Helpful answers by Sherman Homan, Sherman Homan Apr 25, 2008 10:08 AM in response to gsfunkarch Level 3 (710 points) Apr 25, 2008 10:08 AM in response to gsfunkarch Can you pop the old drive back in? What is the error message? Helpful (0) Reply options Link to this error 69877 couldn t open device post by gsfunkarch, gsfunkarch Apr 25, 2008 10:56 AM in response to Sherman Homan Level 1 (0 points) Apr 25, 2008 10:56 AM in response to Sherman Homan I sent the old drive back to Seagate - it was still under warranty and they sent me a replacement drive. The error with the old drive was regarding SMART failure.When I got the new drive - I put it in and upon restarting the computer got a request to initialize the disk as the OS couldn't recognize it. I initialized and then formatted and partitioned to HFS Extended (Journaled) and the drive appears to be working 100%...just won't allow me to rebuild as part of RAID. Helpful (0) Reply options Link to this post by Sherman Homan, Sherman Homan Apr 25, 2008 11:00 AM in response to gsfunkarch Level 3 (710 points) Apr 25, 2008 11:00 AM in response to gsfunkarch What happens if you shuffle the other drives around, I am wondering if there is a problem with the bay the hard drive goes into. Helpful (0) Reply options Link to this post by gsfunkarch, gsfunkarch Apr 28, 2008 7:34 AM in response to Sherman Homan Level 1 (0 points) Apr 28, 2008 7:34 AM in response to Sherman Homan I tried shuffling the drives but I get the same error....! Helpful (0) Reply options Link to this post by gsfunkarch, gsfunkarch Apr 28, 2008 7:51
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack unable to write to the last block of the device mac Overflow the company Business Learn more about hiring developers or posting ads with us
Posix Reports The Operation Couldn T Be Completed Input Output Error
Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network
Volume Erase Failed With The Error Couldn't Open Disk
administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top RAID-5: Two https://discussions.apple.com/thread/1499103?start=0&tstart=0 disks failed simultaneously? up vote 20 down vote favorite 2 We have a Dell PowerEdge T410 server running CentOS, with a RAID-5 array containing 5 Seagate Barracuda 3 TB SATA disks. Yesterday the system crashed (I don't know how exactly and I don't have any logs). Upon booting up into the RAID controller BIOS, I saw that out of the 5 disks, disk 1 was labeled as "missing," and disk 3 was http://serverfault.com/questions/614523/raid-5-two-disks-failed-simultaneously labeled as "degraded." I forced disk 3 back up, and replaced disk 1 with a new hard drive (of the same size). The BIOS detected this and began rebuilding disk 1 - however it got stuck at %1. The spinning progress indicator did not budge all night; totally frozen. What are my options here? Is there any way to attempt rebuilding, besides using some professional data recovery service? How could two hard drives fail simultaneously like that? Seems overly coincidental. Is it possible that disk 1 failed, and as a result disk 3 "went out of sync?" If so, is there any utility I can use to get it back "in sync?" raid storage hardware-raid raid5 data-recovery share|improve this question edited Mar 26 '15 at 9:55 peterh 1 asked Jul 22 '14 at 14:48 Mike Furlender 2221210 18 Yeah, big sata disks tend to do that. (Rebuilding 3 TB takes many hours while you are exposed to double-failures). So this is expected and it's why RAID-5 using such a configuration is absolutely not recommended. –MichelZ Jul 22 '14 at 14:54 9 Indeed. In an ideal world drive failure rates are randomly distributed. Practically, this doesn't happen - they are usually bought from the same batch and subjected to the same stresses,
Miniguide to fixing Volume-Filesystem errors Apr 29, '11 07:30:00AM • Contributed by: santa97298 There are many drive/filesystem errors that can occur on a Mac. Here are some common http://hints.macworld.com/article.php?story=20110216112523818 symptoms that are indicative of some of them: Not able to boot the system: You tried to boot. Apple logo appeared, and wheel spun for about 15-20 seconds, then machine turned off. This repeated every time you tried to boot the system. (REASON: The system does not find your HD and thus the OS to boot). Everything seems to work fine till your failed with system hangs briefly and in an unpredictable way. You wait for a while, and the system magically comes back to normal. But after another while, the same thing re-occurs! (This cycle repeats in the current session). You can do these simple things to check for other possible causes: Run Activity Monitor to see that this is NOT due to temporarily high CPU and/or Memory failed with the usage. Check the system log using Console.app or running tail -f /var/log/system.log in Terminal. If your system is having some I/O error then it is sure that there is an HD failure issue. I don't claim to be an expert on this subject matter, just an (over)enthusiast Mac user. This guide is purely based on my personal experience and is bound to contain errors. So, USE IT AT YOUR OWN RISK! [crarko adds: Consider this hint to also serve as a reminder to check your backups...]Possible problems: Your HD Volume/FileSystem is corrupted Verification: Use Disk Utility and run "verify" to check it. 2. Your HD is dying. Verification: Use Disk Utility and see the SMART status of your HD, although this isn't always reliable. Before making any repair of the disk, make sure that you have the latest backups. Repair might let loose the volume/filesystem info all together and then there will be no other choice than to recover the data by some data rescue s/w like Data Rescue! If you don't have a current backup, you can try booting in Single-User mode by holding Command+S on sta