Jump to content











Photo
- - - - -

grub4dos initrd

grub4dos initrd

  • Please log in to reply
11 replies to this topic

#1 ZEE

ZEE

    Member

  • Members
  • 80 posts
  •  
    Portugal

Posted 02 March 2017 - 12:46 AM

I'm trying to solve a recorrent crash booting from PXE+TFTP+wimboot

 

​everything loads ok except when the loaded .wim file ends loading and bootmgr is about to start

​I think some problem can be from initrd (memdisk)

​I'm trying to put the structure in memdisk as it would be in disk

​\bootmgr

​\boot\boot.sdi

​\boot\bcd

​\x.wim

​so my menu.lst contains

​title BootMgr (WimBoot)
    #pxe keep
    kernel /wimboot
    initrd @bootmgr=/boot/bootmgr
    initrd /boot/boot.sdi
    initrd /boot/memdisk
    initrd /boot/bcd
    initrd @x.wim=/{wim}/win10pese32.wim

*​this loads ok and then crashes the test VM/Virtualbox

tested with/without "pxe keep"

​tested with strange syntax like "initrd @/boot/boot.sdi=/boot/boot.sdi" (initrd accepts this)

​tested with bootfiles from Windows 7 and from Windows 10 (problem is exactly the same)

​I don't know how to inspect the memdisk content (initrd container)

If someone has an idea how to do it I'll appreciate  the knowledge...

​?help... please!



#2 ZEE

ZEE

    Member

  • Members
  • 80 posts
  •  
    Portugal

Posted 02 March 2017 - 12:57 AM

This might help...

​​3E7Ueb7q8Iu5.png

3E7WOJTAP8PN.png



#3 tinybit

tinybit

    Gold Member

  • Developer
  • 1051 posts
  •  
    China

Posted 02 March 2017 - 04:08 AM


    initrd @bootmgr=/boot/bootmgr
    initrd /boot/boot.sdi
    initrd /boot/memdisk
    initrd /boot/bcd
    initrd @x.wim=/{wim}/win10pese32.wim

 

I don't think it could work well with so many initrd commands. I mean, only one initrd command should be used. The use of "multiple initrd commands" is wrong, if I am not mistaken.


  • ZEE likes this

#4 steve6375

steve6375

    Platinum Member

  • Developer
  • 6598 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars
  •  
    United Kingdom

Posted 02 March 2017 - 08:29 AM

Yes, it should be all on one line

See example

http://reboot.pro/to...rt/#entry188401


  • ZEE likes this

#5 ZEE

ZEE

    Member

  • Members
  • 80 posts
  •  
    Portugal

Posted 02 March 2017 - 09:26 PM

tested with one-liner initrd... exactly the same behaviour...

title BootMgr1 (WimBoot)
    #pxe keep
    kernel /wimboot
    initrd @bootmgr=/boot/bootmgr @boot.sdi=/boot/boot.sdi @memdisk=/boot/memdisk @bcd=/boot/bcd @x.wim=/{wim}/win10pese32.wim

 

​even try(ed) some alternative stuff... but no luck...

​title BootMgr2 (WimBoot)
    kernel /wimboot
    initrd @/bootmgr=/boot/bootmgr @/boot/boot.sdi=/boot/boot.sdi @/boot/bcd=/boot/bcd @/x.wim=/{wim}/win10pese32.wim



#6 steve6375

steve6375

    Platinum Member

  • Developer
  • 6598 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars
  •  
    United Kingdom

Posted 02 March 2017 - 09:35 PM

What is /{wim} ??? Is that valid syntax? I have not seen that before? Is @x.wim= valid syntax?

 

The syntax is (AFAIK)

kernel /wimboot
initrd @bcd=/WIN7/boot/bcd @boot.sdi=/WIN7/boot/boot.sdi @bootmgr=/WIN7/bootmgr @boot.wim=/WIN7/sources/boot.wim

Did you try:

kernel /wimboot
initrd @bootmgr=/boot/bootmgr @boot.sdi=/boot/boot.sdi @memdisk=/boot/memdisk @bcd=/boot/bcd @boot.wim=/win10pese32.wim

and maybe also try omitting the memdisk entry?


  • ZEE likes this

#7 ZEE

ZEE

    Member

  • Members
  • 80 posts
  •  
    Portugal

Posted 03 March 2017 - 12:08 AM


​Yes,,, already try that...

​I' finding hard to get documentation about what initrd do (tech stuff)

​and also how to inspect the results (like listing the memdisk contents)

​that would be very useful to debug what is happening...

​if someone about this stuff please shed some light/links...

​;-)



#8 ady

ady

    Frequent Member

  • Advanced user
  • 130 posts

Posted 03 March 2017 - 05:56 AM

​​and also how to inspect the results


I'm not sure that looking at the content of INITRD files would actually help you with your current problem; you would need to actually know what you are looking for.

FWIW, I have used 7-zip to see/navigate the content of (some) INITRD files. Sometimes you need to use 7-zip recursively (in a similar way as opening a ".tar.gz" file). There are other tools too.

#9 steve6375

steve6375

    Platinum Member

  • Developer
  • 6598 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars
  •  
    United Kingdom

Posted 03 March 2017 - 08:52 AM

A good description of wimboot can be found here

http://www.mistyrebo...npe_wimboot.htm

It says that he did not have any success using the method on post #1.

Do we know if anyone has had success using this method (grub4ds + PXE + wimboot to .wim)?

 

 Does this work if booting directly from a drive (and not via PXE?).



#10 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1920 posts
  • Location:Nantes - France
  •  
    France

Posted 03 March 2017 - 02:22 PM

*
POPULAR

I am using grub4dos 0.4.6a (2015-08-25).

Wimboot works for me if i go back to wimboot 2.0 (versus 2.5.2).

Latest version reboots after completing the download of boot.wim.

Latest version works smoothly with ipxe but is more challenging with other network boot loaders.

title wimboot
kernel /wimboot200
initrd @bcd=/boot/bcd @boot.sdi=/boot/boot.sdi @bootmgr=/bootmgr @boot.wim=/sources/boot.wim

  • tinybit, steve6375 and ZEE like this

#11 ZEE

ZEE

    Member

  • Members
  • 80 posts
  •  
    Portugal

Posted 05 March 2017 - 07:03 PM

 

I am using grub4dos 0.4.6a (2015-08-25).

Wimboot works for me if i go back to wimboot 2.0 (versus 2.5.2).

Latest version reboots after completing the download of boot.wim.

Latest version works smoothly with ipxe but is more challenging with other network boot loaders.

title wimboot
kernel /wimboot200
initrd @bcd=/boot/bcd @boot.sdi=/boot/boot.sdi @bootmgr=/bootmgr @boot.wim=/sources/boot.wim

 

​Erwan... You nailed it again... plein dans le mille...

​fetching the wimboot version you suggested (2.0) solved it immediatly...

​Just 2 confirmations about initrd syntax:

​1) it must by one-liner... vg  ->  initrd @grldr=/grldr @grldr.mbr=/grldr.mbr

​2) you must prefix the filepath with filename just like -> initrd @boot.wim=/x.wim

​then evething dance nicely... wimboot and TFTP



#12 tinybit

tinybit

    Gold Member

  • Developer
  • 1051 posts
  •  
    China

Posted 06 March 2017 - 03:23 AM

 

​Erwan... You nailed it again... plein dans le mille...

​fetching the wimboot version you suggested (2.0) solved it immediatly...

​Just 2 confirmations about initrd syntax:

​1) it must by one-liner... vg  ->  initrd @grldr=/grldr @grldr.mbr=/grldr.mbr

​2) you must prefix the filepath with filename just like -> initrd @boot.wim=/x.wim

​then evething dance nicely... wimboot and TFTP

And thank you for this confirmation.


  • ZEE likes this





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

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users