It was network not storage, when you say boot into repair, are you referring to from the DVD?, because when I tried the repair option from the "Choose an option" Screen it did nothing but bring me back to the "choose an option" screen
From: [email protected] To: [email protected] Subject: RE: [NTSysADM] windows 2012 stuck in repair loop-Update Date: Mon, 19 Jan 2015 03:50:42 +0000 You updated drivers (did that include mass storage controller drivers?). Seems that the logical process would be to boot into repair mode, and replace the drivers you installed with the previous working version. It’s hardware related, but I doubt it’s a hardware failure. From: [email protected] [mailto:[email protected]] On Behalf Of J- P Sent: Monday, 19 January 2015 2:44 PM To: [email protected] Subject: RE: [NTSysADM] windows 2012 stuck in repair loop-Update My only concern is if they bring up something hardware related (which clearly is not the case since the windows installation is acknowledged), I wont be able to get any dell support till Monday. Date: Sun, 18 Jan 2015 22:31:42 -0500 Subject: Re: [NTSysADM] windows 2012 stuck in repair loop-Update From: [email protected] To: [email protected] No need to wait until the AM. They'll take your $500 any time day or night. On Sun, Jan 18, 2015 at 9:47 PM, J- P <[email protected]> wrote: I found it odd that a "Livecd" from DELL , designed for servers wouldnt include the package to read NTFS, anyhow I'm not even going that route now, because even if i can mount it, they dont even have the necessary storage for me to copy all the VHD files over to. It looks like I'll be calling PSS in the AM to fix this problem, I sincerely hope that now that they're banging us for 500 dollars they can at least get it done quickly. Thanks for the feedback all From: [email protected] Date: Sun, 18 Jan 2015 18:24:55 -0800 Subject: Re: [NTSysADM] windows 2012 stuck in repair loop-Update To: [email protected] On Sun, Jan 18, 2015 at 5:34 PM, J- P <[email protected]> wrote: unknown filesystem type "NTFS" Have you verified the NTFS filesystem package? Sounds like it needs to be repaired or reinstalled. -- Espi
