Disk Read Error Raid 5
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: A Disk Read Error Has Occured (RAID 5) Windows Small Business Server > Small Business Server Question 0 Sign in to vote Hi guys, Wondering how to fix a disk read error occurred if you can give me any tips or ideas on how to solve the following
A Disk Read Error Occurred Windows 7
issue. I have an SBS 2008 server SP2 that is running in RAID 5, if i recall correctly its a Dell T110. One
A Disk Read Error Occurred Press Ctrl+alt+del To Restart
day the customer came in and the error on the screen read "A disk read error occured Press Ctrl+Alt+Del to Restart". I arrived onsite, checked the RAID controller (Perc 6i) the controller and all the drives are marked
Disk Read Error Windows 7
as optimal so it isn't a failed drive. I then out of curiosity used Hirens Boot CD and selected boot to my PC and what do you know the server booted up correctly. I had opened a call with Dell and ran their Dset Diagnostics which found there to be no issue with the controller, drivers or a RAID puncture. So i am wondering where i can go with it no being a hardware issue but disk read error windows 10 with the system not telling me it is missing a specific file, i have ran sfc/scannow within the environment and it finished without an issue. I did boot to the system CD earlier on and viewed that it could see the partition and was thinking maybe a bootrec /fixmbr might help but i havn't run it yet. Any idea's or pointers on how to proceed, any advice is appreciated. Hoping someone has seen this before as normally to me a disk read error is generally a failed hard drive. Thank You Alex Sunday, January 20, 2013 12:44 AM Reply | Quote Answers 0 Sign in to vote ***Update*** Went into recovery console and ran bootrec.exe /fixboot and it appears the server is now booting correctly. All done in time for the football game. Marked as answer by Andy QiMicrosoft contingent staff, Moderator Monday, January 21, 2013 10:53 AM Sunday, January 20, 2013 4:20 PM Reply | Quote Microsoft is conducting an online survey to understand your opinion of the Technet Web site. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.Would you like to participate? Privacy statement © 2016 Microsoft. All rights reserved.Newsletter|Contact Us|Privacy Statement|Terms of Use|Trademarks|Site Feedback TechNet Products IT Resources Downloads Training Support Products Windows Windows Server System Center Browser Of
Ctrl+Alt+Del to restart Error Raymond Updated 4 years ago Windows 101 Comments When you have a problem while using your computer and you receive an error message during a crash, you're hoping the message will point toward the cause and then it can be appropriately rectified. This a disk read error occurred windows 10 doesn't always happen though and the message can be rather generic and the fix isn't exactly a a disk read error occurred press ctrl+alt+del to restart windows 7 straightforward affair with a clear place to start troubleshooting.Unfortunately, there seems to be many errors you could encounter on your system that sound straightforward but a disk read error occurred xp lead to the same problem, the error message isn't accurate enough for you to make a clear decision about what to do next. A while back I had a problem with my computer, and after some odd things happening such as a https://social.technet.microsoft.com/Forums/en-US/9bc9454e-3439-421c-b1b6-58172d9059b5/a-disk-read-error-has-occured-raid-5?forum=smallbusinessserver CD-R failing a burn and the computer starting to respond very slow, I decided to shut it down and leave it for a while. When I booted it up the next day, I got the error message:A disk read error occurred. Press Ctrl+Alt+Del to restart.However, the BIOS detected the hard drive just fine. After an exhaustive search around the Internet and forums, no one had the exact fix for this problem and there doesn't seem to be one fix to try in preference to https://www.raymond.cc/blog/help-a-disk-read-error-occurred-press-ctrlaltdelete-to-restart/ any others.What makes this even worse is there are so many different ways to attempt to fix this error, it could take days to get through them all. And to make matters worse, a disk read error might not actually mean there's a problem with the hard drive itself! Also there seems to be just as many software causes as hardware causes.Listed below are some of the possible solutions we came across to fix the "A disk read error occurred. Press ctrl+alt+delete to restart" problem.1. Test the MemoryThis isn't actually mentioned that much around the web as a solution to the disk read error problem, but believe it or not, this was my problem. I used a tool called Memtest86+ and ran tests on my RAM, and indeed there were problems. After experimenting between different sticks and RAM slots I eventually deduced my RAM slot 2 was damaged because the sticks worked fine in the other slots.As this is a simple and non destructive test meaning you're not touching the hard drive risking further damage, it is recommended you try this first. It may sound odd but in fact memory problems can be responsible for a vast array of different errors on a system where testing your RAM might be the last thing you think of.2. Try the Drive on Another MachineAs we've said, although this problem sounds like a simple hard drive issue, people around the web have reported that they have traced the problem to faulty video cards, m
account only takes a few minutes. Join Now I have never had this much trouble recovering from this error. Machine is an Intel motherboard with Intel Sata RAID https://community.spiceworks.com/topic/101128-a-disc-read-error-occurred-press-ctrl-alt-del-to-restart controller. I have two SATA 450 gig drives in a RAID 1. I defragged https://news.ycombinator.com/item?id=8306499 this machine on memorial day weekend and then I noticed that the Cobian back up program had errors. Cobina saif there was no C drive when trying to to the volume shawdow process. I could see the hard drive in winodws and this computer has been running every since but had never beet restarted. I disk read restarted it today and now I get a disc read error occurred Press CTRL ALT DEL to restart. I have tried a several software programs to try and get an image of this drive. Most programs see the hard drive but do not see any partition information. Any ideas on what program i can use to image this drive and back up the data? Active Kill DIsk can see disk read error there is information taking up some of the drive but it can not read it. Reply Subscribe View Best Answer RELATED TOPICS: A disk read error occurred press ctrl+alt+del to restart -Virtual Machine 2012R2 Press Ctrl + Alt + Del to restart" windows 7 GP that lock screen - User must press Ctrl+Alt+Del   9 Replies Serrano OP Joel Porozynski Jun 8, 2010 at 12:02 UTC Piriform Recuva is a free file recovery program that does well...it should find all the info and allow you to save it. 0 Poblano OP agengler Jun 8, 2010 at 12:07 UTC Insert their Windows CD, and press a key when prompted to "Boot from CD." Once the loading finishes, do NOT hit ENTER to load Windows. Instead, hit "R" to enter the Recovery Console. Select the Windows install you wish to log into (there's probably only one, unless you're dual-booting with Vista- if that's the case, you can find more help at http://support.microsoft.com/kb/919529) The commands you want are as follows: FIXBOOT
is the best choice, ever [1]. There are cases where RAID0 is mathematically proven more reliable than RAID5 [2]. RAID5 should never be used for anything where you value keeping your data. I am not exaggerating when I say that very often, your data is safer on a single hard drive than it is on a RAID5 array. Please let that sink in.The problem is that once a drive fails, during the rebuild, if any of the surviving drives experience an unrecoverable read error (URE), the entire array will fail. On consumer-grade SATA drives that have a URE rate of 1 in 10^14, that means if the data on the surviving drives totals 12TB, the probability of the array failing rebuild is close to 100%. Enterprise SAS drives are typically rated 1 URE in 10^15, so you improve your chances ten-fold. Still an avoidable risk.RAID6 suffers from the same fundamental flaw as RAID5, but the probability of complete array failure is pushed back one level, making RAID6 with enterprise SAS drives possibly acceptable in some cases, for now (until hard drive capacities get larger).I no longer use parity RAID. Always RAID10 [3]. If a customer insists on RAID5, I tell them they can hire someone else, and I am prepared to walk away.I haven't even touched on the ridiculous cases where it takes RAID5 arrays weeks or months to rebuild, while an entire company limps inefficiently along. When productivity suffers company-wide, the decision makers wish they had paid the tiny price for a few extra disks to do RAID10.In the article, he has 12x 4TB drives. Once two drives failed, assuming he is using enterprise drives (Dell calls them "near-line SAS", just an enterprise SATA), there is a 33% chance the entire array fails if he tries to rebuild. If the drives are plain SATA, there is almost no chance the array completes a rebuild.[1] http://www.smbitjournal.com/2012/11/choosing-a-raid-level-by...[2] http://www.smbitjournal.com/2012/05/when-no-redundancy-is-mo...[3] http://www.smbitjournal.com/2012/11/one-big-raid-10-a-new-st... Twirrim 756 days ago Note that the 10^14 figure is only what the HDD mfgs publish, and it has been the same for something like a decade. It's a nice,