ProLiant Servers (ML,DL,SL)
1819686 Members
3397 Online
109605 Solutions
New Discussion

HPE DL380 Gen10 Windows Server 2016 Boot USB or DVD/ISO With RAID Drivers

 
gmsui
Visitor

HPE DL380 Gen10 Windows Server 2016 Boot USB or DVD/ISO With RAID Drivers

Hello community.  Is there a way to create a bootable USB or DVD/ISO from the boot partition (C:) of a functioning Windows Server 2016 running on a DL380 Gen10 with RAID configuration?  I need to boot from a source that has all the HPE drivers loaded so that I can access the C: and (OS and data) partitions of an existing RAID array.  Booting off a Windows Server 2016 installation ISO does not help because it does not load RAID drivers, therefore the C: and drives are not visible.  Thank you.

3 REPLIES 3
support_s
System Recommended

Query: HPE DL380 Gen10 Windows Server 2016 Boot USB or DVD/ISO With RAID Drivers

System recommended content:

1. HPE ProLiant DL380 Gen10 Plus Server - Option Parts | Factory Integratable Options

2. HPE ProLiant DL380 Gen10 Plus Server - Overview

 

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

 

Thank you for being a HPE valuable community member.


Accept or Kudo

Cali
Honored Contributor

Re: HPE DL380 Gen10 Windows Server 2016 Boot USB or DVD/ISO With RAID Drivers

Hi,

I'm sure, you use Backup Software for your Server.

Most Backup Software (such as Veeam) provides the ability to create a Recovery Media from the last Full Backup.

I would try this because it is the easy way for creation and also recovery.

Cali

 

ACP IT Solutions AGI'm not an HPE employee, so I can be wrong.
gmsui
Visitor

Re: HPE DL380 Gen10 Windows Server 2016 Boot USB or DVD/ISO With RAID Drivers

@Cali Thank you Cali for the reply.  The physical server at issue and others like it are backed up with Microsoft Azure Recovery Services.  Unfortunately I don't see recovery media as an option with MARS and Windows Server Backup.  But, we do have Veeam as an option now, so taking your suggestion, I can try a Veeam backup of one of the healthy servers, create its recovery media, and try it as the boot media for the problem server.  Your suggestion is much appreciated.