Jump to content











Photo
- - - - -

Boot with Grub4Dos from M2 NVMe SSD to RAM

grub4dos m2 nvme

  • Please log in to reply
8 replies to this topic

#1 dogar

dogar
  • Members
  • 2 posts
  •  
    Germany

Posted 19 July 2017 - 11:56 AM

Hello,
i am using a computer with Gigabyte motherboard GA-X99-Ultra Gaming,
AMI UEFI BIOS, RAM is 64 GB
W7 Ultimate is installed on 50 GB VHD
I boot mit grub4dos VHD in RAM:
 
find --set-root /W7.vhd
map --mem (hd1,0)/w7.vhd (hd0)
map --hook
root (hd0,0)
chainloader /bootmgr
 
If i boot 50 GB VHD from Samsung SSD 850 PRO on SATA controller it takes 2 min 30 sec.
 
I want to get it quicker and put VHD on Samsung M2 SM951 NVMe SSD (uses 4 PCIe 3.0 lanes).
But this load takes 10 min !!!
 
How can i get it quicker? Must i install any modules in UEFI BIOS?
Is es any other tool to load VHD in RAM Disk und to start it?
 
Please help me
Thanks


#2 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13647 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 19 July 2017 - 12:28 PM

Don't use --mem mapping, it will be faster.

 

 

:duff:

Wonko



#3 agni

agni

    Frequent Member

  • Tutorial Writer
  • 256 posts
  • Location:Bengaluru (Bangalore)
  •  
    India

Posted 20 July 2017 - 05:14 AM

I think he wants to Run Windows 7 from RAM. Without the --mem mapping, how will it be running from RAM?



#4 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13647 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 20 July 2017 - 07:43 AM

I think he wants to Run Windows 7 from RAM. Without the --mem mapping, how will it be running from RAM?

Your crystal ball is probably better tuned then mine :dubbio:, but if he wants to Run Windows 7 in RAM, how will it be running from RAM without giving it the time to be loaded in RAM?

 

2:30 doesn't seem to me like an "absurd" time, given that 50 GB VHD needs to be copied to RAM and 30/40/50 seconds are needed to boot 7 anyway, I believe.

 

The 50 Gb is an enormous size, particularly for running it in RAM, using a smaller sized VHD will do miracles if --mem is used.

 

Also it sounds like he is using "native" Windows7 VHD booting, that I doubt (but I may well be wrong on this :unsure:) actually runs the VHD in RAM.

 

:duff:

Wonko



#5 dogar

dogar
  • Members
  • 2 posts
  •  
    Germany

Posted 4 weeks ago

Yes, i want to run W7 from RAM
 
BIOS -> Grub4Dos -> map VHD from SSD to RAM Disk -> start OS
 
It works very well on my old system (X58, with 24 GB RAM, 18 GB VHD load from per jumper write protected SCSI HDD to RAM Disk).
 
The old system was too small, thats why i build a new system.
I think that map 50 GB from SATA3 SSD in 2,5 min ist fastest possible speed for  SATA3.
Thats why i try now mit M2 NVMe SSD with 4 PCIe 3.0 lanes. It 'must' work with 8 GBit pro lane.
 
My problem is: how can i map 50 GB VHD from M2 NVMe SSD to RAM Disk with maximal speed.
(install extra modules to UEFI BIOS, another tool as Grub4Dos, ...) ???
I map to RAM also W10, but from .IMG file.
Hier i install W10 on 50 GB primary partition, then from Linux make 'dd if=hd(0,1) of=c:\w10.img'
All this works very good. The only problem is to make map from ssd to ram quicker...


#6 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13647 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 4 weeks ago

Use "not" such a BIG image.

 

Use a smaller "system" image and if you really-really need extra space use another image mounted in a Ramdisk later, either using another driver or using a mountpoint.

 

I am still perplexed by the "Ramdisk" part :unsure:, AFAIK the "native" VHD booting cannot/doesn't "hook" a grub4dos mem mapped image, (you normally use WinVblock or Firadisk as Ramdisk when you use gru4dos mapping).

 

Are you sure that the system is entirely "volatile"? :dubbio:

 

There is no way that I know of to speed up data transfer without *somehow* rewriting the grub4dos code that does the transfer, maybe it is faster on the "normal" SATA channel than it is on the PCIe (for *whatever* reasons).

 

Or - maybe - for your use a "truncated" image might do:

http://reboot.pro/to...n-many-ramdisk/

 

:duff:

Wonko



#7 RoyM

RoyM

    Frequent Member

  • .script developer
  • 415 posts
  • Interests:"Booting and Owning".
  •  
    United States

Posted 4 weeks ago

# UEFI won't work with G4D, without appropriate settings.
# You Must use G4D newest version for this to work.
# (USE) usb --init, it may take a while, but once it's loaded, .iso will take half the time to load.
# This uses G4D's built-in USB Drivers.
 
usb --init
find --set-root /W7.vhd
map (hd1,0)/w7.vhd (hd0)
map --hook
root (hd0,0)
chainloader /bootmgr
 
And Yes, 50G will take 'some' time to load, 'slim it down'.
If this doesn't do it, I would suspect a driver issue.
 
Regards
RoyM


#8 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13647 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 4 weeks ago

 

# UEFI won't work with G4D, without appropriate settings.
# You Must use G4D newest version for this to work.
# (USE) usb --init, it may take a while, but once it's loaded, .iso will take half the time to load.
# This uses G4D's built-in USB Drivers.
 

@RoyM

 There is NO evidence of an ISO nor of USB involved in the OP.

 

:duff:

Wonko



#9 RoyM

RoyM

    Frequent Member

  • .script developer
  • 415 posts
  • Interests:"Booting and Owning".
  •  
    United States

Posted 4 weeks ago

Whoops, My Bad.







Also tagged with one or more of these keywords: grub4dos, m2, nvme

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users