Disk Read Error On Boot Up Windows 2003
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: "A disk read error
Disk Read Error On Boot Up Windows Xp
occurred. Press CTRL+ALT+DEL to restart" after WDS image deployment Windows Server > disk read error on boot up windows 7 Setup Deployment Question 0 Sign in to vote Hello,I have read through the other forums on this error a disk read error occurred windows 7 usb boot and am yet to find a response in which is related to my issue. Most of the posts I had read in which this error occured were sudden happening on
Disk Read Error On Startup Windows 7
their machines. My issue is slightly different: I have a classroom full of 18 HP Compaq dc5700 Small Form Factor pcs. My objective is to reimage the machines in which would be done via WDS server. To get to the point of my problem (I can get into further detail if needed to on response), I took one of the machines
Windows A Disk Read Error Occurred Press Ctrl+alt+del To Restart
from the classroom and re-formatted it via Windows XP SP2 CD and made my image on this machine(including adobe's, antivirus, etc...). Once the image was made I captured it to my WDS server successfully and got everything set up to deploy. I had begun to deploy the image on the other machines and all went smoothly. I had noticed how these machines had the HP Recovery Partition along with the main Partition and unallocated space while selecting the area of the hardrive for WDS to deploy to (within the deployment steps). An example of this step can be found here. I then deleted each of the partition such as what I had done on past bench pcs using WDS so that I was left with my 74.5 GB of unallocated space. I installed the image in this unallocated space and when the computer had rebooted after the deployment finished I first got the following error: "Warning: Your system recovery partition was removed. Press F10 to start the system recovery anyway or another Key to delete the recovery partition". So, I tried pre
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange a disk read error occurred windows 7 fix Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語
A Disk Read Error Occurred Windows 7 Laptop
한국어 Português Español USA Site: Veritas Veritas PartnerNet An error message "A disk read error occurred" may occur at a disk read error occurred windows 10 boot up soon after LightOut restore option is installed. Article:000008561 Publish: Article URL:http://www.veritas.com/docs/000008561 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! https://social.technet.microsoft.com/Forums/windowsserver/en-US/c6ec37a1-4ab3-4f7b-b079-f132ca4ae078/a-disk-read-error-occurred-press-ctrlaltdel-to-restart-after-wds-image-deployment?forum=winserversetup Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem An error message “A disk read error occurred” may occur at boot up soon after LightOut restore option is installed. Error Message A disk read error occurred Press https://www.veritas.com/support/en_US/article.000008561 Ctrl+Alt+Del to restart Cause Master Boot Record (MBR) may be damaged. Solution 1) Repair MBR and reboot the machine. a) In case of Windows 2003, run a command “FIXMBR” in Recovery Console. b) In case of Windows 2008, run a command “BOOTREC /FIXMBR” in System Recovery Environment. Terms of use for this information are found in Legal Notices.
Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? No Yes Did this article save you the trouble of contacting technical support? No Yes How can we make this article more helpful? Email Address (Optional) Your feedback has been submitted successfully! Thank You! Sorry, we couldn't post your feedback right nStart 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 Overflow the company Business Learn more about hiring developers or posting http://serverfault.com/questions/277560/disk-read-error-after-converting-basic-disk-to-dynamic-disk ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask http://blogs.msmvps.com/steveb/2007/01/19/a-disk-read-error-occurred-press-ctrl-alt-del-to-restart-not-what-i-wanted-to-see-tonight/ a question Anybody can answer The best answers are voted up and rise to the top Disk read error after converting basic disk to dynamic disk? up vote 0 down vote favorite I have a bit of an odd setup. Basically, originally disk read in the server was an older lone 160G harddrive. We've decided to upgrade it to a RAID-1 mirrored 2 disk setup against two new 500G harddrives. It'd save a lot of time if we didn't have to reinstall server, so I decided I'd give cloning the disk a try. I can successfully clone it (manually using dd from an OpenBSD install disk). It works after that, but it has over 300G of unallocated space. I wanted it to just be one big parition, disk read error so I used GParted to resize the parition. It works after this, chkdisk runs without any kind of errors and such. Then, when I try setting up this one drive to be a dynamic disk, it will say it must unmount and reboot the computer and such. Consistently, however, when it reboots I just get the error "A disk read error occurred. Press CTRL-ALT-DEL to restart" or something along those lines. I've tried this 3 times, with the same thing each time. Also, I'm aware of the needed 10M of unallocated space on the drive. I went ahead and left 100M just to be safe. Is there anything obvious that would cause converting a perfectly fine basic disk to a dynamic disk to fail? Also, I am using Windows Server 2003 Standard edition, 32 bit windows-server-2003 raid hard-drive dynamic-disk share|improve this question asked Jun 6 '11 at 18:57 Earlz 5025824 add a comment| 2 Answers 2 active oldest votes up vote 0 down vote I had the same issue about 3 months ago - convert drive to dynamic rendered the drive unreadable. To fix this, I booted to a Win2008 server with the drive in another bay, and then used a hex editor to change the dynamic bit. I followed these instructions: http://thelazyadmin.com/blogs/thelazyadmin/archive/2007/01/17/Converting-Dynamic-Disks-Back-to-Basic-Disks.aspx This will revert your disk to basic, but it will be usable. share|improve this answer answered Jun 9 '11 at 13:54 charnley 512312 add a comment| up vote 0 down vote I worked around this pro
Firmware update does not work with Windows Vista - use XP → A disk read error occurred Press Ctrl+Alt+Del to restart - not what I wanted to see tonight. Posted on January 19, 2007 by steveb Once again the external USB drive strikes again! I tell you, they are a blessing and a curse. Ran Microsoft Updates on a customer SBS 2003 SP1 Server via RDP session. On restart it decided to not run IIS or TS services, something that seems to be occurring a lot lately on different boxes after updates. So I fired up a PPTP VPN to the server logging in as the admin of the customer’s domain. Successfully establishing the VPN connection I then started a command session in Vista on my Tablet PC running as administrator. From there I launched a shutdown – i command and brought up the shutdown GUI interface. Using the NetBIOS name of the server I was able to do a remote restart of the SBS box. This has been a trick I have been using since my company’s own SBS box decided not to launch TS when I was applying updates while sitting in a classroom in Las Colinas, Texas with the PSS team this last summer. This was the second machine of the night last night to have behaved this way after updates. Problem was that unlike the other server last night that came back online after the remote restart through the VPN connection, this server went down and then stayed down. Not what I was wanting to see. I fired off the flares to the business owners of the now offline server to power-cycle it in the morning when they arrived in the office to bring it back on its feet. Unfortunately for all of us, they tried it and it didn’t help. The Small Business Server was down for the count. I came into the customer’s office, attached a monitor to the normally headless SBS box to find the following: A disk read error occurred Press Ctrl+Alt+Del to restart This was not what I wanted to be reading. Okay, time for a call to Server Down Support at Microsoft. With PSS tech Uday Godbole on the line, I tossed in the Windows Small Business Server 2003 Disc 1 and headed for the recovery console. What I found there was that the Windows directory was now D:\Windows instead of C:\Windows! Not cool. Changed the drive to C: to find its name as IOMEGA_HDD. Now we had something to work with. Pulled both external USB drives that were attached to the back of the HP ML150 and exited the recovery console. On restart the server fired right up into Windows. On a side note, Microsoft's Uday did a great job on the call. He was referring to past cases as to possible causes and thought of the recovery console which I hadn't gone to yet. I was thinking of runn