Is disconnecting data drives still a thing when fresh installing Windows?

[Salty Wagyu]

I followed some old advice to disconnect any data drives and leave the OS drive intact when reinstalling Windows, otherwise odd things might happen? I think I had my own experience of the System Reserved partition getting written to another drive or a boot order got messed up, can't really remember now. But to this day I've always disconnected non-relevant drives before an OS install on any PCs I work on.

 

Do any of you still do the same?

[goretsky Supervisor]

Hello,

 

I do the same, just to prevent the boot record from being written to the wrong drive.  I can't recall it ever being a problem, but it is only a minute's worth of work for me to open a computer and disconnect the other drives before installing Windows, then plug them back in when the installation is finished.

 

 

Regards,

 

Aryeh Goretsky

 

[DKAngel]

yeah im the same, new installs i plug all the data drives after the os install, had it happen to many times where ive gone to remove a drive and nothing boots up properly anymore

[adrynalyne]

I just disable the drive(s) in the bios/uefi, install, then turn it back on.  

[Radium]

  On 22/05/2018 at 10:35, adrynalyne said:

I just disable the drive(s) in the bios/uefi, install, then turn it back on.  

Expand  

Do you mean that you disable the drives at the controller level or the whole controller instead of unplugging them?

What if you disable the wrong drive/controller??

[+Warwagon MVC]

Ya, it just makes sure you don't nuke the wrong drive during install.

[Mando]

eh, only if your extremely daft and cant read or pay no attention to what you click, never in 25yr of working in IT have I ever disconnected data drives...wtf thats what DR backups are for :P 

 

classic urban legend imo.

[Sulphy]

I have an M.2 as OS drive, and 4 SSD's for data... seems when installing windows from fresh.. after first reboot, i have issues. So i unplug all SSD's, and only run off my M.2 until i have the OS somewhat setup... then plug the rest back in again. its a pain! never had that issue back in the days of pre M.2..

[Mando]

  On 22/05/2018 at 14:38, Sulphy said:

I have an M.2 as OS drive, and 4 SSD's for data... seems when installing windows from fresh.. after first reboot, i have issues. So i unplug all SSD's, and only run off my M.2 until i have the OS somewhat setup... then plug the rest back in again. its a pain! never had that issue back in the days of pre M.2..

Expand  

thats a W10/Ms issue with M2 drives, Win10 insists on being installed on Device 0 M2 slots usually take over the IRQs of SATA-0 and SATA-1 (or share )

[adrynalyne]

  On 22/05/2018 at 12:45, Radium said:

Do you mean that you disable the drives at the controller level or the whole controller instead of unplugging them?

What if you disable the wrong drive/controller??

Expand  

I disable the drive at the controller level. I know what my drive internal names are so it’s easy to differentiate. And in the unlikely event that I disable the wrong one, it’s not much effort to go back into the settings and rectify the issue. It’s quicker and easier than cracking open my case which requires no less than four thumb screws to remove a side. 

 

The only time it might be an issue is if it’s one of my two nvme drives but since I dual boot with incompatible filesystems, it ends up not being an issue. 

[Jason S. Global Moderator]

during install, select Custom, choose the drive on which you want Windows installed. is this what we're talking about? i dont see a reason to disconnect drives.

[+Nik Louch Subscriber²]

I hosed a drive once.  Managed to get a lot of it back as I realised pretty quickly, but a simple error really caused me a load of grief.  So now, yeah.

[adrynalyne]

  On 22/05/2018 at 15:12, Jason S. said:

during install, select Custom, choose the drive on which you want Windows installed. is this what we're talking about? i dont see a reason to disconnect drives.

Expand  

Windows arbitrarily decides where it wants to put the boot files, etc. (especially when you repartition drive or format it beforehand) that includes a hidden partition. Now imagine that being on a data drive and you decide to swap it out one day or format it.  

 

You dont boot anymore in the first instance and you can’t in the second. This can be fixed after the fact but it’s not fun, so this is preventative action. 

[Jason S. Global Moderator]

  On 22/05/2018 at 15:24, adrynalyne said:

Windows arbitrarily decides where it wants to put the boot files, etc. (especially when you repartition drive or format it beforehand) that includes a hidden partition. Now imagine that being on a data drive and you decide to swap it out one day or format it.  

 

You dont boot anymore in the first instance and you can’t in the second. This can be fixed after the fact but it’s not fun, so this is preventative action. 

Expand  

interesting. i guess i never knew that.

[Mando]

  On 22/05/2018 at 15:24, adrynalyne said:

Windows arbitrarily decides where it wants to put the boot files, etc. (especially when you repartition drive or format it beforehand) that includes a hidden partition. Now imagine that being on a data drive and you decide to swap it out one day or format it.  

 

You dont boot anymore in the first instance and you can’t in the second. This can be fixed after the fact but it’s not fun, so this is preventative action. 

Expand  

Aint that caused by not following Microsofts guidance of partitioning the drives in Win setup, which actually causes this scenario Ive never had the instance where windows has ever put the bootloader or hidden partition on other drives, other than primary device0, but i always nuke partitions in winsetup (NT4 onwards). I do the same setting up win servers (as well as under provisioning on the OS vol).

 

ofc though dual booting adds a layer of complexity to the rule.

[adrynalyne]

  On 22/05/2018 at 16:38, Mando said:

Aint that caused by not following Microsofts guidance of partitioning the drives in Win setup, which actually causes this scenario Ive never had the instance where windows has ever put the bootloader or hidden partition on other drives, other than primary device0, but i always nuke partitions in winsetup (NT4 onwards). I do the same setting up win servers (as well as under provisioning on the OS vol).

 

ofc though dual booting adds a layer of complexity to the rule.

Expand  

Nah it happens if you partition during windows setup too sometimes. 

[d5aqoëp]

ASUS, GIGABYTE bios allow to disable SATA controllers individually. MSI doesn’t. You cannot disable M.2 NVMe drives. 

 

Sometimes disconnecting/removing is the only option especially if one is using a third party bootloader like Clover to dual/triple boot Windows/Linux/macOS on the same computer. I know I do.

[adrynalyne]

  On 22/05/2018 at 16:55, d5aqoëp said:

ASUS, GIGABYTE bios allow to disable SATA controllers individually. MSI doesn’t. You cannot disable M.2 NVMe drives. 

 

Sometimes disconnecting/removing is the only option especially if one is using a third party bootloader like Clover to dual/triple boot Windows/Linux/macOS on the same computer. I know I do.

Expand  

I don’t have any problems with Clover with this though I imagine it’s due to me having my drives separate and not using multiple OSes on the same drive. 

[Mando]

  On 22/05/2018 at 16:50, adrynalyne said:

Nah it happens if you partition during windows setup too sometimes. 

Expand  

Really? Ive never personally experienced it mate (maybe W98 and SATA introduction era), that doesnt mean it doesnt happen these days ofc rejoicing at Abit IC7 with Marvel SATA2 ports! omg!

These days at home, i always nuke the volumes via iRST in bios and rebuild my new volumes (2 ssd stripe set and 4 ssd striped set) so i can set them up as GPT for full secure boot.

 

I never professionally depend on data on any drive in a build, so even if i did bork both disks, id restore from the backup anyways regardless on fresh volumes.

[Som]

i've never disconnected a drive for a fresh install

[adrynalyne]

  On 22/05/2018 at 17:14, Mando said:

Really? Ive never personally experienced it mate (maybe W98 and SATA introduction era), that doesnt mean it doesnt happen these days ofc rejoicing at Abit IC7 with Marvel SATA2 ports! omg!

These days at home, i always nuke the volumes via iRST in bios and rebuild my new volumes (2 ssd stripe set and 4 ssd striped set) so i can set them up as GPT for full secure boot.

 

I never professionally depend on data on any drive in a build, so even if i did bork both disks, id restore from the backup anyways regardless on fresh volumes.

Expand  

Oh I’m not worried about data; I just want my drives properly segregated at all times. 

[goretsky Supervisor]

Hello,

 

I've had it happen, back when I was starting to migrate from SCSI HDDs to SATA SSDs.  I switched from booting off of SCSI HDD's to booting from SATA SSD's, and ended up with the boot record on the HDD loading the operating system kernel from from the SSD.  Everything worked fine until I removed the HDDs, at which point the systems would no longer boot.  Easily fixable from the troubleshooter on Windows installation , but rather annoying to deal with at the time.

 

Regards,

 

Aryeh Goretsky

 

  On 22/05/2018 at 13:47, Mando said:

eh, only if your extremely daft and cant read or pay no attention to what you click, never in 25yr of working in IT have I ever disconnected data drives...wtf thats what DR backups are for :P 

 

classic urban legend imo.

Expand  

 

[Michael Scrip]

I used to physically disconnect all my data drive when I did a fresh install... mostly out of paranoia.

 

But it's pretty easy to find my 128GB boot SSD in a sea of 1TB data HDDs...

 

I shouldn't mistakenly install an OS on the wrong drive... at least I hope I don't!

[adrynalyne]

  On 24/05/2018 at 08:19, Michael Scrip said:

I used to physically disconnect all my data drive when I did a fresh install... mostly out of paranoia.

 

But it's pretty easy to find my 128GB boot SSD in a sea of 1TB data HDDs...

 

I shouldn't mistakenly install an OS on the wrong drive... at least I hope I don't!

Expand  

It’s not about mistakenly installing the os to the wrong drive. The bigger issue is that Windows decides where to put the bootloader and associated files, not the user. 

[Michael Scrip]

  On 24/05/2018 at 14:20, adrynalyne said:

It’s not about mistakenly installing the os to the wrong drive. The bigger issue is that Windows decides where to put the bootloader and associated files, not the user. 

Expand  

I see.

 

But even then.... nothing fishy has happened to me so far.

 

Fingers crossed!