H
htruempler
Neuer Benutzer
Threadstarter
- Dabei seit
- 30.07.2015
- Beiträge
- 18
- Version
- Pro
Hallo zusammen, kann mir jemand eine fachlich kompetente Hilfestellung geben, bei folgendem Problem. (Kurzbeschreibung in Englisch, weil parallel vorher ohne Erfolg im HP-Support Forum gepostet, dort hat man definitiv kein Interesse):
"
Short Description Problem Case:
1. OS W10 PRO 64 bit installed on SATA-SSD (Samsung EVO 850, SATA 6GB/Interface, AHCI Protocol. Huge Software-Installation, everything works 100% reliable. W10 new Installation from Scratch to much work/effort.
2. HP Z420 WS, AMI BIOS, Intel C600/X79 Chipset, 4 Core Xeon Processor E5-1603 @ 2.80GHZ
3. BIOS Flashing regularly procedure OK, latest BIOS: J61_0394 flashed. Mods BIOS Flashing (NVMe Insert) not possible for sure, because of HP/AMI integrated strong Checksum protection (Enterprise use of HP WS).
4. Bought an EVO 970 M.2 NVMe SSD, installed it on a DeLOCK M.2 NVMe PCIe x4 Apatper. Build in a free PCIe Slot x4. EVO 970 recognised at W10 OS level as a data storage device. Automatically Microsoft NVMe Driver installation, in addition manual installation of Samsung EVO NVMe Driver. Benchmark at Samsung MAGICIAN Controller-Software, seq. read speed EVO 850 app. 500 MB/sec., EVO 970 3.500 MB/sec. (!).
5. 1:1 Clone EVO 850 to EVO 970 NVMe OK via Samsung Data Migration Tool, or Acronis 2019 Clone solution.
6. Using an W10 USB installation Media (Setup via Microsoft Creation tool), new W!0 Installation works without any trouble.
7. Using the in the RAID-Forum mentioned great Clover methodology to boot an NVMe storage device without a mod BIOS Version, even the booting of the fresh installed W10 environment is functionally working, without any problems!
8. As described at “5.”, unfortunately I´m not able to come to the wished stage, to boot the NVMe EVO 970, after cloning the existing W10 on my 850 EVO to the EVO 970 NVMe. The Device is recognised in the Clover Shell, the booting starts with a Microsoft circle symbol, but it then stops, with a blue screen error and the message “can´t find a booting device”.
Although I tried to find a solution description for this case, I´m at the point now, of personally having no ideas know anymore what to do further to cover this final boot problem issue.
"
Wenn ich mit Acronis 2019 ein aktuelles Backup von meiner W10 OS-Partition mache, und diese dann mit Acronis Recovery Media (USB-Stick) via Restore auf die EVO 970 NVMe bringe, wird dort die abweichend von der MBR-Struktur (weil die NCMe wird als solche erkannt) eine GPT-Struktur
"
Short Description Problem Case:
1. OS W10 PRO 64 bit installed on SATA-SSD (Samsung EVO 850, SATA 6GB/Interface, AHCI Protocol. Huge Software-Installation, everything works 100% reliable. W10 new Installation from Scratch to much work/effort.
2. HP Z420 WS, AMI BIOS, Intel C600/X79 Chipset, 4 Core Xeon Processor E5-1603 @ 2.80GHZ
3. BIOS Flashing regularly procedure OK, latest BIOS: J61_0394 flashed. Mods BIOS Flashing (NVMe Insert) not possible for sure, because of HP/AMI integrated strong Checksum protection (Enterprise use of HP WS).
4. Bought an EVO 970 M.2 NVMe SSD, installed it on a DeLOCK M.2 NVMe PCIe x4 Apatper. Build in a free PCIe Slot x4. EVO 970 recognised at W10 OS level as a data storage device. Automatically Microsoft NVMe Driver installation, in addition manual installation of Samsung EVO NVMe Driver. Benchmark at Samsung MAGICIAN Controller-Software, seq. read speed EVO 850 app. 500 MB/sec., EVO 970 3.500 MB/sec. (!).
5. 1:1 Clone EVO 850 to EVO 970 NVMe OK via Samsung Data Migration Tool, or Acronis 2019 Clone solution.
6. Using an W10 USB installation Media (Setup via Microsoft Creation tool), new W!0 Installation works without any trouble.
7. Using the in the RAID-Forum mentioned great Clover methodology to boot an NVMe storage device without a mod BIOS Version, even the booting of the fresh installed W10 environment is functionally working, without any problems!
8. As described at “5.”, unfortunately I´m not able to come to the wished stage, to boot the NVMe EVO 970, after cloning the existing W10 on my 850 EVO to the EVO 970 NVMe. The Device is recognised in the Clover Shell, the booting starts with a Microsoft circle symbol, but it then stops, with a blue screen error and the message “can´t find a booting device”.
Although I tried to find a solution description for this case, I´m at the point now, of personally having no ideas know anymore what to do further to cover this final boot problem issue.
"
Wenn ich mit Acronis 2019 ein aktuelles Backup von meiner W10 OS-Partition mache, und diese dann mit Acronis Recovery Media (USB-Stick) via Restore auf die EVO 970 NVMe bringe, wird dort die abweichend von der MBR-Struktur (weil die NCMe wird als solche erkannt) eine GPT-Struktur