Re: Changing boot disk interface
From: Les Connor (les.connor_at_DEL.cfive.ca)
Date: 09/29/04
- Next message: Fisheye: "Re: Download"
- Previous message: Marina Roos [SBS-MVP]: "Re: Migrated SBS 2K3 network connectivity issues"
- In reply to: Timothy Morris: "Re: Changing boot disk interface"
- Next in thread: Timothy Morris: "Re: Changing boot disk interface"
- Reply: Timothy Morris: "Re: Changing boot disk interface"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 29 Sep 2004 17:24:00 -0500
I thought I'd made another reply to this thread, did I get that one in the
wrong place too ;-/ ?
All of the disk controllers are in the box now, right? So, the drivers are
already present.
So, you image the current installation to USB or whatever, re-configure your
box and set the bios to boot of the 'new' drive, restore the image and you
should be OK.
It seems to me I'm missing a step here.
But Setup/repair will bail you out if nobody corrects me. The repair keeps
your existing installation, just sorts out any hardware issues. So long as
you don't mess with the NICs.
But you'll likely need to reactivate immediately, so have a phone handy.
-- Les Connor [SBS Community Member] ------------------------------------- SBS Rocks ! "Timothy Morris" <tim@online.kingswoodhouse.e7even.com> wrote in message news:ORbbpEnpEHA.3640@tk2msftngp13.phx.gbl... > That seems to make sense Les and thanks for sticking with it, we seem to > be > stuck in the corner of a very quiet room! > > Will the repair phase leave sbs in otherwise the same state as before? I'm > waiting for a replacement graphics card to arrive from a DAO one I RMA'd > two > weeks ago, and then I can try it on a useless box first. > > Tim > "Les Connor" <les.connor@DEL.cfive.ca> wrote in message > news:O9pCXecpEHA.3500@TK2MSFTNGP15.phx.gbl... >> Hi Tim, >> >> I think my first post was meant for another thread, and then I continued >> down this wrong path with a reply, sorry. Somebody had a boot problem, >> I'll go look for that thread ;-/. >> >> Regarding your issue, there is almost certainly a more elegant solution >> than this, but you can boot from the W2k3 disk and run setup, either >> providing your driver with the F6, or go through to the 'repair' option >> and it's quite possible windows will provide a native driver in the >> hardware detection phase. >> >> -- >> Les Connor [SBS Community Member] >> ------------------------------------- >> SBS Rocks ! >> >> >> >> "Timothy Morris" <tim@online.kingswoodhouse.e7even.com> wrote in message >> news:es7VRVXpEHA.3392@TK2MSFTNGP15.phx.gbl... >>>I haven't even started yet, I'm only at the planning stage! >>> >>> I know from prior experience of using SCSI disks that if you want to >>> boot >>> from a controller which isn't ATA windows needs to know what the driver >>> is. With Windows 2000 you used to have to rename the driver ntbootdd.sys >>> otherwise when booting you'd go through the BIOS screen and the initial >>> load routine, and as soon as the system started loading device drivers >>> it >>> would throw up a STOP 0x7B blue screen error as detailed in the >>> following >>> knowledgebase article: >>> >>> http://support.microsoft.com/default.aspx?scid=kb;en-us;122926&Product=win2000 >>> >>> I'm sure Win 2003 will suffer from a similar problem, I'm just trying to >>> head it off at the pass. I've got a spare PC for "lab testing" if it >>> comes to it I can try it out on that first. >>> >>> Tim >>> "Les Connor" <les.connor@DEL.cfive.ca> wrote in message >>> news:%23HrWUFWpEHA.324@TK2MSFTNGP11.phx.gbl... >>>> The disks surely can be seen prior to the OS loading, not? If not, then >>>> you have to correct that. >>>> >>>> First check the boot order in the bios and make sure it's looking to >>>> the >>>> correct controller. If changes were made in Disk Managment (such as >>>> boot >>>> disk not active) then booting from the floppy should enable you to >>>> correct this. >>>> >>>> The drivers you speak of are for Windows, and you're not getting that >>>> far. >>>> >>>> -- >>>> Les Connor [SBS Community Member] >>>> ------------------------------------- >>>> SBS Rocks ! >>>> >>>> >>>> >>>> "Timothy Morris" <tim@online.kingswoodhouse.e7even.com> wrote in >>>> message >>>> news:uNfkKsTpEHA.3896@TK2MSFTNGP15.phx.gbl... >>>>> What about the fact that the disks are on a different controller which >>>>> requires a device driver - something along the lines of ntbootdd.sys? >>>>> That's really what I'm getting at. >>>>> >>>>> Tim >>>>> >>>>> "Les Connor" <les.connor@DEL.cfive.ca> wrote in message >>>>> news:eIomtENpEHA.2304@TK2MSFTNGP14.phx.gbl... >>>>>>I think you can create a boot disk on an xp box. It needs fdisk on it. >>>>>>Boot from the floppy and run fdisk to mark the correct partition as >>>>>>active, and it should boot up. >>>>>> >>>>>> -- >>>>>> Les Connor [SBS Community Member] >>>>>> ------------------------------------- >>>>>> SBS Rocks ! >>>>>> >>>>>> >>>>>> >>>>>> "Timothy Morris" <tim@online.kingswoodhouse.e7even.com> wrote in >>>>>> message news:uxo$5yMpEHA.3464@tk2msftngp13.phx.gbl... >>>>>>> Can no-one shed any light on this? >>>>>>> >>>>>>> Tim >>>>>>> >>>>>>> "Timothy Morris" <tim@online.kingswoodhouse.e7even.com> wrote in >>>>>>> message news:uQjBJ6loEHA.556@tk2msftngp13.phx.gbl... >>>>>>>> Disk 0 (C: D: and E:) on the ATA 133 interface replaced by hardware >>>>>>>> RAID0 >>>>>>>> 120Gb striped set (2 60Gb SATA disks) >>>>>>>> >>>>>>>> The exisiting software raid striped set will remain intact as disks >>>>>>>> 1 to 3 >>>>>>>> on the mainboard's ATA interface. >>>>>>>> >>>>>>>> Tim >>>>>>>> >>>>>>>> "Les Connor" <les.connor@DEL.cfive.ca> wrote in message >>>>>>>> news:ejk%23WxjoEHA.1176@TK2MSFTNGP12.phx.gbl... >>>>>>>>> I'm not clear on what your disk configuration would look like >>>>>>>>> afterwards, >>>>>>>>> i.e. what the objective is. >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Les Connor [SBS Community Member] >>>>>>>>> ------------------------------------- >>>>>>>>> SBS Rocks ! >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> "Timothy Morris" <tim@online.kingswoodhouse.e7even.com> wrote in >>>>>>>>> message >>>>>>>>> news:epJ49$boEHA.3324@TK2MSFTNGP15.phx.gbl... >>>>>>>>> >I currently have 4 ATA-133 disks in my server >>>>>>>>> > >>>>>>>>> > Disk 0 - 120Gb in 3 equal partitions: >>>>>>>>> > >>>>>>>>> > C: System and Boot partition >>>>>>>>> > D: Install disks - contents of SBS plus anti-virus software etc. >>>>>>>> including >>>>>>>>> > the ClientApps folder >>>>>>>>> > E: Volume Shadow copies >>>>>>>>> > >>>>>>>>> > Disks 1,2, and 3 all 120Gb Striped (software) Raid0 partition >>>>>>>>> > (F:) >>>>>>>>> > containing Users Shared Folders and MDBDATA. >>>>>>>>> > >>>>>>>>> > My mainboard (Nforce NF 2.0) board has 2 SATA connections which >>>>>>>>> > can be >>>>>>>>> > configured as a hardware Raid 0 set. I've bought 2 60Gb SATA >>>>>>>>> > disks >>>>>>>>> > >>>>>>>>> > I have a copy of Norton Ghost and a 500Gb USB 2.0 disk. I know >>>>>>>>> > that if I >>>>>>>>> > just ghost the partitions across I will get a blue-screen >>>>>>>>> > "inaccessible >>>>>>>>> > boot disk" error. I have an up to date SATA drivers disk. What >>>>>>>>> > do >>>>>>>>> > I have >>>>>>>>> > to do in order to boot successfully? >>>>>>>>> > >>>>>>>>> > I'd also like to resize the partitions to say 20/20/80Gb, any >>>>>>>>> > advice as >>>>>>>> to >>>>>>>>> > how to go about this? >>>>>>>>> > >>>>>>>>> > Tim >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > > >
- Next message: Fisheye: "Re: Download"
- Previous message: Marina Roos [SBS-MVP]: "Re: Migrated SBS 2K3 network connectivity issues"
- In reply to: Timothy Morris: "Re: Changing boot disk interface"
- Next in thread: Timothy Morris: "Re: Changing boot disk interface"
- Reply: Timothy Morris: "Re: Changing boot disk interface"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
